From: Andrew Clayton <andrew@rootshell.co.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc6-git[12] spontaneous reboots on x86_64
Date: Tue, 14 Mar 2006 21:30:36 +0000 [thread overview]
Message-ID: <1142371836.2513.24.camel@alpha.digital-domain.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0603141843110.6114@goblin.wat.veritas.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Tue, 2006-03-14 at 18:50 +0000, Hugh Dickins wrote:
> On Tue, 14 Mar 2006, Andrew Clayton wrote:
> > On Tue, 2006-03-14 at 08:06 -0800, Linus Torvalds wrote:
> > >
> > > Reverted. Let's get wider testing before applying an alternate fix.
> >
> > Just to note: Doing what Andi suggested seems to be working OK.
>
> Whereas on EM64T I found the opposite,
> reverting just the stub_execve hunk still behaved badly.
>
> I've double-checked that finding since, built and ran another
> kernel to confirm it. But your Athlon64 still works OK that way?
OK, looks like I may have spoke too soon, just found my ssh session to
it dead and the machine no longer reachable (other machines on the same
network are). I'll be able to see for sure when I get into work in the
morning.
Andrew
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-03-14 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 11:55 Andrew Clayton
2006-03-14 15:30 ` Hugh Dickins
2006-03-14 15:39 ` Andi Kleen
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 [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=1142371836.2513.24.camel@alpha.digital-domain.net \
--to=andrew@rootshell.co.uk \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®