Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Sep 1998 01:29:31 +0200 (MET DST)
From:      Jean-Marc Zucconi <jmz@FreeBSD.ORG>
To:        ken@plutotech.com
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: [CAM] boot messages, not configured devices
Message-ID:  <199809212329.BAA00396@qix>
In-Reply-To: <199809212206.QAA09558@panzer.plutotech.com> (ken@plutotech.com)

next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> Kenneth D Merry writes:

 > Jean-Marc Zucconi wrote...
 >> Thanks to the latest changes in the ncr driver I am able to boot a cam
 >> kernel. It works well, but I get a lot of
 >> 'MSG_MESSAGE_REJECT received (2:8)' messages during boot (see log
 >> below). What do they mean?

 > It looks like one of your CDROM drives doesn't like it when we try to scan
 > additional LUNs.  I've attached a patch to cam_xpt.c, see if that elminates
 > the messages.

Indeed, my drives had a 'SC_ONE_LU' entry in the old scsiconf.c
file. However, your patch does not help - I still get the messages.

 >> In addition the cd driver refuses to attach my CD-R if there is
 >> no CD inside at boot time (cd2: fatal error: NOT READY), although it is
 >> correctly probed during the scan phase:
 >> pass5 at ncr1 bus 0 target 3 lun 0
 >> pass5: <PHILIPS CDD2600 1.07> Removable CD-ROM  SCSI2 device 
 >> pass5: 3.300MB/s transfers

 > Well, that's the passthrough driver, not the probe pseudo-peripheral.  The
 > passthrough driver will attach to anything that survives the probe phase.
 > (i.e., anything that responds to an inquiry)

[...]
 > There are a couple of possible explanations for this.  How long is your bus
 > settle delay?  It's possible that it takes a while to figure out that

it always was 8 seconds (8000 milliseconds now :-) and the old drivers
worked. Increasing to 30 seconds gives the same results.
 
 > doesn't have a CD in it or something like that.  Try increasing SCSI_DELAY
 > to 30000 (30 seconds).  Generally, when CDROM/WORM drives don't have any
 > media on board, they return a status of 0x3a,0x00.  (medium not present)
 > If that fixes the problem, you can decrease it gradually until you figure
 > out how long it needs.

It seems that the PHILIPS CDD2600 reply 'not ready' rather than
'medium not present' to the READ CAPACITY command if the medium is not
present. 

 > If increasing the bus settle delay doesn't fix it, there are other things
 > we can do that will probably fix the problem.

Jean-Marc

-- 
 Jean-Marc Zucconi                    PGP Key: finger jmz@FreeBSD.ORG

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809212329.BAA00396>