wifi works unstable 'kernel-fixed-upstream'

Bug #1421366 reported by Alexander Bubnov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Hello!
My wifi works unstable. It means network goes down time to time. And it makes me crazy. I am not sure where to find a cause but I found strange errors in dmesg
[ 16.264702] iwlwifi 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 16.265640] iwlwifi 0000:05:00.0: irq 48 for MSI/MSI-X
[ 16.598809] iwlwifi 0000:05:00.0: loaded firmware version 8.24.2.2 op_mode iwldvm
[ 16.628704] iwlwifi 0000:05:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 16.628706] iwlwifi 0000:05:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
[ 16.628707] iwlwifi 0000:05:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 16.628709] iwlwifi 0000:05:00.0: Detected Intel(R) WiMAX/WiFi Link 5150 ABG, REV=0x44
[ 16.629218] iwlwifi 0000:05:00.0: L1 Enabled - LTR Disabled
[ 22.416806] iwlwifi 0000:05:00.0: L1 Enabled - LTR Disabled
[ 22.419871] iwlwifi 0000:05:00.0: Radio type=0x1-0x1-0x0
[ 22.542892] iwlwifi 0000:05:00.0: L1 Enabled - LTR Disabled
[ 22.546075] iwlwifi 0000:05:00.0: Radio type=0x1-0x1-0x0
[ 48.073232] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 48.073308] iwlwifi 0000:05:00.0: CSR values:
[ 48.073310] iwlwifi 0000:05:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
[ 48.073335] iwlwifi 0000:05:00.0: CSR_HW_IF_CONFIG_REG: 0X00484704
[ 48.073360] iwlwifi 0000:05:00.0: CSR_INT_COALESCING: 0X00000040
[ 48.073369] iwlwifi 0000:05:00.0: CSR_INT: 0X00000000
[ 48.073377] iwlwifi 0000:05:00.0: CSR_INT_MASK: 0X00000000
[ 48.073386] iwlwifi 0000:05:00.0: CSR_FH_INT_STATUS: 0X00000000
[ 48.073394] iwlwifi 0000:05:00.0: CSR_GPIO_IN: 0X00000000
[ 48.073403] iwlwifi 0000:05:00.0: CSR_RESET: 0X00000000
[ 48.073412] iwlwifi 0000:05:00.0: CSR_GP_CNTRL: 0X080403c5
[ 48.073420] iwlwifi 0000:05:00.0: CSR_HW_REV: 0X00000044
[ 48.073429] iwlwifi 0000:05:00.0: CSR_EEPROM_REG: 0X00000000
[ 48.073438] iwlwifi 0000:05:00.0: CSR_EEPROM_GP: 0X90000804
[ 48.073446] iwlwifi 0000:05:00.0: CSR_OTP_GP_REG: 0X00020000
[ 48.073455] iwlwifi 0000:05:00.0: CSR_GIO_REG: 0X00080042
[ 48.073464] iwlwifi 0000:05:00.0: CSR_GP_UCODE_REG: 0X0000199b
[ 48.073472] iwlwifi 0000:05:00.0: CSR_GP_DRIVER_REG: 0X00000000
[ 48.073481] iwlwifi 0000:05:00.0: CSR_UCODE_DRV_GP1: 0X00000000
[ 48.073506] iwlwifi 0000:05:00.0: CSR_UCODE_DRV_GP2: 0X00000000
[ 48.073514] iwlwifi 0000:05:00.0: CSR_LED_REG: 0X00000040
[ 48.073523] iwlwifi 0000:05:00.0: CSR_DRAM_INT_TBL_REG: 0X88070876
[ 48.073531] iwlwifi 0000:05:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
[ 48.073540] iwlwifi 0000:05:00.0: CSR_ANA_PLL_CFG: 0X00880300
[ 48.073549] iwlwifi 0000:05:00.0: CSR_HW_REV_WA_REG: 0X0001001a
[ 48.073573] iwlwifi 0000:05:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000
[ 48.073576] iwlwifi 0000:05:00.0: FH register values:
[ 48.073628] iwlwifi 0000:05:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X07242000
[ 48.073675] iwlwifi 0000:05:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X0071b6c0
[ 48.073694] iwlwifi 0000:05:00.0: FH_RSCSR_CHNL0_WPTR: 0X00000080
[ 48.073713] iwlwifi 0000:05:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114
[ 48.073733] iwlwifi 0000:05:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
[ 48.073752] iwlwifi 0000:05:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
[ 48.073765] iwlwifi 0000:05:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
[ 48.073779] iwlwifi 0000:05:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
[ 48.073798] iwlwifi 0000:05:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
[ 48.073802] iwlwifi 0000:05:00.0: Loaded firmware version: 8.24.2.2
[ 48.073937] iwlwifi 0000:05:00.0: Start IWL Error Log Dump:
[ 48.073939] iwlwifi 0000:05:00.0: Status: 0x0000004C, count: 5
[ 48.073942] iwlwifi 0000:05:00.0: 0x00000004 | NMI_INTERRUPT_WDG
[ 48.073944] iwlwifi 0000:05:00.0: 0x000006F4 | uPc
[ 48.073946] iwlwifi 0000:05:00.0: 0x000005BA | branchlink1
[ 48.073949] iwlwifi 0000:05:00.0: 0x000006F8 | branchlink2
[ 48.073951] iwlwifi 0000:05:00.0: 0x000008C2 | interruptlink1
[ 48.073953] iwlwifi 0000:05:00.0: 0x00005B02 | interruptlink2
[ 48.073955] iwlwifi 0000:05:00.0: 0x00000002 | data1
[ 48.073957] iwlwifi 0000:05:00.0: 0x07030000 | data2
[ 48.073959] iwlwifi 0000:05:00.0: 0x00000068 | line
[ 48.073961] iwlwifi 0000:05:00.0: 0x35C02C5A | beacon time
[ 48.073963] iwlwifi 0000:05:00.0: 0x8BCA63A6 | tsf low
[ 48.073965] iwlwifi 0000:05:00.0: 0x0000005A | tsf hi
[ 48.073967] iwlwifi 0000:05:00.0: 0x00000000 | time gp1
[ 48.073970] iwlwifi 0000:05:00.0: 0x01855040 | time gp2
[ 48.073972] iwlwifi 0000:05:00.0: 0x00000000 | time gp3
[ 48.073974] iwlwifi 0000:05:00.0: 0x00010818 | uCode version
[ 48.073976] iwlwifi 0000:05:00.0: 0x00000000 | hw version
[ 48.073978] iwlwifi 0000:05:00.0: 0x00484704 | board version
[ 48.073980] iwlwifi 0000:05:00.0: 0x00000002 | hcmd

May be it is a dublicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1099487
And wifi does not work after waking up at all. I do not know any work arounds. Please feel free to contact me. I love ubuntu and ready to help.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-45-generic 3.13.0-45.74
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ts 1475 F.... pulseaudio
CRDA:
 country RU:
  (2402 - 2482 @ 40), (N/A, 20)
  (5735 - 5835 @ 20), (N/A, 30)
CurrentDesktop: Unity
Date: Thu Feb 12 22:22:48 2015
HibernationDevice: RESUME=UUID=0b240f70-b31e-4a9c-a34d-1de66cf1d394
InstallationDate: Installed on 2015-02-08 (3 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: LENOVO 2874RV4
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=6cb89af7-7e1c-4430-b5d7-1a1e4a6a1675 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-45-generic N/A
 linux-backports-modules-3.13.0-45-generic N/A
 linux-firmware 1.127.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6JET77WW (1.35 )
dmi.board.name: 2874RV4
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6JET77WW(1.35):bd04/30/2010:svnLENOVO:pn2874RV4:pvrThinkPadSL410:rvnLENOVO:rn2874RV4:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2874RV4
dmi.product.version: ThinkPad SL410
dmi.sys.vendor: LENOVO

Revision history for this message
Alexander Bubnov (alexander-bubnov) wrote :
Revision history for this message
Alexander Bubnov (alexander-bubnov) wrote :

see some restarting something in dmesg:

$ dmesg | grep iwlwifi | grep Restarting
[ 48.073232] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 91.410595] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 154.214881] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 237.186490] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 340.408895] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 460.220703] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 580.234820] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 700.046086] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 820.062022] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 940.488260] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 1060.196601] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: wifi works unstable

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 kernel[0].

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

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

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

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Alexander Bubnov (alexander-bubnov) wrote :

