1002:7188 system hangs on boot (at loading radeon related modules)

[Piotr Kęplicz]

After an upgrade to Ubuntu 12.10 (kernel 3.5), the system fails to boot. When starting without "quiet splash" options, the last kernel messages relate to loading and initializing radeon and drm modules.

Same problems are here when trying to boot 12.10 live usb images, both 32- and 64-bit.

I'm currently using 3.2 kernel from Precise, which boots fine.

According to RH bug report comment, the problem was introduced with an upstream merge commit:
f9369910a6225b8d4892c3f20ae740a711cd5ace
Ubuntu kernel 3.4.0-5.11 boots fine, 3.5.0-1.1 freezes.

WORKAROUND: When using the following kernel boot parameter the system boots but doesn't switch to the native resolution of 1280x800, and leaves it as 1024x768:
nomodeset

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic i686
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: keplicz 4275 F.... pulseaudio
Date: Wed Oct 24 12:34:20 2012
HibernationDevice: RESUME=UUID=3a2133a7-9acb-4a14-a4f8-2dd1a8b1e412
MachineType: Hewlett-Packard HP Compaq 6910p
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=b1aade02-95c2-4d36-8878-027b70c9ec46 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-32-generic N/A
 linux-backports-modules-3.2.0-32-generic N/A
 linux-firmware 1.95
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2012-10-21 (2 days ago)
dmi.bios.date: 09/13/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MCD Ver. F.0A
dmi.board.name: 30C1
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 68.32
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68MCDVer.F.0A:bd09/13/2007:svnHewlett-Packard:pnHPCompaq6910p:pvrF.0A:rvnHewlett-Packard:rn30C1:rvrKBCVersion68.32:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6910p
dmi.product.version: F.0A
dmi.sys.vendor: Hewlett-Packard

[Piotr Kęplicz (keplicz)]

Here's a fragment from the 3.2 dmesg attached above:

[ 1.438472] [drm] Initialized drm 1.1.0 20060810
[ 1.442289] wmi: Mapper loaded
[ 1.482126] [drm] radeon defaulting to kernel modesetting.
[ 1.482130] [drm] radeon kernel modesetting enabled.
[ 1.482208] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.482216] radeon 0000:01:00.0: setting latency timer to 64
[ 1.490401] [drm] initializing kernel modesetting (RV515 0x1002:0x7188 0x103C:0x30C1).
[ 1.490430] [drm] register mmio base: 0xD8400000
[ 1.490433] [drm] register mmio size: 65536
[ 1.490597] ATOM BIOS: M64S
[ 1.490618] [drm] Generation 2 PCI interface, using max accessible memory
[ 1.490624] radeon 0000:01:00.0: VRAM: 128M 0x0000000000000000 - 0x0000000007FFFFFF (128M used)
[ 1.490627] radeon 0000:01:00.0: GTT: 512M 0x0000000008000000 - 0x0000000027FFFFFF
[ 1.490645] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 1.490647] [drm] Driver supports precise vblank timestamp query.

The 3.5 stops right here.
Below is the rest of the 3.2 dmesg:

[ 1.490660] [drm] radeon: irq initialized.
[ 1.494930] [drm] Detected VRAM RAM=128M, BAR=64M
[ 1.494933] [drm] RAM width 64bits DDR
[ 1.497241] [TTM] Zone kernel: Available graphics memory: 437004 kiB.
[ 1.497244] [TTM] Zone highmem: Available graphics memory: 1030768 kiB.
[ 1.497246] [TTM] Initializing pool allocator.
[ 1.497274] [drm] radeon: 128M of VRAM memory ready
[ 1.497277] [drm] radeon: 512M of GTT memory ready.
[ 1.497296] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 1.498935] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[ 1.500145] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 1.500237] radeon 0000:01:00.0: WB enabled
[ 1.500292] [drm] Loading R500 Microcode

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and 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 in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc2-raring/

[Piotr Kęplicz (keplicz)]

I did the test with the mainline kernel and it failed too.

