From: "J . A . Magallon" <jamagallon@able.es>
To: Stephen Mollett <molletts@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "io mapaddr 0xXXXXX not valid" in smc-mca in 2.4.x
Date: Mon, 26 Feb 2001 21:07:00 +0100 [thread overview]
Message-ID: <20010226210700.C2354@werewolf.able.es> (raw)
In-Reply-To: <20010226154228.48338.qmail@web11205.mail.yahoo.com>
In-Reply-To: <20010226154228.48338.qmail@web11205.mail.yahoo.com>; from molletts@yahoo.com on Mon, Feb 26, 2001 at 16:42:28 +0100
On 02.26 Stephen Mollett wrote:
> In kernel version 2.4.x (x from 0 to 2-ac3), the
> smc-mca driver gives many errors like the following on
> the console log:
>
> io mapaddr 0xXXXXX not valid at smc-mca.c:YYY!
>
> where XXXXX is an address within the shared-memory
> assigned to the adapter card, and YYY is 378, 398 or
> 408.
>
AFAIK, it is a bug in the driver. That output is generated by
arch/i386/lib/iodebug.c, a routine to catch buggy drivers like that.
Look at
include/asm-i386/io.h, line 112 or so:
/*
* Temporary debugging check to catch old code using
* unmapped ISA addresses. Will be removed in 2.4.
*/
#if CONFIG_DEBUG_IOVIRT
extern void *__io_virt_debug(unsigned long x, const char *file, int line);
extern unsigned long __io_phys_debug(unsigned long x, const char *file, int li
ne);
#define __io_virt(x) __io_virt_debug((unsigned long)(x), __FILE__, __LINE__)
//#define __io_phys(x) __io_phys_debug((unsigned long)(x), __FILE__, __LINE__)
#else
#define __io_virt(x) ((void *)(x))
//#define __io_phys(x) __pa(x)
#endif
So you should mail driver mantainer, if it is known....
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.4.2-ac4 #2 SMP Mon Feb 26 00:21:23 CET 2001 i686
next prev parent reply other threads:[~2001-02-26 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 15:42 "io mapaddr 0xXXXXX not valid" in smc-mca in 2.4.x Stephen Mollett
2001-02-26 20:07 ` J . A . Magallon [this message]
2001-02-26 20:15 ` Alan Cox
2001-02-27 19:57 ` Stephen Mollett
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=20010226210700.C2354@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=molletts@yahoo.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 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.