Bug#1052489: iproute2: broken formatting in manual pages due to hermetic-/usr changes

2023-09-22 Thread Paul Wise
Package: iproute2
Version: 6.5.0-4
Severity: minor
Usertags: formatting

The hermetic-/usr changes to the manual pages documenting the new
locations in /usr of the files previously in /etc and overridable
by user files in /etc broke the formatting in the manual pages.

The /usr paths have "or" appended to them instead of as a separate
word and the /etc paths have "(hasprecedenceifexists)" appended to
them instead of with spaces as a separate phrase.

Note that not all mentions of /usr and /etc paths have this issue.

There may be other formatting issues I haven't noticed yet.

   $ for f in $(dpkg -L iproute2 | grep 'man.*\.gz' ) ; do if output=$(man $f 
2> /dev/null | grep "hasprecedenceifexists") ; then echo "$f" ; echo "$output" 
; fi ; done
   /usr/share/man/man8/ip-address.8.gz
 the  scope of the area where this address is valid.  The 
available scopes are listed in /usr/lib/iproute2/rt_scopesor 
/etc/iproute2/rt_scopes(hasprecedenceifexists).  Pre‐
   /usr/share/man/man8/ip-link.8.gz
 specify the group the device belongs to.  The available groups 
are listed in /usr/lib/iproute2/groupor 
/etc/iproute2/group(hasprecedenceifexists).
   /usr/share/man/man8/ip-route.8.gz
/usr/lib/iproute2/rt_dsfieldor 
/etc/iproute2/rt_dsfield(hasprecedenceifexists).
the table to add this route to.  TABLEID may be a 
number or a string from /usr/lib/iproute2/rt_tablesor 
/etc/iproute2/rt_tables(hasprecedenceifexists).  If this pa‐
the realm to which this route is assigned.  REALMID may 
be a number or a string from /usr/lib/iproute2/rt_realmsor 
/etc/iproute2/rt_realms(hasprecedenceifexists).
/etc/iproute2/rt_scopes(hasprecedenceifexists).   If 
this parameter is omitted, ip assumes scope global for all gatewayed unicast 
routes, scope link for direct uni‐
the routing protocol identifier of this route.  RTPROTO 
may be a number or a string from  /etc/iproute2/rt_protosor  
/etc/iproute2/rt_protos(hasprecedenceifexists).
number  or  a string from 
/usr/lib/iproute2/rt_tablesor /etc/iproute2/rt_tables(hasprecedenceifexists).  
If vrftable is used, the argument must be a VRF
string  from  /usr/lib/iproute2/rt_tablesor 
/etc/iproute2/rt_tables(hasprecedenceifexists).  The argument must be a VRF 
device associated with the table
ber or a string from 
/usr/lib/iproute2/rt_tablesor /etc/iproute2/rt_tables(hasprecedenceifexists).  
The argument must be a VRF  device  associated  with

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iproute2 depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libbpf11:1.2.2-2
ii  libbsd00.11.7-4
ii  libc6  2.37-10
ii  libcap21:2.66-4
ii  libcap2-bin1:2.66-4
ii  libdb5.3   5.3.28+dfsg2-2
ii  libelf10.189-4
ii  libmnl01.0.4-3
ii  libselinux13.5-1
ii  libtirpc3  1.3.3+ds-1
ii  libxtables12   1.8.9-2

Versions of packages iproute2 recommends:
pn  libatm1  

Versions of packages iproute2 suggests:
pn  iproute2-doc  
ii  python3   3.11.4-5+b1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Bug#970557: Closing this bug (BTS maintenance for src:linux bugs)

2023-09-22 Thread Vincent Lefevre
Hi,

On 2023-09-22 17:10:37 +0200, car...@debian.org wrote:
> This bug was filed for a very old kernel or the bug is old itself
> without resolution.
> 
> If you can reproduce it with
> 
> - the current version in unstable/testing
> - the latest kernel from backports
[...]

Just a note to say that the machine on which I got this crash
no longer exists.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1051449: linux-image-rt-amd64: Enable "Advantech Embedded Controller Watchdog" support

2023-09-22 Thread Yoann Congal
On Fri, 08 Sep 2023 10:03:23 +0200 Yoann Congal  wrote:> 
Sadly, the driver's KConfig has a dependency bug were it can be compiled
> into a non-operational state. We upstreamed the fix (6eb28a38f6478) [2]
> and it will be released in v6.6. This fix will have to be backported.

FYI, said fix is now in upstream kernel v6.5.4.

Sid kernel now only lacks CONFIG_ADVANTECH_EC_WDT.
I've updated https://salsa.debian.org/kernel-team/linux/-/merge_requests/841



