Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Bug #1776563 reported by Richard Baka on 2018-06-12
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Linux
Incomplete
Medium
amd
Undecided
Unassigned
linux (Ubuntu)
Medium
Unassigned
linux-firmware (Ubuntu)
Undecided
Unassigned

Bug Description

CPU: Ryzen 5 2500U
VGA: Radeon 535
Notebook: Acer Aspire A315

This is a brand new notebook on the market with Ryzen 5/Radeon.
The default kernel of Ubuntu(18.04) hangs at loading with message:

tsc: Refined TSC clocksource calibration: 1996.250 MHz
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: (...), max_idle_ns: (...)
Soft lockup

Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management.

The same thing happens on mainline 4.17,4.18rc1-2.
BIOS upgrade to the latest version: 1.08 hasn't helped

This problem has been reported upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=200087

The latest correctly working kernel was 4.13.* but the heat problem was present with this too.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1776563

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: bionic

apport-collect 1776563 can't be entered because the kernel can not load.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
summary: - Acer Aspire A315 (Ryzen5/Radeon/FHD) Ubuntu 18.04 kernel cant load
+ Ubuntu 18.04 kernel can't load kernel on Acer Aspire A315
+ (Ryzen5/Radeon/FHD)
summary: - Ubuntu 18.04 kernel can't load kernel on Acer Aspire A315
- (Ryzen5/Radeon/FHD)
+ Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)
no longer affects: bugzilla (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: New → Confirmed
Freihut (freihut) wrote :

Had this on my A315 too, but I returned it to the vendor. Seems to be an UEFI-Bug, because it doesn't happened with my Ryzen 2500U from HP. Could also be related to that Ryzen/Radeon 535 combination (Vega/CGN 3).

On Grub-Menu press E and add "pci=noacpi" as kernel-parameter (where normally "quite splash" is). Then go on booting by pressing F10.
Sometimes (XFCE) it was also necessary to add "nomodeset" to boot, Gnome for example didn't need it (AFAIK).

I remember, I also needed to install amd's pro driver (for 18.04) via amdgpu-pro-install to get rid of the "nomodeset". I was able to run amdgpu-pro-uninstall later and still not needed the "nomodeset". Could be related to my system, but you may give it a try.
I was also using Kernel 4.17 (Mainline), which is available on http://kernel.ubuntu.com/~kernel-ppa/mainline/ or with UKUU https://www.omgubuntu.co.uk/2017/02/ukuu-easy-way-to-install-mainline-kernel-ubuntu

Richard Baka (bakarichard91) wrote :

Thanks Freihut, I will try this.

Richard Baka (bakarichard91) wrote :

It works but very slow. This could be an ACPI problem.

Richard Baka (bakarichard91) wrote :

I installed the new amdgpu pro driver and everything is very fast now. This bug should be reported to freedesktop, would you like somebody to do it? :D

Richard Baka (bakarichard91) wrote :

*Sorry correction: Who would like to do it? :D

Richard Baka (bakarichard91) wrote :

"The fact that ACPI was designed by a group of monkeys high on LSD, and is some of the worst designs in the industry obviously makes running it at any point pretty damn ugly."
Torvalds, Linus (2005-07-31). Message. linux-kernel mailing list. IU. Retrieved on 2006-08-28.

Richard Baka (bakarichard91) wrote :

Power management doesn't work well this way. It was hot a little. I've changed back to win10. This should be fixed by kernel developers or with a downstream patch.

2 comments hidden view all 144 comments

Created attachment 276583
dmesg after starting kernel with pci=noacpi

This is a brand new notebook on the market with Ryzen 5/Radeon. With disabled ACPI kernel boots without any problem but my notebook produces more heat than on Win10. Otherwise this happens when it is stayed on the bios screen in a while.

CPU: AMD Ryzen 5 2500U
GPU1: AMD Radeon Vega 8
GPU2: AMD Radeon 535

(I wrote to Acer to fix their bios problems but they said Linux is not supported. I don't think they are right but what can I do?)

Created attachment 276585
attachment-31427-0.html

Out of office 6/18-6/27

Created attachment 276587
Soft lockup failure without noacpi

Nothing changes with disabled iommu.

5 comments hidden view all 144 comments
6 comments hidden view all 144 comments

Created attachment 276589
dmesg after amd_iommu_dump=1

[ 0.000000] AMD-Vi: Using IVHD type 0x11
[ 0.000000] AMD-Vi: device: 00:00.2 cap: 0040 seg: 0 flags: b0 info 0000
[ 0.000000] AMD-Vi: mmio-addr: 00000000fd900000
[ 0.000000] AMD-Vi: DEV_SELECT_RANGE_START devid: 00:01.0 flags: 00
[ 0.000000] AMD-Vi: DEV_RANGE_END devid: ff:1f.6
[ 0.000000] AMD-Vi: DEV_ALIAS_RANGE devid: ff:00.0 flags: 00 devid_to: 00:14.4
[ 0.000000] AMD-Vi: DEV_RANGE_END devid: ff:1f.7
[ 0.000000] AMD-Vi: DEV_SPECIAL(HPET[0]) devid: 00:14.0
[ 0.000000] AMD-Vi: DEV_SPECIAL(IOAPIC[33]) devid: 00:14.0
[ 0.000000] AMD-Vi: DEV_SPECIAL(IOAPIC[34]) devid: 00:00.1
[ 0.000000] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found

no longer affects: xserver-xorg-video-amdgpu (Ubuntu)

Created attachment 276591
Error message before freezing (without quite splash)

Please try booting with linux 4.18-rc1 or later. Also, please try 4.18-rc1+ with/without ACPI

Hi Erik,

Absolutely the same thing on 4.18rc1 and on rc2 too.

Fedora loads without any additional parameters(mysterious).

[ 0.000000] Switched APIC routing to physical flat.
[ 0.002000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.007000] tsc: Fast TSC calibration using PIT
[ 0.008000] tsc: Detected 1996.299 MHz processor
[ 0.008000] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x398d0c7513b, max_idle_ns: 881590744042 ns
[ 0.008000] Calibrating delay loop (skipped), value calculated using timer frequency.. 3992.59 BogoMIPS (lpj=1996299)

Heat production may be still present but I can't measure it because there is no temperature values in "sensors" (there is 5 values in Win10).

Created attachment 277069
Fedora loads without noacpi

summary: - Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)
+ Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon/FHD)
summary: - Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon/FHD)
+ Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon)
11 comments hidden view all 144 comments
summary: - Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon)
+ Acer Aspire A315 ACPI failure on Ubuntu, kernel hangs, can't load 18.04
+ (Ryzen5/Radeon)
summary: - Acer Aspire A315 ACPI failure on Ubuntu, kernel hangs, can't load 18.04
+ Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load
(Ryzen5/Radeon)
description: updated
summary: Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load
- (Ryzen5/Radeon)
+ (AMD Ryzen 5/Radeon/Raven)
summary: - Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load
- (AMD Ryzen 5/Radeon/Raven)
+ Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load,
+ kernel freeze (AMD Ryzen 5/Radeon/Raven)
12 comments hidden view all 144 comments

Erik, I think this is in connection with clocksource calibration but I'm not an expert.

This works:
[ 0.007000] tsc: Fast TSC calibration using PIT
[ 0.008000] tsc: Detected 1996.299 MHz processor
[ 0.008000] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x398d0c7513b, max_idle_ns: 881590744042 ns

This doesn't:
[...] tsc: Refined tsc clocksource calibration: ...
[...] clocksource: tsc: mask: 0xfff...f (...)

Changed in linux:
importance: Unknown → Medium
status: Unknown → Incomplete
2 comments hidden view all 144 comments

Hi, I was trying another kernel parameters and noapic seems to work. It is not needed to disable the whole ACPI "service", however I don't know how important apic is. On kernel 4.18 even temperature sensors appear.
Power management is almost perfect if cpu governor is set to powersave.

At least amdgpu crashes now so kernel doesn't start without nomodeset. Could this be an acpi problem or I should ask kernel firmware developers?

Hi,
amdgpu doesn't crash on my a315-41g-r40x (BIOS V1.08) with
  linux-next-next-20180713 compiled with VGA_SWITCHEROO=N
and with
  kernel parameters: ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2

gg71, where have you been till now? :D
Thanks, I will try it.

gg71, it works almost perfectly, thanks again. I have been working on this for ca one month. Please write a mail to me if you have any new info.

