-   Linux - Kernel (
-   -   Boot freezes with 2.6.35-31 generic-pae on Ubuntu 10.04 (

tauro_kpo 01-01-2012 09:58 PM

Boot freezes with 2.6.35-31 generic-pae on Ubuntu 10.04
Hello everyone, happy 2012 by the way.

I'm using Ubuntu 10.04 and I'm trying to boot kernel 2.6.35-31 generic-pae. Everything seems to go fine until this line


udev: starting version 151
There the booting process freezes, and it doesn't go on at all.

Version 2.6.35-30 generic present this same problem too. But 2.6.35-25 generic works. It's funny, isn't it? Why is it that the newer versions stop working at that point? How could I fix this?

Thank you very much in advance

tauro_kpo 01-10-2012 02:36 AM

Please, anybody?

nini09 01-11-2012 02:16 PM

Can you post 2.6.35-25 generic and 2.6.35-30 generic boot-up message?

tauro_kpo 01-11-2012 08:00 PM

Thanks for helping nini09!

What is exactly the generic boot-up message? Where can I find it to post it?

Sorry for my ignorance, thanks again.

nini09 01-12-2012 03:07 PM

For good one, 2.6.35-25 generic, dmsg command can dump all boot-up message.
For bad one, 2.6.35-30 generic, maybe on the screen only because boot-up is failure, writing down screen if you can.

tauro_kpo 01-13-2012 04:29 AM

2 Attachment(s)

here I attached the complete output of dmesg from the working 2.6.35-25 generic as a text file (it's too big to post it here).

And I've also attached a screen cap of the output of the 2.6.35-30 generic (which is exactly the same as it is shown when trying to run 2.6.35-31 generic-pae). I got it by removing quiet and adding verbose to the kernel booting arguments.

As you will see, after the udev message, it says something like "loading init scripts" which I think seems odd (I don't have such thing as folder /scripts).

It's strange isn't it? What could you tell me to do to fix this?

Thank you very much.

PS: Funny thing, after trying to boot those kernels (30 or 31) a couple of times, this line was automatically added to the booting arguments: crashkernel=384M-2G:64M,2G-:128M
But the same error persists.

nini09 01-13-2012 02:50 PM

It look like one driver of new kernel, maybe USB or Ethernet, has some bug on your machine to cause boot-up failure and try loading image again like you mentioned running init-script again.
You can stay in old one and wait next update or search Ubuntu bug database to see whether they fix it.

tauro_kpo 01-13-2012 02:58 PM


try loading image again like you mentioned running init-script again.
What did I mention? which init-script? Sorry for my ignorance.

I guess I'll stick with the old one, and wait until an update with a fix is released.

Should I report the bug? or perhaps it is already reported?

nini09 01-16-2012 02:34 PM

It is better to report a bug because you can trace it and know when the issue is fixed. But you will have more job to do. You have to isolate which driver cause the issue.

All times are GMT -5. The time now is 04:08 AM.