050d:0237 [ASUS P9X79 PRO] The usb driver appears to fail

[tomdean]

This is a Ubuntu kernel regression as the last known good kernel is 3.2.0-38.

I have a Belkin Components F5U237 USB 2.0 7-Port Hub.
I have a USB 3.0 hub connected by a 3.0 cable to a 3.0 port.
I have used this hub for several months with no problem. When I try to access a device, avrisp2, with avrdude, the hub shuts down and I have to reboot to restore it.

WORKAROUND: avrdude works ok with USB 2.0 ports.

>avrdude -c avrisp2 -p x128a1 -P usb -v -t
avrdude: Version 5.11.1, compiled on Oct 30 2011 at 10:37:28
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "/etc/avrdude.conf"
         User configuration file is "/home/tomdean/.avrduderc"
         User configuration file does not exist or is not a regular file, skipping
         Using Port : usb
         Using Programmer : avrisp2
avrdude: usbdev_open(): Found AVRISP mkII, serno: 000200006818
avrdude: usbdev_send(): wrote -19 out of 1 bytes, err = error submitting URB: No such device
avrdude: stk500_send_mk2(): failed to send command to serial port

From dmesg
[ 1884.572420] xhci_hcd 0000:09:00.0: xHCI host not responding to stop endpoint command.
[ 1884.572425] xhci_hcd 0000:09:00.0: Assuming host is dying, halting host.
[ 1884.572453] xhci_hcd 0000:09:00.0: HC died; cleaning up
[ 1884.572500] usb 5-1: USB disconnect, device number 2
[ 1884.572504] usb 5-1.1: USB disconnect, device number 3
[ 1884.572507] usb 5-1.1.1: USB disconnect, device number 4
[ 1884.572510] usb 5-1.1.1.1: USB disconnect, device number 5
[ 1884.572714] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[ 1884.572732] pl2303 5-1.1.1.1:1.0: device disconnected
[ 1884.573182] usb 5-1.1.4: USB disconnect, device number 6

Upstream URL: http://comments.gmane.org/gmane.linux.usb.general/92215

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-38-generic 3.2.0-38.61
ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
Uname: Linux 3.2.0-38-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xfbf20000 irq 94'
   Mixer name : 'Realtek ALC898'
   Components : 'HDA:10ec0899,104384d8,00100003'
   Controls : 46
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xfbe40000 irq 95'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 6
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Wed Mar 6 23:55:20 2013
HibernationDevice: RESUME=UUID=09687087-bd01-4d8c-929a-614a1fe97765
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US ISO-8859-1
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US ISO-8859-1
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-38-generic root=UUID=20bafb22-8eac-422f-950f-e138c450247c ro
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/tomdean not ours.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-38-generic N/A
 linux-backports-modules-3.2.0-38-generic N/A
 linux-firmware 1.79.1
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P9X79 PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd11/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc1-raring/

[tomdean (tomdean)]

kernel-bug-exists-upstream

I downloaded
linux-headers-3.9.0-030900rc1-generic_3.9.0-030900rc1.201303060659_amd64.deb
linux-image-3.9.0-030900rc1-generic_3.9.0-030900rc1.201303060659_amd64.deb
linux-image-extra-3.9.0-030900rc1-generic_3.9.0-030900rc1.201303060659_amd64.deb

# sudo dpkg -i *.deb
...
run-parts: executing /etc/kernel/postinst.d/dkms 3.9.0-030900rc1-generic /boot/v
mlinuz-3.9.0-030900rc1-generic
ERROR (dkms apport): kernel package linux-headers-3.9.0-030900rc1-generic is not
 supported
ERROR (dkms apport): kernel package linux-headers-3.9.0-030900rc1-generic is not
 supported
Error! Bad return status for module build on kernel: 3.9.0-030900rc1-generic (x8
6_64)
Consult /var/lib/dkms/virtualbox/4.1.12/build/make.log for more information.
...
Errors were encountered while processing:
 linux-headers-3.9.0-030900rc1-generic

On reboot, a loop, many times displaying messages like with address 0..127
[ 17.393079] usb 6-1: device not accepting address 8, error -71

Login thru the messages and startx

The bug still exists

