>> Hmmm kills my pc when loaded into my kernel (2.6.30)... What kernel >> version did you last use this with? > O, it's my bad. I don't update the codes. > Pls try the new attached. It works on the RHEL5 2.6.18-128.el5. Thanks Xie but still causes a system crash unfortunately... ...I think that maybe the easiest way would be to rebuild the kernel with aptly-placed prink()s. But where's the best place to dump? I inserted into scsi_lib.c:scsi_execute() and that does dump commands, but doesn't seem to give me what I want. Just to clarify, I am running a dvd-drive firmware update in a vmware VM (windows xp guest). I have the dvd-drive (/dev/sr1) connected in the VM as a scsi device. I would like to print out ALL traffic to /dev/sr1 - whether generated in the VM or not - and i need both the cmds and the data in both directions. I'm just not familiar with the scsi kernel code and there's quite a lot of things going on there so if anyone could tell me where the best place to put my printk()s in the kernel code would be - that would be great! -- To unsubscribe from this list: 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
