http://bugzilla.novell.com/show_bug.cgi?id=623393 http://bugzilla.novell.com/show_bug.cgi?id=623393#c1 --- Comment #1 from Markus Kohm 2010-07-19 10:03:40 UTC --- PS: Without Step 2 it boot hangs too, but you'd get no informations after "[Linux_initrd @ 0x37530000, 0xabf360 bytes]" -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c2 Tony Jones changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |tonyj@novell.com InfoProvider| |jabber@gmx.org --- Comment #2 from Tony Jones 2010-09-24 20:29:33 UTC --- Hello. Are you still experiencing this issue? -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jabber@gmx.org | -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c5 Markus Kohm changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jabber@gmx.org | --- Comment #5 from Markus Kohm 2010-10-09 20:45:39 UTC --- Last message with initcall_debug is: [0.743857] calling acpi_init+0x0/0xdc @ 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c7 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None --- Comment #7 from Jiri Slaby 2010-10-16 08:49:35 UTC --- The priority is changed by assigned developers. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c Markus Kohm changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Enhancement |Critical -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c10 Markus Kohm changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jabber@gmx.org | --- Comment #10 from Markus Kohm 2010-10-20 10:19:06 UTC --- (In reply to comment #9)

Can you also try the SLE11 SP1 kernel matching your system configuration from:

http://ftp.suse.com/pub/projects/kernel/kotd/SLE11-SP1/

I'd like to verify if the regression appeared in 2.6.32 already or later.

Same problem with kernel-debug-2.6.32.23-0.3.99.7.22ef0dd.i586.rpm and kernel-default-2.6.32.23-0.3.99.7.22ef0dd.i586.rpm: hard lock after "calling acpi_init" message. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c11 Rafael Wysocki changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jabber@gmx.org --- Comment #11 from Rafael Wysocki 2010-10-20 22:18:09 UTC --- Can you try boot an affected kernel with "acpi_osi=" (no value) in the command line and see if that helps? -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c13 Markus Kohm changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jabber@gmx.org | --- Comment #13 from Markus Kohm 2010-10-21 11:04:17 UTC --- (In reply to comment #11)

Can you try boot an affected kernel with "acpi_osi=" (no value) in the command line and see if that helps?

Tried with debug kernel 2.6.34 and 2.6.32.23. No change, still hard lock after "calling acpi_init". After this I've also added acpi.debug_layer=0xffffffff acpi.debug_level=0xffffffff again using 2.6.32.23 and got a lot of additional messages. I made a screen photo and attached 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.

https://bugzilla.novell.com/show_bug.cgi?id=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c15 --- Comment #15 from Rafael Wysocki 2010-10-21 22:01:57 UTC --- Also, please attach the output of dmesg from the good one. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c17 Markus Kohm changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jabber@gmx.org | --- Comment #17 from Markus Kohm 2010-10-26 07:17:45 UTC --- Created an attachment (id=396981) --> (http://bugzilla.novell.com/attachment.cgi?id=396981) output of dmesg, lspci, dmidecode with 2.6.31 and 2.6.34 I've made the requested data. You may find the outputs made with "good" kernel 2.6.31 using acpi at logs/acpi and the outputs made with "bad" kernel 2.6.34 with acpi=off at logs/noacpi. I've used kernel 2.6.34 instead of 2.6.32 because I'm using ext4 and I haven't found an ext4 kernel module at the SLE kernel-debug.rpm and kernel-debug-base.rpm. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c19 Markus Kohm changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jabber@gmx.org | --- Comment #19 from Markus Kohm 2011-01-05 12:20:37 UTC --- Created an attachment (id=407035) --> (http://bugzilla.novell.com/attachment.cgi?id=407035) dmesg output with 2.6.34 and 2.6.37 without initcall_debug (In reply to comment #18)

1. Have you tried booting with acpi=noirq instead acpi=off ?

Yes. Same hard lock problem. I've tried out every setting of acpi option and only acpi=off or acpi=ht (not ith 3.6.37, see below) boot.

2. Please attach dmesg from 2.6.34.y with acpi=ht and _without_ initcall_debug or ACPI debug options.

I've done so with kernel 2.6.34. With kernel 2.6.37 I've made the dmesg output with acpi=off.

3. Can you try the latest kernel from: http://ftp.suse.com/pub/projects/kernel/kotd/master/ matching your system configuration and see if the problem is still there?

The problem is even worse. With kernel 2.6.37 from there, I cannot longer boot with acpi=ht. With this option I get a hard lock after "bio: create slab <bio-0> at 0". But acpi=off still boots. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c21 Rafael Wysocki changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |trenn@novell.com --- Comment #21 from Rafael Wysocki 2011-01-12 23:52:29 UTC --- @Thomas: Why do you think that's \SB_.PCI0.AGPB.VGA0._INI() ? It looks like that might be EC0._Q80 or EC0._Q81 as well, doesn't 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.

https://bugzilla.novell.com/show_bug.cgi?id=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c23 --- Comment #23 from Rafael Wysocki 2011-01-13 00:07:33 UTC --- Created an attachment (id=408109) --> (http://bugzilla.novell.com/attachment.cgi?id=408109) EC: Skip DSDT scan @Markus: Does this patch on top of 2.6.37 make any difference (without acpi=off)? -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c24 Markus Kohm changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jabber@gmx.org | --- Comment #24 from Markus Kohm 2011-01-14 13:15:24 UTC --- (In reply to comment #23)

Created an attachment (id=408109) --> (http://bugzilla.novell.com/attachment.cgi?id=408109) [details] EC: Skip DSDT scan

@Markus: Does this patch on top of 2.6.37 make any difference (without acpi=off)?

Sorry, needed some time to compile and install the patched new kernel (first compilation failed after about 4 hours because of missing space on partition). But it no difference. Still hard lock after "bio: create slab <bio-0> at 0" without acpi=off. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c26 --- Comment #26 from Rafael Wysocki 2011-01-14 22:57:52 UTC --- OK, thanks. I wonder what happens if you comment out the acpi_bus_osc_support() entirely? Anyway, can you please file a bug at http://bugzilla.kernel.org in the ACPI category for this issue and add the address rjw@sisk.pl to the CC list? That will help engage some upstream ACPI developers in the debugging of this issue. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c27 --- Comment #27 from Markus Kohm 2011-01-19 08:30:44 UTC --- I'll test commenting out acoi_bus_osc_support() soon. Currently I've done some more tests and after adding a counter, I've found out, that the 35th call of acpi_init_one_device does not return from acpi_ns_evaluate. With even /* * Because of an earlier namespace analysis, all subtrees that contain an * _INI method are tagged. * * If this device subtree does not contain any _INI methods, we * can exit now and stop traversing this entire subtree. */ /* MKOHM: EXIT FROM THIS TREE, if it is the 35th call of * acpi_init_one_device */ if ( (device_number == 35) || !(device_node->flags & ANOBJ_SUBTREE_HAS_INI)) { printk( KERN_INFO "return\n" ); return_ACPI_STATUS(AE_CTRL_DEPTH); } at acpi_init_one_device, Linux does boot! After boot Num-Lock is active but system seems to work. I know device_node->type is 6 and nesting_level is 4. So: How can I find out more information about 35th device? For bugzilla.kernel.org I fist have to create a account. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c29 --- Comment #29 from Thomas Renninger 2011-01-21 13:05:38 UTC --- Function acpi_init_one_device does not exist, there only is acpi_ns_init_one_device in drivers/acpi/acpica/nsinit.c If you would have attached a real diff, I could have find out where you placed the code from comment #28... Anyway, if it's really this, something might go wrong when the _STA or _INI function of the affected device is called... If it's really this function you could also place a debug print at the beginning like at the end: ACPI_EXCEPTION((AE_INFO, status, "during %s._INI" "execution",scope_name)); then we would know which device exactly is no. 35. This should be enough already. If not, you can also run with: acpi.debug_layer=0xFFFFFFFF acpi.debug_level=0x20F log_bug_len=16M boot parameters and should get quite some additional output. But as said, knowing about the device might be enough. You can then try to do: acpidump >acpidump acpixtract acpidump acpiexec DSDT.dat in acpiexec shell, find the _STA and _INI method path of the bad device via: methods and then execute them: execute ..._INI execute ..._STA I expect this will work, it's more likely that a HW access inside of these cause the hang and acpiexec in userspace cannot access HW. But possibly you already get a warning/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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c30 --- Comment #30 from Markus Kohm 2011-01-28 07:33:56 UTC --- Created an attachment (id=410919) --> (http://bugzilla.novell.com/attachment.cgi?id=410919) crude patch to trace acpi_ns_init_one_device and prevent 35th call of 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.

https://bugzilla.novell.com/show_bug.cgi?id=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c32 --- Comment #32 from Thomas Renninger 2011-01-28 15:03:43 UTC --- It's the VGA._INI method.

From the picture you provided it's hanging when trying to write 0xE3 to APMC. This is the \SB.GSMI function which is called at various places (before entering suspend in _PTS, when exiting suspend in _WAK and in notification handlers(_Lxx).

But it's only called in one INI func: VGA. This "looks" unrelated to EC, but it seems the HW is in a state a possible SMI call (GSMI?!?) does not like. But the new kernel mode setting should be far after this happens, so this cannot be it. What you can try to verify above is to compile the modified DSDT I'll attach into your kernel. You have to place the file into your kernel sources in drivers/acpi/DSDT.hex and then point to it via compile options in .config CONFIG_ACPI_CUSTOM_DSDT_FILE="DSDT.hex" CONFIG_ACPI_CUSTOM_DSDT=y It should not hang (at least not at the same place) anymore... -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #411024|1 |0 is patch| | -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c35 --- Comment #35 from Thomas Renninger 2011-01-28 23:39:16 UTC --- Not sure whether it's time to cheer already. I have no idea why that helps or how to properly fix that. Can you try a S3 cycle, please or do a AC adapter un/re-plug. These are code paths which also call \_SB.GSMI, but with other values. If that helps, I'd say the GSMI method is to pass a specific value to SMI calls (not sure). And it only fails on value 0x6: Method (_INI, 0, NotSerialized) { \_SB.GSMI (0x06) No idea how to find out why and always overriding DSDT is cumbersome... -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c37 --- Comment #37 from Markus Kohm 2011-01-29 14:27:46 UTC --- S3 (powersave -u) results in a lock. But S3 never worked with Linux and this Notebook. Unplugging or replugging the AC adapter results in a lock and this is a problem. I've spend several days in November in bisecting. Unfortunatly I've had several problems compiling or booting. It was very frustrating, when the compilation failed after 4 or 5 hours or the boot resulted in new errors or locks in different states. Changing the configuration sometimes solved the problem, sometimes resulted in others. So at least I've finished the try with no result. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c39 --- Comment #39 from Markus Kohm 2011-01-30 16:25:28 UTC --- (In reply to comment #38)

Can you blacklist the preloadtrace driver, please.

The preloadtrace driver was never installed for kernel 2.6.37. And lsmod | grep preload showed nothing. Nevertheless I've blacklisted it now, created new initrd and nothing changed. Hard while booting without your patch, or while unplugging/replugging AC adapter with your patch. BTW: I think the hard lock while booting is before usage of 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c41 --- Comment #41 from Thomas Renninger 2011-01-30 22:52:39 UTC --- The quirk is a red herring. git log reveals that it's in there since git history. It also only reserves the io ports for non-acpi kernel drivers and the machines hangs even before the quirk gets active. I'll attach dmesg of the working 2.6.31.14 kernel. If you upload dmesg of the recent kernel we could compare whether there is something obvious. But I cannot see anything before ACPI initialization which could cause this. Another idea could be to boot both (now) working kernels with increased acpi.debug_{level,layer} boot params and compare, but there will be quite some output... You could try to read up the chipset documentation and find out about the IO byte which causes the hang (writing 0xE3 to IO port 0x102F) which would probably still not explain why it worked with older kernels, but may give a pointer for what we are searching. I'll also upload another DSDT.hex with the GSMI function emptied. You should then be able to (un)plug AC, etc. Above might all end up without much of a result. Most promising, but cumbersome is a git bisect... -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c43 --- Comment #43 from Thomas Renninger 2011-01-30 22:55:22 UTC --- Created an attachment (id=411153) --> (http://bugzilla.novell.com/attachment.cgi?id=411153) Another modified DSDT with GSMI totally emptied - AC plugging might work with 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.

https://bugzilla.novell.com/show_bug.cgi?id=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c45 --- Comment #45 from Markus Kohm 2011-02-01 11:20:46 UTC --- Created an attachment (id=411484) --> (http://bugzilla.novell.com/attachment.cgi?id=411484) git bisect log Result of "git bisect log" after termination of several "git bisect ...", make, reboot cycles. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c49 Markus Kohm changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|jabber@gmx.org | --- Comment #49 from Markus Kohm 2011-02-02 11:03:41 UTC --- (In reply to comment #46)

a) The above patch is in 2.6.36 onwards and the previous comments seem to say kernels above 2.6.36 also has the same problem. is that correct?

