From: Mike Houston <mikeserv@bmts.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Adrian Bunk <bunk@stusta.de>, Elvis Pranskevichus <el@prans.net>,
Jean Delvare <khali@linux-fr.org>,
Mike Houston <mikeserv@bmts.com>,
mhoffman@lightlink.com, linux-kernel@vger.kernel.org,
lm-sensors@lm-sensors.org, Bjorn Helgaas <bjorn.helgaas@hp.com>,
Adam Belay <ambx1@neo.rr.com>, Zhao Yakui <yakui.zhao@intel.com>,
Thomas Renninger <trenn@suse.de>,
lenb@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [lm-sensors] 2.6.24-rc4 hwmon it87 probe fails
Date: Sun, 9 Dec 2007 23:02:11 -0500 [thread overview]
Message-ID: <20071209230211.1c2077cf.mikeserv@bmts.com> (raw)
In-Reply-To: <1197253887.27516.2.camel@sli10-desk.sh.intel.com>
On Mon, 10 Dec 2007 10:31:27 +0800
Shaohua Li <shaohua.li@intel.com> wrote:
> This should exist in previous kernel (before we remove acpi
> motherboard driver) too. Basically it's a broken BIOS. Could below
> patch work around it?
>
> Thanks,
> Shaohua
>
> Index: linux/drivers/pnp/system.c
> ===================================================================
> --- linux.orig/drivers/pnp/system.c 2007-12-10
> 10:17:46.000000000 +0800 +++ linux/drivers/pnp/system.c
Thanks Shaohua, I tested this as well and it appears to have worked
around the issue for me.
Now, in dmesg, I get:
system 00:01: ioport range 0x290-0x29f has been reserved
(...)
system 00:01: ioport range 0x290-0x294 could not be reserved
In /proc/ioports I see:
0290-029f : pnp 00:01
0290-0297 : it87
0290-0297 : it87
The it87 sensor now works without disabling acpipnp
Mike Houston
next prev parent reply other threads:[~2007-12-10 4:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071204215154.7f26285e.mikeserv@bmts.com>
[not found] ` <20071209000554.GF20441@stusta.de>
[not found] ` <20071208212234.e00b74cd.mikeserv@bmts.com>
[not found] ` <20071209105028.06ed52a6@hyperion.delvare>
[not found] ` <E1J1TRp-0000ZF-6J@asgard.prans.org>
2007-12-09 22:04 ` [lm-sensors] 2.6.24-rc4 hwmon it87 probe fails Adrian Bunk
2007-12-10 2:31 ` Shaohua Li
2007-12-10 2:49 ` Elvis Pranskevichus
2007-12-10 4:02 ` Mike Houston [this message]
2007-12-17 1:59 ` Shaohua Li
2007-12-17 17:14 ` Bjorn Helgaas
2007-12-18 17:59 ` Jean Delvare
2007-12-20 0:20 ` Bjorn Helgaas
2007-12-20 0:45 ` Carlos Corbacho
2007-12-20 2:13 ` Elvis Pranskevichus
2007-12-20 2:17 ` Carlos Corbacho
2007-12-21 19:00 ` Bjorn Helgaas
2007-12-21 19:50 ` Mike Houston
2007-12-22 11:21 ` Jean Delvare
2007-12-23 3:40 ` [lm-sensors] " Bjorn Helgaas
2007-12-23 9:28 ` Jean Delvare
2007-12-23 23:14 ` Bjorn Helgaas
2007-12-25 21:31 ` Jean Delvare
2008-01-02 18:30 ` Bjorn Helgaas
2008-01-12 9:49 ` Jean Delvare
2007-12-19 23:53 ` [lm-sensors] " Bjorn Helgaas
[not found] <fa.QPUBl9Xd2PDsImgWn6hbR+ShV1U@ifi.uio.no>
[not found] ` <fa.ri5Klmu4+MwjYC8x5nSms+xKXfI@ifi.uio.no>
[not found] ` <fa.B/J+j9kGGZ1+gW9FrfHky+cj0Eo@ifi.uio.no>
[not found] ` <fa.Xv3BmMxnCGLOeEijySte5mKDO5k@ifi.uio.no>
2007-12-20 1:09 ` Robert Hancock
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=20071209230211.1c2077cf.mikeserv@bmts.com \
--to=mikeserv@bmts.com \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=bunk@stusta.de \
--cc=el@prans.net \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=shaohua.li@intel.com \
--cc=trenn@suse.de \
--cc=yakui.zhao@intel.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;
as well as URLs for NNTP newsgroup(s).