[sandybridge] GPU lockups and other crashes

Bug #733321 reported by Benjamin Drung
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
plymouth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The stock kernel produces many GPU lockups. As recommended in #ubuntu-x, I tried the kernel from drm-next and drm-intel-next. Both kernel crashes with different crash log. Both crash logs will be attached to this bug.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-6-generic 2.6.38-6.34
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: skipper 2158 F.... pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'Audigy2'/'SB Audigy 4 [SB0610] (rev.0, serial:0x10211102) at 0xd000, irq 16'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 202
   Simple ctrls : 37
Date: Fri Mar 11 16:25:28 2011
HibernationDevice: RESUME=UUID=34cac010-fdc1-4e0b-823e-6d5e833bfc17
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 virbr0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic root=UUID=782d30b2-7975-4d00-bf3e-de316d2b96f6 ro quiet splash drm_kms_helper.poll=0 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-6-generic N/A
 linux-backports-modules-2.6.38-6-generic N/A
 linux-firmware 1.48
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2011-03-11 (0 days ago)
dmi.bios.date: 02/11/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0806
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd02/11/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Benjamin Drung (bdrung) wrote :
Revision history for this message
Benjamin Drung (bdrung) wrote :

Here's the crash log from drm-next.

Revision history for this message
Benjamin Drung (bdrung) wrote :

Here's the crash log from drm-intel-next.

Revision history for this message
Bryce Harrington (bryce) wrote :

<Sarvatt> bdrung: go figure you have the screwed up board mentioned here too http://www.phoronix.com/scan.php?page=article&item=intel_sandy_speed&num=1 :(
<Sarvatt> just booting was screwed up for them, i'm trying to find any discussion on what the actual problems were
<bdrung> Sarvatt: my system runs fine with the drm-intel-next kernel (after only one plymouth related boot crash -> bug #733321)
<Sarvatt> bdrung: even without drm_kms_helper.poll=0 ?
<bdrung> Sarvatt: not tested yet
<Sarvatt> it looks like 2.6.38-rc8 should work if drm-intel-next works

Revision history for this message
Benjamin Drung (bdrung) wrote :

I ran "phoronix-test-suite benchmark build-linux-kernel" with drm_kms_helper.poll=0 and without drm_kms_helper.poll=0 using the drm-intel-next kernel (2.6.38-997.201103081433) and it didn't crashed. This command should trigger a crash according to Phoronix.

Revision history for this message
Bryce Harrington (bryce) wrote :

bdrung, can you confirm that the 2.6.38-rc8 kernel (or newer) doesn't lockup or crash?

I.e., can we close this bug once that kernel gets in?

Revision history for this message
Benjamin Drung (bdrung) wrote :

We can close this bug. The 2.6.38-7 kernel (based on 2.6.38 final) does not show these crashes. It hangs sometimes, but in a different way. I will open a new bug report for it once I can get a crash dump for it.

Changed in linux (Ubuntu):
status: New → Fix Released
Changed in plymouth (Ubuntu):
status: New → Invalid
To post a comment you must log in.