I think this happened with the 1.5.x tree as well. I put
a hardware reset (read a specific location) in the
reboot code. Sorry I'm not at home for the week -- so
I do not have access to the diffs.

By the way, netbooting works within the same subnet,
not over a router (bad firmware) along the way of Roland's
suggestion (I think, I recompiled netboot instead).

Fixes for stray interrupts with serial console have been
sent this list a while ago. Seems to be fixed in 1.5.3RC,
but without access to a system I'm not sure.

I the problems persist, I can post solutions next week.

Juergen Weiss	  | Universitaet Mainz, Zentrum fuer Datenverarbeitung,
weiss@uni-mainz.de| 55099 Mainz, Tel: +49(6131)39-26361, FAX: =
+49(6131)39-26407=20

> -----Original Message-----
> From: David Brownlee [mailto:abs@formula1.com]
> Sent: Sunday, June 02, 2002 4:48 PM
> To: port-alpha@netbsd.org
> Subject: Multia rebooting problems=20
>=20
>=20
> 	Trying to reboot a multia rnnng 1.6_BETA1 with serial=20
> console ends
> 	up with	a machine check - is ayone else seeing this?
>=20
> lead# reboot
> syncing disks... done
> rebooting...
>=20
> *** keyboard not plugged in...
> Keyboard error; using serial port terminal
>=20
> halted CPU 0
>=20
> halt code =3D 5
> HALT instruction executed
> PC =3D fffffc0000300118
> *** no timer interrupts on CPU 0 ***
>=20
> CPU 0 booting
>=20
>=20
> Unexpected Machine Check through vector 00000067
>=20
> IPRs:
> EXC_ADD:00000000001303A0  ICCSR:   0000000000000000  HIER:  =20
> 000000001FFFDC70
> HIRR:   0000000000001022  MM_CSR:  00000000000053A0 =20
> DC_STAT:0000000000000003
> DC_ADDR:00000007FFFFFFFF  ESR:     6FB0D8F900020000  EAR:   =20
> 2008000000000070
> STAT0:  0000013A0000013A  STAT1:   0000080000000800  VA:    =20
> 0000000000000000
> EXC_SUM:0000000000000000  BC_TAG:  0000000000000000
>=20
>=20
>=20
> --=20
> 		David/absolute		abs@formula1.com
>=20
>=20