From: Keith Owens <kaos@ocs.com.au>
To: Mark Ellis <mark.uzumati@virgin.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS on bringing down ppp
Date: Fri, 24 Nov 2000 23:49:05 +1100 [thread overview]
Message-ID: <2401.975070145@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 24 Nov 2000 10:55:39 -0000." <20001124105539.A18945@ElCapitan>
On Fri, 24 Nov 2000 10:55:39 +0000,
Mark Ellis <mark.uzumati@virgin.net> wrote:
>Hi all, consistently getting the following when pppd is terminated. Happens
>in 2.4.0-test11, fine in 2.4.0-test9, don't know about test10. Same happens
>for pppd 2.4.0b4 and 2.4.0, both recompiled for test11. Is this related to
>the modutils incompatability (modutils 2.3.19) ?
I don't think so. I cannot reproduce this oops on 2.4.0-test11 with
modutils 2.3.21, ppp 2.4.0. modutils 2.3.19 should be compatible with
kernel 2.4.0-test11, the incompatibility is between modutils <= 2.3.15
and kernel 2.4.0-test11.
It was difficult to find the right area of code, my compile with
egcs-2.91.66 and -march=i686 gives quite different Assembler, so take
this analysis with a pinch of salt. Is there any chance that you are
using the wrong compiler and/or compiler options?
The oops looks to be on line 102 of kmod.c
for (i = 0; i < current->files->max_fds; i++ ) {
current->files is NULL. That has nothing to do with modutils, rather
it points to an invalid or incomplete current context.
-
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/
next prev parent reply other threads:[~2000-11-24 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 10:55 OOPS on bringing down ppp Mark Ellis
2000-11-24 12:28 ` Andrew Morton
2000-11-24 14:04 ` Alan Cox
2000-11-26 21:00 ` Mark Ellis
2000-11-24 12:49 ` Keith Owens [this message]
2000-11-24 22:16 ` Marc Heckmann
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=2401.975070145@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.uzumati@virgin.net \
/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