[7639] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

RE: Linux SCSI seagate (TMC-950) driver help

daemon@ATHENA.MIT.EDU (Christian Jullien)
Mon Dec 6 16:46:47 1999

From: "Christian Jullien" <eligis@wanadoo.fr>
To: "Marc SCHAEFER" <schaefer@alphanet.ch>
Cc: <linux-scsi@vger.rutgers.edu>
Date:   Mon, 6 Dec 1999 21:41:20 +0100
Message-ID: <NDBBKEKEPPEHBDFOABLGAECICBAA.eligis@wanadoo.fr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.LNX.4.10.9912062011160.10995-100000@vulcan.alphanet.ch>

 > I second the other guy who said that maybe you are not at all getting any
 > interrupts. I looked quickly through seagate.c and the only case
 > I see the
 > interrupt routine called is for reselection.

So, if I understand well, every times I send a request, I'm busy waiting for
the response while, when I allow disconnect I should be waken up by an IRQ ?
right ?

 > Try really hard to change interrupts, etc. Disabling disconnection seems
 > like a remedy for the wrong problem.

Now I agree with you.

I'm confused, what wrong ? I assumes that my IRQ (5 in my case) is well
configured (it's the same IRQ 5, MEM 0x140, base 0xCA000 on my NT box). What
can I do if linux can't send me a request via IRQ 5 ? How I can track that
(i.e. trace IRQ ?) is there a tool to show possible conflicts ? Should I
give up ?


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post