From: Andreas Mohr <andi@lisas.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Mohr <andi@lisas.de>,
Mikulas Patocka <mpatocka@redhat.com>,
David Airlie <airlied@linux.ie>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3.14-rc7 crashes in drm ([PATCH] a crash in mga_driver_irq_uninstall)
Date: Sun, 23 Mar 2014 22:27:15 +0100 [thread overview]
Message-ID: <20140323212715.GA22767@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <CA+55aFyu_5eE5j2LLjhEQSAOAiLyuA65Z2o_TGdvhVMedWKTwA@mail.gmail.com>
On Sun, Mar 23, 2014 at 09:39:16AM -0700, Linus Torvalds wrote:
> On Sun, Mar 23, 2014 at 5:15 AM, Andreas Mohr <andi@lisas.de> wrote:
> >
> > which did end up flawless on 3.12.0-rc2+, too
> > (but failed to improve the issue on 3.14.0-rc7+).
> >
> > So, for all intents and purposes, drm infrastructure seems unavoidably
> > (neither dri disable nor libdrm upgrade helps) affected.
> > Does anyone know which change caused that issue?
> > (I'm asking because bisect here would be relatively painful).
>
> So 3.12-rc2 works. Does 3.13 work? Is this a regression in the current
> 3.14 rc only, or did it happen already in the previous release?
Hmm, given that Mikulas in
https://lkml.org/lkml/2014/2/26/537
offered a diff of linux-3.13.5 files, it truly seems (shock! ack! noo!)
that that indeed may have been a regression at <= 3.13 proper even
(which may pose interesting questions about the level of testing coverage
we still enjoy [not!?] in this hardware area).
Oh well, seems I'll have to prepare/build 3.13 now...
Thanks,
Andreas Mohr
next prev parent reply other threads:[~2014-03-23 21:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 21:25 [PATCH] a crash in mga_driver_irq_uninstall Mikulas Patocka
2014-03-22 23:43 ` 3.14-rc7 crashes in drm ([PATCH] a crash in mga_driver_irq_uninstall) Andreas Mohr
2014-03-23 12:15 ` Andreas Mohr
2014-03-23 16:39 ` Linus Torvalds
2014-03-23 21:27 ` Andreas Mohr [this message]
2014-03-23 21:45 ` Dave Airlie
2014-03-24 8:56 ` Daniel Vetter
2014-03-24 17:17 ` Mikulas Patocka
2014-03-24 20:26 ` Daniel Vetter
2014-03-24 20:40 ` Mikulas Patocka
2014-03-24 21:46 ` Daniel Vetter
2014-03-24 23:11 ` Andreas Mohr
2014-03-25 9:13 ` Daniel Vetter
2014-03-25 22:42 ` Mikulas Patocka
2014-03-26 7:15 ` Daniel Vetter
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=20140323212715.GA22767@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--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
all inboxes | Powered by JetHome®