disk hangs with asus boards

[Ralph Blach]

every few days I have either my root file system hang or my disk array hang.

I am running a asus p5n_d

my root file system is on a single 500gb disk attached to the asus mother board.

[0:0:0:0]    disk    ATA      WDC WD5000AADS-0 01.0  /dev/sda <------root
[4:0:0:0]    cd/dvd  ATAPI    iHAS324   Y      BL1W  /dev/sr0
[9:0:0:0]    disk    AMCC     9650SE-4LP DISK  4.10  /dev/sdb <======data

the cpu is
model name	: Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz

All the disk hangs look like this, but I dont have one from the root file system because the root get remounted Read Only.

Since I See hangs across both disk, so I do not think it is the 3 ware controller or disk.



Apr 16 00:01:29 chipblach kernel: 3w-9xxx: scsi9: AEN: INFO (0x04:0x0029): Verify started:unit=0.
Apr 16 03:00:51 chipblach kernel: 3w-9xxx: scsi9: AEN: INFO (0x04:0x002B): Verify completed:unit=0.
Apr 16 03:07:10 chipblach pulseaudio[2430]: ratelimit.c: 88 events suppressed
Apr 16 03:19:12 chipblach kernel: sd 9:0:0:0: WARNING: (0x06:0x002C): Command (0x2a) timed out, resetting card.
Apr 16 03:19:40 chipblach kernel: 3w-9xxx: scsi9: WARNING: (0x06:0x0037): Character ioctl (0x108) timed out, resetting card.
Apr 16 03:20:18 chipblach kernel: sd 9:0:0:0: WARNING: (0x06:0x002C): Command (0x0) timed out, resetting card.
Apr 16 03:21:13 chipblach kernel: 3w-9xxx: scsi9: WARNING: (0x06:0x0037): Character ioctl (0x108) timed out, resetting card.
Apr 16 03:21:35 chipblach kernel: INFO: task jbd2/dm-2-8:1220 blocked for more than 120 seconds.
Apr 16 03:21:35 chipblach kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 16 03:21:35 chipblach kernel: jbd2/dm-2-8   D 0000000000000001     0  1220      2 0x00000080
Apr 16 03:21:35 chipblach kernel: ffff880127d51b20 0000000000000046 ffff880127d51a90 ffffffff81010296
Apr 16 03:21:35 chipblach kernel: ffff880127d51fd8 ffff880127e1aee0 00000000000153c0 ffff880127d51fd8
Apr 16 03:21:35 chipblach kernel: 00000000000153c0 00000000000153c0 00000000000153c0 00000000000153c0
Apr 16 03:21:35 chipblach kernel: Call Trace:
Apr 16 03:21:35 chipblach kernel: [<ffffffff81010296>] ? read_tsc+0x9/0x1b
Apr 16 03:21:35 chipblach kernel: [<ffffffff810caf3e>] ? sync_page+0x0/0x4a
Apr 16 03:21:35 chipblach kernel: [<ffffffff8144be26>] io_schedule+0x73/0xb5
Apr 16 03:21:35 chipblach kernel: [<ffffffff810caf84>] sync_page+0x46/0x4a
Apr 16 03:21:35 chipblach kernel: [<ffffffff8144c3b7>] __wait_on_bit+0x48/0x7b
Apr 16 03:21:35 chipblach kernel: [<ffffffff810cb0f5>] wait_on_page_bit+0x72/0x79
Apr 16 03:21:35 chipblach kernel: [<ffffffff81066298>] ? wake_bit_function+0x0/0x33
Apr 16 03:21:35 chipblach kernel: [<ffffffff810d35d5>] ? pagevec_lookup_tag+0x25/0x2e
Apr 16 03:21:35 chipblach kernel: [<ffffffff810cb3ae>] filemap_fdatawait_range+0xa4/0x178
Apr 16 03:21:35 chipblach kernel: [<ffffffff811fac55>] ? submit_bio+0xde/0xfb
Apr 16 03:21:35 chipblach kernel: [<ffffffff810cb4a3>] filemap_fdatawait+0x21/0x23
Apr 16 03:21:35 chipblach kernel: [<ffffffff811b2515>] jbd2_journal_commit_transaction+0x879/0x11b4
Apr 16 03:21:35 chipblach kernel: [<ffffffff81059898>] ? try_to_del_timer_sync+0x7b/0x89
Apr 16 03:21:35 chipblach kernel: [<ffffffff811b7382>] kjournald2+0xc6/0x203
Apr 16 03:21:35 chipblach kernel: [<ffffffff8106625f>] ? autoremove_wake_function+0x0/0x39
Apr 16 03:21:35 chipblach kernel: [<ffffffff811b72bc>] ? kjournald2+0x0/0x203
Apr 16 03:21:35 chipblach kernel: [<ffffffff81065de5>] kthread+0x7f/0x87
Apr 16 03:21:35 chipblach kernel: [<ffffffff8100aa64>] kernel_thread_helper+0x4/0x10
Apr 16 03:21:35 chipblach kernel: [<ffffffff81065d66>] ? kthread+0x0/0x87
Apr 16 03:21:35 chipblach kernel: [<ffffffff8100aa60>] ? kernel_thread_helper+0x0/0x10
Apr 16 03:21:42 chipblach kernel: sd 9:0:0:0: Device offlined - not ready after error recovery
Apr 16 03:21:42 chipblach kernel: sd 9:0:0:0: rejecting I/O to offline device
Apr 16 03:21:42 chipblach kernel: sd 9:0:0:0: [sdb] Unhandled error code
Apr 16 03:21:42 chipblach kernel: sd 9:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Apr 16 03:21:42 chipblach kernel: sd 9:0:0:0: [sdb] CDB: Write(10): 2a 00 04 8d a3 a9 00 00 08 00
Apr 16 03:21:42 chipblach kernel: end_request: I/O error, dev sdb, sector 76391337
Apr 16 03:21:42 chipblach kernel: Buffer I/O error on device dm-2, logical block 9548869
Apr 16 03:21:42 chipblach kernel: lost page write due to I/O error on dm-2
Apr 16 03:21:42 chip

Any Ideas,

Thanks

Chip