> Hans-Frieder Vogt writes:
> > Richard Gooch writes:
> > ...
> > > > > CONFIG_SCSI_NCR53C8XX=y
> > > > > CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
> > > > > CONFIG_SCSI_NCR53C8XX_MAX_TAGS=4
> > > >
> > > > A default value of 8 for a max value of 4 for the same thing is
> > > > bogus.
> > >
> > > Hm. I think this is an artefact of using make oldconfig: originally
> > > there was the MAX_TAGS option IIRC and I took the default value of
> > > 4. Later the DEFAULT_TAGS option came along and I took the default
> > > again. Since that new option came first, I didn't realise there was an
> > > inconsistency. Once I selected the default for the new option,
> > > make oldconfig would zoom past the MAX_TAGS option.
> >
> > I also had an old .config file and the same values.
> > After I changed CONFIG_SCSI_NCR53C8XX_MAX_TAGS to 32 (as proposed) the driver
> > 3.1a worked FINE :) (tested with pre-patch 2.1.127-7)
>
> I just tried this too and I can confirm that the timeout problem I was
> having went away.
I just tried the kernel image you sent me and didn't experience any
timeout problem on my system. The problem was probably in driver 3.0i but
just hidden by a different tag numbering scheme. The succes I have with a
kernel image that fails on your system indicates that some other
conditions must be met in order to trigger the timeout problem.
Will let you know if some additionnal testing will be usefull for me.
Thanks.
Regards,
Gerard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/