Re: panic: mb_dtor_mbuf: M_EXT set
On Mon, 23 Jan 2006 17:50:25 +0300 Gleb Smirnoff <[EMAIL PROTECTED]> wrote: > On Mon, Jan 23, 2006 at 04:44:53PM +0200, Ion-Mihai Tetcu wrote: > I> > Probably you hit another incorrect KASSERT in kern_mbuf.c. I have > I> > removed it some time after the first one. Since X was starting at > I> > this moment you couldn't be dropped into debugger, and so the > I> > box was rebooting. > I> > I> I don't know if I understand you right, but starting a bare X and > I> playing around for a while then typing startkde resulted in a > I> reset. > > When panic happens and you have X on the screen, the kernel can't > switch to syscons. It dumps core if you have KDB_UNATTENDED in > kernel, in other case it just reboots. I don't have KDB_UNATTENDED but on this machine the in the last week I got an automatic dump (on a "kmem_map too small" while running an RC1 kernel) and then the reboot and I was under X (kde); I remember I had to wait and watch the HDD led w/o being able to do anything else. -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" Without freedom of choice there is no creativity. -- Kirk, "The return of the Archons", stardate 3157.4 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Mon, Jan 23, 2006 at 04:44:53PM +0200, Ion-Mihai Tetcu wrote: I> > Probably you hit another incorrect KASSERT in kern_mbuf.c. I have I> > removed it some time after the first one. Since X was starting at I> > this moment you couldn't be dropped into debugger, and so the box was I> > rebooting. I> I> I don't know if I understand you right, but starting a bare X and I> playing around for a while then typing startkde resulted in a reset. When panic happens and you have X on the screen, the kernel can't switch to syscons. It dumps core if you have KDB_UNATTENDED in kernel, in other case it just reboots. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Mon, 23 Jan 2006 17:39:56 +0300 Gleb Smirnoff <[EMAIL PROTECTED]> wrote: > On Mon, Jan 23, 2006 at 04:35:07PM +0200, Ion-Mihai Tetcu wrote: > I> > On Mon, Jan 23, 2006 at 04:27:09PM +0200, Ion-Mihai Tetcu wrote: > I> > I> > On Sun, Jan 22, 2006 at 11:58:54PM +0200, Ion-Mihai Tetcu > I> > I> > wrote: > I> > I> > I> > On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff > I> > I> > I> > wrote: > I> > I> > I> > > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb > I> > I> > I> > > Smirnoff wrote: > I> > I> > I> > > T> This should be fixed in src/sys/kern_mbuf.c, > I> > I> > I> > > T> rev. 1.9.2.3 > I> > I> > I> > > > I> > I> > I> > > And another bogus panic is removed in 1.9.2.4 > I> > I> > I> > > > I> > I> > I> > > I> > I> > I> > The kernel is working again, thanks! > I> > I> > I> > I> > I> > I> It's working in regard of vr0, thank you. However now my > I> > I> > I> computer resets w/o anything logged when starting kde; > I> > I> > I> if I only startx it doesn't happen (without exec startkde > I> > I> > I> in .xinitrc); I commented out any fancy options like dri > I> > I> > I> with no effect and it also happen if I kldunload > I> > I> > I> snd_via8233 before starting kde. > I> > I> > I> > I> > I> > I> This is with 1.9.2.3 (cvsupped around 21 to 22 midnight; > I> > I> > I> it didn't happen with sources from 19. > I> > I> > > I> > I> > Bad news. Can you do a binary search and find commit that > I> > I> > makes this regression? > I> > I> > I> > I> FreeBSD 6.0-STABLE #1: Mon Jan 23 00:45:10 EET 2006 > I> > I> works:) > I> > > I> > So upgrading once more did help you? > I> > I> So it seem. I am using ULE, I have no problem with the new kernel > I> with either UL or 4BSD. I didn't test the "bad" kernel with 4BSD, > I> but I could do it if you like. > > Probably you hit another incorrect KASSERT in kern_mbuf.c. I have > removed it some time after the first one. Since X was starting at > this moment you couldn't be dropped into debugger, and so the box was > rebooting. I don't know if I understand you right, but starting a bare X and playing around for a while then typing startkde resulted in a reset. -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" Ferengi Rule of Acquisition #168: Whisper your way to success. -- ST:DS9, "Treachery, Faith, and the Great River" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Mon, Jan 23, 2006 at 04:35:07PM +0200, Ion-Mihai Tetcu wrote: I> > On Mon, Jan 23, 2006 at 04:27:09PM +0200, Ion-Mihai Tetcu wrote: I> > I> > On Sun, Jan 22, 2006 at 11:58:54PM +0200, Ion-Mihai Tetcu wrote: I> > I> > I> > On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff I> > I> > I> > wrote: I> > I> > I> > > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff I> > I> > I> > > wrote: I> > I> > I> > > T> This should be fixed in src/sys/kern_mbuf.c, rev. I> > I> > I> > > T> 1.9.2.3 I> > I> > I> > > I> > I> > I> > > And another bogus panic is removed in 1.9.2.4 I> > I> > I> > > I> > I> > I> > I> > I> > I> > The kernel is working again, thanks! I> > I> > I> I> > I> > I> It's working in regard of vr0, thank you. However now my I> > I> > I> computer resets w/o anything logged when starting kde; if I I> > I> > I> only startx it doesn't happen (without exec startkde I> > I> > I> in .xinitrc); I commented out any fancy options like dri with I> > I> > I> no effect and it also happen if I kldunload snd_via8233 I> > I> > I> before starting kde. I> > I> > I> I> > I> > I> This is with 1.9.2.3 (cvsupped around 21 to 22 midnight; it I> > I> > I> didn't happen with sources from 19. I> > I> > I> > I> > Bad news. Can you do a binary search and find commit that makes I> > I> > this regression? I> > I> I> > I> FreeBSD 6.0-STABLE #1: Mon Jan 23 00:45:10 EET 2006 works:) I> > I> > So upgrading once more did help you? I> I> So it seem. I am using ULE, I have no problem with the new kernel with I> either UL or 4BSD. I didn't test the "bad" kernel with 4BSD, but I I> could do it if you like. Probably you hit another incorrect KASSERT in kern_mbuf.c. I have removed it some time after the first one. Since X was starting at this moment you couldn't be dropped into debugger, and so the box was rebooting. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Mon, 23 Jan 2006 11:05:25 +0300 Gleb Smirnoff <[EMAIL PROTECTED]> wrote: > On Sun, Jan 22, 2006 at 11:58:54PM +0200, Ion-Mihai Tetcu wrote: > I> > On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff wrote: > I> > > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff wrote: > I> > > T> This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 > I> > > > I> > > And another bogus panic is removed in 1.9.2.4 > I> > > > I> > > I> > The kernel is working again, thanks! > I> > I> It's working in regard of vr0, thank you. However now my computer > I> resets w/o anything logged when starting kde; if I only startx it > I> doesn't happen (without exec startkde in .xinitrc); I commented > I> out any fancy options like dri with no effect and it also happen > I> if I kldunload snd_via8233 before starting kde. > I> > I> This is with 1.9.2.3 (cvsupped around 21 to 22 midnight; it didn't > I> happen with sources from 19. > > Bad news. Can you do a binary search and find commit that makes this > regression? FreeBSD 6.0-STABLE #1: Mon Jan 23 00:45:10 EET 2006 works:) -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #113: Root nameservers are out of sync ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Mon, 23 Jan 2006 17:31:47 +0300 Gleb Smirnoff <[EMAIL PROTECTED]> wrote: > On Mon, Jan 23, 2006 at 04:27:09PM +0200, Ion-Mihai Tetcu wrote: > I> > On Sun, Jan 22, 2006 at 11:58:54PM +0200, Ion-Mihai Tetcu wrote: > I> > I> > On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff > I> > I> > wrote: > I> > I> > > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff > I> > I> > > wrote: > I> > I> > > T> This should be fixed in src/sys/kern_mbuf.c, rev. > I> > I> > > T> 1.9.2.3 > I> > I> > > > I> > I> > > And another bogus panic is removed in 1.9.2.4 > I> > I> > > > I> > I> > > I> > I> > The kernel is working again, thanks! > I> > I> > I> > I> It's working in regard of vr0, thank you. However now my > I> > I> computer resets w/o anything logged when starting kde; if I > I> > I> only startx it doesn't happen (without exec startkde > I> > I> in .xinitrc); I commented out any fancy options like dri with > I> > I> no effect and it also happen if I kldunload snd_via8233 > I> > I> before starting kde. > I> > I> > I> > I> This is with 1.9.2.3 (cvsupped around 21 to 22 midnight; it > I> > I> didn't happen with sources from 19. > I> > > I> > Bad news. Can you do a binary search and find commit that makes > I> > this regression? > I> > I> FreeBSD 6.0-STABLE #1: Mon Jan 23 00:45:10 EET 2006 works:) > > So upgrading once more did help you? So it seem. I am using ULE, I have no problem with the new kernel with either UL or 4BSD. I didn't test the "bad" kernel with 4BSD, but I could do it if you like. -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #336: the xy axis in the trackball is coordinated with the summer solstice ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Mon, Jan 23, 2006 at 04:27:09PM +0200, Ion-Mihai Tetcu wrote: I> > On Sun, Jan 22, 2006 at 11:58:54PM +0200, Ion-Mihai Tetcu wrote: I> > I> > On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff wrote: I> > I> > > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff wrote: I> > I> > > T> This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 I> > I> > > I> > I> > > And another bogus panic is removed in 1.9.2.4 I> > I> > > I> > I> > I> > I> > The kernel is working again, thanks! I> > I> I> > I> It's working in regard of vr0, thank you. However now my computer I> > I> resets w/o anything logged when starting kde; if I only startx it I> > I> doesn't happen (without exec startkde in .xinitrc); I commented I> > I> out any fancy options like dri with no effect and it also happen I> > I> if I kldunload snd_via8233 before starting kde. I> > I> I> > I> This is with 1.9.2.3 (cvsupped around 21 to 22 midnight; it didn't I> > I> happen with sources from 19. I> > I> > Bad news. Can you do a binary search and find commit that makes this I> > regression? I> I> FreeBSD 6.0-STABLE #1: Mon Jan 23 00:45:10 EET 2006 works:) So upgrading once more did help you? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Sun, Jan 22, 2006 at 11:58:54PM +0200, Ion-Mihai Tetcu wrote: I> > On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff wrote: I> > > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff wrote: I> > > T> This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 I> > > I> > > And another bogus panic is removed in 1.9.2.4 I> > > I> > I> > The kernel is working again, thanks! I> I> It's working in regard of vr0, thank you. However now my computer I> resets w/o anything logged when starting kde; if I only startx it I> doesn't happen (without exec startkde in .xinitrc); I commented out any I> fancy options like dri with no effect and it also happen if I kldunload I> snd_via8233 before starting kde. I> I> This is with 1.9.2.3 (cvsupped around 21 to 22 midnight; it didn't I> happen with sources from 19. Bad news. Can you do a binary search and find commit that makes this regression? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Sun, 22 Jan 2006 15:16:24 +0100 Christian Brueffer <[EMAIL PROTECTED]> wrote: > On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff wrote: > > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff wrote: > > T> This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 > > > > And another bogus panic is removed in 1.9.2.4 > > > > The kernel is working again, thanks! It's working in regard of vr0, thank you. However now my computer resets w/o anything logged when starting kde; if I only startx it doesn't happen (without exec startkde in .xinitrc); I commented out any fancy options like dri with no effect and it also happen if I kldunload snd_via8233 before starting kde. This is with 1.9.2.3 (cvsupped around 21 to 22 midnight; it didn't happen with sources from 19. -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #153: Big to little endian conversion error ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff wrote: > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff wrote: > T> This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 > > And another bogus panic is removed in 1.9.2.4 > The kernel is working again, thanks! - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp0q3IKlKZS6.pgp Description: PGP signature
Re: panic: mb_dtor_mbuf: M_EXT set
On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff wrote: T> This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 And another bogus panic is removed in 1.9.2.4 -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic: mb_dtor_mbuf: M_EXT set
Hi, got the following panic at boot after an update to RELENG_6 from about 22:00 CET on an i386 SMP system. As this is fully repdoducible, I can provide more info if needed. panic: mb_dtor_mbuf: M_EXT set cpuid = 0 KDB: enter: panic [thread pid 230 tid 100073 ] Stopped at kdb_enter+0x30: leave db> tr Tracing pid 230 tid 100073 td 0xc3621300 kdb_enter(c07c0f49,0,c07bf27a,d7769a78,c3621300) at kdb_enter+0x30 panic(c07bf27a,c079477c,c07c285c,1,c374f000) at panic+0x14e mb_dtor_mbuf(c374f000,100,0,956,0) at mb_dtor_mbuf+0x4a uma_zfree_arg(c1050b40,c374f000,0) at uma_zfree_arg+0x2f mb_free_ext(c374f000,0,0,0,d7769b18) at mb_free_ext+0x19a m_freem(c374f000,0,c09623ca,5cc,c3401400) at m_freem+0x29 sf_stop(c33eb680,1,c09623ca,4c7,4ba) at sf_stop+0x125 sf_init_locked(c33eb74c,0,c09623ca,4ba,c3401400) at sf_init_locked+0x4d sf_init(c33eb700,c083b840,1,8020690c,c3737b00) at sf_init+0x39 ether_ioctl(c3401400,8020690c,c3737b00,529,0) at ether_ioctl+0x67 sf_ioctl(c3401400,8020690c,c3737b00,c3737b7c,1) at sf_ioctl+0x10c in_ifinit(c3401400,c3737b00,c363d150,0,1) at in_ifinit+0x208 in_control(c373c858,8040691a,c363d140,c3401400,c3621300) at in_control+0x986 ifioctl(c373c858,8040691a,c363d140,c3621300,2) at ifioctl+0x1cd soo_ioctl(c3697990,8040691a,c363d140,c3306780,c3621300) at soo_ioctl+0x3ef ioctl(c3621300,d7769d04,c,41d,3) at ioctl+0x45d syscall(3b,3b,3b,8058ba0,1) at syscall+0x2c0 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x2814d287, esp = 0xbfbfe5fc, ebp = 0xbfbfee68 --- db> - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp8EmAW4E3hq.pgp Description: PGP signature
6-STABLE from 19: panic: mb_dtor_mbuf: M_EXT set
Hi,
On ifconfig vr0 up I get each time a the panic bellow; last good kernel
I have is from Dec 31 and if_vr hasn't been touched since November.
# kgdb /usr/obj/usr/src/sys/IT6_U/kernel.debug /usr/crash/vmcore.4
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
[ ... ]
vr0: port 0xe400-0xe4ff mem
0xe3004000-0xe30040ff irq 23 at device 18.0 on pci0
vr0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xe400
miibus0: on vr0
ukphy0: on miibus0
ukphy0: OUI 0x004063, model 0x0032, rev. 10
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: bpf attached
vr0: Ethernet address: 00:0f:ea:0a:96:11
ioapic0: routing intpin 23 (PCI IRQ 23) to cluster 0
vr0: [MPSAFE]
pci1: driver added
found-> vendor=0x1002, dev=0x4966, revid=0x01
bus=1, slot=0, func=0
class=03-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0087, statreg=0x02b0, cachelnsz=8 (dwords)
lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns)
intpin=a, irq=16
powerspec 2 supports D0 D1 D2 D3 current D0
pci1:0:0: reprobing on driver added
<118>#
<118>vr0: flags=8802 mtu 1500
<118> ether 00:0f:ea:0a:96:11
<118> media: Ethernet autoselect (none)
<118> status: no carrier
<118>#
<118>vr0: flags=8802 mtu 1500
<118> ether 00:0f:ea:0a:96:11
<118> media: Ethernet autoselect (none)
<118> status: no carrier
<118>#
panic: mb_dtor_mbuf: M_EXT set
KDB: stack backtrace:
panic(c066952c,c0650ac0,c1035048,c4d44300,e5049b14) at panic+0x13a
mb_dtor_pack(c4d44300,100,0,956,c10383c0) at mb_dtor_pack
uma_zfree_arg(c104de80,c4d44300,0,c4da7934) at uma_zfree_arg+0x36a
mb_free_ext(c4d44300,c4c01400,c4da7000,c4da7000,e5049b74) at mb_free_ext+0x8f
m_freem(c4d44300,0,c52e460c,67c,c4da7950) at m_freem+0x27
vr_stop(c4d9ce80,1,c52e460c,59e,c4da7950) at vr_stop+0xca
vr_init_locked(c4da7950,8,c52e460c,625,0) at vr_init_locked+0x53
vr_ioctl(c4c01400,80206910,c51a8ca0,c04ceb72,c070aee0) at vr_ioctl+0x17f
ifhwioctl(c51a8ca0,c4b6b320,c51a8ca0,20,0) at ifhwioctl+0x5c5
ifioctl(c4e789bc,80206910,c51a8ca0,c4b6b320,2) at ifioctl+0x78
soo_ioctl(c4d9a6c0,80206910,c51a8ca0,c4a9fd80,c4b6b320) at soo_ioctl+0x2e8
ioctl(c4b6b320,e5049d04,c,41d,3) at ioctl+0x118
syscall(3b,3b,3b,3,1) at syscall+0x13d
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281579a7, esp = 0xbfbfe58c, ebp
= 0xbfbfe5d8 ---
KDB: enter: panic
panic: from debugger
Uptime: 17m48s
Dumping 1023 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847
831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527
511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207
191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt full
#0 doadump () at pcpu.h:165
No locals.
#1 0xc04d8606 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
_ep = (struct eventhandler_entry *) 0x0
_el = (struct eventhandler_list *) 0xc4d31680
first_buf_printf = 1
#2 0xc04d80d7 in panic (fmt=0xc065d2b6 "from debugger") at
/usr/src/sys/kern/kern_shutdown.c:555
bootopt = 260
newpanic = 0
buf = "mb_dtor_mbuf: M_EXT set", '\0'
#3 0xc0444592 in db_panic (addr=-1068544094, have_addr=0, count=-1,
modif=0xe5049928 "") at /usr/src/sys/ddb/db_command.c:438
No locals.
#4 0xc0444b10 in db_command_loop () at /usr/src/sys/ddb/db_command.c:350
No locals.
#5 0xc0446934 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:221
jb = {{_jb = {-452683308, -452683336, -452683256, -994659552, 0,
-1069258453, -452683124, -1, -1066911948, 672496039, -452683256, -1068543056}}}
prev_jb = (void *) 0x0
bkpt = 0
#6 0xc04f5432 in kdb_trap (type=0, code=0, tf=0xe5049a5c) at
/usr/src/sys/kern/subr_kdb.c:473
handled = -452683172
#7 0xc0635767 in trap (frame=
{tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = 256, tf_esi = 1, tf_ebp =
-452683100, tf_isp = -452683128, tf_ebx = 1, tf_edx = 1, tf_ecx = -108832,
tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1068544094, tf_cs = 32,
tf_eflags = 662, tf_esp = -1067004259, tf_ss = -1067012681})
at /usr/src/sys/i386/i386/trap.c:593
p = (struct proc *) 0xc4d99c48
