--Signature_Sat__16_Apr_2005_17_59_05_-0400_NpYTapj27gvTeuTR
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> sd0 at scsibus1 target 0 lun 0: <QUANTUM, FIREBALL SE4.3S, PJ0A> disk
> fixed
> sd0: 4110 MB, 7637 cyl, 4 head, 275 sec, 512 bytes/sect x 8418816
> sectors
> probe(mesh0:0:1:0): max sync rate 10.00Mb/s
> sd1 at scsibus1 target 1 lun 0: <IBM OEM, DFHSS4F, 4141> disk fixed
> sd1: drive offline
...
> mesh0: timeout state 3
> mesh0: intr/msk 00/07, exc 00, err 00, st0/1 21/40
> mesh: resetting DMA

> note the last messages, the typical scsi/mesh/sync troubles...
Yeah, looks like the mesh patch didn't make it into 2.0.2 for whatever reas=
on.

> I don't remember which magic michael used last time. I think he forced
> sync on for some devices. This means in any case that negotiation still
> has troubles.
No, I forced sync off first, then I hacked mesh to cope with sync. The prob=
lem is that the unpatched mesh driver accepts sync negotiation from other S=
CSI devices, the bits in flags only keep it from starting the negotiation i=
tself.

have fun
Michael

--Signature_Sat__16_Apr_2005_17_59_05_-0400_NpYTapj27gvTeuTR
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQmGKqcpnzkX8Yg2nAQJkJgf8DXuE9kTuJgxLdsx2G9Qf2NDoV/4cYKGU
2n3QIdQEsIVRxv/lWQyXf5SmiRNU/w4anT65i2rVjQ63Jys3ysnzAcbfL0A38yBu
3HWO+tYUwuOLaEWdaiJ7zXvIePZEpVoq/UfQuT2Nv51GErQyL6NHN/Rm0MF53Ikz
ZnbLjY4xXrORLMPzZt13tXa6tDaT8jlep7bijQcbr7WuR/1iJipJibvQYoTXFaSY
cpYS4UDPnubDeKmsW34E5yrPU7AyECQ1AEOiZT/QNN9A4PUyNMwU7VzX/uusLuS1
elNWnojg6tdg0ZCAOja6bFy6NCF0LqY01CvH2KVAFkhKpabZ0oWPOg==
=y/XF
-----END PGP SIGNATURE-----

--Signature_Sat__16_Apr_2005_17_59_05_-0400_NpYTapj27gvTeuTR--