Bug#1004070: linux-image-4.19.0-18-amd64: kernel crashes when accessing files via nfs

2023-09-22 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo unreproducible

Hi,

On Mon, Jan 23, 2023 at 12:55:18PM +0100, Friedrich Beckmann wrote:
> Hi Salvatore,
> 
> thanks for asking! If I remember correctly later kernels did not
> work at the time when I tested this. But have not tried more recent
> 4.19.x kernel. At the moment I do not have that much time but I will
> share the results here once I test that.

Were you able to test current kernel in buster or even newer from a
regular Debian supported release? 

Regards,
Salvatore



Processed: Re: Bug#1004070: linux-image-4.19.0-18-amd64: kernel crashes when accessing files via nfs

2023-09-22 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo unreproducible
Bug #1004070 [src:linux] linux-image-4.19.0-18-amd64: kernel crashes when 
accessing files via nfs
Added tag(s) unreproducible.

-- 
1004070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: bug 1052063 is forwarded to https://lore.kernel.org/regressions/5dhv0s.d0f751zf65...@gmail.com/

2023-09-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1052063 
> https://lore.kernel.org/regressions/5dhv0s.d0f751zf65...@gmail.com/
Bug #1052063 [src:linux] regression: nvme drive not found after kernel upgrade 
from bookworm-security
Set Bug forwarded-to-address to 
'https://lore.kernel.org/regressions/5dhv0s.d0f751zf65...@gmail.com/'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#970557: marked as done (linux-image-5.8.0-1-amd64: kernel crash in nouveau)

2023-09-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Sep 2023 17:10:37 +0200 (CEST)
with message-id <20230922151037.983c8be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #970557,
regarding linux-image-5.8.0-1-amd64: kernel crash in nouveau
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
970557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.8.7-1
Severity: important

A short time after updating the kernel and rebooted, the kernel
crashed in nouveau while I wasn't using the machine (I only had
an ssh session).

Sep 18 17:56:26 ypig kernel: [ 1445.181686] [ cut here ]
Sep 18 17:56:26 ypig kernel: [ 1445.181755] WARNING: CPU: 1 PID: 0 at 
drivers/gpu/drm/nouveau/nvkm/subdev/mc/base.c:72 nvkm_mc_intr+0x14d/0x170 
[nouveau]
Sep 18 17:56:26 ypig kernel: [ 1445.181756] Modules linked in: bnep bluetooth 
jitterentropy_rng drbg aes_generic crypto_simd cryptd glue_helper ansi_cprng 
ecdh_generic ecc libaes cpufreq_powersave cpufreq_conservative 
cpufreq_userspace binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd grace fscache 
sunrpc smsc47b397 loop firewire_sbp2 nft_counter ip6_tables nft_compat 
nf_tables x_tables nfnetlink snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio snd_hda_intel nouveau intel_powerclamp coretemp mxm_wmi 
snd_intel_dspcfg video snd_hda_codec kvm_intel ttm kvm snd_hda_core 
drm_kms_helper irqbypass cec hp_wmi snd_hwdep sparse_keymap snd_pcm rfkill drm 
intel_cstate evdev snd_timer intel_uncore i2c_algo_bit snd serio_raw button 
iTCO_wdt intel_pmc_bxt wmi_bmof soundcore sg iTCO_vendor_support watchdog 
i7core_edac acpi_cpufreq ext4 crc16 mbcache jbd2 crc32c_generic hid_generic 
usbhid hid sd_mod t10_pi crc_t10dif crct10dif_generic sr_mod cdrom 
crct10dif_common ahci mptsas libahci mptscsih mptbase libata scsi_transport_sas
Sep 18 17:56:26 ypig kernel: [ 1445.181790]  firewire_ohci scsi_mod 
firewire_core psmouse ehci_pci uhci_hcd crc_itu_t crc32c_intel ehci_hcd tg3 
usbcore lpc_ich libphy ptp pps_core usb_common wmi floppy
Sep 18 17:56:26 ypig kernel: [ 1445.181800] CPU: 1 PID: 0 Comm: swapper/1 
Tainted: G  I   5.8.0-1-amd64 #1 Debian 5.8.7-1
Sep 18 17:56:26 ypig kernel: [ 1445.181801] Hardware name: Hewlett-Packard HP 
Z800 Workstation/0AECh, BIOS 786G5 v01.17 08/19/2009
Sep 18 17:56:26 ypig kernel: [ 1445.181842] RIP: 0010:nvkm_mc_intr+0x14d/0x170 
[nouveau]
Sep 18 17:56:26 ypig kernel: [ 1445.181844] Code: 44 24 18 65 48 2b 04 25 28 00 
00 00 75 2b 48 83 c4 20 5b 5d 41 5c 41 5d 41 5e 41 5f c3 41 8b 47 40 85 c0 74 
ba e9 34 97 0a 00 <0f> 0b 45 31 e4 c6 44 24 0f 00 e9 00 ff ff ff e8 bf bf 77 f2 
66 66
Sep 18 17:56:26 ypig kernel: [ 1445.181845] RSP: 0018:be65c3250ee8 EFLAGS: 
00010046
Sep 18 17:56:26 ypig kernel: [ 1445.181846] RAX:  RBX: 
95ed5fcefd00 RCX: 0018
Sep 18 17:56:26 ypig kernel: [ 1445.181847] RDX: 00ff RSI: 
be65c3250f47 RDI: be65d1000100
Sep 18 17:56:26 ypig kernel: [ 1445.181848] RBP: 95eb45d89c00 R08: 
be65c3250ff8 R09: 
Sep 18 17:56:26 ypig kernel: [ 1445.181849] R10:  R11: 
 R12: 
Sep 18 17:56:26 ypig kernel: [ 1445.181850] R13:  R14: 
be65c3250fac R15: 95f00f84b4e0
Sep 18 17:56:26 ypig kernel: [ 1445.181851] FS:  () 
GS:95ed63c4() knlGS:
Sep 18 17:56:26 ypig kernel: [ 1445.181852] CS:  0010 DS:  ES:  CR0: 
80050033
Sep 18 17:56:26 ypig kernel: [ 1445.181853] CR2: 7fa6714218b0 CR3: 
96a0a000 CR4: 06e0
Sep 18 17:56:26 ypig kernel: [ 1445.181854] Call Trace:
Sep 18 17:56:26 ypig kernel: [ 1445.181858]  
Sep 18 17:56:26 ypig kernel: [ 1445.181902]  nvkm_pci_intr+0x4d/0x90 [nouveau]
Sep 18 17:56:26 ypig kernel: [ 1445.181908]  
__handle_irq_event_percpu+0x48/0x190
Sep 18 17:56:26 ypig kernel: [ 1445.181910]  handle_irq_event+0x5d/0xbb
Sep 18 17:56:26 ypig kernel: [ 1445.181912]  handle_edge_irq+0x9c/0x280
Sep 18 17:56:26 ypig kernel: [ 1445.181916]  asm_call_on_stack+0x12/0x20
Sep 18 17:56:26 ypig kernel: [ 1445.181917]  
Sep 18 17:56:26 ypig kernel: [ 1445.181919]  common_interrupt+0xb5/0x150
Sep 18 17:56:26 ypig kernel: [ 1445.181921]  asm_common_interrupt+0x1e/0x40
Sep 18 17:56:26 ypig kernel: [ 1445.181925] RIP: 
0010:cpuidle_enter_state+0xb3/0x3f0
Sep 18 17:56:26 ypig kernel: [ 1445.181927] Code: 65 8b 3d 90 87 fb 4c e8 8b 32 
a6 ff 49 89 

Bug#971696: marked as done (linux-image-4.19.0-11-armmp: network hangs, oops in ath9k_htc after upgrade)

2023-09-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Sep 2023 17:08:47 +0200 (CEST)
with message-id <20230922150847.259d8be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #971696,
regarding linux-image-4.19.0-11-armmp: network hangs, oops in ath9k_htc after 
upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
971696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.146-1
Severity: important

Dear Maintainer,

since the last kernel update (from linux-image-armmp:armhf
4.19+105+deb10u5 / linux-image-4.19.0-10-armmp 4.19.132-1 to
linux-image-armmp 4.19+105+deb10u6 / linux-image-4.19.0-11-armmp
4.19.146-1) our BeagleBone Black systems with AR9271 based WLAN adapter
(ath9k_htc driver) print a kernel warning or oops during boot and all
network related system calls hang, breaking not just WLAN but also
ethernet:

=== Begin ===
root@mavis:~# ip addr
[no output, just hanging]
=== End ===

Kernel oops (from one boot):

