From: Sasha Levin <sasha.levin@oracle.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiri Slaby <jslaby@suse.cz>
Subject: tty ldisc lockups in linux-next
Date: Tue, 25 Sep 2012 10:49:12 +0200 [thread overview]
Message-ID: <50617008.5000207@oracle.com> (raw)
Hi all,
While fuzzing with trinity in a KVM tools guest running linux-next kernel, I keep hitting the following lockup:
[ 842.780242] INFO: task init:1 blocked for more than 120 seconds.
[ 842.780732] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 842.781559] init D ffff88000d5b0000 3344 1 0 0x00000002
[ 842.783226] ffff88000d5adc28 0000000000000082 ffff88000d5adbe8 ffffffff81150ac5
[ 842.784714] ffff88000d5adfd8 ffff88000d5adfd8 ffff88000d5adfd8 ffff88000d5adfd8
[ 842.785737] ffffffff84e2e420 ffff88000d5b0000 ffff88000d5b08f0 7fffffffffffffff
[ 842.786764] Call Trace:
[ 842.787102] [<ffffffff81150ac5>] ? sched_clock_local+0x25/0xa0
[ 842.787858] [<ffffffff83a0be45>] schedule+0x55/0x60
[ 842.788511] [<ffffffff83a09dd5>] schedule_timeout+0x45/0x360
[ 842.789251] [<ffffffff83a0d54d>] ? _raw_spin_unlock_irqrestore+0x5d/0xb0
[ 842.790149] [<ffffffff8117b13d>] ? trace_hardirqs_on+0xd/0x10
[ 842.790594] [<ffffffff83a0d574>] ? _raw_spin_unlock_irqrestore+0x84/0xb0
[ 842.791096] [<ffffffff81137af7>] ? prepare_to_wait+0x77/0x90
[ 842.791535] [<ffffffff81b9b2c6>] tty_ldisc_wait_idle.isra.7+0x76/0xb0
[ 842.792016] [<ffffffff81137cd0>] ? abort_exclusive_wait+0xb0/0xb0
[ 842.792490] [<ffffffff81b9c03b>] tty_ldisc_hangup+0x1cb/0x320
[ 842.792924] [<ffffffff81b933a2>] ? __tty_hangup+0x122/0x430
[ 842.793364] [<ffffffff81b933aa>] __tty_hangup+0x12a/0x430
[ 842.794077] [<ffffffff83a0d574>] ? _raw_spin_unlock_irqrestore+0x84/0xb0
[ 842.794942] [<ffffffff81b955cc>] disassociate_ctty+0x6c/0x230
[ 842.795693] [<ffffffff8110e7e8>] do_exit+0x3d8/0xa90
[ 842.796361] [<ffffffff83a0e4d9>] ? retint_swapgs+0x13/0x1b
[ 842.797079] [<ffffffff8110ef64>] do_group_exit+0x84/0xd0
[ 842.797818] [<ffffffff8110efc2>] sys_exit_group+0x12/0x20
[ 842.798524] [<ffffffff83a0edcd>] system_call_fastpath+0x1a/0x1f
[ 842.799294] 1 lock held by init/1:
[ 842.799734] #0: (&tty->ldisc_mutex){+.+.+.}, at: [<ffffffff81b9bf92>] tty_ldisc_hangup+0x122/0x320
Thanks,
Sasha
next reply other threads:[~2012-09-25 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 8:49 Sasha Levin [this message]
2012-09-25 8:52 ` tty ldisc lockups in linux-next Jiri Slaby
2012-09-25 8:55 ` Sasha Levin
2012-09-25 8:56 ` Jiri Slaby
2012-09-25 9:47 ` Sasha Levin
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=50617008.5000207@oracle.com \
--to=sasha.levin@oracle.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--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.