Bug 749125
| Summary: | WARNING while connecting to wifi | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Matěj Cepl <mcepl> | ||||||
| Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.2 | CC: | johannes, linville, sgruszka, wey-yi.w.guy | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-11-09 14:24:27 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 530265 [details]
sosreport
Just to note that I have numerous cases of this crash now being at the Linuxcon Europe on the local wifi network. It would be awesome if any questions about this bug were asked before Friday, when I have to leave. This appears to me to result from a crash in the iwl5000 firmware. Wey-yi, does this look familiar to you? Perhaps there is some upstream patch we could apply to recover from the firmware crash (or avoid it altogether)? FWIW, the iwlagn driver in RHEL6 is derived from the version in the upstream 2.6.37 kernel. John, need help here, can I have more information on how it happen and when the firmware crash? I could not find the log contain crash information. but since I am on business trip and my network is very slow, I might miss something Thanks Wey Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. (In reply to comment #3) > Just to note that I have numerous cases of this crash now being at the Linuxcon > Europe on the local wifi network. It would be awesome if any questions about > this bug were asked before Friday, when I have to leave. Sorry, I did not notice this bug, actually I did not looked at bugzilla during linuxcon. Do you still have any chance to reproduce it? I think it could be related with roaming, it is interesting what infrastructure they have in clarion hotel. (In reply to comment #7) > Sorry, I did not notice this bug, actually I did not looked at bugzilla during > linuxcon. Do you still have any chance to reproduce it? Unfortunately not. > I think it could be related with roaming, it is interesting what infrastructure > they have in clarion hotel. Somebody from Intel claimed that the problem is caused by too crowded network, where APs are trying to change some variables (changing frequencies), where firmware sends some warning and Linux driver doesn't take it well. But we were running to the pub and I probably forgot half of that. This is what Johannes wrote me: "Ok, well, this one seems fairly obvious to me now -- we send out the probe request to monitor the connection while we're doing something on another channel. Hindsight being 20/20 and all that, I think this off-channel work infrastructure was probably a mistake ... In fact this is also fairly obviously fixed by your patch to diassociate first -- that will stop the connection monitoring stuff :-) I'll think about fixing it. It won't be trivial though I think. The best way would probably be to do a half multi-channel implementation and queue up all these frames per interface and stop the queues according to the channel or so ..." So we need to rework switching channels/off-channel mechanisms in mac80211. This probably would not be easy to backport to RHEL6 (anyway we do not have reproducer, so not be able to confirm fix). Hopefully things will be ready for RHEL7. I'm closing this bug with UPSTREAM resolution. Please reopen if that bug will start to be annoying and/or reproducer will be available. |
Created attachment 530264 [details] ABRT report Description of problem: I got abrt activated and it generated attached report (I will also attach generated sosreport). Version-Release number of selected component (if applicable): kernel-2.6.32-211.el6.x86_64 How reproducible: happened once Steps to Reproduce: 1. not sure (either suspend/resume, or wifi connecting) 2. 3. Actual results: no visible problems (aside from abrt activated) Expected results: Additional info: