MESH problems in 2.2.x
Geert Uytterhoeven
Geert.Uytterhoeven at cs.kuleuven.ac.be
Tue Jun 22 23:00:31 EST 1999
On Mon, 7 Jun 1999, Geert Uytterhoeven wrote:
> On Thu, 3 Jun 1999, Paul Mackerras wrote:
> > Geert Uytterhoeven <Geert.Uytterhoeven at cs.kuleuven.ac.be> 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.
>
> This one seems to work.
But not perfect :-(
Since /me was stupid and told OF `boot scsi/disk at 5:' (i.e. I forgot the file
part of the path), my OF kept on enjoying autoreboot cycles with `rebooting in
the correct mode for this client program' messages. The only thing that stopped
this was to remove the power from the scsi/disk at 5 device. This was the first
time the power was removed since my previous mail about this.
And then I got
scsi1: device driver called scsi_done() for a syncronous reset
again, booting 2.3.6 from vger-june15.
Fortunately I still had the working 2.1.130 kernel around. After I booted that
first, I was able to boot my 2.3.6 kernel.
So to boot recent kernels when you have sync-capable devices on the MESH, two
conditions have to be met:
- boot 2.1.130 first
- mesh_sync_targets = 0 (setting CONFIG_SCSI_MESH_SYNC_RATE=0 doesn't work)
Anyone else seeing this?
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven at cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP} http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium
[[ 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. ]]
More information about the Linuxppc-dev
mailing list