Netdev List
 help / color / mirror / Atom feed
From: "Михаил Новоселов, ШЭМ Думалогия" <mikhailnov@dumalogiya.ru>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [REGRESSION] rtl8723bs (r8723bs) WiFi stopped working on 4.14 on Chuwi Hi12 (Intel CherryTrail SoC)
Date: Sun, 15 Oct 2017 16:37:40 +0300	[thread overview]
Message-ID: <2750281508074660@web27g.yandex.ru> (raw)

Hello,
I've found a regression in kernel 4.14, the last tested kernel was the yesterday daily build http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/ , it worked on 4.12 and 4.13 and now on 4.14 it is able to scan for available networks, but is not able to get an IP adress.
I reported a bug to the kernel's bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=197137 
---------------------------------------------------------------------------------

Hardware platform: Chuwi Hi12 (intell cherrytrail tablet)
On Linux kernels 4.12 and 4.13 the WiFi does work, starting from 4.14 not release builds it does not, including some dily builds of the times somewhere near rc1, the rc3 release and the letest daily build of the code state for 2017-10-04 http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2017-10-05/ 
I will provide logs from 4.14 a bit later, bellow are LOGS FROM 4.13.1 with working WiFi

Full information on hardware and logs (including full dmesg) are here: https://linux-hardware.org/index.php?probe=01521aa6cf (kernel 4.13 and working wifi)

$ dmesg | grep rtl
[    7.899105] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
[    7.899106] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
[   10.570755] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin

Logs from 4.14 with WiFi not working: https://linux-hardware.org/index.php?probe=5c7b00c4cb

                 reply	other threads:[~2017-10-15 13:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2750281508074660@web27g.yandex.ru \
    --to=mikhailnov@dumalogiya.ru \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox