| View previous topic :: View next topic |
| Author |
Message |
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1051
Location: Belgium
|
 Posted: Sat Mar 08, 2025 9:46 pm Post subject: 6.12.16: irq 55 handler after 27 seconds (not kernel) |
 |
|
My kernel was 6.6.52 and I ran an emerge @world after issues with plasma6 to get on the last versions of the system. One of the packages pulled in was 6.12.16. So after the world update finished I set to compile the new kernel. I opened a terminal and went "su -", then ran the following:
| Code: |
eselect kernel list
eselect kernel set 2 (to select 6.12.16)
cp /usr/src/linux-6.6.52-gentoo/.config /usr/src/linux/
cd /usr/src/linux
make oldconfig
make menuconfig |
I then went through a few drivers for hardware I know I do not have and also I changed "Preemption model", which I changed from "Low-latency desktop" to "Real-time". Then I continued as alwyas:
| Code: |
make && make modules_install
mount /boot
make install
grub-mkconfig -o /boot/grub/grub.cfg
emerge --ask --oneshot @module-rebuild voor virtualbox
emerge --oneshot app-emulation/virtualbox-extpack-oracle
revdep-rebuild
perl-cleaner --all -- -av |
Closed all applications and reboot. This did not reboot, it stopped dead at:
| Code: | * Loading module vboxdrv ...
insmod /lib/modules/6.12.16-gentoo/mics/vboxdrv.ko |
Only way to recover was a hard reset.
So I removed (temporary) /etc/modules-load.d/virtualbox.conf to keep the modules from loading. The kernel booted but lsmod showed that vboxdrv, vboxnetadp and vboxnetflt were active. Which I found strange. Virtualbox (latest 7.1.4) started but starting a virtual XP machine opened the window for the virtual machine but then a box came "loading virtual machine". Only way stop that was "kill -9 <pid>", even shutting down the pc from plasma6 didn't work as it assumed the VM was still running.
I wanted to post a thread about this but immediatly found this thread at the top of the page: https://forums.gentoo.org/viewtopic-t-1173243.html
So to check if selecting "Real-time" was the cause I first tried my old kernel 6.6.52 (built with "low-latency desktop") and this worked fine. So I rebuild 6.12.16 with "low-latency desktop" and put /etc/modules-load.d/virtualbox.conf back. The pc started fine and the XP VM started and worked as before. But when I look in dmesg I see this:
| Code: | [ 44.996525] ------------[ cut here ]------------
[ 44.996537] irq 55 handler nvkm_intr+0x0/0x240 enabled interrupts
[ 44.996550] WARNING: CPU: 32 PID: 0 at kernel/irq/handle.c:161 __handle_irq_event_percpu+0x180/0x190
[ 44.996562] Modules linked in: vboxnetflt(O) vboxnetadp(O) vboxdrv(O) k10temp efivarfs
[ 44.996580] CPU: 32 UID: 0 PID: 0 Comm: swapper/32 Tainted: G O 6.12.16-gentoo #4
[ 44.996587] Tainted: [O]=OOT_MODULE
[ 44.996590] Hardware name: Supermicro Super Server/H11SSL-i, BIOS 1.0b 04/27/2018
[ 44.996594] RIP: 0010:__handle_irq_event_percpu+0x180/0x190
[ 44.996600] Code: e4 5b 5d 44 89 e0 41 5c 41 5d 41 5e e9 e9 82 e9 00 48 8b 13 44 89 ee 48 c7 c7 88 67 1d 9c c6 05 7f b7 b9 01 01 e8 40 2a f8 ff <0f> 0b eb a5 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90
[ 44.996605] RSP: 0018:ffffa7bcc6a10f68 EFLAGS: 00010282
[ 44.996611] RAX: 0000000000000000 RBX: ffff8f5f340c1e80 RCX: 0000000000000000
[ 44.996615] RDX: 0000000000010003 RSI: ffffffff9c16bb91 RDI: 00000000ffffffff
[ 44.996619] RBP: 0000000000000001 R08: 00000000ffffbfff R09: 0000000000000001
[ 44.996623] R10: 00000000ffffbfff R11: ffff8f6b2fc9e000 R12: 0000000000000000
[ 44.996627] R13: 0000000000000037 R14: ffff8f5f35260c00 R15: 0000000000000000
[ 44.996630] FS: 0000000000000000(0000) GS:ffff8f631fc00000(0000) knlGS:0000000000000000
[ 44.996635] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 44.996638] CR2: 00007fdb2c000020 CR3: 0000000c34454000 CR4: 00000000003506f0
[ 44.996642] Call Trace:
[ 44.996646] <IRQ>
[ 44.996651] ? __warn+0x80/0x130
[ 44.996658] ? __handle_irq_event_percpu+0x180/0x190
[ 44.996663] ? report_bug+0x18d/0x1c0
[ 44.996669] ? apic_mem_wait_icr_idle+0xb/0x20
[ 44.996677] ? handle_bug+0x53/0x90
[ 44.996683] ? exc_invalid_op+0x13/0x60
[ 44.996689] ? asm_exc_invalid_op+0x16/0x20
[ 44.996699] ? __handle_irq_event_percpu+0x180/0x190
[ 44.996705] ? __handle_irq_event_percpu+0x180/0x190
[ 44.996711] handle_irq_event+0x32/0x70
[ 44.996716] handle_edge_irq+0xa3/0x250
[ 44.996722] __common_interrupt+0x60/0xe0
[ 44.996729] common_interrupt+0x9f/0xc0
[ 44.996735] </IRQ>
[ 44.996738] <TASK>
[ 44.996741] asm_common_interrupt+0x22/0x40
[ 44.996747] RIP: 0010:cpuidle_enter_state+0xc2/0x410
[ 44.996752] Code: 00 e8 c2 85 15 ff e8 0d f2 ff ff 8b 53 04 49 89 c5 0f 1f 44 00 00 31 ff e8 4b c5 14 ff 45 84 ff 0f 85 a5 01 00 00 fb 45 85 f6 <0f> 88 81 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d 0c c4 48
[ 44.996757] RSP: 0018:ffffa7bcc6407e98 EFLAGS: 00000202
[ 44.996762] RAX: ffff8f631fc00000 RBX: ffff8f5f34668800 RCX: 000000000000001f
[ 44.996765] RDX: 0000000000000020 RSI: ffffffff9c16bb91 RDI: ffffffff9c1834de
[ 44.996769] RBP: 0000000000000002 R08: 0000000000000002 R09: 000000484f6a1e80
[ 44.996772] R10: 0000000000000018 R11: ffff8f631fc2bae4 R12: ffffffff9c5eb480
[ 44.996775] R13: 0000000a7a0034b5 R14: 0000000000000002 R15: 0000000000000000
[ 44.996784] ? cpuidle_enter_state+0xb5/0x410
[ 44.996790] cpuidle_enter+0x24/0x40
[ 44.996797] do_idle+0x1a6/0x200
[ 44.996805] cpu_startup_entry+0x20/0x30
[ 44.996810] start_secondary+0xf2/0x100
[ 44.996817] common_startup_64+0x12c/0x138
[ 44.996828] </TASK>
[ 44.996830] ---[ end trace 0000000000000000 ]--- |
Now as it would be too long to list all here:
kernel config: https://quirinus.one/gentoo/kernel_6.12.16_20250308/.config
kernel.log from last boot from /var/log/kernel.log: https://quirinus.one/gentoo/kernel_6.12.16_20250308/kern.log
dmesg: https://quirinus.one/gentoo/kernel_6.12.16_20250308/dmesg
emerge -info: https://quirinus.one/gentoo/kernel_6.12.16_20250308/emerge.info
@world: https://quirinus.one/gentoo/kernel_6.12.16_20250308/world
emerge log (from last update @world): https://quirinus.one/gentoo/kernel_6.12.16_20250308/emerge.log_update_world.log
portage config: https://quirinus.one/gentoo/kernel_6.12.16_20250308/portage.config
| Code: | * sys-kernel/gentoo-sources
Latest version available: 6.12.16
Latest version installed: 6.12.16
Size of files: 145619 KiB
Homepage: https://dev.gentoo.org/~mpagano/genpatches
Description: Full sources including the Gentoo patchset for the 6.12 kernel tree
License: GPL-2 |
| Code: | * app-emulation/virtualbox
Latest version available: 7.1.4
Latest version installed: 7.1.4
Size of files: 202941 KiB
Homepage: https://www.virtualbox.org/
Description: Family of powerful x86 virtualization products for enterprise and home use
License: GPL-2+ GPL-3 LGPL-2.1 MIT dtrace? ( CDDL )
* app-emulation/virtualbox-additions
Latest version available: 7.1.4
Latest version installed: 7.1.4
Size of files: 58300 KiB
Homepage: https://www.virtualbox.org/
Description: CD image containing guest additions for VirtualBox
License: GPL-3 || ( GPL-3 CDDL )
* app-emulation/virtualbox-extpack-oracle
Latest version available: 7.1.4
Latest version installed: 7.1.4
Size of files: 22429 KiB
Homepage: https://www.virtualbox.org/
Description: PUEL extensions for VirtualBox
License: PUEL-12
* app-emulation/virtualbox-guest-additions
Latest version available: 7.1.4
Latest version installed: 7.1.4
Size of files: 201392 KiB
Homepage: https://www.virtualbox.org/
Description: VirtualBox kernel modules and user-space tools for Gentoo guests
License: GPL-3 LGPL-2.1+ MIT || ( GPL-3 CDDL )
* app-emulation/virtualbox-kvm [ Masked ]
Latest version available: 7.1.6a_pre20250207
Latest version installed: [ Not Installed ]
Size of files: 201987 KiB
Homepage: https://www.virtualbox.org/ https://github.com/cyberus-technology/virtualbox-kvm
Description: Family of powerful x86 virtualization products for enterprise and home use
License: GPL-2+ GPL-3 LGPL-2.1 MIT dtrace? ( CDDL )
* app-emulation/virtualbox-modules
Latest version available: 7.1.4-r1
Latest version installed: 7.1.4-r1
Size of files: 721 KiB
Homepage: https://www.virtualbox.org/
Description: Kernel Modules for Virtualbox
License: GPL-3
[ Applications found : 6 ]
|
_________________
Expert in non-working solutions |
|
| Back to top |
|
 |
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1051
Location: Belgium
|
| Posted: Tue Mar 11, 2025 6:48 pm Post subject: |
|
|
I have no idea where to look for this but it doesn't seem related to the kernel. Or at least not to being in the kernel itself. Could be that it only manifest itself with this kernel however because I do not see this with my old 6.6.52.
If I change time between me logging in (boot > terminal > entering user > entering password) ....waiting..... and then "startx" the time in the dmesg changes with it. So it is something that is triggered when X starts. Here I waited about one minute (wich I normally not do). And it just shifted along.
| Code: | [ 10.784151] bond0: active interface up!
[ 11.270650] igb 0000:04:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[ 11.409030] bond0: (slave eno1): link status definitely up, 1000 Mbps full duplex
[ 112.866916] ------------[ cut here ]------------
[ 112.866920] irq 55 handler nvkm_intr+0x0/0x210 enabled interrupts
[ 112.866932] WARNING: CPU: 32 PID: 0 at kernel/irq/handle.c:161 __handle_irq_event_percpu+0x172/0x180
[ 112.866939] Modules linked in: ccp k10temp efivarfs
[ 112.866945] CPU: 32 UID: 0 PID: 0 Comm: swapper/32 Tainted: G O 6.12.16-gentoo #5
[ 112.866949] Tainted: [O]=OOT_MODULE
[ 112.866951] Hardware name: Supermicro Super Server/H11SSL-i, BIOS 1.0b 04/27/2018
[ 112.866952] RIP: 0010:__handle_irq_event_percpu+0x172/0x180
[ 112.866956] Code: ff ff 45 31 e4 5b 5d 44 89 e0 41 5c 41 5d 41 5e c3 48 8b 13 44 89 ee 48 c7 c7 a8 1a 66 9a c6 05 c4 ae 78 01 01 e8 fe bf f9 ff <0f> 0b eb a9 66 2e 0f 1f 84 00 00 00 00 00 55 53 48 89 fb e8 76 fe
[ 112.866959] RSP: 0018:ffff981f06a10f68 EFLAGS: 00010282
[ 112.866961] RAX: 0000000000000000 RBX: ffff8fb1750d7d00 RCX: 0000000000000000
[ 112.866963] RDX: 0000000000010003 RSI: 0000000000000027 RDI: 00000000ffffffff
[ 112.866965] RBP: 0000000000000001 R08: 00000000ffffbfff R09: 0000000000000001
[ 112.866966] R10: 00000000ffffbfff R11: ffff8fbd6fc9b000 R12: 0000000000000000
[ 112.866967] R13: 0000000000000037 R14: ffff8fb17516ec00 R15: 0000000000000000
[ 112.866968] FS: 0000000000000000(0000) GS:ffff8fb55fc00000(0000) knlGS:0000000000000000
[ 112.866970] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 112.866971] CR2: 00007ff6c0000020 CR3: 00000004346ca000 CR4: 00000000003506f0
[ 112.866973] Call Trace:
[ 112.866976] <IRQ>
[ 112.866977] ? __warn+0x80/0x130
[ 112.866981] ? __handle_irq_event_percpu+0x172/0x180
[ 112.866984] ? report_bug+0x189/0x1c0
[ 112.866988] ? prb_read_valid+0x12/0x20
[ 112.866991] ? handle_bug+0x4f/0x90
[ 112.866994] ? exc_invalid_op+0x13/0x60
[ 112.866995] ? asm_exc_invalid_op+0x16/0x20
[ 112.866999] ? __handle_irq_event_percpu+0x172/0x180
[ 112.867002] ? __handle_irq_event_percpu+0x172/0x180
[ 112.867004] handle_irq_event+0x32/0x70
[ 112.867007] handle_edge_irq+0xa4/0x200
[ 112.867010] __common_interrupt+0x5c/0xe0
[ 112.867013] common_interrupt+0x9f/0xc0
[ 112.867016] </IRQ>
[ 112.867017] <TASK>
[ 112.867018] asm_common_interrupt+0x22/0x40
[ 112.867020] RIP: 0010:cpuidle_enter_state+0xbd/0x420
[ 112.867023] Code: 00 e8 47 ff 3f ff e8 92 f4 ff ff 8b 53 04 49 89 c5 0f 1f 44 00 00 31 ff e8 b0 53 3f ff 45 84 ff 0f 85 af 01 00 00 fb 45 85 f6 <0f> 88 86 01 00 00 49 63 ce 4c 8b 14 24 48 8d 04 49 48 8d 14 81 48
[ 112.867025] RSP: 0018:ffff981f06407ea0 EFLAGS: 00000202
[ 112.867026] RAX: ffff8fb55fc00000 RBX: ffff8fb174550000 RCX: 000000000000001f
[ 112.867028] RDX: 0000000000000020 RSI: ffffffff9a5fad30 RDI: ffffffff9a611678
[ 112.867029] RBP: 0000000000000002 R08: 0000000000000002 R09: 0000000000000006
[ 112.867030] R10: 0000001a4763ee9a R11: 0000000000000002 R12: ffffffff9a9e3820
[ 112.867031] R13: 0000001a476436de R14: 0000000000000002 R15: 0000000000000000
[ 112.867034] cpuidle_enter+0x2a/0x40
[ 112.867038] do_idle+0xe3/0x180
[ 112.867042] cpu_startup_entry+0x20/0x30
[ 112.867045] start_secondary+0xe0/0xe0
[ 112.867049] common_startup_64+0x12c/0x138
[ 112.867053] </TASK>
[ 112.867054] ---[ end trace 0000000000000000 ]--- |
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5514
Location: Bavaria
|
| Posted: Wed Mar 12, 2025 1:22 am Post subject: |
|
|
| Spanik wrote: | [...] but it doesn't seem related to the kernel. Or at least not to being in the kernel itself. [...] So it is something that is triggered when X starts. [...]
| Code: | [ 112.866994] ? exc_invalid_op+0x13/0x60
[ 112.866995] ? asm_exc_invalid_op+0x16/0x20 |
|
Yes, I also think your kernel is okay. I dont know how to find the cause for the trap ... but an "invalid operation code" smells like a problem when compiling "something" (sorry I dont know what) with wrong options.
I have not answered because I cannot help here. If nobody jumps in the only hint I could give is to recompile everything (emerge -e).
(Another hint: Always listen to our admins (and moderators) ... see your old thread).
_________________
https://wiki.gentoo.org/wiki/User:Pietinger |
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1051
Location: Belgium
|
| Posted: Wed Mar 12, 2025 10:16 am Post subject: |
|
|
| pietinger wrote: | Yes, I also think your kernel is okay. I dont know how to find the cause for the trap ... but an "invalid operation code" smells like a problem when compiling "something" (sorry I dont know what) with wrong options.
I have not answered because I cannot help here. If nobody jumps in the only hint I could give is to recompile everything (emerge -e). |
Compiling everything again will have to wait to next week as I'm leaving this afternoon and a full recompile will take longer than that.
What I could try is to pull in TWM and start X with that.
| Quote: | | (Another hint: Always listen to our admins (and moderators) ... see your old thread). |
Don't see what I missed this time...
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1051
Location: Belgium
|
| Posted: Wed Mar 12, 2025 10:50 am Post subject: |
|
|
| Spanik wrote: | | What I could try is to pull in TWM and start X with that. |
When using startx with TWM this does not happen. So it looks as if it is while kde/plasma6 is starting.
Up to the total recompile next week...
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5514
Location: Bavaria
|
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1051
Location: Belgium
|
| Posted: Wed Mar 12, 2025 1:49 pm Post subject: |
|
|
When I first found this in my dmesg and it was only when using 6.12.16 and not 6.6.52 I assumed it was a kernel related issue, not related to what was in that thread.
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
Yamakuzure
Advocate
Joined: 21 Jun 2006
Posts: 2311
Location: Adendorf, Germany
|
| Posted: Fri Mar 14, 2025 8:11 am Post subject: |
|
|
When searching for "nvkm_intr exc_invalid_op asm_exc_invalid_op" via google, most top hits talk about clashing nvidia versus nouveau drivers.
X+TWM is software only. Plasma6 makes use of 3d hardware, so that makes sense.
What GPU do you have and which drivers do you use?
Edith found out:
So your dmesg says
| Code: | | [ 1.006182] nouveau 0000:21:00.0: NVIDIA GF119 (0d90a0a1) |
And then Edith found:
https://bugzilla.kernel.org/show_bug.cgi?id=219507
Please have a look here.
_________________
Edited 220,176 times by Yamakuzure |
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1051
Location: Belgium
|
| Posted: Mon Mar 17, 2025 8:10 pm Post subject: |
|
|
| pietinger wrote: | | If nobody jumps in the only hint I could give is to recompile everything (emerge -e). |
Ok, first evening back at home. Started the "emerge -e @world".
| Yamakuzure wrote: | When searching for "nvkm_intr exc_invalid_op asm_exc_invalid_op" via google, most top hits talk about clashing nvidia versus nouveau drivers.
X+TWM is software only. Plasma6 makes use of 3d hardware, so that makes sense.
What GPU do you have and which drivers do you use?
Edith found out:
So your dmesg says
| Code: | | [ 1.006182] nouveau 0000:21:00.0: NVIDIA GF119 (0d90a0a1) |
And then Edith found:
https://bugzilla.kernel.org/show_bug.cgi?id=219507
Please have a look here. |
Interesting. I do indeed use nouveau without nvidia firmware, not needed according to the nouveau documentation and the version I use. But where the OT in the link uses an MSI GT710 I use an MSI GT610. So very similar.
I started the "emerge -e @world" just before this post and it has started rebuilding 1277 packages. So when that is finished I'll see what that does and if it doesn't make a change I'll use the workaround of disabling acceleration mentioned in comment 5 of the link. And come back on it.
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1051
Location: Belgium
|
| Posted: Tue Mar 18, 2025 6:20 pm Post subject: |
|
|
The "emerge -e @world" did not bring any change. So I tried what Yamakuzure linked:
I added the workaround in comment #5 and created a n/etc/X11/xorg.conf with
| Code: | Section "Device"
Identifier "device1"
Driver "nouveau"
Option "DPMS"
Option "NoAccel" "true"
EndSection |
and rebooted. And indeed, the kernel trap about the IRQ is gone. At the same time, graphics has become slower. It takes longer before the desktop is shown, opening a program takes longer before the screen is drawn, there are some artefacts at the edges when dragging a window around.
The issues I had with my W10 VM in Virtualbox are also gone. https://forums.gentoo.org/posting.php?mode=quote&p=8855614 The VM now starts, display scales with the window and if I open an explorer in W10 then it doesn't lock up anymore. But it is slower than before.
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
|
Kernel & Hardware
