crashing on boot up. what error is it?

quellen · 2025-02-16 20:24:31

hi, I just turned on my PC and during the boot screen this error appeared and I had to reset the PC (now it works perfectly):
https://i.postimg.cc/fygMn1PT/photo-202 … -16-58.jpg
(sorry for low quality)

What is it? I think it was caused by an old dvbt decoder that was connected to the USB: it has already happened to me other times that when I connected it the kernel crashed
I can't see the boot log because I disabled the journal

Last edited by quellen (2025-02-16 22:22:46)

seth · 2025-02-16 21:55:12

Please replace the oversized image w/ a link.
Have you googled "ir_raw_event_store"?
(You'll find that it's from the remote control driver stack, somewhat confirming your dvbt theory)

There's a nullptr deref, do you also have a picture that covers the call trace?

quellen · 2025-02-16 22:22:34

no, i only have that photo. i don't use the remote control so in theory i could disable that option but i don't know if it's possible to do it.

Last edited by quellen (2025-02-16 22:29:56)

seth · 2025-02-16 22:48:21

Compare "pacman -Ql linux | grep '/rc/'" and "lsmod" - you can likely just blackist the module.

quellen · 2025-02-17 10:04:51

ok i have blacklisted it (it was rc_hauppauge). Let's see if I can solve it like this...
thank you!

$ cat /etc/modprobe.d/modprobe.conf
alias rc_hauppauge off

quellen · 2025-03-22 12:13:20

seth wrote:

Compare "pacman -Ql linux | grep '/rc/'" and "lsmod" - you can likely just blackist the module.

the problem has not been solved. for example if I touch the decoder while I'm watching tv with mpv everything freezes and I can't even restart the pc.
who should I report this bug to?

(click to enlarge)
to restart I had to press the button on the case

Last edited by quellen (2025-03-22 12:18:21)

seth · 2025-03-22 12:39:29

Depends on what the problem actually is - please post your complete system journal for the boot, eg.

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

for the previous one.
The photo only shows mpv and journald not responding to sigterm.

"touch" means you access the device w/ a third process or means "with my fingers because it's some dongle"?

quellen · 2025-03-22 13:13:52

seth wrote:

Depends on what the problem actually is - please post your complete system journal for the boot, eg.
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
for the previous one.
The photo only shows mpv and journald not responding to sigterm.
"touch" means you access the device w/ a third process or means "with my fingers because it's some dongle"?

touch with finger. maybe the usb connector is worn out and you just move it a little to disconnect it
I don't have the journal, I had disabled it to avoid wearing out the SSD

Last edited by quellen (2025-03-22 13:23:56)

seth · 2025-03-22 13:50:47

Have you tried
1. the behavior on a different port (I've a dvb-c adapter that's kinda peculiar and will cause sth. like this on S3 and one usb-2 hub, but not the another (and I assume it's power supply related - not all ports are made the same)
2. what happens when at this point you just completely yank the adapter
3. duct-tape

Arch Linux

#1 2025-02-16 20:24:31

crashing on boot up. what error is it?

#2 2025-02-16 21:55:12

Re: crashing on boot up. what error is it?

#3 2025-02-16 22:22:34

Re: crashing on boot up. what error is it?

#4 2025-02-16 22:48:21

Re: crashing on boot up. what error is it?

#5 2025-02-17 10:04:51

Re: crashing on boot up. what error is it?

#6 2025-03-22 12:13:20

Re: crashing on boot up. what error is it?

#7 2025-03-22 12:39:29

Re: crashing on boot up. what error is it?

#8 2025-03-22 13:13:52

Re: crashing on boot up. what error is it?

#9 2025-03-22 13:50:47

Re: crashing on boot up. what error is it?

Board footer