From: Patrick McHardy <kaber@trash.net>
To: Alexander Nyberg <alexn@dsv.su.se>
Cc: Andi Kleen <ak@suse.de>, Ed Tomlinson <tomlins@cam.org>,
Parag Warudkar <kernel-stuff@comcast.net>,
linux-kernel@vger.kernel.org
Subject: Re: X86_64: 2.6.12-rc3 spontaneous reboot
Date: Tue, 26 Apr 2005 02:04:23 +0200 [thread overview]
Message-ID: <426D8587.6060507@trash.net> (raw)
In-Reply-To: <1114452899.2012.2.camel@localhost.localdomain>
Alexander Nyberg wrote:
> Usually gives in after about 20 minutes of gcc compiling, sometimes even
> up to 40 minutes. I had 2.6.12-rc2 stand for 2-3 hours so it seems ok.
> If anyone has a better recipe for it please do tell.
uml seems to trigger the bug faster, I'm usually seeing it within
a couple of minutes. I'm doing a binary search now.
> It doesn't appear to be any of the obvious patch candidates...
Which ones did you try?
next prev parent reply other threads:[~2005-04-26 0:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 4:08 X86_64: 2.6.12-rc3 spontaneous reboot Parag Warudkar
2005-04-24 8:41 ` Alexander Nyberg
2005-04-24 13:03 ` Ed Tomlinson
2005-04-24 13:35 ` ismail dönmez
2005-04-25 8:44 ` Patrick McHardy
2005-04-25 15:35 ` Andi Kleen
2005-04-25 18:14 ` Alexander Nyberg
2005-04-26 0:04 ` Patrick McHardy [this message]
2005-04-26 8:26 ` Alexander Nyberg
2005-04-26 13:04 ` Patrick McHardy
2005-04-26 13:53 ` Andi Kleen
2005-04-26 13:57 ` Patrick McHardy
2005-04-26 14:18 ` Patrick McHardy
2005-04-26 14:22 ` Andi Kleen
2005-04-26 14:51 ` Patrick McHardy
2005-04-26 14:53 ` Andi Kleen
2005-04-26 15:04 ` Patrick McHardy
2005-04-27 12:59 ` Andi Kleen
2005-04-27 22:05 ` Patrick McHardy
2005-04-26 20:28 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2005-04-24 21:58 Parag Warudkar
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=426D8587.6060507@trash.net \
--to=kaber@trash.net \
--cc=ak@suse.de \
--cc=alexn@dsv.su.se \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.