Graphical bug and frise (only CTRL ALT F1 work) the PC is a UX32VD on debian testing (i dont use the nvidia card only the intel) my dmesg [ 456.185124] [drm] stuck on render ring [ 456.185131] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 456.185133] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 456.185136] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 456.185137] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 456.185138] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 456.188002] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xfc10000 ctx 1) at 0xfc10e5c [ 723.424413] [drm] stuck on render ring [ 729.405500] [drm] stuck on render ring [ 735.434626] [drm] stuck on render ring [ 741.451743] [drm] stuck on render ring [ 747.456856] [drm] stuck on render ring [ 753.425928] [drm] stuck on render ring [ 759.467066] [drm] stuck on render ring [ 765.472170] [drm] stuck on render ring [ 774.455810] [drm] stuck on render ring [ 782.486643] [drm] stuck on render ring [ 788.491750] [drm] stuck on render ring [ 794.472840] [drm] stuck on render ring [ 800.477944] [drm] stuck on render ring [ 834.506885] [drm] stuck on render ring [ 840.499988] [drm] stuck on render ring [ 840.500039] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x1caa000 ctx 1) at 0x1caa214 [ 846.541122] [drm] stuck on render ring [ 852.510204] [drm] stuck on render ring [ 858.539327] [drm] stuck on render ring [ 867.558997] [drm] stuck on render ring
Created attachment 96805 [details] a print screen of the bug I add a printscreen of the bug but the dmesg dont have same error this time he say only [ 4.764366] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \SMB0 1 (20131115/utaddress-251) [ 4.764377] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 2 (20131115/utaddress-251) [ 4.764383] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 4.764459] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPIS 1 (20131115/utaddress-251) [ 4.764465] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 2 (20131115/utaddress-251) [ 4.764469] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 4.764473] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251) [ 4.764476] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GP01 2 (20131115/utaddress-251) [ 4.764480] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 4.764481] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251) [ 4.764484] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GP01 2 (20131115/utaddress-251) [ 4.764487] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 4.764488] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 4.777394] iTCO_vendor_support: vendor-support=0 [ 4.778885] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10 [ 4.778923] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460) [ 4.779045] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 5.041286] Adding 3919868k swap on /dev/sdb2. Priority:-1 extents:1 across:3919868k SS [ 5.054040] EXT4-fs (sdb1): re-mounted. Opts: (null) [ 5.133183] EXT4-fs (sdb1): re-mounted. Opts: discard,errors=remount-ro [ 5.294531] lp: driver loaded but no devices found [ 5.299381] ppdev: user-space parallel port driver [ 5.310758] fuse init (API version 7.22) [ 5.316936] loop: module loaded [ 5.326381] i2c /dev entries driver [ 5.375493] FAT-fs (sdb3): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 5.387276] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: discard [ 5.643318] RPC: Registered named UNIX socket transport module. [ 5.643321] RPC: Registered udp transport module. [ 5.643322] RPC: Registered tcp transport module. [ 5.643323] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 5.646474] FS-Cache: Loaded [ 5.653474] FS-Cache: Netfs 'nfs' registered for caching [ 5.662377] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 5.992962] tun: Universal TUN/TAP device driver, 1.6 [ 5.992965] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [ 6.057362] vboxdrv: Found 4 processor cores. [ 6.057560] vboxdrv: fAsync=0 offMin=0x171 offMax=0xdfe [ 6.057616] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 6.057618] vboxdrv: Successfully loaded version 4.3.6_Debian (interface 0x001a0007). [ 6.096022] vboxpci: IOMMU not found (not registered) [ 6.973902] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input22 [ 8.334883] Bluetooth: RFCOMM TTY layer initialized [ 8.334893] Bluetooth: RFCOMM socket layer initialized [ 8.334897] Bluetooth: RFCOMM ver 1.11 [ 8.349081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 8.349084] Bluetooth: BNEP filters: protocol multicast [ 8.349091] Bluetooth: BNEP socket layer initialized [ 8.631389] /dev/vmmon[4006]: Module vmmon: registered with major=10 minor=165 [ 8.631393] /dev/vmmon[4006]: Module vmmon: initialized [ 8.911743] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S [ 8.918292] iwlwifi 0000:03:00.0: Radio type=0x2-0x1-0x0 [ 9.189990] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S [ 9.196560] iwlwifi 0000:03:00.0: Radio type=0x2-0x1-0x0 [ 9.286525] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 13.988218] bbswitch: version 0.8 [ 13.988225] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0 [ 13.988230] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP [ 13.988238] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) [ 13.988330] bbswitch: detected an Optimus _DSM function [ 13.988382] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on [ 13.992204] bbswitch: disabling discrete graphics [ 13.992216] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) [ 14.534584] /dev/vmmon[5157]: Module vmmon: unloaded [ 17.523736] vmis-launcher[5808]: segfault at 7fb70b25bad4 ip 00007fb70f092386 sp 00007fff2a9eebf8 error 4 in libc-2.18.so[7fb70ef6d000+1a0000] [ 17.676147] vmis-launcher[5828]: segfault at 7fe4d911bad4 ip 00007fe4dcf52386 sp 00007ffff2ee7178 error 4 in libc-2.18.so[7fe4dce2d000+1a0000]
Could you provide /sys/class/drm/card0/error ? As this looks like an IVB machines chances are that it's the same as Bug 76808. As Chris suggested there the following commit could improve the situation: commit f66fab8e1cd6b3127ba4c5c0d11539fbe1de1e36 Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Tue Feb 11 19:52:06 2014 +0200 drm/i915: Prevent MI_DISPLAY_FLIP straddling two cachelines on IVB This is already in the -nightly kernel, so could you get a copy and give it a try?: git://anongit.freedesktop.org/drm-intel drm-intel-nightly branch.
The render corruption looks like a mesa-10.1 bug.
sorry for no reply faster but no bug this day i don't have update but for around the bug i have configured bumblebee but finali i don't use and no bug hasard? if i have new bug i get the /sys/class/drm/card0/error
Ok, tentatively closing then, please reopen when it shows up again.
Hi, I just had the exact same problem. Actually twice in a row it seems. The second one the pc recovered. It took some time to accept CTRL-ALT-F1, after log in, top shows some activity, and finally I could CTRL-ALT-F7 back to the GUI. dmesg shows: [ 1475.042636] [drm] stuck on render ring [ 1475.042639] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 1475.042639] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 1475.042639] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 1475.042639] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 1475.042640] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. I have the error file, I'll try to attach it. Btw, this is on a DELL Latitude E5430, running Ubuntu 14.04 Trusty Tahr (AMD64), with unity 3D. Recently I installed latest XBMC 13.0 Gotham (don't know if that's related, but there is v-sync tear regression that appears in XBMC 13 - but I don't have the TearFree option in xorg.conf afaics). $ inxi -Gx Graphics: Card: Intel 3rd Gen Core processor Graphics Controller bus-ID: 00:02.0 X.Org: 1.15.1 driver: intel Resolution: 1600x900@60.0hz, 1600x1200@60.0hz GLX Renderer: Mesa DRI Intel Ivybridge Mobile GLX Version: 3.0 Mesa 10.1.0 Direct Rendering: Yes $ lspci -v 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 053c Flags: bus master, fast devsel, latency 0, IRQ 44 Memory at f6400000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915
Created attachment 98465 [details] The /sys/class/drm/card0/error as requested in dmesg
Last comment to say that I don't have the graphics corruption. Just global freeze, only mouse pointer moving. Btw, I also had Virtualbox running in the background (nothing else, this happened almost immediately after boot - which was due to previous freeze).
(In reply to comment #6) > Hi, > > I just had the exact same problem. Actually twice in a row it seems. > The second one the pc recovered. It took some time to accept CTRL-ALT-F1, > after log in, top shows some activity, and finally I could CTRL-ALT-F7 back > to the GUI. Nope. You did not. You had bug 77104.
Ah, ok, sorry. I don't see the difference I must admit. Should I join the crash dump to that ticket instead?
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.