On Sat, 6 Mar 2004, Christopher SEKIYA wrote:

> On Fri, Mar 05, 2004 at 07:04:08PM +0100, Florian St?hr wrote:
>
> > And HERE is the problem:
> >
> > root@diver [~] # panic: target init didn't set unimpl_intr
> > Stopped in pid 8730.1 (sh) at   0x8829b6e4:     jr      ra
> >                 bdslot: nop
> > db>
>
> This should never happen.  You are using an IP22 or IP24, right?  I think
> all of those interrupts are well-understood and handled.
>
> However ... the dummy interrupt handler should complain and continue, not
> panic.  Below is a patch that addresses this behavior.
>
> -- Chris
> 	GPG key FEB9DE7F (91AF 4534 4529 4BCC 31A5  938E 023E EEFB FEB9 DE7F)
>
> Index: machdep.c
> ===================================================================
> RCS file: /cvsroot/src/sys/arch/sgimips/sgimips/machdep.c,v
> retrieving revision 1.79
> diff -u -r1.79 machdep.c
> --- machdep.c	19 Jan 2004 03:26:14 -0000	1.79
> +++ machdep.c	6 Mar 2004 00:07:19 -0000
> @@ -755,9 +755,9 @@
>  }
>
>  static void
> -unimpl_intr(u_int32_t a, u_int32_t b, u_int32_t c, u_int32_t d)
> +unimpl_intr(u_int32_t status, u_int32_t cause, u_int32_t pc, u_int32_t ipending)
>  {
> -	panic("target init didn't set unimpl_intr");
> +	printf("spurious interrupt, ipending %x\n", ipending);
>  }
>
>  static unsigned long
>

Hi,

yep, it's Indigo2.

Thanks for the patch, I'll try as soon as I swapped the hds again (trying
1.6.2 stable on the other) next week.

Well, I just finished my other tests. Look at the post following in some
minutes "Re: mozille trouble again" (=mozilla :-(#$%!) I think I
discovered some other bug(s)...

Thanks for the patch!
Florian