I've altered the controller to use "cachedio" as suggested by Gorazd Golob and rebooted with the iommu=nomerge parameter. At least I've been able to create and mount an ext3 filesystem. However, when I tried untarring a kernel there was a journal error and it was remounted read-only. Here are the relevant system messages: EXT3 FS on sdb2, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs error (device sdb2): ext3_new_block: Allocating block in system zone - block = 44335105 Aborting journal on device sdb2. EXT3-fs error (device sdb2) in ext3_reserve_inode_write: Journal has aborted ext3_abort called. EXT3-fs error (device sdb2): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data Any other suggestions for tracking this one down? Details are at: http://bugzilla.kernel.org/show_bug.cgi?id=6052 It appears to be a problem with the SATA 150-4 on an x86_64 box with 8G RAM. - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
