From: Matthew Harrell <lists-sender-14a37a@bittwiddlers.com>
To: Christoph Hellwig <hch@infradead.org>,
Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.0-test-x] Kernel Oops and pppd segfault
Date: Fri, 5 Sep 2003 16:24:34 -0400 [thread overview]
Message-ID: <20030905202430.GA3425@bittwiddlers.com> (raw)
In-Reply-To: <20030905084126.A15120@infradead.org>
> This should fix the oops, but the failure is still strange.
>
> do you already have a ppp device in /dev before loading the module?
Yeah, I posted this problem a few weeks ago but never had an answer. I
worked around it. I do have a /dev/ppp already in there but get the
exact same oops when attempting to run pppd without my patch and while using
devfs
--
Matthew Harrell Never raise your hand to your
Bit Twiddlers, Inc. children - it leaves your
mharrell@bittwiddlers.com midsection unprotected.
prev parent reply other threads:[~2003-09-05 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 21:30 Florian Zimmermann
2003-09-04 21:38 ` Andrew Morton
2003-09-05 6:34 ` Florian Zimmermann
2003-09-09 20:37 ` Florian Zimmermann
2003-09-05 7:41 ` Christoph Hellwig
2003-09-05 13:42 ` Florian Zimmermann
2003-09-05 20:24 ` Matthew Harrell [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=20030905202430.GA3425@bittwiddlers.com \
--to=lists-sender-14a37a@bittwiddlers.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mharrell-dated-1063225476.b6bd27@bittwiddlers.com \
/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
Powered by JetHome