Bug 434836
Summary: | iwl4965: BUG: scheduling while atomic messages with possibly associated hangs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Douglas E. Warner <silfreed> |
Component: | kernel | Assignee: | John W. Linville <linville> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | kernel-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.6.24.3-34.fc8 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-03-17 19:07:14 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
Douglas E. Warner
2008-02-25 19:18:12 UTC
Also forgot to mention the broken load averages after the above errors: $ uptime 14:21:13 up 6:01, 6 users, load average: 686398.15, -908451.81, 369103.09 I'm not sure if my error matches exactly with that bug; I'm only associated with an 802.11g WAP, not 802.11b. Otherwise the error last reported by my iwl4965 is definitely in both bugs, but the circumstances aren't exactly the same. FYI, I tried to setup a serial console connection to get more output when this problems occurs and now my laptop has run for ~2 days without the errors showing up. I doubt it's resolved, but thought it might be a clue as to what might be going on. My grub line used to be: kernel /vmlinuz-2.6.23.15-137.fc8 ro root=/dev/VolGroup00/LogVol00 quiet And is now: kernel /vmlinuz-2.6.23.15-137.fc8 ro root=/dev/VolGroup00/LogVol00 console=ttyS0,115200 console=tty0 Can you replicate this with current F-8 kernels? http://koji.fedoraproject.org/koji/buildinfo?buildID=42735 I've been running the latest kernel all weekend with the default options (ie, w/o specifying console) and have not had any lockups or the error messages mentioned above. |