8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel 7265

This change was made by a bot.

BIOS updated to 1.07, no change in behavior.

N10ET30W (1.07 )
03/05/2015

No change with 4.0.0-040000rc6.201503291935.

Ryan Finnie, could you please provide the router manufacturer, model, and firmware version presently installed?

ASUS RT-AC87R (retail version of the RT-AC87U, same hardware), firmware 3.0.0.4.378_4608-g7e6c1e5 (latest), in WAP-only mode.

Ryan Finnie, 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.

http://marc.info/?l=linux-wireless&m=142778129512570&w=2

The problem is still being diagnosed on kernel bugzilla, but for the moment, "iw reg set US" seems to be a workaround.

I've had the same problem here.... I have a Thinkpad T450s since 5/1/2015 with the same chip (though linux wants the 7265D ucode though). It was unstable, even when upgrading to the 4.0.1 mainline kernel. What actually kept things stable is by disabling wireless-n.

All the details of how I fixed it from other people:
http://www.reddit.com/r/thinkpad/comments/34ln2h/t450s_ubuntu_1504_unstable_wifi/

Pretty much.... I had to get the latest 7265 ucodes and put it into /lib/firmware:
- sudo rm /lib/firmware/iwlwifi*
- sudo cp /path/to/iwlwifi-7265*-12.ucode /lib/firmware/.
- reboot....

Normal browsing seemed to be more stable but things like streams, speed tests, and youtube would tank the connection.

Then I had to disable wireless-n:
echo 'options iwlwifi 11n_disable=1' | sudo tee -a /etc/modprobe.d/iwlwifi.conf

now it's completely stable, but I have to lose wireless-n as a result. It's not your fault.... It's Intel's...

Jeremy Jao, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

I was going to submit a new bug with my Carbon X3, but it says linux-image-3.19.0-12-generic is not an official package. I'll try again after a reboot with the new kernel.

Anyway, my symptoms differ. I can get it back with a disable/re-enable. I've noticed download speeds seem to vary dramatically, sometimes connection to a website is lost and regained causing the page to timeout temporarily, etc. This started to occur after I upgraded to 15.04. It did not occur previously. I did this to get all the mouse buttons working properly, which they do, but something between the two really messed with wireless dependability.

@flickerfly: Does is this fix "permanent" in that your internet keeps working after that disable/reenable until the next boot?

No, it isn't stable. It often fails again rapidly.

On Sun, May 31, 2015, 8:50 AM Benjamin Geese <email address hidden>
wrote:

> @flickerfly: Does is this fix "permanent" in that your internet keeps
> working after that disable/reenable until the next boot?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1437913
>
> Title:
> 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel
> 7265
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1437913/+subscriptions
>

Christopher, my understanding is that a bisect can't be done based on this paragraph in the original report.

"This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect."

I'll be glad to try to do what you need, but I'd need a link to some directions. I'm not familiar with that procedure.

Can folks affected by this bug see if 3.18.6 is the last good version and 3.18.7 is the first bad version? If so, I can start a bisect between these two versions.

3.18.6 can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.6-vivid/

3.18.7 can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.7-vivid/

As I already wrote on the other bug which is a duplicate (so iirc we should only continue discussion here?):

I've tested v3.18.14-vivid [1] and it works for me, the first 3.19 (3.19.0-16) version (the one shipping with vivid) does not.

Doing `iw reg set US` as a workaround seems to work though. Note that on the upstream bug it says:

> There's a new patch in 3.19 that adds a check for regulatory validity after the connection has been established. This seems to be the code that is causing the deauth here.

[1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.14-vivid/

The reporter's problem was isolated to being related to having an old regulatory database version, and that's in the process of being remedied. I suspect that most of the "duplicates" for this bug are actually different and won't be fixed by the update ...

Marvin, thanks for that regulatory database hint. I hadn't seen that yet.
I'll try it next time I get my laptop out. I've sadly been booting up
Windows frequently due to this bug and really want to stop that. :-)

On Mon, Jun 1, 2015 at 10:41 AM Seth Forshee <email address hidden>
wrote:

> ** Changed in: wireless-regdb (Ubuntu Vivid)
> Importance: Undecided => Medium
>
> ** Changed in: wireless-regdb (Ubuntu Vivid)
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1437913
>
> Title:
> 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel
> 7265
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1437913/+subscriptions
>

Thanks Andy

On Wed, Jun 3, 2015, 9:11 AM Seth Forshee <email address hidden>
wrote:

