Bug 1071914
| Summary: | Regression: Kernel update made Brainboxes ExpressCard device stop working | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Troels Arvin <troels> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, michele, troels |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-3.13.11-100.fc19 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-05-01 22:31:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
Created attachment 869925 [details]
Output from "modinfo ftdi_sio" with an older F19 kernel
Created attachment 869926 [details]
Output from "modinfo ftdi_sio" with a newer F19 kernel
Created attachment 869927 [details]
Output from "lsusb -v" with an older F19 kernel
Created attachment 869928 [details]
Output from "lsusb -v" with a newer F19 kernel
The procedure at http://www.brainboxes.com/faq/items/where-can-i-find-the-latest-linux-drivers-for-my-usb-device-or-e makes the device work again, but init scripts are not a good fit for Fedora, going forward. And it doesn't explain why something which used to work stops working with a newer kernel for the same Fedora generation. *********** 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.13.5-100.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. With 3.13.5-103.fc19.x86_64, the problem is still there. Do I really need to open a new case about this? Hi Troels, no need to open a new BZ, no. If you do a: echo 05d1 1001 >/sys/bus/usb-serial/drivers/ftdi_sio/new_id Does it work? thanks, Michele With 3.13.6-100.fc19.x86_64: When inserting the card, the /dev/ttyUSB0 device is still not automatically created, like it was with some of the earlier FC19 kernels. "echo 05d1 1001 >/sys/bus/usb-serial/drivers/ftdi_sio/new_id" makes the device appear, however. Still, I believe this is a regression: Something used to work with an earlier kernel in FC19, but now it doesn't work any longer unless some special trick is used. Agreed. I just needed confirmation that the echo command worked. I'll send the updated VID/PID upstream. I'll keep you posted here The problem still exists in the newly released 3.13.7-100.fc19.x86_64 package, but the "echo 05d1 1001 >/sys/bus/usb-serial/drivers/ftdi_sio/new_id" still works. From tomorrow, I will no longer have access to the hardware, so I will not be able to follow this bug. Feel free to close it, due to this. Usb serial maintainer will commit the updated PID/VID table for Brainboxes devices. Troels, thanks for reporting. I guess if none else is asking for this we can wait for whenever it will trickle down from upstream This has hit Linus tree now:
commit efe26e16b1d93ac0085e69178cc18811629e8fc5
Author: Michele Baldessari <michele>
Date: Mon Mar 31 10:51:00 2014 +0200
USB: serial: ftdi_sio: add id for Brainboxes serial cards
It was CC'ed to stable@ as well. Setting to POST (Josh, I hope this is correct.
Feel free to clue me in if that's not the right status)
Yep, that's just fine. I'll grab it today. Picked up in Fedora git. Thanks again Michele! kernel-3.14.1-200.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.14.1-200.fc20 Package kernel-3.14.1-200.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.14.1-200.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-5502/kernel-3.14.1-200.fc20 then log in and leave karma (feedback). kernel-3.13.11-100.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/kernel-3.13.11-100.fc19 kernel-3.14.2-200.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.14.2-200.fc20 kernel-3.14.2-200.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. kernel-3.13.11-100.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 869923 [details] udev rules file A kernel update for F19 around New Year made my Brainboxes VX-001 RS232 ExpressCard stop working. I believe that things worked up to generation 3.9 of the Fedora 19 kernel (could also be 3.10). Reverting to the old kernel-3.9.5-301.fc19.x86_64 package (shipped with F19) makes things work again. I can't find the older kernel updates for F19, so I can't pinpoint exactly when it went wrong. Attached 99-bbftdisio.rules file exists in /etc/udev/rules.d/ This used to mean that when the ExpressCard was inserted in my Lenovo laptop, the following message would appear in /var/log/messages: Mar 3 12:10:08 hostname kernel: [ 163.419818] usb 2-1.6: new full-speed USB device number 4 using ehci-pci Mar 3 12:10:08 hostname kernel: [ 163.514104] usb 2-1.6: New USB device found, idVendor=05d1, idProduct=1001 Mar 3 12:10:08 hostname kernel: [ 163.514113] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 3 12:10:08 hostname kernel: [ 163.514117] usb 2-1.6: Product: ExpressCard 1 Port RS232 (U) Mar 3 12:10:08 hostname kernel: [ 163.514121] usb 2-1.6: Manufacturer: Brainboxes Mar 3 12:10:08 hostname kernel: [ 163.514124] usb 2-1.6: SerialNumber: VXFTQ0E0 Mar 3 12:10:08 hostname kernel: [ 163.518301] ftdi_sio 2-1.6:1.0: FTDI USB Serial Device converter detected Mar 3 12:10:08 hostname kernel: [ 163.518351] usb 2-1.6: Detected FT232RL Mar 3 12:10:08 hostname kernel: [ 163.518355] usb 2-1.6: Number of endpoints 2 Mar 3 12:10:08 hostname kernel: [ 163.518359] usb 2-1.6: Endpoint 1 MaxPacketSize 64 Mar 3 12:10:08 hostname kernel: [ 163.518363] usb 2-1.6: Endpoint 2 MaxPacketSize 64 Mar 3 12:10:08 hostname kernel: [ 163.518366] usb 2-1.6: Setting MaxPacketSize 64 Mar 3 12:10:08 hostname kernel: [ 163.518736] usb 2-1.6: FTDI USB Serial Device converter now attached to ttyUSB0 Mar 3 12:10:08 hostname mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6" Mar 3 12:10:08 hostname mtp-probe: bus: 2, device: 4 was not an MTP device After this, a new device would show up in /dev: crw-rw---- 1 root dialout 188, 0 Mar 3 12:10 ttyUSB0 With the newer kernel packages, the following happens when the device is inserted: Mar 3 12:22:41 hostname kernel: [ 163.124979] usb 2-1.6: new full-speed USB device number 3 using ehci-pci Mar 3 12:22:41 hostname kernel: [ 163.219506] usb 2-1.6: New USB device found, idVendor=05d1, idProduct=1001 Mar 3 12:22:41 hostname kernel: [ 163.219517] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 3 12:22:41 hostname kernel: [ 163.219523] usb 2-1.6: Product: ExpressCard 1 Port RS232 (U) Mar 3 12:22:41 hostname kernel: [ 163.219527] usb 2-1.6: Manufacturer: Brainboxes Mar 3 12:22:41 hostname kernel: [ 163.219531] usb 2-1.6: SerialNumber: VXFTQ0E0 Mar 3 12:22:41 hostname mtp-probe: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6" Mar 3 12:22:41 hostname mtp-probe: bus: 2, device: 3 was not an MTP device Mar 3 12:22:41 hostname kernel: [ 163.285249] ftdi_sio: unknown parameter 'product' ignored Mar 3 12:22:41 hostname kernel: [ 163.285253] ftdi_sio: unknown parameter 'vendor' ignored Mar 3 12:22:41 hostname kernel: [ 163.285451] usbcore: registered new interface driver ftdi_sio Mar 3 12:22:41 hostname kernel: [ 163.285478] usbserial: USB Serial support registered for FTDI USB Serial Device - but no /dev/ttyUSB0 shows up in /dev The ftdi_sio kernel module _is_ loaded by the newer kernel, like it was before: # lsmod | fgrep ftdi_sio ftdi_sio 48930 0