https://bugzilla.kernel.org/show_bug.cgi?id=47981
--- Comment #37 from Feng Tang <feng.t...@intel.com> 2012-10-28 13:46:19 --- (In reply to comment #36) > Here's my reasoning: this is a CheckPoint product, and it looks like an > appliance, not really a general-purpose machine. The issue has apparently > been > there from day one, and the kernel shipped on the machine complains noisily > about the issue, but apparently nobody bothered to investigate it. > > This corruption will clearly break other ACPI-related things. We can sort of > work around this one (though the workaround does prevent us from doing any PCI > resource reassignment), but we have no idea what the other lurking ACPI issues > are (and we have no assurance that *only* ACPI things are broken -- maybe the > memory corruption affects other unknown things). It may take significant > debugging effort to identify the next problem. > > The only report I've seen (this one) is apparently from a CheckPoint employee, > so it's not clear that anybody else is trying to run upstream Linux on it. > Being a CheckPoint employee, J Bauer is probably in a position to get the BIOS > fixed. Fair enough to me! Then should we close this bug with a "Won't Fix"? (Sorry for the late response, just came back from vacation) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
