You are not logged in.

Pages: 1

#1 2024-04-01 18:16:45

qualia
Member
Registered: 2024-01-01
Posts: 7

[SOLVED] Kernel Panic during Update D:

Hello. I had a kernel panic during an update and got left with a pretty messed up system. 

 pacman -Qkk | grep -v '0 altered files'

results in https://0x0.st/XzV8.txt. Is this salvageable? Here is my journal if that helps: https://0x0.st/XzVl.txt. Looks like maybe the first issue to address is something with dbus?

Last edited by qualia (2024-04-01 21:54:45)

Offline

#2 2024-04-01 20:40:05

seth
Member
Registered: 2012-09-03
Posts: 51,720

Re: [SOLVED] Kernel Panic during Update D:

https://wiki.archlinux.org/title/Pacman … an_upgrade
Don't forget to mount the boot partition into /mnt/boot after mounting the root partition there - if you have a boot partition.

alacritty bubblewrap dbus-broker-unerror discord ell flatpak iwd lib32-curl lib32-libva lib32-mesa lib32-vulkan-intel libbyerror liblc3 libmalcontent libmfx libpciaccess libreoffice-still libx11 luerror mesa openmpi poppler-glib prrte pyerror python-rpy2 ttf-monoid-nerd vulkan-intel xfcoerror xorgproto

You'll have to re-install all those packages first w/ --dbonly, then properly (pacman --sysroot /mnt --dbonly -Sy …; pacman --sysroot /mnt -S …)
"lain-git" and "ghc-static" look compromised, "nethack" perhaps - reinstall those, too
Finally run "pacman --sysroot /mnt -Syu" and re-check the integrity.

