Bug 149850
Summary: | attempt to access beyond end of device | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Robert Vojta <robert> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | davej, wtogami |
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: | 2005-09-05 14:20:10 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
Robert Vojta
2005-02-28 10:41:17 UTC
There's nothing to go on here. You appear to have bad data on the disk; fsck logs would be useful. But unless it's reproducible, or you have additional kernel logs, we can't tell if it's a hardware fault --- disk, cables, CPU or memory; or a device driver, VM or filesystem problem. memtest86 and a decent filesystem stresser such as "dt" would be good places to start if you want to give the hardware a proper shakedown. My laptop went through these stress tests before I installed FC, all my computers are treated in this way. I'll try to reproduce this tomorrow. If there will be no success, I'll close this bug. An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. Closing as NOTABUG since there's still no indication whether this is hardware or software as a root cause, and there has been no followup. Please reopen if you can reproduce this with more information against a current kernel. |