[Regression] System freezes often during booting

Bug #550382 reported by Stefan Krause
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

My laptop used to boot fine with karmic 32bit. I boot it a few times a day and haven't noticed any problems.
I installed lucid when it was at Alpha 2 and used it daily since then. About a week ago I got random freezes during booting. (Certainly with 2.6.32-17, I'm not sure about 2.6.32-16).

I confirmed that upstream 2.6.33-020633-generic has the same problem.

Please note that I had the same issues for the 64 bit version since karmic(!), but the 32 bit version worked nicely, so I thought it was a 64 bit issue. Switching to 32 bit was an acceptable workaround, but now that the 32 bit doesn't boot most of the time I'm close to desperation (since it means I must switch back to Windows after 7 years...).

The last line printed on the screen is:
[ 0.529300] ata_piix 0000:00:1f.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16

After that the system can only be powered off, rebooting is not possible.

I'd say that the system freezes with a probability of about 50-75%.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-17-generic 2.6.32-17.26
Regression: Yes
Reproducible: Yes
TestedUpstream: Yes
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: stef 1404 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xec004000 irq 23'
   Mixer name : 'SigmaTel STAC9271D'
   Components : 'HDA:83847627,30d4103c,00100201'
   Controls : 24
   Simple ctrls : 14
Date: Sun Mar 28 19:34:48 2010
HibernationDevice: RESUME=UUID=4a0d35a4-112a-4402-97d4-ebcf2957c552
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=14354146-d8e3-403f-8981-25a46d0a41d2 ro
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.33
SourcePackage: linux
dmi.bios.date: 08/29/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DVD Ver. F.40
dmi.board.name: 30E2
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 87.0B
dmi.chassis.asset.tag: CNU82623PK
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68DVDVer.F.40:bd08/29/2008:svnHewlett-Packard:pn:pvrF.40:rvnHewlett-Packard:rn30E2:rvrKBCVersion87.0B:cvnHewlett-Packard:ct10:cvr:
dmi.product.version: F.40
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Stefan Krause (stefan-krause) wrote :
description: updated
Revision history for this message
Stefan Krause (stefan-krause) wrote :

Related bugs are: https://bugzilla.kernel.org/show_bug.cgi?id=14244&action=View
for the 64 bit version (at that time the 32 bit version still worked fine): https://bugs.launchpad.net/ubuntu/+bug/410984

Revision history for this message
Stefan Krause (stefan-krause) wrote :

Screenshot when system is frozen added.

Comparing to a dmesg output of a successful boot I fail to see much difference.
All in all I found 4 lines that appear to be missing in the screenshot:

[ 0.499001] Monitor-Mwait will be used to enter C-1 state
[ 0.499021] Monitor-Mwait will be used to enter C-2 state
[ 0.499041] Monitor-Mwait will be used to enter C-3 state
...
[ 0.535785] ata_piix 0000:00:1f.1: version 2.13

Revision history for this message
Stefan Krause (stefan-krause) wrote :

I checked again. Here are my findings:

Out of 5 attempts lucid booted 2 times successfully with 2.6.32-17 and froze 3 times with that version.
Lucid booted 8 times successfully with 2.6.32-16 (2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:52 UTC 2010 i686 GNU/Linux) and no freezes could be observed

I'm pretty sure that the regression was introduced with -17.

I'll attach the dmesg for -16 and -17 and the diff (after timing output has been removed).

The one difference I could find is that -16 prints something like
 scsi0 : ahci
 scsi1 : ahci
 scsi2 : ahci
 ata1: SATA max UDMA/133 abar m2048@0xec009000 port 0xec009100 irq 31
 ata2: SATA max UDMA/133 abar m2048@0xec009000 port 0xec009180 irq 31
 ata3: SATA max UDMA/133 abar m2048@0xec009000 port 0xec009200 irq 31

and -17 prints
  scsi0 : ata_piix
 scsi1 : ata_piix
 ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x70a0 irq 14
 ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x70a8 irq 15

Since the ata_piix message has as far as I remember always been the last line I suspect that the issue could have to do with that output.

What can I check next?

Revision history for this message
Stefan Krause (stefan-krause) wrote :
Revision history for this message
Stefan Krause (stefan-krause) wrote :
Revision history for this message
Stefan Krause (stefan-krause) wrote :
Revision history for this message
Stefan Krause (stefan-krause) wrote :
Revision history for this message
Stefan Krause (stefan-krause) wrote :

Some more notes:
I compiled both kernel 2.6.34-rc2 and 2.6.32.10 with make oldconfig based on the linux-image-2.6.32-16, but that didn't help. It freezes about half the time when booting.

OpenSuse 11.3 M4 (kernel-2.6.33) on the other hand boots without problems.

Any idea what I could try next?

Revision history for this message
Stefan Krause (stefan-krause) wrote :

Compiled a few kernels and played with the options.
Even a minimal configuration with "Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support (ATA_PIIX)" enabled (the only other selected option is "AHCI SATA support") leads to the freezes.
If I remove the ATA_PIIX option booting appears to work (5 times without problems), but my blureay/dvd-drive is not recognized or prints lots of errors in dmesg ATA/ATAPI/MFM/RLL support (DEPRECATED))

What's the next thing I should do?

Revision history for this message
Stefan Krause (stefan-krause) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Stefan,

If you could also please 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.

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

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Esau B. (e-baqi) wrote :

I too am experiencing freezing of my computer ever since I upgraded to Lucid. Never had the problem in the past 2 versions of Ubuntu, but at least 15 times a day with the stock kernel that came with 10.04. When I downgraded back to Karmic (9.10) the problem disappeared, but when I reinstalled Lucid the freezing started again, and the only way to fix it was to do a hard reset (hold power button down until restart). I then tried the latest mainline kernel, currently 2.6.34-020634-generic on my laptop,and though it's better in terms of it freezing, only 5 times now in the span of a few days, it still has not fixed the freezing problem.

I'm not sure how to print up any reports that might be relevant so please let me know what type of information you would like to help fix the problem.

Thanks.

tags: removed: regression-potential
Revision history for this message
Joe Burgess (joemburgess) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 550382 and any other logs that are relevant for this particular issue.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.