On reboot, hung with the message
[...] sd:0:0:0:0 [sda] Synchronizing SCSI cache

Had to press the hardware reset to reboot

[oh (oystein-homelien)]

I think i'm experiencing the same bug. Motherboard: ASUS P9X79 Deluxe, suddenly usb devices on some ports disappear. This appears from kernel:

kernel: [18170.960026] xhci_hcd 0000:06:00.0: xHCI host not responding to stop endpo
kernel: [18170.960033] xhci_hcd 0000:06:00.0: Assuming host is dying, halting host.
kernel: [18170.960074] xhci_hcd 0000:06:00.0: HC died; cleaning up
kernel: [18170.960139] usb 5-2: USB disconnect, device number 2
kernel: [18170.960146] usb 5-2.3: USB disconnect, device number 3
kernel: [18171.011433] usb 5-2.4: USB disconnect, device number 4
kernel: [18171.011438] usb 5-2.4.3: USB disconnect, device number 5
kernel: [18171.011984] usb 6-2: USB disconnect, device number 2

I think the error state remains across soft reboots such that you have to physically power off, but can't test it right now.

It happens with all kinds of devices ranging from usb 1-3, low power (mouse/keyboard), with and without a hub in the port. Since several motherboard ports drop out simultaneously I imagine they are all tied to one usb controller or one internal hub. Very annoying bug, hope this confirmation helps.

[tomdean (tomdean)]

On 08/03/13 22:02, Christopher M. Penalver wrote:
> tomdean, as per
> http://www.asus.com/Motherboards/P9X79_PRO/#support_Download_8 an update
> is available for your BIOS (4104). If you update to this, does it change
> anything?
>

OK. It will be a couple days before I can do that.

# uname -a
Linux P9X79 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux

does not exhibit the bug.

3.2.0-40-generic does exhibit the bug.

Tom Dean

[tomdean (tomdean)]

On 08/03/13 22:02, Christopher M. Penalver wrote:
> tomdean, as per
> http://www.asus.com/Motherboards/P9X79_PRO/#support_Download_8 an update
> is available for your BIOS (4104). If you update to this, does it change
> anything?
>
> If not, could you please both specify what happened, and provide the output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Updating BIOS did not change the failure symptoms.

If I boot linux 3.2.0-40-generic, the system hangs in a loop, presenting
the message:

...

/var/log/syslog:Aug 8 22:47:12 P9X79 kernel: [ 57.496658] usb 6-1:
device not accepting address 20, error -71
/var/log/syslog:Aug 8 22:47:13 P9X79 kernel: [ 58.232589] usb 6-1:
device not accepting address 22, error -71
/var/log/syslog:Aug 8 22:47:14 P9X79 kernel: [ 58.972486] usb 6-1:
device not accepting address 24, error -71
...

forever.

This does not happen with linux 3.2.0-38-generic.

 > uname -a
Linux P9X79 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
 > sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
...
4104
06/18/2013

Tom Dean

[tomdean (tomdean)]

On 08/09/13 04:35, Christopher M. Penalver wrote:
> tomdean, could you please confirm this issue exists with the latest
> development release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,

It will be a couple days before I can do this.

Tom Dean

[tomdean (tomdean)]

On 08/09/13 04:35, Christopher M. Penalver wrote:
> tomdean, could you please confirm this issue exists with the latest
> development release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
> could you please run the following command in the development release
> from a Terminal (Applications->Accessories->Terminal), as it will
> automatically gather and attach updated debug information to this
> report:

I downloaded saucy-desktop-amd64.iso and created a DVD. On Boot, after
some time, a grey screen was presented, with what looked like the header
of several windows overlapped. After 5 minutes, no change.

I switched to the console and the
'device not accepting address 20, error -71' message was scrolling. The
system seemed to be hung in a loop.

With 12.04, the message is presented one time and stops with the login
prompt is presented.

>
> apport-collect -p linux <replace-with-bug-number>

I could not do this. The screen was scrolling too fast to see what I
was typing...

I will attempt later to do it blind, if necessary.

>
> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For example:
> kernel-fixed-upstream-v3.11-rc4
>
> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
> needs-upstream-testing
>

I installed
3.11.0-031100rc4-generic_3.11.0-031100rc4.201308041735_amd64.

The error message is presented in a loop.

Tom Dean

[tomdean (tomdean)]

I do not want to miss something that may be important. The difference I
see in linux 3.2.0-38 and later kernels is the error happening in a loop
in the later versions.

I do not use the desktop. I boot to the console and then startx. I do
not need the desktop and often run without X.

An additional note, the error message is presented on all kernel
versions I have tested.

However, with ubuntu 12.04 and linux 3.2.0-38-generic, the message is
presented one time and then stops when the console login prompt is
presented.

With all later versions of the kernel, the error message is presented in
a loop and makes the machine performance very sluggish, slinky
scrolling, etc.

The following combination presents the error message one time and then
stops.

 > lsb_release -a
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise

 > uname -a
Linux P9X79 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux

Tom Dean

[tomdean (tomdean)]

On 08/09/13 16:43, Christopher M. Penalver wrote:
> tomdean, just to clarify, with the mainline kernel you couldn't test for
> the problem you originally reported about because the computer was
> having performance problems, correct?
>
> ** Tags removed: kernel-bug-exists-upstream-v3.9-rc1 kernel-bug-exists-upstream3.11.0-031100rc4-
> ** Tags added: kernel-bug-exists-upstream-v3.11-rc4
>
> ** Tags removed: kernel-bug-exists-upstream-v3.11-rc4
> ** Tags added: kernel-unable-to-test-upstream-v3.11-rc4
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

[tomdean (tomdean)]

On 08/09/13 16:43, Christopher M. Penalver wrote:
> tomdean, just to clarify, with the mainline kernel you couldn't test for
> the problem you originally reported about because the computer was
> having performance problems, correct?
>
> ** Tags removed: kernel-bug-exists-upstream-v3.9-rc1 kernel-bug-exists-upstream3.11.0-031100rc4-
> ** Tags added: kernel-bug-exists-upstream-v3.11-rc4
>
> ** Tags removed: kernel-bug-exists-upstream-v3.11-rc4
> ** Tags added: kernel-unable-to-test-upstream-v3.11-rc4
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

I could not test the Ubuntu iso image bacause of the scrolling error
message. I did test the mainline kernel.

The computer was NOT having performance problems.

I performed the kernel test and the tags I added were correct. The
system hung in a loop.

I tested this kernel:

linux-headers-3.11.0-031100rc4-generic_3.11.0-031100rc4.201308041735_amd64.deb

linux-headers-3.11.0-031100rc4_3.11.0-031100rc4.201308041735_all.deb

linux-image-3.11.0-031100rc4-generic_3.11.0-031100rc4.201308041735_amd64.deb

The error messages are continuous. For more than ten minutes, I watched
the error messages scroll on the console. I blindly typed startx and X
started. The system response was very sluggish, with slinky scrolling.

Tom Dean

[tomdean (tomdean)]

On 08/10/13 01:32, Christopher M. Penalver wrote:
> tomdean, did this problem not occur in a release prior to Precise?
>

I do not know. I do not have prior releases. I did not have the USB
3.0 hub prior to my reporting the problem. I reported this problem the
first time I connected the 3.0 hub to my computer.

The problem is not that the error message happens. The problem is that
with linux after 3.2.0-38-generic, the error happens in a loop, forever.
  That has a severe impact on system performance.

The important part of the previous sentence is 'in a loop'. Linux is
distinct from Ubuntu. I can boot different kernels from Ubuntu 12.04.2
LTS at the grub prompt.

I outlined the following to make the two cases distinct. I am sorry if
I caused confusion by having two cases in one response.

The good case: Boot Ubuntu 12.04 with linux 3.2.0-38 from grub
========================================================================
=
= With the following combination, the looping and degraded performance =
does NOT happen.
=
= > lsb_release -a
= LSB Version: core-2.0-amd64:core-2.0-noarch:core-
= 3.0-amd64:core-=3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-
= 3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
= Distributor ID: Ubuntu
= Description: Ubuntu 12.04.2 LTS
= Release: 12.04
= Codename: precise
=
= > uname -a
= Linux P9X79 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC
= 2013 x86_64 x86_64 x86_64 GNU/Linux
=
= The message appears one time for each failed address assignment. And
= then stops. There is NO looping. There is NO slinky scrolling. The
= system response is very good.
=
=======================================================================

The failed case: Boot Ubuntu 12.04 with linux 3.2.0-40 from grub
=======================================================================
=
= If I reboot and select linux 3.2.0-40 or linux 3.2.0-51 from the grub
= menu, the looping happens and system performance is seriously
= degraded. This has happened with a couple other linux kernels, but,
= I did not keep them installed.
=
= Note that I am still running Ubuntu 12.04.2 LTS, just a different
= kernel.
=
= If I watch the console, the error messages scroll by continuously! I
= have not watched for more than 10 minutes, but, at least that long.
= The one time I did startx while the looping condition existed, I may
= have used the system for another 5 minutes, or so, with sluggish
= response ane slinky scrolling
=
=======================================================================

I hope this is clear.

I can boot the failing case and attempt to generate some information
from there, if that will help.

What can I do to help?

Tom Dean

[tomdean (tomdean)]

On 08/10/13 13:12, Christopher M. Penalver wrote:
> tomdean, could you please unplug all USB devices from your computer, plug in just the hub with nothing further attached in it, and then immediately place the following in a terminal and attach the results:
> lsusb -v > lsusb-v.log
>
> ** Tags removed: regression-potential
> ** Tags added: regression-updated
>

I have USB keyboard and mouse, which are by necessity connected to a USB
2.0 hub, Bus 002 Device 004. There is nothing connected to the USB 3.0 hub.

I attached the output of

 > sudo lsusb -v > lsusb-v.log

tomdean

[tomdean (tomdean)]

On 08/10/13 14:00, Christopher M. Penalver wrote:
> tomdean, the next step would be to perform a Ubuntu kernel bisect from
> 3.2.0-38 to 3.2.0-40, in order to identify the offending commit. Could
> you please do this following
> https://wiki.ubuntu.com/Kernel/KernelBisection ?

The problem does NOT exist in Linux 3.2.0-38.

The problem does exist in Linux 3.2.0-39

Tom Dean

[tomdean (tomdean)]

On 08/10/13 17:26, Christopher M. Penalver wrote:
> tomdean, the next step would be to perform a Ubuntu kernel commit bisect
> from 3.2.0-38 to 3.2.0-39, in order to identify the offending commit.
> Could you please do this following
> https://wiki.ubuntu.com/Kernel/KernelBisection ?
>
> ** Tags added: needs-commit-bisect
>
git bisect log attached.

d8ce3e9cc24d4e901b21de013ee821c5ca34c34f is the first bad commit
commit d8ce3e9cc24d4e901b21de013ee821c5ca34c34f
Author: Sarah Sharp <email address hidden>
Date: Wed Nov 14 16:42:32 2012 -0800

Tom Dean

[tomdean (tomdean)]

On 08/11/13 01:34, tomdean wrote:

I filed an upstream report. I CC'd the Bug 1151622, but, launchpad
refused the CC.

Error message:

The message you sent included commands to modify the bug report,
but you didn't sign the message with an OpenPGP key that is
registered in Launchpad.

The upstream report is attached.

Tom Dean

[tomdean (tomdean)]

On 08/11/13 15:41, Greg KH wrote:

I tried linux 3.2.0-40, 3.2.0-5, 3.9.0-7, and, 3.10.5-031005.

The problem started back in 3.2.0-39. Here is a git bisect log

# bad: [ba89d2a7ca8233e29c9fdeabefb7fdbb6775626e] UBUNTU: Ubuntu-3.2.0-39.62
# good: [1420ada1a002d99e49d68d60a72f29ba58376b90] UBUNTU:
Ubuntu-3.2.0-38.61
git bisect start 'Ubuntu-3.2.0-39.62' 'Ubuntu-3.2.0-38.61'
# bad: [a5ba0135bd4ff188ab86297f584113fe25746dd9] can: pch_can: fix
invalid erro
r codes
git bisect bad a5ba0135bd4ff188ab86297f584113fe25746dd9
# bad: [b5b458764552cd7f88b5d11560c076b1ccd3d1f9] PCI: pciehp: Fix wrong
workque
ue cleanup
git bisect bad b5b458764552cd7f88b5d11560c076b1ccd3d1f9
# bad: [92d955046ac4671e71c3f1289eac21bf2f4bf1f0] staging: r8712u: Add
new devic
e ID
git bisect bad 92d955046ac4671e71c3f1289eac21bf2f4bf1f0
# good: [57aacdf465bca560b40b502c51f42ad8b2381b30] USB: Ignore xHCI
Reset Device
  status.
