System freeze upon power unplug

Shout-out to the Manjaro Community…

I’ve recently moved to Manjaro from Ubuntu, and before that from Windows, but since moving away from Windows, I experience full system freeze when battery gets full and I unplug the power cable, since the system becomes totally irresponsive,I have to hard shutdown the device every time.

System:    Kernel: 5.8.0-2-MANJARO x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel 
           wm: xfwm4 dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:   Type: Laptop System: ASUSTeK product: N552VW v: 1.0 serial: <filter> 
           Mobo: ASUSTeK model: N552VW v: 1.0 serial: <filter> UEFI: American Megatrends v: N552VW.304 date: 05/08/2019 
Battery:   ID-1: BAT0 charge: 19.2 Wh condition: 34.0/47.5 Wh (72%) volts: 14.4/14.4 model: ASUSTeK ASUS Battery type: Li-ion 
           serial: N/A status: Discharging cycles: 1307 
CPU:       Topology: Quad Core model: Intel Core i7-6700HQ bits: 64 type: MT MCP arch: Skylake-S rev: 3 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 41621 
           Speed: 800 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 801 6: 801 7: 800 8: 800 
Graphics:  Device-1: Intel HD Graphics 530 vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:191b 
           Device-2: NVIDIA GM107M [GeForce GTX 960M] vendor: ASUSTeK driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:139b 
           Device-3: Chicony HD WebCam (Asus N-series) type: USB driver: uvcvideo bus ID: 1-4:2 chip ID: 04f2:b3fd 
           serial: <filter> 
           Display: x11 server: X.Org 1.20.8 driver: intel,nouveau unloaded: modesetting alternate: fbdev,nv,vesa 
           resolution: 1920x1080~60Hz s-dpi: 96 
           OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 20.1.5 direct render: Yes 
Audio:     Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:a170 
           Sound Server: ALSA v: k5.8.0-2-MANJARO 
Network:   Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel port: e000 bus ID: 02:00.0 chip ID: 8086:095a 
           IF: wlp2s0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: d000 
           bus ID: 03:00.1 chip ID: 10ec:8168 
           IF: enp3s0f1 state: down mac: <filter> 
           IF-ID-1: proton0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:    Local Storage: total: 1.94 TiB used: 30.95 GiB (1.6%) 
           ID-1: /dev/sda vendor: Samsung model: MZNLF128HCHP-00004 size: 119.24 GiB speed: 6.0 Gb/s serial: <filter> 
           rev: 301Q scheme: GPT 
           ID-2: /dev/sdb vendor: Seagate model: ST2000LM003 HN-M201RAD size: 1.82 TiB speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 0001 scheme: GPT 
Partition: ID-1: / size: 104.02 GiB used: 30.95 GiB (29.8%) fs: ext4 dev: /dev/sda2 
Swap:      ID-1: swap-1 type: partition size: 12.76 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 51.0 C mobo: N/A gpu: nouveau temp: 44 C 
           Fan Speeds (RPM): cpu: 2100 
Info:      Processes: 237 Uptime: 45m Memory: 11.60 GiB used: 2.22 GiB (19.2%) Init: systemd v: 245 Compilers: gcc: 10.1.0 
           Packages: 1253 pacman: 1247 snap: 6 Shell: Bash v: 5.0.18 running in: xfce4-terminal inxi: 3.1.05

Hi @xashyar, can you post journalctl -xe -p3 -b-1 please. Best thing to do is run the command after a freeze. (reboot)

Hi @Lunix,

This time I unplugged the battery at around 30% charge then the system froze, the first reboot was not successful (something I’ve began to experience after installing the 5.8 Kernel), the second reboot was successful so I got the log:

Aug 17 23:10:13 user kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x0000000078800000-0x000000007affffff], contact BIOS vendor for fixes
Aug 17 23:10:13 user kernel: pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Aug 17 23:10:13 user kernel: pcieport 0000:00:1c.4: AER:   device [8086:a114] error status/mask=00000100/00002000
Aug 17 23:10:13 user kernel: pcieport 0000:00:1c.4: AER:    [ 8] Rollover              
Aug 17 23:10:13 user kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Aug 17 23:10:13 user kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Aug 17 23:10:14 user kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
Aug 17 23:10:15 user kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f
Aug 17 23:10:16 user kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Aug 17 23:10:20 user lightdm[1123]: gkr-pam: unable to locate daemon control file
Aug 17 23:56:03 user kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Aug 18 07:20:50 user kernel: pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Aug 18 07:20:50 user kernel: pcieport 0000:00:1c.4: AER:   device [8086:a114] error status/mask=00001000/00002000
Aug 18 07:20:50 user kernel: pcieport 0000:00:1c.4: AER:    [12] Timeout

Did you have the same issues with Ubuntu?
My first guess would be asking if your BIOS is up to date.
I think we can solve the firmware bugs with disabling TPM in your BIOS. I think it’s under security somewhere. I’m not sure this will effect the other problem, but we can try.

Yeah but less recurring than now.

Yup it’s the latest available:

I also suspect this problem might be related to this recent update, since I updated the BIOS, just as I was migrating from Windows.

We’ll try that for sure.

Could it also be due to some nouveau driver malfunction?
(Some errors in the logs refer to nouveau.)

It’s a possibility. You will see when you changed the settings. Then we can look further. Problem is that I can’t check when I’m at work :persevere: .

Hello again @lunix,

I looked through BIOS, and couldn’t find anything under TPM.
Under the Security tab there was a Secure Boot Control option which was disabled, other than that nothing remotely close.

Ok, If I’m not mistaken you have dual graphics ? (Intel/NVidia) Does your system switch automatic to NVidia when the power chord is plugged in? I don’t use Nvidia graphics so I don’t know for sure. And to be honest, maybe I’m thinking too much like ‘MS windows’ … :crazy_face:

You could try to unplug your power when both Intel or NVidia are active. Maybe the problem occurs just with one of them?

Although I think that someone with more skills should take a look at this. There are a lot of other topics on the internet with the same problem, but all of them with different solutions.

1 Like

Please try to use REISUB/REISUO instead of hard power off (to avoid FS damage).

2 Likes

Yes

I don’t remember explicitly setting that anywhere, does such an option exist?

This happens now less often, especially when I avoid unplugging after battery full charge notif.