As I reported to sparc@ a few days ago, when running the latest sparc64
kernel I got a panic. I sent all I knew how to in that post, and its
tagged on at the end of this, but I have a more general question.
I did my best to collect the requested information:
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu <#>' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
I ps and trace, easy. mach ddbcpu 1 (or indeed any other number, or
literal <#> ), not so good. Quoth the debugger, 'No such command'.
Is the instruction out of date? Is the command MIA? I don't know, but
perhaps someone else does.
If someone could at least tell me, its okay, you can just reboot, we
don't need anything else, that would be nice.
Also, if someone can tell me how to work out where to draw the line
between not cluttering up the bug tracker and making sure the right
people see things, that would be nifty too. I suspect I should have sent
this one as a bug.
Dave W
--
-------- Original Message --------
Subject: Panic on T1000 running 7/12/08 snapshot
Date: Mon, 08 Dec 2008 14:21:51 +0000
From: Dave Wilson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
As subject, was doing a cvs up of /usr/src from a cvs mirror on the
local machine (its my anoncvs/OS packages mirror), and it panic'd.
This is the third time its done this since I switched from -stable to
-current, each time with a later snap. I was hoping it was something
dumb I'd done in compiling from source, but this time it was before I'd
had a chance to build anything, so I know the kernel/binaries on the
system are as in the snapshot. I'm holding off on rebooting to get the
latest dmesg until someone can tell me what I should run at the ddb
prompt instead of mach ddbcpu 1, which doesn't seem to exist. There's a
dmesg from a week or so ago in my earlier thread to sparc@, if that's
any use.
SD
slash:~# panic: ipi_save_fpstate didn't
kdb breakpoint at 13fe5c0
Stopped at Debugger+0x4: nop
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu <#>' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{0}> trace
fpusave_proc(4001afaa4d0, 1, 4c2fc210, 1d, 7d8, 15180) at fpusave_proc+0x108
trap(4008511fed0, 20, 4bca6cc8, 4000f25b000, 1, 1) at trap+0x290
slowtrap(1dd, 7d8, 4c2fc210, 1d, 7d8, 15180) at slowtrap+0x1d0
end(ffffffffffffffff, ffffffffffffffff, ffffffffffffffff,
ffffffffffffffff, fff
fffffffffffff, ffffffffffffffff) at 0x4bca6c6c
ddb{0}> ps
PID PPID PGRP UID S FLAGS WAIT COMMAND
*25708 18048 18048 1003 7 0 cvs
4875 28119 28119 1003 3 0x2000000 biowait cvs
18048 8178 18048 1003 3 0x2004080 select cvs
8178 32290 32290 1003 3 0x2000180 select sshd
32290 29697 32290 0 3 0x2004080 netio sshd
28119 32684 28119 1003 3 0x2004080 select cvs
32684 15413 15413 1003 3 0x2000180 select sshd
15413 29697 15413 0 3 0x2004080 netio sshd
11407 2412 24565 0 3 0x2004082 select ssh
2412 24565 24565 0 3 0x2004082 piperd cvs
24565 2337 24565 0 3 0x2004082 pause sh
2337 24242 2337 0 3 0x2004082 pause ksh
24242 10989 24242 1000 3 0x2004082 pause ksh
10989 1283 1283 1000 3 0x2000180 select sshd
1283 29697 1283 0 3 0x2004180 netio sshd
10445 1 10445 0 3 0x2004082 ttyin ksh
26460 1 26460 0 3 0x2000080 select cron
29697 1 29697 0 3 0x2000080 select sshd
30301 19810 19810 67 3 0x2000180 netcon httpd
4388 19810 19810 67 3 0x2000180 netcon httpd
27229 19810 19810 67 3 0x2000180 netcon httpd
28864 19810 19810 67 3 0x2000180 netcon httpd
10139 19810 19810 67 3 0x2000180 netcon httpd
2946 1 2946 0 3 0x2000180 select inetd
19810 1 19810 67 3 0x2000180 select httpd
8250 1 8250 0 3 0x2040180 select sendmail
19941 744 12433 83 3 0x2000180 poll ntpd
744 12433 12433 83 3 0x2000180 poll ntpd
12433 1 12433 0 3 0x2000080 poll ntpd
25748 15103 15103 73 3 0x2000180 poll syslogd
15103 1 15103 0 3 0x2000088 netio syslogd
42 0 0 0 3 0x2100200 bored crypto
41 0 0 0 3 0x2100200 aiodoned aiodoned
40 0 0 0 3 0x2100200 syncer update
39 0 0 0 3 0x2100200 cleaner cleaner
38 0 0 0 3 0x100200 reaper reaper
37 0 0 0 3 0x2100200 pgdaemon pagedaemon
36 0 0 0 3 0x2100200 pftm pfpurge
35 0 0 0 7 0x100200 idle31
34 0 0 0 7 0x100200 idle30
33 0 0 0 7 0x100200 idle29
32 0 0 0 7 0x100200 idle28
31 0 0 0 7 0x100200 idle27
30 0 0 0 7 0x100200 idle26
29 0 0 0 7 0x100200 idle25
28 0 0 0 7 0x100200 idle24
27 0 0 0 7 0x100200 idle23
26 0 0 0 7 0x100200 idle22
25 0 0 0 7 0x100200 idle21
24 0 0 0 7 0x100200 idle20
23 0 0 0 7 0x100200 idle19
22 0 0 0 7 0x100200 idle18
21 0 0 0 7 0x100200 idle17
20 0 0 0 7 0x100200 idle16
19 0 0 0 7 0x100200 idle15
18 0 0 0 7 0x100200 idle14
17 0 0 0 7 0x100200 idle13
16 0 0 0 7 0x100200 idle12
15 0 0 0 7 0x100200 idle11
14 0 0 0 7 0x100200 idle10
13 0 0 0 7 0x100200 idle9
12 0 0 0 7 0x100200 idle8
11 0 0 0 7 0x100200 idle7
10 0 0 0 7 0x100200 idle6
9 0 0 0 7 0x100200 idle5
8 0 0 0 7 0x100200 idle4
7 0 0 0 7 0x100200 idle3
6 0 0 0 7 0x100200 idle2
5 0 0 0 7 0x100200 idle1
4 0 0 0 3 0x2100200 bored syswq
3 0 0 0 3 0x100200 idle0
2 0 0 0 3 0x2100200 kmalloc kmthread
1 0 1 0 3 0x2004080 wait init
0 -1 0 0 3 0x2080200 scheduler swapper
ddb{0}> mach ddbcpu 1
No such command
ddb{0}>
