From: Andrew Morton <akpm@digeo.com>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Panic `cat /proc/ioports`
Date: Wed, 12 Feb 2003 09:22:24 -0800 [thread overview]
Message-ID: <20030212092224.27aa4723.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1030212081934.6864A-100000@chaos.analogic.com>
"Richard B. Johnson" <root@chaos.analogic.com> wrote:
>
> On Tue, 11 Feb 2003, Andrew Morton wrote:
>
> > "Richard B. Johnson" <root@chaos.analogic.com> wrote:
> > >
> > > Linux version 2.4.18, after it runs for a few days, will panic
> > > if I do `cat /proc/ioports`. Has this been reported/fixed in
> > > later versions?
> > >
> > > : Unable to handle kernel paging request at virtual address d48e2fa0
> >
> > This means that some driver which was previously loaded forgot to do a
> > release_region(). Later, the /proc code tries to read stuff from within the
> > driver which isn't there any more and oopses.
> >
>
> Yes. I just noticed that most network board drivers in version 2.4.18
> do not execute release_region() after they have done a request_region(),
> if they fail to install because of some error.
Fairly common error.
> The error in this case was
> the failure to allocate memory because I told the kernel I only had 4
> megabytes (exprimental ioremap() of the rest in another module).
>
> Is somebody fixing these drivers (do you know).
There is ongoing janitorial work, and things are getting better.
But I'm not aware of anyone specifically auditing for missing
release_region()s. And given that it is a box-killer rather than
just a memory leak, yes, it is worth an audit.
next prev parent reply other threads:[~2003-02-12 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 20:55 Panic `cat /proc/ioports` Richard B. Johnson
2003-02-11 23:44 ` Andrew Morton
2003-02-12 13:25 ` Richard B. Johnson
2003-02-12 17:22 ` Andrew Morton [this message]
2003-02-12 18:25 ` Randy.Dunlap
2003-02-12 18:56 ` Richard B. Johnson
2003-02-12 19:16 ` Dave Jones
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=20030212092224.27aa4723.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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