On Wednesday 10 June 2009 9:19:13 am Robert wrote: > On Mon, 8 Jun 2009 10:45:39 -0400 > John Baldwin <j...@freebsd.org> wrote: > > > On Saturday 06 June 2009 10:14:31 am Robert wrote: > > > 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 > > > r...@vaio.shasta204.local:/usr/obj/usr/src/sys/VESA i386 > > > > > > The bits from pciconf > > > > > > atap...@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 r...@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. > > > > The last screen of the dmesg output would be helpful. > > > I have installed 7.2 on the laptop because it would panic whenever > going into multiuser. I would prefer to be on stable. > > Here is dmesg.boot. I hope that is what you wanted.
Hmm, can you get the stack trace from the dump that you have? I'm curious which device driver is triggering the panic. -- John Baldwin _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
