mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ed Sweetman <safemode2@comcast.net>
To: Mike Houston <mikeserv@bmts.com>
Cc: Jean Delvare <khali@linux-fr.org>,
	Elvis Pranskevichus <el@prans.net>, Adrian Bunk <bunk@stusta.de>,
	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>
Subject: Re: [lm-sensors] 2.6.24-rc4 hwmon it87 probe fails
Date: Sun, 09 Dec 2007 20:32:41 -0500	[thread overview]
Message-ID: <475C9739.4030306@comcast.net> (raw)
In-Reply-To: <20071209191959.eba5a41f.mikeserv@bmts.com>

Mike Houston wrote:
> On Sun, 9 Dec 2007 23:42:15 +0100
> Jean Delvare <khali@linux-fr.org> wrote:
>
>   
>> On Sun, 09 Dec 2007 16:12:25 -0500, Elvis Pranskevichus wrote:
>>     
>
>   
>>> This indeed looks like a broken ACPI BIOS since the
>>> aforementioned commit touches only the PNP ACPI driver. I'm not
>>> sure how to work around this, though. Ideas?
>>>       
>> Complaining to Gigabyte seems to be the best approach.
>>     
>
> I just happen to have a Windows Vista installation on this box as
> well, and I just thought to check. Sorry, I wish I'd have thought of
> it sooner but I don't go there often. You folks might be interested
> to know that Windows appears to have the same silly problem with the
> i/o resources (from Device Manager):
>
> [000000290 - 000000294]  Motherboard resources
> [000000290 - 00000029F]  Motherboard resources
>
> I don't have anything that reads sensors in Windows though, so I
> couldn't tell you if it could access that it87 chip or not.
>
> So this pretty much confirms that it's a motherboard/bios issue.
>
> Mike Houston
>
>   

I'm seeing this exact problem on an Asus Nforce4 based board. Prior to 
moving to 2.6.24-rc4 it worked just fine.  No additional acpi options 
were selected in kernel config.  

So add Asus A8N-E to the list of broken pnpacpi


  reply	other threads:[~2007-12-10  1:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05  2:51 Mike Houston
2007-12-09  0:05 ` Adrian Bunk
2007-12-09  2:22   ` Mike Houston
2007-12-09  9:50     ` [lm-sensors] " Jean Delvare
2007-12-09 19:40       ` Mike Houston
2007-12-09 21:12       ` Elvis Pranskevichus
2007-12-09 22:04         ` Adrian Bunk
2007-12-10  2:31           ` Shaohua Li
2007-12-10  2:49             ` Elvis Pranskevichus
2007-12-10  4:02             ` Mike Houston
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                         ` 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
2007-12-09 22:42         ` Jean Delvare
2007-12-09 23:15           ` Mike Houston
2007-12-10  0:19           ` Mike Houston
2007-12-10  1:32             ` Ed Sweetman [this message]
2007-12-10 14:55               ` Jean Delvare
     [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       ` [lm-sensors] " 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=475C9739.4030306@comcast.net \
    --to=safemode2@comcast.net \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=bunk@stusta.de \
    --cc=el@prans.net \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=mhoffman@lightlink.com \
    --cc=mikeserv@bmts.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

Powered by JetHome