From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Fwd: Re: i2c: lost sensors with 2.6.10(-mm1) [jamagallon@able.es]
Date: Sat, 08 Jan 2005 00:37:15 +0000 [thread overview]
Message-ID: <1105144635l.16114l.0l@werewolf.able.es> (raw)
In-Reply-To: <1105142540l.5669l.0l@werewolf.able.es> (from jamagallon@able.es on Sat Jan 8 01:02:20 2005)
[-- Attachment #1: Type: text/plain, Size: 4403 bytes --]
On 2005.01.08, J.A. Magallon wrote:
On 2005.01.07, Jean Delvare wrote:
> J.A. Magallon wrote:
>
> > I have lost my sensors info with 2.6.10, in particular -mm1.
> > They work fine with 2.6.9-mm1 (current state of the box, booted on
> > 2.6.9 or 10, no other difference).
> > (...)
> > I have noticed different contents in /sys:
> > under 2.6.9:
> > /sys/devices/platform/i2c-1:
> > /sys/devices/platform/i2c-1/1-0290:
> > /sys/devices/platform/i2c-1/1-0290/power:
> > /sys/devices/platform/i2c-1/power:
> >
> > under 2.6.10:
> > /sys/devices/platform/i2c-1:
> > /sys/devices/platform/i2c-1/power:
> >
> > So some /sys nodes are missing !!!
> > (the isa bus)
>
> This basically means that the i2c client was not registered.
>
> > Debug output from 2.6.10-mm1:
> > (...)
> > Jan 7 01:33:11 werewolf kernel: i2c-core: driver w83627hf registered.
> > Jan 7 01:33:11 werewolf kernel: i2c_adapter i2c-1: found normal isa entry for adapter 9191, addr 0290
>
> However, this suggests that the driver loaded properly and the base
> address was correctly read from Super-I/O space. This would mean that
> the problem happened later, in w83627hf_detect(). The most likely reason
> for this would be if the region request failed (unfortunately we have no
> message, not even debug, if this happens).
>
> > Some ideas ?
>
> Three things to try, in order:
>
> 1* Compare /proc/ioports in 2.6.9-mm1 and 2.6.10-mm1. I suspect that the
> 0x290-0x297 range is held by some device in 2.6.10-mm1.
>
Good start. 2.6.10-mm1 shows this:
@@ -45,6 +44,7 @@
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
+0295-0296 : pnp 00:0d
02f8-02ff : serial
0376-0376 : ide1
03c0-03df : vga+
Differences in dmesg show this (apart from others):
@@ -120,6 +120,7 @@
Normal zone: 257760 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
+__iounmap: bad address b00f0000
ACPI: RSDP (v000 IntelR ) @ 0x000f71f0
ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fee3000
ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fee3040
@@ -149,25 +150,27 @@
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Built 1 zonelists
+mapped APIC to ffffd000 (fee00000)
+mapped IOAPIC to ffffc000 (fec00000)
Initializing CPU#0
@@ -236,7 +239,9 @@
PCI: PCI BIOS revision 2.10 entry at 0xfb7c0, last bus=3
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
-ACPI: Subsystem revision 20040816
+ACPI: Subsystem revision 20041210
+ ACPI-1138: *** Error: Method execution failed [\STRC] (Node efedc380), AE_AML_BUFFER_LIMIT
+ ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0._INI] (Node efedd620), AE_AML_BUFFER_LIMIT
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
@@ -254,6 +259,8 @@
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 *9 10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
+pnp: PnP ACPI init
+pnp: PnP ACPI: found 16 devices
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
@@ -263,6 +270,8 @@
** behavior. If this argument makes the device work again,
** please email the output of "lspci" to bjorn.helgaas@hp.com
** so I can fix the driver.
+pnp: 00:0d: ioport range 0x400-0x4bf could not be reserved
+pnp: 00:0d: ioport range 0x295-0x296 has been reserved
IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
So I guess it is "Plug and Play ACPI support", I'm just going to disable it
and try. If it is the case, there is an IO port conflict...
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.10-jam1 (gcc 3.4.3 (Mandrakelinux 10.2 3.4.3-2mdk)) #2
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.10-jam1 (gcc 3.4.3 (Mandrakelinux 10.2 3.4.3-2mdk)) #3
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-08 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 0:46 i2c: lost sensors with 2.6.10(-mm1) J.A. Magallon
2005-01-07 9:51 ` Jean Delvare
2005-05-19 6:25 ` Jean Delvare
2005-01-08 0:02 ` J.A. Magallon
2005-01-08 0:37 ` J.A. Magallon [this message]
2005-01-08 1:45 ` J.A. Magallon
2005-05-19 6:25 ` J.A. Magallon
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=1105144635l.16114l.0l@werewolf.able.es \
--to=jamagallon@able.es \
--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 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.