From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Cc: "Sergey Kubushin" <ksi@cyberbills.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Peter Kaczuba <pepe@pool.informatik.rwth-aachen.de>,
tytso@mit.edu
Subject: Ram disk problems in 2.4.0ac12
Date: Mon, 29 Jan 2001 09:29:56 +1100 [thread overview]
Message-ID: <9495.980720996@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 26 Jan 2001 17:46:12 -0800." <Pine.LNX.4.31ksi3.0101261742080.598-100000@nomad.cyberbills.com>
On Fri, 26 Jan 2001 17:46:12 -0800 (PST),
"Sergey Kubushin" <ksi@cyberbills.com> wrote:
>Modules still don't load:
>
>=== Cut ===
>ide-mod.o: Can't handle sections of type 32131
>ide-probe-mod.o: Can't handle sections of type 256950710
>ide-disk.o: Can't handle sections of type 688840897
>ext2.o: Can't handle sections of type 69429248
>=== Cut ===
modutils has been ruled out as the cause of this problem. The objects
are valid but when they are loaded they come up as corrupt. Modules
work fine for me on 2.4.0-ac12, when they are loaded from disk. Both
people reporting this bug are using initrd so the obvious culprit is
the ram disk code.
-
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:[~2001-01-28 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 23:53 Linux 2.4.0ac12 Alan Cox
2001-01-27 0:50 ` Linux 2.4.0ac12 (ppp-generic) Aaron Tiensivu
2001-01-27 7:22 ` Jeff Garzik
2001-01-27 1:46 ` Linux 2.4.0ac12 Sergey Kubushin
2001-01-27 6:52 ` Keith Owens
2001-01-28 22:29 ` Keith Owens [this message]
2001-01-30 2:45 ` john slee
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=9495.980720996@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ksi@cyberbills.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pepe@pool.informatik.rwth-aachen.de \
--cc=tytso@mit.edu \
/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