Bug 738387
| Summary: | ipw2200 driver deadlocks with itself trying to take rtnl_mutex | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mads Kiilerich <mads> | ||||||||||
| Component: | kernel | Assignee: | Josh Boyer <jwboyer> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 16 | CC: | awilliam, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, orion, sgruszka, tflink, wwoods | ||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | AcceptedBlocker | ||||||||||||
| Fixed In Version: | kernel-3.1.0-0.rc6.git0.3.fc16 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-09-24 04:37:25 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: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 713564 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Mads Kiilerich
2011-09-14 17:06:23 UTC
Created attachment 523203 [details]
dmesg from successful boot with kernel-PAE-3.1.0-0.rc4.git0.1.fc16.i686
Can you try 3.1-rc6? There were a handful of PCI fixes that went into that release. I see the same problem with rc5 and rc6. Actually the photo might be from rc6 ... and it is possible that most of the successes has been with rc5. Created attachment 523255 [details]
pci ipw lock
I caught a lock stracktrace with rc5.
(In reply to comment #4) > I caught a lock stracktrace with rc5. It does look like ipw2200 has a serious problem there. I assume blacklisting that lets the system boot normally? (In reply to comment #5) > It does look like ipw2200 has a serious problem there. I assume blacklisting > that lets the system boot normally? Confirmed. Manual "modprobe ipw2200" after boot will hang and bring down the wired network too. Me too. ThinkPad X32. Zoiks! John, Stanislaw, is this the fix for this issue? http://www.spinics.net/lists/linux-wireless/msg76673.html I've started a scratch build with the patch from comment #9. For those of you hitting this issue, could you please test when this completes and let us know if it resolves the problem? http://koji.fedoraproject.org/koji/taskinfo?taskID=3354471 I also did a build, if you're really impatient, it's available now: http://adamwill.fedorapeople.org/kernel-3.1.0-0.rc6.git0.2.1.fc16.x86_64.rpm oh, damn, 32-bit might have been a better idea. (In reply to comment #9) > John, Stanislaw, is this the fix for this issue? > > http://www.spinics.net/lists/linux-wireless/msg76673.html Yes. I've built a 32-bit live image with josh's kernel in it, to aid testing. It's uploading now to: http://adamwill.fedorapeople.org/desktop-20110914-i686.iso (ignore the dumb name :>) it should be up in about 30 mins. sha256sum is d1c58cac71e69ddbe1f50f6ebfdc25ba64dcfd078db0fde920a0aba0e34d06c3 . Created attachment 523524 [details]
working 3.1.0-0.rc6.git0.2.1.fc16.i686.PAE dmesg
I confirm that 3.1.0-0.rc6.git0.2.1 from koji can boot and the wireless seems to work.
(In reply to comment #15) > Created attachment 523524 [details] > working 3.1.0-0.rc6.git0.2.1.fc16.i686.PAE dmesg > > I confirm that 3.1.0-0.rc6.git0.2.1 from koji can boot and the wireless seems > to work. Excellent. I'll commit this today. kernel-3.1.0-0.rc6.git0.3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/kernel-3.1.0-0.rc6.git0.3.fc16 Discussed in the 2011-09-16 blocker review meeting. Even though this bug is HW specific, that hardware is common enough and this bug is serious enough to accept it as a Fedora 16 beta blocker as it violates the following alpha release criterion [1]: The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops [1] https://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria Package kernel-3.1.0-0.rc6.git0.3.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.1.0-0.rc6.git0.3.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/kernel-3.1.0-0.rc6.git0.3.fc16 then log in and leave karma (feedback). Mads, can you re-confirm this is fixed in git0.3? thanks! Yes, git0.3 is fine - I gave it karma in bodhi. great, setting VERIFIED then. Please don't close bugs until they are actually pushed stable when we're frozen, Dave - otherwise they risk not being pulled into future Beta composes; we don't have closed bugs on the list when listing out updates which need to be pulled into the compose that are not yet in stable. kernel-3.1.0-0.rc6.git0.3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |