From: Joel Soete <soete.joel@scarlet.be>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Help: major pppoe regression since 2.6.35 (panic on first ppp conection)?
Date: Mon, 20 Dec 2010 11:03:40 +0000 [thread overview]
Message-ID: <4D0F380C.6010902@scarlet.be> (raw)
In-Reply-To: <4D0C9BFA.4080003@scarlet.be>
On 12/18/2010 11:33 AM, Joel Soete wrote:
> Hello all,
>
[snip]
>
> As in general this kind of problem is quickly identified and solved, I
> do some more test with 2.6.36 and even 2.6.37-rc? releases, in smp or up
> config, with or without netfilter, with or without foreign nvidia
> graphical driver but this issue is still there for me?
>
[snip]
Hello,
Just a small update because I read that there is a pppoe fix in latest testing kernel 2.6.37-rc6 but unfortunately it
doesn't help me :<(.
Tx,
J.
PS: I also test kernels 32 and 64 bits without any success.
next prev parent reply other threads:[~2010-12-20 11:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 11:33 Help: major pppoe regression since 2.6.35 (panic on first ppp conection)? Joel Soete
2010-12-20 11:03 ` Joel Soete [this message]
2010-12-22 8:22 ` Andrew Morton
2010-12-22 11:00 ` Jarek Poplawski
2010-12-22 16:00 ` Joel Soete
2010-12-22 16:25 ` Eric Dumazet
2010-12-23 11:02 ` Joel Soete
2010-12-23 12:12 ` Eric Dumazet
2010-12-23 20:25 ` Jarek Poplawski
[not found] ` <4D148271.8030509@scarlet.be>
2010-12-24 15:13 ` Jarek Poplawski
2010-12-25 12:10 ` Jarek Poplawski
2010-12-25 13:51 ` Joel Soete
2010-12-25 15:12 ` [PATCH net-2.6] sundance: Fix oopses with corrupted skb_shared_info Jarek Poplawski
2010-12-25 17:31 ` [PATCH net-2.6] epic100: hamachi: yellowfin: Fix skb allocation size Jarek Poplawski
2010-12-25 17:39 ` [PATCH net-2.6 v2] " Jarek Poplawski
2010-12-26 3:42 ` David Miller
2010-12-26 3:42 ` [PATCH net-2.6] sundance: Fix oopses with corrupted skb_shared_info David Miller
2010-12-26 11:01 ` Jarek Poplawski
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=4D0F380C.6010902@scarlet.be \
--to=soete.joel@scarlet.be \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.