Thank you, Joseph! I did test upstream at v4.13-rcr4 as you suggested. Same complaints. I tried v4.13-rcr4 "lowlatency" as well, same complaints.
What seems strange to me is that I don't think I was getting these complaints under 16.04 LTS Desktop with Studio (ie lowlatency)/LAMP/ZoneMinder overlays. This same machine, same H/W, was subject to intense scrutiny under 16.04 schema as described for at least 3 months after installing the NEC/Renasas 27xxx2 based Startech card. Very hard to believe I didn't pull a DMESG in all that time. But stranger things have happened. Will try to follow on this report as suggested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710548 Title: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech Status in linux package in Ubuntu: Incomplete Bug description: In trying to build a zoneminder server, I think I stumbled on a kernel bug. It seems to have snuck in sometime between 16.04 desktop promoted to server, and 17.04 server promoted to desktop. The suggestion is that the very popular Nec/Renasas 27xxx2 may need "quirk" in the kernel. Timeline: (Scene 1) Loaded 16.04 Ubuntu Desktop Promoted Desktop to Studio Promoted Desktop to Server Added Zoneminder Needed more cams, added Startech PEXUSB3S44V NEC/Renesasa 27XXX2 based card for more USB channels. Everything worked quite well. Some errors in ZM but no DMESG as far as I recall. (Scene 2) Wiped the drive. Loaded 17.04 Server Now getting messages in DMESG complaining of thousands of errors: [96415.044917] handle_tx_event: 516 callbacks suppressed [96415.044924] xhci_hcd 0000:0c:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Messages suggest "quirk" is the solution. a)Researched usb 3.0 "quirk' b)Noticed it's really a "thing" c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. (Scene 3) Anecdotes suggest Nec/Renasas firmware is to blame. a) Kernel indicates 2024 firmaware b) Startech website has 2026 firmware. c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing runfile for effective firmware update of all 4 controllers. Yes, for the 4 channel controller, count them: 4. d) Firmware updated. (Scene 4) Rebooted with new Startech/Nec/Renases 2026 firmware. SAME OLD PLETHORA OF ERRORS (Scene 5) I give up. It may well be worth noting that there are no errors from DMESG until some seconds after the first webcam is attached to the Startech. And I can't overemphasize the fact that I don't think I had any DMESG errors under Desktop 16.04 I think the file attached represents DMESG immediately before the errors start going nuts. My theory is that ZM does lazy polls on missing cams but once it gets 'hold if the cam and sucking data the quirk bug surfaces. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jeff 12776 F.... pulseaudio /dev/snd/controlC3: jeff 12776 F.... pulseaudio /dev/snd/controlC2: jeff 12776 F.... pulseaudio /dev/snd/controlC1: jeff 12776 F.... pulseaudio Date: Sun Aug 13 16:48:41 2017 MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware 1.164.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
