Bug 4670
Summary: | Kernel Panic at install | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | chuck |
Component: | kernel | Assignee: | Cristian Gafton <gafton> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | CC: | chuck, dracon |
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: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
chuck
1999-08-23 17:40:58 UTC
I have a quantum drive connected to a Adaptec 2920, and the same error comes up. It seems to occur when the drive is under heavy usage. For me, it was a 200KB/s download that killed it. Strange thing though is that it only crashes after I have downloaded about 50 megs, and then I get a bus reset time out. Then the sync message comes up and crashes. Here is the actual panic transcribed from the dead machines monitor: TMC Status = 0x40 (interrupt) Interrupt Status = 0x28 (enabled) FIFO Status = 0x08 Int. Condition = 0x00 Configuration 1 = 0x85 Configuration 2 = 0x03 scsi : aborting command due to timeout : pid 3351, scsi0, channel 0, id 6, lun 0 Write (10) 00 00 39 f9 1b 00 00 00 00 scsi: <fdomain> abort Future Domain 16-bit SCSI Driver Version 5.50 scsi0: <fdomain> No BIOS; using SCSI id 7 scsi0: <fdomain> TMC-36C70 (PCI bus) chip at 0x6100 irq 10 arbitration (2), target = 6 cmnd = 0x2a pieces = 64 size = 65536 sent_command = 0, have_data_in = 0, timeout = 0 in_interrupt_flag = 0 IMR = 0x5a68, IRR = 0x0000, ISR = 0x0000 SCSI Status = 0x11 TMC Status = 0x40 (interrupt) Interrupt Status = 0x28 (enabled) FIFO Status = 0x08 Int. Condition = 0x00 Configuration 1 = 0x85 Configuration 2 = 0x03 scsi0 channel 0 : resetting for second half of retries SCSI bus is being reset for host 0 channel 0 scsi: <fdomain> SCSI Bus Reset Future Domain 16-bit SCSI Driver Version 5.50 scsi0: <fdomain> No BIOS; using SCSI id 7 scsi0: <fdomain> TMC-36C70 (PCI bus) chip at 0x6100 irq 10 unknown (34), target = 6 cmnd = 0x2a pieces = 64 size = 65536 sent_command = 0, have_data_in = 0, timeout = 0 in_interrupt_flag = 0 IMR = 0x5a68, IRR = 0x0000, ISR = 0x0000 SCSI Status = 0x11 TMC Status = 0x40 (interrupt) Interrupt Status = 0x00 (enabled) FIFO Status = 0x08 Int. Condition = 0x00 Configuration 1 = 0x85 Configuration 2 = 0x03 scsi0 channel 0 : resetting for second half of retries SCSI bus is being reset for host 0 channel 0 scsi: <fdomain> SCSI Bus Reset Future Domain 16-bit SCSI Driver Version 5.50 scsi0: <fdomain> No BIOS; using SCSI id 7 scsi0: <fdomain> TMC-36C70 (PCI bus) chip at 0x6100 irq 10 unknown (34), target = 6 cmnd = 0x2a pieces = 64 size = 65536 sent_command = 0, have_data_in = 0, timeout = 0 in_interrupt_flag = 0 IMR = 0x5a68, IRR = 0x0000, ISR = 0x0000 SCSI Status = 0x11 TMC Status = 0x40 (interrupt) Interrupt Status = 0x00 (enabled) FIFO Status = 0x08 Int. Condition = 0x00 Configuration 1 = 0x85 Configuration 2 = 0x03 Kernel Panic: scsi: <fdomain> fdomain_16x0_queue() NOT REENTRANT! In swapper task - not syncing Also... Alan Cox suggested I set the can_queue line in fdomain.h to 0 instead of 1 and then recompile the kernel. I did that but it hangs here: Loading fdomain module scsi0: <fdomain> No Bios; using scsi id 7 scsi0: <fdomain> TMC-36C70 (PCI bus) chip at 0x6100 irq 10 scsi0: Future Domain 16-bit SCSI Driver Version 5.50 scsi : 1 host. and it hung right there so I backed up to the kernel provided by RH with the 2.2.5-22 rpm (i586 version). HtH and thanx a lot! |