public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-git breaks Xorg on em64t
Date: Sun, 15 Jan 2006 23:29:40 -0500	[thread overview]
Message-ID: <20060116042940.GA3535@redhat.com> (raw)
In-Reply-To: <200601151647.11730.ak@suse.de>

On Sun, Jan 15, 2006 at 04:47:11PM +0100, Andi Kleen wrote:
 > On Sunday 15 January 2006 08:06, Dave Jones wrote:
 > > On Sun, Jan 15, 2006 at 01:05:07AM +0100, Andi Kleen wrote:
 > >  > On Saturday 14 January 2006 23:51, Dave Jones wrote:
 > >  > > On Sat, Jan 14, 2006 at 07:43:27PM +0100, Andi Kleen wrote:
 > >  > >  > On Saturday 14 January 2006 07:52, Dave Jones wrote:
 > >  > >  > > Andi,
 > >  > >  > >  Sometime in the last week something was introduced to Linus'
 > >  > >  > > tree which makes my dual EM64T go nuts when X tries to start.
 > >  > >  > > By "go nuts", I mean it does various random things, seen so
 > >  > >  > > far..
 > >  > >  > > - Machine check. (I'm convinced this isn't a hardware problem
 > >  > >  > >   despite the new addition telling me otherwise :)
 > >  > >  >
 > >  > >  > Normally it should be impossible to cause machine checks from
 > >  > >  > software on Intel systems.
 > >  > >
 > >  > > -git7+ is the only time I've ever seen one on this box.
 > >  >
 > >  > What happens when you apply
 > >  >
 > >  > ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/patches/page-table-setup
 > >
 > > What does this apply to ? Is it dependant on something else not
 > > merged yet ? I get rejects when I apply it to 2.6.15-git10
 > 
 > To the other patches in the quilt queue (that is the x86-64 pending
 > tree that everybody is supposed to test, but nobody does) 
 > 
 > I see there was a one liner reject with the memory hot add patch in there. I 
 > reordered it now to come first. It was for -git9.

It didn't solve my problem.   It hung at X startup again, and then
the NMI watchdog triggered.  I'll try reverting DaveA's DRM bits,
but I'm not optimistic, as a) this card isn't supported yet, and b) whilst
it's compiled in, it was disabled by X at startup due to me using dual-head.

		Dave


      reply	other threads:[~2006-01-16  4:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-14  6:52 2.6.15-git breaks Xorg on em64t Dave Jones
2006-01-14 14:49 ` Alessandro Suardi
2006-01-14 18:43 ` Andi Kleen
2006-01-14 22:51   ` Dave Jones
2006-01-15  0:05     ` Andi Kleen
2006-01-15  7:06       ` Dave Jones
2006-01-15  8:35         ` Anton Altaparmakov
2006-01-15  9:36         ` Dave Airlie
2006-01-16  6:36           ` Dave Jones
2006-01-16 12:11             ` Dave Airlie
2006-01-15 15:47         ` Andi Kleen
2006-01-16  4:29           ` Dave Jones [this message]

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=20060116042940.GA3535@redhat.com \
    --to=davej@redhat.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.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