Date: Mon, 1 Feb 2010 13:44:51 -0800 From: Daniel Ballenger <dan@svwh.net> To: freebsd-stable@freebsd.org Subject: Kernel Panic on Freebsd 8-RELEASE Message-ID: <DF8E2B90-E92D-48A2-BAC8-176F43247B74@svwh.net>
next in thread | raw e-mail | index | archive | help
--Apple-Mail-4--1009316906 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi all, A recent HLDS update is causing my machine to kernel panic. Here is a copy of the kernel dump: #0 sched_switch (td=3D0xffffffff80be7600, newtd=3D0xffffff00014f6720, = flags=3DVariable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1864 1864 cpuid =3D PCPU_GET(cpuid); (kgdb)=20 (kgdb) bt #0 sched_switch (td=3D0xffffffff80be7600, newtd=3D0xffffff00014f6720, = flags=3DVariable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1864 #1 0xffffffff805879bf in mi_switch (flags=3D260, newtd=3D0x0) at = /usr/src/sys/kern/kern_synch.c:449 #2 0xffffffff805b94a2 in sleepq_timedwait (wchan=3D0xffffffff80be71a0, = pri=3D68) at /usr/src/sys/kern/subr_sleepqueue.c:623 #3 0xffffffff80587f38 in _sleep (ident=3D0xffffffff80be71a0, lock=3D0x0, = priority=3DVariable "priority" is not available. ) at /usr/src/sys/kern/kern_synch.c:230 #4 0xffffffff807c7faa in scheduler (dummy=3DVariable "dummy" is not = available. ) at /usr/src/sys/vm/vm_glue.c:779 #5 0xffffffff8053a859 in mi_startup () at = /usr/src/sys/kern/init_main.c:251 #6 0xffffffff8018a33c in btext () at = /usr/src/sys/amd64/amd64/locore.S:81 #7 0x0000000000e74000 in ?? () #8 0x0000000000000000 in ?? () #9 0x0000000000000000 in ?? () #10 0xffffffff80c0c710 in sleepq_chains () #11 0xffffffff80be7600 in proc0 () #12 0xffffffff80e52be0 in ?? () #13 0xffffffff80e52b98 in ?? () #14 0xffffff00014f6720 in ?? () #15 0xffffffff805a2bd8 in sched_switch (td=3D0x0, newtd=3D0x0, = flags=3DVariable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1858 Previous frame inner to this frame (corrupt stack?) (kgdb) uname -a: FreeBSD dl0009.sjc02.denetron.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: = Thu Jan 28 05:36:57 UTC 2010 = root@dl0009.sjc02.denetron.net:/usr/obj/usr/src/sys/GENERIC amd64 The message displayed to the console: =95 Unread portion of the kernel message buffer: =95 panic: tdsignal(): invalid signal 0 =95 cpuid =3D 2 =95 Uptime: 6m52s =95 Physical memory: 4073 MB t_j in the ##freebsd channel on freenode asked me to do this so I'll = include it incase it's some help: (kgdb) frame 0 #0 sched_switch (td=3D0xffffffff80be7600, newtd=3D0xffffff00014f6720, = flags=3DVariable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1864 1864 cpuid =3D PCPU_GET(cpuid); (kgdb) list 1859 /* 1860 * We may return from cpu_switch on a different = cpu. However, 1861 * we always return with td_lock pointing to the = current cpu's 1862 * run queue lock. 1863 */ 1864 cpuid =3D PCPU_GET(cpuid); 1865 tdq =3D TDQ_CPU(cpuid); 1866 lock_profile_obtain_lock_success( 1867 &TDQ_LOCKPTR(tdq)->lock_object, 0, 0, = __FILE__, __LINE__); 1868 #ifdef HWPMC_HOOKS The crash is repeatable (occurs everytime for me). I also confirmed = that another FreeBSD 8 machine I have ran into the same panic (also = amd64). I'm guessing this is a bug of some kind, if there's more information I = need to provide, just let me know. Thanks, Daniel= --Apple-Mail-4--1009316906--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DF8E2B90-E92D-48A2-BAC8-176F43247B74>