Launchpad has imported 14 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=39947.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-08-09T02:11:45+00:00 Bryce Harrington wrote: For several releases now we've been seeing "fake" GPU lockups flagged by the Intel driver. The user's system (typically) does not lock up, but it is enough to trigger the apport crash handler, which displays a "GPU lockup" dialog to the user and prompts them to file a bug report. The main problem is that this makes it hard to distinguish and prioritize 'real' gpu lockups from these fake ones. I'd like to either figure out what is causing the fake gpu lockups and solve it, or identify a good reliable way of detecting that it's a fake gpu lockup and fix our crash detector to ignore them. Below is an example of one of these types of bugs, forwarded from: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/815798 ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: xserver-xorg-video-intel 2:2.15.0-3ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7 Uname: Linux 3.0.0-6-generic i686 Architecture: i386 BootLog: fsck from util-linux 2.19.1 fsck from util-linux 2.19.1 /dev/sda2: clean, 324507/655360 files, 1668623/2621184 blocks Linux_Home: clean, 79489/6545408 files, 12735361/26159616 blocks Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Chipset: i915gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Mon Jul 25 01:19:49 2011 DistUpgraded: Log time: 2011-07-22 00:26:16.817036 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: virtualbox, 4.0.10, 3.0.0-6-generic, i686: installed DuplicateSignature: [i915gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100 render.IPEHR: 0x02000004 Ubuntu 11.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Uniwill Computer Corp Device [1584:9800] Subsystem: Uniwill Computer Corp Device [1584:9800] InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) InterpreterPath: /usr/bin/python2.7 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ALIENWARE 255/259 Series PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-6-generic root=UUID=2a79b732-f48c-4ead-ac45-09b92b7ffee7 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+7ubuntu6 libdrm2 2.4.26-1ubuntu1 xserver-xorg-video-intel 2:2.15.0-3ubuntu2 SourcePackage: xserver-xorg-video-intel Title: [i915gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100 render.IPEHR: 0x02000004 UpgradeStatus: Upgraded to oneiric on 2011-07-22 (3 days ago) UserGroups: dmi.bios.date: 04/21/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.03W dmi.board.name: 255/259 Series dmi.board.vendor: ALIENWARE dmi.chassis.type: 10 dmi.chassis.vendor: American Megatrends Inc dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.03W:bd04/21/2006:svnALIENWARE:pn255/259Series:pvr:rvnALIENWARE:rn255/259Series:rvr:cvnAmericanMegatrendsInc:ct10:cvr: dmi.product.name: 255/259 Series dmi.sys.vendor: ALIENWARE version.compiz: compiz 1:0.9.5.0-0ubuntu1 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11~1-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11~1-0ubuntu4 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.2-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0-3ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/0 ------------------------------------------------------------------------ On 2011-08-09T02:13:25+00:00 Bryce Harrington wrote: Created attachment 50048 BootDmesg.txt Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/1 ------------------------------------------------------------------------ On 2011-08-09T02:13:44+00:00 Bryce Harrington wrote: Created attachment 50049 CurrentDmesg.txt Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/2 ------------------------------------------------------------------------ On 2011-08-09T02:14:00+00:00 Bryce Harrington wrote: Created attachment 50050 XorgLog.txt Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/3 ------------------------------------------------------------------------ On 2011-08-09T02:14:23+00:00 Bryce Harrington wrote: Created attachment 50051 i915_error_state.txt Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/4 ------------------------------------------------------------------------ On 2011-08-09T08:30:43+00:00 Chris Wilson wrote: They are still bugs, in some ways much more frightening than performing an undefined operation - the chip has detected that we are accessing invalid memory. Who knows what illegal accesses we did before the invalid access! The trick to determine if the GPU is truly wedged would be to cat /sys/kernel/debug/dri/0/i915_wedged (or you can try issuing a throttle command and look for an EIO error code). Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/5 ------------------------------------------------------------------------ On 2011-08-18T21:19:17+00:00 Bryce Harrington wrote: >From what I've seen, most of the false gpu hang reports have a hang which occurs late during boot, basically right at the point that the drm driver is loaded. Could the issue be that some memory is not being initialized, or a race condition in initialization? Do you have an idea if this problem is unique to Ubuntu? I'm wondering if it boils down to some boot optimization we did ourselves, or if it is a legitimate bug in the driver? Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/13 ------------------------------------------------------------------------ On 2011-08-22T19:12:12+00:00 Eugeni Dodonov wrote: (In reply to comment #6) > Do you have an idea if this problem is unique to Ubuntu? I'm wondering if it > boils down to some boot optimization we did ourselves, or if it is a > legitimate > bug in the driver? Don't know if it will help, but I haven't seen such issues in Mandriva/Mageia while maintaining their mesa/X/init stacks. At the same time, we have seen similar issues when booting Ubuntu on same hardware for reference. Don't know if it is a coincidence (as compile flags, versions and so on do not match always), but Ubuntu was the only one to show this. But I admit that I could be wrong, and I certainly haven't tested it in-depth. Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/14 ------------------------------------------------------------------------ On 2011-09-22T23:30:50+00:00 Eugeni Dodonov wrote: I lowered the priority a bit to have it in the same priority scale as other false GPU lockups. Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/23 ------------------------------------------------------------------------ On 2012-04-16T12:30:16+00:00 Chris Wilson wrote: So Display B is unbound but enabled... Big time modesetting screwup. Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/26 ------------------------------------------------------------------------ On 2012-04-16T21:37:48+00:00 Jesse Barnes wrote: Shouldn't the sanitize function have disabled the planes?? If so this should be fixed right? Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/27 ------------------------------------------------------------------------ On 2012-04-17T00:27:22+00:00 Bryce Harrington wrote: Well, we're still seeing false lockups, although not exactly the same set of error codes as this bug. [i915gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000010 render.IPEHR: 0x01000000 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/981171 [IGDgm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00010000 render.IPEHR: 0x01000000 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/978968 (+4 dupes) [i965gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/982021 [gm45] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00100000 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/981297 The latter two sound like actual misbehaviors happened. Would you prefer I file new upstream reports on each of these, or do they seem like the same issue? Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/28 ------------------------------------------------------------------------ On 2012-04-17T00:30:55+00:00 Bryce Harrington wrote: Btw, for comparison, there were 142 bugs collected last cycle as dupes of this: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/828684 Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/29 ------------------------------------------------------------------------ On 2012-04-17T08:08:10+00:00 Chris Wilson wrote: My old favourite: diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_d index e0e8cb5..7978e41 100644 --- a/drivers/gpu/drm/i915/intel_display.c +++ b/drivers/gpu/drm/i915/intel_display.c @@ -5846,7 +5846,6 @@ static int i9xx_crtc_mode_set(struct drm_crtc *crtc, I915_WRITE(DSPCNTR(plane), dspcntr); POSTING_READ(DSPCNTR(plane)); - intel_enable_plane(dev_priv, plane, pipe); ret = intel_pipe_set_base(crtc, x, y, old_fb); Reply at: https://bugs.launchpad.net/xorg-server/+bug/828684/comments/30 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/828684 Title: [i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/828684/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
