Launchpad has imported 14 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=456352.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-07-23T02:43:57+00:00 Ryan wrote: Description of problem: Multiple ACPI problems and warnings on boot, PC will suspend and resume, but on the next reboot, it hangs and requires a hard reset, Thermal Zone and Fan control support also appear to be missing, I had to set the BIOS to take control of the fans, or else they run at 100% at all times. The website for this motherboard: http://www.foxconnchannel.com/product/Motherboards/detail_overview.aspx?ID =en-us0000327 I am using latest BIOS, which seems to allow CPU Frequency scaling to function. Version-Release number of selected component (if applicable): Kernel 2.6.25.10-86 Running a 2.6.26-git9 kernel appears to fix (some?) of this in that ACPI: Failed To Attach Device messages are gone and PC suspends, resumes, and reboots, still get checksum error relating to tbautils. Behaviour is the same with ACPI 1, 2, or 3. How reproducible: Steps to Reproduce: 1. Install Foxconn G33M or G33M-S motherboard. 2. Boot Fedora 3. Try a suspend, resume reboot. Actual results: Depdning on your kernel, either resume no worky, reboot no worky, and in all cases, ugly kernel error messages. Expected results: Suspend, resume, reboot all worky, kernel gives no error messages. Additional info: I've attached a lot of all my kernel related messages. I've attempted to ask Foxconn about this, and they recommended I remove all of my RAM and see if the problem continues. (OK, not as useful as funny, but still) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/0 ------------------------------------------------------------------------ On 2008-07-23T02:43:57+00:00 Ryan wrote: Created attachment 312410 Clip of kernel messages on boot, with shoddy Foxconn motherboard Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/1 ------------------------------------------------------------------------ On 2008-07-23T03:53:40+00:00 Ryan wrote: Created attachment 312417 Clip from /var/log/messages with 2.6.25.11-97 System log messages with kernel 2.6.25.11-97, I installed this kernel because it appears to be more verbose. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/2 ------------------------------------------------------------------------ On 2008-07-27T00:06:44+00:00 Matthew wrote: Linux correctly reports that the table has an incorrect checksum, but that should be purely cosmetic. The only obvious remaining bug is that the machine fails to reboot after a suspend to RAM? Does booting with reboot=b as a kernel command option work around this? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/18 ------------------------------------------------------------------------ On 2008-07-27T02:58:49+00:00 Matthew wrote: Man I suck at bugzilla. Reopening since I closed it by accident. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/20 ------------------------------------------------------------------------ On 2008-07-27T03:08:09+00:00 Ryan wrote: reboot-b has no effect. I've sent you my ACPI dump. Foxconn is apparently working on some kind of a patch, and has stated that they will make an official announcement over why this happened on Monday. They've been frantically working on getting the BIOS to boot up Linux and correctly interface with it on their test machines. >From what I can tell an improved BIOS ROM is on the way? I will post link to the ROM when they put it on their site so we can close this bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/21 ------------------------------------------------------------------------ On 2008-07-27T03:16:51+00:00 Matthew wrote: Just to confirm, you tried reboot=b and not reboot-b , right? It needs to be passed as a kernel option from grub. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/22 ------------------------------------------------------------------------ On 2008-07-27T03:53:18+00:00 Ryan wrote: yes, I put reboot=b in menu.lst, same behavior Get an error on resume that I couldn't make out before. Something like: ATA 6 revalidation error. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/23 ------------------------------------------------------------------------ On 2008-07-27T07:27:58+00:00 Ryan wrote: Just to go over what Matthew has stated on his blog, paraphrasing: "There's no way altering the DSDT fixes any of the errors, especially not the checksum" It does indeed fix all of that, or at least no errors in my log when I change to _OSI and Store Zero (What Vista and XP get), and remove the _OS reference to "Linux", so I don't know, I'm even more uncomfortable with this, he says this shouldn't happen, but it does. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/26 ------------------------------------------------------------------------ On 2008-07-29T08:10:45+00:00 Ryan wrote: I have been in touch with Foxconn several times today, this bug also affects: Asus P5K-E P5E WS and P5E WS PRO MSI P965 series It is the BIOS that is defective, not the chipset. American Megatrends (AMI) shipped the defective BIOS, if yours is an Award BIOS, this is not an issue. http://izanbardprince.wordpress.com/2008/07/28/foxconn-says-acpi-issues- are-amis-fault-is-having-them-repair-the-code/ I've been told to expect the Foxconn fix within a matter of days, users of ASUS or MSI motherboards are encouraged to contact them for the fix and reference that Foxconn has confirmed that the AMI BIOS is defective. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/29 ------------------------------------------------------------------------ On 2008-07-29T10:36:03+00:00 Ryan wrote: I would also like to say before anyone asks that despite what original post says, I never was able to get it to reboot properly after suspend no matter what I did, I was deliriously tired (and typing angry) when I wrote this up, trying to figure out what was wrong, if the problem would go away with the newest kernels. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/31 ------------------------------------------------------------------------ On 2008-08-01T21:19:52+00:00 Ryan wrote: BIOS fix for Foxconn motherboards very soon, I am beta testing a new BIOS that resolves all the party poopers as long as you're using kernel 2.6.26 MSI and ASUS appear to want to have nothing to do with this, thats my hunch anyway, kindly pester them if you're their customer would be my suggestion, but we all know that would make me a hypocrite. :P Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/35 ------------------------------------------------------------------------ On 2008-08-06T14:49:41+00:00 Matthew wrote: I've been in communication with the AMI engineers. The issue appears to be that Linux doesn't clear the WAK_STS flag on resume, which causes the BIOS to think that a reset is actually a resume. I've got a test board now, so will check this later today. Should be a trivial patch. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/38 ------------------------------------------------------------------------ On 2008-08-06T18:36:40+00:00 Matthew wrote: Fix applied to Rawhide and sent upstream. Should land within the next day or so. Tested successfully on a G33M board. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/39 ** Changed in: linux (Fedora) Importance: Unknown => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/251338 Title: Defective AMI BIOS on multiple Foxconn, MSI, and ASUS Intel LGA 775 motherboards breaks ACPI support Status in linux package in Ubuntu: Fix Released Status in linux source package in Hardy: Fix Released Status in linux package in Fedora: Fix Released Bug description: SRU justification: Impact: After resuming "the other OS" seems to reset WAK_STS which some boards use as indication whether a machine is rebooting or resuming. So when not clearing that flag the reboot after resume does not work correctly. Fix: Backport of upstream patch from Matthew Garret which is confirmed to fix the issue in Intrepid. Testcase: On affected BIOSes suspend and resume, then reboot. --- Update: Heart Zhang at Foxconn has posted on the forums, with instructions on how to download the test/beta of their repaired BIOS for their G33M and G33M-S boards, and says all affected Foxconn boards will be fixed soon: http://ubuntuforums.org/showthread.php?t=877721 I need to stress that as it is, you will need to be using kernel 2.6.26 to fix some kernel bugs that this BIOS still provokes, but it looks like most of the issues with the BIOS itself are resolved, Foxconn is trying to get it tested and all the loose ends ties up before making a release, so even if you grab this build, you'll want the release one too when it arrives. Description of problem: Multiple ACPI problems and warnings on boot, PC may suspend and resume on recent kernels, but on resume sound will not work except with kernel 2.6.26, and in any case, on next reboot the system hangs and requires a hard reset, Thermal Zone and Fan control support also appear to be missing, I had to set the BIOS to take control of the fans, or else they run at 100% at all times. The website for the affected Foxconn G33M-S motherboard that I own: http://www.foxconnchannel.com/product/Motherboards/detail_overview.aspx?ID =en-us0000327 I am using latest BIOS for my Foxconn G33M-S, which seems to allow CPU Frequency scaling to function, earlier BIOS versions don't allow this. Version-Release number of selected component: Any Linux kernel. Running a 2.6.26-git9 kernel from kernel.org appears to fix (some?) of this in that ACPI: Failed To Attach Device messages are gone and PC suspends, resumes, still but hangs on reboot if suspend has been used that session, still get checksum error relating to tbautils, and still no fan control support. Running a customized DSDT table meant for Windows Vista or XP, gets the problem down to just crashing on reboot if I've suspended and resumed in that session, AMI BIOS has some weird Linux path and these need to be removed, unknown how they are triggering Linux into accepting this. Behavior is the same with ACPI 1, 2, or 3 as selected in the BIOS setup program. How reproducible: Steps to Reproduce: 1. Install an affected Foxconn, MSI, or ASUS Intel LGA775 motherboard with the defective AMI BIOS. 2. Boot Ubuntu (or any Linux distribution) 3. Try a suspend, resume, playing sounds, reboot. Actual results: Depending on your kernel, all kind of things, either the system won't boot at all, resume doesn't work at all, reboot doesn't work after resuming, sound never works after resuming (except in Intrepid development branch or with other 2.6.26 based kernel), and in all cases, ugly kernel error messages in the system log. Expected results: Everything works, kernel gives no error messages. Additional info: I’ve attached all debugging info requested by DebuggingACPI page. Foxconn is aware of the situation and has promised a BIOS update expeditiously, status of MSI and ASUS on the issue is unknown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
