Ubuntu
linux package

8086:422b [Samsung NP900X3A-A01AU] Intel Centrino Ultimate-N 6300 AGN and packet loss using WiFi-N

Bug #837076 reported by Haw Loeung
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Linux
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Low
Unassigned
Saucy
Won't Fix
Low
Unassigned
Trusty
Incomplete
Low
Unassigned

Bug Description

I have recently swapped the internal WiFi adapter with an Ultimate-N 6300 and I'm seeing a lot of packet loss. Some additional info is as follows:
wlan1 IEEE 802.11abgn ESSID:"star-local"
          Mode:Managed Frequency:2.412 GHz Access Point: 00:22:75:29:EC:61
          Bit Rate=121.5 Mb/s Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=49/70 Signal level=-61 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:205 Invalid misc:5 Missed beacon:0

$ ping -c 20 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_req=1 ttl=64 time=3.83 ms
64 bytes from 192.168.2.1: icmp_req=2 ttl=64 time=2.56 ms
64 bytes from 192.168.2.1: icmp_req=3 ttl=64 time=2.59 ms
64 bytes from 192.168.2.1: icmp_req=4 ttl=64 time=2.57 ms
64 bytes from 192.168.2.1: icmp_req=5 ttl=64 time=3.23 ms
64 bytes from 192.168.2.1: icmp_req=6 ttl=64 time=3.13 ms
64 bytes from 192.168.2.1: icmp_req=7 ttl=64 time=4.04 ms
64 bytes from 192.168.2.1: icmp_req=11 ttl=64 time=3.89 ms
64 bytes from 192.168.2.1: icmp_req=12 ttl=64 time=3.80 ms
64 bytes from 192.168.2.1: icmp_req=13 ttl=64 time=82.4 ms
64 bytes from 192.168.2.1: icmp_req=14 ttl=64 time=105 ms
64 bytes from 192.168.2.1: icmp_req=15 ttl=64 time=2.57 ms
64 bytes from 192.168.2.1: icmp_req=16 ttl=64 time=2.97 ms
64 bytes from 192.168.2.1: icmp_req=17 ttl=64 time=2.57 ms
64 bytes from 192.168.2.1: icmp_req=18 ttl=64 time=2.57 ms
64 bytes from 192.168.2.1: icmp_req=19 ttl=64 time=3.94 ms
64 bytes from 192.168.2.1: icmp_req=20 ttl=64 time=3.51 ms

--- 192.168.2.1 ping statistics ---
20 packets transmitted, 17 received, 15% packet loss, time 19028ms
rtt min/avg/max/mdev = 2.567/13.879/105.633/29.547 ms

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/837076/+attachment/3929375/+files/log

WORKAROUND: Remove and reload the module with "11n_disable=1".

wlan1 IEEE 802.11abg ESSID:"star-local"
          Mode:Managed Frequency:2.412 GHz Access Point: 00:22:75:29:EC:61
          Bit Rate=54 Mb/s Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=49/70 Signal level=-61 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:32 Missed beacon:0

$ ping -c 20 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_req=1 ttl=64 time=1.82 ms
64 bytes from 192.168.2.1: icmp_req=2 ttl=64 time=1.17 ms
64 bytes from 192.168.2.1: icmp_req=3 ttl=64 time=1.80 ms
64 bytes from 192.168.2.1: icmp_req=4 ttl=64 time=0.650 ms
64 bytes from 192.168.2.1: icmp_req=5 ttl=64 time=1.52 ms
64 bytes from 192.168.2.1: icmp_req=6 ttl=64 time=2.29 ms
64 bytes from 192.168.2.1: icmp_req=7 ttl=64 time=1.29 ms
64 bytes from 192.168.2.1: icmp_req=8 ttl=64 time=1.65 ms
64 bytes from 192.168.2.1: icmp_req=9 ttl=64 time=1.70 ms
64 bytes from 192.168.2.1: icmp_req=10 ttl=64 time=1.06 ms
64 bytes from 192.168.2.1: icmp_req=11 ttl=64 time=1.52 ms
64 bytes from 192.168.2.1: icmp_req=12 ttl=64 time=1.49 ms
64 bytes from 192.168.2.1: icmp_req=13 ttl=64 time=1.89 ms
64 bytes from 192.168.2.1: icmp_req=14 ttl=64 time=1.46 ms
64 bytes from 192.168.2.1: icmp_req=15 ttl=64 time=1.41 ms
64 bytes from 192.168.2.1: icmp_req=16 ttl=64 time=1.28 ms
64 bytes from 192.168.2.1: icmp_req=17 ttl=64 time=1.40 ms
64 bytes from 192.168.2.1: icmp_req=18 ttl=64 time=0.946 ms
64 bytes from 192.168.2.1: icmp_req=19 ttl=64 time=1.32 ms
64 bytes from 192.168.2.1: icmp_req=20 ttl=64 time=1.32 ms

