Re: ahc and SMP

2000-09-24 Thread German Tischler 

On Sun, Sep 24, 2000 at 05:36:43AM +0200, Kenneth D. Merry wrote:
 On Sun, Sep 24, 2000 at 00:04:38 +0200, German Tischler wrote:
 So if you don't have enough pass(4) devices in /dev, you may not see some
 of the devices that are there.
 
 So make sure you have /dev/pass{0-4}.
 
 Another way to make sure you have a pass device for cd1 is to do:
 
 camcontrol tur cd1 -v

Thank you, that lets cdrecord find all devices. What got me confused
is that MAKEDEV pass4 does not create pass4 but 0-3, but that is
clear from reading MAKEDEV.

--gt



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

ahc and SMP

2000-09-23 Thread German Tischler 

Hi.

On my machine the ahc (aic) driver times out while probing for devices
on SMP, while it is working on UP.

dmesg says

ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter port 0xd000-0xd0ff mem 0xe100
-0xe1000fff irq 15 at device 6.0 on pci0
aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs

while booting the SMP kernel it says

(probe0:ahc0:0:0:0) Timedout SCB 9 handled by another timeout
(probe1:ahc0:0:1:0) SCB 0x8 - timed out while idle, SEQADDR == 0x167
sg[0] - Addr 0x7f2f684 : Length -2147483612
(probe1:ahc0:0:1:0) Queuing a BDR SCB
(probe1:ahc0:0:1:0) no longer in timeout, status = 34a

and after some more time will print more timeout messages and will not (at
least not for a few minutes) finish probing or announce any SCSI devices.

devices connected are

da0 at ahc0 bus 0 target 2 lun 0
da0: IBM DORS-32160 S82C Fixed Direct Access SCSI-2 device
da0: 10.000MB/s transfers (10.000MHz, offset 15)
da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C)
da1 at ahc0 bus 0 target 3 lun 0
da1: IBM DCAS-34330 S65A Fixed Direct Access SCSI-2 device
da1: 20.000MB/s transfers (20.000MHz, offset 15)
da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
da2 at ahc0 bus 0 target 8 lun 0
da2: IBM DDYS-T18350N S80D Fixed Direct Access SCSI-3 device
da2: 40.000MB/s transfers (20.000MHz, offset 63, 16bit)
da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)

Is anyone else seeing this ?

Another strange thing is that cdrecord -scanbus tells me

scsibus0:
0,0,0 0) *
0,1,0 1) *
0,2,0 2) 'IBM ' 'DORS-32160  ' 'S82C' Disk
0,3,0 3) 'IBM ' 'DCAS-34330  ' 'S65A' Disk
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
0,8,0 8) 'IBM ' 'DDYS-T18350N' 'S80D' Disk
scsibus1:
1,0,0   100) 'YAMAHA  ' 'CRW4260 ' '1.0h' Removable CD-ROM
1,1,0   101) *
1,2,0   102) *
1,3,0   103) *
1,4,0   104) *
1,5,0   105) *
1,6,0   106) *
1,7,0   107) *

While camcontrol devlist says

IBM DORS-32160 S82C  at scbus0 target 2 lun 0 (pass0,da0)
IBM DCAS-34330 S65A  at scbus0 target 3 lun 0 (pass1,da1)
IBM DDYS-T18350N S80Dat scbus0 target 8 lun 0 (pass2,da2)
YAMAHA CRW4260 1.0h  at scbus1 target 0 lun 0 (pass3,cd0)
NEC CD-ROM DRIVE:465 1.03at scbus1 target 1 lun 0 (pass4,cd1)

Maybe just a bug in cdrecord.

--gt



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ahc and SMP

2000-09-23 Thread Kenneth D. Merry 

On Sun, Sep 24, 2000 at 00:04:38 +0200, German Tischler wrote:

[ problems with SMP, but not UP kernels, I don't know anything about that ]

 Is anyone else seeing this ?
 
 Another strange thing is that cdrecord -scanbus tells me
 
 scsibus0:
 0,0,0 0) *
 0,1,0 1) *
 0,2,0 2) 'IBM ' 'DORS-32160  ' 'S82C' Disk
 0,3,0 3) 'IBM ' 'DCAS-34330  ' 'S65A' Disk
 0,4,0 4) *
 0,5,0 5) *
 0,6,0 6) *
 0,7,0 7) *
 0,8,0 8) 'IBM ' 'DDYS-T18350N' 'S80D' Disk
 scsibus1:
 1,0,0   100) 'YAMAHA  ' 'CRW4260 ' '1.0h' Removable CD-ROM
 1,1,0   101) *
 1,2,0   102) *
 1,3,0   103) *
 1,4,0   104) *
 1,5,0   105) *
 1,6,0   106) *
 1,7,0   107) *
 
 While camcontrol devlist says
 
 IBM DORS-32160 S82C  at scbus0 target 2 lun 0 (pass0,da0)
 IBM DCAS-34330 S65A  at scbus0 target 3 lun 0 (pass1,da1)
 IBM DDYS-T18350N S80Dat scbus0 target 8 lun 0 (pass2,da2)
 YAMAHA CRW4260 1.0h  at scbus1 target 0 lun 0 (pass3,cd0)
 NEC CD-ROM DRIVE:465 1.03at scbus1 target 1 lun 0 (pass4,cd1)
 
 Maybe just a bug in cdrecord.

IIRC, cdrecord opens up each device to do an inquiry on it.

So if you don't have enough pass(4) devices in /dev, you may not see some
of the devices that are there.

So make sure you have /dev/pass{0-4}.

Another way to make sure you have a pass device for cd1 is to do:

camcontrol tur cd1 -v

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message