git bisect good 57aacdf465bca560b40b502c51f42ad8b2381b30
# bad: [bd16a66a754bae16fd65187f145e9d3d538acdc1] ASoC: wm5100: Remove
DSP B and
  left justified formats
git bisect bad bd16a66a754bae16fd65187f145e9d3d538acdc1
# bad: [695b3de0f04703d3effa0ccdcb6bd6327d302fe3] USB: Ignore port state
until r
eset completes.
git bisect bad 695b3de0f04703d3effa0ccdcb6bd6327d302fe3
# bad: [4a4e15fb9e182d8e787048ef0f981419a9422279] USB: Increase reset
timeout.
git bisect bad 4a4e15fb9e182d8e787048ef0f981419a9422279
# bad: [d8ce3e9cc24d4e901b21de013ee821c5ca34c34f] USB: Allow USB 3.0
ports to be
  disabled.
git bisect bad d8ce3e9cc24d4e901b21de013ee821c5ca34c34f

Tom Dean

[tomdean (tomdean)]

I removed the USB 3.0 hub and disabled 3.0 support in BIOS.

If I boot any kernel after

> uname -a
Linux P9X79 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I get slinky scrolling in any xterm. This looks like the system is heavily loaded. But, top shows no activity.

How may I isolate this problem?

[tomdean (tomdean)]

Here is a copy of the upstream report.

I tested the latest kernel, 3.12.0-031200rc7-generic and the problem is there. But, not with 3.2.0-38-generic

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[tomdean (tomdean)]

On 01/02/14 20:17, Launchpad Bug Tracker wrote:
> [Expired for linux (Ubuntu) because there has been no activity for 60
> days.]
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Expired
>
Will this ever be fixed?

[tomdean (tomdean)]

On 01/02/14 21:38, Christopher M. Penalver wrote:
> tomdean, please see
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151622/comments/30
> .
>
No, I do not have a direct web link to the post.

[tomdean (tomdean)]

On 01/02/14 21:38, Christopher M. Penalver wrote:
> tomdean, please see
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151622/comments/30
> .
>
http://comments.gmane.org/gmane.linux.usb.general/92215

Is this it?

[penalvch (penalvch)]

tomdean, thank you for the URL. I see what happened in why your post was largely ignored, as it was because you didn't follow the directions in noting everything in the upstream kernel, you did everything in downstream. So, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/ and if reproducible, repost to linux-usb following *verbatim* https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your new e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[tomdean (tomdean)]

On 01/02/14 22:33, Christopher M. Penalver wrote:
> tomdean, thank you for the URL. I see what happened in why your post was
> largely ignored, as it was because you didn't follow the directions in
> noting everything in the upstream kernel, you did everything in
> downstream. So, could you please test the latest mainline kernel via
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/ and if
> reproducible, repost to linux-usb following *verbatim*
> https://wiki.ubuntu.com/Bugs/Upstream/kernel ?
>
> Please provide a direct URL to your new e-mail to the mailing list once
> you have made it so that it may be tracked.
>
> Thank you for your understanding.
>
> ** Tags added: needs-upstream-testing
>
> ** Attachment removed: "Copy og the Upstream Report"
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151622/+attachment/3898898/+files/upstream-report
>

It will be several days before this can be done - the machine is in use.

tomdean

[tomdean (tomdean)]

On 01/02/14 22:33, Christopher M. Penalver wrote:

The looping in the USB driver with the message about failure to assign
address with a USB 3.0 device is not there with the latest kernel.

 > uname -a
Linux P9X79 3.13.0-031300rc6-generic #201312291935 SMP Mon Dec 30
00:37:05 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

However, the slinky scroll is present with the latest kernel. The
slinky scroll is not present in the 3.2.0-38-generic kernel.

I am using X and twm.

To demo this, I do ls -R to get a lot of lines in the xterm buffer.
Then, with the mouse, grab the scroll bar and move up at a medium speed
so the display attempts to keep up with the scrolling. The result is a
slinky scroll. There are no error messages. top does not show any
activity other than Xorg, which goes to 90% of one cpu. With the
3.2.0-38-generic kernel, the slinky scroll does not happen.

The slinky scroll happens with all kernels I have tried, after
3.2.0-38-generic.

How do I isolate this?

Tom Dean

[tomdean (tomdean)]

On 01/02/14 22:33, Christopher M. Penalver wrote:
Booting

 > uname -a
Linux P9X79 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux

and repeating the scroll test does not result in a slinky scroll and top
shows Xorg using 15% of one cpu, max.

Something after 3.2.0-38-generic, starting with 3.2.0-39-generic is
causing this problem.

I am using a USB keyboard and mouse, so I suspect the USB subsystem. I
have the USB 3.0 on board device disabled in BIOS and no USB 3.0 devices
are attached.

Adding a significant load to the system, 5 processes using 100% of a cpu
does not produce the slinky scroll.

Tom Dean

[penalvch (penalvch)]

tomdean, thank you for testing the v3.13-rc6 mainline kernel. Just to clarify, regarding only the issue mentioned in the Bug Description about accessing the avrisp2, with avrdude when plugged into the Belking Hub, the problem is not reproducible, correct?

[tomdean (tomdean)]

On 01/06/14 14:02, Christopher M. Penalver wrote:
> tomdean, thank you for testing the v3.13-rc6 mainline kernel. Just to
> clarify, regarding only the issue mentioned in the Bug Description about
> accessing the avrisp2, with avrdude when plugged into the Belking Hub,
> the problem is not reproducible, correct?
>

Correct.

Question: How do I trace/report the slinky scroll?

To demonstrate, open an xterm. Reposition the xterm (grab the top bar
and move the xterm left or right about 1/4 its width). The xterm is
redrawn from the top down, taking on the order or 1 second.

Alternately, open an xterm with a 1000 line buffer. execute ls several
times to put several hundred lines in the buffer. Scroll up (grab the
scroll bar and drag it up). The text in the xterm is displayed like a
slinky scroll.

This effect is not present with kernel 3.2.0-38-generic. But, is
present in kernels 3.2.0-39-generic and later. At least all I have
tested, up to and including:

 > uname -a
Linux P9X79 3.13.0-031300rc6-generic #201312291935 SMP Mon Dec 30
00:37:05 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

With kernels 3.2.0-39-generic and later, top shows Xorg using 70% to
100% of one CPU when demonstrating the effect.

With kernel 3.2.0-38-generic, this is 20% to 30%.

Tom Dean

[penalvch (penalvch)]

tomdean, thank you for providing the requested information. As Trusty has been rebased to the 3.13.x series kernel, could you please test this and advise to the results via http://cdimage.ubuntu.com/daily-live/current/ ?

[tomdean (tomdean)]

On 01/09/14 14:41, Christopher M. Penalver wrote:
> tomdean, thank you for providing the requested information. As Trusty
> has been rebased to the 3.13.x series kernel, could you please test this
> and advise to the results via http://cdimage.ubuntu.com/daily-
> live/current/ ?
>

I tried the daily build of Jan 9. Kernel 3.13.0-1-generic, Ubuntu
Trusty Tahr, 14.04.

The USB 3.0 hub works with a USB disk drive. I could not test avrdude.

It appears the slinky scroll is not present.

I do not use the Gnome Desktop, just X11, twm and xterms on the 12.04
system.

In the 14.04 system, I started a gnome terminal and from that started an
xterm. Moving the xterm does not have the slinky drawing. Filling the
xterm with lines and scrolling up does not have the slinky scrolling.

It is possible to install 14.04 on a spare disk in a week, or so. Then,
if I can remember what I did to eliminate the gnome desk top, I may be
able to do the test exactly.

However, I believe the symptoms I observed will not be present in a
14.04 installation that is configured the same as 12.04.

Tom Dean

[tomdean (tomdean)]

