Bug 188221

please attach the acpidump output

BTW, what makes you think this is a regression? is there any earlier kernel version that you don't see this message?

I'm using kernel v4.8.9 and before v4.4.30.
With these kernels I don't have this BIOS error message.

(In reply to lercoli4670 from comment #2)
> I'm using kernel v4.8.9 and before v4.4.30.
> With these kernels I don't have this BIOS error message.

then it would be good if you can attach the kernel config file you're using for both 4.8.9 and 4.9.0-rc6

Created attachment 245251 [details]
kernel_v4.8.9_config_file

Created attachment 245261 [details]
kernel_v4.9.0-rc6_config_file

The message comes from a driver that is new in 4.9-rc.

Please don't guess things, it isn't helpful.

I'm a Linux user not a Linux developer so my perspective is different of yours.
That's all.
However, to avoid misunderstandings, I'll never change the Regression listbox anymore.

please attach the acpidump output, which is helpful to debug this issue

Created attachment 245551 [details]
acpidump file

Please also attach content of /proc/iomem and /proc/ioports.

Created attachment 245571 [details]
iomem file

Created attachment 245581 [details]
ioport file

Ah, you need to be root in order to see the offsets. Can you do something like this instead:

  $ sudo cat /proc/ioports > ioports.txt
  $ sudo cat /proc/iomem > iomem.txt

and attach those.

Created attachment 245591 [details]
iomem.txt file

Created attachment 245601 [details]
ioports.txt file

Created attachment 245611 [details]
wdat_wdt debug patch

Can you try the attached patch? It prints out all the watchdog resources so that we can see the actual conflict. Once you have the patch applied please attach dmesg to this bug.

Could you tell me how to try this attached path ?

Assuming you know how to build the kernel (since you are already using v4.9-rc6):

1. Save the patch somewhere under your Linux source tree
2. Run 'git apply path/to/wdat_wdt.diff'
3. Rebuild the kernel
4. Install the kernel
5. Reboot

I don't build the kernel because I use the .deb files of Ubuntu at http://kernel.ubuntu.com/~kernel-ppa/mainline/.

OK, I think I already know what happens here.

The WDAT table uses RTC SRAM (port 0x70 and 0x71) to hold one bit at byte 0x45. That bit is set to one when the watchdog is started, and cleared when it is stopped. That particular I/O region is reserved for RTC according /proc/ioports:

  0070-0077 : rtc0

This is the reason why we fail to request it for wdat_wdt.

I'm not sure if this can be fixed easily because we really should not touch the RTC registers (even if those are not related to the RTC core functionality) from WDAT driver behind the RTC driver's back.

Well, this is a tough one.

The driver does the right thing IMO, except that the messages might be less confusing.

OK thanks.

I think I'll submit a patch changing 
[   1.138605] ACPI : watchdog : Failed to create platform devices

to something like

[   1.138605] ACPI : watchdog : WDAT device creation failed

or similar. Maybe it is worth printing the conflicting resource in platform_device_create() as well.

Is there a workaround for my Toshiba/Ubuntu to use kernel v4.9.x ?

It is just a warning. Your system should work just fine but you cannot use WDAT watchdog on that.

I've checked watchdog on terminal and it's not installed on my Ubuntu 
so it should work.

Ok, with kernel v4.9.0-rc7 it works.
Thank You.

How is this closed it's still happening through 3.10.x
toshiba Satelite here too

*4.10.3+

I've tested it on kernel v4.10.4 and it works(Ubuntu 16.10).