Re: drm: i915 hangcheck/GPU errors

2012-03-06 Thread Eugeni Dodonov 
On Tue, Mar 6, 2012 at 10:47, Randy Dunlap  wrote:

> Hi,
>
> My Toshiba Portege (Intel Core i5) hangs every few days.
> Sometimes I can see no log messages/reasons for it.
> Sometimes there are messages about X receiving potentially
> fatal signals.
>
> Today's hang appears to have some useful info (maybe).
>
> Mar  6 09:01:45 dragon kernel: [137308.704424]
> [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> Mar  6 09:01:45 dragon kernel: [137308.704552] [drm] capturing error
> event; look for more information in /debug/dri/0/i915_error_state
> Mar  6 09:01:45 dragon kernel: [137308.718950] [drm:i915_wait_request]
> *ERROR* i915_wait_request returns -11 (awaiting 16513584 at 16513581, next
> 16513585)
> Mar  6 09:02:13 dragon kernel: [137336.754647]
> [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> Mar  6 09:02:13 dragon kernel: [137336.754698] [drm:i915_wait_request]
> *ERROR* i915_wait_request returns -11 (awaiting 16517081 at 16517078, next
> 16517082)
>

This error state file is in debugfs, usually in /sys/kernel/debug/dri/0/
directory.

Could you please report it into our bugzilla, attaching the files and
information mentioned at
http://intellinuxgraphics.org/how_to_report_bug.html please?

-- 
Eugeni Dodonov

___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

drm: i915 hangcheck/GPU errors

2012-03-06 Thread Eugeni Dodonov 
On Tue, Mar 6, 2012 at 10:47, Randy Dunlap  wrote:

> Hi,
>
> My Toshiba Portege (Intel Core i5) hangs every few days.
> Sometimes I can see no log messages/reasons for it.
> Sometimes there are messages about X receiving potentially
> fatal signals.
>
> Today's hang appears to have some useful info (maybe).
>
> Mar  6 09:01:45 dragon kernel: [137308.704424]
> [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> Mar  6 09:01:45 dragon kernel: [137308.704552] [drm] capturing error
> event; look for more information in /debug/dri/0/i915_error_state
> Mar  6 09:01:45 dragon kernel: [137308.718950] [drm:i915_wait_request]
> *ERROR* i915_wait_request returns -11 (awaiting 16513584 at 16513581, next
> 16513585)
> Mar  6 09:02:13 dragon kernel: [137336.754647]
> [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> Mar  6 09:02:13 dragon kernel: [137336.754698] [drm:i915_wait_request]
> *ERROR* i915_wait_request returns -11 (awaiting 16517081 at 16517078, next
> 16517082)
>

This error state file is in debugfs, usually in /sys/kernel/debug/dri/0/
directory.

Could you please report it into our bugzilla, attaching the files and
information mentioned at
http://intellinuxgraphics.org/how_to_report_bug.html please?

-- 
Eugeni Dodonov

-- next part --
An HTML attachment was scrubbed...
URL:

drm: i915 hangcheck/GPU errors

2012-03-06 Thread Randy Dunlap 
Hi,

My Toshiba Portege (Intel Core i5) hangs every few days.
Sometimes I can see no log messages/reasons for it.
Sometimes there are messages about X receiving potentially
fatal signals.

Today's hang appears to have some useful info (maybe).

Mar  6 09:01:45 dragon kernel: [137308.704424] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
Mar  6 09:01:45 dragon kernel: [137308.704552] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
Mar  6 09:01:45 dragon kernel: [137308.718950] [drm:i915_wait_request] *ERROR* 
i915_wait_request returns -11 (awaiting 16513584 at 16513581, next 16513585)
Mar  6 09:02:13 dragon kernel: [137336.754647] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
Mar  6 09:02:13 dragon kernel: [137336.754698] [drm:i915_wait_request] *ERROR* 
i915_wait_request returns -11 (awaiting 16517081 at 16517078, next 16517082)

...

Mar  6 09:05:44 dragon kernel: [137548.071904] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
Mar  6 09:05:44 dragon kernel: [137548.071951] [drm:i915_wait_request] *ERROR* 
i915_wait_request returns -11 (awaiting 16550939 at 16550936, next 16550940)
Mar  6 09:05:57 dragon kernel: [137560.924459] X/1399: potentially unexpected 
fatal signal 6.
Mar  6 09:05:57 dragon kernel: [137560.924463] 
Mar  6 09:05:57 dragon kernel: [137560.924466] CPU 1 
Mar  6 09:05:57 dragon kernel: [137560.924468] Modules linked in: usblp 
snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq 
snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 af_packet acpi_cpufreq mperf lp 
ppdev parport_pc parport snd_hda_codec_hdmi snd_hda_codec_realtek uvcvideo 
videobuf2_core videobuf2_vmalloc videobuf2_memops usbhid hid mousedev 
snd_hda_codec arc4 snd_hwdep iwlwifi toshiba_acpi psmouse snd_pcm snd_timer 
sparse_keymap ehci_hcd battery serio_raw mac80211 evdev thermal ac xhci_hcd 
snd_page_alloc wmi power_supply e1000e mei(C) sdhci_pci sdhci mmc_core 
firmware_class cfg80211 rfkill processor sg rtc_cmos loop unix [last unloaded: 
snd_hda_intel]
Mar  6 09:05:57 dragon kernel: [137560.924560] 
Mar  6 09:05:58 dragon kernel: [137560.924564] Pid: 1399, comm: X Tainted: G
 C   3.3.0-rc5 #2 TOSHIBA PORTEGE R835/Portable PC
Mar  6 09:05:58 dragon kernel: [137560.924572] RIP: 0033:[<7f57463c7035>]  
[<7f57463c7035>] 0x7f57463c7034
Mar  6 09:05:58 dragon kernel: [137560.924581] RSP: 002b:7fff0ac33758  
EFLAGS: 3206
Mar  6 09:05:58 dragon kernel: [137560.924585] RAX:  RBX: 
 RCX: 
Mar  6 09:05:58 dragon kernel: [137560.924589] RDX: 0006 RSI: 
0577 RDI: 0577
Mar  6 09:05:58 dragon kernel: [137560.924593] RBP: 7fff0ac341a0 R08: 
7f57464ee8e0 R09: 00411e40
Mar  6 09:05:59 dragon kernel: [137560.924597] R10: 0008 R11: 
3206 R12: 0037
Mar  6 09:06:00 dragon kernel: [137560.924600] R13: 7fff0ac33a80 R14: 
004f R15: 0007
Mar  6 09:06:00 dragon kernel: [137560.924604] FS:  7f57487a18a0() 
GS:88014a60() knlGS:
Mar  6 09:06:02 dragon kernel: [137560.924609] CS:  0010 DS:  ES:  CR0: 
80050033
Mar  6 09:06:02 dragon kernel: [137560.924612] CR2: 00418ff0 CR3: 
00013d059000 CR4: 000406e0
Mar  6 09:06:02 dragon kernel: [137560.924616] DR0:  DR1: 
 DR2: 
Mar  6 09:06:02 dragon kernel: [137560.924620] DR3:  DR6: 
0ff0 DR7: 0400
Mar  6 09:06:03 dragon kernel: [137560.924624] Process X (pid: 1399, threadinfo 
88013e9cc000, task 88012412)
Mar  6 09:06:03 dragon kernel: [137560.924627] 
Mar  6 09:06:03 dragon kernel: [137560.924630] Call Trace:




Any ideas/suggestions?



"look for more information in /debug/dri/0/i915_error_state"

Where is that file?  in debugfs or somewhere else?

thanks,
-- 
~Randy
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

drm: i915 hangcheck/GPU errors

2012-03-06 Thread Randy Dunlap 
Hi,

My Toshiba Portege (Intel Core i5) hangs every few days.
Sometimes I can see no log messages/reasons for it.
Sometimes there are messages about X receiving potentially
fatal signals.

Today's hang appears to have some useful info (maybe).

Mar  6 09:01:45 dragon kernel: [137308.704424] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
Mar  6 09:01:45 dragon kernel: [137308.704552] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
Mar  6 09:01:45 dragon kernel: [137308.718950] [drm:i915_wait_request] *ERROR* 
i915_wait_request returns -11 (awaiting 16513584 at 16513581, next 16513585)
Mar  6 09:02:13 dragon kernel: [137336.754647] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
Mar  6 09:02:13 dragon kernel: [137336.754698] [drm:i915_wait_request] *ERROR* 
i915_wait_request returns -11 (awaiting 16517081 at 16517078, next 16517082)

...

Mar  6 09:05:44 dragon kernel: [137548.071904] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
Mar  6 09:05:44 dragon kernel: [137548.071951] [drm:i915_wait_request] *ERROR* 
i915_wait_request returns -11 (awaiting 16550939 at 16550936, next 16550940)
Mar  6 09:05:57 dragon kernel: [137560.924459] X/1399: potentially unexpected 
fatal signal 6.
Mar  6 09:05:57 dragon kernel: [137560.924463] 
Mar  6 09:05:57 dragon kernel: [137560.924466] CPU 1 
Mar  6 09:05:57 dragon kernel: [137560.924468] Modules linked in: usblp 
snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq 
snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 af_packet acpi_cpufreq mperf lp 
ppdev parport_pc parport snd_hda_codec_hdmi snd_hda_codec_realtek uvcvideo 
videobuf2_core videobuf2_vmalloc videobuf2_memops usbhid hid mousedev 
snd_hda_codec arc4 snd_hwdep iwlwifi toshiba_acpi psmouse snd_pcm snd_timer 
sparse_keymap ehci_hcd battery serio_raw mac80211 evdev thermal ac xhci_hcd 
snd_page_alloc wmi power_supply e1000e mei(C) sdhci_pci sdhci mmc_core 
firmware_class cfg80211 rfkill processor sg rtc_cmos loop unix [last unloaded: 
snd_hda_intel]
Mar  6 09:05:57 dragon kernel: [137560.924560] 
Mar  6 09:05:58 dragon kernel: [137560.924564] Pid: 1399, comm: X Tainted: G
 C   3.3.0-rc5 #2 TOSHIBA PORTEGE R835/Portable PC
Mar  6 09:05:58 dragon kernel: [137560.924572] RIP: 0033:[<7f57463c7035>]  
[<7f57463c7035>] 0x7f57463c7034
Mar  6 09:05:58 dragon kernel: [137560.924581] RSP: 002b:7fff0ac33758  
EFLAGS: 3206
Mar  6 09:05:58 dragon kernel: [137560.924585] RAX:  RBX: 
 RCX: 
Mar  6 09:05:58 dragon kernel: [137560.924589] RDX: 0006 RSI: 
0577 RDI: 0577
Mar  6 09:05:58 dragon kernel: [137560.924593] RBP: 7fff0ac341a0 R08: 
7f57464ee8e0 R09: 00411e40
Mar  6 09:05:59 dragon kernel: [137560.924597] R10: 0008 R11: 
3206 R12: 0037
Mar  6 09:06:00 dragon kernel: [137560.924600] R13: 7fff0ac33a80 R14: 
004f R15: 0007
Mar  6 09:06:00 dragon kernel: [137560.924604] FS:  7f57487a18a0() 
GS:88014a60() knlGS:
Mar  6 09:06:02 dragon kernel: [137560.924609] CS:  0010 DS:  ES:  CR0: 
80050033
Mar  6 09:06:02 dragon kernel: [137560.924612] CR2: 00418ff0 CR3: 
00013d059000 CR4: 000406e0
Mar  6 09:06:02 dragon kernel: [137560.924616] DR0:  DR1: 
 DR2: 
Mar  6 09:06:02 dragon kernel: [137560.924620] DR3:  DR6: 
0ff0 DR7: 0400
Mar  6 09:06:03 dragon kernel: [137560.924624] Process X (pid: 1399, threadinfo 
88013e9cc000, task 88012412)
Mar  6 09:06:03 dragon kernel: [137560.924627] 
Mar  6 09:06:03 dragon kernel: [137560.924630] Call Trace:




Any ideas/suggestions?



"look for more information in /debug/dri/0/i915_error_state"

Where is that file?  in debugfs or somewhere else?

thanks,
-- 
~Randy