From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: Bug, kernel panic, NULL dereference , cleanup_once / icmp_route_lookup.clone.19.clone / nat , 2.6.39-rc7-git11
Date: Wed, 18 May 2011 15:46:07 +0300 [thread overview]
Message-ID: <4ae96506c000a4b3c8f78ccef836deaf@visp.net.lb> (raw)
In-Reply-To: <1305719047.2991.4.camel@edumazet-laptop>
On Wed, 18 May 2011 13:44:07 +0200, Eric Dumazet wrote:
> Le mercredi 18 mai 2011 à 12:05 +0200, Eric Dumazet a écrit :
>> Le mercredi 18 mai 2011 à 12:53 +0300, Denys Fedoryshchenko a écrit
>> :
>>
>> > Yes, i will try. I should enable SLUB debugging only, or also
>> anything
>> > else?
>> >
>> > But possible it will take time to reproduce bug, seems it is
>> occuring
>> > rare. With 2.6.39 release i will rollout update to few hundreds
>> PPPoE's,
>> > maybe it will increase chances to get information.
>> >
>>
>> I would try both : slub_debug=ZFP slub_nomerge
>>
>> or maybe only slub_debug=ZFPU
>>
>> Thanks !
>>
>
> Hmm, do you have both ipv6/ipv4 trafic on your machine by any chance
> ?
It is NAS, has ipv6 enabled recently (i am preparing for ipv6), but
ipv6 is not routed anywhere, maybe just automatically addresses
appearing on interfaces, including the one looking to customer subnet.
ppp is ipv4 only.
next prev parent reply other threads:[~2011-05-18 12:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 22:16 Bug, kernel panic, NULL dereference , cleanup_once / icmp_route_lookup.clone.19.clone / nat , 2.6.39-rc7-git11 Denys Fedoryshchenko
2011-05-18 9:27 ` Denys Fedoryshchenko
2011-05-18 9:37 ` Eric Dumazet
2011-05-18 9:53 ` Denys Fedoryshchenko
2011-05-18 10:05 ` Eric Dumazet
2011-05-18 11:44 ` Eric Dumazet
2011-05-18 12:46 ` Denys Fedoryshchenko [this message]
2011-05-18 15:52 ` Eric Dumazet
2011-05-18 19:29 ` Eric Dumazet
2011-05-19 5:19 ` Eric Dumazet
2011-05-19 6:11 ` Denys Fedoryshchenko
2011-05-19 6:30 ` Eric Dumazet
2011-05-19 6:39 ` Denys Fedoryshchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ae96506c000a4b3c8f78ccef836deaf@visp.net.lb \
--to=denys@visp.net.lb \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox