From owner-freebsd-stable@FreeBSD.ORG Sat Jun 6 14:43:08 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BF32106564A for ; Sat, 6 Jun 2009 14:43:08 +0000 (UTC) (envelope-from traveling08@cox.net) Received: from fed1rmpop108.cox.net (fed1rmpop108.cox.net [68.230.241.12]) by mx1.freebsd.org (Postfix) with ESMTP id 3179E8FC1A for ; Sat, 6 Jun 2009 14:43:07 +0000 (UTC) (envelope-from traveling08@cox.net) Received: from fed1rmimpo01.cox.net ([70.169.32.71]) by fed1rmmtao105.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090606141436.ZQND20430.fed1rmmtao105.cox.net@fed1rmimpo01.cox.net> for ; Sat, 6 Jun 2009 10:14:36 -0400 Received: from vaio ([98.176.33.70]) by fed1rmimpo01.cox.net with bizsmtp id 0eEc1c00C1WnGw203eEcm4; Sat, 06 Jun 2009 10:14:37 -0400 X-VR-Score: -140.00 X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=MgEkKS8qx2k2w5gca6MA:9 a=0ZMySGETfU5Hlin10moA:7 a=67NZBWmUkk7u6mNzv3psOHY4y2QA:4 X-CM-Score: 0.00 Date: Sat, 6 Jun 2009 07:14:31 -0700 From: Robert To: freebsd-stable@freebsd.org Message-ID: <20090606071431.092609ce@vaio> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.2; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Panic resource_list_alloc 7.2 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2009 14:43:08 -0000 Greetings This problem seems the same as this one from May of this year http://lists.freebsd.org/pipermail/freebsd-stable/2009-May/050088.html This happens on an older HP laptop. It was running on 7.1 prerelease fine and then I updated to 7.2 Stable yesterday. FreeBSD hp.shasta204.local 7.2-STABLE FreeBSD 7.2-STABLE #0: Fri Jun 5 11:47:29 PDT 2009 root@vaio.shasta204.local:/usr/obj/usr/src/sys/VESA i386 The bits from pciconf atapci0@pci0:0:7:1: class=0x010180 card=0x00000000 chip=0x71118086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB/EB/MB PIIX4/4E/4M IDE Controller' class = mass storage subclass = ATA The date of ata-chipset.c -rw-r--r-- 1 root wheel 188823 May 22 02:21 ata-chipset.c The chipset is found in the above file ata_intel_ident(device_t dev) { struct ata_pci_controller *ctlr = device_get_softc(dev); static struct ata_chip_id ids[] = {{ ATA_I82371FB, 0, 0, 2, ATA_WDMA2, "PIIX" }, { ATA_I82371SB, 0, 0, 2, ATA_WDMA2, "PIIX3" }, { ATA_I82371AB, 0, 0, 2, ATA_UDMA2, "PIIX4" }, ^^^^^^^ { ATA_I82443MX, 0, 0, 2, ATA_UDMA2, "PIIX4" }, I can include the dump if needed but I am not at this time to shorten the email. But here is the panic. Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 68939776B (65 MB) Blocksize: 512 Dumptime: Sat Jun 6 05:40:52 2009 Hostname: hp.shasta204.local Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.2-STABLE #0: Fri Jun 5 11:47:29 PDT 2009 root@vaio.shasta204.local:/usr/obj/usr/src/sys/VESA Panic String: resource_list_alloc: resource entry is busy Dump Parity: 3285399556 Bounds: 1 Dump Status: good Any help would be greatly appreciated. Robert