Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932243AbWBFR0x (ORCPT ); Mon, 6 Feb 2006 12:26:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932246AbWBFR0x (ORCPT ); Mon, 6 Feb 2006 12:26:53 -0500 Received: from fmr23.intel.com ([143.183.121.15]:44511 "EHLO scsfmr003.sc.intel.com") by vger.kernel.org with ESMTP id S932243AbWBFR0x (ORCPT ); Mon, 6 Feb 2006 12:26:53 -0500 Date: Mon, 6 Feb 2006 09:17:26 -0800 From: Benjamin LaHaise To: linux-kernel@vger.kernel.org Subject: Badness in blk_do_ordered Message-ID: <20060206171726.GA16324@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1409 Lines: 27 On a machine using ICH6 SATA and nbd, I just got this from the current git HEAD (e3f749c4af69c4344d89f11e2293e3790eb4eaca): nbd: registered device at major 43 Badness in blk_do_ordered at block/ll_rw_blk.c:550 Call Trace: {blk_do_ordered+753} {elv_next_request+36} {scsi_request_fn+120} {blk_run_queue+48} {bar_end_io+0} {scsi_next_command+46} {scsi_end_request+192} {scsi_io_completion+452} {sd_rw_intr+544} {scsi_device_unbusy+85} {scsi_softirq_done+212} {blk_done_softirq+123} {__do_softirq+80} {call_softirq+30} {do_softirq+47} {do_IRQ+62} {mwait_idle+0} {ret_from_intr+0} {mwait_idle+54} {cpu_idle+98} {start_kernel+434} {_sinittext+646} Anyone else seeing this? -ben - 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/