--- 192.168.2.1 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19026ms
rtt min/avg/max/mdev = 0.650/1.453/2.291/0.356 ms

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-9-generic 3.0.0-9.14
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: hloeung 2208 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xc0700000 irq 48'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,144dc098,00100100 HDA:80862805,80860101,00100000'
   Controls : 18
   Simple ctrls : 10
Date: Tue Aug 30 09:21:33 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 90X3A
ProcEnviron:
 LANGUAGE=en_AU:en_GB:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 LC_MESSAGES=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-9-generic root=UUID=b4df4065-2b5c-4a10-9c50-4d01d05d09c3 ro elevator=deadline apparmor=0 quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-9-generic N/A
 linux-backports-modules-3.0.0-9-generic N/A
 linux-firmware 1.60
RfKill:
 7: phy7: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to oneiric on 2011-08-08 (21 days ago)
dmi.bios.date: 03/08/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04HL
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 90X3A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04HL:bd03/08/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn90X3A:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn90X3A:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 90X3A
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
---
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: hloeung 1724 F.... pulseaudio
DistroRelease: Ubuntu 13.10
Lsusb:
 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
MachineType: SAMSUNG ELECTRONICS CO., LTD. 90X3A
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-7-generic root=UUID=b4df4065-2b5c-4a10-9c50-4d01d05d09c3 ro quiet splash elevator=noop apparmor=0 pcie_aspm=force i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 intel_pstate=enable zswap.enabled=1 vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-7-generic N/A
 linux-backports-modules-3.11.0-7-generic N/A
 linux-firmware 1.113
StagingDrivers: zram
Tags: saucy staging
Uname: Linux 3.11.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev sambashare users video
dmi.bios.date: 03/08/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04HL
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 90X3A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04HL:bd03/08/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn90X3A:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn90X3A:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 90X3A
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
---
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: hloeung 1724 F.... pulseaudio
DistroRelease: Ubuntu 13.10
Lsusb:
 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
MachineType: SAMSUNG ELECTRONICS CO., LTD. 90X3A
MarkForUpload: True
Package: linux
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-7-generic root=UUID=b4df4065-2b5c-4a10-9c50-4d01d05d09c3 ro quiet splash elevator=noop apparmor=0 pcie_aspm=force i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 intel_pstate=enable zswap.enabled=1 vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-7-generic N/A
 linux-backports-modules-3.11.0-7-generic N/A
 linux-firmware 1.113
StagingDrivers: zram
Tags: saucy staging
Uname: Linux 3.11.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev sambashare users video
dmi.bios.date: 03/08/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04HL
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 90X3A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04HL:bd03/08/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn90X3A:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn90X3A:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 90X3A
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

See original description
Revision history for this message
Haw Loeung (hloeung) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-11.18)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel currently in the release pocket than the one you tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-11.18
Revision history for this message
Haw Loeung (hloeung) wrote : Re: [iwlagn] Intel Centrino Ultimate-N 6300 AGN and packet loss

Hi Brad,

It still seems to be happening with 3.0.0-11.18. One thing I notice is that iwconfig shows a pretty high "Tx excessive retries" count.

$ iwconfig
wlan1 IEEE 802.11abgn ESSID:"xxx"
          Mode:Managed Frequency:2.412 GHz Access Point: xx:xx:xx:xx:Exxxx
          Bit Rate=90 Mb/s Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=51/70 Signal level=-59 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:77 Invalid misc:21 Missed beacon:0

$ ping -c 20 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_req=1 ttl=64 time=103 ms
64 bytes from 192.168.2.1: icmp_req=2 ttl=64 time=89.2 ms
64 bytes from 192.168.2.1: icmp_req=3 ttl=64 time=111 ms
64 bytes from 192.168.2.1: icmp_req=4 ttl=64 time=2.46 ms
64 bytes from 192.168.2.1: icmp_req=5 ttl=64 time=2.47 ms
64 bytes from 192.168.2.1: icmp_req=6 ttl=64 time=78.2 ms
64 bytes from 192.168.2.1: icmp_req=7 ttl=64 time=3.92 ms
64 bytes from 192.168.2.1: icmp_req=8 ttl=64 time=2.47 ms
64 bytes from 192.168.2.1: icmp_req=9 ttl=64 time=2.53 ms
64 bytes from 192.168.2.1: icmp_req=10 ttl=64 time=5.04 ms
64 bytes from 192.168.2.1: icmp_req=11 ttl=64 time=3.53 ms
64 bytes from 192.168.2.1: icmp_req=12 ttl=64 time=3.38 ms
64 bytes from 192.168.2.1: icmp_req=13 ttl=64 time=2.50 ms
64 bytes from 192.168.2.1: icmp_req=14 ttl=64 time=2.42 ms
64 bytes from 192.168.2.1: icmp_req=15 ttl=64 time=2.89 ms
64 bytes from 192.168.2.1: icmp_req=17 ttl=64 time=8.88 ms
64 bytes from 192.168.2.1: icmp_req=18 ttl=64 time=2.02 ms
64 bytes from 192.168.2.1: icmp_req=19 ttl=64 time=3.87 ms
64 bytes from 192.168.2.1: icmp_req=20 ttl=64 time=2.47 ms

--- 192.168.2.1 ping statistics ---
20 packets transmitted, 19 received, 5% packet loss, time 19036ms
rtt min/avg/max/mdev = 2.028/22.775/111.207/38.007 ms

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Haw Loeung (hloeung) wrote :

Forgot to add:

$ uname -a
Linux darkon 3.0.0-11-generic #18-Ubuntu SMP Tue Sep 13 23:38:01 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.19)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.19
Revision history for this message
Haw Loeung (hloeung) wrote : Re: [iwlagn] Intel Centrino Ultimate-N 6300 AGN and packet loss

Still happening:

$ ping -c 20 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_req=1 ttl=64 time=2.85 ms
64 bytes from 192.168.2.1: icmp_req=2 ttl=64 time=2.21 ms
64 bytes from 192.168.2.1: icmp_req=3 ttl=64 time=11.5 ms
64 bytes from 192.168.2.1: icmp_req=4 ttl=64 time=130 ms
64 bytes from 192.168.2.1: icmp_req=5 ttl=64 time=47.9 ms
64 bytes from 192.168.2.1: icmp_req=6 ttl=64 time=2.79 ms
64 bytes from 192.168.2.1: icmp_req=7 ttl=64 time=852 ms
64 bytes from 192.168.2.1: icmp_req=8 ttl=64 time=7.16 ms
64 bytes from 192.168.2.1: icmp_req=9 ttl=64 time=87.1 ms
64 bytes from 192.168.2.1: icmp_req=9 ttl=64 time=232 ms (DUP!)
64 bytes from 192.168.2.1: icmp_req=10 ttl=64 time=39.5 ms
64 bytes from 192.168.2.1: icmp_req=11 ttl=64 time=6.86 ms
64 bytes from 192.168.2.1: icmp_req=12 ttl=64 time=4.58 ms
64 bytes from 192.168.2.1: icmp_req=13 ttl=64 time=8.40 ms
64 bytes from 192.168.2.1: icmp_req=14 ttl=64 time=8.02 ms
64 bytes from 192.168.2.1: icmp_req=15 ttl=64 time=3.31 ms
64 bytes from 192.168.2.1: icmp_req=16 ttl=64 time=225 ms
64 bytes from 192.168.2.1: icmp_req=18 ttl=64 time=140 ms
64 bytes from 192.168.2.1: icmp_req=19 ttl=64 time=22.9 ms
64 bytes from 192.168.2.1: icmp_req=20 ttl=64 time=6.96 ms

--- 192.168.2.1 ping statistics ---
20 packets transmitted, 19 received, +1 duplicates, 5% packet loss, time 19033ms
rtt min/avg/max/mdev = 2.211/92.196/852.078/188.467 ms

$ iwconfig
lo no wireless extensions.

