Re: fix dom0 crash on large machines

["Christoph Egger" <Christoph_Egger%gmx.de@localhost>]

> On Tue, Nov 24, 2009 at 04:23:03PM +0100, Christoph Egger wrote:
> > > wow.
> > 
> > NetBSD Dom0 didn't boot through to the login, though.
> > The boot stopped with an endless loop of
> > 
> > probe(mpt0:0:1:0): command timeout
> > mpt0: recovered from command timeout
> 
> 
> Hum, could be a bus_dma issue. But I succefully ran NetBSD 5
> on a 48Gb machine with mpt and bnx devices with my patch for
> an additionnal 16Mb-4Gb freelist. Could you try with this patch?

That was already with your patch.
 
> > The mpt0 is a
> > 
> > mpt0 at pci2 dev 0 function 0: Symbios Logic SAS1064E
> > linkdev LN20 returned ACPI global irq 76, line 76
> > ioapic2: int20 0x1807b<vector=0x7b,delmode=0x0,level,masked,dest=0x0>
> 0x10000000<target=0x10>
> > mpt0: interrupting at ioapic2 pin 20, event channel 8
> > mpt0: Phy 0: Link Rate 3.0 Gbps
> > scsibus0 at mpt0: 112 targets, 8 luns per target
> > 
> > and disabling mpt0 in userconf ended with
> > 
> > nfs_boot: trying DHCP/BOOTP
> > bge0: watchdog timeout -- resetting
> > nfs_boot: timeout...
> > bge0: watchdog timeout -- resetting
> > nfs_boot: timeout...
> > bge0: watchdog timeout -- resetting
> > nfs_boot: timeout...
> 
> but it could also be an interrupt routing issue; for both
> devices.

That is what Marthin Husemann said, too.

> Could you try a native NetBSD kernel ?

That's difficult in a testenvironment with having
pxegrub everywhere.

Would be possible when boot(8) is bootable from grub via
multiboot support.

Christoph