System stuck with "Fixing recursive fault, reboot is required"

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
rajeevrdev
Level 1
Level 1
Posts: 28
Joined: Sun Aug 01, 2021 7:58 am

System stuck with "Fixing recursive fault, reboot is required"

Post by rajeevrdev »

I have recently installed Mint 20.2 on my Lenovo G50-80 . Sometimes when I shutdown , system get stuck with below screen and i have to long press power button to shutdown. It seems the issue has to do with radeon graphics. I have integrated intel graphics . I have had issues with radeon driver in earlier Mint version as well and I think only Intel graphics is being used.
Image

Code: Select all

 inxi -Fxxxz
System:    Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 5.0.5 wm: muffin 5.0.1 
           dm: LightDM 1.30.0 Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: LENOVO product: 80E5 v: Lenovo G50-80 serial: <filter> Chassis: type: 10 v: Lenovo G50-80 
           serial: <filter> 
           Mobo: LENOVO model: Lenovo G50-80 v: NO DPK serial: <filter> UEFI: LENOVO v: B0CN97WW date: 01/08/2016 
Battery:   ID-1: BAT0 charge: 23.0 Wh condition: 23.0/37.6 Wh (61%) volts: 16.3/14.4 model: Lenovo IdeaPad type: Unknown 
           serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i5-5200U bits: 64 type: MT MCP arch: Broadwell rev: 4 L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 17558 
           Speed: 1329 MHz min/max: 500/2700 MHz Core speeds (MHz): 1: 864 2: 973 3: 884 4: 1125 
Graphics:  Device-1: Intel HD Graphics 5500 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:1616 
           Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] vendor: Lenovo 
           driver: radeon v: kernel bus ID: 04:00.0 chip ID: 1002:6660 
           Display: x11 server: X.Org 1.20.11 driver: ati,modesetting,radeon unloaded: fbdev,vesa resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 21.0.3 direct render: Yes 
Audio:     Device-1: Intel Broadwell-U Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:160c 
           Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:9ca0 
           Sound Server: ALSA v: k5.4.0-81-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169 v: kernel port: 4000 
           bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: down mac: <filter> 
           Device-2: Intel Wireless 3160 driver: iwlwifi v: kernel port: 4000 bus ID: 03:00.0 chip ID: 8086:08b4 
           IF: wlp3s0 state: up mac: <filter> 
           IF-ID-1: virbr0 state: down mac: <filter> 
           IF-ID-2: virbr0-nic state: down mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 390.99 GiB (42.0%) 
           ID-1: /dev/sda vendor: Western Digital model: WD10JPCX-24UE4T0 size: 931.51 GiB speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 1A01 scheme: MBR 
Partition: ID-1: / size: 91.17 GiB used: 32.19 GiB (35.3%) fs: ext4 dev: /dev/sda5 
           ID-2: /home size: 809.06 GiB used: 358.79 GiB (44.3%) fs: ext4 dev: /dev/sda7 
           ID-3: swap-1 size: 14.90 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A gpu: radeon temp: 40 C 
           Fan Speeds (RPM): N/A 

When I went through journalctl of the shutdown I see the below errors and warns

