freebsd-scsi Digest, Vol 359, Issue 2
freebsd-sc...@freebsd.org
freebs...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
or, via email, send a message with subject or body 'help' to
freebsd-sc...@freebsd.org
You can reach the person managing the list at
freebsd-s...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-scsi digest..."
Today's Topics:
1. Query on mkpart behaviour when there is no SCSI connected.
(VIKAS SONI)
----------------------------------------------------------------------
Message: 1
Date: Tue, 9 Mar 2010 11:31:13 +0530
From: VIKAS SONI <vikas...@gmail.com>
Subject: Query on mkpart behaviour when there is no SCSI connected.
To: freebs...@freebsd.org
Message-ID:
<e4ce418f1003082201x420...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
We are debugging SCSI driver for LynxOS on ppc architecture board.
We are trying to run mkpart application (mkpart /dev/rsdncr.0) on ppc board
when there is no SCSI connected.
The observed behavior is the user application will hang and (Ctrl + C) is
used to get the bash prompt or to come out of user application.
As the request for device identification is not completed due to no SCSI
connected, it waits over semaphore at that point in the driver and does not
return
back to user application with some error. The only way to come out of user
application is by pressing (Ctrl +C).
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[System: /] $ mkpart /dev/rsdncr.0
^C
[System: /] $ mkpart /dev/rsdncr.1
^C
[System: /] $ mkpart /dev/rsdncr.2
^C
[System: /]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Is our understanding correct?
Is the user application when no SCSI connected is supposed to behave in this
way?
Thanks in advance,
Vikas Soni
------------------------------
End of freebsd-scsi Digest, Vol 359, Issue 2
********************************************