From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REPORT] BUG: spinlock recursion on CPU#0, init/1
Date: Tue, 18 Jan 2011 17:19:05 +0100 [thread overview]
Message-ID: <201101181719.05608.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <a7a9bdaa5936630925fb7ffd1a1795b1@mail.gmail.com>
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=27022
for your bug report, please add your address to the CC list in there, thanks!
On poniedziałek, 10 stycznia 2011 o 16:21:59 Santosh Shilimkar wrote:
> On latest mainline commit I seeing a regression when rootfs
> is mounted on NFS. Not sure if it's already known regression.
>
> Anybody is aware of this one ?
>
> --------------------------------------
> Uncompressing Linux... done, booting the kernel.
> Linux version 2.6.37-03766-g0390214 (a0393909@a0393909-desktop) (gcc
> version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #44 SMP Mon Jan 10 20:41:27
> IST 2011
>
> [....]
>
> VFS: Mounted root (nfs filesystem) on device 0:13.
> Freeing init memory: 296K
> BUG: spinlock recursion on CPU#0, init/1
> lock: ef5a1e0c, .magic: dead4ead, .owner: init/1, .owner_cpu: 0
> [<c0063290>] (unwind_backtrace+0x0/0xe4) from [<c024ce90>]
> (do_raw_spin_lock+0x48/0x158)
> [<c024ce90>] (do_raw_spin_lock+0x48/0x158) from [<c012f4e0>]
> (nameidata_dentry_drop_rcu+0x84/0x17c)
> [<c012f4e0>] (nameidata_dentry_drop_rcu+0x84/0x17c) from [<c012f608>]
> (d_revalidate+0x30/0x58)
> [<c012f608>] (d_revalidate+0x30/0x58) from [<c0132120>]
> (link_path_walk+0xb44/0xb64)
> [<c0132120>] (link_path_walk+0xb44/0xb64) from [<c0132338>]
> (do_path_lookup+0x44/0xcc)
> [<c0132338>] (do_path_lookup+0x44/0xcc) from [<c0132f08>]
> (do_filp_open+0xc8/0x56c)
> [<c0132f08>] (do_filp_open+0xc8/0x56c) from [<c0124828>]
> (do_sys_open+0x58/0xe4)
> [<c0124828>] (do_sys_open+0x58/0xe4) from [<c005c240>]
> (ret_fast_syscall+0x0/0x3c)
> BUG: spinlock lockup on CPU#0, init/1, ef5a1e0c
> [<c0063290>] (unwind_backtrace+0x0/0xe4) from [<c024cf84>]
> (do_raw_spin_lock+0x13c/0x158)
> [<c024cf84>] (do_raw_spin_lock+0x13c/0x158) from [<c012f4e0>]
> (nameidata_dentry_drop_rcu+0x84/0x17c)
> [<c012f4e0>] (nameidata_dentry_drop_rcu+0x84/0x17c) from [<c012f608>]
> (d_revalidate+0x30/0x58)
> [<c012f608>] (d_revalidate+0x30/0x58) from [<c0132120>]
> (link_path_walk+0xb44/0xb64)
> [<c0132120>] (link_path_walk+0xb44/0xb64) from [<c0132338>]
> (do_path_lookup+0x44/0xcc)
> [<c0132338>] (do_path_lookup+0x44/0xcc) from [<c0132f08>]
> (do_filp_open+0xc8/0x56c)
> [<c0132f08>] (do_filp_open+0xc8/0x56c) from [<c0124828>]
> (do_sys_open+0x58/0xe4)
> [<c0124828>] (do_sys_open+0x58/0xe4) from [<c005c240>]
> (ret_fast_syscall+0x0/0x3c)
> BUG: spinlock lockup on CPU#1, kworker/u:2/499, c05d3c80
> [<c0063290>] (unwind_backtrace+0x0/0xe4) from [<c024cf84>]
> (do_raw_spin_lock+0x13c/0x158)
> [<c024cf84>] (do_raw_spin_lock+0x13c/0x158) from [<c014afac>]
> (exit_fs+0x2c/0x84)
> [<c014afac>] (exit_fs+0x2c/0x84) from [<c0098274>] (do_exit+0x254/0x674)
> [<c0098274>] (do_exit+0x254/0x674) from [<c00b0944>] (kthread+0x88/0x8c)
> [<c00b0944>] (kthread+0x88/0x8c) from [<c005d490>]
> (kernel_thread_exit+0x0/0x8)
>
> --------------------------------------
>
> Regards,
> Santosh
> --
> 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/
--
Maciej Rutecki
http://www.maciek.unixy.pl
next prev parent reply other threads:[~2011-01-18 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 15:21 [REPORT] BUG: spinlock recursion on CPU#0, init/1 Santosh Shilimkar
2011-01-10 15:33 ` Peter Zijlstra
2011-01-18 16:19 ` Maciej Rutecki [this message]
2011-01-19 23:58 ` Nick Piggin
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=201101181719.05608.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.