Control-C under High I/O Crashes Box, 2.6.16.20 or 2.6.17

[Justin Piszcz <jpiszcz@lucidpixels.com>]

This is very rare, but when it happens it is very irritating.

It has happened on an old Dell Optiplex GX110 (1.0GHZ) and a new 3.4GHZ 
box with a Promise/Maxtor ATA/133 PCI controller.

When more than 1 heavy I/O (cp/mv/etc) process is running and you hit 
control-c on one of the heavy processes, the box locks up and this appears 
in the logs:

Jun 19 06:20:23 p34 kernel: [4295114.329000] hdk: dma_timer_expiry: dma 
status == 0x20
Jun 19 06:20:23 p34 kernel: [4295114.329000] hdk: DMA timeout retry
Jun 19 06:20:23 p34 kernel: [4295114.329000] PDC202XX: Secondary channel 
reset.
Jun 19 06:20:23 p34 kernel: [4295114.329000] hdk: status error: 
status=0x58 { DriveReady SeekComplete DataRequest }
Jun 19 06:20:23 p34 kernel: [4295114.329000] ide: failed opcode was: 
unknown
Jun 19 06:20:23 p34 kernel: [4295114.584000] hdk: status timeout: 
status=0xd0 { Busy }
Jun 19 06:20:23 p34 kernel: [4295114.584000] ide: failed opcode was: 
unknown
Jun 19 06:20:23 p34 kernel: [4295114.584000] PDC202XX: Secondary channel 
reset.
Jun 19 06:20:24 p34 kernel: [4295114.684000] ide5: reset: success

Just thought I'd mention it, maybe other people have also experienced this 
as well.

Justin.

-
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/