* Help needed to solve SCSI problem
@ 1999-03-26 23:23 Thomas Bogendoerfer
1999-03-26 23:49 ` William J. Earl
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Bogendoerfer @ 1999-03-26 23:23 UTC (permalink / raw)
To: linux
I'm now total stuck with the remaining SCSI problem, and need some help.
I have a really broken cdrom drive. With this cdrom I'm able produce a
scsi timeout, which will cause a hang of the complete machine. I've
traced the problem a little bit further, and detected, that I get
interrupts on interrupt vector 0 (it's named VECTOR_GIO0 in the Irix
header files). I always see 17 irq 0 then the machine hangs completly.
Please, could someone tell what this interrupt means, so I can either
solve it by servicing the interrupt the right way or avoid it by doing
something else ?
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Help needed to solve SCSI problem
1999-03-26 23:23 Help needed to solve SCSI problem Thomas Bogendoerfer
@ 1999-03-26 23:49 ` William J. Earl
1999-03-27 0:39 ` Thomas Bogendoerfer
0 siblings, 1 reply; 3+ messages in thread
From: William J. Earl @ 1999-03-26 23:49 UTC (permalink / raw)
To: Thomas Bogendoerfer; +Cc: linux
Thomas Bogendoerfer writes:
> I'm now total stuck with the remaining SCSI problem, and need some help.
>
> I have a really broken cdrom drive. With this cdrom I'm able produce a
> scsi timeout, which will cause a hang of the complete machine. I've
> traced the problem a little bit further, and detected, that I get
> interrupts on interrupt vector 0 (it's named VECTOR_GIO0 in the Irix
> header files). I always see 17 irq 0 then the machine hangs completly.
>
> Please, could someone tell what this interrupt means, so I can either
> solve it by servicing the interrupt the right way or avoid it by doing
> something else ?
I believe that is the two bits:
#define EXTIO_HPC3_BUSERR 0x0010
#define EXTIO_SG_STAT_0 0x0001
HPC3_BUSERR means that the HPC3 got a bus error reading from memory.
The driver is probably broken and giving bad commands to the HPC3.
You should be able to find the error address in the GIO_ERR_ADDR register:
#define GIO_ERR_ADDR 0x1fa000f4 /* GIO error address (w, ro) */
(0xbfa000f4 as a K1SEG address).
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Help needed to solve SCSI problem
1999-03-26 23:49 ` William J. Earl
@ 1999-03-27 0:39 ` Thomas Bogendoerfer
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Bogendoerfer @ 1999-03-27 0:39 UTC (permalink / raw)
To: William J. Earl; +Cc: linux
On Fri, Mar 26, 1999 at 03:49:32PM -0800, William J. Earl wrote:
> #define EXTIO_HPC3_BUSERR 0x0010
> #define EXTIO_SG_STAT_0 0x0001
ahh, another register I didn't know.
> HPC3_BUSERR means that the HPC3 got a bus error reading from memory.
> The driver is probably broken and giving bad commands to the HPC3.
> You should be able to find the error address in the GIO_ERR_ADDR register:
I've checked the MC registers cstat, gstat, the HPC3 registers intstat,
instat.bug, bus error and the extio register. All of them are zero. Any
other idea ?
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~1999-03-27 0:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-03-26 23:23 Help needed to solve SCSI problem Thomas Bogendoerfer
1999-03-26 23:49 ` William J. Earl
1999-03-27 0:39 ` Thomas Bogendoerfer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.