Comment 16 for bug 907377

Revision history for this message
Tim Gardner (timg-tpi) wrote :

This is where things start to go south: in the syslog attached to comment #3:

Dec 21 13:54:37 kernel: [ 94.417294] NMI: PCI system error (SERR) for reason b1 on CPU 0.
Dec 21 13:54:37 kernel: [ 94.417298] Dazed and confused, but trying to continue
Dec 21 13:54:37 kernel: [ 94.417305] DRHD: handling fault status reg 2
Dec 21 13:54:37 kernel: [ 94.417311] DMAR:[DMA Read] Request device [03:00.0] fault addr ffeec000
Dec 21 13:54:37 kernel: [ 94.417313] DMAR:[fault reason 06] PTE Read access is not set
Dec 21 13:54:54 kernel: [ 111.087385] hpsa 0000:03:00.0: Controller lockup detected: 0xffff0000
Dec 21 13:54:54 kernel: [ 111.087398] hpsa 0000:03:00.0: cp ffff88018ce00000 had hardware error
Dec 21 13:54:54 kernel: [ 111.127427] sd 0:0:0:0: [sda] Unhandled error code
Dec 21 13:54:54 kernel: [ 111.127431] sd 0:0:0:0: [sda] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 21 13:54:54 kernel: [ 111.127436] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 06 84 ef b8 00 00 d0 00
Dec 21 13:54:54 kernel: [ 111.127446] end_request: I/O error, dev sda, sector 109375416
Dec 21 13:54:54 kernel: [ 111.127556] Aborting journal on device sda1-8.
Dec 21 13:54:54 kernel: [ 111.127564] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4501: Journal has aborted
Dec 21 13:54:54 kernel: [ 111.127586] EXT4-fs error (device sda1) in ext4_init_inode_table:1195: Journal has aborted