Re: Problem w/ 2.2.10-ac12 & NCR53c875

Dumb Kid (dumbkid@hotmail.com)
Tue, 27 Jul 1999 19:14:03 GMT


We have an alpha w/ NCR53c860 boots fine on
2.2.10-ac12 without any modification.

It might only affect ncr53c875 adapters.

sym53c8xx: at PCI bus 0, device 9, function 0
sym53c8xx: 53c860 detected with Symbios NVRAM
sym53c860-0: rev=0x02, base=0x19000000, io_port=0x8800, irq=19
sym53c860-0: Symbios format NVRAM, ID 7, Fast-20, Parity Checking
sym53c860-0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/ce/a0/00/00/00
sym53c860-0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/ce/a0/00/08/00
sym53c860-0: resetting, command processing suspended for 2 seconds
sym53c860-0: restart (scsi reset).
ncr53c8xx: at PCI bus 0, device 9, function 0
ncr53c8xx: IO region 0x8800 to 0x887f is in use
scsi0 : sym53c8xx - version 1.3c
scsi : 1 host.
sym53c860-0: command processing resumed
Vendor: SEAGATE Model: ST34555N Rev: 0930
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
sym53c860-0-<0,0>: tagged command queue depth set to 8
scsi : detected 1 SCSI disk total.
sym53c860-0-<0,*>: FAST-20 SCSI 20.0 MB/s (50 ns, offset 8)

>From: Gerard Roudier <groudier@club-internet.fr>
>To: Ed Hall <edhall@screech.weirdnoise.com>
>CC: Dumb Kid <dumbkid@hotmail.com>, linux-kernel@vger.rutgers.edu,
>linux-scsi@vger.rutgers.edu
>Subject: Re: Problem w/ 2.2.10-ac12 & NCR53c875
>Date: Tue, 27 Jul 1999 19:45:12 +0200 (MET DST)
>
>
>
>On Mon, 26 Jul 1999, Ed Hall wrote:
>
> > > I am having trouble getting the 2.2.10-ac12 to boot. My system
> > > is alpha LX164 w/ NCR53c875.
> >
> > I noticed this with 2.2.10-ac11. Reverting
>"arch/alpha/kernel/core_pyxis.c"
> > to the original 2.2.10 file fixes it for now. I'm sure a more
> > permanent fix will be appearing shortly from Alan Cox and from the
> > tireless Alpha contingent.
> >
> > The problem is a mismatch between where various patches assume the PCI
> > windows are located, and not the SCSI driver itself.
>
>And, in case of people would ignore it, I have had to diagnose the problem
>by myself and I donnot have an Alpha machine, neither really know of the
>Alpha stuff, since the solution was very slow to come.
>The solution is known since almost a week, and I didn't see any official
>fix for it posted to the lists by the maintainers of the offending code.
>
>If the reason is that this bad changes in the pyxis_core stuff only affect
>the sym53c8xx devices and only on Alpha machines and thus guys think it is
>not important, then they just appear as not interesting people to me. I am
>wondering about what would have happened facing a bad change that affected
>also (or only) Adaptec devices on Intel platforms.
>
>Gérard.
>

_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com

-
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/