Even kernel 2.6.37 has the problem.

b) this MTRR rendezvous patch should affect only the systems which have multiple logical cpus (and the fix is addressed by 68f202e4e87cfab4439568bf397fcc5c7cf8d729) and your system seem to have only one logical cpu. Correct?

Correct, but I often see messages like "weird, boot CPU (#0) not listed by the BIOS." Don't know, if this is part of the problem. (In reply to comment #48)

I've built and copied i386 kernel flavors with the bisected patch reverted here: ftp.suse.com/pub/people/trenn/bug_623393_mtrr_rendezvous_patch_reverted (if not already it should get synced and show up there in some hours).

I've tried your desktop kernel (to avoid removing my working default kernel 2.6.31) and it was able to boot. WLAN with WPA2-PSK does not work, but I hope this is only a configuration problem. Was this the same patch Suresh proposed or should I try this one too (compiling my own kernel)? Would it be a solution to remove COMFIG_SMP? -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c51 Markus Kohm changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|jabber@gmx.org | --- Comment #51 from Markus Kohm 2011-02-02 17:40:06 UTC --- I've tried Suresh's patch with kernel 2.6.36. Currently I'm working with this patched kernel. So I can say: It works! I've also tried to compile a 2.6.38 kernel with this patch, but get an error while build (not at the patches module but at selinux compilation). I'll disable selinux and try it again, but I need at least 6 hours for "make all". Is it enough to try "make i386_defconfig; make isolinux" and boot this from CD (which will fail on searching root)? If you need to know, if unplugging/replugging of AC adapter works, or you need a dmesg, I need to build a full kernel and install it.

and find it's way into 11.4 kernel pretty soon.

That would be great! -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c53 Suresh Siddha changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|suresh.b.siddha@intel.com | --- Comment #53 from Suresh Siddha 2011-02-02 21:25:37 UTC --- First of all thanks to Markus for bisesting and test results. Second of all this issue will be hit on UP systems where the bios doesn't setup certain tables properly. Hence we didn't see similar failures so far. (In reply to comment #52)

Hm, with Suresh patch from comment #47 you also get: set_mtrr_aps_delayed_init for UP machines.

that call is just an init code, which actually makes sure that we don't touch the boot cpu's mtrr's later down in the boot path. I will think of a clean and simple patch to fix this issue.

...

I've tried Suresh's patch with kernel 2.6.36. Currently I'm working with this patched kernel. So I can say: It works!

Thanks for testing it out Markus.

Is that enough for you Suresh? Do you plan to submit this patch upstream and eventually to stable@?

Yes. Will do that mostly by end of day today and will update this bug with my lkml post once I did that.

I can already push it into our kernel and it should still show up in 11.4. I still like to wait for statement from Suresh, though.

Can you wait for couple of more days till the patch gets accepted into -tip tree? At that moment, you can take the patch into your distro. thanks. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c55 --- Comment #55 from Markus Kohm 2011-02-03 07:02:47 UTC --- Tonight the build of a new kernel (master) with Suresh's FIRST patch was successful. Currently it's running: Linux aspire1310.site 2.6.38-rc3-debug+ #2 SMP Thu Feb 3 00:11:23 CET 2011 i686 athlon i386 GNU/Linux (In reply to comment #54)

I posted a different patch to address this. Markus can you please double check one more time to see if it fixes your issue and Ack it on lkml if it works for you?

