Messages in this thread | | | Date | Tue, 24 Jul 2007 10:51:35 +0200 | From | Tilman Schmidt <> | Subject | Re: 2.6.22-git17 boot failure |
| |
Jeremy Fitzhardinge schrieb: > Well, it looks to me like it all falls over once it hits usermode; > everything up till then is identical (except for the Xen-related > initcalls which naturally don't exist in the non-Xen case).
Just a wild thought: could the actual problem be with accessing the initrd? After all, everything that's failing is based on modules which are stuffed there. But I know far too less about initrd to pursue this thought further.
> I'm at a loss. I don't know if there's some way to debug the initrd in > more detail. I suspect that its failing all PCI probing, rather being a > specific SCSI/AHCI problem (since none of the other messages appear either). > > Does the Xen case just hang, or reboot, or what? The kernel messages > just appear to stop. I'd expect it to at least complain about not > mounting the root filesystem or something.
Yes, of course. Sorry, I thought I'd mentioned that. It shows the standard behaviour of a Suse that cannot mount its root filesystem: first a message: "waiting for /dev/system/root to appear" followed by a series of dots, and then fallback into a standalone /bin/sh.
> Andi, any thoughts about how to debug the suse boot sequence? > > J
<listening eagerly>
T.
-- Tilman Schmidt E-Mail: tilman@imap.cc Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[unhandled content-type:application/pgp-signature] | |