http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c1 --- Comment #1 from Jon Nelson 2010-02-21 21:14:51 UTC --- Created an attachment (id=343684) --> (http://bugzilla.novell.com/attachment.cgi?id=343684) phone shot of boot screen -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c2 --- Comment #2 from Jon Nelson 2010-03-02 17:54:31 UTC --- More info: machine *does* boot on battery power. but after some point it will not. I would guess that point is 35% of battery life remaining, but it might be more or less than that. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c4 --- Comment #4 from Jon Nelson 2010-03-02 19:01:41 UTC --- Lenovo Thinkpad T61p I'll attach the other bits. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c6 --- Comment #6 from Jon Nelson 2010-03-02 19:03:06 UTC --- Created an attachment (id=346078) --> (http://bugzilla.novell.com/attachment.cgi?id=346078) acpidump > acpidump.out 2>&1 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c8 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Kernel AssignedTo|astarikovskiy@novell.com |kernel-maintainers@forge.pr | |ovo.novell.com Product|openSUSE 11.2 |openSUSE 11.3 Target Milestone|--- |Final --- Comment #8 from Jon Nelson 2010-07-08 23:56:47 UTC --- Freshly upgraded to openSUSE 11.3, kernel 2.6.34-12-desktop x86_64. Happened again, *5 times in a row*. Then I turned on the power strip. It *still* failed to boot, but only once. After that, it boots perfectly again. Battery life when it came up was 52%. Attaching photo of screen (2.6.34-12-desktop). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c10 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmh@hmh.eng.br AssignedTo|kernel-maintainers@forge.pr |astarikovskiy@novell.com |ovo.novell.com | --- Comment #10 from Thomas Renninger 2010-07-09 09:11:52 UTC --- DSDT.dsl tells: * OEM ID "LENOVO" * OEM Table ID "TP-7L " What kind of Lenovo is that? Can you attach dmidecode as well, please. Do you run the latest BIOS? Best double check for BIOS updates. In former times Lenovo also provided Embedded Controller firmware updates, best also check if such an update is available and install it. Eventually Henrique has heard about such problems already, sounds very much Lenovo specific... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

From the logs:

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c12 --- Comment #12 from Henrique de Moraes Holschuh 2010-07-13 14:50:21 UTC --- thinkpad_acpi: ThinkPad BIOS 7LETC6WW (2.26 ), EC 7KHT24WW-1.08 thinkpad_acpi: Lenovo ThinkPad T61p, model 64608VU BIOS page: http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67989 There is a new version there (2.27). Changelog doesn't look too interesting, but I know for a fact it doesn't list many of the fixes Lenovo usually does to a BIOS. If you remove ACPI battery support, and after that it works right every time, it is a kernel bug (in either battery or EC drivers). I recall some fixes to the battery and to the EC drivers that matter. Also, some of the later changes in ACPI area are causing problems with ThinkPads, I don't know what SuSE is shipping, but you might want to cross-check it with LKML and the ACPI ML. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c14 --- Comment #14 from Jon Nelson 2010-07-13 22:58:38 UTC --- Created an attachment (id=375744) --> (http://bugzilla.novell.com/attachment.cgi?id=375744) photo of failed boot with lots of acpi debug enabled -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c16 --- Comment #16 from Jon Nelson 2010-07-13 23:02:18 UTC --- With layer = 0xffffffff only, the last thing I see: nsload-0136 [00] ns_load_table : **** Completed Table Method Parsing and Object Initialization -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c18 --- Comment #18 from Thomas Renninger 2010-07-14 10:16:09 UTC --- Some corrections to my previous post: dmesg shows: ACPI: Added _OSI(Linux) So this one seem to be whitelisted to return true for _OSI(Linux) already. To try out the difference you can try: acpi_osi=!Linux Also I expect not the broken FACP2 table of Revision 2, but the working one of Revision 3 is used. But this one also has a defect: <4>[ 0.000000] ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 20090521 tbfadt-527 <4>[ 0.000000] ACPI Warning: Optional field Gpe1Block has zero address or length: 000000000000102C/0 20090521 tbfadt-558 Please make sure you have the latest BIOS first! Otherwise the patch I am going to attach should fix the Gpe1Block address/length by using the correct 64 bit structure. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c20 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jnelson-suse@jamponi.net --- Comment #20 from Thomas Renninger 2010-07-14 10:49:35 UTC --- Setting needinfo. Again: Please try with the latest BIOS, I don't want to change something if this is due to an already fixed BIOS. If you still see this, I can provide you with a kernel rpm to test. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c22 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jnelson-suse@jamponi.net --- Comment #22 from Thomas Renninger 2010-07-14 16:42:36 UTC --- A bit of another patch..., but can you try a kernel from here: ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/ But wait a day and check whether my change is included: Wed Jul 14 18:39:08 CEST 2010 - trenn@suse.de - patches.arch/acpi_fix_fadt_32_bit_zero_length.patch: Only use 32 bit addresses if they have a valid length (bug#581644). with rpm -qp --changelog kernel-xy.rpm |less on the downloaded rpm. You should then see in dmesg this line: <4>[ 0.000000] ACPI Warning: Optional field Gpe1Block has zero address or length: 000000000000102C/0 20090521 tbfadt-558 and an addtional: - not using it... hopefully this helps. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c24 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Robert.Moore@intel.com --- Comment #24 from Thomas Renninger 2010-07-20 08:11:17 UTC --- Thanks for the test! I am rather busy this week, I try to look into that asap. I expect (not sure of course) that the defect comes from the different 32 bit and 64 bit GPE1 block setup in your BIOS. For 64 bit an address and correct length of the gpe1 block register is provided, for the 32 bit it's not. The warning message: Optional field Gpe1Block has zero address or length: 000000000000102C/0 20090521 tbfadt-558 is already wrong, because it mixes up the 64 bit address and the 32 bit length value (zero). From what I've read from the code, the 64 bit address is still used (while 32 bit values are preferred), because the 32 bit address is zero. I tried to zero out the 64 bit address so that it does not get used, but I will double check whether I've overseen something. Eventually it's the other way around and the gpe1 block register must get used, but did not. In comment 10 I requested dmidecode output. Can you attach this as well, so that we know which system we are looking at. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=581644 http://bugzilla.novell.com/show_bug.cgi?id=581644#c26 --- Comment #26 from Jon Nelson 2010-07-20 12:59:01 UTC --- Created an attachment (id=377172) --> (http://bugzilla.novell.com/attachment.cgi?id=377172) dmidecode [w/updated bios] -- Configure bugmail: http://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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c28 --- Comment #28 from Jon Nelson 2010-08-20 04:12:46 UTC --- More info: Still a problem on openSUSE 11.3 Still a problem with openSUSE 11.3 Kernel-Of-The-Day (as of 2.6.35.1-1-desktop) Boots successfully with "acpi_osi=Linux". I can't confirm whether the "acpi_osi=Linux" thing will work *every* time, but so far 2 out of 2 work. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c29 --- Comment #29 from Thomas Renninger 2010-08-23 14:55:56 UTC ---