The posted output has weird newline errors and some parts seem missing, don't copy and paste out of the console, redirect the ouptut into a file and upload it to 0x0.st (1st link below) if need be.
It also means that the above list might be incomplete or contain "typos" (awk doesn't really typo, but you get the point wink)

Edit:
https://bugs.archlinux.org/task/77789, Try to add 

sudo touch /etc/systemd/do-not-udevadm-trigger-on-update

Last edited by seth (2024-04-01 20:40:24)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2024-04-01 21:55:21

qualia
Member
Registered: 2024-01-01
Posts: 7

Re: [SOLVED] Kernel Panic during Update D:

This did it... Seth, you are so beautiful and amazing thank you so much for taking the time to help people!

Offline

#4 2024-04-05 21:48:03

seth
Member
Registered: 2012-09-03
Posts: 51,720

Re: [SOLVED] Kernel Panic during Update D:

Hi, do you still recall the nature of the update crash?
Did the system suddenly reboot or did it stall and you then rebooted it with the power button?

---
This is a mass-inquiry, so please excuse if your thread actually detailed that.
We're trying to get some data on the situation, so it would be very helpful if you can just briefly respond.
Thanks a lot.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2024-04-14 21:15:43

Grandfather-Paradox
Member
Registered: 2017-08-22
Posts: 19

Re: [SOLVED] Kernel Panic during Update D:

This has been happening to me constantly for the last 1-2 months. Is anyone else having recurring issues with this?

Offline

#6 2024-04-14 21:22:50

seth
Member
Registered: 2012-09-03
Posts: 51,720

Re: [SOLVED] Kernel Panic during Update D:

Yes.
Do you
1. use the binary nvidia
2. have nvidia_uvm loaded (lsmod | grep uvm)
3. have added /etc/systemd/do-not-udevadm-trigger-on-update

Also how "constantly"? Only when systemd was updated or also on other updates?
We're pretty sure that it's the 550xx driver, unsure whether it's just teh nvidia_uvm module and also not which exact event (systemd daemon-reexec or udev trigger) triggers this.
Afawk nvidia-open is not affected (but has other caveats, you want to read the github readme before deciding on that)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2024-04-14 21:30:11

Grandfather-Paradox
Member
Registered: 2017-08-22
Posts: 19

Re: [SOLVED] Kernel Panic during Update D:

seth wrote:

Yes.
Do you
1. use the binary nvidia
2. have nvidia_uvm loaded (lsmod | grep uvm)
3. have added /etc/systemd/do-not-udevadm-trigger-on-update

Also how "constantly"? Only when systemd was updated or also on other updates?
We're pretty sure that it's the 550xx driver, unsure whether it's just teh nvidia_uvm module and also not which exact event (systemd daemon-reexec or udev trigger) triggers this.
Afawk nvidia-open is not affected (but has other caveats, you want to read the github readme before deciding on that)

Hi Seth,
1. Yes, I use the binary nvidia driver.
2. Yes, nvidia_uvm is loaded.
3. I just added /etc/systemd/do-not-udevadm-trigger-on-update after reading it on here. Should I leave that?

It doesn't happen on every update, but it happens on updates with and without systemd being installed. As others noted, I'm pretty sure it happens during the post-transaction hooks.

Offline

#8 2024-04-14 21:46:01

seth
Member
Registered: 2012-09-03
Posts: 51,720

Re: [SOLVED] Kernel Panic during Update D:

Leave the file in place - if it's the udevadm trigger, the crashes will stop.
If they don't stop, blacklist the nvidia_uvm module ("module_blacklist=nvidia_uvm", https://wiki.archlinux.org/title/Kernel_parameters - the module is relevant to CUDA which next to actual GPGPU stuff you might or not use for HW video en-/decoding)

If you're hitting this frequently enough (sorry for the trouble) we migth finally get ahead with this…

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2024-04-14 21:52:00

Grandfather-Paradox
Member
Registered: 2017-08-22
Posts: 19

Re: [SOLVED] Kernel Panic during Update D:

seth wrote:

Leave the file in place - if it's the udevadm trigger, the crashes will stop.
If they don't stop, blacklist the nvidia_uvm module ("module_blacklist=nvidia_uvm", https://wiki.archlinux.org/title/Kernel_parameters - the module is relevant to CUDA which next to actual GPGPU stuff you might or not use for HW video en-/decoding)

If you're hitting this frequently enough (sorry for the trouble) we migth finally get ahead with this…

Happy to help if I can - it's been driving me crazy. So far, after adding that file, I ran an update with quite a few packages and didn't have any crash. These packages were updated for reference:

Packages (79) aspnet-targeting-pack-8.0.4.sdk104-1  attica-6.1.0-1  breeze-icons-6.1.0-1  calibre-7.8.0-3
              chromium-124.0.6367.49-1  dotnet-host-8.0.4.sdk104-1  dotnet-runtime-8.0.4.sdk104-1
              dotnet-sdk-8.0.4.sdk104-1  dotnet-targeting-pack-8.0.4.sdk104-1  gegl-0.4.48-2
              gnome-online-accounts-3.50.1-1  karchive-6.1.0-1  kauth-6.1.0-1  kbookmarks-6.1.0-1  kcmutils-6.1.0-1
              kcodecs-6.1.0-1  kcolorscheme-6.1.0-1  kcompletion-6.1.0-1  kconfig-6.1.0-1  kconfigwidgets-6.1.0-1
              kcontacts-1:6.1.0-1  kcoreaddons-6.1.0-1  kcrash-6.1.0-1  kdbusaddons-6.1.0-1  kdnssd-6.1.0-1
              kglobalaccel-6.1.0-1  kguiaddons-6.1.0-1  ki18n-6.1.0-1  kiconthemes-6.1.0-1  kidletime-6.1.0-1
              kio-6.1.0-1  kirigami-6.1.0-1  kitemmodels-6.1.0-1  kitemviews-6.1.0-1  kjobwidgets-6.1.0-1
              knewstuff-6.1.0-1  knotifications-6.1.0-1  knotifyconfig-6.1.0-1  kpackage-6.1.0-1  kparts-6.1.0-1
              kservice-6.1.0-1  kstatusnotifieritem-6.1.0-1  ktexttemplate-6.1.0-1  ktextwidgets-6.1.0-1
              kwallet-6.1.0-1  kwidgetsaddons-6.1.0-1  kwindowsystem-6.1.0-1  kxmlgui-6.1.0-1  less-1:643-2
              lib32-mesa-1:24.0.5-1  libcap-ng-0.8.5-1  libgoa-3.50.1-1  libplacebo-6.338.2-4  libwireplumber-0.5.1-2
              linux-6.8.5.arch1-1  linux-lts-6.6.27-1  linux-lts-headers-6.6.27-1  mesa-1:24.0.5-1
              netstandard-targeting-pack-8.0.4.sdk104-1  nvidia-550.67-6  nvidia-lts-1:550.67-6  onetbb-2021.12.0-1
              pcsclite-2.1.0-2  prison-6.1.0-1  solid-6.1.0-1  sonnet-6.1.0-1  subtitleedit-4.0.5-1
              syndication-6.1.0-1  syntax-highlighting-6.1.0-1  ttf-noto-nerd-3.2.1-1  webkit2gtk-2.44.1-1
              webkit2gtk-4.1-2.44.1-1  webkitgtk-6.0-2.44.1-1  wireplumber-0.5.1-2  xdg-desktop-portal-1.18.3-1
              xorg-server-21.1.13-1  xorg-server-common-21.1.13-1  xorg-server-devel-21.1.13-1
              xorg-server-xvfb-21.1.13-1

Edit: Adding post-transaction hooks as well.

:: Running post-transaction hooks...
( 1/15) Reloading system manager configuration...
( 2/15) Reloading user manager configuration...
( 3/15) Arming ConditionNeedsUpdate...
( 4/15) Updating the MIME type database...
( 5/15) Updating module dependencies...
( 6/15) Install DKMS modules
==> dkms install --no-depmod vboxhost/7.0.14_OSE -k 6.6.27-1-lts
==> depmod 6.6.27-1-lts
( 7/15) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: '6.6.27-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: '6.6.27-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts-fallback.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: '6.8.5-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_420xx'
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.8.5-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_420xx'
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> Initcpio image generation successful
( 8/15) Reloading system bus configuration...
( 9/15) Updating fontconfig cache...
(10/15) Updating 32-bit fontconfig cache...
(11/15) Compiling GSettings XML schema files...
(12/15) Updating icon theme caches...
(13/15) Update Nvidia module in initcpio
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: '6.6.27-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: '6.6.27-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts-fallback.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: '6.8.5-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_420xx'
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.8.5-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_420xx'
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> Initcpio image generation successful
(14/15) Remove unused package files cached by pikaur in user's home directory
==> no candidate packages found for pruning
(15/15) Updating the desktop file MIME type cache...

Last edited by Grandfather-Paradox (2024-04-14 21:53:48)

Offline

#10 2024-04-14 22:07:11

Grandfather-Paradox
Member
Registered: 2017-08-22
Posts: 19

Re: [SOLVED] Kernel Panic during Update D:

seth wrote:

Leave the file in place - if it's the udevadm trigger, the crashes will stop.
If they don't stop, blacklist the nvidia_uvm module ("module_blacklist=nvidia_uvm", https://wiki.archlinux.org/title/Kernel_parameters - the module is relevant to CUDA which next to actual GPGPU stuff you might or not use for HW video en-/decoding)

If you're hitting this frequently enough (sorry for the trouble) we migth finally get ahead with this…

Two more noteworthy things I forgot to mention. Frequently, when I attempt to reboot my computer, it gets stuck on one of the steps. This started at the same time as the crashes with updating. This is responsive to SysRq commands, however. The following was in the logs for this event:

10:00:27 PM bluetoothd: Failed to add UUID: Failed (0x03)
10:00:23 PM gdm-session-wor: gkr-pam: unable to locate daemon control file
10:00:21 PM bluetoothd: Failed to add UUID: Failed (0x03)
10:00:17 PM kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
10:00:17 PM systemd-udevd: /etc/udev/rules.d/S99-2000S1.rules:26 GOTO="libsane_rules_end" has no matching label, ignoring.
10:00:16 PM kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
10:00:15 PM (uetoothd): Failed to add UUID: Failed (0x03)
10:00:14 PM kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
10:00:12 PM kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
10:00:12 PM systemd-modules: Failed to find module 'vboxpci'
10:00:12 PM kernel: 
10:00:12 PM systemd-udevd: /etc/udev/rules.d/S99-2000S1.rules:26 GOTO="libsane_rules_end" has no matching label, ignoring.
10:00:11 PM systemd: Failed to start Remount Root and Kernel File Systems.
10:00:11 PM systemd-remount: /usr/bin/mount for / exited with exit status 1.

I am also experiencing occasional kernel panics when interacting with the UI. I just experienced one when attempting to reply to your post, when I clicked the "quote" button. I have no way of knowing if this is related, but if it's an issue with the Nvidia driver, it might make sense.

Offline

#11 2024-04-14 22:16:51

Grandfather-Paradox
Member
Registered: 2017-08-22
Posts: 19

Re: [SOLVED] Kernel Panic during Update D:

I have now blacklisted nvidia_uvm and rebooted, so we'll see if that stops the crashes.

Offline

#12 2024-04-15 07:22:26

seth
Member
Registered: 2012-09-03
Posts: 51,720

Re: [SOLVED] Kernel Panic during Update D:

Frequently, when I attempt to reboot my computer, it gets stuck on one of the steps.

https://bbs.archlinux.org/viewtopic.php?id=293400 but w/ the tail of the journal also https://bbs.archlinux.org/viewtopic.php?id=294399

I am also experiencing occasional kernel panics when interacting with the UI. I just experienced one when attempting to reply to your post

nvidia ./. cgroupfs will rather not cause such symptoms, but do you have a backtrace from such panic?
Maybe the GPU is just generally unstable?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2024-04-15 21:54:37

Grandfather-Paradox
Member
Registered: 2017-08-22
Posts: 19

Re: [SOLVED] Kernel Panic during Update D:

seth wrote:

Frequently, when I attempt to reboot my computer, it gets stuck on one of the steps.

https://bbs.archlinux.org/viewtopic.php?id=293400 but w/ the tail of the journal also https://bbs.archlinux.org/viewtopic.php?id=294399

I am also experiencing occasional kernel panics when interacting with the UI. I just experienced one when attempting to reply to your post

nvidia ./. cgroupfs will rather not cause such symptoms, but do you have a backtrace from such panic?
Maybe the GPU is just generally unstable?

I've also been having issues with Bluetooth since this started, as I've seen others note. Usually I can turn it on with no problem, but then it fails to turn off if I try to shut it off and stops working. This doesn't cause a kernel panic, but it makes the system lock up when trying to reboot. I noticed this in the logs that may pertain to this problem:

Bluetooth: hci0: SCO packet for unknown connection handle 257

As far as the kernel panic backtrace, I don't believe I have that. I'm looking through the logs but don't see anything relevant. Is there anything I should set up that would give you the most useful information?

Offline

#14 2024-04-15 22:11:50

seth
Member
Registered: 2012-09-03
Posts: 51,720

Re: [SOLVED] Kernel Panic during Update D:

As far as the kernel panic backtrace, I don't believe I have that.

What are the symptoms of the panic (flashing keyboard LEDs? do you actually see errors in the console?) and can you reboot w/ the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) ?
(nb. that you've to explicitly enabled that first)
The moment you push the power button, all information will be lost

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#15 2024-04-15 22:16:02

Grandfather-Paradox
Member
Registered: 2017-08-22
Posts: 19

Re: [SOLVED] Kernel Panic during Update D:

seth wrote:

As far as the kernel panic backtrace, I don't believe I have that.

What are the symptoms of the panic (flashing keyboard LEDs? do you actually see errors in the console?) and can you reboot w/ the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) ?
(nb. that you've to explicitly enabled that first)
The moment you push the power button, all information will be lost

The screen remains completely frozen on whatever it was on, no responsiveness whatsoever. I have the SysRq keys enabled, and it doesn't respond to any of them in any way - REISUB has no effect. It stays like that until I force shutdown the computer.

Offline

Pages: 1

Board footer

Powered by FluxBB