From: Stephen Clark <sclark46@earthlink.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
Chris Wilson <chris@chris-wilson.co.uk>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Keith Packard <keithp@keithp.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm next tree
Date: Wed, 23 Mar 2011 08:21:53 -0400 [thread overview]
Message-ID: <4D89E5E1.3070402@earthlink.net> (raw)
In-Reply-To: <AANLkTinoTs89ThBnZ17+fPE+t1V=GycKq2EJG-LadFZQ@mail.gmail.com>
On 03/22/2011 10:19 PM, Linus Torvalds wrote:
> So I had hoped - yes, very naïve of me, I know - that this merge
> window would be different.
>
> But it's not.
>
> On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie<airlied@linux.ie> wrote:
>
>> i915: big 855 fix, lots of output setup refactoring, lots of misc fixes.
>>
> .. and apparently a lot of breakage too. My crappy laptop that I abuse
> for travel is - once more - broken by the updates. I cannot suspend
> and resume, because every resume seems to fail.
>
> One of the more useful failures was:
>
> [ 61.656055] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
> elapsed... GPU hung
> [ 61.656079] [drm] capturing error event; look for more information
> in /debug/dri/0/i915_error_state
> [ 61.664387] [drm:i915_wait_request] *ERROR* i915_wait_request
> returns -11 (awaiting 2 at 0, next 3)
>
> and I'm attaching the error_state file from that particular case here.
> In other cases it seems to just hang entirely.
>
> Keith/Jesse/Chris - I don't know that it's i915, and it will take
> forever to bisect (I'll try). But it does seem pretty likely.
>
> Linus
>
Why can't the gpu be reset/restarted when this happens? When a nic card
gets hung it is reinitialized
and restarted why not the gpu?
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next prev parent reply other threads:[~2011-03-23 12:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 4:09 [git pull] drm next tree Dave Airlie
2011-03-23 2:19 ` Linus Torvalds
2011-03-23 12:21 ` Stephen Clark [this message]
2011-03-23 14:39 ` Jerome Glisse
2011-03-23 15:22 ` Jesse Barnes
2011-03-23 14:22 ` Alessandro Suardi
2011-03-23 15:29 ` Linus Torvalds
2011-03-23 15:33 ` Jesse Barnes
2011-03-24 0:54 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2014-01-30 2:49 Dave Airlie
2014-01-30 4:54 ` Linus Torvalds
2014-01-30 12:33 ` Paul Bolle
2014-01-30 15:55 ` Jiri Kosina
2014-02-07 10:08 ` Jiri Kosina
2014-02-07 11:10 ` Jani Nikula
2014-02-07 13:40 ` Jiri Kosina
2014-02-07 14:05 ` Daniel Vetter
2014-02-07 14:15 ` Jiri Kosina
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=4D89E5E1.3070402@earthlink.net \
--to=sclark46@earthlink.net \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).