Bug 511128 (iwlagn-crashes)
| Summary: | iwlagn crashes on large file transfers (over 100MB) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Turgut Kalfaoglu <turgut> | ||||
| Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 11 | CC: | gjunk, itamar, kernel-maint, madko, reinette.chatre | ||||
| 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: | 2010-01-18 09:42:18 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
Turgut Kalfaoglu
2009-07-13 19:42:20 UTC
I am seeing similar crash - seems to happen every time I run backups - ie sustained large network load. kernel 2.6.29.6-213.fc11.x86_64 I do see a series of errors in /var/log/messages of the form: iwlagn: No space for Tx iwlagnL Error sending REPLY_TX_LINK_QUALITY_CMD: enqueue_hcmd failed: -28 Also the attached driver errors looking very similar to above. Created attachment 355337 [details]
kernel errors
Attached kernel messages about iwlagn crash.
I'm sure Matthias is sick to death of people assigning bugs to iwlwifi-firmware that clearly belong to the kernel... (In reply to comment #3) > I'm sure Matthias is sick to death of people assigning bugs to iwlwifi-firmware > that clearly belong to the kernel... It's usually only a couple each month. I'm sure the kernel maintainers are the ones suffering most in the end ;-) Thanks for reassigning. *** This bug has been marked as a duplicate of bug 493018 *** |