4 comments hidden view all 144 comments

The solution for Acer A315-41G-* notebooks: (USE AT YOUR OWN RISK - PLS be very careful)

1. Load kernel with these parameters: ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 nomodeset
This is how it can be done (1. answer/first half 1-4): https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter

1/b.(if it is not installed) Install ubuntu and load installed kernel again using the parameters (see 1.)

2. Start a terminal and do these steps:
> cd ~
> mkdir kernelbuild
> cd kernelbuild
> wget -c https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.17.6.tar.xz
> tar -xvf linux-4.17.6.tar.xz
> cd linux-4.17.6
> sudo apt install git build-essential kernel-package fakeroot libncurses5-dev libssl-dev ccache bison flex
> make menuconfig
+> Save,OK,EXIT
> nano .config
+> ctrl+w and search for CONFIG_VGA_SWITCHEROO=y
+> replace y with n (this is not ideal and should be fixed later)
+> ctrl+o, enter
> make -j4 (this will take a while, be patient)
> make modules_install
> sudo make install
> sudo nano /etc/default/grub
+> Edit the correct line and add the parameters: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2"
+>CTRL+O, enter
>sudo update-grub
+> reboot and start the correct kernel

If you install xsensors (sudo apt install xsensors) and start it (xsensors) you can monitor the temperature values of your notebook. (Recommended)

Richard Baka (bakarichard91) wrote :

Dear Ubuntu maintainers,

couldn't this be fixed by an ubuntu kernel patch? The hardest part is to disable gpu switching at kernel load time. APIC fixing parameters can be hardcoded for these models I think or search for the correct pci controller using a smart script.

This was a hell of an investigation, never again. Thanks for gg71, he/she is a lifesaver.

4 comments hidden view all 144 comments

Hi Richard:

This issue should be related to the buggy BIOS ivrs table.
Kernel panic when found no southbridge device ID.

Could you try boot kernel with "amd_iommu_dump=1 amd_iommu=off" (remove other kernel parameters you tried to solve this issue).

If it works, please attach the dmesg here.
I will try to make a kernel patch to make kernel boot with irq map disabled instead of panic.

Richard Baka (bakarichard91) wrote :

Hi AaronMa,

thanks for the response. I tried it but it didn't work. I think iommu problem is not the main reason of the kernel hang. Otherwise it can be disabled in BIOS and there is no change.

The main reason is: https://bugzilla.kernel.org/attachment.cgi?id=276587 like you can se on this picture is that IOAPIC[4] and IOAPIC[5] are not in the invrs table so we should search the correct pci controllers using lspci and give them to the kernel.

In this way:
LINUX_DEFAULT="quiet splash ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2"

Kernel can be started even with noapic but two sensors will be missing and the advanced touchpad functions will not work. This is the reason of CONFIG_VGA_SWITCHEROO=n compile time kernel parameter.

