Bug 885294
Summary: | [abrt]: WARNING: at drivers/net/wireless/iwlegacy/4965-mac.c:2693 il4965_hdl_tx+0xd3f/0xd80 [iwl4965]() | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Karolina <karolina.sarna> | ||||
Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 17 | CC: | chmelarz, gansalmon, itamar, jlbouras, jonathan, kernel-maint, madhu.chinakonda, sgruszka, smbugzilla | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:7d2251bbd2bda90d2867d651afb84fc8474d8425 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-03-28 17:12:48 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: | |||||||
Attachments: |
|
Description
Karolina
2012-12-08 11:11:04 UTC
I would like to see what happen before this warning. Please attach full dmesg (which include this warning). You can find it in .cache/abrt/spool/oops-{DATE}/ or in /var/spool/abrt/oops-{DATE}/ . Is this problem reproducible for you or happened at random ? Created attachment 664086 [details]
dmesg file
There are several 4965 firmware hangs (real problem here) before the warning, what manifest in dmesg by messages like: [ 1412.824032] iwl4965 0000:06:00.0: Queue 2 stuck for 2004 ms. [ 1412.824044] iwl4965 0000:06:00.0: On demand firmware reload [ 1412.825010] iwl4965 0000:06:00.0: Timeout stopping DMA channel 1 [0x07fd0003] First firmware hang happen after about 20 minutes of usage. Does this happen on every system boot, i.e. if you look to dmesg do you see those "Queue X stuck" messages? If so, I'll ask you to provide logs with verbose debug messages (instructions letter). If not, I do not really see possibility to fix this, but perhaps there is workaround - use some of iwl4965 module options: fw_restart, 11n_disable, swcrypto; or kernel option: nohz=off. *** Bug 902634 has been marked as a duplicate of this bug. *** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |