From owner-freebsd-current Mon Apr 24 04:36:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA01654 for current-outgoing; Mon, 24 Apr 1995 04:36:10 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id EAA01648 ; Mon, 24 Apr 1995 04:36:09 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: dyson@freefall.cdrom.com cc: current@freefall.cdrom.com Subject: mmap panics still Date: Mon, 24 Apr 1995 04:36:09 -0700 Message-ID: <1647.798723369@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk Hi Satoshi jsut tried the same program on thud, and it still panic'd the kernel, although the message was different this time. Apr 24 02:47:57 thud savecore: reboot after panic: lockholder (%d) != 0 thud# kgdb ./kernel Reading symbol data from /d/local/src/sys/compile/THUDG/kernel...done. (kgdb) core-file /var/crash/vmcore.2 IdlePTD 1df000 panic: lockholder (%d) != 0 current pcb at 1d0ad0 Reading in symbols for ../../i386/i386/machdep.c...done. (kgdb) bt #0 boot (arghowto=260) (../../i386/i386/machdep.c line 869) #1 0xf0117bc5 in panic (...) #2 0xf0101311 in db_panic (...) #3 0xf01011fa in db_command (...) #4 0xf0101379 in db_command_loop (...) #5 0xf0103e3c in db_trap (...) #6 0xf01a3d0e in kdb_trap (...) #7 0xf01ab348 in trap (...) #8 0xf01a45d1 in exception:calltrap () #9 0xf0117bbf in panic (...) #10 0xf0192686 in ufs_lock (...) #11 0xf01a214d in vnode_pager_lock (...) #12 0xf0195ee4 in vm_fault (...) #13 0xf01ab5c7 in trap_pfault (...) #14 0xf01ab2c7 in trap (...) #15 0xf01a45d1 in exception:calltrap () #16 0xf0185535 in ffs_read (...) #17 0xf01329d2 in vn_read (...) #18 0xf0118d83 in read (...) #19 0xf01abcc3 in syscall (...) Any ideas? This was with a kernel compiled AFTER John's fixes to mmap() Gary