RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 749125 - WARNING while connecting to wifi
Summary: WARNING while connecting to wifi
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stanislaw Gruszka
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-26 09:30 UTC by Matěj Cepl
Modified: 2011-11-09 14:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-09 14:24:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
ABRT report (3.33 KB, text/plain)
2011-10-26 09:30 UTC, Matěj Cepl 		no flags Details
sosreport (1.66 MB, application/x-xz;)
2011-10-26 09:31 UTC, Matěj Cepl 		no flags Details
View All

Description Matěj Cepl 2011-10-26 09:30:30 UTC 
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:
Comment 1 Matěj Cepl 2011-10-26 09:31:33 UTC 
Created attachment 530265 [details]
sosreport
Comment 3 Matěj Cepl 2011-10-26 15:41:45 UTC 
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.
Comment 4 John W. Linville 2011-10-27 13:53:03 UTC 
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.
Comment 5 wey-yi.w.guy 2011-10-28 00:49:25 UTC 
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
Comment 6 RHEL Program Management 2011-10-31 05:47:41 UTC 
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.
Comment 7 Stanislaw Gruszka 2011-11-03 11:16:04 UTC 
(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.
Comment 8 Matěj Cepl 2011-11-03 16:01:07 UTC 
(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.
Comment 9 Stanislaw Gruszka 2011-11-09 14:24:27 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.