| Summary: | Kerneloops for Broadcom 802.11 STA driver | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | M Read <mstuff> |
| Component: | broadcom-wl | Assignee: | NVieville <nicolas.vieville> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P5 | ||
| Version: | 18 | ||
| Hardware: | All | ||
| OS: | GNU/Linux | ||
| namespace: | |||
|
Description
M Read
2013-08-29 09:53:29 CEST
Hello, Thanks for pointing this. It will be probably useful to check problems for this driver with this tool. Is there any particular "oops" in the list you wanted to highlight? I noticed that for the moment the problem produce warnings, which is annoying but not blocking. After checking the current patches applied on the rpmfusion packages, I don't see any difference that could explain these "oops" compared with other distributions that provide this driver. Help about this will be appreciated. Maybe other distributions are also affected by this problem. As a first path for investigation, I saw in wl_cfg80211.c file that every call to cfg80211_roamed function uses a NULL pointer as second argument but it should be a ieee80211_channel structure pointer. Maybe some verification are made in last kernels about this pointer and produce warnings when it is NULL. Some other wireless device drivers also call this function with a NULL pointer as the second parameter. Maybe they are affected as well. But it's only a guess. As my skill in analyzing kernel oops is not very high, I can not get, for the moment, any precise information from these oops reports that could tell me the exact location of the problem. Any help on this point would be also really appreciated. Feel free to make any comment about this. Cordially, -- NVieville Hi NVieville Happy to give any help I can, but I am really only a "user" (aren't we all?). So, as far as making sense of kernel oops messages, I think someone with more knowledge might be more use to you. Keep well. All seems sorted, thank you. M |