There is an another problem: this notebook has two GPUs and amdgpu (or the kernel, I don't know) can not handle this correctly so gpu switching has to be disabled

Richard Baka (bakarichard91) wrote :

Kernel can be started even with noapic but two sensors will be missing and the advanced touchpad functions will not work.

!!!This line is not here: This is the reason of CONFIG_VGA_SWITCHEROO=n compile time kernel parameter.

There is an another problem: this notebook has two GPUs and amdgpu (or the kernel, I don't know) can not handle this correctly so gpu switching has to be disabled
!!!But here: This is the reason of CONFIG_VGA_SWITCHEROO=n compile time kernel parameter.

Richard Baka (bakarichard91) wrote :

AaronMa,

This is the iommu debug:

[ 0.000000] AMD-Vi: Using IVHD type 0x11
[ 0.000000] AMD-Vi: device: 00:00.2 cap: 0040 seg: 0 flags: b0 info 0000
[ 0.000000] AMD-Vi: mmio-addr: 00000000fd900000
[ 0.000000] AMD-Vi: DEV_SELECT_RANGE_START devid: 00:01.0 flags: 00
[ 0.000000] AMD-Vi: DEV_RANGE_END devid: ff:1f.6
[ 0.000000] AMD-Vi: DEV_ALIAS_RANGE devid: ff:00.0 flags: 00 devid_to: 00:14.4
[ 0.000000] AMD-Vi: DEV_RANGE_END devid: ff:1f.7
[ 0.000000] AMD-Vi: DEV_SPECIAL(HPET[0]) devid: 00:14.0
[ 0.000000] AMD-Vi: DEV_SPECIAL(IOAPIC[33]) devid: 00:14.0
[ 0.000000] AMD-Vi: DEV_SPECIAL(IOAPIC[34]) devid: 00:00.1
[ 0.000000] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found

I will give you the correct iommu "addresses" after dinner :).

Richard Baka (bakarichard91) wrote :

HOT NEWS!!

CONFIG_VGA_SWITCHEROO=n can be avoided using these kernel parameters amdgpu.runpm=0 radeon.modeset=0.
Further investigation is in progress...

Richard Baka (bakarichard91) wrote :

This could be the better solution because of the notebook's lowest heating but I'm not sure.

Richard Baka (bakarichard91) wrote :
Download full text (4.5 KiB)

Hi all,

After a bit of testing the power management seems to be better but it is far away from perfect. I don't see any anomaly watching temperature sensors (instead of ath10k_hwmon-pci(?!??)) but my notebook is definitely warm if I hold it on my lap.
This is more better on win10, I don't know why.

mosomaci@pc:~$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tdie: +55.0°C (high = +70.0°C)
Tctl: +55.0°C

amdgpu-pci-0100
Adapter: PCI adapter
vddgfx: +0.81 V
fan1: N/A
temp1: +50.0°C (crit = +104000.0°C, hyst = -273.1°C)
power1: 1.13 kW (cap = 28.00 W)

ath10k_hwmon-pci-0300
Adapter: PCI adapter
temp1: +91.0°C

amdgpu-pci-0400
Adapter: PCI adapter
vddgfx: N/A
vddnb: N/A
fan1: N/A
temp1: +55.0°C (crit = +80.0°C, hyst = +0.0°C)
power1: N/A

Could our APIC fix not a perfect solution for this problem? I know that the DSDT is totally broken:

[ 0.088280] ACPI: Added _OSI(Module Device)
[ 0.088280] ACPI: Added _OSI(Processor Device)
[ 0.088280] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.088280] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.088280] ACPI: Added _OSI(Linux-Dell-Video)
[ 0.092591] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.100296] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.LPC0.EC0._Q46], AE_ALREADY_EXISTS (20180531/dswload2-316)
[ 0.100309] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180531/psobject-221)
[ 0.100313] ACPI Error: Ignore error and continue table load (20180531/psobject-604)
[ 0.100321] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPC0.EC0.UX**], AE_NOT_FOUND (20180531/psargs-330)
[ 0.100326] ACPI Error: Ignore error and continue table load (20180531/psobject-604)
[ 0.100332] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPC0.EC0.M000], AE_NOT_FOUND (20180531/psargs-330)
[ 0.100336] ACPI Error: Ignore error and continue table load (20180531/psobject-604)
[ 0.100343] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPC0.EC0.M049], AE_NOT_FOUND (20180531/psargs-330)
[ 0.100347] ACPI Error: Ignore error and continue table load (20180531/psobject-604)
[ 0.100353] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPC0.EC0.M280], AE_NOT_FOUND (20180531/psargs-330)
[ 0.100357] ACPI Error: Ignore error and continue table load (20180531/psobject-604)
[ 0.100364] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPC0.EC0.M009], AE_NOT_FOUND (20180531/psargs-330)
[ 0.100369] ACPI Error: Ignore error and continue table load (20180531/psobject-604)
[ 0.100372] ACPI Error: Skipping While/If block (20180531/psloop-594)
[ 0.100378] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPC0.EC0.M000], AE_NOT_FOUND (20180531/psargs-330)
[ 0.100383] ACPI Error: Ignore error and continue table load (20180531/psobject-604)
[ 0.100390] ACPI Error: Cannot release Mutex [QMUX], not acquired (20180531/exmutex-359)
[ 0.100394] ACPI Error: Ignore error and continue table load (20180531/psobject-604)
[ 0.100402] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP2.BCM5], AE_NOT_FOUND (20180531...

Read more...

summary: - Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load,
- kernel freeze (AMD Ryzen 5/Radeon/Raven)
+ Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
+ load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
tags: added: patch
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Changed in linux-firmware (Ubuntu):
status: New → Confirmed
64 comments hidden view all 144 comments
Richard Baka (bakarichard91) wrote :

siyia, I don't recognize any problem but I'm not sure there aren't any. That is sure I've broken some functions.

Richard Baka (bakarichard91) wrote :

Don't you want to write an e-mail to Acer Support? This should be the message:
"Please recompile the firmware SSDT/DSDT files using Intel aml compiler fix the syntax errors and give BIOS update for us, thanks"

Darksurf (piroisl33t-u) wrote :

I've already contacted Acer support and they give the BS answer "We don't support Linux". I tell them crappy BIOS doesn't matter whether or not its windows or Linux. its still crappy bios. I suggested they fix it upstream and I got the response that they'll send it upstream (I'm sure they will /sarcasm).

Richard Baka, I attempted that method, because your method didn't generate the .dsl files. -da flag didn't do anything but print some output without ever creating any dsl files. I ended up having to generate the .dsl files one at a time using the -e flag to pull dependencies for each and generate the .dsl files with external calls. Unfortunately SSDT14.dsl was making calls for a method that doesn't even exist.

So

    External (_SB_.PCI0.GP18.SATA.TPTS, MethodObj) // Warning: Unknown method, guessing 1 arguments
    External (_SB_.PCI0.GP18.SATA.TWAK, MethodObj) // Warning: Unknown method, guessing 1 arguments
    External (_SB_.PCI0.SATA.TPTS, MethodObj) // Warning: Unknown method, guessing 1 arguments
    External (_SB_.PCI0.SATA.TWAK, MethodObj) // Warning: Unknown method, guessing 1 arguments

These I couldn't get no matter what I included. So I did some digging in the dsdt.dsl file. Those Methods(TPTS a.k.a. Prepare to Sleep,TWAK a.k.a. WAKE) don't even exist under the scope PCI0.GP18.SATA. What does exist is S0W (which means Sleep Wake Status) PS0 (Power State 0 a.k.a. Sleep) and PS3 (Power State 3 a.k.a WAKE)

PCI0.SATA Scope doesn't even EXIST! So I just removed any calls and pointers to it in SSDT14.dsl (a whole 2 calls which were if/then statements pointing at PCI0.GP18.SATA first...

I'm going to try to build the files now. Is it safe to merge the DSDT and SSDT files into a single file?

Darksurf (piroisl33t-u) wrote :

Yeah, This rabbit hole just keeps getting deeper. a whole 46 Errors, Log attached. Some appear like they'd be easy to fix for someone who understood the language.

I'm confused by ssdt14.dsl compile as it only has one error

ssdt14.dsl 1341: Arg1
Error 6126 - ^ syntax error, unexpected PARSEOP_ARG1

Not sure why you would RETURN, but then have arguments afterwards? Even so, what would be the proper syntax in this case?

If (CondRefOf (MOEM))
        {
            Return (MOEM) /* External reference */
            Arg0
            Arg1
            Arg2
        }

Darksurf (piroisl33t-u) wrote :

Yeah, This rabbit hole just keeps getting deeper. a whole 46 Errors, Log attached. Some appear like they'd be easy to fix for someone who understood the language.

I'm confused by ssdt14.dsl compile as it only has one error

ssdt14.dsl 1341: Arg1
Error 6126 - ^ syntax error, unexpected PARSEOP_ARG1

Not sure why you would RETURN, but then have arguments afterwards? Even so, what would be the proper syntax in this case?

If (CondRefOf (MOEM))
        {
            Return (MOEM) /* External reference */
            Arg0
            Arg1
            Arg2
        }

siyia (siyia) wrote :

Richard barka are your tables valid for bios 1.09?

siyia (siyia) wrote :

ok they are darksurf remove arg1 and recompile

siyia (siyia) wrote :

Richard barka your ssdt files are error free why don't you submit them in the kernel Bugzilla for further testing?

Richard Baka (bakarichard91) wrote :

Darksurf, I think you should use my decompile parameters. I left same ssdt from that command exactly because of these dependency problem. You didn't write the same like me.
Unknown method warnings shouldn't be appeared.

siyia, the original files should be uploaded to be fixed correctly using the error output. My fix is just a working hack

siyia (siyia) wrote :

upload original tables and then your "fixed" tables in the bug report for a315 41g series and ask for help, status should change from need info to confirmed

Darksurf (piroisl33t-u) wrote :

Richard Baka, Whenever I attempt to decompile using your parameters, nothing happens. it doesn't work. I instead get a segfault. I'm attaching my acpi dump, you're welcome to take a wack at it. in fact, I'd greatly appreciate it if you would and would explain to me what you did to get it to decompile to .dsl files.

siyia (siyia) wrote :

you compile dsl files with iasl -tc

siyia (siyia) wrote :

. dsl files are already decompiled:)

