From owner-freebsd-i386@FreeBSD.ORG Fri Jun 4 13:33:13 2004 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C16C16A4CE for ; Fri, 4 Jun 2004 13:33:13 -0700 (PDT) Received: from web14522.mail.yahoo.com (web14522.mail.yahoo.com [216.136.224.51]) by mx1.FreeBSD.org (Postfix) with SMTP id 10CBA43D48 for ; Fri, 4 Jun 2004 13:33:13 -0700 (PDT) (envelope-from eclipsetyperx@yahoo.com) Message-ID: <20040604203255.23343.qmail@web14522.mail.yahoo.com> Received: from [66.213.45.28] by web14522.mail.yahoo.com via HTTP; Fri, 04 Jun 2004 13:32:55 PDT Date: Fri, 4 Jun 2004 13:32:55 -0700 (PDT) From: Digital Node To: freebsd-i386@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: panic: lockmgr: locking against myself X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 20:33:13 -0000 Hello, I came across this bug last night, I am running 5.2.1 released on a dell laptop (p3 650, 128mb ram, 10gb hd, 440bx chipset (Stay tuned for dmesg)). The machine was compiling fine and when i came back it was rebooted. When rebooted it again (i had the install cd in the cdrom drive) it booted up and gave me my login, I logged in and started recompiling gnome2, after about 1 min I started compiling openssl as well. and about 30 second after that I got this Kernel Panic: Panic: lockmgr: locking against myself Syncinig disks, buffers remaining... panic: ffs_copyonwrite: recursive call so I rebooted it and tryed again and about 5 mins into gnome2 compiling again it did it again. and on the 3rd attempt it had hosed a directory in the port tree where make (or I) could delete it, at this point I dropped to single user mode and ran fsck on the drive ( /usr ) and it found about 100 soft errors, but on the folder I was haveing trouble deleteing it was giving me error no "." and no ".." so i had it fix it and it worked fine after. I'm pretty sure that this stems from running fsck in the background after a faulty stop, my guess is that there should be some kind of lock on lock manager so it can catch before it's going too lock itself and block the process till it's free, but I do not know the full curimstances so I'm leaving to u guys/gals. Below is my dmesg, lspci -v, and a sample of my blood dmesg: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2.1-RELEASE #0: Wed Jun 2 13:56:45 EDT 2004 root@evil.tier1.vpn:/usr/src/sys/i386/compile/EVIL Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a52000. Preloaded elf module "/boot/kernel/vesa.ko" at 0xc0a521cc. Preloaded elf module "/boot/kernel/snd_maestro3.ko" at 0xc0a52278. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0a5232c. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a523d8. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (648.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 134066176 (127 MB) avail memory = 120582144 (114 MB) Pentium Pro MTRR support enabled VESA: v2.0, 8128k memory, flags:0x0, mode table:0xc09d4c62 (1000022) VESA: ATI MACH64 npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fbd20 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 7 INTD is routed to irq 11 pcib0: slot 8 INTA is routed to irq 5 agp0: mem 0xf4000000-0xf7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: at device 0.0 (no driver attached) cbb0: at device 3.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib0: slot 3 INTA is routed to irq 11 cbb0: [MPSAFE] cbb1: at device 3.1 on pci0 cardbus1: on cbb1 pcib0: slot 3 INTA is routed to irq 11 cbb1: [MPSAFE] isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x860-0x86f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] uhci0: port 0xdce0-0xdcff irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) pcm0: port 0xd800-0xd8ff mem 0xfaffe000-0xfaffffff irq 5 at device 8.0 on pci0 pcm0: atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: