from:"Mike Gerow"

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

2016-07-29 Thread Mike Gerow

Of course. The device itself doesn't have any interesting markings, but
luckily I still have the packaging it came in too.

** Attachment added: "IMG_20160729_134607.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/4709935/+files/IMG_20160729_134607.jpg

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged

Bug description:
  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm
  still digging around to try and figure out why this doesn't seem to be
  working, but I was wondering if you all had any idea what might be
  going pear-shaped here.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+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 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

2016-07-29 Thread Mike Gerow

And the other side.

** Attachment added: "IMG_20160729_134619.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/4709936/+files/IMG_20160729_134619.jpg

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged

Bug description:
  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm
  still digging around to try and figure out why this doesn't seem to be
  working, but I was wondering if you all had any idea what might be
  going pear-shaped here.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+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 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

2016-06-20 Thread Mike Gerow

Sadly no, I only saw it happen once and I have no idea what might have
caused it. The one and only time I saw it was with the 4.2 kernel,
though.

I don't have access to the machine that it happened on anymore,
unfortunately, but I'll see if I can reproduce the issue on another
machine I have access to.

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

Title:
  Transient panic on boot with wily proposed kernel (4.2.0-39)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Attached picture of panic, although there's not really much there. It
  kinda looks like init has decided to kill itself.

  It's only happened once in the three times I've booted into the new
  kernel. I haven't had a chance to test it more beyond that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593835/+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 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

2016-06-17 Thread Mike Gerow

If none of y'all are seeing anything like this in the proposed kernel I
wouldn't be surprised if it has something to do with my setup, so this
bug probably shouldn't block the release.

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

Title:
  Transient panic on boot with wily proposed kernel (4.2.0-39)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Attached picture of panic, although there's not really much there. It
  kinda looks like init has decided to kill itself.

  It's only happened once in the three times I've booted into the new
  kernel. I haven't had a chance to test it more beyond that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593835/+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 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

2016-06-17 Thread Mike Gerow

Company policy disables apport, but if there's anything specific I'm
happy to provide it.

** 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/1593835

Title:
  Transient panic on boot with wily proposed kernel (4.2.0-39)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Attached picture of panic, although there's not really much there. It
  kinda looks like init has decided to kill itself.

  It's only happened once in the three times I've booted into the new
  kernel. I haven't had a chance to test it more beyond that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593835/+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 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

2016-06-17 Thread Mike Gerow

Also relevant, I have installed a few dkms modules that could be causing
trouble (including one that is unfortunately closed-source and that I
can't share...):

$ dkms status -k 4.2.0-39-generic
bbswitch, 0.7, 4.2.0-39-generic, x86_64: installed
hpuefi, 1.0.3+gg8, 4.2.0-39-generic, x86_64: installed
nvidia-340, 340.96, 4.2.0-39-generic, x86_64: installed

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

Title:
  Transient panic on boot with wily proposed kernel (4.2.0-39)

Status in linux package in Ubuntu:
  New

Bug description:
  Attached picture of panic, although there's not really much there. It
  kinda looks like init has decided to kill itself.

  It's only happened once in the three times I've booted into the new
  kernel. I haven't had a chance to test it more beyond that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593835/+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 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

2016-06-17 Thread Mike Gerow

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593835/+attachment/4685754/+files/lspci-vnvn.log

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

Title:
  Transient panic on boot with wily proposed kernel (4.2.0-39)

Status in linux package in Ubuntu:
  New

Bug description:
  Attached picture of panic, although there's not really much there. It
  kinda looks like init has decided to kill itself.

  It's only happened once in the three times I've booted into the new
  kernel. I haven't had a chance to test it more beyond that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593835/+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 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

2016-06-17 Thread Mike Gerow

$ cat /proc/version_signature 
Ubuntu 4.2.0-39.46~14.04.1-generic 4.2.8-ckt11

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

Title:
  Transient panic on boot with wily proposed kernel (4.2.0-39)

Status in linux package in Ubuntu:
  New

Bug description:
  Attached picture of panic, although there's not really much there. It
  kinda looks like init has decided to kill itself.

  It's only happened once in the three times I've booted into the new
  kernel. I haven't had a chance to test it more beyond that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593835/+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 1593835] [NEW] Transient panic on boot with wily proposed kernel (4.2.0-39)

2016-06-17 Thread Mike Gerow

Public bug reported:

Attached picture of panic, although there's not really much there. It
kinda looks like init has decided to kill itself.

It's only happened once in the three times I've booted into the new
kernel. I haven't had a chance to test it more beyond that.

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

** Attachment added: "IMG_20160617_113834.jpg"
   
https://bugs.launchpad.net/bugs/1593835/+attachment/4685752/+files/IMG_20160617_113834.jpg

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

Title:
  Transient panic on boot with wily proposed kernel (4.2.0-39)

Status in linux package in Ubuntu:
  New

Bug description:
  Attached picture of panic, although there's not really much there. It
  kinda looks like init has decided to kill itself.

  It's only happened once in the three times I've booted into the new
  kernel. I haven't had a chance to test it more beyond that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593835/+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 1582864] Re: use after free of BOS in usb_reset_and_verify_device

2016-06-17 Thread Mike Gerow

$ uname -a
Linux gerow0 4.2.0-39-generic #46~14.04.1-Ubuntu SMP Mon Jun 13 15:40:38 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

No oopses in wily, verified. Booting into vivid next.

** Tags removed: verification-needed-wily
** Tags added: verification-done-wily

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

Title:
  use after free of BOS in usb_reset_and_verify_device

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Should be fixed with upstream commit
  e5bdfd50d6f76077bf8441d130c606229e100d40, which reverts upstream
  commit d8f00cd685f5c8e0def8593e520a7fef12c22407.

  With slub_debug enabled this manifests as a deref of 0x6b6b... in
  usb_disable_ltm

  [  218.235302] general protection fault:  [#1] SMP 
  [  218.235311] Modules linked in: usb_storage tcp_diag inet_diag iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables autofs4 rpcsec_gss_krb5 rfcomm bnep bluetooth 
snd_hda_codec_hdmi binfmt_misc nvidia(POX) snd_hda_codec_realtek snd_hda_intel 
snd_usb_audio snd_hda_codec snd_usbmidi_lib uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core snd_hwdep snd_seq_midi joydev snd_pcm videodev 
snd_page_alloc snd_seq_midi_event nfsd snd_rawmidi snd_seq auth_rpcgss 
parport_pc nfs_acl ppdev nfs lockd sunrpc fscache honeevent(OX) snd_seq_device 
snd_timer snd drm lp parport sb_edac mei_me hp_wmi sparse_keymap gpio_ich 
hpuefi(OX) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm soundcore edac_core mei serio_raw tpm_infineon lpc_ich mac_hid wmi shpchp 
dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse isci e1000e ahci 
libsas lib
 ahci ptp pps_core scsi_transport_sas pata_acpi
  [  218.235410] CPU: 15 PID: 243 Comm: khubd Tainted: P   OX 
3.13.0-85-generic #129-Ubuntu
  [  218.235414] Hardware name: Hewlett-Packard HP Z620 Workstation/158A, BIOS 
J61 v03.87 02/09/2015
  [  218.235418] task: 8807eff98000 ti: 8807effa task.ti: 
8807effa
  [  218.235421] RIP: 0010:[]  [] 
usb_disable_ltm+0x56/0xb0
  [  218.235437] RSP: 0018:8807effa1cd0  EFLAGS: 00010202
  [  218.235440] RAX:  RBX: 8807ea532e68 RCX: 

  [  218.235443] RDX: 6b6b6b6b6b6b6b6b RSI: 00300021 RDI: 
8807ea532e68
  [  218.235446] RBP: 8807effa1d08 R08:  R09: 

  [  218.235449] R10: 8807ff804240 R11: 8136d2a1 R12: 

  [  218.235451] R13: 8807ebddd480 R14: 0001 R15: 
0012
  [  218.235455] FS:  () GS:88101fce() 
knlGS:
  [  218.235458] CS:  0010 DS:  ES:  CR0: 80050033
  [  218.235461] CR2: 013b1c08 CR3: 01c0e000 CR4: 
000407e0
  [  218.235463] Stack:
  [  218.235465]  81551236 8807ea532ef0  
8807ea532e68
  [  218.235476]  8807ea532ef0 8807ebddbf60  
8807effa1d48
  [  218.235483]  81545c4d 8807ea532f50 8807ebddb4d0 
02a0
  [  218.235490] Call Trace:
  [  218.235499]  [] ? usb_disable_device+0x126/0x290
  [  218.235506]  [] usb_disconnect+0xad/0x200
  [  218.235511]  [] hub_port_connect_change+0xd3/0xb20
  [  218.235518]  [] ? hub_port_status+0xdd/0x120
  [  218.235523]  [] hub_events+0x4d4/0xa20
  [  218.235528]  [] hub_thread+0x35/0x160
  [  218.235535]  [] ? prepare_to_wait_event+0x100/0x100
  [  218.235540]  [] ? hub_events+0xa20/0xa20
  [  218.235549]  [] kthread+0xd2/0xf0
  [  218.235554]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [  218.235564]  [] ret_from_fork+0x58/0x90
  [  218.235570]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [  218.235572] Code: e9 48 8b 52 10 48 85 d2 74 e0 f6 42 03 02 74 da 83 7f 1c 
05 75 d4 48 8b 97 40 03 00 00 48 85 d2 74 c8 48 8b 52 10 48 85 d2 74 bf  42 
03 02 74 b9 48 83 bf 50 03 00 00 00 74 af 55 45 31 c9 41 
  [  218.235618] RIP  [] usb_disable_ltm+0x56/0xb0
  [  218.235624]  RSP 
  [  218.235655] ---[ end trace 954cac763165b767 ]---

  Without slub_debug you end up getting a double free and messing up the
  allocator and apparmor tends to be the first one to notice:

  [  574.027518] hub 4-0:1.0: Cannot enable port 3.  Maybe the USB cable is bad?
  [  574.548076] usb 4-3: USB disconnect, device number 2
  [  576.040995] [ cut here ]
  [  576.041003] WARNING: CPU: 17 PID: 11627 at 
/build/linux-03BQvT/linux-3.13.0/include/linux/kref.h:47 
apparmor_file_alloc_security+0x167/0x180()
  [  576.041005] Modules linked in: tcp_diag inet_diag xt_u32 ip6t_REJECT

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

2016-06-17 Thread Mike Gerow

$ uname -a
Linux gerow0 3.19.0-62-generic #70~14.04.1-Ubuntu SMP Mon Jun 13 16:30:31 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

No oopses in vivid either, verified.

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

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

Title:
  use after free of BOS in usb_reset_and_verify_device

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Should be fixed with upstream commit
  e5bdfd50d6f76077bf8441d130c606229e100d40, which reverts upstream
  commit d8f00cd685f5c8e0def8593e520a7fef12c22407.

  With slub_debug enabled this manifests as a deref of 0x6b6b... in
  usb_disable_ltm

  [  218.235302] general protection fault:  [#1] SMP 
  [  218.235311] Modules linked in: usb_storage tcp_diag inet_diag iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables autofs4 rpcsec_gss_krb5 rfcomm bnep bluetooth 
snd_hda_codec_hdmi binfmt_misc nvidia(POX) snd_hda_codec_realtek snd_hda_intel 
snd_usb_audio snd_hda_codec snd_usbmidi_lib uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core snd_hwdep snd_seq_midi joydev snd_pcm videodev 
snd_page_alloc snd_seq_midi_event nfsd snd_rawmidi snd_seq auth_rpcgss 
parport_pc nfs_acl ppdev nfs lockd sunrpc fscache honeevent(OX) snd_seq_device 
snd_timer snd drm lp parport sb_edac mei_me hp_wmi sparse_keymap gpio_ich 
hpuefi(OX) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm soundcore edac_core mei serio_raw tpm_infineon lpc_ich mac_hid wmi shpchp 
dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse isci e1000e ahci 
libsas lib
 ahci ptp pps_core scsi_transport_sas pata_acpi
  [  218.235410] CPU: 15 PID: 243 Comm: khubd Tainted: P   OX 
3.13.0-85-generic #129-Ubuntu
  [  218.235414] Hardware name: Hewlett-Packard HP Z620 Workstation/158A, BIOS 
J61 v03.87 02/09/2015
  [  218.235418] task: 8807eff98000 ti: 8807effa task.ti: 
8807effa
  [  218.235421] RIP: 0010:[]  [] 
usb_disable_ltm+0x56/0xb0
  [  218.235437] RSP: 0018:8807effa1cd0  EFLAGS: 00010202
  [  218.235440] RAX:  RBX: 8807ea532e68 RCX: 

  [  218.235443] RDX: 6b6b6b6b6b6b6b6b RSI: 00300021 RDI: 
8807ea532e68
  [  218.235446] RBP: 8807effa1d08 R08:  R09: 

  [  218.235449] R10: 8807ff804240 R11: 8136d2a1 R12: 

  [  218.235451] R13: 8807ebddd480 R14: 0001 R15: 
0012
  [  218.235455] FS:  () GS:88101fce() 
knlGS:
  [  218.235458] CS:  0010 DS:  ES:  CR0: 80050033
  [  218.235461] CR2: 013b1c08 CR3: 01c0e000 CR4: 
000407e0
  [  218.235463] Stack:
  [  218.235465]  81551236 8807ea532ef0  
8807ea532e68
  [  218.235476]  8807ea532ef0 8807ebddbf60  
8807effa1d48
  [  218.235483]  81545c4d 8807ea532f50 8807ebddb4d0 
02a0
  [  218.235490] Call Trace:
  [  218.235499]  [] ? usb_disable_device+0x126/0x290
  [  218.235506]  [] usb_disconnect+0xad/0x200
  [  218.235511]  [] hub_port_connect_change+0xd3/0xb20
  [  218.235518]  [] ? hub_port_status+0xdd/0x120
  [  218.235523]  [] hub_events+0x4d4/0xa20
  [  218.235528]  [] hub_thread+0x35/0x160
  [  218.235535]  [] ? prepare_to_wait_event+0x100/0x100
  [  218.235540]  [] ? hub_events+0xa20/0xa20
  [  218.235549]  [] kthread+0xd2/0xf0
  [  218.235554]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [  218.235564]  [] ret_from_fork+0x58/0x90
  [  218.235570]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [  218.235572] Code: e9 48 8b 52 10 48 85 d2 74 e0 f6 42 03 02 74 da 83 7f 1c 
05 75 d4 48 8b 97 40 03 00 00 48 85 d2 74 c8 48 8b 52 10 48 85 d2 74 bf  42 
03 02 74 b9 48 83 bf 50 03 00 00 00 74 af 55 45 31 c9 41 
  [  218.235618] RIP  [] usb_disable_ltm+0x56/0xb0
  [  218.235624]  RSP 
  [  218.235655] ---[ end trace 954cac763165b767 ]---

  Without slub_debug you end up getting a double free and messing up the
  allocator and apparmor tends to be the first one to notice:

  [  574.027518] hub 4-0:1.0: Cannot enable port 3.  Maybe the USB cable is bad?
  [  574.548076] usb 4-3: USB disconnect, device number 2
  [  576.040995] [ cut here ]
  [  576.041003] WARNING: CPU: 17 PID: 11627 at 
/build/linux-03BQvT/linux-3.13.0/include/linux/kref.h:47 
apparmor_file_alloc_security+0x167/0x180()
  [  576.041005] Modules linked in: tcp_diag inet_diag xt_u32 ip6t_REJECT 
nf_conntrack_ipv6

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

2016-05-27 Thread Mike Gerow

And by "doesn't seem to have the same issue" I mean I still get the
"Stop submitting intr, status -71" error when disconnecting the device,
but it doesn't seem to randomly stop working between when I initially
plug it in and some time in the future (probably averages around 15
minutes).

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm
  still digging around to try and figure out why this doesn't seem to be
  working, but I was wondering if you all had any idea what might be
  going pear-shaped here.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+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 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

2016-05-27 Thread Mike Gerow

If it's any help at all: my personal laptop running Debian unstable
doesn't seem to have the same issue with this device (it's on 4.5.0).

Also, this adapter specifically is the "Monoprice USB3.0 Gigabit
Ethernet Adapter" , which
is Realtek 8153-based as the bug title mentions.

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm
  still digging around to try and figure out why this doesn't seem to be
  working, but I was wondering if you all had any idea what might be
  going pear-shaped here.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+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 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

2016-05-27 Thread Mike Gerow

Yes, I've only specifically checked trusty, wily, and the 4.6 kernel
from .

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm
  still digging around to try and figure out why this doesn't seem to be
  working, but I was wondering if you all had any idea what might be
  going pear-shaped here.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+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 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

2016-05-26 Thread Mike Gerow

Oh, and here's the full dmesg output from the 4.6 run.

** Attachment added: "dmesg.mainline"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/4670966/+files/dmesg.mainline

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

Status in linux package in Ubuntu:
  New

Bug description:
  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm
  still digging around to try and figure out why this doesn't seem to be
  working, but I was wondering if you all had any idea what might be
  going pear-shaped here.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+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 1586195] [NEW] Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

2016-05-26 Thread Mike Gerow

Public bug reported:

Seems to be paired with dmesg entries like this on the trusty kernel:

[24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
[24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
[24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
[24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
[24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
[24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
[24763.809953] .
[24763.810579] usb 4-4.2: USB disconnect, device number 7
[24763.940765] userif-1: sent link down event.
[24763.940769] userif-1: sent link up event.

And like this on mainline:

[  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
[  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
[  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
[  259.752921] usb 4-3: Manufacturer: Realtek
[  259.752922] usb 4-3: SerialNumber: 0100
[  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
[  259.993254] r8152 4-3:1.0 eth0: v1.08.3
[  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
[  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
[  302.832697] .
[  302.833086] usb 4-3: USB disconnect, device number 4

Mainline version fyi:
[0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 
5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 
UTC 2016

I also get a similar message about 'Failed to disable LTM' if I just
unplug the device before the breakage occurs.

I've attached lsusb before the breakage occurs (so you can see the
device) from the mainline kernel.

Interestingly it appears the drivers on trusty and wily/mainline are
different (r815x vs r8152) yet still exhibit similar troubles. I'm still
digging around to try and figure out why this doesn't seem to be
working, but I was wondering if you all had any idea what might be going
pear-shaped here.

Thanks!

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

** Attachment added: "lsusb.before"
   
https://bugs.launchpad.net/bugs/1586195/+attachment/4670965/+files/lsusb.before

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

Status in linux package in Ubuntu:
  New

Bug description:
  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

2016-05-25 Thread Mike Gerow

Looks good! Started with slub_debug and not seeing any Oopses when
uplugging usb3 storage.

$ uname -rsov
Linux 3.13.0-87-generic #133-Ubuntu SMP Tue May 24 18:32:09 UTC 2016 GNU/Linux

$ dmesg
...
[   79.103213] usb 4-3: new SuperSpeed USB device number 2 using xhci_hcd
[   79.121274] usb 4-3: Parent hub missing LPM exit latency info.  Power 
management will be impacted.
[   79.124995] usb 4-3: New USB device found, idVendor=090c, idProduct=1000
[   79.124997] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   79.124998] usb 4-3: Product: USB Flash Disk
[   79.124999] usb 4-3: Manufacturer: General
[   79.125000] usb 4-3: SerialNumber: 041120013498
[   79.133013] usb-storage 4-3:1.0: USB Mass Storage device detected
[   79.133058] scsi9 : usb-storage 4-3:1.0
[   79.133100] usbcore: registered new interface driver usb-storage
[   80.467553] scsi 9:0:0:0: Direct-Access General  USB Flash Disk   1100 
PQ: 0 ANSI: 6
[   80.467749] sd 9:0:0:0: Attached scsi generic sg1 type 0
[   80.468294] sd 9:0:0:0: [sdb] 125960192 512-byte logical blocks: (64.4 
GB/60.0 GiB)
[   80.468733] sd 9:0:0:0: [sdb] Write Protect is off
[   80.468735] sd 9:0:0:0: [sdb] Mode Sense: 43 00 00 00
[   80.469164] sd 9:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   80.476633]  sdb: sdb1 sdb2
[   80.478409] sd 9:0:0:0: [sdb] Attached SCSI removable disk
[   84.533954] usb 4-3: USB disconnect, device number 2
[   84.534205] sd 9:0:0:0: [sdb] Synchronizing SCSI cache
[   84.534243] sd 9:0:0:0: [sdb]  
[   84.534246] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   92.110736] usb 4-3: new SuperSpeed USB device number 3 using xhci_hcd
[   92.12] usb 4-3: Parent hub missing LPM exit latency info.  Power 
management will be impacted.
[   92.132571] usb 4-3: New USB device found, idVendor=090c, idProduct=1000
[   92.132573] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   92.132574] usb 4-3: Product: USB Flash Disk
[   92.132575] usb 4-3: Manufacturer: General
[   92.132576] usb 4-3: SerialNumber: 041120013498
[   92.133446] usb-storage 4-3:1.0: USB Mass Storage device detected
[   92.133507] scsi10 : usb-storage 4-3:1.0
[   93.393578] usb 4-3: reset SuperSpeed USB device number 3 using xhci_hcd
[   93.411644] usb 4-3: Parent hub missing LPM exit latency info.  Power 
management will be impacted.
[   93.412809] xhci_hcd :08:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 8807a239f400
[   93.412811] xhci_hcd :08:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 8807a239f440
[   93.751289] scsi 10:0:0:0: Direct-Access General  USB Flash Disk   1100 
PQ: 0 ANSI: 6
[   93.751502] sd 10:0:0:0: Attached scsi generic sg1 type 0
[   93.752012] sd 10:0:0:0: [sdb] 125960192 512-byte logical blocks: (64.4 
GB/60.0 GiB)
[   93.752456] sd 10:0:0:0: [sdb] Write Protect is off
[   93.752459] sd 10:0:0:0: [sdb] Mode Sense: 43 00 00 00
[   93.752888] sd 10:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   93.760680]  sdb: sdb1 sdb2
[   93.762441] sd 10:0:0:0: [sdb] Attached SCSI removable disk
[   98.704248] usb 4-3: USB disconnect, device number 3
...

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  use after free of BOS in usb_reset_and_verify_device

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Should be fixed with upstream commit
  e5bdfd50d6f76077bf8441d130c606229e100d40, which reverts upstream
  commit d8f00cd685f5c8e0def8593e520a7fef12c22407.

  With slub_debug enabled this manifests as a deref of 0x6b6b... in
  usb_disable_ltm

  [  218.235302] general protection fault:  [#1] SMP 
  [  218.235311] Modules linked in: usb_storage tcp_diag inet_diag iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables autofs4 rpcsec_gss_krb5 rfcomm bnep bluetooth 
snd_hda_codec_hdmi binfmt_misc nvidia(POX) snd_hda_codec_realtek snd_hda_intel 
snd_usb_audio snd_hda_codec snd_usbmidi_lib uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core snd_hwdep snd_seq_midi joydev snd_pcm videodev 
snd_page_alloc snd_seq_midi_event nfsd snd_rawmidi snd_seq auth_rpcgss 
parport_pc nfs_acl ppdev nfs lockd sunrpc fscache honeevent(OX) snd_seq_device 
snd_timer snd drm lp parport sb_edac mei_me hp_wmi sparse_keymap gpio_ich 
hpuefi(OX) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm soundcore edac_core mei serio_raw tpm_infineon lpc_ich mac_hid wmi shpchp 
dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

2016-05-20 Thread Mike Gerow

Excellent. Thanks for the prompt response!

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

Title:
  use after free of BOS in usb_reset_and_verify_device

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Should be fixed with upstream commit
  e5bdfd50d6f76077bf8441d130c606229e100d40, which reverts upstream
  commit d8f00cd685f5c8e0def8593e520a7fef12c22407.

  With slub_debug enabled this manifests as a deref of 0x6b6b... in
  usb_disable_ltm

  [  218.235302] general protection fault:  [#1] SMP 
  [  218.235311] Modules linked in: usb_storage tcp_diag inet_diag iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables autofs4 rpcsec_gss_krb5 rfcomm bnep bluetooth 
snd_hda_codec_hdmi binfmt_misc nvidia(POX) snd_hda_codec_realtek snd_hda_intel 
snd_usb_audio snd_hda_codec snd_usbmidi_lib uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core snd_hwdep snd_seq_midi joydev snd_pcm videodev 
snd_page_alloc snd_seq_midi_event nfsd snd_rawmidi snd_seq auth_rpcgss 
parport_pc nfs_acl ppdev nfs lockd sunrpc fscache honeevent(OX) snd_seq_device 
snd_timer snd drm lp parport sb_edac mei_me hp_wmi sparse_keymap gpio_ich 
hpuefi(OX) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm soundcore edac_core mei serio_raw tpm_infineon lpc_ich mac_hid wmi shpchp 
dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse isci e1000e ahci 
libsas lib
 ahci ptp pps_core scsi_transport_sas pata_acpi
  [  218.235410] CPU: 15 PID: 243 Comm: khubd Tainted: P   OX 
3.13.0-85-generic #129-Ubuntu
  [  218.235414] Hardware name: Hewlett-Packard HP Z620 Workstation/158A, BIOS 
J61 v03.87 02/09/2015
  [  218.235418] task: 8807eff98000 ti: 8807effa task.ti: 
8807effa
  [  218.235421] RIP: 0010:[]  [] 
usb_disable_ltm+0x56/0xb0
  [  218.235437] RSP: 0018:8807effa1cd0  EFLAGS: 00010202
  [  218.235440] RAX:  RBX: 8807ea532e68 RCX: 

  [  218.235443] RDX: 6b6b6b6b6b6b6b6b RSI: 00300021 RDI: 
8807ea532e68
  [  218.235446] RBP: 8807effa1d08 R08:  R09: 

  [  218.235449] R10: 8807ff804240 R11: 8136d2a1 R12: 

  [  218.235451] R13: 8807ebddd480 R14: 0001 R15: 
0012
  [  218.235455] FS:  () GS:88101fce() 
knlGS:
  [  218.235458] CS:  0010 DS:  ES:  CR0: 80050033
  [  218.235461] CR2: 013b1c08 CR3: 01c0e000 CR4: 
000407e0
  [  218.235463] Stack:
  [  218.235465]  81551236 8807ea532ef0  
8807ea532e68
  [  218.235476]  8807ea532ef0 8807ebddbf60  
8807effa1d48
  [  218.235483]  81545c4d 8807ea532f50 8807ebddb4d0 
02a0
  [  218.235490] Call Trace:
  [  218.235499]  [] ? usb_disable_device+0x126/0x290
  [  218.235506]  [] usb_disconnect+0xad/0x200
  [  218.235511]  [] hub_port_connect_change+0xd3/0xb20
  [  218.235518]  [] ? hub_port_status+0xdd/0x120
  [  218.235523]  [] hub_events+0x4d4/0xa20
  [  218.235528]  [] hub_thread+0x35/0x160
  [  218.235535]  [] ? prepare_to_wait_event+0x100/0x100
  [  218.235540]  [] ? hub_events+0xa20/0xa20
  [  218.235549]  [] kthread+0xd2/0xf0
  [  218.235554]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [  218.235564]  [] ret_from_fork+0x58/0x90
  [  218.235570]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [  218.235572] Code: e9 48 8b 52 10 48 85 d2 74 e0 f6 42 03 02 74 da 83 7f 1c 
05 75 d4 48 8b 97 40 03 00 00 48 85 d2 74 c8 48 8b 52 10 48 85 d2 74 bf  42 
03 02 74 b9 48 83 bf 50 03 00 00 00 74 af 55 45 31 c9 41 
  [  218.235618] RIP  [] usb_disable_ltm+0x56/0xb0
  [  218.235624]  RSP 
  [  218.235655] ---[ end trace 954cac763165b767 ]---

  Without slub_debug you end up getting a double free and messing up the
  allocator and apparmor tends to be the first one to notice:

  [  574.027518] hub 4-0:1.0: Cannot enable port 3.  Maybe the USB cable is bad?
  [  574.548076] usb 4-3: USB disconnect, device number 2
  [  576.040995] [ cut here ]
  [  576.041003] WARNING: CPU: 17 PID: 11627 at 
/build/linux-03BQvT/linux-3.13.0/include/linux/kref.h:47 
apparmor_file_alloc_security+0x167/0x180()
  [  576.041005] Modules linked in: tcp_diag inet_diag xt_u32 ip6t_REJECT 
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_NFLOG xt_tcpudp 
xt_comment ipt_REJECT xt_multiport xt_connmark xt_conntrack xt_mark iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

2016-05-17 Thread Mike Gerow

Nice, looks like it works for me!

$ uname -rsov
Linux 3.13.0-86-generic #131~lp1582864 SMP Tue May 17 20:16:27 UTC 2016 
GNU/Linux

And here's my dmesg (previously I was getting an oops when unplugging my usb3 
thumbdrive).
$ dmesg
...
[   90.797829] usb 4-3: new SuperSpeed USB device number 2 using xhci_hcd
[   90.815906] usb 4-3: Parent hub missing LPM exit latency info.  Power 
management will be impacted.
[   90.819631] usb 4-3: New USB device found, idVendor=090c, idProduct=1000
[   90.819633] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   90.819634] usb 4-3: Product: USB Flash Disk
[   90.819635] usb 4-3: Manufacturer: General
[   90.819636] usb 4-3: SerialNumber: 041120013498
[   90.827444] usb-storage 4-3:1.0: USB Mass Storage device detected
[   90.827485] scsi9 : usb-storage 4-3:1.0
[   90.827522] usbcore: registered new interface driver usb-storage
[   92.162200] scsi 9:0:0:0: Direct-Access General  USB Flash Disk   1100 
PQ: 0 ANSI: 6
[   92.162387] sd 9:0:0:0: Attached scsi generic sg1 type 0
[   92.162925] sd 9:0:0:0: [sdb] 125960192 512-byte logical blocks: (64.4 
GB/60.0 GiB)
[   92.163355] sd 9:0:0:0: [sdb] Write Protect is off
[   92.163358] sd 9:0:0:0: [sdb] Mode Sense: 43 00 00 00
[   92.163785] sd 9:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   92.171207]  sdb: sdb1 sdb2
[   92.172967] sd 9:0:0:0: [sdb] Attached SCSI removable disk
[   94.797927] usb 4-3: USB disconnect, device number 2
[  100.640350] usb 4-3: new SuperSpeed USB device number 3 using xhci_hcd
[  100.658527] usb 4-3: Parent hub missing LPM exit latency info.  Power 
management will be impacted.
[  100.662189] usb 4-3: New USB device found, idVendor=090c, idProduct=1000
[  100.662191] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  100.662192] usb 4-3: Product: USB Flash Disk
[  100.662193] usb 4-3: Manufacturer: General
[  100.662194] usb 4-3: SerialNumber: 041120013498
[  100.663121] usb-storage 4-3:1.0: USB Mass Storage device detected
[  100.663219] scsi10 : usb-storage 4-3:1.0
[  101.996701] scsi 10:0:0:0: Direct-Access General  USB Flash Disk   1100 
PQ: 0 ANSI: 6
[  101.996889] sd 10:0:0:0: Attached scsi generic sg1 type 0
[  101.997446] sd 10:0:0:0: [sdb] 125960192 512-byte logical blocks: (64.4 
GB/60.0 GiB)
[  101.997894] sd 10:0:0:0: [sdb] Write Protect is off
[  101.997897] sd 10:0:0:0: [sdb] Mode Sense: 43 00 00 00
[  101.998325] sd 10:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[  102.005805]  sdb: sdb1 sdb2
[  102.007584] sd 10:0:0:0: [sdb] Attached SCSI removable disk
[  102.718253] usb 4-3: USB disconnect, device number 3
[  102.718566] sd 10:0:0:0: [sdb] Synchronizing SCSI cache
[  102.718599] sd 10:0:0:0: [sdb]  
[  102.718601] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  108.333005] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
[  108.351069] usb 4-3: Parent hub missing LPM exit latency info.  Power 
management will be impacted.
[  108.354758] usb 4-3: New USB device found, idVendor=090c, idProduct=1000
[  108.354764] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  108.354768] usb 4-3: Product: USB Flash Disk
[  108.354771] usb 4-3: Manufacturer: General
[  108.354773] usb 4-3: SerialNumber: 041120013498
[  108.355795] usb-storage 4-3:1.0: USB Mass Storage device detected
[  108.355949] scsi11 : usb-storage 4-3:1.0
[  109.689267] scsi 11:0:0:0: Direct-Access General  USB Flash Disk   1100 
PQ: 0 ANSI: 6
[  109.689642] sd 11:0:0:0: Attached scsi generic sg1 type 0
[  109.690191] sd 11:0:0:0: [sdb] 125960192 512-byte logical blocks: (64.4 
GB/60.0 GiB)
[  109.690635] sd 11:0:0:0: [sdb] Write Protect is off
[  109.690638] sd 11:0:0:0: [sdb] Mode Sense: 43 00 00 00
[  109.691070] sd 11:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[  109.698735]  sdb: sdb1 sdb2
[  109.700562] sd 11:0:0:0: [sdb] Attached SCSI removable disk
[  110.854797] usb 4-3: USB disconnect, device number 4
[  110.855419] sd 11:0:0:0: [sdb] Synchronizing SCSI cache
[  110.855455] sd 11:0:0:0: [sdb]  
[  110.855458] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  158.381766] init: kdump-tools main process (6045) terminated with status 1
[  159.852867] init: mnp_logger_goobuntu main process ended, respawning

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

Title:
  use after free of BOS in usb_reset_and_verify_device

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Should be fixed with upstream commit
  e5bdfd50d6f76077bf8441d130c606229e100d40, which reverts upstream
  commit

[Kernel-packages] [Bug 1582864] [NEW] use after free of BOS in usb_reset_and_verify_device

2016-05-17 Thread Mike Gerow

Public bug reported:

Should be fixed with upstream commit
e5bdfd50d6f76077bf8441d130c606229e100d40, which reverts upstream commit
d8f00cd685f5c8e0def8593e520a7fef12c22407.

With slub_debug enabled this manifests as a deref of 0x6b6b... in
usb_disable_ltm

[  218.235302] general protection fault:  [#1] SMP 
[  218.235311] Modules linked in: usb_storage tcp_diag inet_diag iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables autofs4 rpcsec_gss_krb5 rfcomm bnep bluetooth 
snd_hda_codec_hdmi binfmt_misc nvidia(POX) snd_hda_codec_realtek snd_hda_intel 
snd_usb_audio snd_hda_codec snd_usbmidi_lib uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core snd_hwdep snd_seq_midi joydev snd_pcm videodev 
snd_page_alloc snd_seq_midi_event nfsd snd_rawmidi snd_seq auth_rpcgss 
parport_pc nfs_acl ppdev nfs lockd sunrpc fscache honeevent(OX) snd_seq_device 
snd_timer snd drm lp parport sb_edac mei_me hp_wmi sparse_keymap gpio_ich 
hpuefi(OX) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm soundcore edac_core mei serio_raw tpm_infineon lpc_ich mac_hid wmi shpchp 
dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse isci e1000e ahci 
libsas libah
 ci ptp pps_core scsi_transport_sas pata_acpi
[  218.235410] CPU: 15 PID: 243 Comm: khubd Tainted: P   OX 
3.13.0-85-generic #129-Ubuntu
[  218.235414] Hardware name: Hewlett-Packard HP Z620 Workstation/158A, BIOS 
J61 v03.87 02/09/2015
[  218.235418] task: 8807eff98000 ti: 8807effa task.ti: 
8807effa
[  218.235421] RIP: 0010:[]  [] 
usb_disable_ltm+0x56/0xb0
[  218.235437] RSP: 0018:8807effa1cd0  EFLAGS: 00010202
[  218.235440] RAX:  RBX: 8807ea532e68 RCX: 
[  218.235443] RDX: 6b6b6b6b6b6b6b6b RSI: 00300021 RDI: 8807ea532e68
[  218.235446] RBP: 8807effa1d08 R08:  R09: 
[  218.235449] R10: 8807ff804240 R11: 8136d2a1 R12: 
[  218.235451] R13: 8807ebddd480 R14: 0001 R15: 0012
[  218.235455] FS:  () GS:88101fce() 
knlGS:
[  218.235458] CS:  0010 DS:  ES:  CR0: 80050033
[  218.235461] CR2: 013b1c08 CR3: 01c0e000 CR4: 000407e0
[  218.235463] Stack:
[  218.235465]  81551236 8807ea532ef0  
8807ea532e68
[  218.235476]  8807ea532ef0 8807ebddbf60  
8807effa1d48
[  218.235483]  81545c4d 8807ea532f50 8807ebddb4d0 
02a0
[  218.235490] Call Trace:
[  218.235499]  [] ? usb_disable_device+0x126/0x290
[  218.235506]  [] usb_disconnect+0xad/0x200
[  218.235511]  [] hub_port_connect_change+0xd3/0xb20
[  218.235518]  [] ? hub_port_status+0xdd/0x120
[  218.235523]  [] hub_events+0x4d4/0xa20
[  218.235528]  [] hub_thread+0x35/0x160
[  218.235535]  [] ? prepare_to_wait_event+0x100/0x100
[  218.235540]  [] ? hub_events+0xa20/0xa20
[  218.235549]  [] kthread+0xd2/0xf0
[  218.235554]  [] ? kthread_create_on_node+0x1c0/0x1c0
[  218.235564]  [] ret_from_fork+0x58/0x90
[  218.235570]  [] ? kthread_create_on_node+0x1c0/0x1c0
[  218.235572] Code: e9 48 8b 52 10 48 85 d2 74 e0 f6 42 03 02 74 da 83 7f 1c 
05 75 d4 48 8b 97 40 03 00 00 48 85 d2 74 c8 48 8b 52 10 48 85 d2 74 bf  42 
03 02 74 b9 48 83 bf 50 03 00 00 00 74 af 55 45 31 c9 41 
[  218.235618] RIP  [] usb_disable_ltm+0x56/0xb0
[  218.235624]  RSP 
[  218.235655] ---[ end trace 954cac763165b767 ]---

Without slub_debug you end up getting a double free and messing up the
allocator and apparmor tends to be the first one to notice:

[  574.027518] hub 4-0:1.0: Cannot enable port 3.  Maybe the USB cable is bad?
[  574.548076] usb 4-3: USB disconnect, device number 2
[  576.040995] [ cut here ]
[  576.041003] WARNING: CPU: 17 PID: 11627 at 
/build/linux-03BQvT/linux-3.13.0/include/linux/kref.h:47 
apparmor_file_alloc_security+0x167/0x180()
[  576.041005] Modules linked in: tcp_diag inet_diag xt_u32 ip6t_REJECT 
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_NFLOG xt_tcpudp 
xt_comment ipt_REJECT xt_multiport xt_connmark xt_conntrack xt_mark iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) 
vboxdrv(OX) nfnetlink_log nfnetlink autofs4 rfcomm bnep bluetooth binfmt_misc 
honeevent(OX) rpcsec_gss_krb5 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache 
snd_hda_codec_hdmi snd_hda_codec_realtek nvidia(POX) snd_hda_intel parport_pc 
snd_hda_codec ppdev lp snd_hwdep snd_pcm snd_page_alloc snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd mei_me 
parport gpio_ich hpuefi(OX) sb_edac edac_core lpc_ich drm mei joydev hp_wmi 
sparse_keymap tpm_infineon soundcore mac_hid

[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D

2016-04-26 Thread Mike Gerow

Hi, sorry for the lack of update. In the meantime I've seen reports of a
few cases of this on actual desktops and laptops, so the workaround of
disabling the usbhid dirver via udev isn't really an option there :)

Our setup relies on a handful of out-of-tree modules that don't seem to
build on 4.5.2, and since this tends to only happen after about a week
of use I don't think I'll be able to find anyone who'd be able to test
the 4.5.2 mainline kernel. I do know that these modules compile on the
wily kernel, though. Would it be helpful to test against that?

I'll start trying to get some machines trying to reproduce this on the
wily kernel, but let me know if there's anything else I can do that
might help to debug this.

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

Title:
  khubd/usbhid deadlock(?) creates processes in state D

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (Note that the attached logs are not a machine exhibiting the issue)

  I've observed this issue specifically on Dell's PowerEdge R410 with
  its DRAC. I manage quite a few other machines with DRACs and haven't
  seen this issue so it may be limited to the R410. I've seen cases of
  this both with the precise and trusty kernel.

  Basically, what happens is that things that read any info about the
  DRAC's usbhid device will block in an uninterruptible state. A quick
  way to do this is with "cat
  /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This
  means that commands like lspci will block as well. The thing is that
  it doesn't happen every time, but once it happens the first time all
  future reads on the device will block in state D too.

  This is also associated with the following from the kernel (first from a 
precise machine):
  [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197857.716899] usb 5-2: device descriptor read/64, error -71
  [197857.944966] usb 5-2: device descriptor read/64, error -71
  [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197858.285090] usb 5-2: device descriptor read/64, error -71
  [197858.513108] usb 5-2: device descriptor read/64, error -71
  [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.145214] usb 5-2: device not accepting address 2, error -71
  [197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.669322] usb 5-2: device not accepting address 2, error -71
  [197859.675357] usb 5-2: USB disconnect, device number 2
  [198047.530714] INFO: task khubd:203 blocked for more than 120 seconds.
  [198047.537147]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.551792] khubd   D 880803fe18a0 0   203  2 
0x
  [198047.551803]  8810036b1c18 0046 88102fc53180 
8810036b1fd8
  [198047.551809]  00013180 00013180 881003f7c800 
880804634800
  [198047.551814]  8810036b1c38 8810020908e8 8810020908ec 

  [198047.551819] Call Trace:
  [198047.551828]  [] schedule+0x29/0x70
  [198047.551833]  [] schedule_preempt_disabled+0xe/0x10
  [198047.551837]  [] __mutex_lock_slowpath+0x114/0x1b0
  [198047.551845]  [] ? usb_alloc_urb+0x1e/0x50
  [198047.551848]  [] mutex_lock+0x23/0x37
  [198047.551852]  [] usb_disconnect+0x5a/0x210
  [198047.551857]  [] ? usb_control_msg+0xea/0x110
  [198047.551860]  [] hub_port_connect_change+0xcf/0x9c0
  [198047.551864]  [] ? hub_port_status+0xd5/0x120
  [198047.551868]  [] hub_events+0x464/0x8c0
  [198047.551871]  [] ? __schedule+0x38e/0x700
  [198047.551875]  [] hub_thread+0x35/0x150
  [198047.551881]  [] ? __wake_up_sync+0x20/0x20
  [198047.551885]  [] ? hub_events+0x8c0/0x8c0
  [198047.551890]  [] kthread+0xc9/0xe0
  [198047.551893]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551898]  [] ret_from_fork+0x58/0x90
  [198047.551902]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds.
  [198047.558892]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.573524] kworker/9:1 D 880803fe18a0 0   246  2 
0x
  [198047.573547] Workqueue: events hid_reset [usbhid]
  [198047.573550]  8808011f9788 0046 88080fc93180 
8808011f9fd8
  [198047.573555]  00013180 00013180 881003f94800 
8808011f
  [198047.573559]  8808011f9798 8808011f98d8 7fff 
7fff
  [198047.573564] Call Trace:
  [198047.573579]  [] schedule+0x29/0x70
  [198047.573582]  [] schedule_timeout+0x1e5/0x250
  [198047.573587]  [] ? wake_affine+0x16d/0x2d0
  [198047.573591]

[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D

2016-03-19 Thread Mike Gerow

Hi Joseph

I'll see if I can nab some extra hardware to try it out. Keep in mind
that I haven't found a way to reproduce this reliably yet, with our
usual setup it can take a few weeks before it happens. Basically we have
a cron job that periodically exports the state of our machines, which
includes calling lsusb. Eventually this bug happens, all future calls to
the job get stuck in D, and the machine eventually runs out of
resources, requiring it to be rebooted.

I did browse kernel sources upstream and didn't notice anything that
would appear to fix this issue, but I'm certainly no kernel-guru.

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

Title:
  khubd/usbhid deadlock(?) creates processes in state D

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (Note that the attached logs are not a machine exhibiting the issue)

  I've observed this issue specifically on Dell's PowerEdge R410 with
  its DRAC. I manage quite a few other machines with DRACs and haven't
  seen this issue so it may be limited to the R410. I've seen cases of
  this both with the precise and trusty kernel.

  Basically, what happens is that things that read any info about the
  DRAC's usbhid device will block in an uninterruptible state. A quick
  way to do this is with "cat
  /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This
  means that commands like lspci will block as well. The thing is that
  it doesn't happen every time, but once it happens the first time all
  future reads on the device will block in state D too.

  This is also associated with the following from the kernel (first from a 
precise machine):
  [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197857.716899] usb 5-2: device descriptor read/64, error -71
  [197857.944966] usb 5-2: device descriptor read/64, error -71
  [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197858.285090] usb 5-2: device descriptor read/64, error -71
  [197858.513108] usb 5-2: device descriptor read/64, error -71
  [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.145214] usb 5-2: device not accepting address 2, error -71
  [197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.669322] usb 5-2: device not accepting address 2, error -71
  [197859.675357] usb 5-2: USB disconnect, device number 2
  [198047.530714] INFO: task khubd:203 blocked for more than 120 seconds.
  [198047.537147]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.551792] khubd   D 880803fe18a0 0   203  2 
0x
  [198047.551803]  8810036b1c18 0046 88102fc53180 
8810036b1fd8
  [198047.551809]  00013180 00013180 881003f7c800 
880804634800
  [198047.551814]  8810036b1c38 8810020908e8 8810020908ec 

  [198047.551819] Call Trace:
  [198047.551828]  [] schedule+0x29/0x70
  [198047.551833]  [] schedule_preempt_disabled+0xe/0x10
  [198047.551837]  [] __mutex_lock_slowpath+0x114/0x1b0
  [198047.551845]  [] ? usb_alloc_urb+0x1e/0x50
  [198047.551848]  [] mutex_lock+0x23/0x37
  [198047.551852]  [] usb_disconnect+0x5a/0x210
  [198047.551857]  [] ? usb_control_msg+0xea/0x110
  [198047.551860]  [] hub_port_connect_change+0xcf/0x9c0
  [198047.551864]  [] ? hub_port_status+0xd5/0x120
  [198047.551868]  [] hub_events+0x464/0x8c0
  [198047.551871]  [] ? __schedule+0x38e/0x700
  [198047.551875]  [] hub_thread+0x35/0x150
  [198047.551881]  [] ? __wake_up_sync+0x20/0x20
  [198047.551885]  [] ? hub_events+0x8c0/0x8c0
  [198047.551890]  [] kthread+0xc9/0xe0
  [198047.551893]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551898]  [] ret_from_fork+0x58/0x90
  [198047.551902]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds.
  [198047.558892]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.573524] kworker/9:1 D 880803fe18a0 0   246  2 
