All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Nyberg <alexn@dsv.su.se>
To: Andi Kleen <ak@suse.de>
Cc: Patrick McHardy <kaber@trash.net>, 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: Mon, 25 Apr 2005 20:14:59 +0200	[thread overview]
Message-ID: <1114452899.2012.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20050425153541.GC16828@wotan.suse.de>

> > >I think rc3 has code from rc2-mm2/3.  Both of these reboot here randomly.  
> > >Nothing
> > >shows up on a serial console...  Think something is seriously wrong with 
> > >x86_64 in rc3.
> > >That being said its possible its fixed in HEAD by.
> > >
> > >[PATCH] x86_64: fix new out of line put_user()
> > >[PATCH] x86_64: Bug in new out of line put_user()
> > 
> > I'm seeing the same problem with a fresh git checkout when running uml
> > or gcc in 32bit mode. Nothing is received from netconsole. If anyone
> > can suggest which patches might be worth reverting I'll try that.
> 
> Well, you can revert all my x86-64 changes for testing that went
> in after rc2. Does that make a difference? If yes then please
> do a binary search or give me a test case that shows the problem.
> 

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.

It doesn't appear to be any of the obvious patch candidates...


  reply	other threads:[~2005-04-25 18:15 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 [this message]
2005-04-26  0:04           ` Patrick McHardy
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=1114452899.2012.2.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 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.