Re: Bug#312699: Please have hotplug rescan the scsi bus for scsi loads.
On Fri, Jun 10, 2005 at 01:11:30PM +0200, Christoph Hellwig wrote: On Fri, Jun 10, 2005 at 05:53:30PM +0900, Horms wrote: This works just fine when you use a 2.6 kernel. With the 2.4 kernel even the manual scan is extremly dangerous. I notice from the initial bug report that the kernel in question here is 2.4.27, which I guess means a hotplug script is in order. Marco, do you have any advice on how this should be done? As said even a hotplug script on 2.4.x would be dangerous. Anything that requires hotplugging or rescanning of scsi devices should absolutely use 2.6.x. Ok, I misunderstood that the first time around. I guess we should just close this and be done with it. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#312699: Please have hotplug rescan the scsi bus for scsi loads.
reassign 312699 hotplug thanks On Thu, Jun 09, 2005 at 10:00:02PM +0200, Christoph Hellwig wrote: On Thu, Jun 09, 2005 at 07:14:22PM +0200, Marco d'Itri wrote: reassign 312699 kernel thanks On Jun 09, Michael Heldebrant Ph.D [EMAIL PROTECTED] wrote: For a Dell Latitude X200 laptop and docking station is is necessary to manually run scsiadd -s to enable the cdrom drive through the firewire interface. Is there a way to intelligently rescan the scsi bus when potential scsi devices may enter and leave the system or should I look into reporting a bug against the sbp2 kernel module? I'd start with the kernel. If the kernel people say that this cannot be fixed in the driver then you could write a script for /etc/hotplug.d/ieee1394/ . If you can make it run scsiadd only on this specific system then I could add it to the hotplug package. This works just fine when you use a 2.6 kernel. With the 2.4 kernel even the manual scan is extremly dangerous. I notice from the initial bug report that the kernel in question here is 2.4.27, which I guess means a hotplug script is in order. Marco, do you have any advice on how this should be done? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#312699: Please have hotplug rescan the scsi bus for scsi loads.
On Jun 10, Horms [EMAIL PROTECTED] wrote: I'd start with the kernel. If the kernel people say that this cannot be fixed in the driver then you could write a script for /etc/hotplug.d/ieee1394/ . I notice from the initial bug report that the kernel in question here is 2.4.27, which I guess means a hotplug script is in order. Marco, do you have any advice on how this should be done? As I wrote, add a script to /etc/hotplug.d/ieee1394/. Make it log the environment and you will see which variables you can test for. But as hch explained, bus rescans can crash the system so I will not add such a script to the package (and I do not want to waste time supporting 2.4 kernels anyway). -- ciao, Marco signature.asc Description: Digital signature
Re: Bug#312699: Please have hotplug rescan the scsi bus for scsi loads.
reassign 312699 kernel thanks On Jun 09, Michael Heldebrant Ph.D [EMAIL PROTECTED] wrote: For a Dell Latitude X200 laptop and docking station is is necessary to manually run scsiadd -s to enable the cdrom drive through the firewire interface. Is there a way to intelligently rescan the scsi bus when potential scsi devices may enter and leave the system or should I look into reporting a bug against the sbp2 kernel module? I'd start with the kernel. If the kernel people say that this cannot be fixed in the driver then you could write a script for /etc/hotplug.d/ieee1394/ . If you can make it run scsiadd only on this specific system then I could add it to the hotplug package. -- ciao, Marco signature.asc Description: Digital signature
Re: Bug#312699: Please have hotplug rescan the scsi bus for scsi loads.
On Thu, Jun 09, 2005 at 07:14:22PM +0200, Marco d'Itri wrote: reassign 312699 kernel thanks On Jun 09, Michael Heldebrant Ph.D [EMAIL PROTECTED] wrote: For a Dell Latitude X200 laptop and docking station is is necessary to manually run scsiadd -s to enable the cdrom drive through the firewire interface. Is there a way to intelligently rescan the scsi bus when potential scsi devices may enter and leave the system or should I look into reporting a bug against the sbp2 kernel module? I'd start with the kernel. If the kernel people say that this cannot be fixed in the driver then you could write a script for /etc/hotplug.d/ieee1394/ . If you can make it run scsiadd only on this specific system then I could add it to the hotplug package. This works just fine when you use a 2.6 kernel. With the 2.4 kernel even the manual scan is extremly dangerous. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
