MX Linux Forum

Posted: **Sun Dec 10, 2023 5:10 pm**

Recently I updated mx linux 23.1 , after I rebooted and logged in with my username, it crashes. So when I waited awhile after I did a cold shut down of my computer and rebooted, I selected a older kerel version 6.1.0.13. So far haven't had issues.

Has anyone else had this problem recently? Does this have to do with the bigger updates in the past 2 days?

Posted: **Sun Dec 10, 2023 5:46 pm**

We need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules

Posted: **Sun Dec 10, 2023 5:50 pm**

j2mcgreg wrote: Sun Dec 10, 2023 5:46 pm We need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules

Code: Select all

System:
  Kernel: 6.1.0-14-amd64 [6.1.64-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-14-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_x64 Libretto July 31  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: Gigabyte model: GA-MA790X-UD4P v: x.x serial: <superuser required>
    BIOS: Award v: F2 date: 03/02/2009
CPU:
  Info: model: AMD Phenom 9950 bits: 64 type: MCP arch: K10 level: v1 built: 2007-08
    process: AMD 65nm family: 0x10 (16) model-id: 2 stepping: 3 microcode: 0x1000083
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 512 KiB desc: d-4x64 KiB; i-4x64 KiB
    L2: 2 MiB desc: 4x512 KiB L3: 2 MiB desc: 1x2 MiB
  Speed (MHz): avg: 1300 min/max: 1300/2600 boost: disabled scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 1300 2: 1300 3: 1300 4: 1300 bogomips: 20802
  Flags: ht lm nx pae sse sse2 sse3 sse4a svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD RV730 XT [Radeon HD 4670] vendor: Micro-Star MSI driver: radeon v: kernel
    alternate: amdgpu arch: TeraScale code: R6xx/RV6xx/RV7xx process: TSMC 55-65nm built: 2005-13
    pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 2 speed: 5 GT/s ports: active: DVI-I-1
    empty: DVI-I-2 bus-ID: 01:00.0 chip-ID: 1002:9490 class-ID: 0300 temp: 33.5 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: radeon
    unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1280x1024 s-dpi: 96 s-size: 338x270mm (13.31x10.63") s-diag: 433mm (17.03")
  Monitor-1: DVI-I-1 mapped: DVI-0 model-id: PTS 0x06a5 serial: <filter> built: 2005
    res: 1280x1024 hz: 60 dpi: 96 gamma: 1.5 size: 337x270mm (13.27x10.63") diag: 432mm (17")
    ratio: 5:4 modes: max: 1280x1024 min: 720x400
  API: OpenGL v: 3.3 Mesa 22.3.6 renderer: AMD RV730 (DRM 2.50.0 / 6.1.0-14-amd64 LLVM 15.0.6)
    compat-v: 3.0 direct-render: Yes
Audio:
  Device-1: AMD SBx00 Azalia vendor: Gigabyte GA-880GMA-USB3 driver: snd_hda_intel v: kernel
    bus-ID: 00:14.2 chip-ID: 1002:4383 class-ID: 0403
  Device-2: AMD RV710/730 HDMI Audio [Radeon HD 4000 series] vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 2
    speed: 5 GT/s bus-ID: 01:00.1 chip-ID: 1002:aa38 class-ID: 0403
  API: ALSA v: k6.1.0-14-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 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: Gigabyte driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: ce00 bus-ID: 03:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Realtek 802.11ac NIC type: USB driver: rtl8821cu bus-ID: 1-1:2 chip-ID: 0bda:c811
    class-ID: 0000 serial: <filter>
  IF: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 233.76 GiB used: 28.06 GiB (12.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD2500YD-01NVB1 size: 233.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 2E01
    scheme: MBR
Partition:
  ID-1: / raw-size: 233.76 GiB size: 229.03 GiB (97.98%) used: 28.06 GiB (12.3%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: radeon temp: 33.5 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2128 pm: dpkg pkgs: 2092 libs: 1058 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 36
  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/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
Info:
  Processes: 225 Uptime: 8m wakeups: 1 Memory: 7.75 GiB used: 1.6 GiB (20.7%) Init: SysVinit
  v: 3.06 runlevel: 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: BIOS (legacy, CSM, MBR)

Posted: **Sun Dec 10, 2023 5:53 pm**

Having problems also.
WiFi cannot connect and system freezes with kernel 6.1.0-15

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_x64 Libretto October 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: Dell product: Latitude E6520 v: 01 serial: <superuser required> Chassis:
    type: 9 serial: <superuser required>
  Mobo: Dell model: 0692FT v: A00 serial: <superuser required> UEFI: Dell v: A22 date: 09/13/2018
Battery:
  ID-1: BAT0 charge: 60.0 Wh (100.0%) condition: 60.0/57.7 Wh (104.0%) volts: 12.3 min: 11.1
    model: SMP DELL P8TC721 type: Li-ion serial: <filter> status: full
  Device-1: hidpp_battery_0 model: Logitech M570 serial: <filter> charge: 75% rechargeable: yes
    status: discharging
CPU:
  Info: model: Intel Core i7-2760QM bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
    built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 964 high: 1090 min/max: 800/3500 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1023 2: 800 3: 928 4: 900 5: 1026 6: 1024 7: 1090 8: 921
    bogomips: 38313
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  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: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GF119M [NVS 4200M] vendor: Dell driver: nouveau v: kernel non-free:
    series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx process: 40/28nm
    built: 2010-16 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports: active: HDMI-A-1,LVDS-1
    empty: DP-1,DP-2,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:1056 class-ID: 0300 temp: 51.0 C
  Device-2: Sunplus Innovation Laptop_Integrated_Webcam_FHD type: USB driver: uvcvideo
    bus-ID: 1-1.5:3 chip-ID: 1bcf:2802 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1848 s-dpi: 96 s-size: 508x489mm (20.00x19.25") s-diag: 705mm (27.76")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary,top-left model: Denon DENON-AVR
    serial: <filter> built: 2015 res: 1920x1080 hz: 60 dpi: 52 gamma: 1.2
    size: 930x520mm (36.61x20.47") diag: 1066mm (41.9") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  Monitor-2: LVDS-1 pos: bottom-r model: Seiko Epson 0x5441 built: 2010 res: 1366x768 hz: 60
    dpi: 101 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes:
    max: 1366x768 min: 640x350
  API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NVD9 direct-render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Dell 6
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
  Device-2: NVIDIA GF119 HDMI Audio vendor: Dell driver: snd_hda_intel v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e08 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 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: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e v: kernel port: 5040
    bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Broadcom BCM4313 802.11bgn Wireless Network Adapter vendor: Dell Inspiron M5010 /
    XPS 8300 driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 14e4:4727 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 1.36 TiB used: 12.21 GiB (0.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Smart Modular Tech. model: SHGS31-1000GS-2 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0Q00
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Smart Modular Tech. model: SHGS31-500GS-2 size: 465.76 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0Q00
    scheme: GPT
Partition:
  ID-1: / raw-size: 80 GiB size: 78.19 GiB (97.74%) used: 11.72 GiB (15.0%) fs: ext4 dev: /dev/sda1
    maj-min: 8:1
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%) used: 107.3 MiB (21.5%) fs: vfat
    dev: /dev/sdb1 maj-min: 8:17
  ID-3: /home raw-size: 377 GiB size: 370.02 GiB (98.15%) used: 387.5 MiB (0.1%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 2 GiB used: 4.2 MiB (0.2%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 58.0 C mobo: 37.0 C sodimm: SODIMM C gpu: nouveau temp: 51.0 C
  Fan Speeds (RPM): cpu: 2673
Repos:
  Packages: 2066 pm: dpkg pkgs: 2061 libs: 1042 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 5
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  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/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 263 Uptime: 28m wakeups: 5 Memory: 3.78 GiB used: 2.11 GiB (55.9%) Init: SysVinit
  v: 3.06 runlevel: 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: **Sun Dec 10, 2023 5:55 pm**

Related to this viewtopic.php?t=78337

Posted: **Sun Dec 10, 2023 5:56 pm**

Folks, start your own topics, do NOT tack on to other people's, even if it is related.

Posted: **Sun Dec 10, 2023 6:01 pm**

Eadwine Rose wrote: Sun Dec 10, 2023 5:55 pm Related to this viewtopic.php?t=78337

What I dont understand is that so far 6.1.0-14 is working for me, but 6.1.0-15 doesnt.

Posted: **Sun Dec 10, 2023 6:03 pm**

login seems to be OK. I'm running the kernel now.

Is that all I have to do, try to log in?

Posted: **Sun Dec 10, 2023 6:05 pm**

dolphin_oracle wrote: Sun Dec 10, 2023 6:03 pm login seems to be OK. I'm running the kernel now.

Is that all I have to do, try to log in?

Makes me thinking next time I reboot my computer is just go into 6.1.0.13 instead. I wonder if its still a risk for me to continue using 6.1.0.14.

Posted: **Sun Dec 10, 2023 6:08 pm**

SimplyFojin wrote: Sun Dec 10, 2023 6:05 pm
dolphin_oracle wrote: Sun Dec 10, 2023 6:03 pm login seems to be OK. I'm running the kernel now.

Is that all I have to do, try to log in?
Makes me thinking next time I reboot my computer is just go into 6.1.0.13 instead. I wonder if its still a risk for me to continue using 6.1.0.14.

the risk was apparently ext4 file system corruption. I don' t know how likely that is.

could you have an incomplete update?

Code: Select all

sudo dpkg --configure -a

Posted: **Sun Dec 10, 2023 6:10 pm**

dolphin_oracle wrote: Sun Dec 10, 2023 6:08 pm
SimplyFojin wrote: Sun Dec 10, 2023 6:05 pm
dolphin_oracle wrote: Sun Dec 10, 2023 6:03 pm login seems to be OK. I'm running the kernel now.

Is that all I have to do, try to log in?
Makes me thinking next time I reboot my computer is just go into 6.1.0.13 instead. I wonder if its still a risk for me to continue using 6.1.0.14.
the risk was apparently ext4 file system corruption. I don' t know how likely that is.

could you have an incomplete update?
Code: Select all
sudo dpkg --configure -a

So what your saying is that I shouldn't even use 6.1.0.13 ever again? Even though it works for me? Again, 6.1.0.15 causes crashing and no internet.

Posted: **Sun Dec 10, 2023 6:13 pm**

you asked about the risk to 6.1.0.14. 6.1.0.13 did not have the ext4 file system problem as far as I know.

Posted: **Sun Dec 10, 2023 6:15 pm**

FWIW, the 6.1.0-13 kernels are still in the debian repo and accessible.

Posted: **Sun Dec 10, 2023 6:20 pm**

dolphin_oracle wrote: Sun Dec 10, 2023 6:15 pm FWIW, the 6.1.0-13 kernels are still in the debian repo and accessible.

What about history in package manager? This is what I spotted today.

Code: Select all

2023-12-10  12:09:36  upgrade  system-keyboard-qt                 amd64  23.12.01mx23                     23.12.02mx23
2023-12-10  12:09:35  upgrade  quick-system-info-gui              amd64  23.09.01                         23.12.01
2023-12-10  12:09:34  upgrade  mx-usb-unmounter                   amd64  23.02                            23.12
2023-12-10  12:09:33  upgrade  mx-tweak                           amd64  23.11.01mx23                     23.12.01mx23
2023-12-10  12:09:32  upgrade  mx-remastercc                      amd64  23.6                             23.7
2023-12-10  12:09:31  upgrade  mx-codecs                          amd64  23.7.02                          23.7.03
2023-12-10  12:09:30  upgrade  linux-libc-dev                     amd64  6.1.64-1                         6.1.66-1
2023-12-10  12:09:29  upgrade  linux-image-amd64                  amd64  6.1.64-1                         6.1.66-1
2023-12-10  12:09:16  install  linux-image-6.1.0-15-amd64         amd64  <none>                           6.1.66-1
2023-12-10  12:09:15  upgrade  linux-headers-amd64                amd64  6.1.64-1                         6.1.66-1
2023-12-10  12:09:12  install  linux-headers-6.1.0-15-amd64       amd64  <none>                           6.1.66-1
2023-12-10  12:09:11  upgrade  linux-kbuild-6.1                   amd64  6.1.64-1                         6.1.66-1
2023-12-10  12:09:06  install  linux-headers-6.1.0-15-common      all    <none>                           6.1.66-1
2023-12-10  12:09:05  upgrade  linux-compiler-gcc-12-x86          amd64  6.1.64-1                         6.1.66-1
2023-12-10  12:09:04  upgrade  formatusb                          amd64  23.11.01                         23.11.03
2023-12-10  12:09:02  upgrade  bash-config                        amd64  23.07.01                         23.07.02
2023-12-10  12:08:21  remove   linux-image-6.1.0-12-amd64         amd64  6.1.52-1                         <none>
2023-12-10  12:08:20  remove   linux-headers-6.1.0-12-amd64       amd64  6.1.52-1                         <none>
2023-12-10  12:08:18  upgrade  base-files                         amd64  12.4+deb12u3

And for yesterday...

Code: Select all

2023-12-09  14:37:23  upgrade  python3-distro-info                all    1.5                              1.5+deb12u1
2023-12-09  14:37:22  upgrade  nvidia-detect                      amd64  525.125.06-1~deb12u1             525.147.05-4~deb12u1
2023-12-09  14:37:21  upgrade  network-manager-openconnect        amd64  1.2.8-3                          1.2.8-3+deb12u1
2023-12-09  14:37:20  upgrade  network-manager-openconnect-gnome  amd64  1.2.8-3                          1.2.8-3+deb12u1
2023-12-09  14:37:19  upgrade  linux-libc-dev                     amd64  6.1.55-1                         6.1.64-1
2023-12-09  14:37:18  upgrade  linux-image-amd64                  amd64  6.1.55-1                         6.1.64-1
2023-12-09  14:37:05  install  linux-image-6.1.0-14-amd64         amd64  <none>                           6.1.64-1
2023-12-09  14:37:04  upgrade  linux-headers-amd64                amd64  6.1.55-1                         6.1.64-1
2023-12-09  14:37:01  install  linux-headers-6.1.0-14-amd64       amd64  <none>                           6.1.64-1
2023-12-09  14:37:00  upgrade  linux-kbuild-6.1                   amd64  6.1.55-1                         6.1.64-1
2023-12-09  14:36:56  install  linux-headers-6.1.0-14-common      all    <none>                           6.1.64-1
2023-12-09  14:36:55  upgrade  linux-compiler-gcc-12-x86          amd64  6.1.55-1                         6.1.64-1
2023-12-09  14:36:54  upgrade  libqpdf29                          amd64  11.3.0-1                         11.3.0-1+deb12u1
2023-12-09  14:36:53  upgrade  libminizip1                        amd64  1.1-8+b1                         1.1-8+deb12u1
2023-12-09  14:36:53  upgrade  libde265-0                         amd64  1.0.11-1                         1.0.11-1+deb12u1
2023-12-09  14:36:51  upgrade  exfatprogs                         amd64  1.2.0-1                          1.2.0-1+deb12u1
2023-12-09  14:36:50  upgrade  distro-info-data                   all    0.58                             0.58+deb12u1
2023-12-09  14:36:49  upgrade  ca-certificates-java               all    20230620~deb12u1                 20230710~deb12u1
2023-12-09  14:36:47  upgrade  tzdata                             all    2023c-5                          2023c-5+deb12u1
2023-12-09  14:36:46  upgrade  libcups2                           amd64  2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:44  upgrade  libgnutls30                        amd64  3.7.9-2                          3.7.9-2+deb12u1
2023-12-09  14:36:43  upgrade  cups                               amd64  2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:42  upgrade  cups-daemon                        amd64  2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:41  upgrade  cups-server-common                 all    2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:40  upgrade  cups-ppdc                          amd64  2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:39  upgrade  cups-core-drivers                  amd64  2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:39  upgrade  cups-client                        amd64  2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:38  upgrade  cups-bsd                           amd64  2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:37  upgrade  cups-common                        all    2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:36  upgrade  cups-ipp-utils                     amd64  2.4.2-3+deb12u4                  2.4.2-3+deb12u5
2023-12-09  14:36:34  upgrade  perl-modules-5.36                  all    5.36.0-7                         5.36.0-7+deb12u1
2023-12-09  14:36:32  upgrade  perl-base                          amd64  5.36.0-7                         5.36.0-7+deb12u1
2023-12-09  14:36:31  upgrade  perl                               amd64  5.36.0-7                         5.36.0-7+deb12u1
2023-12-09  14:36:29  upgrade  libperl5.36                        amd64  5.36.0-7                         5.36.0-7+deb12u1
2023-12-09  14:36:26  upgrade  base-files                         amd64  12.4+deb12u2

Posted: **Sun Dec 10, 2023 6:22 pm**

nothing jumping out at me.

the dpkg --configure -a command, if it didn't' return any output, would indicate the updates are complete at least. that would still leave the question of why the -15 kernel doesn't work correctly,but at least you would know the updates were complete.

Posted: **Sun Dec 10, 2023 6:30 pm**

dolphin_oracle wrote: Sun Dec 10, 2023 6:22 pm nothing jumping out at me.

the dpkg --configure -a command, if it didn't' return any output, would indicate the updates are complete at least. that would still leave the question of why the -15 kernel doesn't work correctly,but at least you would know the updates were complete.

Updates were complete by typing

Code: Select all

sudo dpkg --configure -a

then entering my password? I did try that and their wasn't output. So I think the updating process is completed like you said.

Posted: **Sun Dec 10, 2023 7:02 pm**

@SimplyFojin
I think that your best bet would be to use Boot Options in MX Tools to roll back to the 6.1.0-13 kernel. That's what I did on my Aspire V5 as soon as the kernel problem was identified.

@Lfever
You should use Repo Manager in MX Tools (Individual Sources tab) to enable the AHS repo, log out / in and then run the new updates, Finally, you should use MXPI (MX Package Installer) to install the Liquorix 6.5.11-3 kernel. There are reports elsewhere here in the forums that Dells seem to run better with a Liquorix kernel.
Edited to add that the Liquorix kernels are not affected by this bug.

Posted: **Sun Dec 10, 2023 7:27 pm**

j2mcgreg wrote: Sun Dec 10, 2023 7:02 pm ... I think that your best bet would be to use Boot Options in MX Tools to roll back to the 6.1.0-13 kernel. That's what I did on my Aspire V5 as soon as the kernel problem was identified....

Right, so waiting for the 6.1.0-16 kernel

Posted: **Sun Dec 10, 2023 11:32 pm**

Same problem as others with -15 kernel. Had to go back to -13 kernel

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_x64 Libretto October 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: MSI model: H110M GAMING (MS-7994) v: 1.0 serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 5.80 date: 12/16/2016
CPU:
  Info: model: Intel Pentium G4400 bits: 64 type: MCP arch: Skylake-S level: v2 built: 2015
    process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 800 min/max: 800/3300 scaling: driver: intel_pstate governor: powersave
    cores: 1: 800 2: 800 bogomips: 13199
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: 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: IBRS, IBPB: conditional, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 510 vendor: Micro-Star MSI driver: i915 v: kernel arch: Gen-9
    process: Intel 14n built: 2015-16 ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2,HDMI-A-3
    bus-ID: 00:02.0 chip-ID: 8086:1902 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: DP-1 model: Acer HA220Q serial: <filter> built: 2017 res: 1920x1080 hz: 60 dpi: 102
    gamma: 1.2 size: 476x268mm (18.74x10.55") diag: 546mm (21.5") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 510 (SKL GT1)
    direct-render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 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: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel modules: wl pcie:
    gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:2725 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-3: TP-Link Archer T2U PLUS [RTL8821AU] type: USB driver: rtl8821au bus-ID: 1-10:4
    chip-ID: 2357:0120 class-ID: 0000 serial: <filter>
  IF: wlan1 state: up mac: <filter>
Drives:
  Local Storage: total: 223.57 GiB used: 40.11 GiB (17.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT240BX200SSD1 size: 223.57 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: .6 scheme: GPT
Partition:
  ID-1: / raw-size: 223.57 GiB size: 219 GiB (97.96%) used: 40.11 GiB (18.3%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 26.0 C pch: 35.5 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2675 libs: 1517 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  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-earth-pro.list
    1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/weewx.list
    1: deb [arch=all] http://weewx.com/apt/python3 buster main
Info:
  Processes: 217 Uptime: 13m wakeups: 1 Memory: 11.57 GiB used: 2.54 GiB (21.9%) Init: SysVinit
  v: 3.06 runlevel: 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: BIOS (legacy, CSM, MBR)

Posted: **Mon Dec 11, 2023 2:58 am**

The 6.10.64 (6.10-14) kernel was replaced by 6.10.66 in Debian Bookworm. All those other updates were pushed as part of the 12.2 to 12.3 Bookworm point release. Those point releases happen on a regular schedule ~every two months.

Posted: **Mon Dec 11, 2023 10:04 am**

Typo? 6.10.64 and 6.10.66

Posted: **Mon Dec 11, 2023 3:09 pm**

quite a lot of bug report action on the debian bugtracker about the 6.1.0-15 kernel. apparently a commit was imported from upstream that had already been reverted in elsewhere. the commit dealing with cfg80211, which certainly relates to wifi.

Posted: **Mon Dec 11, 2023 3:16 pm**

Yes, I needed to go back to linux kernel 6.1.0.13. Xfce crashes and everything... I needed to restart with REISUB.

Code: Select all

$ sudo reboot 
E 363.522568] INFO: task kworker/0:0:7 blocked for more than 241 seconds. I 363.524055] Tainted: G DE 6.1.0-15-amd64 #1 Debian 6.1.66-1 E 363.525542] "echo 0 > fprocisgsikernelihung_task_timeout_secs" disables this message. I 363.527341] INFO: task kworker/3:2:252 blocked for more than 128 seconds. I 363.528936] Tainted: G OE 6.1.0-15-amd64 *1 Debian 6.1.66-1 363.530508] "echo 0 > iprocisgsikernelibung_task_timeout_secs" disables this message. [ 363.5322427 INFO: task cgmanager:1725 blocked for more than 120 seconds. I 363.533823] Tainted: G OE 6.1.0-15-amd64 #1 Debian 6.1.55-1 363.535418] "echo 0 > iprocisysikernelihung_task_timeout_secs" disables this message. I 363.537157] INFO: task cups-browsed:2064 blocked for more than 241 seconds. [ 363.538759] Tainted: G OE 6.1.0-15-amd64 #1 Debian 6.1.66-1 E. 363.540266] "echo 0 > iproasysikernel/hung.task.timeout_secs" disables this message. 
,,,,,,,,PCP,m4A.P.T.11VM0041,404"010VA

Posted: **Mon Dec 11, 2023 4:09 pm**

dolphin_oracle wrote: Mon Dec 11, 2023 3:09 pm quite a lot of bug report action on the debian bugtracker about the 6.1.0-15 kernel. apparently a commit was imported from upstream that had already been reverted in elsewhere. the commit dealing with cfg80211, which certainly relates to wifi.

FYI, I recently got a new update from MX Updater and it removed 6.1.0.-14 kernel. With future updates is it possible for the MX linux team to make it so 6.1.0.-13 and 6.1.0.-0 kernels ARE NOT removed? Given the whole 6.1.0.-15 problem?

Posted: **Mon Dec 11, 2023 4:37 pm**

SimplyFojin wrote: Mon Dec 11, 2023 4:09 pm
dolphin_oracle wrote: Mon Dec 11, 2023 3:09 pm quite a lot of bug report action on the debian bugtracker about the 6.1.0-15 kernel. apparently a commit was imported from upstream that had already been reverted in elsewhere. the commit dealing with cfg80211, which certainly relates to wifi.
FYI, I recently got a new update from MX Updater and it removed 6.1.0.-14 kernel. With future updates is it possible for the MX linux team to make it so 6.1.0.-13 and 6.1.0.-0 kernels ARE NOT removed? Given the whole 6.1.0.-15 problem?

sure just remove the linux-image-amd64 and linux-headers-amd64 packages and there will be no automatic updates.

Posted: **Mon Dec 11, 2023 4:51 pm**

dolphin_oracle wrote: Mon Dec 11, 2023 4:37 pm
SimplyFojin wrote: Mon Dec 11, 2023 4:09 pm
dolphin_oracle wrote: Mon Dec 11, 2023 3:09 pm quite a lot of bug report action on the debian bugtracker about the 6.1.0-15 kernel. apparently a commit was imported from upstream that had already been reverted in elsewhere. the commit dealing with cfg80211, which certainly relates to wifi.
FYI, I recently got a new update from MX Updater and it removed 6.1.0.-14 kernel. With future updates is it possible for the MX linux team to make it so 6.1.0.-13 and 6.1.0.-0 kernels ARE NOT removed? Given the whole 6.1.0.-15 problem?
sure just remove the linux-image-amd64 and linux-headers-amd64 packages and there will be no automatic updates.

Wouldn't that cause issues like dependency hell? I don't understand how that would work.

Posted: **Mon Dec 11, 2023 4:54 pm**

Nope. They are just meta packages. They bring in the new kernels when they’re available.

Posted: **Mon Dec 11, 2023 5:02 pm**

dolphin_oracle wrote: Mon Dec 11, 2023 4:54 pm Nope. They are just meta packages. They bring in the new kernels when they’re available.

I see. However I don't understand how to properly remove them and whenever this issue is solved download them again.

Posted: **Mon Dec 11, 2023 5:04 pm**

They are just packages. You can use any package manager.

Posted: **Mon Dec 11, 2023 5:19 pm**

dolphin_oracle wrote: Mon Dec 11, 2023 5:04 pm They are just packages. You can use any package manager.

I think what I'm trying to convey, isn't there a terminal command to remove both packages safely?

Posted: **Mon Dec 11, 2023 5:21 pm**

Code: Select all

sudo apt purge linux-image-amd64 linux-headers-amd64 -y

Code: Select all

sudo apt update ; sudo apt install linux-image-amd64 linux-headers-amd64 -y

Posted: **Mon Dec 11, 2023 7:00 pm**

SimplyFojin wrote: Mon Dec 11, 2023 5:19 pm
dolphin_oracle wrote: Mon Dec 11, 2023 5:04 pm They are just packages. You can use any package manager.
I think what I'm trying to convey, isn't there a terminal command to remove both packages safely?

sudo apt remove linux-image-amd64 linux-headers-amd64

Posted: **Tue Dec 12, 2023 9:34 am**

In the meantime, my second command was for this one:

SimplyFojin wrote: Mon Dec 11, 2023 5:02 pm...and whenever this issue is solved download them again.

:)

(Not to apply them successively)

Posted: **Tue Dec 12, 2023 6:01 pm**

dolphin_oracle wrote: Mon Dec 11, 2023 7:00 pm
SimplyFojin wrote: Mon Dec 11, 2023 5:19 pm
dolphin_oracle wrote: Mon Dec 11, 2023 5:04 pm They are just packages. You can use any package manager.
I think what I'm trying to convey, isn't there a terminal command to remove both packages safely?
sudo apt remove linux-image-amd64 linux-headers-amd64

How is that different from Charlie Browns method? I want to make sure which way is effective for not screwing up my computer.

Posted: **Tue Dec 12, 2023 7:37 pm**

Stevo wrote: Mon Dec 11, 2023 2:58 am The 6.1.64 (6.1.0-14) kernel was replaced by 6.1.66 in Debian Bookworm. All those other updates were pushed as part of the 12.2 to 12.3 Bookworm point release. Those point releases happen on a regular schedule ~every two months.

Right, ext issue "iomap: update ki_pos a little later in iomap_dio_complete " was fixed with 6.1.66 = (deb 6.1.0-15) (also for k6.6.5) ... and the wifi issue "Revert "wifi: cfg80211: fix CQM for non-range use" was fixed with 6.1.67 (deb 6.1.0-16) (also for k 6.6.6) ... so that should be OK now (not only Debian kernels was affected, but a lot of distribs) . So should be OK now with 6.1.67 (deb 6.1.0-16) (also with k6.6.6).

Posted: **Tue Dec 12, 2023 7:52 pm**

doublon

Posted: **Tue Dec 12, 2023 9:13 pm**

SimplyFojin wrote: Tue Dec 12, 2023 6:01 pm
dolphin_oracle wrote: Mon Dec 11, 2023 7:00 pm
SimplyFojin wrote: Mon Dec 11, 2023 5:19 pm

I think what I'm trying to convey, isn't there a terminal command to remove both packages safely?
sudo apt remove linux-image-amd64 linux-headers-amd64
How is that different from Charlie Browns method? I want to make sure which way is effective for not screwing up my computer.

man apt wrote:Removing a package removes all packaged data, but leaves usually small (modified) user
configuration files behind, in case the remove was an accident. Just issuing an
installation request for the accidentally removed package will restore its function as
before in that case. On the other hand you can get rid of these leftovers by calling
purge even on already removed packages. Note that this does not affect any data or
configuration stored in your home directory.

man apt-get wrote: remove
remove is identical to install except that packages are removed instead of installed.
Note that removing a package leaves its configuration files on the system...

purge
purge is identical to remove except that packages are removed and purged (any
configuration files are deleted too).

Remove is softer, you can use that one.

Posted: **Wed Dec 13, 2023 2:04 am**

linux-image-amd64 and linux-headers-amd64 are the amd64 stock kernel and header metapackages, not the actual kernel and headers. They are built at the same time as the latest kernel, and will depend on that same version, which, as of now, is 6.1.0-16 for Bookworm, (6.1.67 kernel source). When a new stock kernel becomes available in the repos, a new set of metapackages in the repos will become an upgrade, which in turn pulls the new matching kernel and headers. Removing the metapackages stops the upgrades without removing the actual kernel and headers, which can become a terrible, horrible, no good, very bad thing.

Posted: **Wed Dec 13, 2023 8:12 am**

@Stevo Thank you for the best explanation I've read so far. Bookmarked your post for future reference :)

(Btw. then we can also say "nothing to be afraid of purging" , in this case).

Posted: **Wed Dec 13, 2023 3:31 pm**

If 6.1.0.15 is the problem child, and I'm on 6.1.0.13 (bog standard MX-23 xfce4 up-to-date) why is the updater still offering to upgrade to:

Code: Select all

linux-image-6.1.0-15-amd64 (6.1.66-1)

even when the repo is set to the Salt Lake City location? Shouldn't it be blacklisted?

Posted: **Wed Dec 13, 2023 3:37 pm**

figueroa wrote: Wed Dec 13, 2023 3:31 pm If 6.1.0.15 is the problem child, and I'm on 6.1.0.13 (bog standard MX-23 xfce4 up-to-date) whey is the updater still offering to upgrade to:
Code: Select all
linux-image-6.1.0-15-amd64 (6.1.66-1)
even when the repo is set to the Salt Lake City location? Shouldn't it be blacklisted?

comes from debian, not MX. We would have removed the offending kernel (and in fact have removed ones that had the issue that we did supply) but debian has chosen to leave it up. which is dumb, but not our servers.

you can remove the linux-image-amd64 and linux-headers-amd64 packages and the update will not be offered. I will be posting when the next kernel is ready, which should be pretty soon.

Posted: **Wed Dec 13, 2023 4:17 pm**

Thank's @dolphin_oracle. What I chose to do in the short term was to do a basic upgrade (not full-upgrade) through the command-line, since there were many other package upgrades to make. Just doing "apt-get upgrade" held back the kernel and header. I'll watch carefully and avoid updating kernel and header till Debian to stabilize the next version.

Posted: **Thu Dec 14, 2023 12:40 am**

Stevo wrote: Wed Dec 13, 2023 2:04 am Removing the metapackages stops the upgrades without removing the actual kernel and headers, which can become a terrible, horrible, no good, very bad thing.

So I shouldn't do anything? I'm concerned when theirs a new kernel update that 6.1.0.13 and 6.1.0.10 will be deleted.

Posted: **Thu Dec 14, 2023 1:05 am**

SimplyFojin wrote: Thu Dec 14, 2023 12:40 am
Stevo wrote: Wed Dec 13, 2023 2:04 am Removing the metapackages stops the upgrades without removing the actual kernel and headers, which can become a terrible, horrible, no good, very bad thing.
So I shouldn't do anything? I'm concerned when theirs a new kernel update that 6.1.0.13 and 6.1.0.10 will be deleted.

Depending on what version(s) you have purged, you *should ReInstall* the metapackages in any scenario, to get the next releases offered by 'apt update' or MXPI, IMO.

See this last (asof: 2023/12/14 - 07:00) posting on the bugtracker: https://bugs.debian.org/cgi-bin/bugrepo ... 1057843#98

Finally, I wanted to note: if you did `apt purge linux-image-6.1.0-14-amd64`, you might need to `apt install linux-image-amd64` (the meta package) before you can successfully pick up the new linux-image-6.1.0-15-amd64 automatically as a dependency (say, when doing apt update; apt dist-upgrade). At least, I needed to, as I think the purge automatically removed the meta package, leaving me with no *automatic* upgrade to the new kernel via those commands.

Good luck!

Also - in this posting, he gives some hints on howto check for possible files data corruption

Posted: **Thu Dec 14, 2023 12:19 pm**

SimplyFojin wrote: Thu Dec 14, 2023 12:40 am So I shouldn't do anything? I'm concerned when theirs a new kernel update that 6.1.0.13 and 6.1.0.10 will be deleted.

For this very reason you need to remove /purge that. Cause it will keep last two and install the new one (totally 3 kernels). At least till you feel/see/learn it's ok with the new released (Debian, default) kernel (whatever it is ...-17 , ...-18 etc..).. then you can simply install back the metapackages (as above or with MXPI) and let it install that new kernel etc. and go on auto-installation/removal as before ...

In case you want particularly (and to always) keep the -10 and/or -13 (for whatever reason), then you need to "apt-mark hold" them.

Posted: **Thu Dec 14, 2023 12:48 pm**

Same - doesn't connect to wifi and crashes soon after. Using 6.1.0-13 works just fine though. Also it hangs on shutdown when trying to stop the network processes. Should I make a separate topic? They seem exactly alike.

Posted: **Thu Dec 14, 2023 12:52 pm**

Just make the -13 default with "MX Boot Options" - "Boot to", at least till the "proven to be non-buggy" release is announced (whatever: -16 or -17 ...), then you can happily remove the -14 and -15 ..

(Or just remove them now (MX Cleanup is simple to use for this) and also the metapackages to prevent their reinstallation as an update)

Posted: **Thu Dec 14, 2023 12:56 pm**

Let's just hope Debian gets out kernel 6.1.67 = 6.1.0-16 soon and also let's hope it doesn't introduce another nasty problem. Debian had enough going wrong in the last few days....

6.1.0-15 runs fine on my machine, but that is probably only because I don't use any wifi hardware. I had 6.1.0-14 running for one day, but since the file system corruption actually happens only with very special programs (i.e. usually database software), my system (and most desktop systems) shouldn't be affected.

For now, staying on 6.1.0-13 is surely the safest option.

Posted: **Thu Dec 14, 2023 1:02 pm**

Thanks! Done! I wish I had checked the forums (on another computer) - or thought to use Kernel -13 a while ago. I have been trying to troubleshoot this for hours and installed the old wifi driver to no success.

The weird thing is that things were working with my old TP-link TN-WN822N, and stopped working I think when I tried to install the old driver for my main wifi adapter and tried to switch to it. Then it just kept failing to accept my wifi password and would eventually freeze.

Ah well I guess probably not too important but maybe it is somehow useful - especially that using that was working - and it wasn't crashing!

EDIT - do you think that the fact that I had to manually power off my computer by holding the power button so many times could have damaged anything? Are there any commands or anything I can do to help restore the filesystem if any thing was damaged?

Posted: **Fri Dec 15, 2023 11:02 am**

Kernel 6.1.67 = 6.1.0-16 is now offered in the MX-Package Installer.

Posted: **Fri Dec 15, 2023 11:06 am**

Yup, I'm running the update just right now

I will definitely make sure to keep -13 around as well, just in case...

Posted: **Fri Dec 15, 2023 11:16 am**

@MadMax I do that as well.

Posted: **Fri Dec 15, 2023 12:47 pm**

PlatinumArts wrote: Thu Dec 14, 2023 1:02 pm... any commands or anything I can do to help restore the filesystem if any thing was damaged?

fsck

You can also do this: If you're able to boot to a live session: GParted , right-click on partition(s) : "Check".

Posted: **Fri Dec 15, 2023 1:04 pm**

Charlie Brown wrote: Fri Dec 15, 2023 12:47 pm
PlatinumArts wrote: Thu Dec 14, 2023 1:02 pm... any commands or anything I can do to help restore the filesystem if any thing was damaged?
fsck

You can also do this: If you're able to boot to a live session: GParted , right-click on partition(s) : "Check".

Due too the special nature and the potential damage sparked by the ext4-bug

, a classic 'fsck' will report nothing serious (/impe/), have a look at this post on the bugtracker

https://bugs.debian.org/cgi-bin/bugrepo ... 1057843#98

:
Then I used `last` to identify the time between the problematic reboot into 6.1.0-14 and the deliberate reboot (back in to 6.1.0-13)

This showed me that the 'problem time' was between 2023-12-10 06:00:00 and 2023-12-10 19:00:00 (UTC).

From there, I ran the followin gcommand to show me all files that were modified more or less between that time. I ignore a bunch of things I don't care about such as /var/log and other volatile parts of the filesystem.

find / -type f -newermt "2023-12-10 05:59:00" \! -newermt "2023-12-10 19:00:00" | egrep -v "/proc|/run|/sys|/var/log"

At least this gave me a somewhat small subset of files to manually check, which made it feel less daunting. Naturally it depends on your filesystem what files might've changed.

I was fortunate that none of the client applications I use, seem to use O_DIRECT, so I found no corrupted files (so far).
:

lodr3 (on whos two affected boxes, that have been ~18h on the way with the problematic 6.1.64 and 6.1.65 kernels

): no data corruption detected

(thus far ...)

edit (sorry):

still

w#all that versioning (esp.: bcof of contemporaneous :zfs-bug: )

Posted: **Fri Dec 15, 2023 1:19 pm**

fsck won't hurt (I actually did it on all my disks after booting into 6.1.0-15 before I knew further details about the bug), but it will not detect errors created by the faulty kernels. These errors are all within file data, not metadata and since ext4 has no built-in checksums, there is really no way to find the errors. The only way to go about it is to isolate files that have been changed while the kernel was active and manually check them.

On the bright side, the error would only happen if the writing program used O_DIRECT which is really, really uncommon for desktop applications. O_DIRECT means the program tells the kernel to bybass all kernel caching and write directly to the disk. That means that program has to take care of caching itself which really is only beneficial for specialized applications like databases (MySQL, MariaDB etc). Regular desktop applications will almost always use kernel caching with something like fsync. Same goes for system tools like apt, so I'm not really worried that installing the 12.4 update including 6.1.0-15 while running 6.1.0-14 could have damaged anything in the root filesystem.

One way to examine further whether you might have affected files is to check the programs you use via strace and search in their actual syscall for O_DIRECT (also don't panic if you grep for it, there is a syscall named O_DIRECTORY which has nothing to do with the former one).

Posted: **Fri Dec 15, 2023 1:27 pm**

If you do the fsck / e2fsck / GParted on live session with an official iso (as suggested above):

The kernel is 6.1.0.10 (on MX-23) and 6.1.0.13 (on MX-23.1) or other non-buggy ones with previous releases.

Posted: **Fri Dec 15, 2023 1:29 pm**

MadMax wrote: Fri Dec 15, 2023 1:19 pm fsck won't hurt (I actually did it on all my disks after booting into 6.1.0-15 before I knew further details about the bug), but it will not detect errors created by the faulty kernels. These errors are all within file data, not metadata and since ext4 has no built-in checksums, there is really no way to find the errors. The only way to go about it is to isolate files that have been changed while the kernel was active and manually check them.

On the bright side, the error would only happen if the writing program used O_DIRECT which is really, really uncommon for desktop applications. O_DIRECT means the program tells the kernel to bybass all kernel caching and write directly to the disk. That means that program has to take care of caching itself which really is only beneficial for specialized applications like databases (MySQL, MariaDB etc). Regular desktop applications will almost always use kernel caching with something like fsync. Same goes for system tools like apt, so I'm not really worried that installing the 12.4 update including 6.1.0-15 while running 6.1.0-14 could have damaged anything in the root filesystem.

One way to examine further whether you might have affected files is to check the programs you use via strace and search in their actual syscall for O_DIRECT (also don't panic if you grep for it, there is a syscall named O_DIRECTORY which has nothing to do with the former one).

thx for this detailed explanation!

My greatest concern about direct-i/o and O_DIRECT was 'rsync', bcof i used heavily timeshift-snapshots, taken during the period, the faulty kernels were running, to solve my ZFS issues, but - fortunately - 'rsync' does not use O_DIRECT, as far as i have g00gled! OR?

Posted: **Fri Dec 15, 2023 6:29 pm**

Charlie Brown wrote: Fri Dec 15, 2023 1:27 pm If you do the fsck / e2fsck / GParted on live session with an official iso (as suggested above):

The kernel is 6.1.0.10 (on MX-23) and 6.1.0.13 (on MX-23.1) or other non-buggy ones with previous releases.

Luckily after I updated today, 6.1.0-13 and -10 are still there. Even though 6.1.0-16 works, 6.1.0-15 still shows up. And thats very problematic given that kernel version crashes my computer.

Posted: **Fri Dec 15, 2023 7:50 pm**

When booted with -10 or -13 or -16 you can remove the -14 and -15 simply with 2 clicks with "MX Cleanup" - 'Kernel Removal Tool' below the window :)

Posted: **Wed Dec 20, 2023 11:34 am**

Charlie Brown wrote: Fri Dec 15, 2023 7:50 pm When booted with -10 or -13 or -16 you can remove the -14 and -15 simply with 2 clicks with "MX Cleanup" - 'Kernel Removal Tool' below the window :)

16 is working perfectly and MX cleanup removed 15 easily, thank you so much for the tip and for all of your help!
- Mike

Posted: **Wed Dec 20, 2023 1:24 pm**

PlatinumArts wrote: Wed Dec 20, 2023 11:34 am... thank you so much for the tip and for all of your help!..

My pleasure :)

Posted: **Tue Mar 26, 2024 5:45 pm**

I experienced some kind of, either system or desktop, corruption with both Plasma and Xfce editions ... both 64 bit.
The corruptions happened after doing a system update.

When booting up I did not get the usual screen display ... a keyboard was shown ... alt+tab shows a login screen, but had to use the keyboard to type in a password ... and nothing happened.

Dell Inspiron 15 5567 PC Laptop, 16 gb system memory, samsung 512 ssd.

No joy!
I gave up!

Posted: **Tue Mar 26, 2024 11:21 pm**

Please do not tack onto an already solved thread. That kernel has already gone through several updates since then by Debian.

Also, forum rules ask for a QSI with every post about this kind of issue. One thing among many is that it tells us exactly what kernel you have now.

MX Linux Forum

linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

Re: linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?