[9190] in linux-scsi channel archive
Re: Problems with Linux-2.4.0-test[23] and st0
daemon@ATHENA.MIT.EDU (=?ISO-8859-1?Q?G=E9rard_Roudier?=)
Thu Jul 13 15:14:43 2000
Date: Thu, 13 Jul 2000 20:47:24 +0200 (CEST)
From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr>
To: Hartwig Felger <hgfelger@hgfelger.de>
cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.4.10.10007122118110.303-100000@frog.athome>
Message-ID: <Pine.LNX.4.10.10007132033320.2032-100000@linux.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
I have some idea about the problem.
The driver renegotiates on auto request sense following a check condition.
Given the default verbosity of the driver, if you are using variable
blocks with the device returning check condition status on each I/O in
order to allow to retrieve the actual block size using a request sense,
then the problem gets clear.
Could you for now try the following boot options:
sym53c8xx=verb:0,debug:0
Thanks for the report.
Gérard.
On Wed, 12 Jul 2000, Hartwig Felger wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Salut,
> as I made a backup on my tape, I tryed to get an index in a second run. I
> do that with dds2index (Version 2.4.12 pretty old...). It took a huge
> amount of time. Later I found out, that it had filled my /var/log/message
> - -----------o<----------
> Jul 7 00:01:18 dog kernel: scntl3=0x30 scntl4=0x0 ofs=15 fak=2 chg=0.
> Jul 7 00:01:18 dog kernel: sym53c875-0-<6,0>: sync msgout: 1-3-1-c-10.
> Jul 7 00:01:18 dog kernel: sym53c875-0-<6,0>: sync msg in: 1-3-1-20-f.
> Jul 7 00:01:18 dog kernel: sym53c875-0-<6,0>: sync: per=32 scntl3=0x30
> scntl4=0x0 ofs=15 fak=2 chg=0.
> Jul 7 00:01:18 dog kernel: sym53c875-0-<6,0>: sync msgout: 1-3-1-c-10.
> Jul 7 00:01:18 dog kernel: sym53c875-0-<6,0>: sync msg in: 1-3-1-20-f.
> Jul 7 00:01:18 dog kernel: sym53c875-0-<6,0>: sync: per=32 scntl3=0x30
> scntl4=0x0 ofs=15 fak=2 chg=0.
> ...
> got 316 lines a second!!!
> - --------------------->o-------------
>
> Today I tryed to do a tar behind the backup, just to watch what the log
> may say - for that I did a "mtst fsf 2":
> - -------------------o<--------------------
> Jul 12 20:38:37 dog kernel: Detected scsi tape st0 at scsi0, channel 0, id
> 6, lun 0
> Jul 12 20:38:37 dog kernel: st: bufsize 32768, wrt 30720, max init.
> buffers 4, s/g segs 16.
> Jul 12 20:38:37 dog kernel: sym53c875-0-<6,0>: sync msgout: 1-3-1-c-10.
> Jul 12 20:38:37 dog kernel: sym53c875-0-<6,0>: sync msg in: 1-3-1-20-f.
> Jul 12 20:38:37 dog kernel: sym53c875-0-<6,0>: sync: per=32 scntl3=0x30
> scntl4=0x0 ofs=15 fak=2 chg=0.
> Jul 12 20:38:37 dog kernel: sym53c875-0-<6,*>: FAST-10 SCSI 6.7 MB/s (150
> ns, offset 15)
> Jul 12 20:38:37 dog kernel: sym53c875-0-<6,0>: sync msgout: 1-3-1-c-10.
> Jul 12 20:38:37 dog kernel: sym53c875-0-<6,0>: sync msg in: 1-3-1-20-f.
> Jul 12 20:38:37 dog kernel: sym53c875-0-<6,0>: sync: per=32 scntl3=0x30
> scntl4=0x0 ofs=15 fak=2 chg=0.
> Jul 12 20:38:37 dog kernel: st0: Block limits 1 - 16777215 bytes.
> - ----------------->o------------------
> tar did not produce a line in the log (fine!). So I think, it has
> something to do with positioning.
>
> hartwig :-(
>
> - --
> 1024D/339FD693 Hartwig Felger <hgfelger@hgfelger.de>
> Key fingerprint = FB2F 3EE9 345A D55B 6FF2 0EC1 F5B0 684F 339F D693
> For the pulic keys, please visit my page.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.0 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iD8DBQE5bM0S9bBoTzOf1pMRAmO5AJ9TD0jbU2aovk/uqb5S2O6gfVw6gwCeI2iI
> /uSwBMp1K9h/Nrr2OPK2OLY=
> =jBRF
> -----END PGP SIGNATURE-----
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.rutgers.edu
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
