On Mon, 16 May 2005 08:47:21 +0200
Laurens Vets <laurens@daemon.be> wrote:

> Michael wrote:
> > Hello,
> >=20
> >=20
> >>I have just installed NetBSD 2.0.2 on a SparcStation 20 with Dual=20
> >>HyperSparc 180 Mhz CPU's.  However, when I try to untar the=20
> >>pkgsrc.tar.gz tarball, my SS20 goes to the ok prompt with a "Level 15=20
> >>Interrupt".  Does anybody has any idea what might be going on?  Where=20
> >>might the problem be?  I'm new to NetBSD.
> >=20
> >=20
> > Ouch. A level 15 interrupt can mean different things, almost all are
> > rather unpleasant and point at hardware problems. So...
> > - does the machine run properly under Solaris?
> > - are the memory modules seated properly?
> > - are the CPU modules seated properly?
> > - does anything get too hot?
> > - does it work with only one CPU?
> > - did the SS20 come with these CPUs? If not - is the firmware new
> > enough?
>=20
> Seems my cg14 is broken :(  Removed it from the system and NetBSD is=20
> running rock solid for a couple of days now.  Thanks!

I can easily crash my SS20/cg14 running X, and get=20
either a
"Level 15 interrupt"
either a
"Watchdog Reset"
either a kernel crash with log.
I may have enough time to send_pr that with the full log before tomorrow.
Tested configurations :
* SS20 + 2x HM125-1024 + cg14 running netbsd 2.0RC5 UP or SMP (both crash)
* SS20 + 2x SM71 + cg14 running netbsd 2.0.2 UP or SMP (both crash)=20
* another SS20 (not mine) + 2x HM150-512 + cg6 running netbsd 2.0RC5 SMP
All 3 configurations are able to compile stuff for days without any error, =
but I can
crash them in about 2 or 3 seconds under X.
Way to reproduce it : you need evilwm (a very minimalistic wm), I haven't
tested that under other wms.
1/ .xinitrc with "evilwm" inside
2/ launch X
3/ use CTRL+ALT+ENTER to launch an xterm
4/ use ALT-2 (not the one in the numeric keypad) to go to workspace 2
5/ use CTRL+ALT+ENTER to launch an xterm
6/ swap repeatedly between workspace 1 and workspace 2 with ALT-1 and ALT-2
Now, if both xterms were overlapping AND the mouse was over both of them,
I get a crash in a few seconds. If the mouse is only over one of them, no c=
rash.

Maybe that already helps. I'll try to copy/paste the kernel crash log manua=
lly
before tomorrow.

Cheers

Fran=E7ois

PS : again, sorry for my post yesterday.=20