You are not logged in.

#1 2024-03-17 10:37:48

demensdeum
Member
From: Hyperborea
Registered: 2022-07-02
Posts: 40
Website

[Solved]panic on shutdown "Unable to access opcode bytes at [address]"

Sometimes my laptop stuck on shutdown with kernel panic "Unable to access opcode bytes".
From error I can assume that is something CPU related, last time I saw something like this in 2015 with outdated CPU microcode.

Photo of kernel panic:
https://ibb.co/34r6vxT

uname -a

Linux DEMENSACERCP2077 6.7.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 08 Mar 2024 01:59:01 +0000 x86_64 GNU/Linux

hwinfo --short:
https://pastebin.com/2xYK8bhS

Last edited by demensdeum (2024-04-06 20:31:06)

Offline

#2 2024-04-04 20:26:25

nvann
Member
Registered: 2024-04-04
Posts: 6

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

Same error, can't seem to fix it, tried settings kernel parameters such as "intel_idle.max_cstate=1 i915.enable_dc=0 ahci.mobile_lpm_policy=1" as per these instructions (https://wiki.archlinux.org/title/Intel_ … Intel_CPUs) on the wiki which have not fixed the issue

Offline

#3 2024-04-06 18:29:20

demensdeum
Member
From: Hyperborea
Registered: 2022-07-02
Posts: 40
Website

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

@nvann do you have Nvidia also?
For me bad that kernel started to panic in the middle of work, not only on shutdown

Last edited by demensdeum (2024-04-06 18:40:40)

Offline

#4 2024-04-06 20:30:17

demensdeum
Member
From: Hyperborea
Registered: 2022-07-02
Posts: 40
Website

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

Removed NVIDIA driver -> no problem [Solved?]

Offline

#5 2024-04-06 21:11:34

nvann
Member
Registered: 2024-04-04
Posts: 6

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

I do have nvidia, I'm using the dkms proprietary driver, you just removed it? I kinda need it because nouveau's performance is quite lacking on my system. And yes, the panic also happens after a few hours of usage, it usually spits out a few dmesg errors which start with

[13907.454511] BUG: unable to handle page fault for address: 0000000000001587
[13907.454520] #PF: supervisor read access in kernel mode
[13907.454522] #PF: error_code(0x0000) - not-present page

(the address my change after each reboot and subsequent error)
And then, little by little, a few programs start to give out, for example I won't be able to use ps, or htop, or sudo, until finally some big application like qbittorrent or firefox gives out and my whole system freezes. I wouldn't mark it as solved since not using the proprietary driver is a game-breaker for a lot of people, but I have yet to test if it fixes the problem on my end.

Last edited by nvann (2024-04-06 21:33:07)

Offline

#6 2024-04-06 21:39:23

demensdeum
Member
From: Hyperborea
Registered: 2022-07-02
Posts: 40
Website

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

whole system freezes

@nvann same story, NVIDIA driver known for instability with Optimus (PRIME) systems, which is my case (Intel + Nvidia Laptop)

Offline

#7 2024-04-06 21:49:34

nvann
Member
Registered: 2024-04-04
Posts: 6

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

demensdeum wrote:

whole system freezes

@nvann same story, NVIDIA driver known for instability with Optimus (PRIME) systems, which is my case (Intel + Nvidia Laptop)

Our systems are quite similar, mine also has an intel iGPU and an nvidia dGPU.

Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02)
NVIDIA Corporation GM108M [GeForce MX110] (rev a2)

I wouldn't surprise me if our nvidia cards were to blame, specially since they are the oldest family still supported by the proprietary driver, or that at least were supported.

Offline

#8 2024-04-19 20:00:38

demensdeum
Member
From: Hyperborea
Registered: 2022-07-02
Posts: 40
Website

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

nvann, please check https://bbs.archlinux.org/viewtopic.php … 2#p2162662

Last edited by demensdeum (2024-04-19 20:01:11)

Offline

#9 2024-04-21 01:21:37

nvann
Member
Registered: 2024-04-04
Posts: 6

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

demensdeum wrote:

Did you fix the issue by blacklisting uvm or downgrading the driver? I guess either solution is better than using nouveau but I'd rather know the exact solution since I'll probably do a full reinstall

Offline

#10 2024-04-21 18:30:59

demensdeum
Member
From: Hyperborea
Registered: 2022-07-02
Posts: 40
Website

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

@nvann blacklisted nvidia_uvm (modprobe.blacklist=nvidia_uvm in grub.cfg), second day works ok, but sometimes looks slow because of disabled cuda(?)

Offline

#11 2024-04-21 19:12:40

nvann
Member
Registered: 2024-04-04
Posts: 6

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

demensdeum wrote:

@nvann blacklisted nvidia_uvm (modprobe.blacklist=nvidia_uvm in grub.cfg), second day works ok, but sometimes looks slow because of disabled cuda(?)

NVENC, which performes hardware accelerated video encoding, also requires the uvm module

Offline

#12 2024-04-22 06:33:50

demensdeum
Member
From: Hyperborea
Registered: 2022-07-02
Posts: 40
Website

Re: [Solved]panic on shutdown "Unable to access opcode bytes at [address]"

@nvann, for some reason I can still use NVENC in OBS, but it feels way slower than usual, I can only assume that it is starting to work on cpu

Offline

Board footer

Powered by FluxBB