wlan1 IEEE 802.11abgn ESSID:"star-local"
          Mode:Managed Frequency:2.412 GHz Access Point: 00:22:75:29:EC:61
          Bit Rate=11 Mb/s Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=55/70 Signal level=-55 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:25 Invalid misc:66 Missed beacon:0

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.20)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: [iwlagn] Intel Centrino Ultimate-N 6300 AGN and packet loss

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

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

Thanks in advance.

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
summary: - [iwlagn] Intel Centrino Ultimate-N 6300 AGN and packet loss
+ 8086:422b [iwlagn] Intel Centrino Ultimate-N 6300 AGN and packet loss
Revision history for this message
Haw Loeung (hloeung) wrote : Re: 8086:422b [iwlagn] Intel Centrino Ultimate-N 6300 AGN and packet loss
Download full text (3.5 KiB)

Hi,

It seems I'm still seeing issues with packet loss, spikes in latency, and TX excessive retries.

[hloeung@darkon tmp]$ ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=3.16 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=3.28 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=6.11 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=3.29 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=1634 ms
64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=762 ms
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=3.29 ms
64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=3.27 ms
64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=3.27 ms
64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=7.41 ms
64 bytes from 192.168.2.1: icmp_seq=12 ttl=64 time=3.03 ms
64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=3.26 ms
64 bytes from 192.168.2.1: icmp_seq=14 ttl=64 time=3.31 ms
64 bytes from 192.168.2.1: icmp_seq=15 ttl=64 time=3.29 ms
64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=5.84 ms
64 bytes from 192.168.2.1: icmp_seq=17 ttl=64 time=3.27 ms
64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=6.15 ms
64 bytes from 192.168.2.1: icmp_seq=19 ttl=64 time=8.55 ms
64 bytes from 192.168.2.1: icmp_seq=20 ttl=64 time=5.69 ms
64 bytes from 192.168.2.1: icmp_seq=21 ttl=64 time=3.82 ms
64 bytes from 192.168.2.1: icmp_seq=23 ttl=64 time=1962 ms
64 bytes from 192.168.2.1: icmp_seq=25 ttl=64 time=1012 ms
64 bytes from 192.168.2.1: icmp_seq=26 ttl=64 time=5.96 ms
64 bytes from 192.168.2.1: icmp_seq=27 ttl=64 time=3.02 ms
64 bytes from 192.168.2.1: icmp_seq=28 ttl=64 time=3.54 ms
64 bytes from 192.168.2.1: icmp_seq=29 ttl=64 time=3.22 ms
64 bytes from 192.168.2.1: icmp_seq=30 ttl=64 time=7.55 ms
64 bytes from 192.168.2.1: icmp_seq=31 ttl=64 time=3.26 ms
64 bytes from 192.168.2.1: icmp_seq=32 ttl=64 time=2.99 ms
64 bytes from 192.168.2.1: icmp_seq=34 ttl=64 time=2297 ms
64 bytes from 192.168.2.1: icmp_seq=35 ttl=64 time=1289 ms
64 bytes from 192.168.2.1: icmp_seq=36 ttl=64 time=281 ms
64 bytes from 192.168.2.1: icmp_seq=37 ttl=64 time=5.25 ms
64 bytes from 192.168.2.1: icmp_seq=38 ttl=64 time=2.28 ms
64 bytes from 192.168.2.1: icmp_seq=39 ttl=64 time=3.27 ms
64 bytes from 192.168.2.1: icmp_seq=40 ttl=64 time=3.22 ms
64 bytes from 192.168.2.1: icmp_seq=41 ttl=64 time=3.26 ms
64 bytes from 192.168.2.1: icmp_seq=42 ttl=64 time=7.46 ms
64 bytes from 192.168.2.1: icmp_seq=43 ttl=64 time=6.18 ms
^C
--- 192.168.2.1 ping statistics ---
43 packets transmitted, 39 received, 9% packet loss, time 42088ms
rtt min/avg/max/mdev = 2.280/240.515/2297.437/575.005 ms, pipe 3

[hloeung@darkon tmp]$ iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:"star-local"
          Mode:Managed Frequency:2.452 GHz Access Point: 00:22:75:29:EC:61
          Bit Rate=135 Mb/s Tx-Power=15 dBm
          Retry limit:0 RTS thr:off Fragment thr:off
          Power Management:on
          Link Quality=54/70 Signal level=-56 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:5517 Invalid misc:25 Missed beacon:0

This is happening on...

Read more...

tags: added: apport-collected saucy
description: updated
Revision history for this message
Haw Loeung (hloeung) wrote : AlsaInfo.txt

apport information

description: updated
Revision history for this message
Haw Loeung (hloeung) wrote : BootDmesg.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : CRDA.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : Dependencies.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : IwConfig.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : Lspci.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : ProcEnviron.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : ProcModules.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : PulseList.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : RfKill.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : UdevDb.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : UdevLog.txt

apport information

Revision history for this message
Haw Loeung (hloeung) wrote : WifiSyslog.txt

apport information

Haw Loeung (hloeung)
summary: - 8086:422b [iwlagn] Intel Centrino Ultimate-N 6300 AGN and packet loss
+ 8086:422b [iwlwifi] Intel Centrino Ultimate-N 6300 AGN and packet loss
Alberto Salvia Novella (es20490446e)
Changed in linux (Ubuntu Saucy):
importance: Undecided → High
Haw Loeung (hloeung)
tags: removed: kernel-request-3.0.0-11.18 kernel-request-3.0.0-12.19 kernel-request-3.0.0-12.20 needs-upstream-testing
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Please test latest development kernel (3.11.0-7.14)

Given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.11.0-7.14
Revision history for this message
Haw Loeung (hloeung) wrote : Re: 8086:422b [iwlwifi] Intel Centrino Ultimate-N 6300 AGN and packet loss

Still happening with the latest kernel (3.11.0-8):

[hloeung@darkon tmp]$ uname -a
Linux darkon 3.11.0-8-generic #15-Ubuntu SMP Fri Sep 20 04:11:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[hloeung@darkon tmp]$ iwconfig
lo no wireless extensions.

Module was only loaded with 802.11n enabled and within a few minutes, over 1.7k TX retries:

wlan0 IEEE 802.11abgn ESSID:"star-local-5GHz"
          Mode:Managed Frequency:5.22 GHz Access Point: C0:25:06:A6:31:0E
          Bit Rate=162 Mb/s Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:on
          Link Quality=58/70 Signal level=-52 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:1714 Invalid misc:2 Missed beacon:0

Also spikes in latency and packet loss:

64 bytes from 203.12.160.35: icmp_seq=12 ttl=227 time=82.6 ms
64 bytes from 203.12.160.35: icmp_seq=13 ttl=227 time=108 ms
64 bytes from 203.12.160.35: icmp_seq=14 ttl=227 time=25.0 ms
64 bytes from 203.12.160.35: icmp_seq=15 ttl=227 time=22.0 ms
64 bytes from 203.12.160.35: icmp_seq=16 ttl=227 time=49.5 ms
64 bytes from 203.12.160.35: icmp_seq=17 ttl=227 time=53.0 ms
64 bytes from 203.12.160.35: icmp_seq=18 ttl=227 time=25.8 ms
64 bytes from 203.12.160.35: icmp_seq=20 ttl=227 time=650 ms
64 bytes from 203.12.160.35: icmp_seq=21 ttl=227 time=1806 ms
64 bytes from 203.12.160.35: icmp_seq=22 ttl=227 time=813 ms
64 bytes from 203.12.160.35: icmp_seq=23 ttl=227 time=41.3 ms
64 bytes from 203.12.160.35: icmp_seq=24 ttl=227 time=42.1 ms
64 bytes from 203.12.160.35: icmp_seq=25 ttl=227 time=40.3 ms
64 bytes from 203.12.160.35: icmp_seq=26 ttl=227 time=57.3 ms
64 bytes from 203.12.160.35: icmp_seq=27 ttl=227 time=47.3 ms
64 bytes from 203.12.160.35: icmp_seq=28 ttl=227 time=20.0 ms
64 bytes from 203.12.160.35: icmp_seq=29 ttl=227 time=53.2 ms
64 bytes from 203.12.160.35: icmp_seq=30 ttl=227 time=42.4 ms
64 bytes from 203.12.160.35: icmp_seq=31 ttl=227 time=36.3 ms
64 bytes from 203.12.160.35: icmp_seq=32 ttl=227 time=55.4 ms
64 bytes from 203.12.160.35: icmp_seq=33 ttl=227 time=44.2 ms
64 bytes from 203.12.160.35: icmp_seq=34 ttl=227 time=1510 ms
64 bytes from 203.12.160.35: icmp_seq=35 ttl=227 time=501 ms
64 bytes from 203.12.160.35: icmp_seq=36 ttl=227 time=1290 ms
64 bytes from 203.12.160.35: icmp_seq=37 ttl=227 time=288 ms
64 bytes from 203.12.160.35: icmp_seq=38 ttl=227 time=55.3 ms
64 bytes from 203.12.160.35: icmp_seq=39 ttl=227 time=37.0 ms

Yet with 802.11n disabled, all seems happier.

Changed in linux (Ubuntu Saucy):
status: Incomplete → Confirmed
Alberto Salvia Novella (es20490446e)
Changed in linux (Ubuntu Saucy):
status: Confirmed → Triaged
status: Triaged → Confirmed
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Please, can anyone report this bug upstream? (https://wiki.ubuntu.com/Bugs/Upstream/kernel)

Revision history for this message
penalvch (penalvch) wrote :

Cut from Bug Description.

tags: added: bot-stop-nagging needs-full-computer-model
removed: kernel-request-3.11.0-7.14
description: updated
tags: added: needs-upstream-testing
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: 8086:422b [iwlwifi] Intel Centrino Ultimate-N 6300 AGN and packet loss
+ using WiFi-N
Revision history for this message
Haw Loeung (hloeung) wrote : Re: 8086:422b [iwlwifi] Intel Centrino Ultimate-N 6300 AGN and packet loss using WiFi-N

NP900X3A-A01AU. Original came with Broadcom WiFi adaptor, I replaced it with an Intel Ultimate-N 6300 (Model 633ANHMW).

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: removed: needs-full-computer-model
penalvch (penalvch)
summary: - 8086:422b [iwlwifi] Intel Centrino Ultimate-N 6300 AGN and packet loss
- using WiFi-N
+ 8086:422b [NP900X3A-A01AU] Intel Centrino Ultimate-N 6300 AGN and packet
+ loss using WiFi-N
penalvch (penalvch)
Changed in linux (Ubuntu):
importance: High → Low
status: Confirmed → Incomplete
summary: - 8086:422b [NP900X3A-A01AU] Intel Centrino Ultimate-N 6300 AGN and packet
- loss using WiFi-N
+ 8086:422b [Samsung NP900X3A-A01AU] Intel Centrino Ultimate-N 6300 AGN
+ and packet loss using WiFi-N
Revision history for this message
Haw Loeung (hloeung) wrote :
Download full text (3.8 KiB)

Hi,

I've tested the latest upstream kernel and it seems the problem still exists.

[hloeung@darkon tmp]$ uname -a
Linux darkon 3.11.10-03111001-generic #201312110635 SMP Wed Dec 11 11:35:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

(from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.1-saucy/)

Without 11n_disable=1:

| [hloeung@darkon tmp]$ ping 203.12.160.35 -c 100 | grep -v 'ttl=[[:digit:]]\+[[:space:]]time=[[:digit:]]\{2\}\.'
| PING 203.12.160.35 (203.12.160.35) 56(84) bytes of data.
| 64 bytes from 203.12.160.35: icmp_seq=13 ttl=227 time=1492 ms
| 64 bytes from 203.12.160.35: icmp_seq=14 ttl=227 time=502 ms
| 64 bytes from 203.12.160.35: icmp_seq=18 ttl=227 time=1979 ms
| 64 bytes from 203.12.160.35: icmp_seq=19 ttl=227 time=1001 ms
| 64 bytes from 203.12.160.35: icmp_seq=20 ttl=227 time=1595 ms
| 64 bytes from 203.12.160.35: icmp_seq=21 ttl=227 time=636 ms
| 64 bytes from 203.12.160.35: icmp_seq=26 ttl=227 time=1661 ms
| 64 bytes from 203.12.160.35: icmp_seq=27 ttl=227 time=701 ms
| 64 bytes from 203.12.160.35: icmp_seq=31 ttl=227 time=1321 ms
| 64 bytes from 203.12.160.35: icmp_seq=33 ttl=227 time=565 ms
| 64 bytes from 203.12.160.35: icmp_seq=50 ttl=227 time=719 ms
| 64 bytes from 203.12.160.35: icmp_seq=54 ttl=227 time=1503 ms
| 64 bytes from 203.12.160.35: icmp_seq=55 ttl=227 time=512 ms
| 64 bytes from 203.12.160.35: icmp_seq=56 ttl=227 time=602 ms
| 64 bytes from 203.12.160.35: icmp_seq=60 ttl=227 time=1500 ms
| 64 bytes from 203.12.160.35: icmp_seq=61 ttl=227 time=517 ms
| 64 bytes from 203.12.160.35: icmp_seq=62 ttl=227 time=961 ms
| 64 bytes from 203.12.160.35: icmp_seq=76 ttl=227 time=1439 ms
| 64 bytes from 203.12.160.35: icmp_seq=77 ttl=227 time=450 ms
| 64 bytes from 203.12.160.35: icmp_seq=82 ttl=227 time=1442 ms
| 64 bytes from 203.12.160.35: icmp_seq=83 ttl=227 time=454 ms
| 64 bytes from 203.12.160.35: icmp_seq=88 ttl=227 time=1214 ms
| 64 bytes from 203.12.160.35: icmp_seq=89 ttl=227 time=214 ms
| 64 bytes from 203.12.160.35: icmp_seq=93 ttl=227 time=1182 ms
| 64 bytes from 203.12.160.35: icmp_seq=94 ttl=227 time=667 ms
| 64 bytes from 203.12.160.35: icmp_seq=100 ttl=227 time=1384 ms
|
| --- 203.12.160.35 ping statistics ---
| 100 packets transmitted, 97 received, 3% packet loss, time 99188ms
| rtt min/avg/max/mdev = 17.821/287.165/1979.984/501.613 ms, pipe 2
|
| [hloeung@darkon tmp]$ iwconfig
| lo no wireless extensions.
|
| wlan0 IEEE 802.11abgn ESSID:"star-local-5GHz"
| Mode:Managed Frequency:5.22 GHz Access Point: C0:25:06:A6:31:0E
| Bit Rate=240 Mb/s Tx-Power=15 dBm
| Retry long limit:7 RTS thr:off Fragment thr:off
| Power Management:off
| Link Quality=61/70 Signal level=-49 dBm
| Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
| Tx excessive retries:18288 Invalid misc:21 Missed beacon:0

Notice the high Tx excessive retries? Now iwlwifi module reloaded with 11n_disable=1:

| [hloeung@darkon tmp]$ ping 203.12.160.35 -c 100 | grep -v 'ttl=[[:digit:]]\+[[:space:]]time=[[:digit:]]\{2\}\.'
| PING 203.12.160.35 (203.12.160.35) 56(84) bytes of data.
|
| --- 203.12.160.35 ping statistics ---
| 100 packets trans...

Read more...

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.11.10.1-saucy
removed: needs-upstream-testing
Haw Loeung (hloeung)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
penalvch (penalvch)
tags: added: needs-upstream-testing
removed: kernel-bug-exists-upstream
Revision history for this message
Haw Loeung (hloeung) wrote :

Hi,

I just upgraded to Trusty earlier on today so am now running with Linux 3.12. Still seeing the same issues:

| [hloeung@darkon tmp]$ cat /etc/lsb-release
| DISTRIB_ID=Ubuntu
| DISTRIB_RELEASE=14.04
| DISTRIB_CODENAME=trusty
| DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)"

| [hloeung@darkon tmp]$ uname -a
| Linux darkon 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:39:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
|
| [hloeung@darkon tmp]$ ping 203.12.160.35 -c 100 | grep -v 'ttl=[[:digit:]]\+[[:space:]]time=[[:digit:]]\{2\}\.'
| PING 203.12.160.35 (203.12.160.35) 56(84) bytes of data.
| 64 bytes from 203.12.160.35: icmp_seq=2 ttl=227 time=420 ms
| 64 bytes from 203.12.160.35: icmp_seq=6 ttl=227 time=133 ms
| 64 bytes from 203.12.160.35: icmp_seq=53 ttl=227 time=125 ms
| 64 bytes from 203.12.160.35: icmp_seq=68 ttl=227 time=109 ms
| 64 bytes from 203.12.160.35: icmp_seq=88 ttl=227 time=1515 ms
| 64 bytes from 203.12.160.35: icmp_seq=89 ttl=227 time=513 ms
| 64 bytes from 203.12.160.35: icmp_seq=99 ttl=227 time=2656 ms
| 64 bytes from 203.12.160.35: icmp_seq=100 ttl=227 time=1714 ms
|
| --- 203.12.160.35 ping statistics ---
| 100 packets transmitted, 91 received, 9% packet loss, time 99210ms
| rtt min/avg/max/mdev = 16.272/99.272/2656.825/362.102 ms, pipe 2

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc4-trusty/ seems incomplete and only has dpkg for headers so I went with http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/. Again, doesn't appear to be resolved:

