From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: 2.6.18-git21, possible recursive locking in kseriod ends up in DWARF2 unwinder stuck
Date: Wed, 4 Oct 2006 23:17:04 +0200 [thread overview]
Message-ID: <5a4c581d0610041417y113bb92cs10971308180980e5@mail.gmail.com> (raw)
Non-fatal (box is still alive and apparently well) on boot,
FC5-uptodate on a Dell Latitude C640. From the dmesg ring:
[ 8.680000] =============================================
[ 8.680000] [ INFO: possible recursive locking detected ]
[ 8.680000] 2.6.18-git21 #1
[ 8.680000] ---------------------------------------------
[ 8.680000] kseriod/163 is trying to acquire lock:
[ 8.680000] (&ps2dev->cmd_mutex/1){--..}, at: [<c03198c3>]
ps2_command+0x89/0x358
[ 8.680000]
[ 8.680000] but task is already holding lock:
[ 8.680000] (&ps2dev->cmd_mutex/1){--..}, at: [<c03198c3>]
ps2_command+0x89/0x358
[ 8.680000]
[ 8.680000] other info that might help us debug this:
[ 8.680000] 4 locks held by kseriod/163:
[ 8.680000] #0: (serio_mutex){--..}, at: [<c0317a5f>]
serio_thread+0x11/0x2ca
[ 8.680000] #1: (&serio->drv_mutex){--..}, at: [<c0316f2c>]
serio_connect_driver+0x17/0x32
[ 8.680000] #2: (psmouse_mutex){--..}, at: [<c0320a90>]
psmouse_connect+0x11/0x24a
[ 8.680000] #3: (&ps2dev->cmd_mutex/1){--..}, at: [<c03198c3>]
ps2_command+0x89/0x358
[ 8.680000]
[ 8.680000] stack backtrace:
[ 8.680000] [<c010339c>] show_trace_log_lvl+0x24/0x39
[ 8.680000] [<c0103b54>] dump_stack+0x24/0x28
[ 8.680000] [<c0129c8f>] __lock_acquire+0x128/0xa1c
[ 8.680000] [<c012a897>] lock_acquire+0x6a/0x84
[ 8.680000] [<c03d14f5>] mutex_lock_nested+0xd8/0x25b
[ 8.680000] [<c03198c3>] ps2_command+0x89/0x358
[ 8.680000] [<c031fed9>] psmouse_sliced_command+0x2c/0x74
[ 8.680000] [<c0323be0>] synaptics_pt_write+0x2a/0x5a
[ 8.680000] [<c031978e>] ps2_sendbyte+0x51/0xfd
[ 8.680000] [<c031994f>] ps2_command+0x115/0x358
[ 8.680000] [<c031fa59>] psmouse_probe+0x24/0x7d
[ 8.680000] [<c0320b8d>] psmouse_connect+0x10e/0x24a
[ 8.680000] [<c0316f36>] serio_connect_driver+0x21/0x32
[ 8.680000] [<c02e0615>] really_probe+0x3c/0xc3
[ 8.680000] [<c02dfaea>] bus_for_each_drv+0x52/0x84
[ 8.680000] [<c02e07a9>] device_attach+0x5e/0x72
[ 8.680000] [<c02dfa6c>] bus_attach_device+0x24/0x50
[ 8.680000] [<c02ded5c>] device_add+0x37d/0x4bf
[ 8.680000] [<c0317b29>] serio_thread+0xdb/0x2ca
[ 8.680000] [<c0123d19>] kthread+0xc5/0xf4
[ 8.680000] [<c0102edb>] kernel_thread_helper+0x7/0x10
[ 8.680000] DWARF2 unwinder stuck at kernel_thread_helper+0x7/0x10
[ 8.680000]
[ 8.680000] Leftover inexact backtrace:
[ 8.680000]
[ 8.680000] =======================
--alessandro
"Well a man has two reasons for things that he does
the first one is pride and the second one is love
all understandings must come by this way"
(Husker Du, 'She Floated Away')
next reply other threads:[~2006-10-04 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 21:17 Alessandro Suardi [this message]
2006-10-04 21:25 ` Jiri Kosina
2006-10-05 20:34 ` Dmitry Torokhov
2006-10-06 9:22 ` Jiri Kosina
2006-10-06 11:38 ` Peter Zijlstra
2006-10-06 13:29 ` Dmitry Torokhov
2006-10-13 6:12 ` Ingo Molnar
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=5a4c581d0610041417y113bb92cs10971308180980e5@mail.gmail.com \
--to=alessandro.suardi@gmail.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
all inboxes | Powered by JetHome®