From dmesg: <5>[ 0.000000] ACPI: DMI detected: Lenovo ThinkPad T61 <5>[ 0.000000] ACPI: Added _OSI(Linux) That means acpi_osi=Linux should already be the default. acpi_osi=!Linux should make a difference (and there should be stated something in dmesg (dmesg |grep -i osi), that it got applied. Sorry, for not looking deeper earlier. Possibly you find a ACPI related BIOS option which makes a difference (ACPI version or similar). The gpe block declaration and the corresponding warning still looks very suspicious if I find the time I have another look at it. You may want to try above meanwhile or googling for the problem might be worth it, the T61p is a very common machine.

-- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c32 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #32 from Thomas Renninger 2010-12-08 10:49:11 UTC --- Some ideas: there is the very latest mainline kernel build here: ftp://ftp.suse.com/pub/projects/kernel/kotd/master/x86_64 you could install it via rpm -ivh kernel-desktop.rpm and kernel-desktop-base.rpm then the old kernel is kept and you can boot the old/original one again.

Despite being "powered", it would still not boot (and, interestingly, the backlight did not reset to "bright" when I plugged in the brick). Backlight is a good hint. Iirc someone else had problems booting recently and suspected it happens when the backlight is adjusted. Most likely it's the video.ko driver (together with the Intel graphics cards i915 driver if you have such a card) causing this. Possibly it may be the thinkpad-acpi driver doing backlight switching.

You could try to blacklist them in /etc/modprobe.conf.local: blacklist video blacklist thinkpad-acpi not sure whether this is enough for the video driver or whether it gets loaded due to dependencies to the graphics driver. You could try to move it away then from: mv /lib/modules/`uname -r`/kernel/drivers/acpi/video.ko /tmp and move it back later if you finished tests: mv /tmp/video.ko /lib/modules/`uname -r`/kernel/drivers/acpi -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c33 --- Comment #33 from Jon Nelson 2011-01-21 21:08:25 UTC --- Tried 2.6.37-39-desktop. Same problem. I don't think it's either video or thinkpad-acpi because when it fails to boot it's /long/ before module-loading time. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c35 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|jnelson-suse@jamponi.net | --- Comment #35 from Jon Nelson 2011-08-05 17:53:53 UTC --- Trying out kernel 3.0 (by virtue of tumbleweed for 11.4) and have the same problem. Won't boot on battery at times. I note that if I pass (note the typo!): acpi_debug_level=0xffffffff (instead of acpi.debug_level=....) it boots. Every time. I'm going to reboot again into 3.0 and try a few other things. This has been a problem since 11.3. Any more thoughts on what might be causing this? -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c37 --- Comment #37 from Len Brown 2011-08-05 21:42:27 UTC ---

nvidia: module license 'NVIDIA' taints kernel.

does it still fail with this tainting removed? I have a t61 with i915 graphics, and it works fine. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c39 --- Comment #39 from Jon Nelson 2011-08-05 21:46:13 UTC --- Well, it fails long, long before it loads any modules. Also, I've been using the nouveau driver since openSUSE 11.4 came out, and the proprietary module has not been installed since then. The kernel does not report that it is tainted any longer. With kernel 3.0, the last line I see is: ACPI: Core revision 20110413 When it boots successfully, dmesg reports this as the first line to follow: .TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c41 --- Comment #41 from Jon Nelson 2011-08-06 02:57:34 UTC --- I gave 'max_cpus=1'. No change. Per comment 13 I tried 'noacpi', 'noacpi noapic nolapic' (all together). I'll try 'noapic', 'nolapic', and 'nolapic_timer' shortly. I *did* notice that if I get the battery down enough that it starts flashing and beeping (orange flashing) that I can boot again -- at least, it worked once. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c43 --- Comment #43 from Jon Nelson 2011-08-06 19:08:31 UTC --- kernel built right out of the linux-2.6 git tree -- de96355c111679dd6e2c5c73e25e814c72510c58 -- no luck. It was built with ACPI_DEBUG off No change. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c47 Len Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |jnelson-suse@jamponi.net --- Comment #47 from Len Brown 2011-08-08 15:10:51 UTC ---

I gave 'max_cpus=1'. No change.

Do you mean the cmdline parameter "maxcpus=1"? -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c49 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |jnelson-suse@jamponi.net --- Comment #49 from Thomas Renninger 2011-08-09 21:28:29 UTC --- You have an XSDT and an RSDT table each probably pointing to another FACP/FADT (same table, acpidump names them FACP, also called FADT): XSDT -> FACP1 -> Revision 3 (used by default) RSDT -> FACP2 -> Revision 2 Two things you could try: 1) Prefer RSDT over XSDT FACP2 is somehow broken or at least iasl has problems disassembling it and I get at the end: [080h 0128 1] Value to cause reset : 06 **** ACPI table terminates in the middle of a data structure! // ACPI Warning: FADT revision 2 does not match length: found 81 expected 84 Still you should easily give this a try by passing: acpi=rsdt boot parameter, let's see what happens. 2) Fix values in FACP1 Iirc the 32 bit values are prefered over the 64 bit ones because we expect Windows is (afaik was) doing it, but Linux ACPI code still double checks whether they are equal. That's were the warnings are coming from you mentioned in comment #46: The GPE1 block is defined in the 64 bit structures, but not in the 32. Iirc this will result in ignoring the GPE1 block. I'll attach a fixed FACP/FADT which defines the GPE1 block for the 32 bit address as well and equal to the 64 bit address GPE1 block declaration. I'll attach some code which allows you to let the kernel make use of the fixed FADT. I hope it works, you should see a message that the FADT got overridden and the warning messages you pointed to should vanish. The patches you need should apply on 3.0 hopefully also on latest 3.1 kernels: https://patchwork.kernel.org/patch/918412/ https://patchwork.kernel.org/patch/918402/ If you have the newly compiled kernel in place copy the instrumented FADT which I am going to attach and for example name it test_initrd: cp /tmp/FACP1.aml /boot/test_initrd then put the initrd you would have used on top of it: cat /boot/initrd >>/boot/test_initrd and let your bootloader use the new kernel (with above two patches applied) and the newly created, instrumented /boot/test_initrd as initrd. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c51 --- Comment #51 from Robert Moore 2011-08-09 21:45:59 UTC --- [000h 0000 4] Signature : "FACP" [Fixed ACPI Description Table] [004h 0004 4] Table Length : 00000081 [008h 0008 1] Revision : 02 Yep, there's no such thing as an FADT with a length of 0x81. The rev 2 FADT is supposed to be length 0x84 -- thus the warning. Fortunately, in this case, the missing 3 bytes are reserved, so no harm is done. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c53 --- Comment #53 from Jon Nelson 2011-08-10 04:00:18 UTC --- acpi=rsdt -> no luck compiling kernel now, will try the modified facp when I'm able. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c55 --- Comment #55 from Jon Nelson 2011-08-10 14:31:23 UTC --- If I use the initrd /without/ the facp pre-pended, it boots fine. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c57 --- Comment #57 from Thomas Renninger 2011-08-10 15:25:58 UTC ---

I've added Yes, perfect. Sorry for the early code, I plan to clean this up and will repost (the patch was initially marked as RFC, but "should" work). But I don't have time cleaning up and reposting right now.

You should see a "FACP" or "FADT" overridden really early (with your "addon"). It now should also find the initrd again where the disk/lvm drivers are in. If not the override may still have been successful and unpacking the initrd and trying to load the disk driver should come after the boot hang. So, if the machine does not hang anymore that early and you see the "override message", the overriding worked and it was the GPE1 block not being defined in the 32 bit address declarations... -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c59 --- Comment #59 from Jon Nelson 2011-08-10 20:10:50 UTC --- I've added a bunch more printk(KERN_INFO....) to that drivers/acpi/osl.c and even tried hard-coding the offset at 244 -- no luck. Nothing I try seems to get past the EDD detection. To be absolutely clear: the "new" initrd is the attachment: bug-581644_FACP1.modif.aml (244 bytes - what the dsl claims the table is as well) with the results from "mkinitrd" *appended* to it directly, right? -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c61 --- Comment #61 from Jon Nelson 2011-08-12 13:38:45 UTC --- So here is an update. I've modified the patches extensively, and can now override *most* but not *all* of the ACPI tables. As an example, I can override these: APIC, ASF!, BOOT, DSDT, ECDT, FACS, HPET, MCFG, RSDP, SSDT1, SSDT2, SSDT3, SSDT4, SSDT5, TCPA, and XSDT. However, If I override the FACP table, with the modified version or the /exact/ version pulled out of existing ACPI tables, the boot hangs. I'll be modifying the patches a bit more. Would you be interested in the changes I've made? -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c63 --- Comment #63 from Jon Nelson 2011-08-12 15:04:19 UTC --- (In reply to comment #62)

...

I'll be modifying the patches a bit more. Would you be interested in the changes I've made? Definitely!

The patches are currently a bit rough, and I have tried several different approaches. Please allow me some time to clean them up a bit, but would you prefer to collaborate out-of-band (ie, email) on this for now? It might be easier.

One idea I had is to copy the table data away from initrd (and get the fully initrd memory released). My idea for a cleaned up version was to: - memblock_find_in_range() - memblock_x86_reserve_range() - copy the ACPI table(s) in there - increase initrd_start pointer to the starting address of the real initrd/cpio - make sure initrd including (already copied away) ACPI tables are freed here: /arch/x86/mm/init.c:free_initrd_mem()

There is a acpi=copy_dsdt boot param, I wanted to have a look what they are doing there...

Ahh. Nice. I'll look at that, as well as the above approach. I also tried alloc_bootmem, kalloc, and a few others.

Hope this helps. I hope to be able to spend some time on this next week.

Your efforts are very much appreciated!

No, Sir, *your* efforts are very much appreciated! -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c65 --- Comment #65 from Rafael Wysocki 2011-08-12 21:36:25 UTC --- (In reply to comment #49)

2) Fix values in FACP1

