From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: ioanm-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org
Cc: Christian Fetzer
<fetzer.ch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: I/O address 0x0cd6 already in use
Date: Thu, 7 Jul 2016 12:16:00 -0700 [thread overview]
Message-ID: <20160707191600.GA9431@roeck-us.net> (raw)
In-Reply-To: <CAH2idRciNOYZ9x8HC6oJM77pfJ2V93eamSxxpGMe_gtQOoyi2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Jul 07, 2016 at 08:19:56PM +0300, Ioan Moldovan wrote:
> [ioan@ioanpc ~]$ sudo cat /proc/ioports | grep 0cd6
> 0cd6-0cd7 : pnp 00:07
> 0cd6-0cd7 : smba_idx
>
> Look like pnp & smba_idx, no idea what those 2 are!
>
Please don't drop the mailing list from your replies; others may be interested
in the problem as well. Also, please avoid top-posting.
The culprit is drivers/i2c/busses/i2c-piix4.c, which specifically requests
IO address 0xcd6-0cd7. In earlier kernels, that driver released the region
after it was done with its initialization. This is no longer the case;
instead, the region is only released when the driver is unloaded.
In other words, it is now either-or. You can load the watchdog driver
or the i2c driver, but not both.
This was introduced with commit 2fee61d22e60 ("i2c: piix4: Add support
for multiplexed main adapter in SB800"). Copying the author and the i2c
mailing list for comments.
Guenter
> 2016-07-07 18:14 GMT+03:00 Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>:
> > On 07/07/2016 06:12 AM, Ioan Moldovan wrote:
> >>
> >> At every boot of my PC I noticed the following error telling me the IO
> >> address 0x0cd6 is already in use:
> >>
> >> [ 6.083233] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05
> >> [ 6.083292] sp5100_tco: PCI Vendor ID: 0x1022, Device ID: 0x780b,
> >> Revision ID: 0x16
> >> [ 6.083296] sp5100_tco: I/O address 0x0cd6 already in use
> >>
> >> Not being a kernel developer, I have no way to fix this.
> >>
> >
> > You probably won't be able to fix it. Try "sudo cat /proc/ioports";
> > it might tell you who is using that io address space.
> >
> > Guenter
> >
> >> CPU Details:
> >> vendor_id : AuthenticAMD
> >> cpu family : 21
> >> model : 48
> >> model name : AMD Athlon(tm) X4 860K Quad Core Processor
> >> stepping : 1
> >> microcode : 0x6003104
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-watchdog"
> >> in
> >> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>
> >
>
>
>
> --
> Ioan Moldovan
> ioan.moldovan1999-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: ioanm@linux.com
Cc: Christian Fetzer <fetzer.ch@gmail.com>,
linux-watchdog@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org
Subject: Re: I/O address 0x0cd6 already in use
Date: Thu, 7 Jul 2016 12:16:00 -0700 [thread overview]
Message-ID: <20160707191600.GA9431@roeck-us.net> (raw)
In-Reply-To: <CAH2idRciNOYZ9x8HC6oJM77pfJ2V93eamSxxpGMe_gtQOoyi2Q@mail.gmail.com>
On Thu, Jul 07, 2016 at 08:19:56PM +0300, Ioan Moldovan wrote:
> [ioan@ioanpc ~]$ sudo cat /proc/ioports | grep 0cd6
> 0cd6-0cd7 : pnp 00:07
> 0cd6-0cd7 : smba_idx
>
> Look like pnp & smba_idx, no idea what those 2 are!
>
Please don't drop the mailing list from your replies; others may be interested
in the problem as well. Also, please avoid top-posting.
The culprit is drivers/i2c/busses/i2c-piix4.c, which specifically requests
IO address 0xcd6-0cd7. In earlier kernels, that driver released the region
after it was done with its initialization. This is no longer the case;
instead, the region is only released when the driver is unloaded.
In other words, it is now either-or. You can load the watchdog driver
or the i2c driver, but not both.
This was introduced with commit 2fee61d22e60 ("i2c: piix4: Add support
for multiplexed main adapter in SB800"). Copying the author and the i2c
mailing list for comments.
Guenter
> 2016-07-07 18:14 GMT+03:00 Guenter Roeck <linux@roeck-us.net>:
> > On 07/07/2016 06:12 AM, Ioan Moldovan wrote:
> >>
> >> At every boot of my PC I noticed the following error telling me the IO
> >> address 0x0cd6 is already in use:
> >>
> >> [ 6.083233] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05
> >> [ 6.083292] sp5100_tco: PCI Vendor ID: 0x1022, Device ID: 0x780b,
> >> Revision ID: 0x16
> >> [ 6.083296] sp5100_tco: I/O address 0x0cd6 already in use
> >>
> >> Not being a kernel developer, I have no way to fix this.
> >>
> >
> > You probably won't be able to fix it. Try "sudo cat /proc/ioports";
> > it might tell you who is using that io address space.
> >
> > Guenter
> >
> >> CPU Details:
> >> vendor_id : AuthenticAMD
> >> cpu family : 21
> >> model : 48
> >> model name : AMD Athlon(tm) X4 860K Quad Core Processor
> >> stepping : 1
> >> microcode : 0x6003104
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-watchdog"
> >> in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>
> >
>
>
>
> --
> Ioan Moldovan
> ioan.moldovan1999@gmail.com
next prev parent reply other threads:[~2016-07-07 19:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 13:12 I/O address 0x0cd6 already in use Ioan Moldovan
2016-07-07 15:14 ` Guenter Roeck
[not found] ` <CAH2idRciNOYZ9x8HC6oJM77pfJ2V93eamSxxpGMe_gtQOoyi2Q@mail.gmail.com>
[not found] ` <CAH2idRciNOYZ9x8HC6oJM77pfJ2V93eamSxxpGMe_gtQOoyi2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-07 19:16 ` Guenter Roeck [this message]
2016-07-07 19:16 ` Guenter Roeck
2016-07-08 4:59 ` Ioan Moldovan
2016-07-08 13:23 ` Guenter Roeck
2016-07-09 4:08 ` Ioan Moldovan
2016-07-09 8:59 ` Guenter Roeck
2016-07-09 13:34 ` Ioan Moldovan
2016-07-09 15:06 ` Guenter Roeck
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=20160707191600.GA9431@roeck-us.net \
--to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
--cc=fetzer.ch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ioanm-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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.