[Bug 681217] New: OpenSuSE 11.4: Broken ECDT table from ASUSTek on MSI-Laptop CR620
https://bugzilla.novell.com/show_bug.cgi?id=681217 https://bugzilla.novell.com/show_bug.cgi?id=681217#c0 Summary: OpenSuSE 11.4: Broken ECDT table from ASUSTek on MSI-Laptop CR620 Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: andihartmann@freenet.de QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=420421) --> (http://bugzilla.novell.com/attachment.cgi?id=420421) dmesg output User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b13pre) Gecko/20110316 Firefox/4.0b13pre SeaMonkey/2.1b2pre The ACPI code of the machine cannot be decoded without error. [ 0.430877] ACPI: EC: Detected MSI hardware, enabling workarounds. [ 0.430903] ACPI: EC: EC description table is found, configuring boot EC [ 0.430906] ACPI: EC: Look up EC in DSDT [ 0.430998] ACPI: EC: ASUSTek keeps feeding us with broken ECDT tables, which are very hard to workaround. Trying to use DSDT EC info instead. Please send output of acpidump to linux-acpi@vger.kernel.org [ 0.460128] ACPI: Executed 1 blocks of module-level executable AML code [ 0.470596] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored Sending to linux-acpi seems not to work. Reproducible: Always Steps to Reproduce: 1. Boot the machine 2. Check in dmesg 3. Actual Results: see details Expected Results: there should be no error -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c1
--- Comment #1 from Andreas Hartmann
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c2
--- Comment #2 from Andreas Hartmann
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c3
Thomas Renninger
Sending to linux-acpi seems not to work. This is because the list does not accept that huge attachments. Better upload it somewhere and point to it.
Also the EC maintainer (who added the message) does not work on this stuff anymore. Hm, the message really indicates that there is something wrong with the table. Eh, the acpidump from comment #1 seems to have valid info, but acpixtract cannot extract the tables from?!? Am I doing something wrong? Bob, do you mind giving it a try, please. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c4
Lin Ming
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c5
--- Comment #5 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c6
--- Comment #6 from Lin Ming
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c7
--- Comment #7 from Thomas Renninger
I tried the latest version 20110330 and it works. Argh, "less" automatically decompresses gzip/bzip2 'ed files and shows them in text format. file acpidump revealed that the data was compressed and uncompressing it let's acpixtract extract the files just fine, sorry for the noise.
The message comes from this part of the broken ECDT table: [03Ch 0060 4] UID : 00000000 [040h 0064 1] GPE Number : 00 [041h 0065 1] Namepath : "" GPE number and path to the EC in DSDT are zero, but should be (from the EC object from the DSDT): GPE Number : 0x17 Namepath : "\_SB.PCI0.LPCB.EC" The EC driver already seem to detect this situation correctly and successfully works it around. The message is not 100% correct, as it's an MSI notebook, but it complains about ASUSTek. As long as you do not experience further breakage, things should be fine: - Kernel should complain about the broken table (maybe more generic not mentioning asustek) - Try to set EC up from EC object in DSDT -> seem to work Andreas: Can you attach dmidecode as well, please. How old is this machine? We had some contacts to MSI recently, I can try to point them to this "easy to fix in BIOS" problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c8
--- Comment #8 from Andreas Hartmann
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c9
Thomas Renninger
Since I switched to kernel 2.6.38 We mostly stick to 2.6.37.X stable kernels. If there are patches you want to show up there, you could submit them yourself with the authors in CC if they are applicable: http://www.mjmwired.net/kernel/Documentation/stable_kernel_rules.txt
If you need bigger patches introducing new features, not suitable for stable@, the new Tumbleweed distribution might be what you search for, there you get a 2.6.38 build with all the external kernel modules you might need: http://en.opensuse.org/Portal:Tumbleweed I close this one won't fix, there is not much we can do, the kernel should still complain about the missing bits in the table. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c10
--- Comment #10 from Joey Lee
Joey: If you still have contacts to MSI you may want to forward this, hopefully they pick it up:
The ECDT table for early EC access is only half filled with valid info. The gpe no. and path to the EC object must be valid as well. On this machine it would be: GPE Number : 0x17 Namepath : "\_SB.PCI0.LPCB.EC"
This is a MSI CR620 BIOS Information Version: E1681IMS VER.10B Release Date: 10/21/2010
I keep in mind to enhance the error message a bit, it should be a FIRMWARE_BUG message, etc.
Sorry for I am late to reply this bug. Thank's for Thomas's help, I already send out mail to our PM Jeffrey and also transfer this information to MSI. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c11
--- Comment #11 from Joey Lee
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c12
--- Comment #12 from Andreas Hartmann
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c13
--- Comment #13 from Joey Lee
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c14
--- Comment #14 from Thomas Renninger
might need poke MSI customer services There should be no need. I expect Andreas' machine works fine or there should have been follow up errors. It's great that MSI fixed this in upcoming BIOSes though, to avoid possible issues that could arise.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c15
--- Comment #15 from Andreas Hartmann
might need poke MSI customer services There should be no need. I expect Andreas' machine works fine or there should have been follow up errors.
That's not the truth - this machine does have great trouble with hibernation: Ether the machine crashes during hibernation or it crashes during waking up after the image was reloaded (without any log entry in messages or else where) or it just reboots after waking up or I'm getting tons of different scheduling while atomic crashes in messages. I think they should really fix there fault - I payed for it! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
this machine does have great trouble with hibernation But this likely is another problem. I can't say for sure whether there might be a tiny bug/issue in the "work around" code paths. If there is, I can't see it. As ec.c does not have suspend/resume functions, you "should" only get in
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c16
--- Comment #16 from Thomas Renninger
Either the machine crashes during hibernation or it crashes during waking up after the image was reloaded Crashes means hard freeze, no interrupts anymore (e.g. CapsLock LED does not toggle on CapsLock key pressing?). If the machine is still responding a bit (e.g. keyboard LEDs), you might even be able to log in through ssh. In this case it's likely graphics cards related.
In either case, Rafael should be able to help you to find out more, but please use another bug to keep separated problems separated, it can still be set as a duplicate if it comes out that this really also is the root cause for hibernation not working. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c17
--- Comment #17 from Joey Lee
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c18
--- Comment #18 from Andreas Hartmann
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c19
--- Comment #19 from Joey Lee
I just want to report, that since kernel 2.6.37.6 and all other updates since the original openSuSE 11.4 packages the problems with s2disk and resume seem to be gone. The synaptics touchpad is always detected now and the graphics is usable now (but still has some minor problems: there are millions of "[33720.171720] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero." entries).
Please file a new bug for "*ERROR* fixme: max PWM is zero." entries).", then I
will cc. to Michael Chang, our drm expert to look at.
--- Comment #20 from Joey Lee
I just want to report, that since kernel 2.6.37.6 and all other updates since the original openSuSE 11.4 packages the problems with s2disk and resume seem to be gone. The synaptics touchpad is always detected now and the graphics is usable now (but still has some minor problems: there are millions of "[33720.171720] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero." entries).
Please file a new bug for "*ERROR* fixme: max PWM is zero." entries).", then I will cc. to Michael Chang, our drm expert to look at. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=681217
https://bugzilla.novell.com/show_bug.cgi?id=681217#c19
--- Comment #19 from Joey Lee
I just want to report, that since kernel 2.6.37.6 and all other updates since the original openSuSE 11.4 packages the problems with s2disk and resume seem to be gone. The synaptics touchpad is always detected now and the graphics is usable now (but still has some minor problems: there are millions of "[33720.171720] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero." entries).
Please file a new bug for "*ERROR* fixme: max PWM is zero." entries).", then I
will cc. to Michael Chang, our drm expert to look at.
--- Comment #20 from Joey Lee
I just want to report, that since kernel 2.6.37.6 and all other updates since the original openSuSE 11.4 packages the problems with s2disk and resume seem to be gone. The synaptics touchpad is always detected now and the graphics is usable now (but still has some minor problems: there are millions of "[33720.171720] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero." entries).
Please file a new bug for "*ERROR* fixme: max PWM is zero." entries).", then I will cc. to Michael Chang, our drm expert to look at. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com