public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm fixes
Date: Mon, 30 Nov 2015 08:33:19 +0100	[thread overview]
Message-ID: <20151130073319.GC17050@phenom.ffwll.local> (raw)
In-Reply-To: <CAPM=9tzss6bGpk5wOahGeGohoLweD3j_kbTwByz_OEjG7e2eyA@mail.gmail.com>

On Sat, Nov 28, 2015 at 05:36:54AM +1000, Dave Airlie wrote:
> On 28 November 2015 at 05:05, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > On Thu, Nov 19, 2015 at 8:07 PM, Dave Airlie <airlied@linux.ie> wrote:
> >>
> >> core: Atomic fixes and Atomic helper fixes
> >> i915: Revert for the backlight regression along with a bunch of fixes.
> >
> > So I have no idea if the GPU updates are my problem, but my main
> > desktop machine has been hanging silently a few times lately.
> >
> > It has never done it while unattended, even if it's doing things like
> > compiling the kernel. So I'm a bit inclined to blame graphics.
> >
> > Sadly, when it hangs, it's a total hang and doesn't leave anything in
> > the logs - I just have to reboot.
> >
> > I'll try to see if I can get anything at all out of the machine, but I
> > thought I'd ask if there is some known issue with Haswell graphics in
> > the 4.4-rc code base?
> >
> > Sorry for the complete lack of details, and really any hard reason to
> > even blame the GPU people.. You may be entirely blameless.
> 
> I've been running this fixes pull on my haswell laptop since I sent it to you,
> 
> and I've been using it, F22 + gnome-shell.
> 
>  05:35:41 up 7 days, 18:31, 35 users,  load average: 0.26, 0.26, 0.23
> 
> So I'm not aware of anything at least with Haswell in general.

Yeah I just hunted down a test infrastructure failure on my Haswell the
past few days with various loads and output configs. Seemed very happy.
And not aware of anything else blowing up (bdw/skl would be less
surprising).
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-11-30  7:33 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.00.1511200403280.14352@skynet.skynet.ie>
2015-11-27 19:05 ` [git pull] drm fixes Linus Torvalds
2015-11-27 19:36   ` Dave Airlie
2015-11-30  7:33     ` Daniel Vetter [this message]
2015-11-30 19:14       ` Linus Torvalds
     [not found] <alpine.DEB.2.00.1503202149180.5859@skynet.skynet.ie>
2015-03-23 15:33 ` Josh Boyer
2015-03-23 18:34   ` Josh Boyer
2015-03-24  7:32     ` Daniel Vetter
2015-03-24 13:15       ` Josh Boyer
2015-03-24 13:40         ` [Intel-gfx] " Daniel Vetter
2015-03-24 13:57           ` Josh Boyer
2015-03-24 14:22             ` Josh Boyer
2015-03-24 14:34               ` [Intel-gfx] " Daniel Vetter
2015-03-24 14:46                 ` Josh Boyer
2015-03-24 16:10                   ` Josh Boyer
2015-03-24 16:48                     ` Daniel Vetter
2015-03-24 16:49                       ` [Intel-gfx] " Daniel Vetter
2015-03-24 16:54                         ` Josh Boyer
2015-03-25  3:49                           ` Xi Ruoyao
2015-03-25  8:54                     ` Daniel Vetter
2015-03-25 13:11                       ` [Intel-gfx] " Josh Boyer
2015-03-25 14:00                         ` Daniel Vetter
2015-03-25 14:56                           ` Xi Ruoyao
2015-03-25 15:12                             ` Xi Ruoyao
2015-03-25 15:37                           ` [Intel-gfx] " Josh Boyer
2015-03-25 15:50                             ` Daniel Vetter
2015-03-25 15:53                               ` Josh Boyer
2015-03-25 16:42                                 ` Josh Boyer
2015-03-25 17:17                                   ` Daniel Vetter
2015-03-25 17:37                                     ` Josh Boyer
2015-03-25 19:40                                       ` Josh Boyer
2015-03-25 23:32                                         ` Xi Ruoyao
2015-03-26  8:41                                           ` Xi Ruoyao
2015-03-24  1:41   ` Dave Jones
2015-03-25  8:56     ` Daniel Vetter
2015-03-25 14:34       ` Dave Jones
     [not found] <alpine.DEB.2.00.1502270441160.21188@skynet.skynet.ie>
2015-03-01  5:40 ` Linus Torvalds
2015-03-01  6:08   ` Linus Torvalds
2015-03-01  7:27     ` Linus Torvalds
2015-03-01 20:35       ` Linus Torvalds
2015-03-01 21:00         ` Linus Torvalds
2015-03-02  1:59           ` Linus Torvalds
2015-03-02  9:04             ` Daniel Vetter
2015-03-02 16:53               ` Linus Torvalds
2015-03-02  9:44     ` Paul Bolle
2015-03-02 10:26       ` Jani Nikula
2015-03-02 10:33       ` Daniel Vetter
     [not found] <alpine.DEB.2.00.1308300006570.10513@skynet.skynet.ie>
2013-08-31 23:02 ` Linus Torvalds
2013-09-01 20:10   ` Linus Torvalds
2013-09-02  6:54   ` Daniel Vetter
2013-09-02 16:53     ` Linus Torvalds

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=20151130073319.GC17050@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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