siyia (siyia) wrote :

or if you're talking about the. dat files use iasl -d on each file separately.

Richard Baka (bakarichard91) wrote :

Darksurf, it gives segmentation fault by me. Could you do the dump on Linux not on Windows?

Darksurf (piroisl33t-u) wrote :

That dump came from acpi -b as root

Richard Baka (bakarichard91) wrote :

OK, iasl is too old in distros, I'm compiling a new one.

Richard Baka (bakarichard91) wrote :

This works:
iasl -da ssdt1.dat ssdt2.dat ssdt3.dat ssdt4.dat ssdt5.dat ssdt6.dat ssdt8.dat ssdt11.dat ssdt12.dat dsdt.dat

Richard Baka (bakarichard91) wrote :

Darksurf, this shouldn't be showed:

"iASL Warning: There were 8 external control methods found during
     * disassembly, but only 0 were resolved (8 unresolved)"

So my previous command was not correct. Maybe you should try decompile it with MS decompiler.

siyia (siyia) wrote :

Richard why in your firmware files you include dsdt.aml as a tar archive that has all the ssdt tables inside?

siyia (siyia) wrote :

guys linpus Linux is fedora based! and it is supported by acer laptops that's why it reads the ssdt dsdt tables correctly!

Another User (another-user) wrote :

