Bug 804449
Summary: | [abrt] kernel: WARNING: at /builddir/build/BUILD/kernel-3.1.fc16/compat-wireless-3.2-1/drivers/net/wireless/p54/main.c:351 p54_config+0x215/0x250 [p54common]() | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ramón Mayo <barrymoabdib> |
Component: | kernel | Assignee: | John W. Linville <linville> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | gansalmon, gurligebis, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:5c9cc07747be8ab16a7b0b20b1df2eeed8b431f3 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-11-14 15:07:39 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
Ramón Mayo
2012-03-18 21:08:40 UTC
Are you getting a lot of these? Or just this one? I'm not sure how important this is, if we really need a warning. OTOH, if it happens a lot then it is surely a problem. Only sometimes, so i dont know how to reproduce it. Pluging again the usb wireless card didnt trigger it again. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. This night I got 5 of this warnings with the 3.3.0-4.fc16.x86_64 kernel again. I'm having the exact same problem on Gentoo with a vanilla kernel, so it's not Redhat specific. I found out, that v3.1 is good, and v3.2-rc1 is bad, so I bisected it, and got this bisect log: git bisect start # good: [c3b92c8787367a8bb53d57d9789b558f1295cc96] Linux 3.1 git bisect good c3b92c8787367a8bb53d57d9789b558f1295cc96 # bad: [1ea6b8f48918282bdca0b32a34095504ee65bab5] Linux 3.2-rc1 git bisect bad 1ea6b8f48918282bdca0b32a34095504ee65bab5 # bad: [37be944a0270402f9cda291a930b0286f6dc92f5] Merge branch 'drm-core-next' of git://people.freedesktop.org/~airlied/linux git bisect bad 37be944a0270402f9cda291a930b0286f6dc92f5 # good: [7e0bb71e75020348bee523720a0c2f04cc72f540] Merge branch 'pm-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm git bisect good 7e0bb71e75020348bee523720a0c2f04cc72f540 # good: [46a971913611a23478283931460a95be962ce329] Staging: hv: move hyperv code out of staging directory git bisect good 46a971913611a23478283931460a95be962ce329 # bad: [8a4a8918ed6e4a361f4df19f199bbc2d0a89a46c] Merge branch 'sched-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip git bisect bad 8a4a8918ed6e4a361f4df19f199bbc2d0a89a46c # good: [aa77677e0a288e08073620db5d2a31df83ca4788] Merge branch 'staging-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging git bisect good aa77677e0a288e08073620db5d2a31df83ca4788 # good: [c752d04066a36ae30b29795f3fa3f536292c1f8c] perf symbols: Increase symbol KSYM_NAME_LEN size git bisect good c752d04066a36ae30b29795f3fa3f536292c1f8c # bad: [19b4a8d520a6e0176dd52aaa429261ad4fcaa545] Merge branch 'core-rcu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip git bisect bad 19b4a8d520a6e0176dd52aaa429261ad4fcaa545 # good: [048b718029033af117870d3da47da12995be14a3] Merge branch 'rcu/next' of git://github.com/paulmckrcu/linux into core/rcu git bisect good 048b718029033af117870d3da47da12995be14a3 # good: [96f8e98bfeba3efa82eca85343bc058f6eced888] locking, x86, iommu: Annotate irq_2_ir_lock as raw git bisect good 96f8e98bfeba3efa82eca85343bc058f6eced888 # good: [c020570138f5d9cb1fc0a853f9cf9e641178b5c5] x86, ioapic: Consolidate the explicit EOI code git bisect good c020570138f5d9cb1fc0a853f9cf9e641178b5c5 # good: [68cc3990a545dc0da221b4844dd8b9c06623a6c5] rtmutex: Add missing rcu_read_unlock() in debug_rt_mutex_print_deadlock() git bisect good 68cc3990a545dc0da221b4844dd8b9c06623a6c5 # good: [08613e4626c06ca408fc55071f6aedee36986a87] caif: Fix BUG() with network namespaces git bisect good 08613e4626c06ca408fc55071f6aedee36986a87 # good: [982653009b883ef1529089e3e6f1ae2fee41cbe2] Merge branch 'core-iommu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip git bisect good 982653009b883ef1529089e3e6f1ae2fee41cbe2 # good: [3cfef9524677a4ecb392d6fbffe6ebce6302f1d4] Merge branch 'core-locking-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip git bisect good 3cfef9524677a4ecb392d6fbffe6ebce6302f1d4 Which results in this: 19b4a8d520a6e0176dd52aaa429261ad4fcaa545 is the first bad commit That commit seems to be a merge commit, so I'm unable to spot what it is in that commit that breaks things badly: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=19b4a8d520a6e0176dd52aaa429261ad4fcaa545 Any ideas would be welcomed. Does disabling CONFIG_PREEMPT also fix it for you? It fixes it on my system. # Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient). With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report. |