https://bugzilla.novell.com/show_bug.cgi?id=758166 https://bugzilla.novell.com/show_bug.cgi?id=758166#c1 --- Comment #1 from Cristian Rodríguez 2012-04-19 21:16:36 CLT --- Created an attachment (id=487070) --> (http://bugzilla.novell.com/attachment.cgi?id=487070) This one is booting with nox2apic -- 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=758166 https://bugzilla.novell.com/show_bug.cgi?id=758166#c Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |crrodriguez@opensuse.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=758166 https://bugzilla.novell.com/show_bug.cgi?id=758166#c4 --- Comment #4 from Cristian Rodríguez 2012-05-10 17:27:10 CLT --- (In reply to comment #2)

Afaik (did not check now, but did some time ago) there is no possibility to override the apic mode via boot param for testing.

The option is x2apic_phys "x2apic_phys [X86-64,APIC] Use x2apic physical mode instead of default x2apic cluster mode on platforms supporting x2apic." already tested it before and in Rc6 where the patch you mentioned is already present, same 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=758166 https://bugzilla.novell.com/show_bug.cgi?id=758166#c6 --- Comment #6 from Thomas Renninger 2012-05-11 07:57:27 UTC ---

does the boot parameter "nox2apic" influences the output of acpidump? No.

I guess all that can be done then is to blacklist the machine to not use x2apic. Can you attach dmidecode, please. Would be interesting whether x2apic is enabled on Windows at all, but I have no idea how to check that. If possible you could provide boot messages with: apic=debug debug boot parameters added for reference. Maybe there is something suspicious, but this all points to bad HW/BIOS (looking for a BIOS update regularly is a good idea). -- 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=758166 https://bugzilla.novell.com/show_bug.cgi?id=758166#c8 --- Comment #8 from Cristian Rodríguez 2012-05-12 21:55:45 CLT --- (In reply to comment #6)

...

does the boot parameter "nox2apic" influences the output of acpidump? No.

I guess all that can be done then is to blacklist the machine to not use x2apic. Can you attach dmidecode, please.

Would be interesting whether x2apic is enabled on Windows at all, but I have no idea how to check that.

If possible you could provide boot messages with: apic=debug debug boot parameters added for reference. Maybe there is something suspicious, but this all points to bad HW/BIOS (looking for a BIOS update regularly is a good idea).

I will try to take a look on what windows is doing in that respect. -- 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=758166 https://bugzilla.novell.com/show_bug.cgi?id=758166#c11 --- Comment #11 from Cristian Rodríguez 2012-05-14 13:12:31 CLT --- (In reply to comment #9)

...

Also toggling this kernel option OFF: config IRQ_REMAP ... workarounds the problem... Have you compiled it out or have you just used the boot param intremap=off ?

Both.. booting with intremap=off says: "Enabled IRQ remapping failed" (or something similar I do not have the exact message in memory) When compiled without IRQ_REMAP It does say nothing about IRQ remapping.

That's weird or say a good finding: Booting with nox2apic also enables interrupt remapping: Enabled IRQ remapping in xapic mode (cmp. with your logs/dmesg in your snd attachment).

Yes, It goes into "legacy xapic" mode (according to the somehow convulted intel docs)

The logs there have some nice debug output. If it's somehow possible to get a failing boot with these "apic=debug acpi.debug_layer=0x400000 i8042.debug debug"

I already try that, even built the kernel to panic on soft/hard lockups, oppses, lockdep debugging etc.. and acpi either does not say a word and "hangs" without message, OR it continues booting with non-functional keyboard/touchpad, once I plug an external keyboard, I can use the system but without wifi @_@ .. as the Intel ucode for the iwlwifi driver fails to load... (that is extremely weird, because if I remove the driver, wait a few minutes and reload again, it works...)

as well, we would have something we can compare good vs bad in detail.

This could get a very nasty one.., I try to get some time for it, but as there is a workaround (nox2apic) and my queue is rather filled right now, it may take some time for the one or other answer.

No hurry, I have not yet seen any negative effect of the workaround and constantly checking for BIOS updates as I'm more and more convinced this is a BIOS bug. -- 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=758166 https://bugzilla.novell.com/show_bug.cgi?id=758166#c13 --- Comment #13 from Cristian Rodríguez 2012-10-13 00:28:30 CLT --- found the optimal workaround.. booting only with "acpi_backlight=vendor" fixes the 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=758166 https://bugzilla.novell.com/show_bug.cgi?id=758166#c15 --- Comment #15 from Thomas Renninger 2012-11-07 09:48:09 UTC --- Wow, interesting. Not sure, but it could have to do with these dmesg lines: drm: registered panic notifier [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS APIC error on CPU0: 00(80) : Illegal register address APIC error on CPU0: 80(80) : Illegal register address acpi device:2e: registered as cooling_device4 video: probe of LNXVIDEO:00 failed with error -5 acpi device:32: registered as cooling_device4 Iirc you already put acpidump somewhere, can you attach it to this bug as well, please. There is another video/graphics ACPI device defined which gets probed successfully: LNXVIDEO:01 Unfortunately I do not see an easy way how to force the video.ko driver to only probe the LNXVIDEO:01 and whether the machine is stable then (and the APIC errors do not show up) and backlight still works, etc. I could imagine there is an access to an APIC register which is not allowed in X2APIC mode and as you came that far already in limiting the source of the problem, I may be able to find it. Otherwise, if we cannot further root cause this, I would summarize this and submit the patch on linux-acpi@vger.kernel.org. Possibly there still someone has an idea or the workaround may get accepted if not. -- 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=758166 https://bugzilla.novell.com/show_bug.cgi?id=758166#c Ihno Krumreich changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Other |openSUSE 12.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.

http://bugzilla.novell.com/show_bug.cgi?id=758166 --- Comment #18 from Cristian Rodríguez --- This problem while still reproducible in -stable version 3.17.x appears to be resolved now. 3.18.0-rc4-3.g0521fb3-desktop is capable of booting the machine with no special parameters and no crazy wifi/keyboard behaviour. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=758166 --- Comment #20 from Cristian Rodríguez --- (In reply to Jiri Slaby from comment #19)

So can we close given 3.18 is now in stable and is going to factory?

Yeah, I am running linus' tree on the machine now and it works ok (SUSE kernel HEAD also fine) -- You are receiving this mail because: You are on the CC list for the bug.