MX Linux Forum

Posted: **Wed Jan 24, 2024 9:41 am**

I used the Snapshot tool to make a ISO from my running system, and then used the Live USB Maker tool to put it on my flash drive.
When I booted the flash drive, I got some kind of kernel panic.
I thought this was maybe because of the liquorix kernel, so I made a second snapshot, this time using the default 6.1 Debian kernel. But it was the same kernel panic.
See photo:

Posted: **Wed Jan 24, 2024 9:42 am**

My QSI

Code: Select all

System:
  Kernel: 6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.6.12-1-liquorix-amd64
    root=UUID=<filter> ro quiet splash init=/lib/systemd/systemd
  Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_wayland vt: 1 dm: SDDM
    Distro: MX-23.2_ahs_x64 Libretto October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B365M-A v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 2208 date: 07/09/2021
Battery:
  ID-1: hidpp_battery_0 charge: 28% condition: N/A volts: 3.7 min: N/A model: Logitech G903
    LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A serial: <filter> status: discharging
CPU:
  Info: model: Intel Core i7-9700 bits: 64 type: MCP arch: Coffee Lake gen: core 9 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xD (13)
    microcode: 0xFA
  Topology: cpus: 1x cores: 8 smt: <unsupported> cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB
    L2: 2 MiB desc: 8x256 KiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 3000 high: 3001 min/max: N/A cores: 1: 3000 2: 3001 3: 3000 4: 3001 5: 3000
    6: 3001 7: 3000 8: 3000 bogomips: 48000
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1,HDMI-A-2 empty: DP-1
    bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
  Device-2: USB C Video Adaptor type: USB driver: N/A bus-ID: 1-3.1.1:8 chip-ID: 25a4:9321
    class-ID: 1100 serial: <filter>
  Device-3: Microdia USB Live camera type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-3.4:7
    chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_wayland
    driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: HDMI-A-1 model: VG27AQ1A serial: <filter> built: 2020 res: 2560x1440 dpi: 109
    gamma: 1.2 size: 596x336mm (23.46x13.23") diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440
    min: 720x400
  Monitor-2: HDMI-A-2 model: Samsung S24B300 serial: <filter> built: 2013 res: 1920x1080 dpi: 94
    gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 1-3.4:7 chip-ID: 0c45:636b alternate: snd_soc_avs class-ID: 0102 bus-ID: 00:1f.3
    serial: <filter> chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: Microdia USB Live camera type: USB driver: snd-usb-audio,uvcvideo
  API: ALSA v: k6.6.12-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 2-3.1:6
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  IF: eth1 state: down mac: <filter>
  IF-ID-1: virbr0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-2: vnet0 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
    bus-ID: 1-9:6 chip-ID: 0a12:0001 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
    sub-v: 22bb hci-v: 4.0 rev: 22bb
  Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 2.26 TiB used: 1004.51 GiB (43.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G size: 447.13 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: K1B3 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD120 size: 1.82 TiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ACF0
    scheme: GPT
Partition:
  ID-1: / raw-size: 81.6 GiB size: 80.01 GiB (98.06%) used: 30.57 GiB (38.2%) fs: ext4
    dev: /dev/sda6 maj-min: 8:6
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 50.6 MiB (52.7%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 33.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2699 pm: dpkg pkgs: 2689 libs: 1464 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 10
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://it.mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://it.mxrepo.com/mx/repo/ bookworm ahs
Info:
  Processes: 403 Uptime: 22m wakeups: 2 Memory: 15.49 GiB used: 5.28 GiB (34.1%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Wed Jan 24, 2024 10:26 am**

If you use Ventoy to create the USB drive, you must upgrade Ventoy to its latest version. The earlier versions of Ventoy are incompatible with MX 23.

Posted: **Wed Jan 24, 2024 10:31 am**

shmu26 wrote: Wed Jan 24, 2024 9:41 am... used the Live USB Maker tool to put it on my flash drive.

j2mcgreg wrote: Wed Jan 24, 2024 10:26 am... If you use Ventoy to create the USB drive, you must ...

Posted: **Wed Jan 24, 2024 10:42 am**

I don't know what's going on, could it be some kernel options (even if you changed kernels)?

Why do you use rcupdate.rcu_expedited=1

Posted: **Wed Jan 24, 2024 10:53 am**

Adrian wrote: Wed Jan 24, 2024 10:42 am... Why do you use rcupdate.rcu_expedited=1 ...

It seems Liquorix does it , same here :

Kernel: 6.7.1-1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0 intel_pstate=disable rcupdate.rcu_expedited=1
BOOT_IMAGE=/boot/vmlinuz-6.7.1-1-liquorix-amd64 root=UUID=xxxx ro quiet nosplash

Posted: **Wed Jan 24, 2024 10:56 am**

did you try to keep the init=/lib/systemd/systemd line? that's not going to work.

I think you are crashing before that though.

Posted: **Wed Jan 24, 2024 10:57 am**

Adrian wrote: Wed Jan 24, 2024 10:42 am I don't know what's going on, could it be some kernel options (even if you changed kernels)?

Why do you use rcupdate.rcu_expedited=1

Just to clear things up, I did not use ventoy, I used the MX Linux Live USB Maker tool.

As for Kernel options: My system has the metapackage for liquorix kernel, and the default Debian 6.1 kernel.
I did not set any options for them.

I don't know what rcupdate.rcu_expedited=1 means, but maybe it is related to the metapackage for liquorix?

But one sin (two sins?) I can confess to is that I booted my real system with systemd, and also logged in with wayland, when I made both the ISO and the live flash drive. Could that be relevant?

Posted: **Wed Jan 24, 2024 11:02 am**

dolphin_oracle wrote: Wed Jan 24, 2024 10:56 am did you try to keep the init=/lib/systemd/systemd line? that's not going to work.

I think you are crashing before that though.

Is this a decision I would make when creating the ISO, or when booting? But either way, I did things the default way. With the exception that for the second ISO , I chose the 6.1 kernel.

Posted: **Wed Jan 24, 2024 11:12 am**

Maybe post the log files, perhaps for both mx-snapshot and mx-live-usb-maker,
probably still be accessible through QSI-tool.

Posted: **Wed Jan 24, 2024 11:15 am**

Like fehlix I think you crash before systemd, but systemd is problematic on Live environment that's one of the main reason we boot by default to sysVinit. Try to edit the kernel line (you should have an option before it boots to edit the line, I guess it depends on how exactly you boot).

When you take a snapshot you have an option to edit the kernel line too. Maybe we should filter out systemd option by default, @fehlix, what do you think?

Posted: **Wed Jan 24, 2024 11:17 am**

fehlix wrote: Wed Jan 24, 2024 11:12 am Maybe post the log files, perhaps for both mx-snapshot and mx-live-usb-maker,
probably still be accessible through QSI-tool.

attached

Posted: **Wed Jan 24, 2024 11:31 am**

Adrian wrote: Wed Jan 24, 2024 11:15 am
When you take a snapshot you have an option to edit the kernel line too. Maybe we should filter out systemd option by default, @fehlix, what do you think?

I boot systemd but when making snapshots, systemd is not in my boot options by default (nor do I add it).

quickshot_240124_082640.jpg

Posted: **Wed Jan 24, 2024 11:42 am**

Minutes ago I started up my desktop tower computer from the HDD as I always do and had some weird activity: some box appeared first which I've NEVER seen before. I think that box wanted me to pick something but it disappeared soon and more bizarre behavior occurred. Somehow I opened up Pale Moon just to consult this forum-- I didn't want to just re-boot because I thought maybe things will be far worse if I do that.

With MX23, I'm using 6.6.12-1-liquorix-amd64 which is the latest in this series.

Is this strange, weird start-up and early OS operation behavior I encountered the same as what was happening to the originator of this thread?

Posted: **Wed Jan 24, 2024 11:46 am**

Did you post in a wrong thread, what does have to do with the kernel panic?

Posted: **Wed Jan 24, 2024 11:55 am**

Adrian, I'm no expert in kernel panics. I just thought what happened to me might be the same as or similar to what happened to the MX user who started this thread. With reliable, steady MX, everything always goes well for me every day for years and then suddenly, out-of-the-blue, something bizarre occurs and I don't know what to make of it nor know what to do to end it. I suppose I can just re-boot now and see if the same thing happens, but tell me first if that's a good idea to do.

Posted: **Wed Jan 24, 2024 12:17 pm**

sps7 wrote: Wed Jan 24, 2024 11:55 am Adrian, I'm no expert in kernel panics. I just thought what happened to me might be the same as or similar to what happened to the MX user who started this thread. With reliable, steady MX, everything always goes well for me every day for years and then suddenly, out-of-the-blue, something bizarre occurs and I don't know what to make of it nor know what to do to end it. I suppose I can just re-boot now and see if the same thing happens, but tell me first if that's a good idea to do.

Doesn't sound anything related, you'd know if you have a kernel panic.

Posted: **Wed Jan 24, 2024 12:20 pm**

OK, thanks Adrian.

Posted: **Wed Jan 24, 2024 3:34 pm**

It's the OP again, so I made a snapshot on a sysvinit session, and I still get kernel panic.
new logs attached.
The snapshot log is a link because it was to large to upload.
https://www.dropbox.com/scl/fi/ugf1e9ph ... 4akvg&dl=0

Posted: **Wed Jan 24, 2024 3:40 pm**

how about your excludes file?

Posted: **Wed Jan 24, 2024 4:12 pm**

What if you use a different usb stick?

It may be due to faulty hardware.

(You can also change splash to nosplash on the installed system to see if the same /similar is on the installed system (though it manages to boot)).

Also you can try (other than trying another stick): re-generate the initrd image(s) (on the installed system) then create the snapshot :

Code: Select all

sudo update-initramfs -uk all

Posted: **Wed Jan 24, 2024 4:20 pm**

Can you boot the ISO in a VM? Do you have anything set up on the computer, VirtualBox, VMWare, KVM? You could try the ISO in a VM that would eliminate the USB question.

Posted: **Wed Jan 24, 2024 6:44 pm**

Or add a fromiso grub menu entry, in case you don't have a VM setup to boot iso attached to the VM.

A fromiso-Gub menu entry looks something like this:
with the snapshot iso "MX-snapshot.iso" copied into an /iso/ directory on an ext4 file system:
adjust boot options as desired:

Code: Select all

# custom.cfg
# save under /boot/grub/custom.cfg
#
menuentry "ISO-Boot MX-snapshot.iso" {
  isopath=/iso/MX-snapshot.iso
  bootoptions="kbd=de kbvar=nodeadkeys kbopt=caps:none lang=de tz=Europe/Amsterdam" 

  insmod ext2
  insmod part_gpt
  insmod part_msdos
  insmod probe
  insmod loopback
  # use this to search for the full isopath
  search --no-floppy --file --set=root $isopath
  probe -u $root --set=buuid
  loopback loop $isopath
  linux  (loop)/antiX/vmlinuz buuid=${buuid} fromiso=${isopath} quiet splasht nosplash ${bootoptions}
  initrd (loop)/antiX/initrd.gz
}

Posted: **Wed Jan 24, 2024 9:57 pm**

dolphin_oracle wrote: Wed Jan 24, 2024 3:40 pm how about your excludes file?

Not sure where to find that file. But when I made the snapshot, I did not exclude anything. I checked no boxes and I did not edit the text file.

Posted: **Thu Jan 25, 2024 11:13 am**

Maybe check the file
/etc/initrd_release
and fix the 2nd VERSION= line
by adding a mssing ["] double quote, if missing,
before making the snapshot.
As mentioned here:
viewtopic.php?p=763190#p763190

Posted: **Sun Jan 28, 2024 2:53 pm**

fehlix wrote: Thu Jan 25, 2024 11:13 am Maybe check the file
/etc/initrd_release
and fix the 2nd VERSION= line
by adding a mssing ["] double quote, if missing,
before making the snapshot.
As mentioned here:
viewtopic.php?p=763190#p763190

Thanks for the follow-up and I am happy to see that the issue was resolved.

Posted: **Sun Jan 28, 2024 2:57 pm**

Then as the starter of "this" thread you (only you) can mark it as solved :)

MX Linux Forum

Kernel panic when booting from live USB

Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB [Solved]

Re: Kernel panic when booting from live USB

Re: Kernel panic when booting from live USB