Red Hat Bugzilla – Bug 37533
(SCSI TMSCIM)GNU Parted causes an oops when used with tmscsim. This makes installer to cash when selecting partitioning type as well.
Last modified: 2008-08-01 12:22:51 EDT
The furthest I got for text, nofb, lowres was this:
going to insmod ext3.o
looking for USB mouse
no IDE floppy device found
raid5: using funct
raid5: personality registred as nr 4
I could complete the install using expert where it added the following
lines for VC3 when I got to select packages instead of the crash.
Detected 128 of memory
Swap attempt of 128 to 256
Maximum cylinder is 198
For text I got this Ooops.
eax: 00000000 ebx: c12ea0f4 ecx: 00000081 edx: 000be40c
esi: c7f1fa10 edi: 00000080 ebp: c12ea078 esp: c0241f14f2
ds: 0018 es: 0018 ss: 0018
Process swapper (pid:0, stackpage=c0241000)
Stack c0241f47 c12ea0f4 c12ea078 00000081 c88294d6 c12ea078 c12ea0f4
c12ea078 c12ea0f4 c0241f47 00000282 912711c0 00000246 00000000 c025f550
00000000 c7f1ea80 04000001 0000000b c0241fac c010a019 0000000b
Call Trace [<c88294d6>] [<c010a019>] [<c010a168>] [<c12ea078>] [<c0107210>]
[<c0108f58>] [<c0107210>] [<c0107233>] [<c010729a>] [<c0105000>]
Code: 80 60 27 fe 85 f6 0f 84 9f 00 00 00 80 4e 27 02 e9 96 00 00
Kernel Panic: Aiee, killing interrupt handler
In interrupt handler - not syncing
Let me know if there is something wrong with the oops since I can
reproduce it pretty easy.
I previously had a RH7 installation w/ ~50 swap, 128 ram
This is a kernel problem. Changing component to the kernel.
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
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
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++
I tried to disconnect Quantum drive + delete all previous Linux partitions but
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
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. ***
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
program that make tmscsim oops. Basically,
cmd = 0x12; /* INQUIRY */
cmd = 0x00; /* lun=0, evpd=0 */
cmd = 0x00; /* page code = 0 */
cmd = 0x00; /* (reserved) */
cmd = 96; /* allocation length */
cmd = 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
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/