=== Begin ===
[  OK  ] Started Network Manager Script Dispatcher Service.
[   40.785065] IPv6: ADDRCONF(NETDEV_UP): wlx6cfdb9aac04b: link is not ready
[   41.258639] [ cut here ]
[   41.263512] kernel BUG at mm/slub.c:294!
[   41.267603] Internal error: Oops - BUG: 0 [#1] SMP ARM
[   41.272962] Modules linked in: cmac bnep arc4 btusb btrtl btbcm btintel 
bluetooth drbg ansi_cprng evdev ath9k_htc ath9k_common ath9k_hw ath 
ecdh_generic mac80211 hid_generic cfg80211 usbhid snd_usb_audio snd_usbmidi_lib 
rfkill snd_hwdep hid snd_rawmidi snd_seq_device nls_ascii nls_cp437 vfat fat 
snd_soc_simple_card snd_soc_spdif_rx snd_soc_simple_card_utils omap_rng 
rng_core snd_soc_davinci_mcasp snd_soc_edma snd_soc_sdma snd_soc_core 
snd_pcm_dmaengine snd_pcm snd_timer cppi41 snd at24 soundcore omap_wdt 
leds_gpio ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic 
fscrypto ecb smsc musb_dsps musb_hdrc udc_core davinci_mdio usbcore phy_am335x 
phy_generic phy_am335x_control ti_cpsw cpsw_ale cpsw_common davinci_cpdma 
omap_hsmmc musb_am335x tps65217
[   41.343301] CPU: 0 PID: 301 Comm: NetworkManager Not tainted 4.19.0-11-armmp 
#1 Debian 4.19.146-1
[   41.352549] Hardware name: Generic AM33XX (Flattened Device Tree)
[   41.358916] PC is at kfree+0x1b4/0x1f0
[   41.362826] LR is at 0xda4af800
[   41.366100] pc : []lr : []psr: 600f0013
[   41.372630] sp : da061570  ip : dfd2389c  fp : da06159c
[   41.378073] r10: 2878  r9 : cf178000  r8 : dd1d1900
[   41.383518] r7 : cf07ce88  r6 :   r5 : da4af800  r4 : c0991234
[   41.390320] r3 : c112abb0  r2 : da4af800  r1 : 2a33  r0 : de001a00
[   41.397123] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[   41.404561] Control: 10c5387d  Table: 9a114019  DAC: 0051
[   41.410554] Process NetworkManager (pid: 301, stack limit = 0x42389799)
[   41.417448] Stack: (0xda061570 to 0xda062000)
[   41.421991] 1560: da05d680 00041392 
 dd1d1900
[   41.430520] 1580: dd1d1900 da4af940 cf07ce88 dd1d1900 da0615ac da0615a0 
c0991234 c051adac
[   41.439050] 15a0: da0615cc da0615b0 c0995398 c0991210 dd1d1900 dd1d1900 
bf716128 cf07ce88
[   41.447578] 15c0: da0615e4 da0615d0 c09947f0 c099524c cf07cc00 dd1d1900 
da061604 da0615e8
[   41.456106] 15e0: c0994858 c09947cc cf07cc00 cf07cc0c ff92 cf07ce88 
da06162c da061608
[   41.464635] 1600: bf716128 c0994828 c1205dcc dd44ce20  ff0f 
ff0f cf178000
[   41.473165] 1620: da06168c da061630 bf71bff8 bf715fb8 da061650 0004 
0064 da061694
[   41.481693] 1640: da4d1fa0 da4d18c0 da4d1f80 cf178000 da06168c da061660 
bf6993c0 00041392
[   41.490221] 1660:  cf178000 bf71be94 cf17826c cf17826c c1205dcc 
0001 
[   41.498751] 1680: da061704 da061690 bf6a2f38 bf71bea0  786c 
48e09eb4 7854
[   41.507279] 16a0: 0004 7820 0c04 7824 00d8abff 7868 
84036086 783c
[   41.515807] 16c0: 72ee0a72 7838 0029 7828 66964300 00041392 
000186a0 cf178000
[   41.524336] 16e0: cf179000 cf17826c cf17826c  cf17a000  
da061744 da061708
[   41.532866] 1700: bf6a3e1c bf6a2d60 cf17826c 0898 bf71be94 bf6a0aa0 
da061744 cf178000
[   41.541394] 1720: cf179000 cf17826c bf71be94  cf17a000  
da0617bc da061748
[   41.549922] 1740: bf69b548 bf6a3ce0 c03808e4 0100 0200 0001 
 2000
[   41.558453] 1760: 00551139   c1205dcc cf178028 00023f60 

Bug#1052472: linux-image-6.5.0-1-powerpc64: Can't run program if its executable file was made immutable via chattr(1)

2023-09-22 Thread WHR
Package: src:linux
Version: 6.5.3-1
Severity: normal
X-Debbugs-Cc: msl023...@gmail.com, msl023...@gmail.com


Taking executable file /usr/bin/ssh to demonstrate the issue:

# which ssh
/usr/bin/ssh
# ssh   
   
usage: ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-B bind_interface]
   [-b bind_address] [-c cipher_spec] [-D [bind_address:]port]
   [-E log_file] [-e escape_char] [-F configfile] [-I pkcs11]
   [-i identity_file] [-J [user@]host[:port]] [-L address]
   [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p 
port]
   [-Q query_option] [-R address] [-S ctl_path] [-W host:port]
   [-w local_tun[:remote_tun]] destination [command]
# chattr +i /usr/bin/ssh
   
# ssh
Segmentation fault


By trying to load the program via ld.so(1) with truss (actually strace), it 
shows that a mmap(2) call used to load the data segument failed due to EPERM:

# truss -s 128 -f /lib/powerpc64-linux-gnu/ld64.so.1 /usr/bin/ssh
execve("/lib/powerpc64-linux-gnu/ld64.so.1", 
["/lib/powerpc64-linux-gnu/ld64.so.1", "/usr/bin/ssh"], 0x7fffc0380530 /* 29 
vars */) = 0
brk(NULL)   = 0x1000db6
openat(AT_FDCWD, "/usr/bin/ssh", O_RDONLY|O_CLOEXEC) = 3
read(3, 
"\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\25\0\0\0\1\0\0\0\0\0\22h\220\0\0\0\0\0\0\0@\0\0\0\0\0\22\4\330\0\0\0\1\0@\08\0\t\0@\0\35\0\34\0\0\0\6\0\0\0\4\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\1\370\0\0\0\0\0\0\1\370\0\0\0\0\0\0\0\10\0\0\0\3\0\0\0\4"...,
 832) = 832
mmap(NULL, 1259760, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 
0) = 0x7fff9372
mprotect(0x7fff9383, 65536, PROT_NONE) = 0
mmap(0x7fff9384, 131072, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x11) = -1 EPERM (Operation not 
permitted)
close(3)= 0
writev(2, [{iov_base="/usr/bin/ssh", iov_len=12}, {iov_base=": ", 
iov_len=2}, {iov_base="error while loading shared libraries", iov_len=36}, 
{iov_base=": ", iov_len=2}, {iov_base="/usr/bin/ssh", iov_len=12}, {iov_base=": 
", iov_len=2}, {iov_base="failed to map segment from shared object", 
iov_len=40}, {iov_base="", iov_len=0}, {iov_base="", iov_len=0}, 
{iov_base="\n", iov_len=1}], 10/usr/bin/ssh: error while loading shared 
libraries: /usr/bin/ssh: failed to map segment from shared object
) = 107
exit_group(127) = ?
+++ exited with 127 +++


I can also reproduce this issue on Bullseye (with Linux 5.10.0-21-amd64);
while Buster (Linux 4.19.0-23-amd64) is fine.



-- Package-specific info:
** Version:
Linux version 6.5.0-1-powerpc64 (debian-kernel@lists.debian.org) (gcc-13 
(Debian 13.2.0-4) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP Debian 
6.5.3-1 (2023-09-13)

** Command line:
root=ZFS=zr/ROOT/debiansid-be ro quiet 
cgroup_enable=cpuset,cpu,cpuacct,blkio,memory,devices,freezer,net_cls,perf_event,net_prio
 systemd.unified_cgroup_hierarchy=0 
net.ifname-policy=keep,onboard,slot,path,kernel zfs.zfs_txg_timeout=60 
zfs.zfs_arc_max=2166172771 init=/init

** Tainted: PDO (4225)
 * proprietary module was loaded
 * kernel died recently, i.e. there was an OOPS or BUG
 * externally-built ("out-of-tree") module was loaded

** Kernel log:
[ 9345.731918] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9345.731916] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9345.732177] ata16.00: configured for UDMA/66
[ 9345.732243] ata8.00: configured for UDMA/66
[ 9346.079899] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9346.079900] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9346.080160] ata16.00: configured for UDMA/66
[ 9346.080225] ata8.00: configured for UDMA/66
[ 9346.427890] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9346.427891] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9346.428151] ata8.00: configured for UDMA/66
[ 9346.428217] ata16.00: configured for UDMA/66
[ 9346.771879] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9346.771879] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9346.772139] ata8.00: configured for UDMA/66
[ 9346.772204] ata16.00: configured for UDMA/66
[ 9347.115855] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9347.115856] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9347.116116] ata16.00: configured for UDMA/66
[ 9347.116182] ata8.00: configured for UDMA/66
[ 9347.467841] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9347.467842] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9347.468102] ata16.00: configured for UDMA/66
[ 9347.468166] ata8.00: configured for UDMA/66
[ 9347.811831] ata8: SATA link