Badness in as_completed_request

From: Aaron Lehmann
Date: Wed Nov 05 2003 - 04:04:16 EST


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:
[<c021675d>] as_completed_request+0x1ad/0x1e0
[<c020f84f>] elv_completed_request+0x1f/0x30
[<c0211a4c>] __blk_put_request+0x3c/0xc0
[<c0212902>] end_that_request_last+0x52/0xa0
[<c0238b72>] scsi_end_request+0xb2/0xe0
[<c0238f0b>] scsi_io_completion+0x1bb/0x470
[<c02437ea>] sd_rw_intr+0x5a/0x1e0
[<c02351db>] scsi_finish_command+0x7b/0xc0
[<c011feeb>] update_wall_time+0xb/0x40
[<c02350ee>] scsi_softirq+0xae/0xe0
[<c011c250>] do_softirq+0x90/0xa0
[<c010ab05>] do_IRQ+0xc5/0xe0
[<c0105000>] _stext+0x0/0x30
[<c01090a8>] common_interrupt+0x18/0x20
[<c0105000>] _stext+0x0/0x30
[<c0106e13>] default_idle+0x23/0x30
[<c0106e7c>] cpu_idle+0x2c/0x40
[<c035c69f>] start_kernel+0x13f/0x150
[<c035c430>] unknown_bootoption+0x0/0x100

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/