sporadic boot hang; possible kernel panic

Bug #696042 reported by pip
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Boot hangs with 'lock' lights flashing in synchronisation. A hard boot is the only cure.
This occurs more than once daily & is very unpredictable. Consequently I am unable to reproduce this bug on either of two machines that it occurs on.

The last stable kernel was 2.6.35-23.

2.6.37-10 would not boot at all without acpi=off, so this is an improvement on that.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.37-11-generic 2.6.37-11.25
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7
Uname: Linux 2.6.37-11-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pip 931 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with ALC250 at irq 17'
   Mixer name : 'Realtek ALC250 rev 2'
   Components : 'AC97a:414c4752'
   Controls : 33
   Simple ctrls : 21
Date: Fri Dec 31 16:20:01 2010
Frequency: Once a day.
HibernationDevice: RESUME=UUID=52a28855-ab72-4233-8efe-cbb9237efa24
InstallationMedia: Lubuntu 10.10 "Maverick Meerkat" - i386 (20101010)
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: RM plc IAL55
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-11-generic root=UUID=6d2cc3e2-26e8-4e7c-ba53-99bd17209ec9 ro vt.handoff=7 quiet splash
RelatedPackageVersions: linux-firmware 1.44
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 04/25/2006
dmi.bios.vendor: Insyde Software Corporation
dmi.bios.version: 1.01A
dmi.board.name: Alviso
dmi.board.vendor: Intel Corporation
dmi.board.version: V1.0
dmi.chassis.type: 10
dmi.chassis.vendor: COMPAL
dmi.modalias: dmi:bvnInsydeSoftwareCorporation:bvr1.01A:bd04/25/2006:svnRMplc:pnIAL55:pvr:rvnIntelCorporation:rnAlviso:rvrV1.0:cvnCOMPAL:ct10:cvr:
dmi.product.name: IAL55
dmi.sys.vendor: RM plc

Revision history for this message
pip (verymadpip) wrote :
tags: added: regression-release
removed: regression-update
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

pip, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please report the results following https://wiki.ubuntu.com/DebuggingKernelBoot ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
pip (verymadpip) wrote : Re: [Bug 696042] Re: sporadic boot hang; possible kernel panic

Christopher,

I'm pleased to tell you that this issue was cleared up in the final release.
I'm also pleased to say that the issue has not reoccured (for me at any
rate) since it was fixed. It may be worth noting that the hardware
involved initially (both machines) is no longer available to test on, so
perhaps that may be a factor. Having said that, the hardware
replacements are quite recent, but the issue had gone away anyway.

Regards,

Pip

On 08/04/12 20:41, Christopher M. Penalver wrote:
> pip, thank you for reporting this and helping make Ubuntu better. This
> bug was reported a while ago and there hasn't been any activity in it
> recently. We were wondering if this is still an issue? If so, could you
> please report the results following
> https://wiki.ubuntu.com/DebuggingKernelBoot ? As well, can you try with
> the latest development release of Ubuntu? ISO CD images are available
> from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command in the
> development release from a Terminal
> (Applications->Accessories->Terminal). It will automatically gather and
> attach updated debug information to this report.
>
> apport-collect -p linux<replace-with-bug-number>
>
> 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.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

Revision history for this message
penalvch (penalvch) wrote :

pip, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.