Bug 17166

Summary:	Kernel - wl bcm call traces
Product:	Mageia	Reporter:	Mauricio Andrés Bustamante Viveros <neoser10>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal	CC:	lists.jjorge
Version:	5
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	kernel, broadcom-wl?	CVE:
Status comment:
Attachments:	Full Journal

Description Mauricio Andrés Bustamante Viveros 2015-11-18 03:55:52 CET

Description of problem:
I am getting call traces for 802.11 kernel module in a laptop Latitude E6420, and when I switch to tty, sometimes get errors about the power transmit

Version-Release number of selected component (if applicable):
Default and Core Updates kernels

How reproducible:
Every boot process

Steps to Reproduce:
1. Power on the computer and select any kernel

Reproducible: 

Steps to Reproduce:

Comment 1 Mauricio Andrés Bustamante Viveros 2015-11-18 03:58:29 CET

Created attachment 7208 [details]
Full Journal

Comment 2 Mauricio Andrés Bustamante Viveros 2015-11-18 03:59:52 CET

Seconds after fill this bug, mga updates is shown, and i see a broadcom-wl-common update......

Comment 3 Samuel Verschelde 2015-12-07 13:38:10 CET

(In reply to Mauricio Andrés Bustamante Viveros from comment #2)
> Seconds after fill this bug, mga updates is shown, and i see a
> broadcom-wl-common update......

Did it solve your issue?

Comment 4 Mauricio Andrés Bustamante Viveros 2015-12-08 16:09:22 CET

With the 4.X.X kernel, I see the call traces, I will install the core updates kernel and report

Comment 5 Mauricio Andrés Bustamante Viveros 2015-12-08 16:59:41 CET

Again with 4.1.13 server kernel is the call trace, referring to sme.c module

Samuel Verschelde 2015-12-08 17:37:58 CET

CC: (none) => lists.jjorge
Assignee: bugsquad => tmb
Source RPM: (none) => kernel, broadcom-wl?

Comment 6 José Jorge 2015-12-08 18:43:53 CET

This is an upstream bug, I also see it it here. The real bug is the driver was not updated upstream to follow kernel interface changes.

Like other broadcom bugs, either you switch to open-source driver, or you wait for an upstream fix. Please reopen if you see a better way to do.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX