Created attachment 791693 [details] /var/log/messages excerpt I have a firewire HDD enclosure that used to work fine up to Fedora 17. I use it occasionally to backup and read data from a work project. A couple of weeks ago, I upgraded my system to F19. Yesterday, I needed to access some files stored on the drive, but it never showed up on my disks' list. After many reboots, plugging and unplugging the drive, I had it appear in gnome-disks, but the program reported that it contained no media, and that was as far as I was able to go. I can't remember the version of my last F17 kernel, but it was the latest available and I had used the enclosure a few minutes before the upgrade. I am currently on 3.10.9-200.fc19.x86_64. I am attaching the relevant excerpt from my /var/log/messages. Several worker threads get killed, the last one after about 7 minutes. If I manually remove and re-insert firewire-ohci, the process repeats itself in the exact same way.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
I ran a few tests today -all with kernel 3.11-, I think there is some sort of "misunderstanding" between the controller of the enclosure and the kernel. The only markings on the enclosure itself read "MOBILE DISK" on the top and "HD-337-COMBO" on the bottom plate. I took it apart and I had to use a magnifying glass to read the etching on the controller, it was an AGERE FW801A chip. Inside the enclosure I've got an old 250GB Western Digital IDE disk. I connected a Seagate FreeAgent Pro disk and it came up in an instant. I plugged the 337-combo and I got the same errors as with previous kernels. In /sys/bus/firewire/devices/ I got the following: /sys/bus/firewire/devices/fw1.0/modalias:ieee1394:ven000001A3mo00008034sp0000609Ever00010483 /sys/bus/firewire/devices/fw1.0/model:0x008034 /sys/bus/firewire/devices/fw1.0/rom_index:10 /sys/bus/firewire/devices/fw1.0/specifier_id:0x00609e /sys/bus/firewire/devices/fw1.0/uevent:DRIVER=firewire_sbp2 /sys/bus/firewire/devices/fw1.0/uevent:MODALIAS=ieee1394:ven000001A3mo00008034sp0000609Ever00010483 /sys/bus/firewire/devices/fw1.0/version:0x010483 /sys/bus/firewire/devices/fw1/dev:249:1 /sys/bus/firewire/devices/fw1/guid:0x0001a350000290a4 /sys/bus/firewire/devices/fw1/is_local:0 /sys/bus/firewire/devices/fw1/uevent:MAJOR=249 /sys/bus/firewire/devices/fw1/uevent:MINOR=1 /sys/bus/firewire/devices/fw1/uevent:DEVNAME=fw1 /sys/bus/firewire/devices/fw1/units:0x00609e:0x010483 /sys/bus/firewire/devices/fw1/vendor:0x0001a3 /sys/bus/firewire/devices/fw1/vendor_name:337 COMBO I booted off a F16 live CD and the device was working fine. On-board firewire controller (from lspci): 04:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) lscsi -L output: [14:0:0:0] disk WDC WD25 00JB-00FUA0 0.01 /dev/sdg device_blocked=0 iocounterbits=32 iodone_cnt=0xa ioerr_cnt=0x0 iorequest_cnt=0xf queue_depth=1 queue_type=none scsi_level=0 state=running timeout=30 type=0 Please let me know if you need more information.
Hi Alexander, the latest F17 kernel version was kernel-3.9.10-100.fc17.x86_64.rpm. Could you confirm if it worked or not? In theory you could even try downloading it and see if it works on your more recent Fedora installation (http://archives.fedoraproject.org/pub/archive/fedora/linux/updates/17/x86_64/) I ask because if that version worked it should be moderately simple to find the commit that broke things as there are not too many firewire changes these days: $ git lg v3.9..HEAD drivers/firewire/ |wc -l 38 Thanks, Michele
Created attachment 828730 [details] new /var/log/messages excerpt on 3.9.10-100c.f17 Just tested it and it works with kernel 3.9.10-100.fc17. Please, see the attached file. It seems that there is some sort of error in both cases, but the disk gets mounted in 3.9, whereas in kernels up to 3.11.7-200.fc19 it does not.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
I have just upgraded to 3.12.6-200.fc19 and I can confirm it is now working again. Good job!