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

brian mullan 610200 at bugs.launchpad.net
Tue Jul 27 22:08:46 UTC 2010


Update... and tonite I rebooted same machine and -24 fails.... but again -17
boots right up

On Tue, Jul 27, 2010 at 9:27 AM, brian mullan
<bmullan.mail at gmail.com>wrote:

> First, as I'd said in the bug report... its a hit or miss whether the newer
> kernels (post -17) boot completely or not.
>
> This morning... the very same *2.6.32-24* kernel booted right up first
> time?   Last night I tried a dozen times both cold and warm boot and it
> would never get to login screen just the blinking cursor then a blank
> screen.
>
> Running Repair did little more than that except I could at least do a
> ctrl-alt-del to reboot instead of a hard reset.
>
> This has been a random problem with every kernel since *2.6.32-17* which
> has always booted up.  So the only thing my "bug" report was filed for was
> to perhaps give a timeframe for when the problem was introduced.    I've
> seen on the ubuntu forums that many people are seeing this same issue or at
> least one very similar to it.   The descriptions vary but when I read the
> text about frozen boot, or boots to a blank screen etc. most sounded like
> the same issue.
>
> Anyway... I sent the debug info just now.
>
> You can close this bug if you want I just was hoping to give you guys the
> timeframe.
>
> thanks.
> Brian
>
>
>
> On Tue, Jul 27, 2010 at 6:22 AM, Mitch Towner <
> mitch.towner.ubuntu at gmail.com> wrote:
>
>> Thank you for taking the time to report this bug and helping to make
>> Ubuntu better. This bug did not have a package associated with it, which
>> is important for ensuring that it gets looked at by the proper
>> developers. You can learn more about finding the right package at
>> https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this
>> bug as a bug in linux.
>>
>> When reporting bugs in the future please use apport, either via the
>> appropriate application's "Help -> Report a Problem" menu or using
>> 'ubuntu-bug' and the name of the package affected. You can learn more
>> about this functionality at https://wiki.ubuntu.com/ReportingBugs.
>>
>> Please run the following command from a terminal window to automatically
>> gather and attach updated debug information to this report.
>>
>> apport-collect 610200
>>
>> Also, if you could test the latest upstream kernel available that would
>> be great. It will allow additional upstream developers to examine the
>> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once
>> you've tested the upstream kernel, please remove the 'needs-upstream-
>> testing' tag. This can be done by clicking on the yellow pencil icon
>> next to the tag located at the bottom of the bug description and
>> deleting the 'needs-upstream-testing' text. Please let us know your
>> results.
>>
>> Thanks in advance.
>>
>> ** Package changed: ubuntu => linux (Ubuntu)
>>
>> ** Changed in: linux (Ubuntu)
>>       Status: New => Incomplete
>>
>> ** Tags added: lucid needs-kernel-logs needs-upstream-testing
>>
>> --
>> kernels after 2.6.32-17 have random failures in booting
>> https://bugs.launchpad.net/bugs/610200
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

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




More information about the kernel-bugs mailing list