Bug 66247
Summary: | Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Shaun Murphy <shaun.murphy> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.3 | CC: | herrold |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
URL: | http://www.unix-scripts.com/err.txt | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-06-07 23:19:42 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
Shaun Murphy
2002-06-06 19:07:52 UTC
That is an oops from 2.4.18-3smp. We know that this specific bug is possible in 2.4.18-3, and it is supposed to be fixed in 2.4.18-4. If it is still happening on 2.4.18-4smp, then there must be something different there from the original bug, and I really need an oops trace of the 2.4.18-4 crash to be able to debug it. In all other reported cases, 2.4.18-4 does fix this bug. i have both kernels still on the server. I left 2.4.18-3 on their just incase 2.4.18-4 didnt work and it was set to default. So sombody might have rebooted the machine and it would have booted on 2.4.18-3 then. I set 2.4.18-4 to default. Also why when you guys release kernel's do you not release a SMP kernel? We do, always. There is a 2.4.18-4smp kernel just as there was a 2.4.18-3smp kernel. The kernel from your original bug report was an smp kernel. n/m i'm just a idiot who doesnt look in the i686 dir :/ Thanks for your help guys and quick responce i will let you know if i see this error with 2.4.18-4. I'm really supprised with how fast you guys responded. I figured i was going to have to wait months for a reply. No problem --- it's always easier for us to respond to bugs that are already fixed, in any case. :-) I'll close this as fixed(ERRATA) for now, but please feel free to reopen it if you see the problem on 2.4.18-4smp. *** Bug 71562 has been marked as a duplicate of this bug. *** *** Bug 74245 has been marked as a duplicate of this bug. *** |