There's a similar report in the RedHat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=845745
- boot freezes with Fedora's 3.5 kernel, also reported on the same hardware as here (HP Compaq 6910p Mobility Radeon X2300).
Apparently this bug can affect other graphics drivers as well.

[penalvch (penalvch)]

Piotr Kęplicz, thank you for testing the mainline kernel. The next step is to perform a Ubuntu kernel bisect from 3.2 to 3.5.0-17.28, in order to identify the last good Ubuntu kernel version, and first bad one. As per https://launchpad.net/ubuntu/quantal/+source/linux we have:
    3.2.0-23.36
    3.2.0-24.37
    3.4.0-1.1
    3.4.0-1.2
    3.4.0-1.3
    3.4.0-2.4
    3.4.0-2.5
    3.4.0-2.6
    3.4.0-3.7
    3.4.0-3.8
    3.4.0-4.9
    3.4.0-4.10
    3.4.0-5.11
    3.5.0-1.1
    3.5.0-2.2
    3.5.0-3.3
    3.5.0-4.4
    3.5.0-5.5
    3.5.0-6.6
    3.5.0-7.7
    3.5.0-8.8
    3.5.0-9.9
    3.5.0-10.10
    3.5.0-11.11
    3.5.0-12.12
    3.5.0-13.13
    3.5.0-13.14
    3.5.0-14.15
    3.5.0-14.16
    3.5.0-14.17
    3.5.0-14.18
    3.5.0-14.19
    3.5.0-15.20
    3.5.0-15.21
    3.5.0-15.22
    3.5.0-15.23
    3.5.0-16.24
    3.5.0-16.25
    3.5.0-17.26
    3.5.0-17.27
    3.5.0-17.28

Hence, could you please test 3.5.0-8.8 via https://launchpad.net/ubuntu/+source/linux/3.5.0-8.8/+build/3702773 ?

For more on bisecting, please see https://wiki.ubuntu.com/Kernel/KernelBisection .

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Piotr Kęplicz (keplicz)]

According to RH bug report comment, the problem was introduced with an upstream merge commit f9369910a6225b8d4892c3f20ae740a711cd5ace (before 3.5.0-rc1 release).
Indeed: 3.4.0-5.11 boots fine, 3.5.0-1.1 (upstream 3.5.0-rc3) freezes.

[penalvch (penalvch)]

Piotr Kęplicz, thank you for performing the Ubuntu kernel bisect. The next step is to perform a Ubuntu kernel commit bisect from 3.4.0-5.11 to 3.5.0-1.1, in order to identify the last good Ubuntu kernel commit, immediately followed by the first bad one. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[OldJoe (oldwisejoe)]

have the same bug. hp6910p, radeon x2300, Intel® Core™2 Duo CPU T7500 @ 2.20GHz × 2. Have a succesfull boot on 3.2.0-29-generic, but next kernel releases has fail boot.

[penalvch (penalvch)]

OldJoe, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Piotr Kęplicz (keplicz)]

I think OldJoe's experiencing this particular bug - it's the same laptop (HP Compaq 6910p) but with a faster CPU.

[Fibonacci (fibonacci-prower)]

I'm trying to do the kernel commit bisect, since I'm also experiencing this particular bug.
However, I could find no kernel older than 3.5 on git://kernel.ubuntu.com/ubuntu/ubuntu-quantal.git, and no kernel newer than 3.2 on git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git.
Perhaps I'm doing something wrong. How can I then perform the bisect?

[Josef Andersson (northar)]

I suffer from the same bug, and reported it here. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1029790
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?

[Josef Andersson (northar)]

Bug is fixed upstream, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1029790 and comment "

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 as it should on my hp6910p again, it haven't worked without nomodeset since 12.04. Cheers!

[Piotr Kęplicz (keplicz)]

Apparently "proposed" kernel updates for quantal (3.5.0-37.58) and raring (3.8.0-28.41) both carry the necessary patch: "radeon: Fix system hang issue when using KMS with older cards". Indeed, the updated kernel for raring works fine :-)

[Julian Wiedmann (jwiedmann)]

The patch actually landed in raring-updates with 3.8.0-27.40. Thanks for testing!