Code: Select all

 journalctl -rb -1
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: Fixing recursive fault but reboot is needed!
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: CR2: 00007f0d38f1e29c CR3: 000000011ee0a004 CR4: 00000000003606e0
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: FS:  0000000000000000(0000) GS:ffff9df316b80000(0000) knlGS:0000000000000000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: R13: ffff9df30391c000 R14: ffff9df304d32800 R15: ffff9df304d32848
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: R10: ffff9df308c48600 R11: 0000000000000001 R12: ffff9df30391c000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RBP: ffffc24b823f7d28 R08: 0000000000000000 R09: ffffffffc0194100
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RDX: ffff9df30b4f8000 RSI: ffff9df304d32800 RDI: ffff9df304d32820
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RAX: 0000000000000000 RBX: ffff9df304d32800 RCX: 0000000000000000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RSP: 0018:ffffc24b823f7cf0 EFLAGS: 00010246
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: Code: 50 02 00 00 49 8d b7 50 02 00 00 48 39 c6 0f 85 fa fe ff ff 49 8d 7f 68 e8 c1 f3 cd ff e9 f7 fe ff ff 48 8b 43 48 4c 8d >
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RIP: 0010:radeon_vm_fini+0x16c/0x250 [radeon]
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: ---[ end trace 6e19a400c1111ea8 ]---
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: CR2: 0000000000000000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  serio_raw mac_hid acpi_pad sch_fq_codel msr parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress ra>
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_>
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: R13: 00000000000008c0 R14: 00007f0d39028fc8 R15: 0000000000000000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: R10: 00007f0d399c0eb0 R11: 0000000000003246 R12: 00007f0d39025610
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RBP: 0000000000000000 R08: 00000000000000e7 R09: fffffffffffffc80
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  serio_raw mac_hid acpi_pad sch_fq_codel msr parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress ra>
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_>
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: R13: 00000000000008c0 R14: 00007f0d39028fc8 R15: 0000000000000000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: R10: 00007f0d399c0eb0 R11: 0000000000003246 R12: 00007f0d39025610
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RBP: 0000000000000000 R08: 00000000000000e7 R09: fffffffffffffc80
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RAX: ffffffffffffffda RBX: 00007f0d39025610 RCX: 00007f0d38f1e2c6
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RSP: 002b:00007ffd90d58af8 EFLAGS: 00003246 ORIG_RAX: 00000000000000e7
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: Code: Bad RIP value.
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RIP: 0033:0x7f0d38f1e2c6
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  do_syscall_64+0x57/0x190
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  __x64_sys_exit_group+0x18/0x20
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  do_group_exit+0x47/0xb0
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  do_exit+0x36e/0xaf0
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  task_work_run+0x8f/0xb0
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  ____fput+0xe/0x10
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  __fput+0xcc/0x260
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  drm_release+0xa5/0xe0 [drm]
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  drm_file_free.part.0+0x1d2/0x270 [drm]
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel:  radeon_driver_postclose_kms+0x1cc/0x1f0 [radeon]
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: Call Trace:
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: CR2: 0000000000000000 CR3: 000000011ee0a004 CR4: 00000000003606e0
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: FS:  0000000000000000(0000) GS:ffff9df316b80000(0000) knlGS:0000000000000000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: R13: ffff9df30391c000 R14: ffff9df304d32800 R15: ffff9df304d32848
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: R10: ffff9df308c48600 R11: 0000000000000001 R12: ffff9df30391c000
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RBP: ffffc24b823f7d28 R08: 0000000000000000 R09: ffffffffc0194100
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RDX: ffff9df30b4f8000 RSI: ffff9df304d32800 RDI: ffff9df304d32820
Aug 30 02:02:00 raj-Lenovo-G50-80 kernel: RAX: 0000000000000000 RBX: ffff9df3
I do see some errors on screen when I boot up my machine but havent faced any issues and not sure if its related

Code: Select all

