public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: linux-next: WARNING: at kernel/lockdep.c:2680 check_flags+0x98/0x151()
Date: Tue, 03 Jun 2008 08:53:21 +0100	[thread overview]
Message-ID: <g22t9h$b01$1@ger.gmane.org> (raw)
In-Reply-To: 4844868F.20104@gmail.com

Kevin Winchester wrote:

> In next-20080530 and next-20080602 (and possibly earlier - I can't
> remember the linux-next tree before that I tried) I get the following:
> 
> [   12.885153] ------------[ cut here ]------------
> [   12.885203] WARNING: at kernel/lockdep.c:2680 check_flags+0x98/0x151()
> [   12.885248] Pid: 4, comm: watchdog/0 Not tainted
> 2.6.26-rc4-next-20080602 #13

I saw this and mentioned it too - 
http://groups.google.co.uk/group/fa.linux.kernel/browse_thread/thread/77d4cedb7b27fa3b/fc66f2d849b42031?lnk=gst&q=watchdog+sitsofe#fc66f2d849b42031 .

> This is completely reproducible on every boot - should I try to bisect it?

Things that have been bisected seem far more likely to be looked at so if
you have the stomach... If you do start bisection I can confirm that it is
in next-20080529 . I can also mention that on my system the warning seems
to go away if I boot with nmi_watchdog=2 .

-- 
Sitsofe | http://sucs.org/~sits/


  reply	other threads:[~2008-06-03  7:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 23:47 linux-next: WARNING: at kernel/lockdep.c:2680 check_flags+0x98/0x151() Kevin Winchester
2008-06-03  7:53 ` Sitsofe Wheeler [this message]
2008-06-03  8:53 ` Peter Zijlstra
2008-06-03 12:22   ` Kevin Winchester
2008-06-03 16:28     ` Johannes Weiner
2008-06-03 16:34       ` Peter Zijlstra
2008-06-04 17:50     ` [X86][BISECTED] WARNING: at kernel/lockdep.c:2680 Sitsofe Wheeler
     [not found]       ` <20080605130823.GD6332@elte.hu>
2008-06-05 23:53         ` Kevin Winchester
2008-06-04  7:45 ` linux-next: WARNING: at kernel/lockdep.c:2680 check_flags+0x98/0x151() Sitsofe Wheeler

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='g22t9h$b01$1@ger.gmane.org' \
    --to=sitsofe@yahoo.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