From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 3 Jun 1999 15:46:12 +1000 Message-Id: <199906030546.PAA00546@tango.anu.edu.au> From: Paul Mackerras To: Geert.Uytterhoeven@cs.kuleuven.ac.be CC: linuxppc-dev@lists.linuxppc.org In-reply-to: (message from Geert Uytterhoeven on Wed, 2 Jun 1999 10:47:18 +0200 (CEST)) Subject: Re: MESH problems in 2.2.x Reply-to: Paul.Mackerras@cs.anu.edu.au References: Sender: owner-linuxppc-dev@lists.linuxppc.org List-Id: Geert Uytterhoeven wrote: > During boot up I now see the message: > > scsi1: device driver called scsi_done() for a syncronous reset The reset and abort handling in the mesh driver needs to be updated; the way the scsi mid-layer expects them to work changed during the 2.1 series but I haven't updated the mesh driver to the new way yet, partly because I don't know exactly what the new way is. :-) > Since the message mentions `syncronous reset' and since the old Conner doesn't > seem to do synchronous mode, this makes me think the mesh driver fails with > synchronous devices in 2.2.x. Is this correct? Does anyone else see this > problem? It's working OK for me now with a 2.3.4 kernel, having fixed ioremap (the fix is now in vger for both the 2.2 and 2.3 branches). If you want to disable sync mode, you could change the initializer for mesh_sync_targets in drivers/scsi/mesh.c from 0xff to 0. Regards, Paul. [[ This message was sent via the linuxppc-dev mailing list. Replies are ]] [[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]] [[ reply is of general interest. Please check http://lists.linuxppc.org/ ]] [[ and http://www.linuxppc.org/ for useful information before posting. ]]