dmesg --level=err,warn
[    0.141485] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.141485]  #3
[    0.145500] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.210801] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GFX0._DSM.ECR1], AE_NOT_FOUND (20190816/psargs-330)
[    0.210824] No Local Variables are initialized for Method [_DSM]
[    0.210825] Initialized Arguments for Method [_DSM]:  (4 arguments defined for method invocation)
[    0.210826]   Arg0:   000000008a71e6f3 <Obj>           Buffer(16) D0 37 C9 E5 53 35 7A 4D
[    0.210831]   Arg1:   000000002acc75b8 <Obj>           Integer 0000000000000003
[    0.210834]   Arg2:   00000000a3aca129 <Obj>           Integer 0000000000000009
[    0.210836]   Arg3:   00000000a9841925 <Obj>           Package 00000000a9841925
[    0.210839] ACPI Error: Aborting method \_SB.PCI0.GFX0._DSM due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    0.261924] pci 0000:00:14.0: can't derive routing for PCI INT A
[    0.261926] pci 0000:00:14.0: PCI INT A: no GSI - using ISA IRQ 7
[    0.536001] DMAR: Failed to find handle for ACPI object \_SB.PCI0.SDMA
[    0.536008] DMAR: Failed to find handle for ACPI object \_SB.PCI0.SDHC
[    0.585677] xhci_hcd 0000:00:14.0: can't derive routing for PCI INT A
[    0.585679] xhci_hcd 0000:00:14.0: PCI INT A: no GSI - using ISA IRQ 7
[    0.607413] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.607414] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.607415] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.607416] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.607417] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.607418] platform eisa.0: Cannot allocate resource for EISA slot 5
[    0.607419] platform eisa.0: Cannot allocate resource for EISA slot 6
[    0.607420] platform eisa.0: Cannot allocate resource for EISA slot 7
[    0.607421] platform eisa.0: Cannot allocate resource for EISA slot 8
[    0.659511] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GFX0._DSM.ECR1], AE_NOT_FOUND (20190816/psargs-330)
[    0.659560] No Local Variables are initialized for Method [_DSM]
[    0.659562] Initialized Arguments for Method [_DSM]:  (4 arguments defined for method invocation)
[    0.659563]   Arg0:   0000000076b917d5 <Obj>           Buffer(16) D0 37 C9 E5 53 35 7A 4D
[    0.659569]   Arg1:   0000000073cc9cf8 <Obj>           Integer 0000000000000002
[    0.659572]   Arg2:   00000000bd3a6fbf <Obj>           Integer 0000000000000000
[    0.659575]   Arg3:   0000000092f18021 <Obj>           Package 0000000092f18021
[    0.659579] ACPI Error: Aborting method \_SB.PCI0.GFX0._DSM due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    0.824668] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[    0.900342] ATPX version 1, functions 0x00000033
[    0.900596] ATPX Hybrid Graphics
[    0.945041] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GFX0._DSM.ECR1], AE_NOT_FOUND (20190816/psargs-330)
[    0.945054] No Local Variables are initialized for Method [_DSM]
[    0.945055] Initialized Arguments for Method [_DSM]:  (4 arguments defined for method invocation)
[    0.945056]   Arg0:   000000008a37f7e1 <Obj>           Buffer(16) D3 73 D8 7E D0 C2 4F 4E
[    0.945063]   Arg1:   00000000811550e4 <Obj>           Integer 0000000000000001
[    0.945065]   Arg2:   0000000016f862df <Obj>           Integer 0000000000000000
[    0.945067]   Arg3:   0000000074fa87cf <Obj>           Package 0000000074fa87cf
[    0.945071] ACPI Error: Aborting method \_SB.PCI0.GFX0._DSM due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.207485] ATPX version 1, functions 0x00000033
[    1.207628] ATPX Hybrid Graphics
[    1.207700] CRAT table not found
[   17.207058] systemd-journald[348]: File /var/log/journal/dafd9a61376b4676aa8b190bc1ed4b43/system.journal corrupted or uncleanly shut down, renaming and replacing.
[   21.333654] Bluetooth: hci0: unexpected event for opcode 0xfc2f
[   31.154088] kauditd_printk_skb: 16 callbacks suppressed
[   40.575043] vboxdrv: loading out-of-tree module taints kernel.
[   40.675280] VBoxNetFlt: Successfully started.
[   40.767639] VBoxNetAdp: Successfully started.
[   41.050390] Started bpfilter
[   53.930097] systemd-journald[348]: File /var/log/journal/dafd9a61376b4676aa8b190bc1ed4b43/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
I have seen few such issues but none of them had a solution. I am considering trying kernel update to 5.8 or disabling radeon as the last step. Everything except this random shutdown issue works pretty well so any suggestion to fix this bug would be welcome.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
djph
Level 7
Level 7
Posts: 1882
Joined: Thu Jun 27, 2019 5:43 am
Location: ::1

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by djph »

