Hi Feng,
On Thu, Aug 23, 2012 at 01:08:14PM +0800, Feng Tang wrote:
> On Wed, 22 Aug 2012 22:55:43 +0100
> Matthew Garrett wrote:
>
> > On Wed, Aug 22, 2012 at 09:55:12PM +0200, Wim Van Sebroeck wrote:
> >
> > > Any idea why the acpi_check_resource_conflict() check gives a conflict?
> >
> > Be
On Wed, 22 Aug 2012 22:55:43 +0100
Matthew Garrett wrote:
> On Wed, Aug 22, 2012 at 09:55:12PM +0200, Wim Van Sebroeck wrote:
>
> > Any idea why the acpi_check_resource_conflict() check gives a conflict?
>
> Because the resource range is declared in ACPI and we assume that that
> means the fir
On Wed, Aug 22, 2012 at 09:55:12PM +0200, Wim Van Sebroeck wrote:
> Any idea why the acpi_check_resource_conflict() check gives a conflict?
Because the resource range is declared in ACPI and we assume that that
means the firmware wants to scribble on it. We'd need the output of
acpidump to work
Hi All,
Cc-ing Samuel and Guenter also.
> There are many reports (including 2 of my machines) that iTCO_wdt watchdog
> driver fails to be initialized in 3.5 kernel with error message like:
>
> [5.265175] ACPI Warning: 0x1060-0x107f SystemIO conflicts with
> Region \_SB_.PCI0.LPCB.TC
4 matches
Mail list logo