From: Alexander Nyberg <alexn@dsv.su.se>
To: Patrick McHardy <kaber@trash.net>
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 10:26:11 +0200 [thread overview]
Message-ID: <1114503971.887.8.camel@localhost.localdomain> (raw)
In-Reply-To: <426D8587.6060507@trash.net>
tis 2005-04-26 klockan 02:04 +0200 skrev Patrick McHardy:
> 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.
Ok, I'll try to compile UML, most of the times it doesn't work out for
me, but having something that triggers more reliably would be useful.
Sometimes it has taken even over an hour with gcc.
> > It doesn't appear to be any of the obvious patch candidates...
>
> Which ones did you try?
freepgt series and everything that directly touches ia32 emulation
between rc2 and rc3. The problem is I have only my saved commit mails
right now and some x64 patches seem to be missing, I need to learn git
and start reversing stuff from there...
No snapshots available either, whoever introduced the bug chose a bad
timing ;-)
next prev parent reply other threads:[~2005-04-26 8:26 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
2005-04-26 8:26 ` Alexander Nyberg [this message]
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=1114503971.887.8.camel@localhost.localdomain \
--to=alexn@dsv.su.se \
--cc=ak@suse.de \
--cc=kaber@trash.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox