10ec:b723 Realtek RTL8723BE wireless card drops connection

Bug #1459367 reported by Arnaud LE CAM
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I loose my connection randomly (HP laptop, model 15-r207nf) with Realtek RTL8723BE wireless card connecting to my router via 802.11n at 150 Mbps:
Router manufacturer : Free
Model : Freebox Server (r1)
Commercial name : Freebox Revolution 6
Firmware version : 3.1.1

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/pcmC0D0p: arnaud 1415 F...m pulseaudio
 /dev/snd/controlC0: arnaud 1409 F.... panel-17-mixer
                      arnaud 1415 F.... pulseaudio
CurrentDesktop: XFCE
Date: Wed May 27 19:46:19 2015
HibernationDevice: RESUME=UUID=677c116e-29ca-4442-a248-9302170fbb6b
InstallationDate: Installed on 2015-04-18 (38 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=3c2695c5-1341-4096-966f-ad24d315f451 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
UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2213
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.47
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.32:bd10/28/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0974120000405F00000620180:rvnHewlett-Packard:rn2213:rvr57.47:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 0974120000405F00000620180
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :
summary: Realtek RTL8723BE wireless card drops connection in Linux kernel
- 3.19.0-13
+ 3.19.0-18
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
penalvch (penalvch)
tags: added: bios-outdated-f.36
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

Hi,
Bios-updating (Bios version : F.36 / Bios release date : 12/18/2014) didn't change anything.

But I had a look on dmesg's outputs, and it gives two informations :

1) dmesg's output is always the same on reconnection

 wlan0: deauthenticated from f4:ca:e5:f0:33:98 (Reason: 2=PREV_AUTH_NOT_VALID)
 cfg80211: Calling CRDA to update world regulatory domain
 cfg80211: World regulatory domain updated:
 cfg80211: DFS Master region: unset
 cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
 cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
 cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
 cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
 cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
 cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
 wlan0: authenticate with f4:ca:e5:f0:33:98
 wlan0: send auth to f4:ca:e5:f0:33:98 (try 1/3)
 wlan0: authenticated
 wlan0: associate with f4:ca:e5:f0:33:98 (try 1/3)
 wlan0: RX AssocResp from f4:ca:e5:f0:33:98 (capab=0x411 status=0 aid=2)
 wlan0: associated

2) those "groups of dmesgs" appear periodically (time between two reconnections, in fact) :
600 sec
1200 sec
600 sec
600 sec
1200 sec

I hope it will be useful...

Best regards,

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

Arnaud LE CAM, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-f.36
removed: bios-outdated-f.36
Changed in linux (Ubuntu):
importance: Low → Medium
status: Confirmed → Incomplete
Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

I installed latest upstream kernel available (4.1.0-994-generic #201505300205), nothing has changed.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-994-generic
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

nothing has changed with 4.1-rc5

tags: added: kernel-bug-exists-upstream-4.1-rc5
removed: kernel-bug-exists-upstream-4.1.0-994-generic
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

Christopher,
Here are informations you asked for :

Router manufacturer : Free
Model : Freebox Server (r1)
Commercial name : Freebox Revolution 6
Firmware version : 3.1.1

And, if it could help :
- Freebox Server software can be found here : http://floss.freebox.fr/freebox_server/3.0.2/index.html
- Dev's blog can be found here : http://dev.freebox.fr/blog/

Thank you

Revision history for this message
penalvch (penalvch) wrote :

Arnaud LE CAM, could you please comment to if this is with 802.11n (150, 300, etc.), 802.11g, or both?

tags: added: needs-workaround-test
Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

Christopher,
My router connects with 802.11n at 150 mps (but the router also supports 802.11b and 802.11g).
Best regards,

Revision history for this message
penalvch (penalvch) wrote :

Arnaud LE CAM, could you please provide the results of the following terminal command:
systool -v -m rtl8723be

Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

Here it is :

Module = "rtl8723be"

  Attributes:
    coresize = "98304"
    initsize = "0"
    initstate = "live"
    refcnt = "0"
    srcversion = "35F1A640DD23340CE249D81"
    taint = ""
    uevent = <store method only>

  Parameters:
    debug = "0"
    disable_watchdog = "N"
    fwlps = "Y"
    ips = "Y"
    swenc = "N"
    swlps = "N"

  Sections:
    .bss = "0x0000000000000000"
    .data = "0x0000000000000000"
    .exit.text = "0x0000000000000000"
    .gnu.linkonce.this_module= "0x0000000000000000"
    .init.text = "0x0000000000000000"
    .note.gnu.build-id = "0x0000000000000000"
    .parainstructions = "0x0000000000000000"
    .rodata = "0x0000000000000000"
    .rodata.str1.1 = "0x0000000000000000"
    .rodata.str1.8 = "0x0000000000000000"
    .strtab = "0x0000000000000000"
    .symtab = "0x0000000000000000"
    .text = "0x0000000000000000"
    __mcount_loc = "0x0000000000000000"
    __param = "0x0000000000000000"

Revision history for this message
penalvch (penalvch) wrote :

Arnaud LE CAM, could you please advise if the following file modification improves the situation (please restart first before retesting):
sudo nano /etc/modprobe.d/rtl8723be.conf
options rtl8723be ips=0 fwlps=0

Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

Hi Christopher,
With those options, I'm connected without any interruption for 6 hours. So I suppose it worked... Thank you for your help.
Few questions now :
Can I downgrade back to kernel 3.19.0-18 (setting ips and fwlps options to 0) to keep a "regular" Ubuntu install ?
Should I do nothing else to help debugging ?

Revision history for this message
penalvch (penalvch) wrote :

Arnaud LE CAM, just to clarify, how long would you go without interruption before the WORKAROUND?

>"Can I downgrade back to kernel 3.19.0-18 (setting ips and fwlps options to 0) to keep a "regular" Ubuntu install ?"
Feel free to test and advise if it changes anything.

>"Should I do nothing else to help debugging ?"
Please test the latest mainline kernel (now 4.1-rc6), with and without the WORKAROUND, and advise to the results.

Also, does switching from 802.11n to g at the router change anything?

Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

I've been testing on several configurations :
kernel : 3.19.0-18 / 4.1-rc5 / 4.1-rc7
wifi (n/g)
options flags : fwlps (0/1) and ips (0/1)
It seems that it works exclusively with fwlps=0, regardless kernel version, wifi or ips option (except with 4.1-rc7, where ips option should be set to 0 too).
Results are attached.

penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-4.1-rc7
removed: kernel-bug-exists-upstream-4.1-rc5 needs-workaround-test
Revision history for this message
penalvch (penalvch) wrote :

Arnaud LE CAM, just to clarify, for 4.1-rc7 it works to your expectations without having to use any WORKAROUNDS (i.e. fwlps/ips=0)?

tags: removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1-rc7
Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

For 4.1-rc7 it only works with the following combinations :
fwlps=1 and ips=0 ;
fwlps=0 and ips=1 ;
fwlps=0 and ips=0.

penalvch (penalvch)
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1-rc7
penalvch (penalvch)
description: updated
Revision history for this message
penalvch (penalvch) wrote : Re: 10ec:b723 Realtek RTL8723BE wireless card drops connection in Linux kernel 3.19.0-18

Arnaud LE CAM, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (linux-wireless) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive.

Thank you for your understanding.

summary: - Realtek RTL8723BE wireless card drops connection in Linux kernel
- 3.19.0-18
+ 10ec:b723 Realtek RTL8723BE wireless card drops connection in Linux
+ kernel 3.19.0-18
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Arnaud LE CAM (arnaudlecam) wrote :

Christopher,
It has been reported here :
http://marc.info/?l=linux-wireless&m=143420832618489&w=2
Thank you

penalvch (penalvch)
summary: - 10ec:b723 Realtek RTL8723BE wireless card drops connection in Linux
- kernel 3.19.0-18
+ 10ec:b723 Realtek RTL8723BE wireless card drops connection
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.