[Bug 24533] Re: [Bug 24533] Re: Fail to boot smp kernel

[Richard Green]

> I'm not sure how to can get X to start while staying in the console to
> see any kernel messages.
   I don't know either.  On my previous system (SuSE), I had available a 
runlevel 3with a text console, and I could start X explicitly after I had 
logged in.  I haven't found a similar config in Kubuntu.  I was wondering 
about uninstalling kdm.  Would that let me boot to a tty login prompt, so 
that I could login, then start X?  That might help determine if it's kdm 
or X itself that's tripping up the kernel... ...or would that just break 
the system?

> Have you checked /var/log/kern.log to see if
> anything is captured there?
   I checked that.  The last 20 messages or so were exactly the same, both 
when pooting the 686 kernel and crashing, and the 386 kernel successfully.
>
> Have you tried booting the SMP kernel with nosmp boot option?
   I did try that as well.  Very strange results!  WHen I add the 'nosmp' 
option and boot, the boot seems to take forever, I get a plethora of 
spurious 'lost interrupt' messages, finally culminating with a message to 
the effect of 'hda1 does not exist' and it drops me into a busybox shell. 
My hard disk isn't mounted, but I was able to `cat /proc/cpuinfo' and 
verify that it was indeed running in uniprocessor mode.  Since I couldn't 
mount the root pertition, I made no attempt to start X (startx isn't one 
of busybox's builtin commands!)

-- 
Fail to boot smp kernel
https://launchpad.net/bugs/24533