public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "ismail dönmez" <ismail.donmez@gmail.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Alexander Nyberg <alexn@dsv.su.se>,
	Parag Warudkar <kernel-stuff@comcast.net>,
	linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: X86_64: 2.6.12-rc3 spontaneous reboot
Date: Sun, 24 Apr 2005 16:35:06 +0300	[thread overview]
Message-ID: <2a4f155d0504240635a325a48@mail.gmail.com> (raw)
In-Reply-To: <200504240903.31377.tomlins@cam.org>

Running 2.6.12-rc3 here on amd64 and I don't see any reboots. So it
might be config dependent.


On 4/24/05, Ed Tomlinson <tomlins@cam.org> wrote:
> On Sunday 24 April 2005 04:41, Alexander Nyberg wrote:
> > sön 2005-04-24 klockan 00:08 -0400 skrev Parag Warudkar:
> > > While running a 32 bit Java program 2.6.12-rc3 rebooted spontaneously
> leaving 
> > > a corrupt partition table and disk with errors. There was nothing in
> dmesg 
> > > (no oops/panic) except some -MARK- entries during the reboot.
> > > 
> > 
> > Is this reproducible? If so, can you give a detailed description of how.
> 
> 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()
> 
> some people have reported reversing (in -mm)
> 
> sched-unlocked-context-switches.patch
> 
> Helps too.
> 
> Ed Tomlinson
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
Time is what you make of it

  reply	other threads:[~2005-04-24 13:35 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 [this message]
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
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=2a4f155d0504240635a325a48@mail.gmail.com \
    --to=ismail.donmez@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox