Well, that's good- but the midlayer really should check for the
XS_DRIVER_STUFFUP case and say something a bit less cryptic than "invalid
return code".


On Fri, 17 May 2002, mel kravitz wrote:

> Before you do anything Matt Thomas isolated this to size of ram
> i have in the box -1.128GB causes observed problem -i verified
> this with 128MB and box is fine.
> -Mel
> 
> 
> Matthew Jacob wrote:
> > 
> > Actually- I'm going to check in a change to the midlayer so it doesn't say
> > "invalid return"
> > 
> > On Fri, 17 May 2002, Manuel Bouyer wrote:
> > 
> > > On Thu, May 16, 2002 at 04:24:13PM -0400, mel kravitz wrote:
> > > > Hi,
> > > > On one of my PWS433au boxes running current (4/29) i am getting after
> > > > running for
> > > > a few min...sd0(isp0:0:0:0): ..invalid return code from adapter:3
> > > > after several log messages the drive  effectively 'disconnects' from the
> > > > system
> > > > and no keyboard input works. I added a siop0 card, changed hard drive
> > > > etc...same
> > > > message. Anyone seen this ? Is this terminal  for the box-> dumpster
> > > > time?
> > >
> > > Hum, code 3 is "XS_DRIVER_STUFFUP". If no other message from siop0 is printed,
> > > then it's because the drive returned an invalid status.
> > >
> > > Can you recompile a kernel with the attached patch ? The siop driver should
> > > give more details about what's going on.
> > >
> > > --
> > > Manuel Bouyer <bouyer@antioche.eu.org>
> > > --
> > >
>