Stefan Richter <stefanr <at> s5r6.in-berlin.de> writes: > DRHD: handling fault status reg 2 > DMAR:[DMA Read] Request device [04:00.0] fault addr fffff000 > DMAR:[fault reason 02] Present bit in context entry is clear ... > The log sounds as if this happens during from-device DMA of 04:00.4 into > a consistent buffer, yet the fault is logged for device 04:00.0. The > log is from a Dell M4500. The devices are, according to a web search, > 04:00.0 CardBus bridge [0607]: Ricoh Co Ltd Device [1180:e476] (rev 02) > 04:00.4 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd Device [1180:e832] > (rev 03) (prog-if 10) This happens on my M4500 also - discovered with a Cardbus USB controller, which appears fine until you plug in a USB device - then prints a few repetitions of the error message before locking up the system hard. Have not been able to capture the output, but it's the same error. I can also reproduce it by loading the firewire driver, although that doesn't hard lock (just spams the console) - even with the yenta & pcmcia drivers unloaded. dmesg, lspci output at http://bur.st/~abrasive/public/cb-hang/ Any suggestions for things to prod? Thanks, James -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
