From: "Georg Nikodym" <georgn@somanetworks.com>
To: "Richard Purdie" <rpurdie@bigfoot.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: <BUG Report: kernel BUG at slab.c:1062! from pppd with speedtouch drivers and pppoatm>
Date: Wed, 11 Jul 2001 14:19:47 -0400 [thread overview]
Message-ID: <15180.39107.179401.666431@somanetworks.com> (raw)
In-Reply-To: <00c101c10a33$8a024920$0301a8c0@rpnet.com>
In-Reply-To: <00c101c10a33$8a024920$0301a8c0@rpnet.com>
>>>>> "RP" == Richard Purdie <rpurdie@bigfoot.com> writes:
>> > I'm trying to get Linux to work with an Alcatel Speedtouch ADSL
>> > USB
RP> modem.
>> > By executing the following script after boot up I get the BUG
>> > message
RP> after
>> > running pppd.
>>
>> Have you tried asking the author of the speedtouch driver about
>> this?
RP> I've sent him a copy of the bug report I submitted here. I'm
RP> still unsure of where the problem lies. My machine is being
RP> unpredictable even when the driver hasn't been loaded.
The BUG() invocation is a result of invalid flags being passed to
kmem_cache_grow().
The numeric values associated with things like GFP_ATOMIC changed in
2.4.6. Your problem is likely related to the use of modules built on
something other than the kernel you're running.
(I know this because I spent entirely too long debugging somebody's
code yesterday that thought it was a good idea to have his own copies
of the definitions of GFP_ATOMIC, et al.)
next prev parent reply other threads:[~2001-07-11 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 18:01 Richard Purdie
2001-07-11 18:19 ` Georg Nikodym [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-11 15:11 Richard Purdie
2001-07-11 15:37 ` dr john halewood
2001-07-11 15:55 ` Richard Purdie
2001-07-11 23:36 ` Richard Purdie
2001-07-11 23:51 ` Linus Torvalds
[not found] ` <200107112351.f6BNpa304221@penguin.transmeta.com>
2001-07-12 15:10 ` Richard Purdie
2001-07-11 16:14 ` Greg KH
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=15180.39107.179401.666431@somanetworks.com \
--to=georgn@somanetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@bigfoot.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
all inboxes | Powered by JetHome®