> ** Changed in: wireless-regdb (Ubuntu)
> Assignee: (unassigned) => Andy Whitcroft (apw)
>
> ** Changed in: wireless-regdb (Ubuntu Vivid)
> Assignee: (unassigned) => Andy Whitcroft (apw)
>
> ** Changed in: wireless-regdb (Ubuntu)
> Importance: Medium => High
>
> ** Changed in: wireless-regdb (Ubuntu Vivid)
> Importance: Medium => High
>
> ** Also affects: linux (Ubuntu Trusty)
> Importance: Undecided
> Status: New
>
> ** Also affects: wireless-regdb (Ubuntu Trusty)
> Importance: Undecided
> Status: New
>
> ** Also affects: linux (Ubuntu Wily)
> Importance: High
> Status: Invalid
>
> ** Also affects: wireless-regdb (Ubuntu Wily)
> Importance: High
> Assignee: Andy Whitcroft (apw)
> Status: Confirmed
>
> ** Changed in: linux (Ubuntu Trusty)
> Status: New => Invalid
>
> ** Changed in: wireless-regdb (Ubuntu Trusty)
> Status: New => Confirmed
>
> ** Changed in: wireless-regdb (Ubuntu Trusty)
> Importance: Undecided => High
>
> ** Changed in: wireless-regdb (Ubuntu Trusty)
> Assignee: (unassigned) => Andy Whitcroft (apw)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1437913
>
> Title:
> 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel
> 7265
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1437913/+subscriptions
>

@sforshee - I'm trying to better understand the consequences of Ubuntu currently having an "an old regulatory database version", as some System76 customers are having WiFi problems when connecting to AC routers with an Intel 7265 and `sudo iw reg set US` seems to fix their issues.

In particular, should a regulatory domain be set automatically once the database is updated? Currently I'm seeing the world-regulatory domain (ie, not set), which seems to be an intersection of all domains and means some band that could be used aren't (in the US anyway).

FYI, for anyone experiencing this problem, you can permanently set the reg by editing /etc/default/crda like this, replacing US with your country code:

# Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set
# the initial regulatory domain setting for IEEE 802.11 devices which operate
# on this system.
#
# Governments assert the right to regulate usage of radio spectrum within
# their respective territories so make sure you select a ISO/IEC 3166-1 alpha2
# country code suitable for your location or you may infringe on local
# legislature. See `/usr/share/zoneinfo/zone.tab' for a table of timezone
# descriptions containing ISO/IEC 3166-1 alpha2 country codes.

REGDOMAIN=US

On Thu, Jun 04, 2015 at 03:45:32PM -0000, Jason Gerard DeRose wrote:
> @sforshee - I'm trying to better understand the consequences of Ubuntu
> currently having an "an old regulatory database version", as some
> System76 customers are having WiFi problems when connecting to AC
> routers with an Intel 7265 and `sudo iw reg set US` seems to fix their
> issues.
>
> In particular, should a regulatory domain be set automatically once the
> database is updated? Currently I'm seeing the world-regulatory domain
> (ie, not set), which seems to be an intersection of all domains and
> means some band that could be used aren't (in the US anyway).

The answer is a bit complicated. iwlwifi will actually read out a set of
custom regulatory rules from the firmware and supply those to the
wireless core. This becomes the "default" set of rules rather than the
generic world domain when no specific regulatory domain has been
supplied. This could be a similarly conservative set of rules meant to
be "safe" around the world, or it could reflect the rules of the country
where the device was intended to be sold (I'm not sure off the top of my
head which it is for this card, but my best recollection is that it's
the former).

To emphasize the point - even though the kernel has retrieved the world
domain from crda, prints them in dmesg, and outputs them in response to
'iw reg get', these rules are *not* being used for an Intel wireless
card unless the user has manually loaded those rules (e.g. 'iw reg set
00'). Instead the kernel is using the rules it was given by the device's
firmware.

When a specific regulatory domain is set a process in userspace (crda)
will read the rules for that domain from the regulatory database and
load them into the kernel, and those rules will be used instead of the
ones the driver supplied. Sometimes the access point will broadcast
information about the regulatory domain in its beacon frames, in which
case the regulatory rules for the country will be loaded automatically
when connecting to that AP. More often (in my experience at least) the
AP does not provide this information.

The update to the database will change nothing about this process. The
same rules are going to be supplied by iwlwifi, and country-specific
rules will still be loaded or not loaded automatically based on what the
AP is broadcasting exactly as before. All it will change is the rules
which get loaded into the kernel for a given regulatory domain.

You aren't specific about what kind of problems your customers are
experiencing. One possibility is that the AP is using a channel that the
default rules says is not allowed but the US rules do allow, and that
loading the US rules opens up use on that channel. If this is the
problem then it will not be fixed by updating the database.

@sforshee - thank you very much for your explanation, I think I'm starting to understand the issue better.

Hi

Did anyone try the 25.17.12.0 firmware version from :
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
He solve the issue for me, no more disconnection and perfectly stable.
Hope it will help you.

Not for me , I have kernel 3.19.0-21-generic #21, with the latest firmware iwlwifi-7265-12.ucode, and I see only one bar strengh, when I have on the same place 100% in windows

see bug 1284093 which is in the SRU queue now

I have a Toshiba Satellite P55W and it also has Wifi unstable on 14.04 64bit with Intel 7265

Also having this same problem, with HP Envy 15
01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 61)

Using latest firmware. Connection drops after a while of use, pages just stop loading, no indication the connection has dropped. Disabling and enabling the wifi fixes the issue.

Also having this problem with 19.10 on a HP ENVY x360 Convertible 13m-ag0xxx -

03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

Similarly to above, my connection randomly drops, it looks like the driver crashes. Toggling aeroplane mode (or rebooting) gets the wifi working again.

Correction: aeroplane mode works once or twice, after a while rebooting is the only option.