1002:7188 Can't boot 13.04 raring without nomodeset, worked with earlier kernels.

Bug #1180557 reported by Josef Andersson
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

With my hp6910p the last kernel to work without nomodeset on my computer was 3.2x (Ubuntu 12.04). After that, Kernel 3.5 (Ubuntu 12.10) and kernel 3.8 (ubuntu 13.04) only gives black boot screen.

WORKAROUND: nomodeset

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-20-generic 3.8.0-20.31
ProcVersionSignature: Ubuntu 3.8.0-20.31-generic 3.8.11
Uname: Linux 3.8.0-20-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kina 2173 F.... pulseaudio
Date: Wed May 15 23:01:27 2013
HibernationDevice: RESUME=UUID=7463a7db-abb4-471c-8e75-50db13c55ced
InstallationDate: Installed on 2012-11-16 (180 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: Hewlett-Packard HP Compaq 6910p (GB951EA#AK8)
MarkForUpload: True
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-20-generic root=UUID=0fe3effd-9cec-4d38-8364-c2fe1869b0f3 ro nomodeset quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-20-generic N/A
 linux-backports-modules-3.8.0-20-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-04-27 (18 days ago)
dmi.bios.date: 07/06/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MCD Ver. F.19
dmi.board.name: 30C1
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 68.36
dmi.chassis.asset.tag: CND7421506
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68MCDVer.F.19:bd07/06/2010:svnHewlett-Packard:pnHPCompaq6910p(GB951EA#AK8):pvrF.19:rvnHewlett-Packard:rn30C1:rvrKBCVersion68.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6910p (GB951EA#AK8)
dmi.product.version: F.19
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Josef Andersson (northar) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote : Re: Can't boot 13.04 raring without nomodeset, worked with earlier kernels.

northar, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

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

Also, 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 mainline kernels archive directory 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. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

description: updated
tags: added: needs-upstream-testing regression-release
tags: added: latest-bios-f.19
tags: added: quantal
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - Can't boot 13.04 raring without nomodeset, worked with earlier kernels.
+ 1002:7188 Can't boot 13.04 raring without nomodeset, worked with earlier
+ kernels.
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Josef Andersson (northar) wrote :

1.
Tried daily, and it wont even boot with nomodeset - tried all other options too that are available in boot menu, like acpi=off and so on. Screen goes black with blinking cursor no matter what now.
2. Next: will test with mainline kernel.

Revision history for this message
Josef Andersson (northar) wrote :

Mailine v3.10-rc2 tested, same (no luck) result. Updated tags.

tags: added: kernel-bug-exists-upstream kernel-fixed-upstream-v3.10-rc2
tags: added: kernel-exists-upstream-v3.10-rc2
removed: kernel-fixed-upstream-v3.10-rc2
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: removed: needs-upstream-testing
tags: added: kernel-bug-exists-upstream-v3.10-rc2
removed: kernel-exists-upstream-v3.10-rc2
Revision history for this message
penalvch (penalvch) wrote :

northar, thank you for testing the newest mainline kernel. The next step is to commit bisect Ubuntu kernel versions between Precise and Quantal, Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Josef Andersson (northar) wrote :

I started doing bisect, but the commit that does this bug is already found, see https://bugzilla.redhat.com/show_bug.cgi?id=845745
and the commit is
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=2099810f903caa1920f3ef6014fb7f36e4786490 "pci bus mastering"

How to report that to upstreams?

penalvch (penalvch)
tags: added: needs-upstream-testing
removed: kernel-bug-exists-upstream
Revision history for this message
Josef Andersson (northar) wrote :

From bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1029790 "

This is finally fixed in the upstream 3.10 kernel by commit e49f3959a96dc279860af7e86e6dbcfda50580a5 and in the 3.9.6 kernel by commit e335ccae2ae4caef26a1e81711c44aec1cc83bd2

Those commits even mention the same redhat bug number as quoted in comment #61 of this bug.

The Ubuntu 13.10 "Saucy Salamander" kernel is now based on the upstream 3.9.6 kernel.
"

And daily works on my hp6910p again.

Revision history for this message
Id2ndR (id2ndr) wrote :

current saucy daily works for me with HP nc6400.

Revision history for this message
penalvch (penalvch) wrote :

northar, did you need a backport to a release prior to Saucy, or may we close this as Status Invalid?

Revision history for this message
Josef Andersson (northar) wrote :

12,10 and 13.04 are meant to be exprimental releases right? So now that it works in Saucy daily again, it's fine. Close it.

Revision history for this message
penalvch (penalvch) wrote :

northar, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180557/comments/8 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.