Bug 4323 - fdomain Kernel Panic
fdomain Kernel Panic
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Cristian Gafton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-02 21:59 EDT by cmills
Modified: 2008-08-01 12:22 EDT (History)
0 users

See Also:
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: ---


Attachments (Terms of Use)

  None (edit)
Description cmills 1999-08-02 21:59:18 EDT
After installing Redhat on an IDE system, I added an
Adaptec AHA-2920a SCSI controller and a Connor 2.1Gb HD...
Now after running insmod fdomain and mounting the SCSI
Drive, I get a kernel panic as shown from the syslog below.

Aug  2 19:25:18 betaphi kernel: scsi0: <fdomain> No BIOS;
using scsi id 7
Aug  2 19:25:18 betaphi kernel: scsi0: <fdomain> TMC-36C70
(PCI bus) chip at 0xf780 irq 5
Aug  2 19:25:18 betaphi kernel: scsi0 : Future Domain 16-
bit SCSI Driver Version 5.50
Aug  2 19:25:18 betaphi kernel: scsi : 1 host.
Aug  2 19:25:18 betaphi kernel:   Vendor: CONNER    Model:
CFP2107E  2.14GB  Rev: 172A
Aug  2 19:25:18 betaphi kernel:   Type:   Direct-
Access                      ANSI SCSI revision: 02
Aug  2 19:25:18 betaphi kernel: Detected scsi disk sda at
scsi0, channel 0, id 0, lun 0
Aug  2 19:25:21 betaphi kernel: SCSI device sda: hdwr
sector= 512 bytes. Sectors= 4194304 [2048 MB] [2.0 GB]
Aug  2 19:25:21 betaphi kernel:  sda: sda1
__________________________________________

After a little time of use:


Aug  2 20:08:18 betaphi kernel: scsi : aborting command due
to timeout : pid 27407, scsi0, channel 0, id 0, lun 0 Write
(10) 00 00 2d 2f d1 00 00 80 00
Aug  2 20:08:18 betaphi kernel: scsi: <fdomain> abort
Aug  2 20:08:18 betaphi kernel: Future Domain 16-bit SCSI
Driver Version 5.50
Aug  2 20:08:18 betaphi kernel: scsi0: <fdomain> No BIOS;
using scsi id 7
Aug  2 20:08:18 betaphi kernel: scsi0: <fdomain> TMC-36C70
(PCI bus) chip at 0xf780 irq 5
Aug  2 20:08:18 betaphi kernel: other (8), target = 0 cmnd
= 0x2a pieces = 64 size = 65536
Aug  2 20:08:18 betaphi kernel: sent_command = 10,
have_data_in = -1, timeout = 0
Aug  2 20:08:18 betaphi kernel: in_interrupt_flag = 0
Aug  2 20:08:18 betaphi kernel: IMR = 0x10d8, IRR = 0x0000,
ISR = 0x0000
Aug  2 20:08:18 betaphi kernel: SCSI Status      = 0x11
Aug  2 20:08:18 betaphi kernel: TMC Status       = 0xf0
Aug  2 20:08:18 betaphi kernel: Interrupt Status = 0x98
(enabled)
Aug  2 20:08:18 betaphi kernel: FIFO Status      = 0x08
Aug  2 20:08:18 betaphi kernel: Int. Condition   = 0x00
Aug  2 20:08:18 betaphi kernel: Configuration 1  = 0x83
Aug  2 20:08:18 betaphi kernel: Configuration 2  = 0x03
Aug  2 20:08:33 betaphi kernel: scsi : aborting command due
to timeout : pid 27407, scsi0, channel 0, id 0, lun 0 Write
(10) 00 00 2d 2f d1 00 00 80 00
Aug  2 20:08:33 betaphi kernel: scsi: <fdomain> abort
Aug  2 20:08:33 betaphi kernel: Future Domain 16-bit SCSI
Driver Version 5.50
Aug  2 20:08:33 betaphi kernel: scsi0: <fdomain> No BIOS;
using scsi id 7
Aug  2 20:08:33 betaphi kernel: scsi0: <fdomain> TMC-36C70
(PCI bus) chip at 0xf780 irq 5
Aug  2 20:08:33 betaphi kernel: arbitration (2), target = 0
cmnd = 0x2a pieces = 64 size = 65536
Aug  2 20:08:33 betaphi kernel: sent_command = 0,
have_data_in = 0, timeout = 0
Aug  2 20:08:33 betaphi kernel: in_interrupt_flag = 0
Aug  2 20:08:33 betaphi kernel: IMR = 0x10d8, IRR = 0x0000,
ISR = 0x0000
Aug  2 20:08:33 betaphi kernel: SCSI Status      = 0x11
Aug  2 20:08:33 betaphi kernel: TMC Status       = 0x40
Aug  2 20:08:33 betaphi kernel: Interrupt Status = 0x28
(enabled)
Aug  2 20:08:33 betaphi kernel: FIFO Status      = 0x08
Aug  2 20:08:33 betaphi kernel: Int. Condition   = 0x00
Aug  2 20:08:33 betaphi kernel: Configuration 1  = 0x83
Aug  2 20:08:33 betaphi kernel: Configuration 2  = 0x03

Note You need to log in before you can comment on or make changes to this bug.