[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

Ooops. I can see that point. The Startech card I'm using claims to be
based on the uPD720202: perhaps it has two if them. I'd say that the
uPD720202 needs the XHCI_TRUST_TX_LENGTH quirk as well.

-Jeff

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

Thank you Joseph, sorry I couldn't try your test kernel but I've just
been chasing my tail trying to figure out why I can install some kernels
and not others.

My email is mysterylectric...@yahoo.com

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

Re: [Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

I wasn't able to test the kernel you provided, dpkg -i complained of 
conflicting packages. I suspect because the kernel was down-rev relative to the 
running kernel. But I don't reslly know, I'm relatively new to compilling and 
installing kernels. 
However, I was able to compile and install my own kernel on the target machine. 
Once again, all I did was change line 184 to be identical to like 187 and it 
worked like a charm: no more errors. 
So my suggestion was that if you made the exact same change, your test jernel 
_should_ work. But I can understand if that's just not the way it's done around 
here, and I'll be happy to test your kernel if I can get around the error 
message. Is there an option I can give to dpkg to force the installation?
-Jeff
On Friday, July 27, 2018, 8:41:19 AM PDT, Joseph Salisbury 
 wrote:  
 
 Sorry for the delay.  Just to confirm, the test kernel posted in comment
#3 did in fact resolve this bug?  If so, I'll submit an SRU request.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184                        pdev->device == 0x0014)
  185                xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187                        pdev->device == 0x0015)
  188                xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

The underlying bug is also described in bug ID #1737629, but I think
that report was prior to the typo ie: before the "fix" with the typo was
added.

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

The typo is still present in 4.15.0-29.31

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

I downloaded the three files you mentioned and tried to install them
using 'dpkg -i *.deb' as root. Two of the pkgs installed OK but the
kernel proper did not, giving error:

  Selecting previously unselected package 
linux-image-unsigned-4.15.0-22-generic.
dpkg: regarding 
linux-image-unsigned-4.15.0-22-generic_4.15.0-22.25_lp1773704_amd64.deb 
containing linux-image-unsigned-4.15.0-22-generic:
 linux-image-unsigned-4.15.0-22-generic conflicts with 
linux-image-4.15.0-22-generic
  linux-image-4.15.0-22-generic (version 4.15.0-22.24) is present and installed.

dpkg: error processing archive 
linux-image-unsigned-4.15.0-22-generic_4.15.0-22.25_lp1773704_amd64.deb 
(--install):
 conflicting packages - not installing linux-image-unsigned-4.15.0-22-generic

I rebooted the system and as one might expect, the errors in dmesg log
persist.

I read up a bit on dpkg hoping I could -f "force" the installation but
it appears more complicated than that.

How to proceed? Strange, I've installed test kernels (for this same
issue in fact, see bug ID #1710548, which did in fact fix the problem:
but the typo in the re-write of the fix that found it's way into the
distro uproots the fix).

Again I have to underscore the fact that I've built my own kernels with
line 184 changed to be identical to line 187 and the problems are
solved.

If that was your approach, please consider your fix to have been
successfully tested.

I didn't have much trouble installing the kernels I built so the above
errors from dpkg are a mystery to me.

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

Re: [Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

No, premature. Bug still exists. I'll try your kernel at the next sitting.
-Jeff

On Tuesday, May 29, 2018, 1:11:03 PM PDT, Joseph Salisbury 
 wrote:  
 
 I built a patched test kernel.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1773704

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184                        pdev->device == 0x0014)
  185                xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187                        pdev->device == 0x0015)
  188                xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

Re: [Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

Hey! This bug may be fixed.As best I recall I did a fresh install from nightly 
build about 3 days ago, but had not installed zoneminder so no op to tickle the 
bug.
Today I did an upgrade and a dist-upgrade, then loaded zoneminder, started 
pulling data over renesas port, so far no dmesg errors, I think it's fixed. 
Did you fix it? Well blessings on whoever did.
I'll let you know if it pops up again. Thank you so much
On Tuesday, May 29, 2018, 1:11:03 PM PDT, Joseph Salisbury 
 wrote:  
 
 I built a patched test kernel.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1773704

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184                        pdev->device == 0x0014)
  185                xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187                        pdev->device == 0x0015)
  188                xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

Re: [Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

Just though of something. reinstalled a system from daily build yesterday.
So here's the deal: I'l try to see if it's fixed as of yesterday
But it will take me some hours to re-con zoneminder to trigger the bug.
-jeff
On Tuesday, May 29, 2018, 1:11:03 PM PDT, Joseph Salisbury 
 wrote:  
 
 I built a patched test kernel.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1773704

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184                        pdev->device == 0x0014)
  185                xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187                        pdev->device == 0x0015)
  188                xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

