Its probaly due to the semaphore changes that went in to test11 by
Richard Henderson. scsi_wait_req will grab one on entry. Did test10
work for you on Alpha?

Regards,

Torben Mathiasen

> -----Original Message-----
> From: Rival, Frank 
> Sent: 30. november 2000 21:37
> To: Ezolt, Phillip
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
> Estabrook, Jay; [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: Alpha SCSI error on 2.4.0-test11
> 
> 
> Hi Phil,
> 
> Phillip Ezolt wrote:
> 
> > Hi All,
> > 
> > Qlogic SCSI support seems broken on 2.4.0-test11 on a Miata 
> (Digital Personal WorkStation 600au).
> > 
> > When starting up, we get a machine check after initialing 
> the qlogic SCSI code. 
> > 
> > Using the Alpha kgdb, we figured out that the code is dying 
> in scsi_wait_request().
> 
> Wow, I'm impressed!  I didn't realize that kgdb worked on 
> Alpha...Were 
> you using the remote kgdb?  (You can answer me offline to save 
> bandwidth.)  This would be a _huge_ help in trying to figure 
> out why my 
> Wildfire^WGS160 is crashing with the DISCONTIGMEM code that I 
> stole from 
> Jay and have been hacking on.
> 
> Speaking of that system, it has two QLogic adapters in it 
> (both 1040Bs, 
> like the Miata), and they are working just fine under 2.4.0-test11 
> (obviously, without my changes ;).  It looks like it's probably the 
> platform code that's busted.  I can't remember...are those Pyxis or 
> CIA?  Anyway, could this have something to do with the PCI & 
> PCI bridge 
> work that Richard and Ivan just submitted?
> 
> - Pete
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Reply via email to