On Fri, Mar 10, 2006 at 08:10:12AM +0100, Sven Luther wrote: > > I've done a little poking of my own at sysfs based on the comments in > > the yaird code. I can confirm that it is possible for a PCI IDE driver > > to be listed as associated with a PCI device without actually being the > > driver used to access the device. This happens on my alpha, where > > ide-generic must be used due to bugs in the cmd64x driver, yet running > > modprobe cmd64x does show this driver associated with the PCI device: > > $ ls -l /sys/devices/pci0000\:00/0000\:00\:0b.0/driver > > lrwxrwxrwx 1 root root 0 2006-03-09 19:46 /sys/devices/pci0000:00/0000:00:0b.0/driver -> ../../../bus/pci/drivers/CMD64x_IDE > Mmm. When this was happening, could you use and mount partition on this device ? > And when doing so, do you know which of ide-generic or cmd64x would be used to > read the drive ? Are you suggesting that loading cmd64x has changed which driver is associated with /dev/hda, even though the machine has partitions mounted from it at the time? > And again, is the right thing to do here, not to fix those cmd64x bugs ? Um, that's completely missing the point. The point of this exercise was to try to rule out a possible explanation for the yaird workaround. Which I did. > > However, /sys/block/hda/device still points to the right place, and it's my > > understanding that /sys/block is what yaird walks, so this still is no > > explanation for how someone could have mis-identified a bug in this area. > How does it find the device and then the driver starting from block ? $ readlink /sys/block/hda/device ../../devices/ide0/0.0 $ So we should expect yaird to only load ide-generic on this system, since cmd64x, while loaded, is not associated with the root device (according to sysfs or otherwise). -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature