Ubuntu

PCI Failure in Precise

Reported by Martin Owens on 2012-01-18
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned

Bug Description

I talked with awp on irc about how to report this issue. In the report below you will see a working set of logs from dmesg and a working lspci. I will add to this a log containing the non-working dmesg and lspci

Basically for 90% of boots the computer fails to load because it can't load the graphics driver. You can actually tell when the boot will work because it will show the full plymouth boot animation. In all other cases it's either the text plymoth or a purple screen which then goes to black and a non-functioning computer. Requiring a hard reset.

Bug appeared in Maverick 2.6.35 and has been in each release since.

WORKAROUND: pci=bios

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-9-generic 3.2.0-9.16
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: doctormo 1778 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf8400000 irq 49'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,14c00025,00100003 HDA:10573055,10573055,00100700'
   Controls : 16
   Simple ctrls : 11
CheckboxSubmission: d6ae92d4f627f9865ce2f781868281ef
CheckboxSystem: 3e53d3ea5811723345f19eff5070f9ab
Date: Wed Jan 18 13:25:45 2012
HibernationDevice: RESUME=UUID=4bd5c23a-d20d-4480-8f64-2408029a3aa4
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: - N/A
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-9-generic root=UUID=f7620e66-8613-4617-98cf-ac233253bcc0 ro ”pci=noacpi” quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-9-generic N/A
 linux-backports-modules-3.2.0-9-generic N/A
 linux-firmware 1.67
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-01-17 (1 days ago)
dmi.bios.date: 12/31/2007
dmi.bios.vendor: COMPAL
dmi.bios.version: 1.16
dmi.board.name: JFL92
dmi.board.vendor: -
dmi.board.version: IFT00
dmi.chassis.asset.tag: -
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnCOMPAL:bvr1.16:bd12/31/2007:svn-:pnN/A:pvrN/A:rvn-:rnJFL92:rvrIFT00:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: N/A
dmi.product.version: N/A
dmi.sys.vendor: -

Martin Owens (doctormo) wrote :
Brad Figg (brad-figg) on 2012-01-18
Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Martin Owens (doctormo) wrote :

Some additional information before I build the upstream kernel:

In my attempts to boot into recovery I could not get a successful boot. It would always stop on:

pci: 00.000.01 ICH7 LPC Generic IO decode 4 PIO at 1640 (mask 007f)

I've just gone through the kernel's pci boot options. Almost all of them have no effect except for pci=bios which causes the computer to boot into both recovery mode and into normal Ubuntu 12.04 flawlessly. I've booted 8 times with this option set to make sure it's not intermittent.

Martin Owens (doctormo) on 2012-01-18
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-10.17
Martin Owens (doctormo) on 2012-01-20
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: bot-stop-nagging
Brad Figg (brad-figg) on 2012-02-16
Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: lucid maverick natty needs-upstream-testing oneiric
removed: kernel-bug-exists-upstream kernel-request-3.2.0-10.17
description: updated

Martin Owens, 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 remove your WORKAROUND, and provide the information following https://wiki.ubuntu.com/DebuggingKernelBoot ? As well, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.