I have same problem with ACER Aspire a315-41-R19S (ryzen 2200u without dGPU). I'm using Ubuntu 18.04.1 with noapic kernel parameter (Manjaro don't work without it too). With suggested ivrs_ioapic[4]... parameters GUI is very slow.
Fedora boots without any additional kernel parameters, but message about buggy firmware present in dmesg

Another User (another-user) wrote :

Earlier I've got kernel panic (no working init found) with IOMMU disabled in BIOS and without additional kernel parameters.
And one strange thing: with Ubuntu my touchpad works in advanced multitouch mode but in bios is set basic mode. With Fedora 28 it works in basic mode and do not work when set to advanced.
P.S: Sorry for my bad English

Richard Baka (bakarichard91) wrote :

Another User (another-user), install newer kernel than ubuntu's default and don't use noapic just ivrs parameters.

siyia (siyia) wrote :

darksurf you have to add dsdt. aml in the end of the decompile command to remove the iasl warning. f. e iasl -da ssdt1.aml ssdt2.aml dsdt.aml

Darksurf (piroisl33t-u) wrote :

siyia, you're welcome to try it yourself from my ACPIDUMP attachment earlier. its not as simple as it normally would be. In some cases, it just causes iasl to segfault.

https://github.com/acpica/acpica/issues/414

