From owner-freebsd-current@FreeBSD.ORG Mon Jun 14 17:07:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4F9B16A4CE for ; Mon, 14 Jun 2004 17:07:53 +0000 (GMT) Received: from smtp18.wxs.nl (smtp18.wxs.nl [195.121.6.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65FA043D1F for ; Mon, 14 Jun 2004 17:07:53 +0000 (GMT) (envelope-from ronald-freebsd7@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210]) by smtp18.wxs.nlSMTP id <0HZB008C76935W@smtp18.wxs.nl> for freebsd-current@freebsd.org; Mon, 14 Jun 2004 19:07:52 +0200 (CEST) Received: (qmail 981 invoked from network); Mon, 14 Jun 2004 17:07:50 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Mon, 14 Jun 2004 17:07:50 +0000 Received: (qmail 1123 invoked from network); Mon, 14 Jun 2004 17:07:43 +0000 Received: from unknown (HELO guido.thuis.klop.ws) (192.168.0.2) by 192.168.0.16 with SMTP; Mon, 14 Jun 2004 17:07:43 +0000 Received: (qmail 5198 invoked from network); Mon, 14 Jun 2004 17:07:48 +0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; Mon, 14 Jun 2004 17:07:48 +0000 Date: Mon, 14 Jun 2004 19:07:47 +0200 From: Ronald Klop To: FreeBSD-current Message-id: MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_JGqdW23vYFpKEyhnKfk+pQ)" User-Agent: Opera M2/7.50 (FreeBSD, build 673) Subject: panic: ffs_valloc: dup alloc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 17:07:53 -0000 --Boundary_(ID_JGqdW23vYFpKEyhnKfk+pQ) Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT Hello, I'm getting this panic 'panic: ffs_valloc: dup alloc'. It happens on -CURRENT, since quite some time. It happens when doing an rsync from a remote server to my secondary disk. (ad2,master on ata1), there is no slave on this controller. And it always happens, so it is very repeatable. Is this probably a hardware failure? Or software? $ uname -a FreeBSD henk.thuis.klop.ws 5.2-CURRENT FreeBSD 5.2-CURRENT #24: Mon Jun 14 00:25:19 CEST 2004 root@henk.thuis.klop.ws:/usr/obj/usr/src/sys/HENK i386 A backtrace of the kernel core dump is in the attached gdb.txt. My dmesg is also attached. Can I provide more info? Greetings, Ronald. PS: Searched the archives and google, but didn't find anything usefull yet. -- Ronald Klop Amsterdam, The Netherlands --Boundary_(ID_JGqdW23vYFpKEyhnKfk+pQ) Content-type: application/octet-stream; name=dmesg.boot Content-transfer-encoding: 8bit Content-disposition: attachment; filename=dmesg.boot inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:50:8b:a3:d9:44 fxp0: [GIANT-LOCKED] pcm0: port 0x2060-0x207f irq 11 at device 14.0 on pci0 pcm0: Reserved 0x20 bytes for rid 0x10 type 4 at 0x2060 pcm0: pcm0: [GIANT-LOCKED] isab0: at device 20.0 on pci0 isa0: on isab0 atapci0: port 0x2040-0x204f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 20.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x2040 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: at 0x1f0 irq 14 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x2020-0x203f irq 11 at device 20.2 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x2020 uhci0: [GIANT-LOCKED] 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 intpm0: port 0xfc00-0xfc0f irq 9 at device 20.3 on pci0 intpm0: Reserved 0x10 bytes for rid 0x90 type 4 at 0xfc00 intpm0: I/O mapped fc00 intpm0: intr IRQ 9 enabled revision 0 intpm0: [GIANT-LOCKED] intsmb0: on intpm0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped f800 acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 ppc0 port 0x778-0x77d,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 lpt0: on ppbus0 lpt0: Interrupt-driven port sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: