From: "David S. Miller" <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: sparc: cannot load any modules with 2.6.17-rc3
Date: Tue, 09 May 2006 22:00:00 +0000 [thread overview]
Message-ID: <20060509.150000.102037355.davem@davemloft.net> (raw)
In-Reply-To: <20060505113514.GA28863@palantir8>
From: Martin Habets <errandir_news@mph.eclipse.co.uk>
Date: Tue, 9 May 2006 22:27:22 +0100
> Sadly, no. I can try to do some of the easier things, but fixing
> something like the esp driver without the esp&dma datasheets is
> beyond me I'm afraid :).
http://en.wikipedia.org/wiki/NCR_53C9x
The DMA programming manual is really not that necessary to
understand the chip.
> Yes, these actually fail to load. Maybe it's a memory corruption in module.c
> somehow: if I make too many debugging changes in apply_relocate_add() the
> problem disappears.
> I'm trying different things now to make it show me the failing section and
> symbol when it fails. I'll post again once I have more details.
Are you using Debian's gcc-4.1 compiler to build kernels?
That has already had problems reported with it wrt. miscompiling
the simplest kernel code such as the SUN disk label checksum
calculation in fs/partitions/sun.c and the similar code in
util-linux's fdisk.
next prev parent reply other threads:[~2006-05-09 22:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 11:35 sparc: cannot load any modules with 2.6.17-rc3 Martin Habets
2006-05-05 11:35 ` Martin Habets
2006-05-06 0:34 ` David S. Miller
2006-05-06 0:34 ` David S. Miller
2006-05-06 9:12 ` Martin Habets
2006-05-08 6:12 ` David S. Miller
2006-05-09 21:27 ` Martin Habets
2006-05-09 22:00 ` David S. Miller [this message]
2006-05-10 7:15 ` Jurij Smakov
2006-05-10 8:24 ` BERTRAND Joël
2006-05-10 20:29 ` David S. Miller
2006-05-11 16:33 ` Martin Habets
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=20060509.150000.102037355.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@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.