Bug 161101
Summary: | Assertion failure in journal_commit_transaction() at fs/jbd/commit.c:790: "jh->b_next_transaction == ((void *)0)" | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Jeff Burke <jburke> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | anderson, davej, jbacik, jbaron |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHSA-2006-0132 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-03-07 19:09:33 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: | 164439, 168429 |
Description
Jeff Burke
2005-06-20 15:48:51 UTC
I'm looking into this a bit deeper now. Is this still reproducible on current kernels? Have you seen any further oopses like it? When you say "intermittent", just how hard is it to reproduce? How long does it take, what sort of system are you reproducing it on, and do any systems seem not to show the problem? Some additional questions: Have previous kernels been subjected to the same level of testing as recent ones, ie. are we _sure_ this started appearing recently? (I know for a fact that earlier pre-U2-beta kernels had a bug which would show up in just the same way, so I would be really surprised if they passed similar loads reliably.) How repeatable is it? You mention at least 2 kernels showing it, but there's only one oops here --- do you have a vmcore from a mainline build? An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0132.html |