Bug 879252
Summary: | iwlwifi: BUG: soft lockup - CPU#0 stuck for 22s! | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joel Uckelman <uckelman> |
Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | gansalmon, itamar, jonathan, jwalant.soneji, kernel-maint, madhu.chinakonda, matthias.scheutz, sgruszka |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:4db3c92bfa1062f22d5c7131bf654ed28f94d098 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-30 13:33:49 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
Joel Uckelman
2012-11-22 12:54:54 UTC
*** Bug 879251 has been marked as a duplicate of this bug. *** Please install and boot a kernel-debug and try to reproduce this problem. Debug kernel should print some more informative call trace messages, so when you will reproduce this problem, attach dmesg output here. I've been able to reproduce the problem once with a debug kernel after two days of running one, but I couldn't get any dmesg output from it. When this problem occurs with a normal kernel, the cores in my CPU get stuck at 100% usage (according to htop) one at a time over the course of a few minutes, which gives abrt enough chance to spot the problem with the kernel and collect output from dmesg. The debug kernel is way, way less responsive, so when (by all appearances) the same thing happened a few minutes ago, neither I nor abrt had a chance to get anything from dmesg---by the time I realized something was going on, the machine had locked up---and when I rebooted, there was nothing interesting in /var/log/messages. What to do? Hmm, that strange. Please run on debug-kernel for few hours and then dump dmesg and attach it here, perhaps there will be some massages, which indicate where the problem is. all of a sudden, i was trying to go to a web site on firefox, i go the kernel panic and then slowly but surely nothing else worked anymore (i could still move the mouse, but no more keyboard inputs and the windows were not responding either) Package: kernel OS Release: Fedora release 17 (Beefy Miracle) I'm still getting stuck CPUs with kernel 3.7.3-101.fc17.x86_64. Sometime in the next few days I'll try running a debug kernel again to see if I can produce some useful data. Please run it for some long period - let say a month. In most cases debug kernel should show problem quickly, but there are cases (what I realized currently) which need long time to reproduce also on debug kernel. *** Bug 904699 has been marked as a duplicate of this bug. *** I think I found where the problem is, not needed any further informations for now. This will be fixed on 3.9 which include commit: commit 2bfb50924c7e92362ac937aef2ab56bc7bd3ca52 Author: Johannes Berg <johannes.berg> Date: Thu Dec 27 21:43:48 2012 +0100 iwlwifi: use threaded interrupt handler Closing with rawhide resolution ... |