0x
  [198047.573547] Workqueue: events hid_reset [usbhid]
  [198047.573550]  8808011f9788 0046 88080fc93180 
8808011f9fd8
  [198047.573555]  00013180 00013180 881003f94800 
8808011f
  [198047.573559]  8808011f9798 8808011f98d8 7fff 
7fff
  [198047.573564] Call Trace:
  [198047.573579]  [] schedule+0x29/0x70
  [198047.573582]  [] schedule_timeout+0x1e5/0x250
  [198047.573587]  [] ? wake_affine+0x16d/0x2d0
  [198047.573591]  [] wait_for_completion+0xa7/0x160
  [198047.573596]  [] ? try_to_wake_up+0x210/0x210
  [198047.573602]  []

[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D

2016-03-14 Thread Mike Gerow

Sorry, I'm not super familiar with apport (our security folks make us
disable it because they get upset for reasons I don't quite grasp).

I tried to install apport and python-apport, but no dice on actually
running apport-collect.

$ apport-collect 1557172
Traceback (most recent call last):
  File "/usr/bin/apport-cli", line 370, in 
if not app.run_argv():
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 525, in 
run_update_report
pkgs = self.crashdb.get_affected_packages(self.options.update_report)
  File "/usr/lib/python2.7/dist-packages/apport/crashdb_impl/memory.py", line 
79, in get_affected_packages
return [self.reports[id]['report']['SourcePackage']]
IndexError: list index out of range

Is there some other way for me to get the info you need?

** 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/1557172

Title:
  khubd/usbhid deadlock(?) creates processes in state D

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (Note that the attached logs are not a machine exhibiting the issue)

  I've observed this issue specifically on Dell's PowerEdge R410 with
  its DRAC. I manage quite a few other machines with DRACs and haven't
  seen this issue so it may be limited to the R410. I've seen cases of
  this both with the precise and trusty kernel.

  Basically, what happens is that things that read any info about the
  DRAC's usbhid device will block in an uninterruptible state. A quick
  way to do this is with "cat
  /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This
  means that commands like lspci will block as well. The thing is that
  it doesn't happen every time, but once it happens the first time all
  future reads on the device will block in state D too.

  This is also associated with the following from the kernel (first from a 
precise machine):
  [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197857.716899] usb 5-2: device descriptor read/64, error -71
  [197857.944966] usb 5-2: device descriptor read/64, error -71
  [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197858.285090] usb 5-2: device descriptor read/64, error -71
  [197858.513108] usb 5-2: device descriptor read/64, error -71
  [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.145214] usb 5-2: device not accepting address 2, error -71
  [197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.669322] usb 5-2: device not accepting address 2, error -71
  [197859.675357] usb 5-2: USB disconnect, device number 2
  [198047.530714] INFO: task khubd:203 blocked for more than 120 seconds.
  [198047.537147]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.551792] khubd   D 880803fe18a0 0   203  2 
0x
  [198047.551803]  8810036b1c18 0046 88102fc53180 
8810036b1fd8
  [198047.551809]  00013180 00013180 881003f7c800 
880804634800
  [198047.551814]  8810036b1c38 8810020908e8 8810020908ec 

  [198047.551819] Call Trace:
  [198047.551828]  [] schedule+0x29/0x70
  [198047.551833]  [] schedule_preempt_disabled+0xe/0x10
  [198047.551837]  [] __mutex_lock_slowpath+0x114/0x1b0
  [198047.551845]  [] ? usb_alloc_urb+0x1e/0x50
  [198047.551848]  [] mutex_lock+0x23/0x37
  [198047.551852]  [] usb_disconnect+0x5a/0x210
  [198047.551857]  [] ? usb_control_msg+0xea/0x110
  [198047.551860]  [] hub_port_connect_change+0xcf/0x9c0
  [198047.551864]  [] ? hub_port_status+0xd5/0x120
  [198047.551868]  [] hub_events+0x464/0x8c0
  [198047.551871]  [] ? __schedule+0x38e/0x700
  [198047.551875]  [] hub_thread+0x35/0x150
  [198047.551881]  [] ? __wake_up_sync+0x20/0x20
  [198047.551885]  [] ? hub_events+0x8c0/0x8c0
  [198047.551890]  [] kthread+0xc9/0xe0
  [198047.551893]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551898]  [] ret_from_fork+0x58/0x90
  [198047.551902]  [] ? flush_kthread_worker+0xb0/0xb0
  [198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds.
  [198047.558892]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
  [198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [198047.573524] kworker/9:1 D 880803fe18a0 0   246  2 
0x
  [198047.573547] Workqueue: events hid_reset [usbhid]
  [198047.573550]  8808011f9788 0046 88080fc93180 
8808011f9fd8
  [198047.573555]  00013180 00013180 881003f94800 
8808011f
  [198047.573559]  8808011f9798

[Kernel-packages] [Bug 1557172] [NEW] khubd/usbhid deadlock(?) creates processes in state D

2016-03-14 Thread Mike Gerow

Public bug reported:

(Note that the attached logs are not a machine exhibiting the issue)

I've observed this issue specifically on Dell's PowerEdge R410 with its
DRAC. I manage quite a few other machines with DRACs and haven't seen
this issue so it may be limited to the R410. I've seen cases of this
both with the precise and trusty kernel.

Basically, what happens is that things that read any info about the
DRAC's usbhid device will block in an uninterruptible state. A quick way
to do this is with "cat
/sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This means
that commands like lspci will block as well. The thing is that it
doesn't happen every time, but once it happens the first time all future
reads on the device will block in state D too.

This is also associated with the following from the kernel (first from a 
precise machine):
[197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[197857.716899] usb 5-2: device descriptor read/64, error -71
[197857.944966] usb 5-2: device descriptor read/64, error -71
[197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[197858.285090] usb 5-2: device descriptor read/64, error -71
[197858.513108] usb 5-2: device descriptor read/64, error -71
[197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[197859.145214] usb 5-2: device not accepting address 2, error -71
[197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[197859.669322] usb 5-2: device not accepting address 2, error -71
[197859.675357] usb 5-2: USB disconnect, device number 2
[198047.530714] INFO: task khubd:203 blocked for more than 120 seconds.
[198047.537147]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
[198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[198047.551792] khubd   D 880803fe18a0 0   203  2 0x
[198047.551803]  8810036b1c18 0046 88102fc53180 
8810036b1fd8
[198047.551809]  00013180 00013180 881003f7c800 
880804634800
[198047.551814]  8810036b1c38 8810020908e8 8810020908ec 

[198047.551819] Call Trace:
[198047.551828]  [] schedule+0x29/0x70
[198047.551833]  [] schedule_preempt_disabled+0xe/0x10
[198047.551837]  [] __mutex_lock_slowpath+0x114/0x1b0
[198047.551845]  [] ? usb_alloc_urb+0x1e/0x50
[198047.551848]  [] mutex_lock+0x23/0x37
[198047.551852]  [] usb_disconnect+0x5a/0x210
[198047.551857]  [] ? usb_control_msg+0xea/0x110
[198047.551860]  [] hub_port_connect_change+0xcf/0x9c0
[198047.551864]  [] ? hub_port_status+0xd5/0x120
[198047.551868]  [] hub_events+0x464/0x8c0
[198047.551871]  [] ? __schedule+0x38e/0x700
[198047.551875]  [] hub_thread+0x35/0x150
[198047.551881]  [] ? __wake_up_sync+0x20/0x20
[198047.551885]  [] ? hub_events+0x8c0/0x8c0
[198047.551890]  [] kthread+0xc9/0xe0
[198047.551893]  [] ? flush_kthread_worker+0xb0/0xb0
[198047.551898]  [] ret_from_fork+0x58/0x90
[198047.551902]  [] ? flush_kthread_worker+0xb0/0xb0
[198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds.
[198047.558892]   Not tainted 3.13.0-74-generic #118~precise1-Ubuntu
[198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[198047.573524] kworker/9:1 D 880803fe18a0 0   246  2 0x
[198047.573547] Workqueue: events hid_reset [usbhid]
[198047.573550]  8808011f9788 0046 88080fc93180 
8808011f9fd8
[198047.573555]  00013180 00013180 881003f94800 
8808011f
[198047.573559]  8808011f9798 8808011f98d8 7fff 
7fff
[198047.573564] Call Trace:
[198047.573579]  [] schedule+0x29/0x70
[198047.573582]  [] schedule_timeout+0x1e5/0x250
[198047.573587]  [] ? wake_affine+0x16d/0x2d0
[198047.573591]  [] wait_for_completion+0xa7/0x160
[198047.573596]  [] ? try_to_wake_up+0x210/0x210
[198047.573602]  [] flush_work+0x29/0x40
[198047.573605]  [] ? start_worker+0x40/0x40
[198047.573609]  [] __cancel_work_timer+0x9c/0x1b0
[198047.573623]  [] cancel_work_sync+0x10/0x20
[198047.573632]  [] hid_cancel_delayed_stuff+0x29/0x30 
[usbhid]
[198047.573640]  [] usbhid_close+0xcc/0x110 [usbhid]
[198047.573650]  [] hidinput_close+0x22/0x30 [hid]
[198047.573659]  [] input_close_device+0x61/0x90
[198047.573663]  [] evdev_cleanup+0xbf/0xd0
[198047.573670]  [] evdev_disconnect+0x36/0x70
[198047.573674]  [] __input_unregister_device+0xc5/0x1a0
[198047.573678]  [] input_unregister_device+0x55/0x80
[198047.573687]  [] hidinput_disconnect+0x95/0xc0 [hid]
[198047.573695]  [] hid_disconnect+0x68/0x70 [hid]
[198047.573708]  [] hid_device_remove+0xd5/0xf0 [hid]
[198047.573720]  [] __device_release_driver+0x7f/0xf0
[198047.573724]  [] device_release_driver+0x2c/0x40
[198047.573728]  [] bus_remove_device+0x104/0x170
[198047.573736]  [] device_del+0x118/0x1a0
[198047.573744]  [] hid_destroy_device+0x30/0x70 [hid]
[198047.573754]  []

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[Kernel-packages] [Bug 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

[Kernel-packages] [Bug 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

[Kernel-packages] [Bug 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

[Kernel-packages] [Bug 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

[Kernel-packages] [Bug 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

[Kernel-packages] [Bug 1593835] Re: Transient panic on boot with wily proposed kernel (4.2.0-39)

[Kernel-packages] [Bug 1593835] [NEW] Transient panic on boot with wily proposed kernel (4.2.0-39)

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[Kernel-packages] [Bug 1586195] [NEW] Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

[Kernel-packages] [Bug 1582864] [NEW] use after free of BOS in usb_reset_and_verify_device

[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D

[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D

[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D

[Kernel-packages] [Bug 1557172] [NEW] khubd/usbhid deadlock(?) creates processes in state D

24 matches

Site Navigation

Mail list logo

Footer information