mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: regression(?) 3.3-rc4 -> 3.3-rc5: drm intel hangs
Date: Tue, 28 Feb 2012 09:14:09 +0100	[thread overview]
Message-ID: <1330416849.3899.11.camel@mattotaupa> (raw)
In-Reply-To: <20120228040327.GA9973@gamma.logic.tuwien.ac.at>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

Dear Norbert,


Am Dienstag, den 28.02.2012, 13:03 +0900 schrieb Norbert Preining:
> Dear all,
> 
> (please Cc)
> 
> since upgrade to 3.3-rc5 I see the following behaviour repeatedly:
> 
> Feb 28 11:42:47 mithrandir kernel: [15627.756071] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> Feb 28 11:42:47 mithrandir kernel: [15627.756087] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
> Feb 28 11:42:47 mithrandir kernel: [15627.758428] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 7 at 4, next 8)
> Feb 28 11:42:47 mithrandir kernel: [15628.260094] [drm:i915_reset] *ERROR* Failed to reset chip.
> 
> Is this is known issue?

I do not know. But it would be interesting to know if you just see this
in your log files or if you also see some effects like screen
corruptions. You can increase the log level by adding `drm.debug=0x06`
to the Linux kernel command line [1].

[…]


Thanks,

Paul


[1] http://intellinuxgraphics.org/how_to_report_bug.html

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-02-28  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28  4:03 Norbert Preining
2012-02-28  8:14 ` Paul Menzel [this message]
2012-03-01  7:42   ` Norbert Preining
2012-02-28  8:18 ` Dave Airlie
2012-02-28  8:32 ` Daniel Vetter
2012-03-09  8:07   ` Norbert Preining
2012-03-30  1:20     ` Norbert Preining

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1330416849.3899.11.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preining@logic.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®