Bug 843551
| Summary: | [iwl3945]: WARNING: _il_grab_nic_access | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | winnen209 |
| Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | bugs, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, winnen209 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | abrt_hash:3a1599ce18283860da3b7299860e831504444a09 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-14 14:06:05 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
winnen209
2012-07-26 15:12:18 UTC
What you do when this warning happen (suspend from resume, boot machine or something else)? It is reproducible or happen accidentally and never repeat again? (In reply to comment #1) > What you do when this warning happen (suspend from resume, boot machine or > something else)? It is reproducible or happen accidentally and never repeat > again? The bug is highly reproducible, and has been going on for some time. It occurs about 50% of the time from the following steps. The warning is generated as follows: 1. Boot system*, load Desktop Environment (Gnome 3 is the current case, it has happened in others as well) 2. Check that wireless is connecting and internet works, confirm it does. 3. Suspend system from the DE menu. (Any method of suspending should generate the same warning/error) 4. Resume system. <----- This is when the warning is issued. 5. Check wireless status, see that it is not detecting the wireless card. Upon the warning being issued, the system no longer recognizes the wireless card, and no action short of rebooting seems to redetect the card. I have tried modprobe, restarting NetworkManager, turning the hardware switch off and then on again, and several other potential solutions without results. *NOTE: Even upon booting, the system occasionally will not load the wireless card drivers, but this happens much less often than suspend/resume. When the error occurs, the system does not recognize wireless at all. Gnome's NetworkManager plugin will list wireless as an option upon resume, but will not list a card or any networks. I believe the issue is a kernel/driver issue, rather than a NetworkManager issue, but I admit I do not know enough to confirm that. So issue happens after resume from suspend to RAM. "CSR_GP_CNTRL 0xffffffff" mean that we can not talk to with device through PCIe bus, iow this is PCI driver or hardware bug. We have few similar issues reported: http://marc.info/?t=133148795500004&r=1&w=2 https://bugzilla.kernel.org/show_bug.cgi?id=42658 http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2143 Are you using compiz or similar? If so does disabling it help. If not, does workaround from http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2143#c44 help? *** Bug 857536 has been marked as a duplicate of this bug. *** Are you using compiz or similar? If so does disabling it help. If not, does workaround from http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2143#c44 help? For (In reply to comment #5) > Are you using compiz or similar? If so does disabling it help. If not, does > workaround from > http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2143#c44 > help? I am not using Compiz with the system's Gnome 3. This workaround works for me. I made a small script to run any time the issue comes up and it fixes it every time. Thank you. Still, it is troublesome that it is necessary to do so. Can you still reproduce it on 3.5 ? F-16 did not update to 3.5 but you might try to download below F-17 kernel and try to boot it and test if issue is still present. http://koji.fedoraproject.org/koji/buildinfo?buildID=357945 # Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient). This PCI bug appears to have been resolved with the new kernel. I cannot replicate it on kernel 3.6.2-1.fc16. |