| [hloeung@darkon tmp]$ uname -a
| Linux darkon 3.13.0-031300rc3-generic #201312061335 SMP Fri Dec 6 18:37:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
|
| [hloeung@darkon tmp]$ ping 203.12.160.35 -c 100 | grep -v 'ttl=[[:digit:]]\+[[:space:]]time=[[:digit:]]\{2\}\.'
| PING 203.12.160.35 (203.12.160.35) 56(84) bytes of data.
| 64 bytes from 203.12.160.35: icmp_seq=1 ttl=227 time=744 ms
| 64 bytes from 203.12.160.35: icmp_seq=5 ttl=227 time=680 ms
| 64 bytes from 203.12.160.35: icmp_seq=11 ttl=227 time=1160 ms
| 64 bytes from 203.12.160.35: icmp_seq=12 ttl=227 time=528 ms
| 64 bytes from 203.12.160.35: icmp_seq=31 ttl=227 time=134 ms
| 64 bytes from 203.12.160.35: icmp_seq=32 ttl=227 time=594 ms
| 64 bytes from 203.12.160.35: icmp_seq=33 ttl=227 time=144 ms
| 64 bytes from 203.12.160.35: icmp_seq=34 ttl=227 time=374 ms
| 64 bytes from 203.12.160.35: icmp_seq=46 ttl=227 time=1276 ms
| 64 bytes from 203.12.160.35: icmp_seq=47 ttl=227 time=296 ms
| 64 bytes from 203.12.160.35: icmp_seq=48 ttl=227 time=411 ms
| 64 bytes from 203.12.160.35: icmp_seq=94 ttl=227 time=182 ms
|
| --- 203.12.160.35 ping statistics ---
| 100 packets transmitted, 99 received, 1% packet loss, time 99146ms
| rtt min/avg/max/mdev = 17.350/86.519/1276.172/210.985 ms, pipe 2

Regards,

Haw

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream-vv3.13-rc3-trusty trusty
removed: kernel-bug-exists-upstream-v3.11.10.1-saucy needs-upstream-testing
Haw Loeung (hloeung)
tags: added: kernel-bug-exists-upstream
Haw Loeung (hloeung)
Changed in linux (Ubuntu Trusty):
importance: Low → High
penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-vv3.13-rc3
removed: kernel-bug-exists-upstream-vv3.13-rc3-trusty
tags: added: kernel-bug-exists-upstream-v3.13-rc3
removed: kernel-bug-exists-upstream-vv3.13-rc3
Revision history for this message
penalvch (penalvch) wrote :

Haw Loeung, thank you for performing the requested tests. Could you please fill in the missing debug information following https://wiki.ubuntu.com/Kernel/LinuxWireless ?

Marking Importance Low as per https://wiki.ubuntu.com/Bugs/Importance :
"Low: Bugs which affect functionality, but to a lesser extent than most bugs, examples are:
 Bugs that have easy work-arounds"

Changed in linux (Ubuntu Trusty):
importance: High → Low
status: Confirmed → Incomplete
Changed in linux (Ubuntu Saucy):
importance: High → Low
Shaawin Vsingam (shaawin95)
Changed in linux (Ubuntu Trusty):
status: Incomplete → Confirmed
Revision history for this message
Shaawin Vsingam (shaawin95) wrote :

Why was this marked incomplete ? I can definitely confirm it exists in trusty, having the same results as Loeung

Revision history for this message
penalvch (penalvch) wrote :

Shaawin Vsingam, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in linux (Ubuntu Trusty):
status: Confirmed → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Closing unsupported series nomination.

This bug was nominated against a series that is no longer supported, ie saucy. The bug task representing the saucy nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Saucy):
status: Confirmed → Won't Fix
To post a comment you must log in.