Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757955AbZC1OMx (ORCPT ); Sat, 28 Mar 2009 10:12:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754329AbZC1OMn (ORCPT ); Sat, 28 Mar 2009 10:12:43 -0400 Received: from mailbackup.inode.at ([213.229.60.24]:59590 "EHLO mailbackup.inode.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753917AbZC1OMm (ORCPT ); Sat, 28 Mar 2009 10:12:42 -0400 Date: Sat, 28 Mar 2009 15:11:25 +0100 From: Matthias Reichl To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , FUJITA Tomonori Subject: Re: [Bug #12612] hard lockup when interrupting cdda2wav Message-ID: <20090328141125.GA4061@horus.com> Mail-Followup-To: Matthias Reichl , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , FUJITA Tomonori References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4543 Lines: 113 On Sat, Mar 21, 2009 at 06:07:27PM +0100, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of regressions introduced between 2.6.27 and 2.6.28. > > The following bug entry is on the current list of known regressions > introduced between 2.6.27 and 2.6.28. Please verify if it still should > be listed and let me know (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12612 > Subject : hard lockup when interrupting cdda2wav > Submitter : Matthias Reichl > Date : 2009-01-28 16:41 (53 days old) > References : http://marc.info/?l=linux-kernel&m=123316111415677&w=4 > Handled-By : FUJITA Tomonori > Patch : http://marc.info/?l=linux-scsi&m=123371501613019&w=2 The bug is still present in 2.6.28.9 and in 2.6.29 (see backtraces below). so long, Hias ============================================= [ INFO: possible recursive locking detected ] 2.6.28.9-dbg #1 --------------------------------------------- swapper/0 is trying to acquire lock: (&q->__queue_lock){.+..}, at: [] blk_put_request+0x25/0x60 but task is already holding lock: (&q->__queue_lock){.+..}, at: [] blk_end_io+0x5a/0xa0 other info that might help us debug this: 1 lock held by swapper/0: #0: (&q->__queue_lock){.+..}, at: [] blk_end_io+0x5a/0xa0 stack backtrace: Pid: 0, comm: swapper Not tainted 2.6.28.9-dbg #1 Call Trace: [] __lock_acquire+0x1797/0x1930 [] lock_acquire+0x9a/0xe0 [] blk_put_request+0x25/0x60 [] _spin_lock_irqsave+0x43/0x90 [] blk_put_request+0x25/0x60 [] blk_put_request+0x25/0x60 [] sg_finish_rem_req+0xa4/0x100 [] sg_rq_end_io+0x278/0x2e0 [] end_that_request_last+0x61/0x260 [] blk_end_io+0x68/0xa0 [] scsi_end_request+0x41/0xd0 [] scsi_io_completion+0x130/0x470 [] blk_done_softirq+0x75/0x90 [] __do_softirq+0x9b/0x180 [] native_sched_clock+0x13/0x70 [] call_softirq+0x1c/0x30 [] do_softirq+0x65/0xa0 [] irq_exit+0xa5/0xb0 [] do_IRQ+0x107/0x1d0 [] ret_from_intr+0x0/0xf [] mwait_idle+0x56/0x60 [] mwait_idle+0x4d/0x60 [] cpu_idle+0x63/0xc0 ============================================= [ INFO: possible recursive locking detected ] 2.6.29-dbg #1 --------------------------------------------- swapper/0 is trying to acquire lock: (&q->__queue_lock){.+..}, at: [] blk_put_request+0x25/0x60 but task is already holding lock: (&q->__queue_lock){.+..}, at: [] blk_end_io+0x5a/0xa0 other info that might help us debug this: 1 lock held by swapper/0: #0: (&q->__queue_lock){.+..}, at: [] blk_end_io+0x5a/0xa0 stack backtrace: Pid: 0, comm: swapper Not tainted 2.6.29-dbg #1 Call Trace: [] __lock_acquire+0xfda/0x1b70 [] error_exit+0x29/0xb0 [] sg_rq_end_io+0x0/0x2e0 [] bad_to_user+0xac/0x5c4 [] lock_acquire+0x9a/0xe0 [] blk_put_request+0x25/0x60 [] _spin_lock_irqsave+0x43/0x90 [] blk_put_request+0x25/0x60 [] blk_put_request+0x25/0x60 [] sg_finish_rem_req+0xa4/0x100 [] sg_rq_end_io+0x278/0x2e0 [] end_that_request_last+0x5a/0x280 [] blk_end_io+0x68/0xa0 [] scsi_io_completion+0x146/0x520 [] blk_done_softirq+0x75/0x90 [] __do_softirq+0x9b/0x180 [] call_softirq+0x1c/0x30 [] do_softirq+0x65/0xb0 [] irq_exit+0x85/0xa0 [] do_IRQ+0xb7/0x1b0 [] ret_from_intr+0x0/0xf [] mwait_idle+0x86/0x90 [] mwait_idle+0x7d/0x90 [] cpu_idle+0x67/0xc0 -- 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/