Updated kernel is probably your best initial step.
rajeevrdev
Level 1
Level 1
Posts: 28
Joined: Sun Aug 01, 2021 7:58 am

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by rajeevrdev »

djph wrote: Mon Aug 30, 2021 11:12 am Updated kernel is probably your best initial step.
I just tried it. problem still persists.
djph
Level 7
Level 7
Posts: 1882
Joined: Thu Jun 27, 2019 5:43 am
Location: ::1

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by djph »

That's certainly problematic.

Might be beneficial to install amdgpupro (the proprietary kernel modules) instead of relying on radeon ... but I don't use AMD graphics, so might be pointing you in the wrong direction.
User avatar
SMG
Level 25
Level 25
Posts: 31313
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by SMG »

rajeevrdev wrote: Mon Aug 30, 2021 10:13 amIt seems the issue has to do with radeon graphics. I have integrated intel graphics .
The data you posted indicates your system has both integrated Intel graphics and a separate AMD GPU. Just because you are current using the Intel graphics does not mean the AMD GPU does not exist. It does and its drivers are installed.

Graphics:
Device-1: Intel HD Graphics 5500 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:1616
Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] vendor: Lenovo
driver: radeon v: kernel bus ID: 04:00.0 chip ID: 1002:6660
Display: x11 server: X.Org 1.20.11 driver: ati,modesetting,radeon unloaded: fbdev,vesa resolution: 1366x768~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 21.0.3 direct render: Yes

While your system is currently showing as rendering with Intel graphics, we would have to check other files to know for sure if the AMD renderer is loaded.

Dual-graphics laptops (which is what you have) can have the graphics installed in many different configurations. Some manufacturers have a setting in BIOS/UEFI which permits uses one or both of the options. (Using either GPU might be called "hybrid" or "switchable" while using the AMD card would likely be "discrete". Some also have an option to just use the onboard Intel.) Some manufacturers only permitted switching the GPUs in Windows modules. You will have to check to see what is available for your hardware.
rajeevrdev wrote: Mon Aug 30, 2021 10:13 amWhen I went through journalctl of the shutdown I see the below errors and warns
The errors are related to the radeon driver which is loaded at boot time (per the data you posted).
rajeevrdev wrote: Mon Aug 30, 2021 10:13 am I have seen few such issues but none of them had a solution.
A number of those "errors" are not errors and are actually messages. Some of the errors might be fixed by a newer BIOS/UEFI if one is available.
rajeevrdev wrote: Mon Aug 30, 2021 10:13 am I am considering trying kernel update to 5.8
I do not think there were any changes to the radeon module for you Sun XT so I am not surprised you did not see a difference. I did help someone on another thread get the amdgpu driver loaded for the Sun XT, but that was system with onboard AMD and the Sun XT card. I do not know if that would help this situation.

Let us know if there are any options in your laptop's BIOS/UEFI to select which GPU can be used.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
rajeevrdev
Level 1
Level 1
Posts: 28
Joined: Sun Aug 01, 2021 7:58 am

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by rajeevrdev »

I haven't played with BIOS/UEFI settings yet as my system is old and I really dont wanna brick my system . I have heard some horror stories on bios update on Lenovo. How safe is it to update BIOS with USB? And I checked lenovo latest bios update available. Its an exe file. Can I update bios with it from linux? How safe is it? From description it only includes security update not bug fixes . https://pcsupport.lenovo.com/in/en/prod ... IOS%2FUEFI

Currently my system works fine except this random shutdown stuck glitch. What would be the best way to go forward?
User avatar
SMG
Level 25
Level 25
Posts: 31313
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by SMG »

rajeevrdev wrote: Tue Aug 31, 2021 6:25 am I haven't played with BIOS/UEFI settings yet as my system is old and I really dont wanna brick my system .
I asked you what settings are available in BIOS/UEFI and how they are set. I did not advise you to change any of the settings. Knowing what settings, if any, there are will give us an idea of what might be possible to address your concern.
rajeevrdev wrote: Tue Aug 31, 2021 6:25 amHow safe is it to update BIOS with USB?
I know people on this forum have updated BIOS/UEFIs with usb, but I would think your concern is specific to your hardware. Someone may have already asked that question on the Lenovo user forum, so I advise checking there with your concerns and question about updating and the forms available to do it.

It is possible updating the BIOS/UEFI would not affect those messages, so you may be fine leaving as it is.
rajeevrdev wrote: Tue Aug 31, 2021 6:25 am What would be the best way to go forward?
Please answer the question I asked about BIOS/UEFI settings.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
rajeevrdev
Level 1
Level 1
Posts: 28
Joined: Sun Aug 01, 2021 7:58 am

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by rajeevrdev »

I just cheked the settings in BIOS. "Discrete" is the selected option in graphics card. Here is a screenshot. Image
User avatar
SMG
Level 25
Level 25
Posts: 31313
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by SMG »

rajeevrdev wrote: Tue Aug 31, 2021 11:23 amI just cheked the settings in BIOS. "Discrete" is the selected option in graphics card. Here is a screenshot.
What I was able to find about that setting is it determines how the graphics memory is handled. Graphics memory is either handled on the AMD card (discrete) or in the CPU (UMA only). I did not find anything which indicates those settings specifically enable or disable a GPU.

The information I found on the Lenovo site indicates the ability to switch is done within a Windows program. That could mean the hardware for switching was set at whatever the last setting was when Windows was on that computer, so it is what it is.

You indicated that this does not happen all the time. Perhaps noticing what is different on those times it does not happen would be a clue. The journal -rb -1 info you provided does not go back to the start of the kernel panic, so any clues of what might have tripped it are not yet known.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
rajeevrdev
Level 1
Level 1
Posts: 28
Joined: Sun Aug 01, 2021 7:58 am

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by rajeevrdev »

My system never had windows. It came with MS DOS before i installed mint. The AMD graphics card was not used in my Mint 18 as well but it didnt have this shutdown problem. The issue happens randomly but cant find a specific scenario which causes this issue. journalctl had just this indicative of an error nothing else that points to kernel panic. I can provide the full log next time it happens. I am in a situation where I think the best solution is to disable the AMD card so that the shutdown issue goes away, cant seem to get it working in any way.
User avatar
SMG
Level 25
Level 25
Posts: 31313
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by SMG »

rajeevrdev wrote: Tue Aug 31, 2021 4:03 pmMy system never had windows. It came with MS DOS before i installed mint.
While I've heard of computers coming with FreeDOS instead of an operating system, I was not aware of computers coming with just MS DOS. The Lenovo Product Overview - Lenovo G50-80, G50-80 touch indicates it came with Windows 8.1.
rajeevrdev wrote: Tue Aug 31, 2021 4:03 pmThe AMD graphics card was not used in my Mint 18 as well but it didnt have this shutdown problem.
I would think your Mint 18 used a different kernel which likely means a different radeon driver version. Mint 18 also had different Xorg and mesa versions (as well as other files).
rajeevrdev wrote: Tue Aug 31, 2021 4:03 pmThe issue happens randomly but cant find a specific scenario which causes this issue. journalctl had just this indicative of an error nothing else that points to kernel panic.
There is the possibility that future kernel update or graphics-related files updates may clear it.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
User avatar
all41
Level 19
Level 19
Posts: 9498
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by all41 »

@rajeevrdev
If your shutdown sequence hangs again during troubleshooting try this to gracefully
power down:

