[Bug 610200] [NEW] kernels after 2.6.32-17 have random failures in booting

Tue Jul 27 11:22:31 UTC 2010

You have been subscribed to a public bug:

In Lucid (10.04)...

I've had a problem on my AMD based machine, 4core, Gigabyte ga-ma78gm-
s2h Motherboard, 8GB mem, two 2 SATA terabyte HDs.

One thing I've found is that ANY kernel *AFTER*   2.6.32-17
has this randomness at boot time whether the system will completely boot or not.

Today I downloaded and installed 2.6.32-24

It fails to boot (I've tried cold boot, warm boot).
** Running repair also fails to completely boot and I'm unable to even get to a command prompt.

My experience is that if I keep trying it "may" eventually boot but
I believe there was some change AFTER  2.6.32-17
that's causing the problem (plymouth?)

2.6.32.23... also fails to complete bootup many times but eventually will... 
eventually my guess is that 2.6.32.24 will also boot "sometimes".

But why does 2.6.32.17 -ALWAYS- boot for me?   I guess that's the clue
I'm sending.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

-- 
kernels after 2.6.32-17 have random failures in booting
https://bugs.edge.launchpad.net/bugs/610200
You received this bug notification because you are a member of Kernel Bugs, which is subscribed to linux in ubuntu.