Re: [Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

Dear Mr. Salisbury,
I can't believe it's been 12 days since I filed this report. Seems like it was 
just yesterday. And in fact it's just today I found your missives. Shame on me! 
I'm having a bad case of battle fatigue with this issue. I'm deploying like 
TODAY.  Do I live with errors? Do I compile my own kernel ( have done for 6 mos 
now)? Do I try your kernel? Do I live with errors until the typo  is fixed? 
I hope you can trust me on this one, This is a single-character typo. Fix the 
typo, everything works fine.
The only question at this point is how to run it up the flagpole as quickly as 
possible. I suspect it's upstream of Ubuntu. 
On Tuesday, May 29, 2018, 11:51:15 AM PDT, Joseph Salisbury 
 wrote:  
 
 ** Changed in: linux (Ubuntu Bionic)
    Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
    Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Bionic)
      Status: Triaged => In Progress

** Changed in: linux (Ubuntu)
      Status: Triaged => In Progress

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184                        pdev->device == 0x0014)
  185                xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186        if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187                        pdev->device == 0x0015)
  188                xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

Don't see the point in adding log files for a simple and obvious typo,
but before code  was added for this fix I believe I did generate before
and after logs under bug ID #1710548. In any case I'm running kernels in
which I've fixed the typo.

Status changed to confirmed.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

[Kernel-packages] [Bug 1773704] [NEW] Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

[Jeffrey Miller]

Public bug reported:

A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.


183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
184 pdev->device == 0x0014)
185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
187 pdev->device == 0x0015)
188 xhci->quirks |= XHCI_RESET_ON_RESUME;

Line 184 should be identical to line 187, ie: should read pdev->device
== 0x0015)

I've compiled the kernel both with and without the typo. As written,
hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
needed when zoneminder tries to access my USB webcams. With the fix
applied as I've suggested the messages disappear.

The typo is still present in 4.15.0-22.24

For more background, you may refer to bug ID #1710548

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1773704

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  New

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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

Re: [Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Hi,
It looks like someone attempted a fix, but it was beset by a typo. I fixed the 
typo and compiled the kernel and the issue was resolved. I detailed the typo in 
the original thread. Can you run this up the flagpole for me? I don't know how 
to get in touch with the devs. 
Thank you,
-Jeff
On Sunday, March 25, 2018, 9:36:06 PM PDT, Kai-Heng Feng 
 wrote:  
 
 This was my attempt to send a quirk patch:
https://lkml.org/lkml/2017/9/6/516

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1710548

Title:
  Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech
  C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Building zoneminder server. I think I stumbled on a kernel bug.

  The suggestion is that the popular Renesas / NEC - µPD720202 may need
  "quirk" in the kernel.

  Wiped the drive.
  Loaded 17.04 Server
  Now getting 100's of messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :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)Discovered it's really a "thing"
  c)Couldn't find recipe for patching kernel for NEC/Renasas "quirk" fix.

  [EDIT]: Note C920 webcam is USB 2.0.
  Note DMESG errors disappear when cam is plug into motherboard USB 2.0 ports. 

  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware.
  c) SIDEBAR: 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 update iterations.
  d) Firmware updated.

  Rebooted with new Startech/Nec/Renases 2026 firmware.
  SAME OLD PLETHORA OF ERRORS

  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, while zoneminder
  is running.

  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 a hold of the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04,17.10,18.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36 also in 4.13 and 4.15
  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

-- 
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:
  Renesas / NEC - µPD720202 needs 

[Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Yeah it's a typo.

-- 
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:
  Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech
  C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Building zoneminder server. I think I stumbled on a kernel bug.

  The suggestion is that the popular Renesas / NEC - µPD720202 may need
  "quirk" in the kernel.

  Wiped the drive.
  Loaded 17.04 Server
  Now getting 100's of messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :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)Discovered it's really a "thing"
  c)Couldn't find recipe for patching kernel for NEC/Renasas "quirk" fix.

  [EDIT]: Note C920 webcam is USB 2.0.
  Note DMESG errors disappear when cam is plug into motherboard USB 2.0 ports. 

  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware.
  c) SIDEBAR: 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 update iterations.
  d) Firmware updated.

  Rebooted with new Startech/Nec/Renases 2026 firmware.
  SAME OLD PLETHORA OF ERRORS

  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, while zoneminder
  is running.

  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 a hold of the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04,17.10,18.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36 also in 4.13 and 4.15
  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:
   USERPID 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

[Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Hmm, having resigned to building my own kernels for the foreseeable
future, I DL'd the source tree for bionic and took a peek at xhci-pci.c
It looks like someone has tried to incorporate the patch of interest. I
find:

if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
pdev->device == 0x0014)
xhci->quirks |= XHCI_TRUST_TX_LENGTH;
if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
pdev->device == 0x0015)
xhci->quirks |= XHCI_RESET_ON_RESUME;

So I recompiled as-is, though common sense suggested I was already
running the exact same (bionic) kernel.

The build seemed to succeed but the errors in dmesg persist.

Could the 14 in:

pdev->device == 0x0014)

.. represent a typo?

I guess I'll change that tonight and try recompiling.

-Jeff

-- 
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:
  Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech
  C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Building zoneminder server. I think I stumbled on a kernel bug.

  The suggestion is that the popular Renesas / NEC - µPD720202 may need
  "quirk" in the kernel.

  Wiped the drive.
  Loaded 17.04 Server
  Now getting 100's of messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :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)Discovered it's really a "thing"
  c)Couldn't find recipe for patching kernel for NEC/Renasas "quirk" fix.

  [EDIT]: Note C920 webcam is USB 2.0.
  Note DMESG errors disappear when cam is plug into motherboard USB 2.0 ports. 

  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware.
  c) SIDEBAR: 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 update iterations.
  d) Firmware updated.

  Rebooted with new Startech/Nec/Renases 2026 firmware.
  SAME OLD PLETHORA OF ERRORS

  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, while zoneminder
  is running.

  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 a hold of the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04,17.10,18.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36 also in 4.13 and 4.15
  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:
   USERPID 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
  

[Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

** Description changed:

  Building zoneminder server. I think I stumbled on a kernel bug.
  
  The suggestion is that the popular Renesas / NEC - µPD720202 may need
  "quirk" in the kernel.
- 
  
  Wiped the drive.
  Loaded 17.04 Server
  Now getting 100's of messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :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/RenasaSs "quirk" fix.
+ b)Discovered it's really a "thing"
+ c)Couldn't find recipe for patching kernel for NEC/Renasas "quirk" fix.
  
  [EDIT]: Note C920 webcam is USB 2.0.
+ Note DMESG errors disappear when cam is plug into motherboard USB 2.0 ports. 
  
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware.
  c) SIDEBAR: 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 update iterations.
  d) Firmware updated.
  
  Rebooted with new Startech/Nec/Renases 2026 firmware.
  SAME OLD PLETHORA OF ERRORS
  
  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, while zoneminder
  is running.
  
- 
- 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.
+ 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 a hold of 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
+ DistroRelease: Ubuntu 17.04,17.10,18.04
+ Package: linux-image-4.10.0-32-generic 4.10.0-32.36 also in 4.13 and 4.15
  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:
   USERPID 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

-- 
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:
  Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech
  C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Building zoneminder server. I think I stumbled on a kernel bug.

  The suggestion is that the popular Renesas / NEC - µPD720202 may need
  "quirk" in the kernel.

  Wiped the drive.
  Loaded 17.04 Server
  Now getting 100's of messages in DMESG complaining of thousands of errors:
  [96415.044917] 

[Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Bug still exists in 4.15 kernel/Bionc Beaver

** Description changed:

- 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.
+ Building zoneminder server. I think I stumbled on a kernel bug.
  
  The suggestion is that the popular Renesas / NEC - µPD720202 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 Renesas / NEC - µPD720202 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:
+ Now getting 100's of messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :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/RenasaSs "quirk" fix.
  
  [EDIT]: Note C920 webcam is USB 2.0.
  
- (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.
+ c) SIDEBAR: 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 update iterations.
  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.
+ 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, while zoneminder
+ is running.
  
- 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.
+ 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:
   USERPID 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: 

[Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

** Summary changed:

- Renesas / NEC - µPD720202 May also need Quirk in 17.04, no problem in 16.04?  
Logitech C920 Webcam/Zoneminder/Startech
+ Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920 
Webcam/Zoneminder/Startech

-- 
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:
  Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech
  C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Confirmed

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 popular Renesas / NEC - µPD720202 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 Renesas / NEC - µPD720202 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 :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/RenasaSs "quirk" fix.

  [EDIT]: Note C920 webcam is USB 2.0.

  (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:
   USERPID 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:

[Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Curious as to when this fix will propagate into mainline. Haven't looked
into it very deeply, but it seems that kernel/"ubuntu base" updates
trounce the fix.

-- 
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:
  Renesas / NEC - µPD720202 May also need Quirk in 17.04, no problem in
  16.04?  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Confirmed

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 popular Renesas / NEC - µPD720202 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 Renesas / NEC - µPD720202 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 :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/RenasaSs "quirk" fix.

  [EDIT]: Note C920 webcam is USB 2.0.

  (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:
   USERPID 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: 

[Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Title and post edited to reflect actual chipset name Renesas / NEC -
µPD720202 not 27xxx2 as initially and mistakenly reported.

Do not duplicate as new bug.

-- 
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:
  Renesas / NEC - µPD720202 May also need Quirk in 17.04, no problem in
  16.04?  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Confirmed

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 popular Renesas / NEC - µPD720202 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 Renesas / NEC - µPD720202 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 :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/RenasaSs "quirk" fix.

  [EDIT]: Note C920 webcam is USB 2.0.

  (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:
   USERPID 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: 

[Kernel-packages] [Bug 1710548] Re: Renesas / NEC - µPD720202 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

** Summary changed:

- Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?  
Logitech C920 Webcam/Zoneminder/Startech
+ Renesas / NEC - µPD720202 May also need Quirk in 17.04, no problem in 16.04?  
Logitech C920 Webcam/Zoneminder/Startech

** Description changed:

  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
+ The suggestion is that the popular Renesas / NEC - µPD720202 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. 
+ Needed more cams, added Startech  PEXUSB3S44V Renesas / NEC - µPD720202 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. 
+ 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 :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. 
+ b)Noticed it's really a "thing"
+ c)Couldn't find recipe for patching kernel for NEC/RenasaSs "quirk" fix.
+ 
+ [EDIT]: Note C920 webcam is USB 2.0.
  
  (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. 
+ 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. 
+ (Scene 4)
+ Rebooted with new Startech/Nec/Renases 2026 firmware.
  SAME OLD PLETHORA OF ERRORS
  
  (Scene 5)
- I give up. 
+ 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 
+ 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:
-  USERPID 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
+  USERPID 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
+  LANGUAGE=en_US
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB:
-  0 mgadrmfb
-  1 nouveaufb
+  0 mgadrmfb
+  1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d 

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
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:
  Confirmed

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 :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:
   USERPID 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 : 

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

** Tags added: kernel-bug-exists-upstream

-- 
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:
  Confirmed

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 :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:
   USERPID 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   : 

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Placeholder for DMESG attachment after the fix, sorry: file extension
collision.

** Attachment added: "postfix.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+attachment/4934482/+files/postfix.txt

-- 
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 :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:
   USERPID 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

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Placeholder for DMESG attachment after the fix incorporated by  Kai-Heng
Feng in

http://people.canonical.com/~khfeng/linux-
image-4.13.0-rc5+_4.13.0-rc5+-2_amd64.deb

Note well the kernel complaints such as:

[96415.044917] handle_tx_event: 516 callbacks suppressed
[96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

..are gone.


** Attachment added: "DMESG after fix"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+attachment/4934481/+files/post_fix_linux-image-4.13.0-rc5+_4.13.0-rc5+-2_amd64.deb

-- 
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 :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:
   USERPID 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: 

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Dear Kai-Heng Feng,

Sure enough you fixed it. No complaints now.

I'd be very curious to look over the source code changes to improve my
linux-fu.

But that's secondary.

For now I hope an administrator can mark up my bug report to ensure that
the changes you have made get propagated.

Thank you very much for taking my bug report seriously.

-Jeff

-- 
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 :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:
   USERPID 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: 

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Will sit, and think, and talk to you soon.

-- 
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 :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:
   USERPID 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   : 

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Post script: these warnings do not crash or otherwise interfere with
system operation.  ZoneMinder, in particular, `seems to function just
fine.

It's just...annoying and it seems the fix should be simple. Either this
chipset needs quirk, or not.

Does that sound crazy?

-- 
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 :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:
   USERPID 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:

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

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 :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:
   USERPID 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: 

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Placeholder for attachment

** Attachment added: "dmesg.4.13.0rc4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+attachment/4933122/+files/dmesg.4.13.0rc4

-- 
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 :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:
   USERPID 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: 

[Kernel-packages] [Bug 1710548] [NEW] Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Public bug reported:

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 :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:
 USERPID 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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug zesty

** Attachment added: "The Queit B4 The Storm"
   
https://bugs.launchpad.net/bugs/1710548/+attachment/4931944/+files/dmesg.4.txt

-- 
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:
  Confirmed

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