From: Pekka Pietikainen <pp@ee.oulu.fi>
To: linux-kernel@vger.kernel.org
Subject: 2.6.23-rc8-git2 possible recursive locking when running screen
Date: Wed, 3 Oct 2007 12:24:08 +0300 [thread overview]
Message-ID: <20071003092408.GA17356@ee.oulu.fi> (raw)
Seen this a few times lately on a machine running rawhide when running
screen (and doing "something", it's not automatic. And box works just fine).
I think I saw this a few weeks back, so it's not a new regression.
=============================================
[ INFO: possible recursive locking detected ]
2.6.23-0.211.rc8.git2.fc8 #1
---------------------------------------------
screen/32227 is trying to acquire lock:
(&q->lock){++..}, at: [<c0426703>] __wake_up+0x15/0x42
but task is already holding lock:
(&q->lock){++..}, at: [<c0426703>] __wake_up+0x15/0x42
other info that might help us debug this:
2 locks held by screen/32227:
#0: (&tty->atomic_read_lock){--..}, at: [<c0554ca2>] read_chan+0x1a1/0x5af
#1: (&q->lock){++..}, at: [<c0426703>] __wake_up+0x15/0x42
stack backtrace:
[<c0406463>] show_trace_log_lvl+0x1a/0x2f
[<c0406e4d>] show_trace+0x12/0x14
[<c0406e65>] dump_stack+0x16/0x18
[<c0449c3a>] __lock_acquire+0x189/0xc67
[<c044ab92>] lock_acquire+0x7b/0x9e
[<c06334fa>] _spin_lock_irqsave+0x4a/0x77
[<c0426703>] __wake_up+0x15/0x42
[<c04aece2>] ep_poll_safewake+0x86/0xa8
[<c04af969>] ep_poll_callback+0x9f/0xaa
[<c042483e>] __wake_up_common+0x32/0x55
[<c042671f>] __wake_up+0x31/0x42
[<c054f864>] tty_wakeup+0x4f/0x54
[<c0555e9b>] pty_unthrottle+0x15/0x21
[<c055301b>] check_unthrottle+0x2e/0x30
[<c0554fad>] read_chan+0x4ac/0x5af
[<c0551c99>] tty_read+0x66/0xac
[<c0489fee>] vfs_read+0xad/0x167
[<c048a482>] sys_read+0x3d/0x61
[<c040522e>] syscall_call+0x7/0xb
=======================
next reply other threads:[~2007-10-03 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 9:24 Pekka Pietikainen [this message]
2007-10-04 15:39 ` 2.6.23-rc8-git2 possible recursive locking when running screen Rafael J. Wysocki
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=20071003092408.GA17356@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--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 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.