I have Ubuntu 12.04 as a primary desktop. The hardware is a P9X79
motherboard with USB keyboard and USB mouse. I do not use Unity, etc. I
start TWM and use xterm most of the time.

If I boot linux-3.2.0-38-generic (Ubuntu 12.04), and fill the xterm
buffer with lines of text (repeat ls;ls;...;ls) and then grab the left
scroll bar with mouse-center button and scroll up, the effect is a
smooth scrolling of the text lines.

If I boot linux-3.2.0-39-generic (Ubuntu 12.04), or later linux kernel,
and fill the xterm buffer with lines of text (repeat ls;ls;...;ls) and
then grab the left scroll bar with mouse-center button and scroll up,
the effect is a slinky scroll of the text. The latest kernel I have is
linux-3.13.0-1, which has the slinky scroll.

I installed Ubuntu 14.04 on a spare disk and configured it similar to
the 12.04 system. After updating, it now runs Linux 3.13.0-6-generic.
If I fill the xterm buffer with lines of text (repeat ls;ls;...;ls) and
then grab the left scroll bar with mouse-center button and scroll up,
the effect is a smooth scrolling of the text lines.

Question: It appears the slinky scroll is related to Ubuntu 12.04, not
the particular kernel. Is this true?

Tom Dean

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[penalvch (penalvch)]

tomdean, just to clarify, in Trusty you may use the USB 3.0 hub on a USB 3.0 port as desired with avrdude?

[tomdean (tomdean)]

On 04/06/14 15:21, Christopher M. Penalver wrote:

I connected a USB disk to the 3.0 hub. I read 20 to 25 GB from the
disk. I did not write to it because of existing data on the disk.

I connected the Atmel ISP to the 3.0 hub and tried to access it with
avrdude3. Failed. The results are at the bottom.

I have a wired USB keyboard and mouse. The response is much better in
Trusty.

Tom Dean

 > lsusb
Bus 002 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011
Bluetooth
Bus 002 Device 006: ID 045e:0768 Microsoft Corp. Sidewinder X4
Bus 002 Device 007: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 002 Device 003: ID 050d:0237 Belkin Components F5U237 USB 2.0 7-Port Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 2109:0810
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 005: ID 03eb:2104 Atmel Corp. AVR ISP mkII
Bus 005 Device 004: ID 2109:2812
Bus 005 Device 003: ID 2109:2812
Bus 005 Device 002: ID 2109:3431
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 > sudo avrdude -c avrisp2 -p x128a1 -Pusb -v -t
[sudo] password for tomdean:

avrdude: Version 6.0.1, compiled on Oct 21 2013 at 15:55:32
          Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
          Copyright (c) 2007-2009 Joerg Wunsch

          System wide configuration file is "/etc/avrdude.conf"
          User configuration file is "/home/tomdean/.avrduderc"
          User configuration file does not exist or is not a regular
file, skipping

          Using Port : usb
          Using Programmer : avrisp2
avrdude: usbdev_open(): Found AVRISP mkII, serno: 000200006818
avrdude: usbdev_send(): wrote -19 out of 1 bytes, err = error submitting
URB: No such device
avrdude: stk500_send_mk2(): failed to send command to serial port
 > sudo avrdude -c avrisp2 -p x128a1 -Pusb -v -t

avrdude: Version 6.0.1, compiled on Oct 21 2013 at 15:55:32
          Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
          Copyright (c) 2007-2009 Joerg Wunsch

          System wide configuration file is "/etc/avrdude.conf"
          User configuration file is "/home/tomdean/.avrduderc"
          User configuration file does not exist or is not a regular
file, skipping

          Using Port : usb
          Using Programmer : avrisp2
avrdude: usbdev_open(): did not find any USB device "usb"
 > lsusb
Bus 002 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011
Bluetooth
Bus 002 Device 006: ID 045e:0768 Microsoft Corp. Sidewinder X4
Bus 002 Device 007: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 002 Device 003: ID 050d:0237 Belkin Components F5U237 USB 2.0 7-Port Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device ...

[tomdean (tomdean)]

I upgraded to Ubuntu 14.04 LTS.

The problems and artifacts I saw with 12.04 LTS are not present.

Thank you,
Tom Dean

[penalvch (penalvch)]

tomdean, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151622/comments/49 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.