:Thomas Nikolajsen <thomas.nikolajsen@mail.dk> added the comment:
:
:It is full build of HEAD from June 27th.
:Updated source & rebuild today, but it didn't change panic.
:I am going to make a virgin checkout & full build tomorrow; to triple check ;-)
:
:No problem with reboot, halt, or shutdown -o from serial console.
:No problem running shutdown -p from ssh login.
:Panic is seen every time shutdown without -o is used on serial console.
:
: -thomas

I'm going to need a kernel core dump. If I do
'shutdown -h how "shutting down"' on a serial console on my test box it
shuts down ok.

I will note that there are definitely some shutdown issues in HEAD
at the moment. These issues are primarily related to assertions that
have been added to validate the shutdown code (meaning that the problems
have always existed, but now we actually detect them).

I did try to narrow down when I do/don't see crash:
- no crash from single user (boot -s)
- I tried disabling services:
reboot after rename /etc/rc.conf & no nfs-mounts: still crash.
- GENERIC do crash

I did check /usr/src: no problem.
(comparing to virgin checkout from primary cvs-src)

:Thomas Nikolajsen <thomas.nikolajsen@mail.dk> added the comment:
:
:New core dump uploaded to
:crash/VOP_STDCLOSE-BAD_OPENCOUNT/2
:
: -thomas
:PS: I will be off for two weeks.

Ok. Hmm. email me your /etc/fstab and any manual commands you are
running to set up NFS and MFS mounts. You have some NFS and MFS mounts
which could be contributing to the bug, I need to try to set up something
similar to try to reproduce the problem.

panic at shutdown; only seen once in recent time. no comconsole this
time.
other host than earlier (don't use old host much in meantime),
now on other SMP (no APIC_IO) host, atom330, 2 cores, 2 HTT on each.

crash dump is rather big, 600MB, worth uploading to leaf?
(host has 2GB RAM, didn't limit RAM use by hw.physmem (yet))
(I have complete dump, with kernel and all modules in use).

Um, there is a comment in spec_close() that says that s_ttyvp may
have v_opencount==0 (if the tty was revoked). But then vop_stdclose()
is called unconditionally at the end of spec_close(). It seems to me
that it should be called if and only if v_opencount > 0.

Thomas,

Could you check in the crash dump the value of p->p_session->s_ttyvp
in the innermost call to spec_close() please?