From: Mirko.Klemm@t-online.de (Mirko Klemm)
To: linux-kernel@vger.kernel.org
Subject: 2.4.0-test9 pppoe broken?
Date: Mon, 30 Oct 2000 20:33:06 +0100 [thread overview]
Message-ID: <00103020330603.00684@trabant> (raw)
Hi,
I just upgraded from test7 to test9, now the pppoe (to be precise, pppox on
which pppoe depends) module segfaults when loaded with modprobe the first
time, a second attempt causes lots of disk activity and eats up all processor
time, eventually locking me out of my system (no oops, though, so I guess
it's actually modprobe that crashes).
I use modutils 2.3.14, and I got pppox device nodes in my /dev on major 144
from a different pppox module, a third-party pppoe implementation that was
partly user and partly kernel based as opposed to the all-kernel 2.4.0
solution. As everything works fine with test7 I wonder what has changed in
test9. What could be wrong here? Any ideas?
Thanks,
Mirko
------------------------------------------------------
Mirko Klemm
Mirko.Klemm@t-online.de
GPG-Public Key at:
http://www.mutantenzoo.de/mklemm.asc
encrypted messages preferred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-10-30 19:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00103020330603.00684@trabant \
--to=mirko.klemm@t-online.de \
--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.