kernels after 2.6.32-17 have random failures in booting

[brian mullan]

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.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bmullan 1473 F.... pulseaudio
 /dev/snd/controlC1: bmullan 1473 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a002,00100101'
   Controls : 40
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'U0x41e0x4058'/'Creative Labs USB Device 0x41e:0x4058 at usb-0000:00:12.2-3.2, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB041e:4058'
   Controls : 3
   Simple ctrls : 2
Card2.Amixer.info:
 Card hw:2 'HDMI'/'HDA ATI HDMI at 0xfdefc000 irq 19'
   Mixer name : 'ATI RS690/780 HDMI'
   Components : 'HDA:1002791a,00791a00,00100000'
   Controls : 4
   Simple ctrls : 1
Card2.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 10.04
Frequency: Once every few days.
HibernationDevice: RESUME=UUID=89d30e2f-8b6f-4f0c-87bf-f73f4a0fb00b
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=fcd975bd-3c1b-48c2-8c26-4bd63bfeb8f0 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Regression: No
RelatedPackageVersions: linux-firmware 1.34.1
Reproducible: No
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: lucid needs-upstream-testing
Uname: Linux 2.6.32-24-generic x86_64
UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare
dmi.bios.date: 02/10/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8a
dmi.board.name: GA-MA78GM-S2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8a:bd02/10/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78GM-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78GM-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA78GM-S2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Mitch Towner (kermiac)]

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.

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

apport information

[brian mullan (bmullan)]

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 <<email address hidden>
> 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.
>

[brian mullan (bmullan)]

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 <email address hidden>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 <
> <email address hidden>> 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.
>>
>
>

[brian mullan (bmullan)]

update - tonite I reboot this *same system* and now *2.6.32-24 will
not*completely boot to login again

BUT again 2.6.32-17 boots right up and works?

Something introduced after -17 kernel update is causing the problem.

Brian

On Tue, Jul 27, 2010 at 9:27 AM, brian mullan <email address hidden>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 <
> <email address hidden>> 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
>...

[brian mullan (bmullan)]

attached is my /var/log/kern.log file

On Sat, Jul 31, 2010 at 1:57 AM, Mitch Towner <<email address hidden>
> wrote:

> ** Tags removed: needs-kernel-logs
>
> --
> 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.
>

[WalterHangartner (walter-hangartner)]

With maverick about half the boots work. I have a 10.04 on same machine, and this boots all the time. I have ATI Radeon HD4550 graphics with HDMI. I use open source drivers. When the boot does not complete, then I have a strange pattern on screen, the top third of screen is black and below is this pattern.

I have the impression that it stops just before outputing the welcome sound.

I can however shudown by shortly pressing the power button on computer, there comes a terminal window and shutdown succeeds

[Jeremy Foshee (jeremyfoshee)]

Hi folks,
   We have discovered that this was due to a race occurring during boot where we change framebuffers in an odd fashion. we have put a fix in the maverick tree and released a kernel that should address this issue. Would those of you affected mind taking a look at it?

Also, for reference, it is the kernel team's policy that any person affected by an issue file their own bug for that issue even if they should find a bug that fits their problem exactly. This is explained a bit better in https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs

Those of you still affected after your testing of the latest maverick, please file new bugs for your issues.

Thanks!

~JFo

[brian mullan (bmullan)]

thanks Jeremy... I knew there had to be something along those lines causing
this.

I'll try to fix and let you know as my encountering this problem is pretty
consistent each week.

On Thu, Aug 12, 2010 at 10:19 AM, Jeremy Foshee
<email address hidden>wrote:

> Hi folks,
> We have discovered that this was due to a race occurring during boot
> where we change framebuffers in an odd fashion. we have put a fix in the
> maverick tree and released a kernel that should address this issue. Would
> those of you affected mind taking a look at it?
>
> Also, for reference, it is the kernel team's policy that any person
> affected by an issue file their own bug for that issue even if they
> should find a bug that fits their problem exactly. This is explained a
> bit better in https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
>
> Those of you still affected after your testing of the latest maverick,
> please file new bugs for your issues.
>
> Thanks!
>
> ~JFo
>
> --
> 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.
>

[brian mullan (bmullan)]

I've been trying to use the new kernel updates for 10.10 as they come out
and have tried both

   - 2.6.35-14
   - 2.6.35-15

Neither appears to be solving this problem with random boot failures ...
where it never gets to the login spash screen.

Recovery doesn't seem to work either.

But if I try 5-6 times. It will eventually boot again.

Brian

On Thu, Aug 12, 2010 at 1:04 PM, brian mullan <email address hidden>wrote:

> thanks Jeremy... I knew there had to be something along those lines causing
> this.
>
> I'll try to fix and let you know as my encountering this problem is pretty
> consistent each week.
>
>
>
> On Thu, Aug 12, 2010 at 10:19 AM, Jeremy Foshee <<email address hidden>
> > wrote:
>
>> Hi folks,
>> We have discovered that this was due to a race occurring during boot
>> where we change framebuffers in an odd fashion. we have put a fix in the
>> maverick tree and released a kernel that should address this issue. Would
>> those of you affected mind taking a look at it?
>>
>> Also, for reference, it is the kernel team's policy that any person
>> affected by an issue file their own bug for that issue even if they
>> should find a bug that fits their problem exactly. This is explained a
>> bit better in https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
>>
>> Those of you still affected after your testing of the latest maverick,
>> please file new bugs for your issues.
>>
>> Thanks!
>>
>> ~JFo
>>
>> --
>> 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.
>>
>
>

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[brian mullan (bmullan)]

it is still affecting 10.10 ... at least on my machine but not as bad as on
10.04.

On 10.04 its gotten better as it fails to boot less often BUT again on 10.04
with th .17 kernel it ALWAYS boots.

On Wed, Sep 22, 2010 at 11:52 PM, Jeremy Foshee
<email address hidden>wrote:

> This bug report was marked as Incomplete and has not had any updated
> comments for quite some time. As a result this bug is being closed.
> Please reopen if this is still an issue in the current Ubuntu
> development release http://cdimage.ubuntu.com/daily-live/current/ .
> Also, please be sure to provide any requested information that may have
> been missing. To reopen the bug, click on the current status under the
> Status column and change the status back to "New". Thanks.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: kj-expired
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Expired
>
> --
> 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.
>