On May 31 Jonathan Isom wrote: > Well I did some further testing. If I boot with /bin/sh as init and > manually load the firewire modules the C200 works. I moved out all > kernel modules but firewire and loaded init and it start giving the > offline messages. So it appears to be a userspace problem. (Or a firmware problem actually, provoked by Linux userspace that does not behave like a Windows system.) > Just not sure where to start. I already did some digging in udev but > no luck so far. I'm running gentoo which probably make tracking it > down just a little harder as there are few identical installs in the > world. Below is a listing of init scripts loaded at boot. > > Any Ideas? [...] Nothing obvious as far as I can tell. The mythbackend perhaps? Or a GUI desktop component that is started after login into xdm? I don't know if there is a logging facility in the kernel's SCSI layer that could expose the process name of SCSI ioctl issuers, but you can add one: --- a/drivers/scsi/sr.c +++ b/drivers/scsi/sr.c @@ -479,6 +479,9 @@ static int sr_block_open(struct block_de ret = cdrom_open(&cd->cdi, bdev, mode); if (ret) scsi_cd_put(cd); + else + printk(KERN_INFO "***** %s opened by %s *****\n", + cd->cdi.name, current->comm); } mutex_unlock(&sr_mutex); return ret; -- Stefan Richter -=====-==-== -=-= ===== http://arcgraph.de/sr/ -- 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
