[Kernel-packages] [Bug 1690085]

2019-03-21 Thread to_load
(In reply to alfie from comment #561) > This is pretty strange, could someone explain it to me? Wasn't mwait bugged > in ryzen? Looks like this patch makes kernel to ignore BIOS messages about unsupported C-state. this function used in "acpi_processor_ffh_cstate_probe" which further used in

[Kernel-packages] [Bug 1690085]

2019-03-18 Thread to_load
So if you got message with "typical current idle" option: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) it means probe of this C-state failed and it must be avoided by kernel. Is there any difference between C-state list in OS with and without this option? I have only laptop

[Kernel-packages] [Bug 1776563]

2019-03-18 Thread to_load
Whoa, looks like ACER really trying fix this! Sadly, current solution is not working for all. And touchpad behaviors somewhat strange. It forced to advanced mode in 1.03 bios too, but does not cause suspend issues - sleep by Fn+F1 works fine. -- You received this bug notification because you

[Kernel-packages] [Bug 1690085]

2019-03-17 Thread to_load
I assume there is several (at least two) similar problems that cause spontaneous system hangs. One of them is mwait bug listed in AMD errata. Looks like idle=halt is partial workaround for this. But, as said in AMD community forum, guest OS in virtual machine may execute mait instruction and

[Kernel-packages] [Bug 1776563]

2019-03-17 Thread to_load
(In reply to siyia from comment #100) > "ACPI: 15 ACPI AML tables successfully acquired and loaded" > > everything acpi-wise seems to be working now. What about /proc/interrupts ? Is APIC is shown there? In my case (noapic) irqs looks like: 12: 408608 0 0 0

[Kernel-packages] [Bug 1776563]

2019-01-30 Thread to_load
Are these (other than noapic) workarounds really enable APIC controller? With acpi=noirq only PIC and MSI entries present in /proc/interrupts. So I assume acpi=off does the same. While noapic obviously disables APIC but works fine for me. Looks like ivrs_ioapic... enables APIC, but in my case

[Kernel-packages] [Bug 1690085]

2019-01-22 Thread to_load
(In reply to Aaron Muir Hamilton from comment #480) > So my box was mostly idle for the last day or so, and had locked up while > the monitor was asleep, so I had to reset it. Can you test your system with idle=halt parameter instead of idle=nomwait? -- You received this bug notification

[Kernel-packages] [Bug 1690085]

2019-01-08 Thread to_load
I have random freezes with Ryzen 2200u laptop. Display image just freezes and system stops responding. Only way to get out from this state is to holding power button (even magic SysRq key does not work). No any clues in logs. With Ubuntu 18.04 it was happen nearly once per week (not intense use).

[Kernel-packages] [Bug 1690085]

2019-01-08 Thread to_load
(In reply to BrĂ¡ulio Bhavamitra from comment #464) > You freeze seems GPU related, try a new kernel/firmware I also have got amdgpu crash with same screen freeze, but magic key had worked that time and error left in kernel log. And I was able reproduce that with certain game in dolphin emulator.

[Kernel-packages] [Bug 1776563]

2018-11-07 Thread to_load
My wi-fi: 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) Subsystem: Lite-On Communications Inc QCA9377 802.11ac Wireless Network Adapter Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci Also in dmeseg i have

[Kernel-packages] [Bug 1776563]

2018-11-07 Thread to_load
Mine device (a315-41-R19S) can sleep on Ububtu 18.04 LTS with default kernel 4.15. But it have no dGPU - maybe this is the reason... Have noapic kernel boot parameter and factory bios 1.03. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1776563]

2018-11-07 Thread to_load
(In reply to siyia from comment #55) > i just cannot understand how fedora kernel config can fix buggy acer bios?i > mean the tables are completely broken,yet under fedora the load without any > error,can this be replicated upstream,fedora 29 uses kernel 4.18.16. Fedora 29 really do not show any