Bug 37533
Summary: | (SCSI TMSCIM)GNU Parted causes an oops when used with tmscsim. This makes installer to cash when selecting partitioning type as well. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Per Winkvist <per.winkvist> | ||||
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 7.2 | ||||||
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:38:58 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
Per Winkvist
2001-04-25 07:18:42 UTC
This is a kernel problem. Changing component to the kernel. Hi Arjan, I got the same problems with 7.2, though this time I can not even complete the install with the expert option. I got a kernel panic (in text mode) this time to. It looks exactly the same as the previous one for 7.1 that I got. Do you want me to attach it ? or file a new bug ? I'm willing to try things since I really, really would like to get Linux up and running ASAP! This is the only time I'm not been able to install RH since 4.1 :( Any ideas on what sort of hardware this is ? Abit BH-6 w/ Celeron 300A (* see below for further info) Tekram DC-390 SCSI controller (I believe it is using the ncr53c8xx or AMxxCxxx driver) (PCI) 1 Quantum Empire 1G SCSI 2 disk, 1 seagate 4.3 gb disk ATI Mach64 video connected to AGP SoundBlaster AWE32 (isa) I have never gotten an oops before while running the system, gcc and g++ performs reliable I tried to disconnect Quantum drive + delete all previous Linux partitions but nothing changed. (*) Chipset Intel 440BX Memory Slots 3 168pin DIMM Slots (EDO/SDRAM) Expansion Slots 1 AGP Slot 5 PCI Slots 2 ISA Slots (1 Shared / 2 Full Length) BIOS Award BIOS In 7.1 it oopsed after I selected type of install (as summary sais). But for 7.2 it oopses 0.000001 seconds after I select fdisk or diskdruid. I have identified the cause! When I replaced the tmscsim module that the installer auto probed for me with the AM53C974 module the installer didn't oops when I selected partitioning method. The /tmp/syslog had almost the same entries for both modules. The only differance is that for tmscsim it said something like "Tekram DC390/AM53" at the top while for the other module it said AM53C974. Both modules found the disks and tmscsim even showed the 10Mb/s transfer rate. So this must be a bug in the tmscsim driver right ? I'll try to see what happens after the install is completed... After installing 7.2 I can successfully run it with the tmscsim module (which oopsed during the installation after selecting partitioning type). So what is the installer doing that is flawed !?, Where can I find the source for the installation disk ? *** Bug 56546 has been marked as a duplicate of this bug. *** *** Bug 56546 has been marked as a duplicate of this bug. *** Created attachment 38423 [details]
Program that causes tmscsim to oops
I have now found out that it is parted that causes the oops. I have attached a program that make tmscsim oops. Basically, cmd[0] = 0x12; /* INQUIRY */ cmd[1] = 0x00; /* lun=0, evpd=0 */ cmd[2] = 0x00; /* page code = 0 */ cmd[3] = 0x00; /* (reserved) */ cmd[4] = 96; /* allocation length */ cmd[5] = 0x00; /* control */ 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/ |