Bug 145549
Summary: | CONFIG_DEBUG_SPINLOCK option in kernel causes panic with modprobe ndiswrapper | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jonathan Berry <berryja> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | maurizio.antillon, pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-01-19 22:38:32 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
Jonathan Berry
2005-01-19 16:43:50 UTC
the purpose is so that buggy out of tree drivers get fixed. it might work with the option turned off, but the driver is doing something *bad* that could cause problems at any time. Complain to the ndiswrapper authors, as anything the DEBUG_SPINLOCK triggers is their bug. Thanks Dave. I mostly wanted to see if there was a reason for having this flag; I figured it couldn't hurt to ask :). I guess perhaps this is somewhat an artifact of the nature of Fedora, being a testing ground for the RHEL releases. Otherwise, I would think it to be better to just have this in testing kernels, not official releases. Can I ask what kind of things trigger the DEBUG_SPINLOCK and what this triggering should do? Seems like a hard freeze of the system isn't exactly the ideal reaction. I have told the ndiswrapper authors about the issue, but I'm not sure how much they can do. I think it may have to do with the Windows binary drivers that ndiswrapper wraps (which I realize is not your problem). So, if I have to recompile my kernel, I guess I won't mind too much :). it's not a fedora specific thing, it's enabled for RHEL too. Its so low overhead, and catches so many really dumb bugs, it doesn't make sense to not have it on. It'll trigger if a whole bunch of silly things happen, like trying to take a lock that hasn't been initialised, trying to take the same lock twice, etc It panics and does the hard freeze, because in many situations its too dangerous to continue. Locking up early is preferred, rather than silently corrupting data, and eventually crashing. |