Hold down the Alt key and continue to hold during this entire keystroke sequence:
Press and release the PrtScn key (on some keyboards SysRq)
then type
r e i s u o (no spaces just type the letters slowly)

This method is preferred to a hard shutdown using the power button.
You can make it gracefully reboot with the same method but use
r e i s u b
Everything in life was difficult before it became easy.
rajeevrdev
Level 1
Level 1
Posts: 28
Joined: Sun Aug 01, 2021 7:58 am

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by rajeevrdev »

all41 wrote: Tue Aug 31, 2021 7:09 pm @rajeevrdev
If your shutdown sequence hangs again during troubleshooting try this to gracefully
power down:

Hold down the Alt key and continue to hold during this entire keystroke sequence:
Press and release the PrtScn key (on some keyboards SysRq)
then type
r e i s u o (no spaces just type the letters slowly)

This method is preferred to a hard shutdown using the power button.
You can make it gracefully reboot with the same method but use
r e i s u b
Thanks . didnt know about it. I will try that next time it happens.
User avatar
all41
Level 19
Level 19
Posts: 9498
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by all41 »

rajeevrdev wrote: Wed Sep 01, 2021 8:43 am
all41 wrote: Tue Aug 31, 2021 7:09 pm @rajeevrdev
If your shutdown sequence hangs again during troubleshooting try this to gracefully
power down:

Hold down the Alt key and continue to hold during this entire keystroke sequence:
Press and release the PrtScn key (on some keyboards SysRq)
then type
r e i s u o (no spaces just type the letters slowly)

This method is preferred to a hard shutdown using the power button.
You can make it gracefully reboot with the same method but use
r e i s u b
Thanks . didnt know about it. I will try that next time it happens.
The mnemonic is "raising elephants is so utterly boring"
See this link:
https://www.mnemonic-device.com/compute ... ly-boring/
Cheers
Everything in life was difficult before it became easy.
rajeevrdev
Level 1
Level 1
Posts: 28
Joined: Sun Aug 01, 2021 7:58 am

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by rajeevrdev »

I actually had the issue happen again. This time I have the complete log of

Code: Select all

journalctl -b -1 -r
pushed here http://sprunge.us/vw4jC4.

This seems to be the relevant part

Code: Select all

Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: Fixing recursive fault but reboot is needed!
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: CR2: 0000000000000000 CR3: 00000001119ea001 CR4: 00000000003706e0
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: FS:  0000000000000000(0000) GS:ffff8da856c80000(0000) knlGS:0000000000000000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: R13: ffff8da713b50000 R14: ffff8da708ab6200 R15: ffff8da708ab6248
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: R10: ffff8da708d92540 R11: 0000000000000001 R12: ffff8da713b50000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RBP: ffffad9c02553d48 R08: 0000000000000000 R09: ffffffffc03db000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RDX: ffff8da70d1e3080 RSI: ffff8da708ab6200 RDI: ffff8da708ab6220
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RAX: 0000000000000000 RBX: ffff8da708ab6200 RCX: 0000000000000000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RSP: 0018:ffffad9c02553d18 EFLAGS: 00010246
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: Code: ff e8 2a ba 6f d9 4d 8b 7c 24 70 31 f6 49 8b bf 70 01 00 00 e8 37 d5 d5 d9 83 f8 fc 0f 85 4e ff ff ff 48 8b 43 48 4c 8d >
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RIP: 0010:radeon_vm_fini+0x13a/0x220 [radeon]
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: ---[ end trace 29be811a25db468a ]---
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: CR2: 0000000000000000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  ecdh_generic ecc mei_hdcp joydev snd input_leds rapl ideapad_laptop intel_cstate soundcore sparse_keymap serio_raw wmi iwlwif>
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_>
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: R13: 00000000000008c0 R14: 00007f85e00e2fc8 R15: 0000000000000000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: R10: 00007f85e0a7beb0 R11: 0000000000000246 R12: 00007f85e00df610
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RBP: 0000000000000000 R08: 00000000000000e7 R09: fffffffffffffc80
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RAX: ffffffffffffffda RBX: 00007f85e00df610 RCX: 00007f85dffd82c6
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RSP: 002b:00007ffc01f3bc08 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: Code: Unable to access opcode bytes at RIP 0x7f85dffd829c.
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RIP: 0033:0x7f85dffd82c6
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  do_syscall_64+0x38/0x90
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  __x64_sys_exit_group+0x18/0x20
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  do_group_exit+0x43/0xa0
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  ? handle_mm_fault+0xd7/0x2b0
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  do_exit+0x389/0xaf0
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  task_work_run+0x70/0xb0
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  ____fput+0xe/0x10
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  __fput+0x9f/0x250
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  drm_release+0x6e/0xf0 [drm]
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  drm_close_helper.isra.0+0x65/0x70 [drm]
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  drm_file_free.part.0+0x1e5/0x250 [drm]
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel:  radeon_driver_postclose_kms+0x167/0x180 [radeon]
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: Call Trace:
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: CR2: 0000000000000000 CR3: 0000000126410005 CR4: 00000000003706e0
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: FS:  0000000000000000(0000) GS:ffff8da856c80000(0000) knlGS:0000000000000000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: R13: ffff8da713b50000 R14: ffff8da708ab6200 R15: ffff8da708ab6248
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: R10: ffff8da708d92540 R11: 0000000000000001 R12: ffff8da713b50000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RBP: ffffad9c02553d48 R08: 0000000000000000 R09: ffffffffc03db000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RDX: ffff8da70d1e3080 RSI: ffff8da708ab6200 RDI: ffff8da708ab6220
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RAX: 0000000000000000 RBX: ffff8da708ab6200 RCX: 0000000000000000
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RSP: 0018:ffffad9c02553d18 EFLAGS: 00010246
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: Code: ff e8 2a ba 6f d9 4d 8b 7c 24 70 31 f6 49 8b bf 70 01 00 00 e8 37 d5 d5 d9 83 f8 fc 0f 85 4e ff ff ff 48 8b 43 48 4c 8d >
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: RIP: 0010:radeon_vm_fini+0x13a/0x220 [radeon]
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: Hardware name: LENOVO 80E5/Lenovo G50-80, BIOS B0CN97WW 01/08/2016
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: CPU: 1 PID: 967 Comm: Xorg Tainted: G          IOE     5.11.0-34-generic #36~20.04.1-Ubuntu
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: Oops: 0000 [#1] SMP PTI
Sep 10 01:56:42 raj-Lenovo-G50-80 kernel: PGD 0 P4D 0 
Sep 10 01:56:41 raj-Lenovo-G50-80 kernel: #PF: error_code(0x0000) - not-present page
Sep 10 01:56:41 raj-Lenovo-G50-80 kernel: #PF: supervisor read access in kernel mode
Sep 10 01:56:41 raj-Lenovo-G50-80 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000

User avatar
SMG
Level 25
Level 25
Posts: 31313
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by SMG »

rajeevrdev wrote: Fri Sep 10, 2021 8:59 am I actually had the issue happen again. This time I have the complete log of

Code: Select all

journalctl -b -1 -r
pushed here http://sprunge.us/vw4jC4.

This seems to be the relevant part
Yes, that seems to happen right after the virtual machines shut down. The kernel shows as tainted because of VirtualBox (which is common and not usually considered an issue).

The system does show it reached shutdown.

Code: Select all

Sep 10 01:56:59 raj-Lenovo-G50-80 systemd[1]: Reached target Shutdown.
It then appears you may have tried to use the command all41 described?

Code: Select all

Sep 10 02:01:51 raj-Lenovo-G50-80 kernel: sysrq: This sysrq operation is disabled.
Sep 10 02:01:56 raj-Lenovo-G50-80 kernel: sysrq: This sysrq operation is disabled.
Sep 10 02:02:00 raj-Lenovo-G50-80 kernel: sysrq: This sysrq operation is disabled.
Sep 10 02:02:02 raj-Lenovo-G50-80 kernel: sysrq: Emergency Sync
Sep 10 02:02:02 raj-Lenovo-G50-80 kernel: Emergency Sync complete
Sep 10 02:02:12 raj-Lenovo-G50-80 kernel: sysrq: Emergency Remount R/O
However notice there is a five minute gap between when the "reached target shutdown message" and the next lines.

It does not appear to me the system was "stuck" on fixing recursive fault. That may have just been the last error message recorded so that was why it was on the screen while the system finished shutting down. This may be an ACPI power issue. How long do you give it before you decide it will not shut down?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
rajeevrdev
Level 1
Level 1
Posts: 28
Joined: Sun Aug 01, 2021 7:58 am

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by rajeevrdev »

I have waited for almost 30 mins sometimes but it wont shutdown. So I didnt wait this time. I do have a feeling that chance of this happening is high when i turn the power off while working (running on battery). But it doesnt happen always on battery as well.

My earlier Linux mint(18) version had an issue where screen wouldnt turn on when I wake it up from sleep. I could hear the system loading but screen would be dark. This used to happen more often on battery as well. I am not facing this issue on Mint 20.

Still cant figure out the issue . Not sure which might be the safe option I can try as well.
User avatar
SMG
Level 25
Level 25
Posts: 31313
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by SMG »

rajeevrdev wrote: Sat Sep 11, 2021 11:57 am I have waited for almost 30 mins sometimes but it wont shutdown. So I didnt wait this time. I do have a feeling that chance of this happening is high when i turn the power off while working (running on battery). But it doesnt happen always on battery as well.
If sometimes it seems to shut down just fine, I suggest checking a journalctl of a "good" shutdown to see if maybe there is a difference between the two which might point to the source of the issue.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by karlchen »

<mod> sarang's report about the same problem on a different machine can be found here: viewtopic.php?p=2065642#p2065642 </mod>
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
rajeevrdev
Level 1
Level 1
Posts: 28
Joined: Sun Aug 01, 2021 7:58 am

Re: System stuck with "Fixing recursive fault, reboot is required"

Post by rajeevrdev »

I have taken a look into it. It seems few steps are not being run when shutdown freeze. These are those steps.

Code: Select all

Sep 13 03:42:59 raj-Lenovo-G50-80 systemd-journald[348]: Journal stopped
Sep 13 03:42:59 raj-Lenovo-G50-80 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Sep 13 03:42:58 raj-Lenovo-G50-80 systemd-shutdown[1]: Syncing filesystems and block devices.
Sep 13 03:42:58 raj-Lenovo-G50-80 systemd[1]: Shutting down.
Sep 13 03:42:58 raj-Lenovo-G50-80 systemd[1]: Reached target Power-Off.
Sep 13 03:42:58 raj-Lenovo-G50-80 systemd[1]: Finished Power-Off.
Sep 13 03:42:58 raj-Lenovo-G50-80 systemd[1]: systemd-poweroff.service: Succeeded.
Sep 13 03:42:58 raj-Lenovo-G50-80 systemd[1]: Reached target Final Step.
Sep 13 03:42:58 raj-Lenovo-G50-80 systemd[1]: Finished Shuts down the "live" preinstalled system cleanly.
Sep 13 03:42:58 raj-Lenovo-G50-80 systemd[1]: casper.service: Succeeded.
Sep 13 03:42:58 raj-Lenovo-G50-80 systemd[1]: Starting Shuts down the "live" preinstalled system cleanly...
And in normal shutdown the earlier mentioned error logs dont appear as well.
Fixing recursive fault but reboot is needed!
is therefore not present as well. Here is the complete log of normal shutdown. http://sprunge.us/8RvF8H It seems like shutdown is waiting for something to complete.
Locked

Return to “Installation & Boot”