Bug 524616
Summary: | _uid_ses keyring being cleaned up twice. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Casey Dahlin <cdahlin> |
Component: | kernel | Assignee: | Dave Anderson <anderson> |
Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.0 | CC: | dhowells, jwest, tao, vanhoof |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-02-08 22:17:28 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: | |||
Bug Depends On: | |||
Bug Blocks: | 499522, 533192 |
Description
Casey Dahlin
2009-09-21 13:51:33 UTC
Have there been panics like this in the past? What's a good technique for finding the culprit in this case? I've tried systemtap but you can't guarantee the integrity of a disk log after a panic, and getting the stap logs out of a core file has proved ugly. Is there a vmlinux/vmcore pair that I can look at? |