kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #122279
[Bug 1458839] Re: Poor Wi-Fi connectivity when connecting USB dock
Jonas G. Drange, the latest mainline kernel is 4.1-rc6.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1458839
Title:
Poor Wi-Fi connectivity when connecting USB dock
Status in linux package in Ubuntu:
Incomplete
Bug description:
Reproduce:
Insert USB dock (Kensington with usb sound card, ethernet card) cable into any USB port
What happens:
Wi-Fi connectivity worsens and eventually disconnects.
Pinging an online target gives me
[1432638474.615293] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=11 ttl=54 time=1172 ms
[1432638474.636669] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=12 ttl=54 time=185 ms
[1432638475.496000] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=13 ttl=54 time=44.3 ms
[1432638477.638814] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=14 ttl=54 time=1185 ms
[1432638477.644744] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=15 ttl=54 time=192 ms
[1432638478.498248] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=16 ttl=54 time=44.4 ms
[1432638479.662460] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=17 ttl=54 time=207 ms
[1432638480.547434] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=18 ttl=54 time=90.9 ms
[1432638482.597835] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=19 ttl=54 time=1140 ms
[1432638482.601590] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=20 ttl=54 time=144 ms
[1432638484.648946] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=21 ttl=54 time=1191 ms
[1432638484.649794] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=22 ttl=54 time=193 ms
[1432638485.502967] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=23 ttl=54 time=45.1 ms
[1432638487.301295] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=24 ttl=54 time=842 ms
[1432638488.649794] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=25 ttl=54 time=1191 ms
[1432638488.662959] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=26 ttl=54 time=196 ms
[1432638489.514683] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=27 ttl=54 time=46.7 ms
[1432638491.653511] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=28 ttl=54 time=1183 ms
[1432638491.655011] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=29 ttl=54 time=176 ms
[1432638493.659119] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=30 ttl=54 time=1179 ms
[1432638493.664250] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=31 ttl=54 time=177 ms
[1432638494.534200] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=32 ttl=54 time=45.9 ms
…
Disconnecting the USB cable restores the connectivity:
[1432638514.584374] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=52 ttl=54 time=48.5 ms
[1432638515.577822] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=53 ttl=54 time=40.1 ms
[1432638516.579000] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=54 ttl=54 time=39.9 ms
[1432638517.580760] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=55 ttl=54 time=40.5 ms
[1432638518.583465] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=56 ttl=54 time=41.4 ms
[1432638519.583923] 64 bytes from fra07s30-in-f5.1e100.net (173.194.112.101): icmp_seq=57 ttl=54 time=40.1 ms
…
What should have happened:
Connectivity should not be affected by a connected USB dock
Steps taken to debug:
* I've told NetworkManager not to manage the USB network card so that it appears unmanaged. This makes no difference.
* I've tried older kernels, e.g. 3.14 with no luck
* It does not matter what is connected to the dock
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-18-generic 3.19.0-18.18
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: jonas 1514 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue May 26 13:08:44 2015
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-precise-amd64-20120703-2
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=7b9cb658-95dd-4e13-a587-d6d0d59ae7e4
InstallationDate: Installed on 2013-08-27 (637 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
MachineType: Dell Inc. Dell System XPS L322X
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=221de9c1-f10a-4be4-9273-5c12864c8680 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.19.0-18-generic N/A
linux-backports-modules-3.19.0-18-generic N/A
linux-firmware 1.143.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0PJHXN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L322X
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458839/+subscriptions
References