Bug 860399
Summary: | RHEL6.3: Oops in rpciod, RIP rpcauth_refreshcred | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Kelsey Cummings <kgc> |
Component: | kernel | Assignee: | Jeff Layton <jlayton> |
Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3 | CC: | dwysocha, jlayton, nfs-maint, steved |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-04 20:34:25 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kelsey Cummings
2012-09-25 18:10:34 UTC
Would it be possible for you to open a support case with RH support and supply them with the core for analysis? (pasting from what was sent via email)
> > Would it be possible for you to open a support case with RH support and supply
> > them with the core for analysis?
>
> No, but I'd be happy to supply you with the two crash dumps and/or
> perform any analysis for you locally. New support policies make
> community reported bugs more chalenging, eh?
>
Yep, if you don't have a support contract then you'll need to do some
legwork on your own.
You'll want to track down the place where it crashed and see if you can determine why. Most likely, there's a corrupt pointer someplace that we ended up trying to chase. See if you can determine what was corrupt and the nature of that corruption...
It's likely that this bug is a duplicate of bug 878204. Unfortunately, that bug is marked private and I can't add you to the cc list. You may want to try pulling in commit a271c5a0de from upstream kernels and see if that fixes the issue for you. If it does, please note it here and I'll close this bug as a duplicate of that one. I'm going to go ahead and close this bug as a dup of that one. If you find that that commit doesn't help, then please reopen this bug and I'll try to take another look. *** This bug has been marked as a duplicate of bug 878204 *** |