[9045] in linux-scsi channel archive
Re: HP 5P scanner supplied SCSI board driver
daemon@ATHENA.MIT.EDU (Shawn Houston)
Tue Jun 20 17:24:16 2000
Message-ID: <394FD23E.B6523089@mosquitonet.com>
Date: Tue, 20 Jun 2000 12:21:18 -0800
From: Shawn Houston <houston@mosquitonet.com>
MIME-Version: 1.0
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: linux-scsi@vger.rutgers.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Douglas Gilbert wrote:
>
> Shawn Houston wrote:
> >
> > Doug Gilbert or Leonard N. Zubkoff or ???:
> >
> > Looking through the MAINTAINERS file, this address looks like the best
> > bet for reporting my problem:
> >
> > After upgrading to the 2.2.16 kernel, with or without the errata patch,
> > my HP 5P scanner supplied sym53c416 SCSI interface board stopped
> > working. Kernels 2.2.12 through 2.2.15 have no problem.
> >
> > The symtom is that when the scanner is accessed the machine freezes for
> > long periods with short bursts of interaction, just like an IRQ sharing
> > conflict. I tried looking in the 2.2.16 patch set, but there is so much
> > change in the SCSI subsystem that I cannot pinpoint the problem.
> >
> > I have an ATAPI CD-RW that needs the IDE-SCSI module and I think this is
> > where the problem lies. I have had problems with interactions between
> > IDE-SCSI and the IDE subsystems locking up my system in the past when I
> > used hdparm to unmask interrupts on my IDE drive (-u1 flag).
> >
> > I have an AMD K6-2 system with a FIC 503+ MB. HP 9100i ATAPI CD-RW,
> > sym53c416,IDE HD,
> > RH 6.2 base system install, custom kernel.
> >
> > I welcome any direction to help isolate the problem. I am not unfamiliar
> > with the kernel and a pretty good C programmer and I pride myself on my
> > debugging skills.
> >
> > I already checked that the sym53c416 has not changed between 2.2.15 and
> > 2.2.16.
>
> Shawn,
> If you suspect sg you can go to:
> http:/www.torque.net/sg
> and regress that driver from sg version 2.1.37 (as
> found in lk 2.2.16) to 2.1.36. See the table on that
> page for a tarball.
>
> Doug Gilbert
Doug,
I downgraded the latest kernel, 2.2.16 with errata patch, to sg 2.1.36,
the problem went away.
I did notice that building the SCSI system is partialy broken: you can
go ALL modular, or no modules. If you mix you get undefined symbols
errors.
I build my kernel all modules except the very basics, ext2, etc.
If I can help pinpoint the trouble, let me know.
-Shawn Houston
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
