Bug 84202
| Summary: | 2.4.20-2.21BOOT kernel oopses in 3ware driver | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Jan Iven <jan.iven> | ||||||||
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 9 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i386 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2004-09-30 15:40:31 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: | 79579, 100644 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 90048 [details]
Install-time /tmp/syslog with 2 oopsen
Created attachment 90049 [details]
install-time /proc/ksyms
Created attachment 90050 [details]
Oops with symbols resolved
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |
Description of problem: The 2.4.20-2.21BOOT kernel "oopses" in 3ware driver, apparently when first accessing the harddisks ("checking for installed system" (or similar) in anaconda) Version-Release number of selected component (if applicable): 2.4.20-2.21BOOT How reproducible: always Steps to Reproduce: 1.HW: mirrored system disk on 3ware controller 2.interactive anaconda install (text or graphic) 3.enter installation method/network, choose mouse. Actual results: "the installation process terminated abnormally" on tty0, oops on tty3 Expected results: :-) Additional info: attached install-time syslog and ksymoops output (symbols from /proc/ksyms, run on different machine)