From: Ingo Molnar <mingo@elte.hu>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
dri-devel@lists.sf.net
Subject: Re: [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off switch out of staging."
Date: Thu, 4 Feb 2010 07:26:19 +0100 [thread overview]
Message-ID: <20100204062619.GA29154@elte.hu> (raw)
In-Reply-To: <21d7e9971002021234y275fae02k410af92bb16fee73@mail.gmail.com>
* Dave Airlie <airlied@gmail.com> wrote:
> On Wed, Feb 3, 2010 at 1:46 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Dave Airlie <airlied@gmail.com> wrote:
> >
> >> On Tue, Feb 2, 2010 at 6:17 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >> >
> >> > * Dave Airlie <airlied@linux.ie> wrote:
> >> >
> >> >> > Hi Linus,
> >> >> >
> >> >> > Please pull the 'drm-linus' branch from
> >> >> > ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-linus
> >> >> >
> >> >>
> >> >> I've also added an oops fix I seem to lose off my radar to this tree.
> >> >>
> >> >> commit 17aafccab4352b422aa01fa6ebf82daff693a5b3
> >> >> Author: Michel D??nzer <daenzer@vmware.com>
> >> >> Date: ? Fri Jan 22 09:20:00 2010 +0100
> >> >>
> >> >> ? ? drm/radeon/kms: Fix oops after radeon_cs_parser_init() failure.
> >> >
> >>
> >> Wierd this suggests something else is wrong on that machine can you get me
> >> the whole dmesg? I'm guessing some iommu or swiotlb issue.
> >
> > This box has no known hardware or software problems, just this week it booted
> > in excess of 1000 kernels so i'd exclude that angle for now.
> >
> > I have bisected the crash back to the DRM tree and the crash went away with
> > the Kconfig revert i applied - and it got fixed by Jerome's patch. I posted
> > my config and i posted the relevant boot log as well. Find below the full
> > bootlog as well with vanilla -git (ab65832) and the config. (i dont think it
> > matters)
> >
> >> I've asked Jerome to fix the oops, but really anyone with an old .config
> >> won't get hit by this, and we've booted this on quite a lot of machines at
> >> this point.
> >
> > I dont see the commit in yesterday's linux-next. It has very fresh
> > timestamps:
> >
> > ?commit f71d0187987e691516cd10c2702f002c0e2f0edc
> > ?Author: ? ? Dave Airlie <airlied@redhat.com>
> > ?AuthorDate: Mon Feb 1 11:35:47 2010 +1000
> > ?Commit: ? ? Dave Airlie <airlied@redhat.com>
> > ?CommitDate: Mon Feb 1 11:35:47 2010 +1000
> >
> > What kind of widespread testing could this commit have gotten in the less
> > than 24 hours before it hit mainline?
> >
>
> Its shipping in a major distro by default, its planned to be shipped in an
> even more major distro. Its been boot tested on 1000s of machines by 1000s
> of ppl.
Well but that's not the precise tree you sent to Linus, is it?
Ingo
next prev parent reply other threads:[~2010-02-04 6:26 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 2:20 [git pull] drm fixes Dave Airlie
2010-02-01 2:53 ` Dave Airlie
2010-02-02 8:17 ` [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off switch out of staging." Ingo Molnar
2010-02-02 8:25 ` Dave Airlie
2010-02-02 15:44 ` Ingo Molnar
2010-02-04 20:39 ` Dave Airlie
2010-02-04 20:46 ` Ingo Molnar
2010-02-04 21:14 ` Dave Airlie
2010-02-05 0:43 ` Dave Airlie
2010-02-05 7:32 ` Ingo Molnar
2010-02-02 8:35 ` Dave Airlie
2010-02-02 8:37 ` Dave Airlie
2010-02-02 15:42 ` Ingo Molnar
2010-02-02 15:46 ` Ingo Molnar
2010-02-02 20:34 ` Dave Airlie
2010-02-04 6:26 ` Ingo Molnar [this message]
2010-02-04 6:39 ` Dave Airlie
2010-02-04 7:36 ` Ingo Molnar
2010-02-04 7:49 ` Dave Airlie
2010-02-04 7:17 ` hung bootup with " Ingo Molnar
2010-02-04 16:48 ` Matthew Garrett
2010-02-04 17:08 ` Ingo Molnar
2010-02-04 17:15 ` Linus Torvalds
2010-02-04 17:36 ` Ingo Molnar
2010-02-04 17:36 ` Matthew Garrett
2010-02-04 17:54 ` Ingo Molnar
2010-02-04 17:59 ` Matthew Garrett
2010-02-04 18:12 ` Ingo Molnar
2010-02-04 18:15 ` Matthew Garrett
2010-02-04 18:56 ` Ingo Molnar
2010-02-04 19:00 ` Matthew Garrett
2010-02-04 19:19 ` Ingo Molnar
2010-02-04 19:28 ` Jerome Glisse
2010-02-04 20:34 ` Ingo Molnar
2010-02-04 18:30 ` Alex Deucher
2010-02-04 19:06 ` Ingo Molnar
2010-02-04 19:18 ` Alex Deucher
2010-02-04 19:24 ` Linus Torvalds
2010-02-04 19:34 ` Dave Airlie
2010-02-04 20:27 ` Ingo Molnar
2010-02-04 19:32 ` Ingo Molnar
2010-02-04 19:53 ` Jesse Barnes
2010-02-04 20:22 ` Ingo Molnar
2010-02-04 20:27 ` david
2010-02-04 20:33 ` Jesse Barnes
2010-02-04 20:57 ` Ingo Molnar
2010-02-04 20:48 ` Matthew Garrett
2010-02-04 21:05 ` Ingo Molnar
2010-02-04 21:09 ` Matthew Garrett
2010-02-05 7:56 ` Ingo Molnar
2010-02-05 8:34 ` Dave Airlie
2010-02-05 9:00 ` Ingo Molnar
2010-02-05 9:18 ` Dave Airlie
2010-02-05 10:47 ` Ingo Molnar
2010-02-04 21:23 ` Andrew Morton
2010-02-04 21:34 ` Jesse Barnes
2010-02-04 21:35 ` Dave Airlie
2010-02-06 11:10 ` Felipe Contreras
2010-02-02 8:58 ` [crash, PATCH] Revert " Domenico Andreoli
2010-02-02 11:59 ` Jerome Glisse
2010-02-02 15:11 ` Domenico Andreoli
2010-02-02 11:56 ` Jerome Glisse
2010-02-02 15:42 ` Ingo Molnar
2010-02-02 23:15 ` Jerome Glisse
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=20100204062619.GA29154@elte.hu \
--to=mingo@elte.hu \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--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).