From: Andrew Morton <akpm@osdl.org>
To: Chris Ruvolo <chris@ruvolo.net>
Cc: linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net,
Jaroslav Kysela <perex@suse.cz>, Adam Belay <ambx1@neo.rr.com>
Subject: Re: 2.6.0-t1 garbage in /proc/ioports and oops
Date: Sun, 27 Jul 2003 16:38:12 -0700 [thread overview]
Message-ID: <20030727163812.75b98b02.akpm@osdl.org> (raw)
In-Reply-To: <20030718150429.GE15716@ruvolo.net>
Chris Ruvolo <chris@ruvolo.net> wrote:
>
> (adding alsa-devel)
>
> On Thu, Jul 17, 2003 at 09:15:33PM -0700, Andrew Morton wrote:
> > You could load all those modules one at a time, doing a `cat /proc/ioports'
> > after each one. One sneaky way of doing that would be to make your
> > modprobe executable be:
>
> Ok, this let me track it down to the ALSA snd-sbawe module. I did not have
> isapnp compiled into the kernel and was relying on the userspace isapnp to
> configure the device (carried over from 2.4). Apparently the module didn't
> like this.
OK, thanks for that.
>From my reading, snd_sb16_probe() is, in the case of !CONFIG_PNP, doing:
/* block the 0x388 port to avoid PnP conflicts */
acard->fm_res = request_region(0x388, 4, "SoundBlaster FM");
but this reservation is never undone. So later, after the module is
unloaded, a read of /proc/ioports is oopsing when trying to access that
string "SoundBlaster FM". Because it now resides in vfree'd memory.
The fix would be to run release_region() either at the end of
snd_sb16_probe() or on module unload.
Adam or Jaroslav, could you please take care of this?
Thanks.
next prev parent reply other threads:[~2003-07-28 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 1:11 2.6.0-t1 garbage in /proc/ioports and oops Chris Ruvolo
2003-07-18 4:15 ` Andrew Morton
2003-07-18 15:04 ` Chris Ruvolo
2003-07-27 23:38 ` Andrew Morton [this message]
2003-07-27 22:43 ` Adam Belay
2003-07-28 16:20 ` alsa sbawe fails w/o isapnp (was: garbage in /proc/ioports and oops) Chris Ruvolo
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=20030727163812.75b98b02.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ambx1@neo.rr.com \
--cc=chris@ruvolo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).