From: Andrew Morton <akpm@osdl.org>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: linux-kernel@vger.kernel.org, linux-pcmcia@lists.infradead.org
Subject: Re: 2.6.18-rc4-mm2
Date: Sun, 20 Aug 2006 15:36:16 -0700 [thread overview]
Message-ID: <20060820153616.74e698df.akpm@osdl.org> (raw)
In-Reply-To: <200608202327.44932.m.kozlowski@tuxland.pl>
On Sun, 20 Aug 2006 23:27:44 +0200
Mariusz Kozlowski <m.kozlowski@tuxland.pl> wrote:
> Hello,
>
> I get this on my laptop when doing reboot or shutdown. Config is attached.
>
> =============================================
> [ INFO: possible recursive locking detected ]
> ---------------------------------------------
> cardmgr/4736 is trying to acquire lock:
> (pcmcia_socket_list_rwsem){----}, at: [<de86de50>] adjust_memory+0x92/0xe6
> [rsrc_nonstatic]
>
> but task is already holding lock:
> (pcmcia_socket_list_rwsem){----}, at: [<de8653bf>]
> pcmcia_adjust_resource_info+0x1c/0xfe [pcmcia_core]
>
> other info that might help us debug this:
> 2 locks held by cardmgr/4736:
> #0: (pcmcia_socket_list_rwsem){----}, at: [<de8653bf>]
> pcmcia_adjust_resource_info+0x1c/0xfe [pcmcia_core]
> #1: (rsrc_mutex){--..}, at: [<c03d7e67>] mutex_lock+0x1c/0x1f
>
> stack backtrace:
> [<c010366e>] show_trace_log_lvl+0x16b/0x17e
> [<c0103693>] show_trace+0x12/0x16
> [<c0103792>] dump_stack+0x19/0x1d
> [<c012d0e0>] print_deadlock_bug+0xbe/0xc3
> [<c012d141>] check_deadlock+0x5c/0x6c
> [<c012e87e>] __lock_acquire+0x31d/0x92c
> [<c012f550>] lock_acquire+0x6f/0x8c
> [<c012b8a8>] down_read+0x3c/0x4d
> [<de86de50>] adjust_memory+0x92/0xe6 [rsrc_nonstatic]
> [<de86dfb3>] nonstatic_adjust_resource_info+0x55/0x57 [rsrc_nonstatic]
> [<de86546b>] pcmcia_adjust_resource_info+0xc8/0xfe [pcmcia_core]
> [<ded427a2>] ds_ioctl+0x33e/0x5ec [pcmcia]
> [<c0173748>] do_ioctl+0x5c/0x79
> [<c01738c8>] vfs_ioctl+0x55/0x196
> [<c0173a42>] sys_ioctl+0x39/0x5b
> [<c010300f>] syscall_call+0x7/0xb
> [<b7f2c584>] 0xb7f2c584
> [<c0103693>] show_trace+0x12/0x16
> [<c0103792>] dump_stack+0x19/0x1d
> [<c012d0e0>] print_deadlock_bug+0xbe/0xc3
> [<c012d141>] check_deadlock+0x5c/0x6c
> [<c012e87e>] __lock_acquire+0x31d/0x92c
> [<c012f550>] lock_acquire+0x6f/0x8c
> [<c012b8a8>] down_read+0x3c/0x4d
> [<de86de50>] adjust_memory+0x92/0xe6 [rsrc_nonstatic]
> [<de86dfb3>] nonstatic_adjust_resource_info+0x55/0x57 [rsrc_nonstatic]
> [<de86546b>] pcmcia_adjust_resource_info+0xc8/0xfe [pcmcia_core]
> [<ded427a2>] ds_ioctl+0x33e/0x5ec [pcmcia]
> [<c0173748>] do_ioctl+0x5c/0x79
> [<c01738c8>] vfs_ioctl+0x55/0x196
> [<c0173a42>] sys_ioctl+0x39/0x5b
> [<c010300f>] syscall_call+0x7/0xb
yup, thanks. recursive down_read() is deadlockable - an intervening
down_write() from another task wil cause everything to jam up.
next prev parent reply other threads:[~2006-08-20 22:39 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 5:00 2.6.18-rc4-mm2 Andrew Morton
2006-08-20 7:12 ` 2.6.18-rc4-mm2 Reuben Farrelly
2006-08-20 7:23 ` 2.6.18-rc4-mm2 Andrew Morton
2006-08-20 7:44 ` 2.6.18-rc4-mm2 thunder7
2006-08-20 8:03 ` 2.6.18-rc4-mm2 Andrew Morton
2006-08-20 13:22 ` 2.6.18-rc4-mm2 Michal Piotrowski
2006-08-20 13:24 ` 2.6.18-rc4-mm2 Maciej Rutecki
2006-08-20 15:10 ` 2.6.18-rc4-mm2: AFS_FSCACHE=n compile error Adrian Bunk
2006-08-20 17:56 ` 2.6.18-rc4-mm2 Andrew Morton
[not found] ` <6bffcb0e0608200634r5c836053r8fa5cea7b9fdb4cb@mail.gmail.com>
2006-08-21 8:11 ` 2.6.18-rc4-mm2 Maciej Rutecki
2006-08-20 13:30 ` 2.6.18-rc4-mm2 Michal Piotrowski
2006-08-20 18:07 ` 2.6.18-rc4-mm2 Alan Cox
2006-08-21 7:59 ` 2.6.18-rc4-mm2 Jens Axboe
2006-08-20 16:04 ` 2.6.18-rc4-mm2 Michal Piotrowski
2006-08-20 16:45 ` 2.6.18-rc4-mm2 Michal Piotrowski
2006-08-20 16:09 ` [-mm patch] CRYPTO_DEV_PADLOCK_AES must select CRYPTO_BLKCIPHER Adrian Bunk
2006-08-20 23:04 ` Herbert Xu
2006-08-20 23:51 ` Andrew Morton
2006-08-20 17:47 ` [-mm patch] make kernel/rcutorture.c:rcu_bh_torture_synchronize() static Adrian Bunk
2006-08-20 21:27 ` 2.6.18-rc4-mm2 Mariusz Kozlowski
2006-08-20 22:36 ` Andrew Morton [this message]
2006-08-21 1:59 ` 2.6.18-rc4-mm2: tickadj removal breaks 6 architectures Adrian Bunk
2006-08-21 2:08 ` 2.6.18-rc4-mm2: m68k nsproxy compile breakage Adrian Bunk
2006-08-21 14:46 ` Serge E. Hallyn
2006-08-21 16:51 ` Adrian Bunk
2006-08-21 8:12 ` 2.6.18-rc4-mm2 Gregoire Favre
2006-08-21 11:32 ` 2.6.18-rc4-mm2 Frederik Deweerdt
2006-08-21 19:21 ` 2.6.18-rc4-mm2 Gregoire Favre
2006-08-21 9:20 ` 2.6.18-rc4-mm2 Maciej Rutecki
2006-08-21 13:44 ` 2.6.18-rc4-mm2 Andrew Morton
2006-08-21 20:20 ` 2.6.18-rc4-mm2 Maciej Rutecki
2006-08-21 23:22 ` 2.6.18-rc4-mm2 Len Brown
2006-08-22 16:10 ` [Re: 2.6.18-rc4-mm2] standby error Maciej Rutecki
2006-08-22 18:59 ` 2.6.18-rc4-mm2 Grant Wilson
2006-08-21 22:54 ` 2.6.18-rc4-mm2 Len Brown
2006-08-21 21:21 ` 2.6.18-rc4-mm2: x86_64 compile error Adrian Bunk
2006-08-21 21:24 ` Andi Kleen
2006-08-22 8:11 ` Jan Beulich
2006-08-22 11:50 ` Adrian Bunk
2006-08-24 19:54 ` 2.6.18-rc4-mm2: ptkcdvd mapping may cause possible recursive locking Laurent Riffard
2006-08-26 15:28 ` [-mm patch] drivers/net/pcmcia/xirc2ps_cs.c: remove unused label Adrian Bunk
2006-08-26 15:28 ` [-mm patch] fix drivers/hwmon/hdaps.c:hdaps_check_ec() function declaration Adrian Bunk
2006-08-26 19:09 ` Shem Multinymous
2006-08-22 19:07 2.6.18-rc4-mm2 Moore, Robert
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=20060820153616.74e698df.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=m.kozlowski@tuxland.pl \
/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
Powered by JetHome