Bug 77398
Summary: | kernel panic when shutdown | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Borys Wojcik <it> | ||||
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 7.3 | CC: | jure.pecar | ||||
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:40:09 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
Borys Wojcik
2002-11-06 13:45:38 UTC
Created attachment 83846 [details]
Error Messages
ah the gdth driver: we fixed a shutdown oops recently, a kernel for testing this is available from: http://people.redhat.com/arjanv/testkernels/ I forgot it is very importent. The problem onla happends when using Multiprocessor Kernel. After boot with Singleprocessor Kernel everything is OK! I have downloaded kernel-smp-2.4.18-17.2.i686.rpm for testing, but during the installation there is a message that my kernel 2.4.18-17.7.xsmp is newer than that one I want to install. If the fix for this problem in the 2.4.18-7.2 kernel is just a single line change in scsi.c, can you port it to the redhatAS kernel? Through the AS support i couldn't get the patch (so much about the payable support). I kinda NEED the gdth driver working in the 2.4.9e.10 kernel. jure.pecar: please open a separate bug for that see bug #76240. 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/ |