On Mon, 5 Jul 2004, eta wrote: > Got a panic on the new little server I'm testing for use at our school. > > panic: vm_page_t 0xc1c92660 phys_addr mismatch 0000000000b6d000 > 000000002bb6d405. > > Attached is some gdb and dmesg output. It's -current from 2004-06-25, > and I was in the middle of a gnome-upgrade.sh. The kernel config is > generic minus WITNESS plus COMPAT_LINUX. > > Anyone seen this? Unfortunately the backtrace is corrupted by the secondary panic. This might be bad memory, however; the pattern is kind of interesting. Can't say I've seen that on my dual Opteron, but I haven't built -current on it in a while. > > (And as I get ready to send this, it died during my gnome-upgrade.sh > again). > > --- > > dragon# gdb -k kernel.debug vmcore.0 > GNU gdb 5.2.1 (FreeBSD) > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-unknown-freebsd"... > panic: vm_page_t 0xc1c92660 phys_addr mismatch 0000000000b6d000 > 000000002bb6d405 > panic messages: > --- > panic: vm_page_t 0xc1c92660 phys_addr mismatch 0000000000b6d000 > 000000002bb6d405 > cpuid = 0; > Debugger("panic") > > syncing disks, buffers remaining... panic: _mtx_lock_sleep: recursed on > non-recursive mutex vm page queue mutex _at_ > /usr/src/sys/kern/vfs_bio.c:3452 -- Doug White | FreeBSD: The Power to Serve dwhite_at_gumbysoft.com | www.FreeBSD.orgReceived on Tue Jul 06 2004 - 20:54:39 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:00 UTC