Yes, I'll do this today (or tonight, depending on the duration; hope it will compile fast because only few files should be recompiled). Is it OK, if I'll post the Ack without being subscribed to lkml? (BTW: My last name ends up with "m" not "n". But doesn't matter, fixing the kernel problem is much more important. You and the other guys do a real great job!) -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c57 --- Comment #57 from Rafael Wysocki 2011-02-03 19:56:25 UTC --- OK, Suresh, thanks a lot for taking care of this! Do you think it might be possible to fix suspend/resume on this machine? Markus, thanks a lot for the assistance! The patch should go into the mainline and stable kernels shortly. In the meantime I'll put it into the openSUSE 11.3 and opensSUSE 11.4 kernel branches. -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c59 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com --- Comment #59 from Marcus Meissner 2011-03-08 13:26:56 UTC --- We have just released a kernel update for SLE 11 SP1 mentioning/fixing this issue. The released kernel version is 2.6.32.29-0.3.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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c61 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |987 |987 | |maint:released:sle11-sp1:38 | |986 --- Comment #61 from Swamp Workflow Management 2011-03-08 15:02:45 UTC --- Update released for: btrfs-kmp-default, btrfs-kmp-ppc64, cluster-network-kmp-default, cluster-network-kmp-ppc64, ext4dev-kmp-default, ext4dev-kmp-ppc64, gfs2-kmp-default, gfs2-kmp-ppc64, kernel-default, kernel-default-base, kernel-default-debuginfo, kernel-default-debugsource, kernel-default-devel, kernel-default-extra, kernel-ppc64, kernel-ppc64-base, kernel-ppc64-debuginfo, kernel-ppc64-debugsource, kernel-ppc64-devel, kernel-ppc64-extra, kernel-source, kernel-source-debuginfo, kernel-source-vanilla, kernel-syms, kernel-trace, kernel-trace-base, kernel-trace-debuginfo, kernel-trace-debugsource, kernel-trace-devel, kernel-trace-extra Products: SLE-DEBUGINFO 11-SP1 (ppc64) SLE-HAE 11-SP1 (ppc64) SLE-SERVER 11-SP1 (ppc64) -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c63 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |987 |987 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |986 |986 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |985 |985 | |maint:released:sle11-sp1:38 | |988 --- Comment #63 from Swamp Workflow Management 2011-03-08 15:37:45 UTC --- Update released for: btrfs-kmp-default, btrfs-kmp-xen, cluster-network-kmp-default, cluster-network-kmp-xen, ext4dev-kmp-default, ext4dev-kmp-xen, gfs2-kmp-default, gfs2-kmp-xen, hyper-v-kmp-default, kernel-default, kernel-default-base, kernel-default-debuginfo, kernel-default-debugsource, kernel-default-devel, kernel-default-devel-debuginfo, kernel-default-extra, kernel-desktop-devel, kernel-ec2, kernel-ec2-base, kernel-ec2-debuginfo, kernel-ec2-debugsource, kernel-ec2-devel, kernel-ec2-devel-debuginfo, kernel-ec2-extra, kernel-source, kernel-source-debuginfo, kernel-source-vanilla, kernel-syms, kernel-trace, kernel-trace-base, kernel-trace-debuginfo, kernel-trace-debugsource, kernel-trace-devel, kernel-trace-devel-debuginfo, kernel-trace-extra, kernel-xen, kernel-xen-base, kernel-xen-debuginfo, kernel-xen-debugsource, kernel-xen-devel, kernel-xen-devel-debuginfo, kernel-xen-extra Products: SLE-DEBUGINFO 11-SP1 (x86_64) SLE-DESKTOP 11-SP1 (x86_64) SLE-HAE 11-SP1 (x86_64) SLE-SERVER 11-SP1 (x86_64) SLES4VMWARE 11-SP1 (x86_64) -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c65 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |987 |987 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |986 |986 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |985 |985 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |988 |988 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |984 |984 | |maint:released:sle11-sp1:38 | |995 --- Comment #65 from Swamp Workflow Management 2011-03-08 18:09:43 UTC --- Update released for: kernel-default-extra, kernel-xen-extra Products: SLE-SERVER 11-EXTRA (x86_64) -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c67 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |987 |987 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |986 |986 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |985 |985 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |988 |988 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |984 |984 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |995 |995 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |993 |993 | |maint:released:sle11-sp1:38 | |991 --- Comment #67 from Swamp Workflow Management 2011-03-08 20:10:24 UTC --- Update released for: kernel-default-extra, kernel-ppc64-extra Products: SLE-SERVER 11-EXTRA (ppc64) -- 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=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c69 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |987 |987 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |986 |986 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |985 |985 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |988 |988 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |984 |984 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |995 |995 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |993 |993 |maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |991 |991 Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |989 |989 | |maint:released:sle11-sp1:38 | |990 --- Comment #69 from Swamp Workflow Management 2011-03-08 22:11:24 UTC --- Update released for: kernel-default-extra Products: SLE-SERVER 11-EXTRA (ia64) -- 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.