I just installed Ubuntu on Lenovo laptop a week ago so I do not know if this problem existed before.
But I have another laptop, Toshiba. And I have never faced that problem on it. So it seems the problem is related to specific hardware. Let me know if you need to check the problem under prior Ubuntu release I will do it for you.
And I will check this problem with upstream kernel as you asked and say result today or tomorrow.

Revision history for this message
Alexander Bubnov (alexander-bubnov) wrote :

Summury.
1. Kernels beginning at 3.13.0-41 are buggy kernels
2. 3.13.0-40 works fine.
3. with upstream kernel 3.19 the bug is not reproducible.

wifi works fine with 3.13.0-40-generic kernel after this kernel beginnig at 3.13.0-41-generic wifi works unstable, time to time internet connection is lost.
Also wifi is not upping after sleeping or hibernation with kernels somewhere beginning at 3.13.0-41. So if someone has similar problems try to go back to 3.13.0-40 kernel.
But really problem with not upping wifi after sleeping and hibernation is not reproducible with 3.13.0-41 or hard reproducible. But it is easier reproducible with 3.13.0-45. Kernels between 41 and 45 I did not tested for not upping wifi because I already have faced unstable wifi with 40 kernel that is enough to move to and stay on it.
And of course errors I mentioned in this issue appears with kernel beginning 3.13.0-41 and including 3.13.0-41. Here they are:

[ 28.076699] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x82000000.
[ 47.038298] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 90.230594] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 153.073963] iwlwifi 0000:05:00.0: Microcode SW error detected. Restarting 0x2000000.

So it seems there is a regression bug in 3.13.0-41.
I have installed upstream kernel 3.19, got these warnings
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169

I ignored them. After reboot everything with wifi works well.
No errors in dmesg and internet is stable.

uname -a of upstream kernel:
Linux ts-ThinkPad-SL410 3.19.0-031900-generic #201502091451 SMP Mon Feb 9 14:52:52 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

summary: - wifi works unstable
+ wifi works unstable 'kernel-fixed-upstream'
Revision history for this message
Alexander Bubnov (alexander-bubnov) wrote :

How to set tag 'kernel-fixed-upstream'? I just have added it at the title. Right?

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

Alexander Bubnov, as per http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-sl-series-laptops/thinkpad-sl410 an update to your computer's buggy and outdated BIOS is available (1.52). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed.

Thank you for your understanding.

tags: added: bios-outdated-1.52
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alexander Bubnov (alexander-bubnov) wrote :

While I am collecting requested information I noticed that the problem disappeared with the latest kernel update, 3.13.0-46-generic.
But anyway I updated BIOS and checked if it helps on kernel 3.13.0-41. But problem still exists i.e. BIOS update does not help considering kernel 3.13.0-41.
But now it does not matter, so we can close this bug because while we are investigating the problem it seems someone has fixed it. :-)
I cannot be 100% sure because I have not tested kernel 3.13.0-46 and old BIOS.

Now output
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for ts:
6JET94WW (1.52 )
06/19/2012

Thank you for participating.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Alexander Bubnov (alexander-bubnov) wrote :

I mean thank you for your work

Revision history for this message
penalvch (penalvch) wrote :

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

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.