From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759240AbZBEQLV (ORCPT ); Thu, 5 Feb 2009 11:11:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754234AbZBEQLF (ORCPT ); Thu, 5 Feb 2009 11:11:05 -0500 Received: from ogre.sisk.pl ([217.79.144.158]:53513 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754203AbZBEQLC (ORCPT ); Thu, 5 Feb 2009 11:11:02 -0500 From: "Rafael J. Wysocki" To: Matthias Reichl Subject: Re: [Bug #12612] hard lockup when interrupting cdda2wav Date: Thu, 5 Feb 2009 17:10:43 +0100 User-Agent: KMail/1.11.0 (Linux/2.6.29-rc2-tst; KDE/4.2.0; x86_64; ; ) Cc: Linux Kernel Mailing List , Kernel Testers List , FUJITA Tomonori References: <20090205131644.GA5731@horus.com> In-Reply-To: <20090205131644.GA5731@horus.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902051710.44551.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 05 February 2009, Matthias Reichl wrote: > On Wed, Feb 04, 2009 at 11:58:51AM +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 (8 days old) > > References : http://marc.info/?l=linux-kernel&m=123316111415677&w=4 > > Handled-By : FUJITA Tomonori > > This bug is still present in 2.6.28.3. > > ============================================= > [ INFO: possible recursive locking detected ] > 2.6.28.3-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.3-dbg #1 > Call Trace: > [] __lock_acquire+0x1797/0x1930 > [] error_exit+0x29/0xa9 > [] sg_rq_end_io+0x0/0x2e0 > [] 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 Thanks for the update. Rafael