From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>,
nikola.ciprich@linuxbox.cz
Subject: Re: reading /proc/ioports causes OOPS
Date: Sun, 14 Feb 2010 21:52:42 +0100 [thread overview]
Message-ID: <20100214205242.GC4466@nik-comp.linuxbox.cz> (raw)
In-Reply-To: <4B783CD2.1040209@gmail.com>
> My guess is that some module got unloaded and didn't unregister its
> ioport reservation, causing a segfault when the kernel tries to read
> the description string. Can you post the full dmesg output from
> bootup up to this point?
Hi, sure,
here it is: http://nelide.cz/downloads/dmesg.log
I see [last_unloaded]: freq_table there, loading the module back doesn't
fix the problem. I could reboot the machine on wednesday, so I can try
reading /proc/ioports just after reboot to see if there is any change...
nik
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
prev parent reply other threads:[~2010-02-14 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 17:45 reading /proc/ioports causes OOPS Nikola Ciprich
2010-02-14 18:11 ` Robert Hancock
2010-02-14 20:52 ` Nikola Ciprich [this message]
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=20100214205242.GC4466@nik-comp.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.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 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.