Badness in as_completed_request at drivers/block/as-iosched.c:919

From: Oleg Drokin
Date: Wed Oct 22 2003 - 07:34:38 EST


Hello!

2.6.0-test8 (current bk), greeted me with "Badness in as_completed_request"
message on boot at smartd startup:
Oct 22 15:19:21 dol-guldur smartd[1225]: Device: /dev/sdb, is SMART capable. Adding to "monitor" list.
Oct 22 15:19:21 dol-guldur kernel: Badness in as_completed_request at drivers/block/as-iosched.c:919
Oct 22 15:19:21 dol-guldur kernel: Call Trace:
Oct 22 15:19:21 dol-guldur kernel: [<c01f7660>] as_completed_request+0x1d0/0x210
Oct 22 15:19:21 dol-guldur kernel: [<c01efe30>] elv_completed_request+0x20/0x30
Oct 22 15:19:21 dol-guldur kernel: [<c01f2246>] __blk_put_request+0x36/0xb0
Oct 22 15:19:21 dol-guldur smartd[1225]: Started monitoring 1 ATA and 2 SCSI devices
Oct 22 15:19:22 dol-guldur kernel: [<c01f3186>] end_that_request_last+0x56/0xe0
Oct 22 15:19:22 dol-guldur kernel: [<c0215a74>] scsi_end_request+0xb4/0xe0
Oct 22 15:19:22 dol-guldur kernel: [<c0215e28>] scsi_io_completion+0x1c8/0x4f0
Oct 22 15:19:22 dol-guldur kernel: [<c0236149>] sd_rw_intr+0x89/0x270
Oct 22 15:19:22 dol-guldur kernel: [<c0211024>] scsi_finish_command+0x84/0xf0
Oct 22 15:19:22 dol-guldur kernel: [<c0210e0f>] scsi_softirq+0xdf/0x230
Oct 22 15:19:22 dol-guldur kernel: [<c0124feb>] do_softirq+0xcb/0xd0
Oct 22 15:19:22 dol-guldur kernel: [<c010bc05>] do_IRQ+0x105/0x130
Oct 22 15:19:22 dol-guldur kernel: [<c0105000>] rest_init+0x0/0x60
Oct 22 15:19:22 dol-guldur kernel: [<c0109f20>] common_interrupt+0x18/0x20
Oct 22 15:19:22 dol-guldur kernel: [<c0107210>] default_idle+0x0/0x40
Oct 22 15:19:22 dol-guldur kernel: [<c0105000>] rest_init+0x0/0x60
Oct 22 15:19:22 dol-guldur kernel: [<c010723f>] default_idle+0x2f/0x40
Oct 22 15:19:22 dol-guldur kernel: [<c01072cb>] cpu_idle+0x3b/0x50
Oct 22 15:19:22 dol-guldur kernel: [<c0330947>] start_kernel+0x167/0x180
Oct 22 15:19:22 dol-guldur kernel: [<c0330510>] unknown_bootoption+0x0/0x110
Oct 22 15:19:22 dol-guldur kernel:
Oct 22 15:19:22 dol-guldur kernel: Badness in as_completed_request at drivers/block/as-iosched.c:919
Oct 22 15:19:22 dol-guldur kernel: Call Trace:
Oct 22 15:19:22 dol-guldur kernel: [<c01f7660>] as_completed_request+0x1d0/0x210
Oct 22 15:19:22 dol-guldur kernel: [<c01efe30>] elv_completed_request+0x20/0x30
Oct 22 15:19:22 dol-guldur kernel: [<c01f2246>] __blk_put_request+0x36/0xb0
Oct 22 15:19:22 dol-guldur smartd[1225]: Device: /dev/sdb, SMART Failure: DATA CHANNEL IMPENDING FAILURE DATA ERROR RATE TOO HIGH
Oct 22 15:19:22 dol-guldur kernel: [<c01f3186>] end_that_request_last+0x56/0xe0
Oct 22 15:19:22 dol-guldur kernel: [<c0215a74>] scsi_end_request+0xb4/0xe0
Oct 22 15:19:22 dol-guldur kernel: [<c0215e28>] scsi_io_completion+0x1c8/0x4f0
Oct 22 15:19:22 dol-guldur kernel: [<c0236149>] sd_rw_intr+0x89/0x270
Oct 22 15:19:22 dol-guldur kernel: [<c0211024>] scsi_finish_command+0x84/0xf0
Oct 22 15:19:22 dol-guldur kernel: [<c0210e0f>] scsi_softirq+0xdf/0x230
Oct 22 15:19:22 dol-guldur kernel: [<c0124feb>] do_softirq+0xcb/0xd0
Oct 22 15:19:22 dol-guldur kernel: [<c010bc05>] do_IRQ+0x105/0x130
Oct 22 15:19:22 dol-guldur kernel: [<c0105000>] rest_init+0x0/0x60
Oct 22 15:19:22 dol-guldur kernel: [<c0109f20>] common_interrupt+0x18/0x20
Oct 22 15:19:22 dol-guldur kernel: [<c0107210>] default_idle+0x0/0x40
Oct 22 15:19:22 dol-guldur kernel: [<c0105000>] rest_init+0x0/0x60
Oct 22 15:19:22 dol-guldur kernel: [<c010723f>] default_idle+0x2f/0x40
Oct 22 15:19:22 dol-guldur kernel: [<c01072cb>] cpu_idle+0x3b/0x50
Oct 22 15:19:22 dol-guldur kernel: [<c0330947>] start_kernel+0x167/0x180
Oct 22 15:19:22 dol-guldur kernel: [<c0330510>] unknown_bootoption+0x0/0x110
Oct 22 15:19:22 dol-guldur kernel:
Oct 22 15:19:23 dol-guldur smartd: smartd startup succeeded

/dev/sdb is on aic7xxx-compatible scsi controller.

2.6.0-test7 have not shown anything like this.
Hope that helps

Bye,
Oleg
-
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/