Bug 1020018
| Summary: | Wi-fi randomly break after kernel 3.11.4 update | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adrien D <email> | ||||
| Component: | kernel | Assignee: | fedora-kernel-wireless-iwl | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 19 | CC: | email, gansalmon, ilw, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-12-17 06:14:15 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Adrien D
2013-10-16 19:25:45 UTC
I find my previous bug : https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1015908 3.11.2 : Not OK 3.11.3 : OK 3.11.4 : Not OK. Created attachment 813099 [details]
dmesg | grep iwl
If you want more details, ask me, I'm not used to open bugs on bugzilla. no diff between 3.11.3 and 3.11.4 in mac803211 / cfg80211 / iwlwifi / PCI subsytem. PCI transaction seem to fail. Can you please shutdown your computer, remove the battery wait a few seconds and try again? This seems not to be 3.11.3 -> 3.11.4 regression, but random issue which manifest itself on 3.11.2 and 3.11.4 . If you never seen that before on earlier kernels we probably can assume that it is 3.10 -> 3.11 regression. Yes, i found on the internet a people who have the same prolem. I test wireless connection without battery. Hi, After 5 hours , without battery, no problems (no break) but, there are slowdowns. See that (I truncated the results, but about a ping of 5 is "slow", knowing that my internet connection is correct) : $ ping google.fr PING google.fr (173.194.70.94) 56(84) bytes of data. 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=2 ttl=47 time=818 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=3 ttl=47 time=34.0 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=4 ttl=47 time=30.8 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=5 ttl=47 time=32.3 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=6 ttl=47 time=29.8 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=7 ttl=47 time=848 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=8 ttl=47 time=30.1 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=9 ttl=47 time=29.8 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=10 ttl=47 time=30.7 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=11 ttl=47 time=77.1 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=12 ttl=47 time=38.5 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=13 ttl=47 time=793 ms 64 bytes from fa-in-f94.1e100.net (173.194.70.94): icmp_seq=14 ttl=47 time=30.2 ms OK, 5 hours of uptime today with the battery and I have not encountered any problems. It's like he took some time for the newly installed RPM package "understand" how to function. It's strange .... I manifest this weekend to close the bug if I have not had any problems again. OK, 5 hours of uptime today with the battery and I have not encountered any problems. Ping is correct today. It's like he took some time for the newly installed RPM package "understand" how to function. It's strange .... I manifest this weekend to close the bug if I have not had any problems again. Hi, Today : uptime : 14hours, and no troubles with wi-fi. It's OK for me. Just remove the battery solve this problem ? It's strange ... It would be a coincidence between the kernel update and power problem? In short, it is set ! I guess we can close? Hi, I forgot this bug ... No, I can't close it, because, with kernel 3.11.8 and 3.11.9, I have this problem. I tested with and without battery, it's the same. When I can, I connect my laptop with an Ethernet cable... Because the Wi-Fi still not working correctly. Actually, my uptime is 20hours and Wi-Fi works perfectly (kernel 3.11.10) I don't understand.... I Close the bug : CLOSED INSUFFICIENT_DATA, but I don't know if it's the good status. |