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: Sat, 14 Jan 2006 17:51:37 -0500 [thread overview]
Message-ID: <20060114225137.GB23021@redhat.com> (raw)
In-Reply-To: <200601141943.28027.ak@suse.de>
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.
> > - Reboot
> > - Total lockup
> > - NMI watchdog firing, and then lockup
> >
> > I've tried backing out a handful of the x86-64 patches, and
> > didn't get too far, as some of them are dependant on others,
> > it quickly became a real mess to try to bisect where exactly it broke.\
>
> Shouldn't be too bad - i did a binary search for something else and it worked
> pretty well.
The patches reverted, but I hit problems like modprobe segfaulting during
boot, or reboots during APIC init.
> > Any ideas for potential candidates to try & back out ?
> Does it work when you revert all x86-64 changes?
-git6 which was the last one not to include the x86-64 changes boots and runs fine.
I'll try a latest -git with x86-64 backed out when I get a chance.
Dave
next prev parent reply other threads:[~2006-01-14 22:51 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 [this message]
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
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=20060114225137.GB23021@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