From: Andi Kleen <ak@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Clayton <andrew@rootshell.co.uk>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc6-git[12] spontaneous reboots on x86_64
Date: Tue, 14 Mar 2006 16:39:38 +0100 [thread overview]
Message-ID: <200603141639.38988.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0603141523340.4309@goblin.wat.veritas.com>
On Tuesday 14 March 2006 16:30, Hugh Dickins wrote:
> Andi, if you've a replacement patch you'd like everybody to test,
> please post: I for one will surely give it a try.
Hrm, it worked on my test machine.
But what happens when you just revert the last hunk (the stub_execve change)?
-Andi
next prev parent reply other threads:[~2006-03-14 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 11:55 2.6.16-rc6-git[12] spontaneous reboots on x86_64 Andrew Clayton
2006-03-14 15:30 ` Hugh Dickins
2006-03-14 15:39 ` Andi Kleen [this message]
2006-03-14 16:27 ` Hugh Dickins
2006-03-14 16:06 ` Linus Torvalds
2006-03-14 16:24 ` Andrew Clayton
2006-03-14 18:50 ` Hugh Dickins
2006-03-14 18:55 ` Andrew Clayton
2006-03-14 21:30 ` Andrew Clayton
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=200603141639.38988.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=andrew@rootshell.co.uk \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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