Enabling SMP causes boot failure

Enabling SMP causes boot failure

[Matt Brei]

I'm using 2.6.18.1 on a dual Athlon MP 1800+ machine with SMP disabled
which works just fine.  As soon as I enable SMP in the kernel, I get a
bunch of errors about nbdX sending on a closed socket, the device
mapper and the kernel fails with No volume groups found.  If I disable
Network Block Devices and enable LVM and Device Mapper, the nbd and
device map errors stop but I still have the volume group error and a
boot failure.

Any idea why?

Thanks,
Matt

Re: Enabling SMP causes boot failure

[Erik Mouw]

On Tue, Oct 24, 2006 at 08:10:39PM -0500, Matt Brei wrote:
> I'm using 2.6.18.1 on a dual Athlon MP 1800+ machine with SMP disabled
> which works just fine.  As soon as I enable SMP in the kernel, I get a
> bunch of errors about nbdX sending on a closed socket, the device
> mapper and the kernel fails with No volume groups found.  If I disable
> Network Block Devices and enable LVM and Device Mapper, the nbd and
> device map errors stop but I still have the volume group error and a
> boot failure.
> 
> Any idea why?

Nope. Please supply more information. Boot log from SMP and non-SMP,
kernel config, distribution, compiler version etc. would be nice. See
REPORTING-BUGS in your kernel source tree.


Erik
[running a dual Athlon MP 1800+]

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

Re: Enabling SMP causes boot failure

[Bill Davidsen]

Matt Brei wrote:

> I'm using 2.6.18.1 on a dual Athlon MP 1800+ machine with SMP disabled
> which works just fine.  As soon as I enable SMP in the kernel, I get a
> bunch of errors about nbdX sending on a closed socket, the device
> mapper and the kernel fails with No volume groups found.  If I disable
> Network Block Devices and enable LVM and Device Mapper, the nbd and
> device map errors stop but I still have the volume group error and a
> boot failure.
>
> Any idea why? 


None, but things like this are related to acpi issues often enough to 
make some boot time acpi options worth trying. Also: try booting the smp 
kernel with the "nosmp" option. That's not the same as the uni kernel, 
and might aid in telling unhappy kernel from unhappy hardware.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979