From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Tej <bewith.tej@gmail.com>
Cc: Jason Wessel <jason.wessel@windriver.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel PANIC with 2.6.27-rc6
Date: Fri, 3 Oct 2008 18:01:40 +0400 [thread overview]
Message-ID: <20081003140140.GA7595@localhost> (raw)
In-Reply-To: <f1c9d250810030348h5c61241fg79bf769e1da16a8@mail.gmail.com>
[Tej - Fri, Oct 03, 2008 at 04:18:55PM +0530]
| On 9/26/08, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
| > [Cyrill Gorcunov - Thu, Sep 25, 2008 at 11:39:56PM +0400]
| > | [Tej - Fri, Sep 26, 2008 at 12:04:30AM +0530]
| > | ...
| > |
| > | Btw Tej, could you please apply this patch
| > | and check if it help.
| > |
| > | http://lkml.org/lkml/2008/9/22/250
| > |
| > | Aristeu Rozanski fixed one race window which take
| > | place on unpredicted nmi's.
| > |
| > | - Cyrill -
| >
| > Btw Tej, could you post boot log if kernel were started as
| >
| > root=/dev/sda1 ro debug apic=debug kgdbts=V2 splash console=tty0
| > console=ttyS0,
| sorry for this long pause.
|
| machine boots fine with the options specified, and logs are collected
| as follows.
| some warning related to sysctl table checking, but its related to
| libvirtd (KVM) at the end.
|
ok, lets assume NMI race is fixed
- Cyrill -
prev parent reply other threads:[~2008-10-03 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 15:41 Kernel PANIC with 2.6.27-rc6 Tej
2008-09-12 17:58 ` Kernel PANIC with 2.6.27-rc6 (kgdb) Randy Dunlap
[not found] ` <48C94F65.3050405@windriver.com>
2008-09-25 14:35 ` Kernel PANIC with 2.6.27-rc6 Tej
2008-09-25 14:56 ` Cyrill Gorcunov
2008-09-25 15:47 ` Cyrill Gorcunov
2008-09-25 18:34 ` Tej
2008-09-25 19:27 ` Cyrill Gorcunov
2008-09-25 19:39 ` Cyrill Gorcunov
2008-09-26 8:50 ` Cyrill Gorcunov
2008-10-03 10:48 ` Tej
2008-10-03 14:01 ` Cyrill Gorcunov [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=20081003140140.GA7595@localhost \
--to=gorcunov@gmail.com \
--cc=bewith.tej@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.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