From: Andrew Morton <akpm@osdl.org>
To: Chris Ruvolo <chris+lkml@ruvolo.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-t1 garbage in /proc/ioports and oops
Date: Thu, 17 Jul 2003 21:15:33 -0700 [thread overview]
Message-ID: <20030717211533.77c0f943.akpm@osdl.org> (raw)
In-Reply-To: <20030718011101.GD15716@ruvolo.net>
Chris Ruvolo <chris+lkml@ruvolo.net> wrote:
>
> Hi, I am seeing some garbage data in /proc/ioports. Currently, I can cat
> the file without an oops, but on a previous boot, the following oops came
> up when catting the file.
>
> Exact output from /proc/ioports is attached (some 8-bit garbage), as well as
> lsmod output. Let me know if further data is needed.
>
> I suspect that this is a problem in one of the drivers I am using, but
> how do I track down which one it is (since the name is not there)?
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:
#!/bin/sh
echo Loading $* > /dev/console
modprobe.orig $*
cat /proc/ioports > /dev/null
echo that worked
and then just boot in the normal manner.
Have you ever unloaded a module? The usual source of this crash is some
driver forgot to unregister an IO region during module unload. So a read
of /proc/ioports crashes _after_ the module is rmmodded.
next prev parent reply other threads:[~2003-07-18 3:59 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 [this message]
2003-07-18 15:04 ` Chris Ruvolo
2003-07-27 23:38 ` Andrew Morton
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=20030717211533.77c0f943.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=chris+lkml@ruvolo.net \
--cc=linux-kernel@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 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).