possible race on HEAD?
Peter Avalos
pavalos at theshell.com
Fri May 11 16:41:07 PDT 2007
On Fri, May 11, 2007 at 12:10:57PM -0700, Matthew Dillon wrote:
>
> : _lwkt_gettokref
> :mp_lock =3D 00000000; cpuid =3D 0; lapic.id =3D 00000000
> :boot() called on cpu#0
> :Uptime: 1d19h17m16s
> :
> :And then it hard locked on me...had to power cycle.
> :
> :--Peter
>
> Ok, we have two debugging choices for when this happens again:
>
> (1) Debug it while the system is live. If you want to give me
> access when it happens again I can send you my ssh key and
> I can try to debug the problem while the system is live.
>
Sure, next time it happens, I'll let you know. You need normal user access,
root, or console?
> (2) Disable filesystem syncing before doing the panic.
>
> sysctl kern.sync_on_panic=0
>
> (or 'w sync_on_panic 0' from ddb> before panicing)
>
> Hopefully this will allow the panic to get to the kernel core
> dump.
Yeh, I don't know why that disappeared out of my sysctl.conf. Anyway, it's
back in.
>
> Meanwhile I'll start running cvsup on my test box to try to reproduce
> the problem.
>
I think it was a combination of the daily scripts and cvsup cron that gummed
something up. I'm having no problems running cvsup now.
--Peter
Attachment:
pgp00002.pgp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgp00002.pgp
Type: application/octet-stream
Size: 189 bytes
Desc: "Description: PGP signature"
URL: <http://lists.dragonflybsd.org/pipermail/kernel/attachments/20070511/7b060c7d/attachment-0020.obj>
More information about the Kernel
mailing list