sander.sweers at gmail wrote: >next option, iommu=force and iommu=off > >The first one forces *hardware* iommu and the second disables it >completely.
Thank you for your help, Sander. When I use either option, I get the same errors. With iommu=off I get the same SW-IOMMU error with the added bonus of this: Nov 4 16:58:31 mythbox-mbe kernel: Filesystem "md0": Disabling barriers, not supported by the underlying device Nov 4 16:58:31 mythbox-mbe kernel: XFS mounting filesystem md0 Nov 4 16:58:31 mythbox-mbe kernel: DMA: Out of SW-IOMMU space for 8192 bytes at device 0000:00:1f.2 Nov 4 16:58:31 mythbox-mbe kernel: DMA: Out of SW-IOMMU space for 8192 bytes at device 0000:00:1f.2 Nov 4 16:58:31 mythbox-mbe kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 4 16:58:31 mythbox-mbe kernel: ata1.00: cmd 25/00:00:3f:70:1c/00:04:1d:00:00/e0 tag 0 cdb 0x0 data 524288 in Nov 4 16:58:31 mythbox-mbe kernel: res 50/00:00:76:70:1c/00:00:1d:00:00/e0 Emask 0x40 (internal error) Nov 4 16:58:31 mythbox-mbe kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 4 16:58:31 mythbox-mbe kernel: ata2.00: cmd 25/00:00:3f:70:1c/00:04:1d:00:00/e0 tag 0 cdb 0x0 data 524288 in Nov 4 16:58:31 mythbox-mbe kernel: res 50/00:00:96:75:1c/00:00:1d:00:00/f0 Emask 0x40 (internal error) Nov 4 16:58:31 mythbox-mbe kernel: ata2.00: configured for UDMA/133 Nov 4 16:58:31 mythbox-mbe kernel: ata1.00: configured for UDMA/133 Nov 4 16:58:31 mythbox-mbe kernel: ata2.01: configured for UDMA/133 Nov 4 16:58:31 mythbox-mbe kernel: ata2: EH complete <snip> Nov 4 16:58:31 mythbox-mbe kernel: DMA: Out of SW-IOMMU space for 8192 bytes at device 0000:00:1f.2 Nov 4 16:58:31 mythbox-mbe kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 4 16:58:31 mythbox-mbe kernel: ata2.01: cmd 25/00:60:2f:72:1c/00:03:1d:00:00/f0 tag 0 cdb 0x0 data 442368 in Nov 4 16:58:31 mythbox-mbe kernel: res 50/00:00:2f:60:38/00:00:3a:00:00/f0 Emask 0x40 (internal error) Nov 4 16:58:31 mythbox-mbe kernel: ata2.00: configured for UDMA/133 Nov 4 16:58:31 mythbox-mbe kernel: ata2.01: configured for UDMA/133 Nov 4 16:58:31 mythbox-mbe kernel: sd 1:0:1:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Nov 4 16:58:31 mythbox-mbe kernel: sd 1:0:1:0: [sdd] Sense Key : Aborted Command [current] [descriptor] Nov 4 16:58:31 mythbox-mbe kernel: Descriptor sense data with sense descriptors (in hex): Nov 4 16:58:31 mythbox-mbe kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 4 16:58:31 mythbox-mbe kernel: 3a 38 60 2f Nov 4 16:58:31 mythbox-mbe kernel: sd 1:0:1:0: [sdd] Add. Sense: No additional sense information Nov 4 16:58:31 mythbox-mbe kernel: end_request: I/O error, dev sdd, sector 488403503 Nov 4 16:58:31 mythbox-mbe kernel: raid5:md0: read error not correctable (sector 488403440 on sdd1). Nov 4 16:58:31 mythbox-mbe kernel: raid5:md0: read error not correctable (sector 488403448 on sdd1). Nov 4 16:58:31 mythbox-mbe kernel: raid5:md0: read error not correctable (sector 488403456 on sdd1). /dev/md0 is my 4 disk SATA software RAID 5 formatted with XFS. It seems to go thru this sequence for each of the 4 disks in the array. Booting from my Debian installation/rescue CD, deleteing the files in /lib/firmware and removing the appended boot parameters from LILO gets me back to my original issue of the firmware not being able to be opened until I do it by hand after the system boots. Any other ideas? Michael Hanson _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