Darksurf (piroisl33t-u) wrote :

I've got some interesting news. I did in fact contact Acer Support and opened a case. Went from Lvl1 to Lvl2 support, was called a couple weeks later with a survey about support, I gave my honest opinion, stating that I don't blame support team as they are limited in what they can do. Today I received a call from LVL3 support! They wanted me to go over my problem in more detail. I let them know of the issues with disassembly and the calling of scopes and functions that do not even exist in the firmware, and that they may be doing something in software with windows drivers to hide it or make it work anyway. He did let me know that they do target the Windows 10 audience and couldn't promise anything, but then I mentioned with the way Windows 10 updates are going I doubt Acer is going to continue to rewrite drivers everytime Microsoft breaks them with their updates, and considering how terrible QA is with windows updates lately having it all just built correctly in firmware to begin with would avoid that. The man agreed and laughed a little. I let him know about iasl and asked if he could have the team look into acpi a little better and that I knew they had dealt with linpus in the past which is effectively just fedora, so I know they have some experience with Linux. I also mentioned my model wasn't the only one affected by these oddities and there were threads in ubuntu, fedora, and the linux kernel's bug system. He agreed to pass on the issues and information to the engineering team in Taiwan. Fingers crossed. So far the customer support has blown away Samsung. I'm not holding my breath for a fix, but I am impressed I got this far.

The LVL3 support guy said he'd call me back when he got a response from Taiwan's Engineers. So I'm guessing within a couple weeks. I told him I understood it wouldn't be a quick response, or even a quick fix if they agreed. He was very cordial and the conversation went well at the least.

Thumbs up for Acer Customer Support guys. Color me impressed.

Richard Baka (bakarichard91) wrote :

Darksurf (piroisl33t-u)

great-great-great work, we are waiting for the good news. I did the same with AMD. They tried to help me with giving advices but they couldn't fix the tables of course.

siyia (siyia) wrote :

guys does sleep/resume works for you? for me sometimes it crashes with a screen freeze. i trimany boot parameters fixed my tables, also used Richard's tables but it still freezes sometimes,should I open a separate bug report? my laptop is of the dual gpu variety. it's the only thing that bothers me with this laptop.

siyia (siyia) wrote :

it can either freeze before suspend or after waking.

Richard Baka (bakarichard91) wrote :

siyia, dmesg is needed.

siyia (siyia) wrote :

dmesg without any custom tables loaded. i noticed in kernel 4.18.14 that there is an amdgpu commit that fixes suspend hang with dual gpu setups

siyia (siyia) wrote :
siyia (siyia) wrote :

still happens on kernel 4.18.14 :(

siyia (siyia) wrote :
siyia (siyia) wrote :
siyia (siyia) wrote :

attached dmesg before and after suspend

siyia (siyia) wrote :
siyia (siyia) wrote :

all dmesgs added together for comparison before/after sleep working, before/after sleep crashed.

siyia (siyia) wrote :

resuming from suspend always disables cpu power management and the cpu runs at turbo frequency, could you also check it out on your laptop Richard? suspend then resume and run watch lscpu.

Displaying first 40 and last 40 comments. View all 144 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.