Bug 203851 - iwlwifi: 7260: some xfer after boot, 7260 doesn't work
Summary: iwlwifi: 7260: some xfer after boot, 7260 doesn't work
Status: CLOSED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: DO NOT USE - assign "network-wireless-intel" component instead
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-08 12:29 UTC by rejohe5856
Modified: 2019-06-10 13:55 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.2-rc3
Subsystem:
Regression: No
Bisected commit-id:


Attachments
testing configuration file (42.02 KB, application/gzip)
2019-06-08 12:29 UTC, rejohe5856
Details
7260 stopped, so disabled and enabled, and worked again. (73.09 KB, text/plain)
2019-06-08 12:30 UTC, rejohe5856
Details
7260 working correctly with 5.1.7 (70.89 KB, text/plain)
2019-06-08 12:31 UTC, rejohe5856
Details
iwlwifi log file recorded by trace-cmd (1.12 MB, text/plain)
2019-06-10 05:35 UTC, rejohe5856
Details

Description rejohe5856 2019-06-08 12:29:44 UTC
Created attachment 283155 [details]
testing configuration file

I'm trying kernel-5.2-rc3 on some of my computers (fedora 30.)  Wireless-ac 7260 on ivybridge notebook works fine for some minutes.  But after some usage; ie browsing about 10-20 homepages, wifi stops working.  But ifconfig shows that device (wlp2s0) has correct ipv4/ipv6 addresses.

I'm using gnome, so once disabling wifi and enabling it again, it starts working again, but after some browsing, it stops.

I tried the same .config file with kernel-5.1.7, it works fine.  So it must be due to kernel driver.

I attach the config file and dmesg logs of kernel-5.2-rc3 (fails and restarting) and of kernel-5.1.7 (normally working).
Comment 1 rejohe5856 2019-06-08 12:30:51 UTC
Created attachment 283157 [details]
7260 stopped, so disabled and enabled, and worked again.
Comment 2 rejohe5856 2019-06-08 12:31:24 UTC
Created attachment 283159 [details]
7260 working correctly with 5.1.7
Comment 3 Emmanuel Grumbach 2019-06-09 20:03:22 UTC
nothing wrong in the logs. we just can see that you disable and re-enable WiFi.

Can you try to  bisect?
Comment 4 rejohe5856 2019-06-09 22:45:19 UTC
Sorry, what's "bisect"?   I'll try "journalctl -b", but I don't know "bisect."
Comment 5 rejohe5856 2019-06-09 23:04:31 UTC
"bisect" is usually used in anatomy..   As rc4 was released yesterday, I'll try "journalctl -b" and other ways with it.
Comment 6 rejohe5856 2019-06-10 05:35:22 UTC
Created attachment 283167 [details]
iwlwifi log file recorded by trace-cmd

This is retrieved with "trace-cmd record" and decoded with "trace-cmd report".   During this short time, 7260 was locked.

During this period, I browsed google chrome and it was locked.   However I cannot find any sign of lock in this log file!

Anybody tell me how I can trace this phenomenon?
Comment 7 mattchen 2019-06-10 07:42:26 UTC
You have a viable kernel that can show your 7260 is working fine, you also have a defect kernel version that shows your 7260 is somehow failed.
Bisect is your friend to search for what patch(es) that might cause this issue.
Would be good for you to be a fiend of git.
https://git-scm.com/docs/git-bisect
Comment 8 rejohe5856 2019-06-10 07:57:03 UTC
Thanks mattchen,

It makes a sense.   I'll try each patch.

Actually now I'm on 5.1.8 and having no problem at all with 7260.
Comment 9 rejohe5856 2019-06-10 10:07:38 UTC
For a starter, I skipped all of git://git.kernel.org/pub/scm/linux/kernel/git/davem/net and git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next since 5.1, but my 7260 still has problems.

Now I found more possible tree, kernel/git/iwlwifi/ trees.....I try to skip these.
Comment 10 rejohe5856 2019-06-10 13:55:03 UTC
After disabling ipv6 ability with wifi, I found it worked perfectly.   After some trials, I found proper settings enables ipv6 capability with 7260 wifi card.   It's not due to kernel, but probably due to fedora or my isp equipments.

Sorry for your inconvenience.   I close this report as "Invalid."

Sincerely,

Note You need to log in before you can comment on or make changes to this bug.