Bug 52640
| Summary: | ide device names change(disappear?) after upgrade to kernel 2.4.3-12 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Don Himelrick <astrodon> | ||||
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.1 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2004-09-30 15:39:08 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: | |||||||
| Attachments: |
|
||||||
|
Description
Don Himelrick
2001-08-27 15:57:31 UTC
Created attachment 29815 [details]
boot messages from working kernel 2.4.2-2 and lilo.conf
*** See attachment *** Is the way the new kernel ide drivers handle disk geometry different? It seems with the lilo append line I'm using for the new kernel, with the geometry that is reported by the working old kernel, that everything "works" except for hdg. The new kernel reports that hdg has a bad superblock, has a read error, etc., and then panics. -If I probe hdg, the kernel panics with no device driver for hdg. -If I don't probe, the same. -If I don't probe AND specify geometry, the kernel finds the device and gives a read error. If someone could tell me how to capture dmesg from a bombed (at boot) kernel, I sure would be happpy :) 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/ |