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 614275 - [abrt] kernel: WARNING: at net/mac80211/util.c:536 ieee80211_can_queue_work+0x35/0x50 [mac80211]() (Not tainted)
Summary: [abrt] kernel: WARNING: at net/mac80211/util.c:536 ieee80211_can_queue_work+0...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: John W. Linville
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard: abrt_hash:935309850
: 611816 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-14 02:04 UTC by Scott Dodson
Modified: 2010-11-22 16:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-22 16:01:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
File: backtrace (2.50 KB, text/plain)
2010-07-14 02:04 UTC, Scott Dodson
no flags Details

Description Scott Dodson 2010-07-14 02:04:08 UTC
abrt version: 1.1.9
architecture: x86_64
Attached file: backtrace
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-42.el6.x86_64
package: kernel
reason: WARNING: at net/mac80211/util.c:536 ieee80211_can_queue_work+0x35/0x50 [mac80211]() (Not tainted)
release: Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
How to reproduce: Unsure of what triggered this.
time: 1278417581
uid: 0

Comment 1 Scott Dodson 2010-07-14 02:04:10 UTC
Created attachment 431648 [details]
File: backtrace

Comment 3 RHEL Program Management 2010-07-15 14:34:13 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 4 John W. Linville 2010-07-16 14:47:46 UTC
*** Bug 611816 has been marked as a duplicate of this bug. ***

Comment 5 John W. Linville 2010-07-16 17:45:41 UTC
This warning occurs when ieee80211_sta_timer executes with the following conditions:

local->quiescing == false
local->suspended == true
local->resuming == false

It isn't clear how this could happen, but it seems like a narrow window.  I wonder if this can be recreated?

Comment 6 Scott Dodson 2010-08-16 20:11:34 UTC
John,

I've not seen this again since I first reported it.

Comment 7 John W. Linville 2010-11-22 16:01:39 UTC
Closing on the basis of the last two comments -- please reopen if you see this again (especially if you can recreate it)!


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