Date: Wed, 10 Jun 2009 09:45:03 -0700 From: Robert <traveling08@cox.net> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: Panic resource_list_alloc 7.2 stable Message-ID: <20090610094503.104ffbb7@vaio> In-Reply-To: <200906101038.37028.jhb@freebsd.org> References: <20090606071431.092609ce@vaio> <200906081045.39497.jhb@freebsd.org> <20090610061913.04a97b6c@vaio> <200906101038.37028.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 10 Jun 2009 10:38:36 -0400 John Baldwin <jhb@freebsd.org> wrote: > On Wednesday 10 June 2009 9:19:13 am Robert wrote: > > On Mon, 8 Jun 2009 10:45:39 -0400 > > John Baldwin <jhb@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 > > > > <clip older message stuff> > > > > > 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. > (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc07e4b47 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc07e4e19 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc080d6f6 in resource_list_alloc (rl=0xc2630904, bus=0xc25bed80, child=0xc2494180, type=3, rid=0xd528a5b8, start=0, end=4294967295, count=1, flags=12290) at /usr/src/sys/kern/subr_bus.c:2739 #4 0xc06a2057 in pci_alloc_resource (dev=0xc25bed80, child=0xc2494180, type=3, rid=0xd528a5b8, start=0, end=4294967295, count=1, flags=12290) at /usr/src/sys/dev/pci/pci.c:3586 #5 0xc080d57c in bus_alloc_resource (dev=0xc2494180, type=3, rid=0xd528a5b8, start=0, end=4294967295, count=1, flags=12290) at bus_if.h:263 #6 0xc058ef4c in cardbus_parse_cis (cbdev=0xc25bed80, child=0xc2494180, callbacks=0xd528a9e4, argp=0xc2a65000) at /usr/src/sys/dev/cardbus/cardbus_cis.c:481 #7 0xc058f91c in cardbus_open (dev=0xc25ab400, oflags=1, devtype=8192, td=0xc2a91d80) at /usr/src/sys/dev/cardbus/cardbus_device.c:140 #8 0xc076f26a in devfs_open (ap=0xd528aa88) at /usr/src/sys/fs/devfs/devfs_vnops.c:903 #9 0xc0affad2 in VOP_OPEN_APV (vop=0xc0c4f840, a=0xd528aa88) at vnode_if.c:371 #10 0xc0873329 in vn_open_cred (ndp=0xd528ab7c, flagp=0xd528ac78, cmode=1, cred=0xc2ab3d00, fp=0xc2a4be40) at vnode_if.h:199 #11 0xc0873473 in vn_open (ndp=0xd528ab7c, flagp=0xd528ac78, cmode=1, fp=0xc2a4be40) at /usr/src/sys/kern/vfs_vnops.c:94 #12 0xc0870b7d in kern_open (td=0xc2a91d80, path=0xbfbfef32 <Address 0xbfbfef32 out of bounds>, pathseg=UIO_USERSPACE, flags=1, mode=1) at /usr/src/sys/kern/vfs_syscalls.c:1042 #13 0xc08710f0 in open (td=0xc2a91d80, uap=0xd528acfc) at /usr/src/sys/kern/vfs_syscalls.c:1009 #14 0xc0ae9405 in syscall (frame=0xd528ad38) at /usr/src/sys/i386/i386/trap.c:1090 #15 0xc0ace1e0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:255 #16 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) Thanks again Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090610094503.104ffbb7>