From: Andi Kleen <andi@firstfloor.org>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Pete Zaitcev <zaitcev@redhat.com>,
ak@suse.de, linux-kernel@vger.kernel.org,
Benny Halevy <bhalevy@panasas.com>,
akpm@linux-foundation.org
Subject: Re: Andi, you broke my laptop :-)
Date: Thu, 10 May 2007 16:19:42 +0200 [thread overview]
Message-ID: <20070510141942.GM14898@one.firstfloor.org> (raw)
In-Reply-To: <20070510133555.GA5705@amd.com>
On Thu, May 10, 2007 at 03:35:56PM +0200, Joerg Roedel wrote:
> On Thu, May 10, 2007 at 03:01:44PM +0200, Andi Kleen wrote:
> > On Wed, May 09, 2007 at 12:56:16PM -0700, Pete Zaitcev wrote:
> > > Hi, Andi:
> > >
> > > The attached patch (actually, git show output) makes my Dell 1501 to hang
> > > on boot. Sorry, I have no clue why... The culprit is found with git bisect.
> > > But yes, it's an AMD MK-36. I use an x86_64 kernel. It is 100% reproducible.
> >
> > MK-36? Does it have SVM?
> >
> > Anyways we previously had issues with this being miscompiled, but
> > I thought the latest patch should have been ok. What compiler do you use?
> >
> > Can you send me a disassembly listing of arch/x86_64/kernel/time.o?
>
> I debugged this problem a bit and my compiler[1]interprets the =A
> constraint as %rax instead of %edx:%eax on x86_64 which causes the
> problem. The appended patch provides a workaround for this and fixed the
> hang on my machine.
Hmm yes now I can reproduce it too. I didn't see any hangs so i suppose
my (and that of most -mm tester's) compiled binary always happened to have a
suitable value in edx
Thanks for the patch.
-Andi
next prev parent reply other threads:[~2007-05-10 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 19:56 Pete Zaitcev
2007-05-10 13:01 ` Andi Kleen
2007-05-10 13:35 ` Joerg Roedel
2007-05-10 14:19 ` Andi Kleen [this message]
2007-05-10 14:25 ` Benny Halevy
2007-05-10 16:31 ` Pete Zaitcev
[not found] <4642E8AA.7060501@panasas.com>
2007-05-10 10:12 ` Benny Halevy
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=20070510141942.GM14898@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@panasas.com \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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
Powered by JetHome