From: Guillaume Nault <g.nault@alphalink.fr>
To: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
Cc: Dan Williams <dcbw@redhat.com>, Netdev <netdev@vger.kernel.org>,
ebiederm@xmission.com, davem@davemloft.net, simon@farnz.org.uk,
develop@kristov.de
Subject: Re: 4.1.0, kernel panic, pppoe_release
Date: Fri, 25 Sep 2015 21:02:49 +0200 [thread overview]
Message-ID: <20150925190249.GA2962@alphalink.fr> (raw)
In-Reply-To: <3e1192bd3125fd5054c1417bce869505@visp.net.lb>
On Fri, Sep 25, 2015 at 06:02:42PM +0300, Denys Fedoryshchenko wrote:
> On 2015-09-25 17:38, Guillaume Nault wrote:
> >On Tue, Sep 22, 2015 at 04:47:48AM +0300, Denys Fedoryshchenko wrote:
> >>Hi,
> >>Sorry for late reply, was not able to push new kernel on pppoes without
> >>permissions (it's production servers), just got OK.
> >>
> >>I am testing patch on another pppoe server with 9k users, for ~3 days,
> >>seems
> >>fine. I will test today
> >>also on server that was experiencing crashes within 1 day.
> >>
> >Thanks for the feedback. I'm about to submit a fix. Should I add a
> >Tested-by tag for you?
> On one of servers i got same crash as before, within hours. 9k users server
> also crashed after while, so it seems it doesn't help.
> I will do some more tests tomorrow.
Ok, this must be a different bug then. Do you have a trace of a crash
with the patched kernel?
prev parent reply other threads:[~2015-09-25 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 10:57 4.1.0, kernel panic, pppoe_release Denys Fedoryshchenko
2015-07-17 9:24 ` Denys Fedoryshchenko
2015-07-17 15:36 ` Dan Williams
2015-07-17 18:16 ` Denys Fedoryshchenko
2015-09-10 15:56 ` Guillaume Nault
2015-09-22 1:47 ` Denys Fedoryshchenko
2015-09-25 14:38 ` Guillaume Nault
2015-09-25 15:02 ` Denys Fedoryshchenko
2015-09-25 19:02 ` Guillaume Nault [this message]
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=20150925190249.GA2962@alphalink.fr \
--to=g.nault@alphalink.fr \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=develop@kristov.de \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=nuclearcat@nuclearcat.com \
--cc=simon@farnz.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).