Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[hw bug][i7-8750H][linux][lenovo-laptop] AE_AML_OPERAND_TYPE OpcodeName unavailable

Offen
#49 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
15/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
linux

Rechercherichtung

Beginne mit der bereitgestellten Kernel-.config, den gemeldeten dmesg-Auszügen und den aus den Quellen gebauten Kerneln 5.8.7, 5.9.9 und 5.9.11 im Vergleich zum funktionierenden Debian-Kernel. Reproduziere den Freeze und zeichne dabei die Meldungen von ACPI, i915, microcode und Eingabegeräten auf; abgeschlossen ist die Aufgabe, wenn ein reproduzierbarer Unterschied isoliert und die relevante Konfiguration, Firmware und die Logs dokumentiert sind.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Hello.

Last few days I'm trying to update my linux kernel to 5.8.7 from source.
So, I spend a lot's of time to configure the kernel, but, after reboot it always fall.

First what i noticed was strange sound from motherboard after grub start initdr. like sound of
beeping power supply when it not plugged to device.
Input devices don't work, so, i can't enter my LUKS pw.
image

Then, after a lot's of times of compilation the kernel and including all drivers - I'm get able to enter LUKS password, and start boot. When i see Xorg and KDE w lightdm screen - keyboard and touchpad dont react at all. only blinking cursor in user field.
And, after 10 seconds deadlock or full freeze. nothing, only hard reset via power button. And strange beeping all the time.

So, I try to recompile kernel with debug output and boot-tracing options.

Here is one moment - after one of my trying I check BIOS and was happy a lot! - in the BIOS appear "Advanced" tab.
image
Even JTAG configuration appears!
image
image
WOW!

So, closer to bug. When I boot with trace I see next:
image

May be it can be some mitigation technique? I'm talking about UEFI certs and my setup, where I'm using old good legacy.
By the way, in kernel options I try both y/n on cert's support - with no luck.

So, I enable few configuration options, like:

CONFIG_LEDS_APU=y
CONFIG_PCENGINES_APU2=y

compile, install modules, install, update initramfs, reboot, and:
video device with shadowed rom?
image interesting, but not now 👍
Ah! about max_cpu_qlen
image
In menuconfig I read that I can set it to 1000 for best latency. After a lot's of falls I set it to 300 - but it change nothing.

Okey, I give it drivers to usb and hid devices.
I give it all drivers which can be used it my setup.
And, i enable reboot on hangs/freezes and freezes/hangs detector in kernel debug or kernel hacking menu.
Also, some more ktrace were enabled.

image
1)
image
2)
image
3)
image
and boom! system halted!
As I understand - reboot on hangs/freezes works.

The most strange is fact, that I'm using at the moment pre-build 5.8.7 kernel.
And this is how it boot on current kernel - on which one I'm now typing this post:
Linux o 5.8.0-1-amd64 #1 SMP Debian 5.8.7-1 (2020-09-05) x86_64 GNU/Linux
installed from debian repo as binary package.
image

The same kernel version builded from src - hangs.
I try 5.9.9 and 5.9.11 and 5.8.7 builded from source - the same story. Freeze/hang.
The last few trys were builded with default (from /boot/config) configuration of working kernel from debian repo!
The only one effect is that BIOS is default again :(
I really don't have full understanding how I enables that feature. I think is somewhere in

Cpuidle Driver for Intel Processors
or
CPU Frequency scaling

image

All the time my firmware were:

[    0.000000] microcode: microcode updated early to revision 0xd6, date = 2020-04-27
[    1.205619] microcode: sig=0x906ea, pf=0x20, revision=0xd6
[    1.205929] microcode: Microcode Update Driver: v2.2.

and just now I update it to:

[11406.202370] platform microcode: firmware: direct-loading firmware intel-ucode/06-9e-0a
[11406.207868] microcode: updated to revision 0xde, date = 2020-05-25
[11406.207910] microcode: Reload completed, microcode revision: 0xde

will try again with new microcodes.

Also, cut from current dmesg:

[19431.120544] ACPI Debug:  "=====PROJECT_QUERY_20====="
[19431.120581] ACPI Error: Needed [Integer/String/Buffer], found [Reference] 000000002d24f561 (20200528/exresop-388)
[19431.120595] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20200528/dswexec-431)
[19431.120604] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0._Q20 due to previous error (AE_AML_OPERAND_TYPE) (20200528/psparse-529)
[19835.025171] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=2101789 end=2101790) time 347 us, min 1062, max 1079, scanline start 1023, end 1083
[19904.161162] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=2111745 end=2111746) time 261 us, min 1062, max 1079, scanline start 1034, end 1080
[19911.917818] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=2112862 end=2112863) time 306 us, min 1062, max 1079, scanline start 1031, end 1085

So... Sorry if my English is bad, I'm not native speaker.
And, thanks.

p.s. current .config: https://pastebin.ubuntu.com/p/CckP8ZgfV9/

Vorherrschende Sprache
Keine Sprachdaten
Sterne
819
Forks
86
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus intel/Intel-Linux-Processor-Microcode-Data-Files

Alle Issues in intel/Intel-Linux-Processor-Microcode-Data-Files

Ähnliche Issues

Weitere Issues zu Operating Systems

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.