Bug#1009852: Need documentation
I've been trying to track down the cause of this myself. The problem I'm having is that there is no documentation available for the Marvell 88E8001 Ethernet controller. I've found that if I modify my I/O device to insert a 1 ms delay between receiving the command frame and sending the response frame the issue goes away. This leads me to believe the response (from the device without the delay) is arriving during the servicing of the transmit interrupt and the response frame interrupt is somehow being cleared. Chris
Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware
On 10/16/2017 11:32 AM, Paul Fox wrote: ben, chris -- regarding this bug: Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware whatever became of the proposed patch. i'm running ubuntu 16.04.3, kernel 4.4.0-97-generic, and the failure is still present there. paul =-- paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 50.2 degrees) . The patch provided fixed the bug. I think I responded with the news. Chris
Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware
On 08/02/2016 16:56, Ben Hutchings wrote: On Mon, 2016-08-01 at 22:51 -0700, Chris Rhodin wrote: [...] I get this from dmesg. I'm assuming the new error -2 indicates the file was not found. [...] Yes. And the other error code (-110) indicates a time-out. Can you test whether the attached patch fixes this? You can do this by following the instructions at <https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>. Ben. Hi Ben, That worked. All four ports can now connect and communicate. I haven't tested handshaking, hardware or software. I did have to export "ezusb_writememory" from ezusb.c. Chris
Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware
On 07/31/2016 17:31, Ben Hutchings wrote: Control: retitle -1 linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware Control: tag -1 moreinfo On Sun, 2016-07-31 at 00:16 -0700, Chris Rhodin wrote: Subject: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA- 49WLC failed to load firmware Package: src:linux Version: 3.16.7-ckt25-2+deb8u3 Severity: normal Tags: upstream Dear Maintainer, The Keyspan USB serial adapter USA-49WLC fails to load firmware and will not work. This device is based on an older generation Cypress EZ-USB FX (CY7C64613-80NC). The firmware fails to load when the device is attached. While searching for an answer I found the problem may stem from a non-standard implementation of the firmware loading commands. Earlier versions of the kernel (pre-Wheezy) did work with this device. I have tried but have been unable to locate the change in the USB code taht causes this failure. [...] Is the firmware actually installed? (It should be /lib/firmware/keyspan/usa49wlc.fw, I think.) We don't distribute firmware for this device as it's not clear that we have permission to do so. Ben. The firmware is installed at: /lib/firmware/keyspan/usa49wlc.fw If I do the following: 1) Attach the device. 2) Use dmesg to confirm the load failure 3) Detach the device 4) Rename usa49wlc.fw to usa49wlc.fw.sav 5) Attache the device I get this from dmesg. I'm assuming the new error -2 indicates the file was not found. [ 871.336021] usb 1-4.1: new full-speed USB device number 8 using ehci-pci [ 871.428765] usb 1-4.1: New USB device found, idVendor=06cd, idProduct=011a [ 871.428769] usb 1-4.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 872.496494] usbcore: registered new interface driver usbserial [ 872.496520] usbcore: registered new interface driver usbserial_generic [ 872.496539] usbserial: USB Serial support registered for generic [ 872.511885] usbcore: registered new interface driver keyspan [ 872.511909] usbserial: USB Serial support registered for Keyspan - (without firmware) [ 872.511931] usbserial: USB Serial support registered for Keyspan 1 port adapter [ 872.511952] usbserial: USB Serial support registered for Keyspan 2 port adapter [ 872.511986] usbserial: USB Serial support registered for Keyspan 4 port adapter [ 872.512065] keyspan 1-4.1:1.0: Keyspan - (without firmware) converter detected [ 872.516266] usb 1-4.1: firmware: direct-loading firmware keyspan/usa49wlc.fw [ 875.516265] usb 1-4.1: ezusb_ihex_firmware_download - ezusb_writememory failed writing internal memory (-110 7F92 c9001359d006 1) [ 875.516285] usb 1-4.1: failed to load firmware "keyspan/usa49wlc.fw" [ 875.516307] keyspan: probe of 1-4.1:1.0 failed with error -5 [ 920.778513] usb 1-4.1: USB disconnect, device number 8 [ 933.176024] usb 1-4.1: new full-speed USB device number 9 using ehci-pci [ 933.268765] usb 1-4.1: New USB device found, idVendor=06cd, idProduct=011a [ 933.268769] usb 1-4.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 933.269184] keyspan 1-4.1:1.0: Keyspan - (without firmware) converter detected [ 933.269247] usb 1-4.1: firmware: failed to load keyspan/usa49wlc.fw (-2) [ 933.269250] usb 1-4.1: Direct firmware load failed with error -2 [ 933.269252] usb 1-4.1: Falling back to user helper [ 933.270457] usb 1-4.1: failed to load firmware "keyspan/usa49wlc.fw" [ 933.270465] keyspan: probe of 1-4.1:1.0 failed with error -5 Chris
Bug#833035: (no subject)
Subject: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware Package: src:linux Version: 3.16.7-ckt25-2+deb8u3 Severity: normal Tags: upstream Dear Maintainer, The Keyspan USB serial adapter USA-49WLC fails to load firmware and will not work. This device is based on an older generation Cypress EZ-USB FX (CY7C64613-80NC). The firmware fails to load when the device is attached. While searching for an answer I found the problem may stem from a non-standard implementation of the firmware loading commands. Earlier versions of the kernel (pre-Wheezy) did work with this device. I have tried but have been unable to locate the change in the USB code taht causes this failure. -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=ZFS=proliant/root ro boot=zfs quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 16.574336] [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c [ 16.574337] [drm] Encoders: [ 16.574339] [drm] DFP2: INTERNAL_UNIPHY [ 16.574340] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [ 16.574341] [drm] Connector 2: [ 16.574342] [drm] VGA-1 [ 16.574344] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [ 16.574345] [drm] Encoders: [ 16.574346] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 16.638855] [drm] fb mappable at 0xD045E000 [ 16.638857] [drm] vram apper at 0xD000 [ 16.638859] [drm] size 14745600 [ 16.638860] [drm] fb depth is 24 [ 16.638861] [drm]pitch is 10240 [ 16.638943] fbcon: radeondrmfb (fb0) is primary device [ 16.727125] Console: switching to colour frame buffer device 320x90 [ 16.738343] radeon :13:00.0: fb0: radeondrmfb frame buffer device [ 16.738345] radeon :13:00.0: registered panic notifier [ 16.752658] [drm] Initialized radeon 2.39.0 20080528 for :13:00.0 on minor 0 [ 17.852049] floppy0: no floppy controllers found [ 19.871023] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 19.912638] systemd-journald[1444]: Received request to flush runtime journal from PID 1 [ 20.766563] RPC: Registered named UNIX socket transport module. [ 20.766568] RPC: Registered udp transport module. [ 20.766570] RPC: Registered tcp transport module. [ 20.766571] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 20.793952] FS-Cache: Loaded [ 20.848920] FS-Cache: Netfs 'nfs' registered for caching [ 20.907617] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 22.126082] Adding 16777212k swap on /dev/zd0. Priority:-1 extents:1 across:16777212k SSFS [ 22.832872] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 22.832908] NFSD: starting 90-second grace period (net 818ba200) [ 23.072027] vboxdrv: Found 8 processor cores [ 23.072625] vboxdrv: fAsync=0 offMin=0x697 offMax=0xd969 [ 23.172815] vboxdrv: TSC mode is Synchronous, tentative frequency 2333416072 Hz [ 23.172818] vboxdrv: Successfully loaded version 5.0.26 (interface 0x0024) [ 23.557556] VBoxNetFlt: Successfully started. [ 23.579074] VBoxNetAdp: Successfully started. [ 23.931524] VBoxPciLinuxInit [ 24.112241] vboxpci: IOMMU not found (not registered) [ 24.213785] cfg80211: Calling CRDA to update world regulatory domain [ 24.558366] cfg80211: World regulatory domain updated: [ 24.558371] cfg80211: DFS Master region: unset [ 24.558373] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 24.558376] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 24.558378] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 24.558380] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [ 24.558382] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 24.558385] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 24.558387] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 24.558389] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 24.558391] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [ 24.682759] bnx2 :03:00.0: firmware: direct-loading firmware bnx2/bnx2-mips-06-6.2.3.fw [ 24.685499] bnx2 :03:00.0: firmware: direct-loading firmware bnx2/bnx2-rv2p-06-6.0.15.fw [ 24.685547] bnx2 :03:00.0: irq 70 for MSI/MSI-X [ 24.816026] bnx2 :03:00.0 eth0: using MSI [ 24.816087] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 24.818106] bnx2 :05:00.0: irq 71 for MSI/MSI-X [ 24.948022] bnx2
