Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262758AbTKEJAu (ORCPT ); Wed, 5 Nov 2003 04:00:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262760AbTKEJAt (ORCPT ); Wed, 5 Nov 2003 04:00:49 -0500 Received: from vitelus.com ([64.81.243.207]:53150 "EHLO vitelus.com") by vger.kernel.org with ESMTP id S262758AbTKEJAs (ORCPT ); Wed, 5 Nov 2003 04:00:48 -0500 Date: Wed, 5 Nov 2003 00:58:17 -0800 From: Aaron Lehmann To: linux-kernel@vger.kernel.org Subject: Badness in as_completed_request Message-ID: <20031105085817.GH21853@vitelus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1467 Lines: 34 I've been seeing this about every day for the past month or so, while tracking 2.6.0-test*. Usually by the time I feel like reporting it I'm a few revisions behind and decide to upgrade before complaining about it. Now I'm running -test9 and it still happens. This happens every few day or so under normal load and every few minutes under high I/O load. I'm running an x86 system with a 3ware RAID5: Badness in as_completed_request at drivers/block/as-iosched.c:919 Call Trace: [] as_completed_request+0x1ad/0x1e0 [] elv_completed_request+0x1f/0x30 [] __blk_put_request+0x3c/0xc0 [] end_that_request_last+0x52/0xa0 [] scsi_end_request+0xb2/0xe0 [] scsi_io_completion+0x1bb/0x470 [] sd_rw_intr+0x5a/0x1e0 [] scsi_finish_command+0x7b/0xc0 [] update_wall_time+0xb/0x40 [] scsi_softirq+0xae/0xe0 [] do_softirq+0x90/0xa0 [] do_IRQ+0xc5/0xe0 [] _stext+0x0/0x30 [] common_interrupt+0x18/0x20 [] _stext+0x0/0x30 [] default_idle+0x23/0x30 [] cpu_idle+0x2c/0x40 [] start_kernel+0x13f/0x150 [] unknown_bootoption+0x0/0x100 - 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/