* Sym53c8xx in 2.3.now
@ 1999-09-01 15:16 Geert Uytterhoeven
1999-09-01 20:35 ` D. Lance Robinson
1999-09-05 21:12 ` vger on LongTrail (was: Re: Sym53c8xx in 2.3.now) Geert Uytterhoeven
0 siblings, 2 replies; 4+ messages in thread
From: Geert Uytterhoeven @ 1999-09-01 15:16 UTC (permalink / raw)
To: Linux/PPC Development
Anybody who has the sym53c8xx or ncr53c8xx driver working with the latest 2.3.x kernels?
I get:
| 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]
Disabling sym53c8xx and using ncr53c8xx instead doesn't fix the problem.
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven@sonycom.com
Sony Suprastructure Center Europe (SUPC-E) --- Brussels --- Belgium
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Sym53c8xx in 2.3.now
1999-09-01 15:16 Sym53c8xx in 2.3.now Geert Uytterhoeven
@ 1999-09-01 20:35 ` D. Lance Robinson
1999-09-01 22:00 ` Geert Uytterhoeven
1999-09-05 21:12 ` vger on LongTrail (was: Re: Sym53c8xx in 2.3.now) Geert Uytterhoeven
1 sibling, 1 reply; 4+ messages in thread
From: D. Lance Robinson @ 1999-09-01 20:35 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: Linux/PPC Development
Geert,
You should post your message on the linux-scsi list server. Gerard, who
wrote the driver listens in on that list.
send to linux-scsi@vger.rutgers.edu
<>< Lance.
Geert Uytterhoeven wrote:
>
> Anybody who has the sym53c8xx or ncr53c8xx driver working with the latest 2.3.x kernels?
>
> I get:
>
> | 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]
>
> Disabling sym53c8xx and using ncr53c8xx instead doesn't fix the problem.
>
> Greetings,
>
> Geert
>
> --
> Geert Uytterhoeven Geert.Uytterhoeven@sonycom.com
> Sony Suprastructure Center Europe (SUPC-E) --- Brussels --- Belgium
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Sym53c8xx in 2.3.now
1999-09-01 20:35 ` D. Lance Robinson
@ 1999-09-01 22:00 ` Geert Uytterhoeven
0 siblings, 0 replies; 4+ messages in thread
From: Geert Uytterhoeven @ 1999-09-01 22:00 UTC (permalink / raw)
To: D. Lance Robinson; +Cc: Linux/PPC Development
On Wed, 1 Sep 1999, D. Lance Robinson wrote:
> You should post your message on the linux-scsi list server. Gerard, who
> wrote the driver listens in on that list.
>
> send to linux-scsi@vger.rutgers.edu
I already did more than a week ago. No response.
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven@sonycom.com
Sony Suprastructure Center Europe (SUPC-E) --- Brussels --- Belgium
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
^ permalink raw reply [flat|nested] 4+ messages in thread
* vger on LongTrail (was: Re: Sym53c8xx in 2.3.now)
1999-09-01 15:16 Sym53c8xx in 2.3.now Geert Uytterhoeven
1999-09-01 20:35 ` D. Lance Robinson
@ 1999-09-05 21:12 ` Geert Uytterhoeven
1 sibling, 0 replies; 4+ messages in thread
From: Geert Uytterhoeven @ 1999-09-05 21:12 UTC (permalink / raw)
To: Linux/PPC Development
On Wed, 1 Sep 1999, Geert Uytterhoeven wrote:
> Anybody who has the sym53c8xx or ncr53c8xx driver working with the latest 2.3.x kernels?
>
> I get:
>
> | 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...
I'm starting to think that the problem is related to interrupts. I also get one
or two messages `Keyboard timeout[2]', and the keyboard (PS/2) doesn't seem to
work (Caps Lock doesn't toggle the Caps Lock LED).
Besides, things are getting worse. For the current vger kernel, I needed this
patch to make it compile:
Index: include/asm-ppc/serial.h
===================================================================
RCS file: /vger/u4/cvs/linux/include/asm-ppc/serial.h,v
retrieving revision 1.7
diff -u -r1.7 serial.h
--- serial.h 1999/09/02 21:23:49 1.7
+++ serial.h 1999/09/05 21:11:22
@@ -33,7 +33,6 @@
#endif
#else
-#define SERIAL_PORT_DFNS
/*
* PReP, CHRP, etc.
*/
@@ -52,6 +51,9 @@
#define ACCENT_FLAGS 0
#define BOCA_FLAGS 0
#define HUB6_FLAGS 0
+#define RS_TABLE_SIZE 64
+#else
+#define RS_TABLE_SIZE 4
#endif
/*
And now my serial console is scrambled after the serial port init :-(
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven@sonycom.com
Sony Suprastructure Center Europe (SUPC-E) --- Brussels --- Belgium
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-09-05 21:12 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-09-01 15:16 Sym53c8xx in 2.3.now Geert Uytterhoeven
1999-09-01 20:35 ` D. Lance Robinson
1999-09-01 22:00 ` Geert Uytterhoeven
1999-09-05 21:12 ` vger on LongTrail (was: Re: Sym53c8xx in 2.3.now) Geert Uytterhoeven
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).