On 28.06.2012 09:56, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 23:14:43 Alexander Motin wrote:
On 27.06.2012 23:08, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 19:51:15 Alexander Motin wrote:
On 06/27/12 19:26, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 18:15:24
26.06.2012 20:19, Alexander Motin пишет:
I see no problems in this output. I would enable more debugging with
`camcontrol debug -IPp all` before plugging it in to see what's going on.
Here it is:
-
sudo: bsam : TTY=pts/5 ; PWD=/home/bsam ; USER=root ;
COMMAND=/sbin/camcontrol debug
On 06/27/12 11:07, Boris Samorodov wrote:
26.06.2012 20:19, Alexander Motin пишет:
I see no problems in this output. I would enable more debugging with
`camcontrol debug -IPp all` before plugging it in to see what's going on.
Here it is:
-
sudo: bsam : TTY=pts/5 ; PWD=/home/bsam ;
On 06/27/12 11:45, Alexander Motin wrote:
On 06/27/12 11:07, Boris Samorodov wrote:
26.06.2012 20:19, Alexander Motin пишет:
I see no problems in this output. I would enable more debugging with
`camcontrol debug -IPp all` before plugging it in to see what's going
on.
Here it is:
-
sudo:
On 06/27/12 12:55, Boris Samorodov wrote:
27.06.2012 12:45, Alexander Motin пишет:
Something is wrong there. I think this should not happen:
kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
kernel:
27.06.2012 15:51, Alexander Motin пишет:
The only change after that I see potentially related is r237478. It adds
more checks when fetching SCSI sense data, that for some reason are not
working in your case. I still can not completely understand why there
was no any READ CAPACITY errors
On 06/27/12 17:45, Boris Samorodov wrote:
27.06.2012 15:51, Alexander Motin пишет:
The only change after that I see potentially related is r237478. It adds
more checks when fetching SCSI sense data, that for some reason are not
working in your case. I still can not completely understand why
On Wednesday 27 June 2012 17:08:29 Alexander Motin wrote:
umass problem
Hi,
Are you verifying the received data length for the SCSI commands reading out
various data?
BTW: You could try:
usbconfig -d X.Y reset
Not sure if it helps.
--HPS
___
On 06/27/12 18:17, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 17:08:29 Alexander Motin wrote:
umass problem
Hi,
Are you verifying the received data length for the SCSI commands reading out
various data?
Mentioned revision beyond others adds check for the sense data length in
On Wednesday 27 June 2012 17:17:02 Hans Petter Selasky wrote:
On Wednesday 27 June 2012 17:08:29 Alexander Motin wrote:
umass problem
Hi,
Are you verifying the received data length for the SCSI commands reading
out various data?
BTW: You could try:
usbconfig -d X.Y reset
Not
On Wednesday 27 June 2012 17:28:30 Alexander Motin wrote:
On 06/27/12 18:17, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 17:08:29 Alexander Motin wrote:
umass problem
Hi,
Are you verifying the received data length for the SCSI commands reading
out various data?
On 06/27/12 18:31, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 17:28:30 Alexander Motin wrote:
On 06/27/12 18:17, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 17:08:29 Alexander Motin wrote:
umass problem
Hi,
Are you verifying the received data length for the SCSI commands
On Wednesday 27 June 2012 17:33:45 Alexander Motin wrote:
On 06/27/12 18:31, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 17:28:30 Alexander Motin wrote:
On 06/27/12 18:17, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 17:08:29 Alexander Motin wrote:
umass problem
Hi,
On Wednesday 27 June 2012 17:58:57 Boris Samorodov wrote:
27.06.2012 19:36, Hans Petter Selasky пишет:
Then you need to check using usbdump -i usbusX -s 65536 - what is
actually going on there.
I'm using the unpatched kernel (i.e. stock r237572). There is no
/dev/ad*. I use usbconfig
On Wednesday 27 June 2012 18:15:24 Hans Petter Selasky wrote:
ERR=STALLED
Retrying might not work, until sense is cleared, due to stalled error.
MAV: Maybe that failed prevent-allow medium removal left a sense error that
needs to be cleared.
--HPS
On 06/27/12 19:26, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 18:15:24 Hans Petter Selasky wrote:
ERR=STALLED
Retrying might not work, until sense is cleared, due to stalled error.
MAV: Maybe that failed prevent-allow medium removal left a sense error that
needs to be cleared.
It
On Wednesday 27 June 2012 19:51:15 Alexander Motin wrote:
On 06/27/12 19:26, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 18:15:24 Hans Petter Selasky wrote:
ERR=STALLED
Retrying might not work, until sense is cleared, due to stalled error.
MAV: Maybe that failed
On 27.06.2012 23:08, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 19:51:15 Alexander Motin wrote:
On 06/27/12 19:26, Hans Petter Selasky wrote:
On Wednesday 27 June 2012 18:15:24 Hans Petter Selasky wrote:
ERR=STALLED
Retrying might not work, until sense is cleared, due to stalled
Hi!
I've got a Kingston USB 8Gb stick. It was too noisy (with respect
to /var/log/messages) but worked. The system was upgraded today
morning:
-
% uname -a
FreeBSD bsam.wart.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #17 r237572: Tue
Jun 26 04:22:18 SAMT 2012
On Tuesday 26 June 2012 14:29:28 Boris Samorodov wrote:
Hi!
I've got a Kingston USB 8Gb stick. It was too noisy (with respect
to /var/log/messages) but worked. The system was upgraded today
morning:
-
% uname -a
FreeBSD bsam.wart.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #17 r237572: Tue
On 06/26/12 18:41, Hans Petter Selasky wrote:
On Tuesday 26 June 2012 14:29:28 Boris Samorodov wrote:
I've got a Kingston USB 8Gb stick. It was too noisy (with respect
to /var/log/messages) but worked. The system was upgraded today
morning:
-
% uname -a
FreeBSD bsam.wart.ru 10.0-CURRENT
21 matches
Mail list logo
