Bug 213016

Summary:	bcm43xx: lots of suppressed printk log messages from kernel
Product:	[Fedora] Fedora	Reporter:	Alex Kanavin <ak>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6	CC:	jonstanley, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-08 00:27:07 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:

Description Alex Kanavin 2006-10-30 16:10:20 UTC

I'm using FC6 on a Powerbook 12" (bcm43xx driver) with a Motorola SBG900E access
point/cable modem. When the interface is up, /var/log/messages is filled with

Oct 27 00:50:15 cs78142018 kernel: printk: 183 messages suppressed.
Oct 27 00:50:15 cs78142018 kernel: printk: 409 messages suppressed.

It only appears when I configure the Motorola to use WPA AES, but if
it uses WPA TKIP, everything is fine. Running wpa_supplicant directly
from the console with -d option does not produce anything unusual.

How can I investigate this further?

Comment 1 Jon Stanley 2007-12-31 06:46:48 UTC

Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!

Comment 2 Jon Stanley 2008-01-08 00:27:07 UTC

Closing per previous comment.  If you can provide the requested information,
please feel free to re-open this bug.