Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Jun 2005 15:36:23 +0200
From:      Thierry Herbelot <thierry@herbelot.com>
To:        freebsd-current@freebsd.org
Cc:        Mike Silbersack <silby@silby.com>
Subject:   Re: new panics
Message-ID:  <200506251536.25959.thierry@herbelot.com>
In-Reply-To: <200506242331.47205.thierry@herbelot.com>
References:  <20050624145923.P83036@odysseus.silby.com> <20050624155218.D83036@odysseus.silby.com> <200506242331.47205.thierry@herbelot.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Le Friday 24 June 2005 23:31, Thierry Herbelot a écrit :
> Le Friday 24 June 2005 22:56, Mike Silbersack a écrit :
> > That makes some sense, because we may not be getting around to the
> > modified memory until we hit some heavy memory usage.  Also, one
> > backtrace showed the panic happening when uma_reclaim was called from the
> > vm pageout daemon.  Sounds like I should throw something in to
> > (optionally) call uma_reclaim on a regular basis so that we might catch
> > this more quickly.
>

here's the latest panic (recent sources + your patch applied) : what do I do 
next ?

	TfH

Starting background file system checks in 60 seconds.

Sat Jun 25 15:01:26 CEST 2005

FreeBSD/i386 (multi-cur.herbelot.nom) (ttyd0)

login: Jun 25 15:01:36 multi-cur su: thierry.herbelot to root on /dev/ttyp0
This memory last freed by: 0xc15f5100
panic: Memory modified after free 0xc15cd600(256) val=c15f5100 @ 0xc15cd600

cpuid = 0
KDB: enter: panic
[thread pid 520 tid 100089 ]
Stopped at      kdb_enter+0x2b: nop
db> where
Tracing pid 520 tid 100089 td 0xc15a5780
kdb_enter(c084e195) at kdb_enter+0x2b
panic(c0868abb,c15cd600,100,c15f5100,c15cd600) at panic+0x127
trash_ctor(c15cd600,100,cc92f96c,1,c104a9d8) at trash_ctor+0x3f
mb_ctor_mbuf(c15cd600,100,cc92f96c,1) at mb_ctor_mbuf+0x18
uma_zalloc_arg(c104a9a0,cc92f96c,1) at uma_zalloc_arg+0x10f
m_defrag(c1758e00,1,c13b5cb0,1,c08622c6,580) at m_defrag+0x97
rl_encap(c13b5800,c1758e00) at rl_encap+0x2b
rl_start_locked(c13ccc00,c13b5cb0,0,c08622c6,5ab) at rl_start_locked+0x1ef
rl_start(c13ccc00) at rl_start+0x28
if_start(c13ccc00) at if_start+0x7b
ether_output_frame(c13ccc00,c1758e00,0,0,0) at ether_output_frame+0x1d9
ether_output(c13ccc00,c1758e00,cc92faa8,c15cf840,c1593400) at 
ether_output+0x3b4
ip_output(c1758e00,0,cc92faa4,0,0) at ip_output+0x6fc
tcp_output(c1661564,0,1,c165fbf4,0) at tcp_output+0xf8e
tcp_usr_send(c15c1914,0,c1758a00,0,0) at tcp_usr_send+0x1b3
sosend(c15c1914,0,cc92fc78,c1758a00,0) at sosend+0x5e3
soo_write(c15167e0,cc92fc78,c1740d80,0,c15a5780) at soo_write+0x46
dofilewrite(c15a5780,c15167e0,3,807f000,50) at dofilewrite+0xa8
write(c15a5780,cc92fd04,3,9a,286) at write+0x39
syscall(3b,bfbf003b,bfbf003b,80788e0,806fe08) at syscall+0x22f
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (4, FreeBSD ELF32, write), eip = 0x282c1e63, esp = 0xbfbfe4ac, ebp 
= 0xbfbfe4c8 ---
db>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506251536.25959.thierry>