>Number:         26383
>Category:       port-alpha
>Synopsis:       "panic: fpsave ipi didn't" on alpha SMP
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    port-alpha-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 20 22:14:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Greg A. Woods
>Release:        NetBSD 1.6.2_STABLE
>Organization:
Planix, Inc.; Toronto, Ontario; Canada
>Environment:
System: NetBSD 1.6.2_STABLE 
Architecture: alpha
Machine: alpha
>Description:

	NetBSD-1.6.2_STABLE running on a dual processor AS4000

	note: as you can see below, the reboot failed and a manual reset
	was necessary

	This all appears to be the same as the problem reported in the
	"Random panics with 2-0 on CS20" thread starting at:

		http://mail-index.netbsd.org/port-alpha/2004/05/28/0000.html

	other related threads:

		http://mail-index.netbsd.org/port-alpha/2002/11/10/0000.html
		http://mail-index.netbsd.org/port-alpha/2002/10/22/0001.html

	I don't see a related PR anywhere though, thus this one.

panic: fpsave ipi didn't
Stopped in pid 230 (ntpd) at    cpu_Debugger+0x4:       ret     zero,(ra)
db{1}> where
cpu_Debugger() at cpu_Debugger+0x4
panic() at panic+0x160
fpusave_proc() at fpusave_proc+0x2fc
sendsig() at sendsig+0x150
postsig() at postsig+0x1c8
syscall_plain() at syscall_plain+0x238
XentSys() at XentSys+0x5c
--- syscall (4) ---
--- user mode ---
db{1}> show reg
v0                 0x6
t0          0xfffffc00006c2290  db_onpanic
t1                 0x1
t2          0xfffffc005fff0000
t3                   0
t4          0xfffffc0000608c6a  fmt.162+0x1068
t5               0x3e9  rn+0x3c9
t6                 0x1
t7          0xfffffc00007c89a0  cycles_per_usec
s0          0xfffffe003292fac8
s1          0xfffffc0000000008
s2          0xfffffc00007b4d20  msgbufp
s3          0xfffffc00006c30e4  msgbufenabled
s4               0x100  rn+0xe0
s5                0x20  rn
s6          0xfffffc0000695efd  msgperiod.210+0xac5
a0                   0
a1                 0x1
a2                 0x5
a3                 0x8  rettmp
a4                 0x3
a5                 0x8  rettmp
t8                   0
t9          0xfffffc00005ba864  microtime+0xc4
t10         0x134f14b7ede64
t11         0x17d174f6
ra          0xfffffc000045ba20  panic+0x160
t12         0xfffffc00005cc3e0  cpu_Debugger
at          0xfffffc00006c30cc  sched_whichqs
gp          0xfffffc00006b2dd8  special_symbols+0x8080
sp          0xfffffe003292fa48
pc          0xfffffc00005cc3e4  cpu_Debugger+0x4
ps                   0
ai          0x17d174f6
pv          0xfffffc00005cc3e0  cpu_Debugger
cpu_Debugger+0x4:       ret     zero,(ra)
db{1}> reboot
syncing disks... ^]^]rcm

RCM>status

Firmware Rev: V1.1
Escape Sequence: ^]^]RCM
Remote Access: DISABLE
Alerts: DISABLE
Alert Pending: NO
Temp (C): 42.0
RCM Power Control: ON
External Power: OFF
Server Power: ON

RCM>reset

Focus returned to COM port



>How-To-Repeat:

	unknown (it's only happened once so far)

	(two mozilla-gtk2 processes were running at the time, plus
	named, ntpd, and various xterms, ssh2d, ssh2 clients, cron,
	inetd, nfsd, mountd, rpcbind, rpc.lockd, rpc.statd, syslogd,
	smail, shells, emacs, gettys, etc.)

>Fix:

	unknown

>Release-Note:
>Audit-Trail:
>Unformatted: