On 16.03.2011 19:21, Mike Tancsa wrote:
> A new one it seems. On the console,
I have one with full crashdump too.
Crashdump and other files are available on request.
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public Lice
Something new in my logs yesterday:
Mar 1 16:06:38 k-45-pc-1 kernel: Accessing freed node node: ID [2e5c7a]: type
'tee', 0 hooks, flags 0x9, 0 refs, mpd11699-vlan373-781-lt:
Mar 1 16:06:38 k-45-pc-1 kernel: Last active @
/home/src/sys/netgraph/ng_base.c, line 2257
Mar 1 16:06:38 k-45-pc-1 ker
> On 14.01.2011 18:46, Mike Tancsa wrote:
> I also have very loaded mpd/PPPoE servers that panic all the time:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/153255
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/153671
I've just got yet another panic on mpd5 box after about 30 days of upt
On Wed, Feb 16, 2011 at 03:04:09PM +0600, Eugene Grosbein wrote:
E> On 16.02.2011 14:46, Gleb Smirnoff wrote:
E> > On Wed, Feb 16, 2011 at 10:13:59AM +0600, Eugene Grosbein wrote:
E> > E> I run AMD64 with 4GB of memory, lots of memory is free and
E> > E> I still get panics often, sometimes two in a
On 16.02.2011 14:46, Gleb Smirnoff wrote:
> On Wed, Feb 16, 2011 at 10:13:59AM +0600, Eugene Grosbein wrote:
> E> I run AMD64 with 4GB of memory, lots of memory is free and
> E> I still get panics often, sometimes two in a couple of hours.
> E> It does not seem memory exhaustion to me. It seems as
On 1/31/2011 12:10 PM, Julian Elischer wrote:
> On 1/31/11 8:58 AM, Julian Elischer wrote:
>> On 1/31/11 7:13 AM, Przemyslaw Frasunek wrote:
And in this one, can you please show *hook->hk_peer ?
>>> (kgdb) print *hook->hk_peer
>>> $2 = {
>>>hk_name = "\b\000\000\000
>>> \000\000\000\004\00
On 1/31/11 8:58 AM, Julian Elischer wrote:
On 1/31/11 7:13 AM, Przemyslaw Frasunek wrote:
And in this one, can you please show *hook->hk_peer ?
(kgdb) print *hook->hk_peer
$2 = {
hk_name = "\b\000\000\000
\000\000\000\004\000\000\000\001\000\000\000ŐRí\003\003ö\0248cmd4\000\000\000",
hk_p
On 1/31/11 7:13 AM, Przemyslaw Frasunek wrote:
And in this one, can you please show *hook->hk_peer ?
(kgdb) print *hook->hk_peer
$2 = {
hk_name = "\b\000\000\000
\000\000\000\004\000\000\000\001\000\000\000ŐRí\003\003ö\0248cmd4\000\000\000",
hk_private = 0x0, hk_flags = 0, hk_refs = 0,
hk_
> And in this one, can you please show *hook->hk_peer ?
(kgdb) print *hook->hk_peer
$2 = {
hk_name = "\b\000\000\000
\000\000\000\004\000\000\000\001\000\000\000ŐRí\003\003ö\0248cmd4\000\000\000",
hk_private = 0x0, hk_flags = 0, hk_refs = 0,
hk_type = 0, hk_peer = 0x0, hk_node = 0x0, hk_hooks
> (kgdb) print *ng_name_hash[116].lh_first
It looks like this one is corrupted:
(kgdb) print
*ng_name_hash[116].lh_first.nd_nodes.le_next.nd_nodes.le_next.nd_nodes.le_next.nd_nodes.le_next
$19 = {nd_name = "ng258", '\0' , nd_type = 0xc61871a0,
nd_flags = 0, nd_refs = 1, nd_numhooks = 0, nd_priv
On Mon, Jan 31, 2011 at 02:40:55PM +0100, Przemyslaw Frasunek wrote:
P> > In this dump, can we seek for where did 0x74 came from? Can you look at
P> > ng_name_hash[hash]?
P>
P> (kgdb) print hash
P> No symbol "hash" in current context.
P> (kgdb) info all
P> eax0xff9a -102
P> e
> In this dump, can we seek for where did 0x74 came from? Can you look at
> ng_name_hash[hash]?
(kgdb) print hash
No symbol "hash" in current context.
(kgdb) info all
eax0xff9a -102
ecx0xe7ce6895 -405903211
edx0xff9a -102
ebx
On Fri, Jan 14, 2011 at 10:05:31AM +0100, Przemyslaw Frasunek wrote:
P> Hello,
P>
P> I'm using mpd 5.5 on three PPPoE routers, each servicing about 300 PPPoE
P> concurrent sessions. Routers are based on Intel SR1630GP hardware platforms
and
P> runs FreeBSD 7.3-RELEASE.
P>
P> I'm experiencing sta
On 1/17/2011 11:14 AM, Eugene Grosbein wrote:
> On 17.01.2011 17:41, Mike Tancsa wrote:
>
I also have stability issues on RELENG_8.
http://www.freebsd.org/cgi/query-pr.cgi?pr=153497
>>>
>>> Do you change net.isr.direct from default 1 to 0 for your box?
>>
>> No, I leave it at 1
>>
>
Thanks,
I will give those values a try!
---Mike
On 1/17/2011 11:14 AM, Eugene Grosbein wrote:
> On 17.01.2011 17:41, Mike Tancsa wrote:
>
I also have stability issues on RELENG_8.
http://www.freebsd.org/cgi/query-pr.cgi?pr=153497
>>>
>>> Do you change net.isr.direc
On 17.01.2011 17:41, Mike Tancsa wrote:
>>> I also have stability issues on RELENG_8.
>>>
>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=153497
>>
>> Do you change net.isr.direct from default 1 to 0 for your box?
>
> No, I leave it at 1
>
> ---Mike
I was experiencing some instability with
On 1/17/2011 5:48 AM, Eugene Grosbein wrote:
> On 14.01.2011 18:46, Mike Tancsa wrote:
>
>> I also have stability issues on RELENG_8.
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=153497
>
> Do you change net.isr.direct from default 1 to 0 for your box?
No, I leave it at 1
---Mike
>
On 14.01.2011 18:46, Mike Tancsa wrote:
> I also have stability issues on RELENG_8.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=153497
Do you change net.isr.direct from default 1 to 0 for your box?
___
freebsd-net@freebsd.org mailing list
http://lis
On 14.01.2011 18:46, Mike Tancsa wrote:
>> I'm using mpd 5.5 on three PPPoE routers, each servicing about 300 PPPoE
>> concurrent sessions. Routers are based on Intel SR1630GP hardware platforms
>> and
>> runs FreeBSD 7.3-RELEASE.
>>
>> I'm experiencing stability issues related to Netgraph. None
On 1/14/2011 4:05 AM, Przemyslaw Frasunek wrote:
> Hello,
>
> I'm using mpd 5.5 on three PPPoE routers, each servicing about 300 PPPoE
> concurrent sessions. Routers are based on Intel SR1630GP hardware platforms
> and
> runs FreeBSD 7.3-RELEASE.
>
> I'm experiencing stability issues related to
Hello,
I'm using mpd 5.5 on three PPPoE routers, each servicing about 300 PPPoE
concurrent sessions. Routers are based on Intel SR1630GP hardware platforms and
runs FreeBSD 7.3-RELEASE.
I'm experiencing stability issues related to Netgraph. None of above routers can
survive more than 20-30 days o
21 matches
Mail list logo
