From: Andrew Morton <akpm@zip.com.au>
To: Matt <matt@progsoc.uts.edu.au>
Cc: Berend De Schouwer <bds@jhb.ucs.co.za>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Kernel Oops on cat /proc/ioports
Date: Tue, 11 Dec 2001 19:10:07 -0800 [thread overview]
Message-ID: <3C16CA8F.722CB6BB@zip.com.au> (raw)
In-Reply-To: <1008073796.5535.5.camel@bds.ucs.co.za> <3C16ADB1.F9E847E9@zip.com.au>, <3C16ADB1.F9E847E9@zip.com.au>; from akpm@zip.com.au on Tue, Dec 11, 2001 at 05:06:57PM -0800 <20011212135713.M5809@ftoomsh.progsoc.uts.edu.au>
Matt wrote:
>
> speaking of living in module memory, a similar thing happens with the
> via-rhine driver. after my machine has been up for a few hours the
> "via-rhine" string in /proc/iomem and /proc/ioports gets over written
> and prints garbage. since this has never been the cause for an oops on
> my machine i never bothered reporting it. if anyone wants details i'll
> provide.
>
I think it _could_ oops. Would it be correct to assume that
you're linking the driver into the kernel, rather than using it
as a module?
--- linux-2.4.17-pre8/drivers/net/via-rhine.c Mon Dec 10 13:46:21 2001
+++ linux-akpm/drivers/net/via-rhine.c Tue Dec 11 19:08:17 2001
@@ -161,7 +161,7 @@ static char version[] __devinitdata =
KERN_INFO "via-rhine.c:v1.10-LK1.1.12 03/11/2001 Written by Donald Becker\n"
KERN_INFO " http://www.scyld.com/network/via-rhine.html\n";
-static char shortname[] __devinitdata = "via-rhine";
+static char shortname[] = "via-rhine";
/* This driver was written to use PCI memory space, however most versions
next prev parent reply other threads:[~2001-12-12 3:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 12:29 PROBLEM: Kernel Oops on cat /proc/ioports Berend De Schouwer
2001-12-12 0:22 ` Randy.Dunlap
2001-12-12 0:31 ` {multiple} " Randy.Dunlap
2001-12-12 1:06 ` PROBLEM: " Andrew Morton
2001-12-12 2:57 ` Matt
2001-12-12 3:10 ` Andrew Morton [this message]
2001-12-12 3:25 ` Matt
2001-12-12 10:30 ` Berend De Schouwer
2001-12-12 1:25 ` Andrew Morton
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=3C16CA8F.722CB6BB@zip.com.au \
--to=akpm@zip.com.au \
--cc=bds@jhb.ucs.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@progsoc.uts.edu.au \
/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