linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Beregalov <a.beregalov@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
	Kernel Testers List <kernel-testers@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.k
Subject: 2.6.30-rc2: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
Date: Wed, 15 Apr 2009 16:43:52 +0400	[thread overview]
Message-ID: <a4423d670904150543w3d6e1371i874618c6bd8bbd0e@mail.gmail.com> (raw)

Hi

bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex, receive &
transmit flow control ON
BUG: MAX_LOCKDEP_ENTRIES too low!
turning off the locking correctness validator.
Pid: 2382, comm: mount Tainted: G        W  2.6.30-rc2-dirty #121
Call Trace:
 [<ffffffff80280aa7>] add_lock_to_list+0xf7/0x110
 [<ffffffff80282ad1>] ? check_irq_usage+0xb1/0x110
 [<ffffffff802df73c>] ? lock_super+0x3c/0x60
 [<ffffffff80284f20>] __lock_acquire+0xe80/0x12b0
 [<ffffffff802df73c>] ? lock_super+0x3c/0x60
 [<ffffffff802853f0>] lock_acquire+0xa0/0xe0
 [<ffffffff802df73c>] ? lock_super+0x3c/0x60
 [<ffffffff805f0b50>] ? usbfs_fill_super+0x0/0xe0
 [<ffffffff806d9178>] __mutex_lock_common+0x68/0x500
 [<ffffffff802df73c>] ? lock_super+0x3c/0x60
 [<ffffffff802df73c>] ? lock_super+0x3c/0x60
 [<ffffffff805f0b50>] ? usbfs_fill_super+0x0/0xe0
 [<ffffffff806d9738>] mutex_lock_nested+0x48/0x70
 [<ffffffff802df73c>] lock_super+0x3c/0x60
 [<ffffffff802dfa7a>] __fsync_super+0x2a/0xa0
 [<ffffffff802dfb10>] fsync_super+0x20/0x50
 [<ffffffff802f1f70>] ? shrink_dcache_sb+0x20/0x40
 [<ffffffff802dfb8c>] do_remount_sb+0x4c/0x250
 [<ffffffff802e08a5>] get_sb_single+0x75/0x100
 [<ffffffff805f02b9>] usb_get_sb+0x29/0x50
 [<ffffffff802df0e7>] vfs_kern_mount+0x67/0xf0
 [<ffffffff802f942d>] ? get_fs_type+0x4d/0xf0
 [<ffffffff802df21d>] do_kern_mount+0x5d/0x130
 [<ffffffff802fcd88>] do_mount+0x2e8/0x930
 [<ffffffff802a996e>] ? __get_free_pages+0x2e/0x80
 [<ffffffff802fd4b0>] sys_mount+0xe0/0x120
 [<ffffffff8020ba6b>] system_call_fastpath+0x16/0x1b

             reply	other threads:[~2009-04-15 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 12:43 Alexander Beregalov [this message]
2009-04-20  7:42 ` 2.6.30-rc2: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs Alexander Beregalov

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=a4423d670904150543w3d6e1371i874618c6bd8bbd0e@mail.gmail.com \
    --to=a.beregalov@gmail.com \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-fsdevel@vger.k \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).