public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Thu, 25 Sep 2008 23:27:55 +0400	[thread overview]
Message-ID: <20080925192755.GE7259@localhost> (raw)
In-Reply-To: <f1c9d250809251134j6fac8bfu43f08cbf2b330f0a@mail.gmail.com>

[Tej - Fri, Sep 26, 2008 at 12:04:30AM +0530]
...
| >
| > If assume that git bisect is right - it's hardly possible
| 
| i have bisected it twice n jason mentioned that it looks like some
| kind of nmi race condition.
| 
| but i will bisect it again in rc7 and let you know.
| 
| > that proc_nmi_enabled() related changes introduced this
| > error (ie this commit) - kgdb seems to be not
| > touching /proc/sys/kernel/nmi while doing self-tests.
| >
| > 		- Cyrill -
| >
| 

There was a race in nmi code indeed which was fixed recently in
-tip tree but it was leading to use unitialized vars. So give
me some time to digg a bit. I'll do it tomorrow and write you.
Thanks a lot for pointing out this problem!

		- Cyrill -

  reply	other threads:[~2008-09-25 19:28 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 [this message]
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

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=20080925192755.GE7259@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