http://bugzilla.kernel.org/show_bug.cgi?id=9085


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |REJECTED
         Resolution|                            |WILL_NOT_FIX




------- Comment #12 from [EMAIL PROTECTED]  2008-01-24 17:32 -------
Hi, Jan
   Thanks for the info. 
   What Steffen said in comment #7 is very right and this is resource conflict.
Ethernet device wants to request the memory resource of
0xff9f8000-0xff9fBFFF.But the range of 0xFF9FA000-0xFF9FAFFF is reserved by the
device of PNP0C02. So the Ethernet can't request the memory resource and report
the error message.

   This is caused by the commit of a8c78f7fb1571764f48b8af5459abdd2c66a765f,
which reserves system board iomem resources as well as ioport resources for PNP
device. This patch is quite reasonable. This patch isn't merged into the 2.6.20
so ethernet can request the resource successfully. But the patch is merged into
2.6.21-2.6.23, so the ethernet device can't request the memory resource.    
   Of course the ethernet can work well if the boot option of "pnpacpi=off" is
added. 

   The bug is caused by broken BIOS and it is appropriate to fix it by BIOS
update.    


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to