Linux-kernel mailing list archive 1999-34,: Re: NCR53C8XX fix for 2.3.14-pre2

# Re: NCR53C8XX fix for 2.3.14-pre2

Geert Uytterhoeven (Geert.Uytterhoeven@cs.kuleuven.ac.be)
Wed, 25 Aug 1999 22:02:18 +0200 (CEST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Peter Enderborg: "Re: Device deadlock."
- Previous message: Geert Uytterhoeven: "Re: NCR53C8XX fix for 2.3.14-pre2"

On Wed, 18 Aug 1999, Gerard Roudier wrote:
> I just checked the sym/ncr drivers of 2.3.14-pre2. The ncr53c8xx driver
> changes for the new resource stuff are not ok, but the sym53c8xx driver
> seems fine.
>
> Below is the fix for the ncr53c8xx driver. Basically, it fixes the BAR
> reading, particularly for the 896 which uses 64 bit BARs and removes
> the paranoid testing of other BAR flags (which are hardwired for all
> 53c8xx chips in fact, and the driver should never have cared about).
>
> I have tested a bit the both drivers using a 896 (64bit + on-chip RAM),
> 895 (32bit + on-chip RAM) and a 810a (32bit, no RAM) and all seem to work
> fine now.

Thansk! This patch indeed fixes the problem where both sym53c8xx and ncr53c8xx
wanted to play with the same SCSI adapter.

However, now a different problem showed up (with vger-August 24/2.3.15-preXX
on PPC):

| sym53c8xx: at PCI bus 0, device 6, function 0
| sym53c8xx: setting PCI_COMMAND_IO PCI_COMMAND_MEMORY...
| sym53c8xx: setting PCI_COMMAND_MASTER PCI_COMMAND_PARITY...(fix-up)
| sym53c8xx: 53c875 detected
| sym53c875-0: rev=0x04, base=0xc3000000, io_port=0x1400, irq=31
| sym53c875-0: NCR clock is 40218KHz, 40218KHz
| sym53c875-0: ID 7, Fast-20, Parity Checking
| sym53c875-0: on-chip RAM at 0xc3001000
| sym53c875-0: restart (scsi reset).
| sym53c875-0: Downloading SCSI SCRIPTS.
| ncr53c8xx: at PCI bus 0, device 6, function 0
| ncr53c8xx: IO region 0x1400 to 0x147f is in use
| mesh: assuming 50MHz clock frequency
| scsi0 : sym53c8xx - version 1.3c
| scsi1 : MESH
| scsi : 2 hosts.
| scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00
| sym53c8xx_abort: pid=0 serial_number=1 serial_number_at_timeout=1

And then the system hangs in a wait loop...

My devices (from 2.3.6 dmesg):

| Vendor: QUANTUM Model: VIKING II 4.5WLS Rev: 3506
| Type: Direct-Access ANSI SCSI revision: 02
| Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
| Vendor: PLEXTOR Model: CD-ROM PX-12TS Rev: 1.02
| Type: CD-ROM ANSI SCSI revision: 02
| Vendor: HP Model: HP35480A Rev: T503
| Type: Sequential-Access ANSI SCSI revision: 02
| sym53c875-0-<0,0>: tagged command queue depth set to 8
| Vendor: QUANTUM Model: FIREBALL_TM3200S Rev: 300X
| Type: Direct-Access ANSI SCSI revision: 02
| Detected scsi disk sdb at scsi1, channel 0, id 5, lun 0
| scsi : detected 2 SCSI disks total.
| sym53c875-0-<0,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
| SCSI device sda: hdwr sector= 512 bytes. Sectors= 8910423 [4350 MB] [4.4 GB]
| SCSI device sdb: hdwr sector= 512 bytes. Sectors= 6281856 [3067 MB] [3.1 GB]

The last kernel that worked on my machine (CHRP LongTrail) was 2.3.10 (a bit
unstable), but I'm using 2.3.6 right now since it's more stable.

Any clues?

Greetings,

Geert

    --
    Geert Uytterhoeven                     Geert.Uytterhoeven@cs.kuleuven.ac.be
    Wavelets, Linux/{m68k~Amiga,PPC~CHRP}  http://www.cs.kuleuven.ac.be/~geert/
    Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

- Next message: Peter Enderborg: "Re: Device deadlock."
- Previous message: Geert Uytterhoeven: "Re: NCR53C8XX fix for 2.3.14-pre2"