Iirc the 32 bit values are prefered over the 64 bit ones because we expect Windows is (afaik was) doing it, but Linux ACPI code still double checks whether they are equal. That's were the warnings are coming from you mentioned in comment #46: The GPE1 block is defined in the 64 bit structures, but not in the 32. Iirc this will result in ignoring the GPE1 block.

It shouldn't. The code in tbfadt.c only uses 32-bit values if they are nonzero. However, they are preferred over 64-bit values if both are nonzero. -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c67 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|jnelson-suse@jamponi.net | --- Comment #67 from Jon Nelson 2011-08-13 05:07:58 UTC --- (In reply to comment #66)

(In reply to comment #55)

...

If I use the initrd /without/ the facp pre-pended, it boots fine.

Does your kernel with the patches from comment #65 applied boot correctly with a normal initrd?

No. relocate_initrd - in 918402.patch - hangs because (at least in my case) the kernel is /already/ in lowmem (there might also be something funky with relocate_initrd -- in any case, it's not being used here). As I noted earlier, I've extensively re-worked the patches. I have something working now. One thing to note: I seem to be able to successfully override most (if not all) of the acpi tables, *except* FACP. If I override FACP, even with the un-recompiled table, it hangs at boot. The last thing I see is the EDD... ok message. The other tables I am able to override, so far. Why might I not be able to override FACP? I hope to clean up what I've got and make it available. I resorted to using an older trick -- a "magic string" *appended* to the initrd marks the (potential) start of ACPI override tables -- this makes it easier to duplicate the tables in lowmem without causing problems freeing the initrd later. Everything seems to work except FACP. :-( Thoughts or suggestions? -- 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=581644 https://bugzilla.novell.com/show_bug.cgi?id=581644#c69 --- Comment #69 from Jon Nelson 2011-10-21 14:19:21 UTC --- It's been a while, and I have a shiny new laptop (T520i, which is awesome). I still have, for now, the T61p and it is now running openSUSE 12.1 (factory). Still won't boot on battery. Suggestions? -- 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.