Bug 247975
Summary: | list_del corruption BUG. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Oleg Drokin <green> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | chris.brown |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-09-18 20:44:43 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
Oleg Drokin
2007-07-12 13:54:04 UTC
Hello Oleg, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. Cheers Chris I no longer see this problem, so it might be fixed, but might be not - read on. Originally I believed the problem was related to hald polling newly created devices. My initial workaround was to kill hald and the problem stopped. The device appears when remote console for ibm server is attached that brings a virtual cd drive with itself. I see that for quite some time I am running with hald enabled again and no crashes, but on the other hand for all that time nobody used the console software. This is my production machine so I am not very keen on trying to crash it, unfortunately. I understand that info provided is most probably not enough to find the culprit, but this is all I have. If you feel like it, you can probably close the bug. Rather than killing hald you can run this option: hal-disable-polling $DEVICE where $DEVICE is your cdrom drive, e.g. /dev/scd0 Anyway, thanks for initially filing the bug, sorry it took a while to get reviewed and I will close as WORKSFORME. Please re-open if you feel this still needs looking into at any point. Cheers Chris |