Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Aug 2011 10:15:44 +0200
From:      Attilio Rao <attilio@freebsd.org>
To:        Andriy Gapon <avg@freebsd.org>
Cc:        freebsd-stable@freebsd.org, Steven Hartland <killing@multiplay.co.uk>
Subject:   Re: debugging frequent kernel panics on 8.2-RELEASE
Message-ID:  <CAJ-FndAq2ASHzg_%2B9S__x=vTAgzHowMrv1DFSbXwroX27PF36A@mail.gmail.com>
In-Reply-To: <4E4380C0.7070908@FreeBSD.org>
References:  <47F0D04ADF034695BC8B0AC166553371@multiplay.co.uk> <A71C3ACF01EC4D36871E49805C1A5321@multiplay.co.uk> <4E4380C0.7070908@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
I'd really point the finger to faulty hw.

Please run all the necessary diagnostic tools for catching it.

Attilio

2011/8/11 Andriy Gapon <avg@freebsd.org>:
> on 10/08/2011 18:35 Steven Hartland said the following:
>> Fatal double fault
>> rip =3D 0xffffffff8052f6f1
>> rsp =3D 0xffffff86ce600fb0
>> rbp =3D 0xffffff86ce601210
>> cpuid =3D 0; apic id =3D 00
>> panic: double fault
>> cpuid =3D 0
>> KDB: stack backtrace:
>> #0 0xffffffff803af91e at kdb_backtrace+0x5e
>> #1 0xffffffff8037d817 at panic+0x187
>> #2 0xffffffff80574316 at dblfault_handler+0x96
>> #3 0xffffffff8055d06d at Xdblfault+0xad
> [snip]
>> #0 =C2=A0sched_switch (td=3D0xffffffff80830bc0, newtd=3D0xffffff000a73f8=
c0, flags=3DVariable
>> "flags" is not available.)
>> =C2=A0 =C2=A0at /usr/src/sys/kern/sched_ule.c:1858
>> 1858 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0cpuid =3D PCPU_GET(cpuid);
>> (kgdb)
>> #0 =C2=A0sched_switch (td=3D0xffffffff80830bc0, newtd=3D0xffffff000a73f8=
c0, flags=3DVariable
>> "flags" is not available.)
>> =C2=A0 =C2=A0at /usr/src/sys/kern/sched_ule.c:1858
>> #1 =C2=A00xffffffff80385c86 in mi_switch (flags=3D260, newtd=3D0x0)
>> =C2=A0 =C2=A0at /usr/src/sys/kern/kern_synch.c:449
>> #2 =C2=A00xffffffff803b92d2 in sleepq_timedwait (wchan=3D0xffffffff80830=
760, pri=3D68)
>> =C2=A0 =C2=A0at /usr/src/sys/kern/subr_sleepqueue.c:644
>> #3 =C2=A00xffffffff803861e1 in _sleep (ident=3D0xffffffff80830760, lock=
=3D0x0,
>> =C2=A0 =C2=A0priority=3DVariable "priority" is not available.
>> ) at /usr/src/sys/kern/kern_synch.c:230
>> #4 =C2=A00xffffffff80532c29 in scheduler (dummy=3DVariable "dummy" is no=
t available.
>> ) at /usr/src/sys/vm/vm_glue.c:807
>> #5 =C2=A00xffffffff80335d67 in mi_startup () at /usr/src/sys/kern/init_m=
ain.c:254
>> #6 =C2=A00xffffffff8016efac in btext () at /usr/src/sys/amd64/amd64/loco=
re.S:81
>> #7 =C2=A00xffffffff808556e0 in sleepq_chains ()
>> #8 =C2=A00xffffffff8083b1e0 in cpu_top ()
>> #9 =C2=A00x0000000000000000 in ?? ()
>> #10 0xffffffff80830bc0 in proc0 ()
>> #11 0xffffffff80ba4b90 in ?? ()
>> #12 0xffffffff80ba4b38 in ?? ()
>> #13 0xffffff000a73f8c0 in ?? ()
>> #14 0xffffffff803a2cc9 in sched_switch (td=3D0x0, newtd=3D0x0, flags=3DV=
ariable "flags"
>> is not available.
>> )
>> =C2=A0 =C2=A0at /usr/src/sys/kern/sched_ule.c:1852
>> Previous frame inner to this frame (corrupt stack?)
>> (kgdb)
>
> Looks like this is just the first thread in the kernel.
> Perhaps 'thread apply all bt' could help to find the culprit.
>
> --
> Andriy Gapon
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>



--=20
Peace can only be achieved by understanding - A. Einstein



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-FndAq2ASHzg_%2B9S__x=vTAgzHowMrv1DFSbXwroX27PF36A>