Perguntas[kernel](unix)

Com qualquer versão do kernel 6.13.*, estou tendo problemas após um longo período de espera, por exemplo, das 21h às 6h da manhã seguinte.

Tudo que está conectado via docking usb-c (todos exceto o monitor HDMI) e o mouse Bluetooth, NÃO funcionam, mesmo se eu desconectar e reconectar o docking. Realmente tenho que reiniciar o notebook. Alguém tem o mesmo problema?

Problema com kernel 6.13.1,2,3,4,5

Ok com kernel 6.12.9

Registro Dmesg:

[10643.878073] usb 3-4: new full-speed USB device number 9 using xhci_hcd
[10644.011719] usb 3-4: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
[10644.011730] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10644.011733] usb 3-4: Product: USB Receiver
[10644.011736] usb 3-4: Manufacturer: Logitech
[10644.016704] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/0003:046D:C534.0006/input/input34
[10644.161858] hid-generic 0003:046D:C534.0006: input,hidraw5: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-4/input0
[10644.165777] input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1/0003:046D:C534.0007/input/input35
[10644.166147] input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1/0003:046D:C534.0007/input/input36
[10644.221883] input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1/0003:046D:C534.0007/input/input37
[10644.222246] hid-generic 0003:046D:C534.0007: input,hiddev98,hidraw6: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-4/input1
[10644.478885] logitech-djreceiver 0003:046D:C534.0006: hidraw5: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-4/input0
[10644.709084] logitech-djreceiver 0003:046D:C534.0007: hiddev98,hidraw6: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-4/input1
[10644.763507] logitech-djreceiver 0003:046D:C534.0007: device of type eQUAD nano Lite (0x0a) connected on slot 1
[10644.765501] logitech-djreceiver 0003:046D:C534.0007: device of type eQUAD nano Lite (0x0a) connected on slot 2
[10644.766851] input: Logitech Wireless Keyboard PID:4023 Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1/0003:046D:C534.0007/0003:046D:4023.0008/input/input40
[10644.858393] hid-generic 0003:046D:4023.0008: input,hidraw7: USB HID v1.11 Keyboard [Logitech Wireless Keyboard PID:4023] on usb-0000:00:14.0-4/input1:1
[10644.861684] input: Logitech Wireless Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1/0003:046D:C534.0007/0003:046D:4091.0009/input/input45
[10645.058798] logitech-hidpp-device 0003:046D:4091.0009: input,hidraw7: USB HID v1.11 Mouse [Logitech Wireless Mouse] on usb-0000:00:14.0-4/input1:2
[10645.064094] input: Logitech Wireless Keyboard PID:4023 as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1/0003:046D:C534.0007/0003:046D:4023.0008/input/input46
[10645.075605] logitech-hidpp-device 0003:046D:4091.0009: HID++ 4.5 device connected.
[10645.168557] logitech-hidpp-device 0003:046D:4023.0008: input,hidraw8: USB HID v1.11 Keyboard [Logitech Wireless Keyboard PID:4023] on usb-0000:00:14.0-4/input1:1
[10681.685625] usb 3-4: USB disconnect, device number 9
[10857.112086] input: Nothing Ear (a) (AVRCP) as /devices/virtual/input/input47
[17043.126127] perf: interrupt took too long (2511 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[18283.310904] input: Nothing Ear (a) (AVRCP) as /devices/virtual/input/input48
[21588.198467] perf: interrupt took too long (3162 > 3138), lowering kernel.perf_event_max_sample_rate to 63000
[26636.117918] input: Nothing Ear (a) (AVRCP) as /devices/virtual/input/input49
[29883.373488] input: Nothing Ear (a) (AVRCP) as /devices/virtual/input/input50
[30007.818580] INPUT DROP: IN=enp0s13f0u1u2u1 OUT= MAC=04:ba:d6:96:73:11:00:50:56:9f:3f:96:08:00 SRC=172.16.1.16 DST=172.16.2.124 LEN=60 TOS=0x00 PREC=0x00 TTL=255 ID=56820 PROTO=ICMP TYPE=8 CODE=0 ID=3 SEQ=26613 
[30089.110360] perf: interrupt took too long (4043 > 3952), lowering kernel.perf_event_max_sample_rate to 49200
[31023.115641] input: Nothing Ear (a) (AVRCP) as /devices/virtual/input/input51
[35275.141809] input: MX Anywhere 2 Keyboard as /devices/virtual/misc/uhid/0005:046D:B01F.000A/input/input52
[35275.141995] input: MX Anywhere 2 Mouse as /devices/virtual/misc/uhid/0005:046D:B01F.000A/input/input53
[35275.142178] hid-generic 0005:046D:B01F.000A: input,hidraw4: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2] on 20:2b:20:a1:e9:9e
[35410.935450] usb 3-5: USB disconnect, device number 4
[35410.935459] usb 3-5.1: USB disconnect, device number 5
[35410.968770] usb 2-1: USB disconnect, device number 2
[35410.968779] usb 2-1.2: USB disconnect, device number 3
[35410.968783] r8152-cfgselector 2-1.2.1: USB disconnect, device number 5
[35411.030133] usb 2-1.4: USB disconnect, device number 4
[35411.413959] usb 3-5.2: USB disconnect, device number 6
[35411.413965] usb 3-5.2.2: USB disconnect, device number 8
[35411.415051] usb 3-5.3: USB disconnect, device number 7
[36322.178167] PM: suspend entry (s2idle)
[36322.215578] Filesystems sync: 0.037 seconds
[36322.344183] Freezing user space processes
[36322.345937] Freezing user space processes completed (elapsed 0.001 seconds)
[36322.345944] OOM killer disabled.
[36322.345945] Freezing remaining freezable tasks
[36322.346681] Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[36322.346686] printk: Suspending console(s) (use no_console_suspend to debug)
[36322.429982] e1000e: EEE TX LPI TIMER: 00000011
[36322.891685] ACPI: EC: interrupt blocked
[38234.289838] ACPI: EC: interrupt unblocked
[38234.543585] usb 3-10: reset full-speed USB device number 3 using xhci_hcd
[38235.090341] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
[38235.091279] OOM killer enabled.
[38235.091284] Restarting tasks ... 
[38235.091550] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
[38235.093554] done.
[38235.093596] random: crng reseeded on system resumption
[38235.095396] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000a lmp_ver=0b lmp_subver=8852
[38235.096370] Bluetooth: hci0: RTL: rom_version status=0 version=1
[38235.096384] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852au_fw.bin
[38235.096924] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852au_config.bin
[38235.097035] Bluetooth: hci0: RTL: cfg_sz 6, total sz 64499
[38235.105678] PM: suspend exit
[38235.226009] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
[38235.395553] Bluetooth: hci0: RTL: fw version 0xd9d617da
[38235.479408] Bluetooth: hci0: AOSP extensions version v1.00
[38235.479420] Bluetooth: hci0: AOSP quality report is supported
[38235.479607] Bluetooth: MGMT ver 1.23
[38238.273461] usb 3-5: new full-speed USB device number 10 using xhci_hcd
[38238.393204] usb 3-5: device descriptor read/64, error -71
[38238.619873] usb 3-5: device descriptor read/64, error -71
[38238.849837] usb 3-5: new full-speed USB device number 11 using xhci_hcd
[38238.966573] usb 3-5: device descriptor read/64, error -71
[38239.189879] usb 3-5: device descriptor read/64, error -71
[38239.293270] usb usb3-port5: attempt power cycle
[38239.679842] usb 3-5: new full-speed USB device number 12 using xhci_hcd
[38239.679991] usb 3-5: Device not responding to setup address.
[38239.886666] usb 3-5: Device not responding to setup address.
[38240.089839] usb 3-5: device not accepting address 12, error -71
[38240.089927] usb 3-5: WARN: invalid context state for evaluate context command.
[38240.206515] usb 3-5: new full-speed USB device number 13 using xhci_hcd
[38240.206706] usb 3-5: Device not responding to setup address.
[38240.225794] hp_wmi: Unknown event_id - 131073 - 0x0
[38240.246340] Registered IR keymap rc-cec
[38240.246879] rc rc0: DP-1 as /devices/pci0000:00/0000:00:02.0/rc/rc0
[38240.247398] input: DP-1 as /devices/pci0000:00/0000:00:02.0/rc/rc0/input55
[38240.412046] usb 3-5: Device not responding to setup address.
[38240.613457] usb 3-5: device not accepting address 13, error -71
[38240.613635] usb 3-5: WARN: invalid context state for evaluate context command.
[38240.613695] usb usb3-port5: unable to enumerate USB device
[38244.139849] xhci_hcd 0000:00:0d.0: Timeout while waiting for setup device command
[38244.432592] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd
[38244.750203] usb 2-1: New USB device found, idVendor=2109, idProduct=0817, bcdDevice= 3.74
[38244.750211] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[38244.750212] usb 2-1: Product: USB3.0 Hub             
[38244.750213] usb 2-1: Manufacturer: VIA Labs, Inc.         
[38244.751295] hub 2-1:1.0: USB hub found
[38244.751512] hub 2-1:1.0: 4 ports detected
[38289.059732] usb 3-5: new high-speed USB device number 14 using xhci_hcd
[38289.179762] usb 3-5: device descriptor read/64, error -71
[38289.418594] usb 3-5: New USB device found, idVendor=2109, idProduct=2817, bcdDevice= 3.74
[38289.418607] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[38289.418608] usb 3-5: Product: USB2.0 Hub             
[38289.418609] usb 3-5: Manufacturer: VIA Labs, Inc.         
[38289.419832] hub 3-5:1.0: USB hub found
[38289.420141] hub 3-5:1.0: 5 ports detected
[38290.759722] usb 3-5.2: new full-speed USB device number 15 using xhci_hcd
[38290.891370] usb 3-5.2: New USB device found, idVendor=320f, idProduct=5044, bcdDevice= 0.45
[38290.891374] usb 3-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[38290.891375] usb 3-5.2: Product: GMMK PRO
[38290.891376] usb 3-5.2: Manufacturer: USB HID
[38290.899558] input: USB HID GMMK PRO as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5.2/3-5.2:1.0/0003:320F:5044.000B/input/input56
[38291.019872] hid-generic 0003:320F:5044.000B: input,hidraw1: USB HID v1.11 Keyboard [USB HID GMMK PRO] on usb-0000:00:14.0-5.2/input0
[38291.020990] input: USB HID GMMK PRO Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5.2/3-5.2:1.1/0003:320F:5044.000C/input/input58
[38291.021086] input: USB HID GMMK PRO Consumer Control as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5.2/3-5.2:1.1/0003:320F:5044.000C/input/input59
[38291.073232] input: USB HID GMMK PRO Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5.2/3-5.2:1.1/0003:320F:5044.000C/input/input61
[38291.073408] hid-generic 0003:320F:5044.000C: input,hiddev96,hidraw2: USB HID v1.11 Mouse [USB HID GMMK PRO] on usb-0000:00:14.0-5.2/input1
[38291.073881] hid-generic 0003:320F:5044.000D: hiddev97,hidraw3: USB HID v1.11 Device [USB HID GMMK PRO] on usb-0000:00:14.0-5.2/input2
[38291.203098] usb 3-5.3: new high-speed USB device number 16 using xhci_hcd
[38291.333336] usb 3-5.3: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[38291.333341] usb 3-5.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[38291.333342] usb 3-5.3: Product: USB 2.0 Hub
[38291.334271] hub 3-5.3:1.0: USB hub found
[38291.334313] hub 3-5.3:1.0: 4 ports detected
[38291.399719] usb 3-5.5: new high-speed USB device number 17 using xhci_hcd
[38291.484432] usb 3-5.5: New USB device found, idVendor=2109, idProduct=8888, bcdDevice= 0.01
[38291.484438] usb 3-5.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38291.484440] usb 3-5.5: Product: USB Billboard Device   
[38291.484442] usb 3-5.5: Manufacturer: VIA Labs, Inc.         
[38291.484443] usb 3-5.5: SerialNumber: 0000000000000001
[38291.823086] usb 2-1.3: new SuperSpeed USB device number 7 using xhci_hcd
[38291.836978] usb 2-1.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=31.00
[38291.836981] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[38291.836982] usb 2-1.3: Product: USB 10/100/1000 LAN
[38291.836983] usb 2-1.3: Manufacturer: Realtek
[38291.836984] usb 2-1.3: SerialNumber: 001000001
[38291.906604] r8152-cfgselector 2-1.3: reset SuperSpeed USB device number 7 using xhci_hcd
[38291.956741] r8152 2-1.3:1.0 eth0: v1.12.13
[38292.335046] r8152 2-1.3:1.0 enp0s13f0u1u3: renamed from eth0
[38295.385589] r8152 2-1.3:1.0 enp0s13f0u1u3: carrier on
[38342.321212] input: MX Anywhere 2 Keyboard as /devices/virtual/misc/uhid/0005:046D:B01F.000E/input/input62
[38342.321608] input: MX Anywhere 2 Mouse as /devices/virtual/misc/uhid/0005:046D:B01F.000E/input/input63
[38342.322083] hid-generic 0005:046D:B01F.000E: input,hidraw4: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2] on 20:2b:20:a1:e9:9e
[51204.954310] input: MX Anywhere 2 Keyboard as /devices/virtual/misc/uhid/0005:046D:B01F.000F/input/input65
[51204.954541] input: MX Anywhere 2 Mouse as /devices/virtual/misc/uhid/0005:046D:B01F.000F/input/input66
[51204.954699] hid-generic 0005:046D:B01F.000F: input,hidraw4: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2] on 20:2b:20:a1:e9:9e
[51281.794692] netfs: FS-Cache loaded
[51281.821502] RPC: Registered named UNIX socket transport module.
[51281.821504] RPC: Registered udp transport module.
[51281.821505] RPC: Registered tcp transport module.
[51281.821505] RPC: Registered tcp-with-tls transport module.
[51281.821505] RPC: Registered tcp NFSv4.1 backchannel transport module.
[51281.859835] Key type dns_resolver registered
[51281.931438] NFS: Registering the id_resolver key type
[51281.931448] Key type id_resolver registered
[51281.931449] Key type id_legacy registered
[51282.382707] Key type cifs.spnego registered
[51282.382727] Key type cifs.idmap registered
[51282.383303] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[51282.383308] CIFS: Attempting to mount //samba.gmmg.lan/public
[70913.141668] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command
[70913.141702] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
[70913.141731] xhci_hcd 0000:00:14.0: HC died; cleaning up
[70913.141765] usb 3-2: USB disconnect, device number 2
[70913.141883] xhci_hcd 0000:00:14.0: Timeout while waiting for stop endpoint command
[70913.143632] usb 3-5: USB disconnect, device number 14
[70913.143642] usb 3-5.2: USB disconnect, device number 15
[70913.530229] usb 3-5.3: USB disconnect, device number 16
[70913.530703] usb 3-5.5: USB disconnect, device number 17
[70913.531509] usb 3-10: USB disconnect, device number 3

Tenho tido esse problema há algum tempo e pensei que a nova versão do kernel Linux iria corrigi-lo, mas não foi o que aconteceu.

Não consigo descobrir qual é o erro, suspeito de algo relacionado à comparabilidade do BIOS, mas não consigo inicializar o Kali ou qualquer outro sistema operacional Linux nesse computador. Aqui estão as mensagens de erro geradas ao inicializar. (Cálculo: 83HM0001US)

Arquivos antigos do kernel estão se acumulando e eu gostaria de remover todos, exceto a versão atual e as duas versões anteriores, para liberar espaço.

Quando executo apt autoremove, os kernels antigos não são reconhecidos como elegíveis para remoção.

Então eu dei uma olhada /etc/apt/apt.conf.d/01autoremovee parece que todos linux-imageos pacotes são cobertos por NeverAutoRemoveo que explica por que eles não são pegos por apt autoremove. Aqui está o conteúdo:

APT
{
  NeverAutoRemove
  {
    "^firmware-linux.*";
    "^linux-firmware$";
    "^linux-image-[a-z0-9]*$";
    "^linux-image-[a-z0-9]*-[a-z0-9]*$";
  };

  VersionedKernelPackages
  {
    # kernels
    "linux-.*";
    "kfreebsd-.*";
    "gnumach-.*";
    # (out-of-tree) modules
    ".*-modules";
    ".*-kernel";
  };

  Never-MarkAuto-Sections
  {
    "metapackages";
    "contrib/metapackages";
    "non-free/metapackages";
    "restricted/metapackages";
    "universe/metapackages";
    "multiverse/metapackages";
  };

  Move-Autobit-Sections
  {
    "oldlibs";
    "contrib/oldlibs";
    "non-free/oldlibs";
    "restricted/oldlibs";
    "universe/oldlibs";
    "multiverse/oldlibs";
  };
};

Também vi que todas as imagens, cabeçalhos e módulos (usando Pop!_OS com um kernel Linux Surface ) são marcados como instalados manualmente com apt-mark showmanual | grep linux:

linux-headers-6.0.12-76060006
linux-headers-6.0.12-76060006-generic
linux-headers-6.0.6-76060006
linux-headers-6.1.11-76060111
linux-headers-6.1.11-76060111-generic
linux-headers-6.1.11-surface
linux-headers-6.1.12-surface
linux-headers-6.1.6-surface
linux-headers-6.2.0-76060200
linux-headers-6.2.0-76060200-generic
linux-headers-6.2.10-surface
linux-headers-6.2.14-surface
linux-headers-6.2.2-surface
linux-headers-6.2.5-surface
linux-headers-6.2.6-76060206
linux-headers-6.2.6-76060206-generic
linux-headers-6.2.8-surface
linux-headers-6.3.3-surface
linux-headers-6.3.7-surface
linux-headers-6.4.12-surface
linux-headers-6.4.2-surface
linux-headers-6.4.4-surface
linux-headers-6.4.6-76060406
linux-headers-6.4.6-76060406-generic
linux-headers-6.5.4-76060504
linux-headers-6.5.4-76060504-generic
linux-headers-6.5.5-surface
linux-headers-6.5.6-76060506
linux-headers-6.5.6-76060506-generic
linux-headers-6.5.6-surface
linux-headers-6.5.7-surface-2
linux-headers-6.6.1-surface-1
linux-headers-6.6.10-76060610
linux-headers-6.6.10-76060610-generic
linux-headers-6.6.11-surface-1
linux-headers-6.6.5-surface-1
linux-headers-6.6.6-76060606
linux-headers-6.6.6-76060606-generic
linux-headers-6.6.6-surface-1
linux-headers-6.7.2-surface-1
linux-headers-6.7.6-surface-1
linux-headers-6.7.9-surface-1
linux-headers-6.8.0-76060800daily20240311
linux-headers-6.8.0-76060800daily20240311-generic
linux-headers-6.8.1-surface-1
linux-headers-6.8.8-surface-1
linux-headers-6.9.3-76060903
linux-headers-6.9.3-76060903-generic
linux-headers-6.9.3-surface-2
linux-headers-surface
linux-image-6.1.11-surface
linux-image-6.1.12-surface
linux-image-6.1.6-surface
linux-image-6.2.0-76060200-generic
linux-image-6.2.10-surface
linux-image-6.2.14-surface
linux-image-6.2.2-surface
linux-image-6.2.5-surface
linux-image-6.2.6-76060206-generic
linux-image-6.2.8-surface
linux-image-6.3.3-surface
linux-image-6.3.7-surface
linux-image-6.4.12-surface
linux-image-6.4.2-surface
linux-image-6.4.4-surface
linux-image-6.4.6-76060406-generic
linux-image-6.5.4-76060504-generic
linux-image-6.5.5-surface
linux-image-6.5.6-76060506-generic
linux-image-6.5.6-surface
linux-image-6.5.7-surface-2
linux-image-6.6.1-surface-1
linux-image-6.6.10-76060610-generic
linux-image-6.6.11-surface-1
linux-image-6.6.5-surface-1
linux-image-6.6.6-76060606-generic
linux-image-6.6.6-surface-1
linux-image-6.7.2-surface-1
linux-image-6.7.6-surface-1
linux-image-6.7.9-surface-1
linux-image-6.8.0-76060800daily20240311-generic
linux-image-6.8.1-surface-1
linux-image-6.8.8-surface-1
linux-image-6.9.3-76060903-generic
linux-image-6.9.3-surface-2
linux-image-surface
linux-modules-6.0.12-76060006-generic
linux-modules-6.1.11-76060111-generic
linux-modules-6.2.0-76060200-generic
linux-modules-6.2.6-76060206-generic
linux-modules-6.4.6-76060406-generic
linux-modules-6.5.4-76060504-generic
linux-modules-6.5.6-76060506-generic
linux-modules-6.6.10-76060610-generic
linux-modules-6.6.6-76060606-generic
linux-modules-6.8.0-76060800daily20240311-generic
linux-modules-6.9.3-76060903-generic

Então tentei remover um dos pacotes mais antigos manualmente com apt remove linux-image-6.1.11-76060111-generic:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  linux-image-6.1.11-76060111-generic
0 upgraded, 0 newly installed, 1 to remove and 250 not upgraded.
After this operation, 12.3 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 1219145 files and directories currently installed.)
Removing linux-image-6.1.11-76060111-generic (6.1.11-76060111.202302091138~1675975749~22.04~f771a7f) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.11-76060111-generic

Isso deixa para trás os pacotes de cabeçalhos e módulos. Vejo que eles estão listados VersionedKernelPackagesna configuração autoremove, mas meu entendimento é que autoremove deve manter como padrão apenas as últimas versões.

A verificação das dependências dos cabeçalhos e módulos restantes mostra apenas uma dependência no linux-imagepacote removido com sucesso:

user@os:~$ apt-cache rdepends linux-headers-6.1.11-76060111-generic
linux-headers-6.1.11-76060111-generic
Reverse Depends:
  linux-image-6.1.11-76060111-generic

user@os:~$ apt-cache rdepends linux-modules-6.1.11-76060111-generic 
linux-modules-6.1.11-76060111-generic
Reverse Depends:
  linux-image-6.1.11-76060111-generic

Que outros fatores podem estar desempenhando um papel na prevenção de que esses pacotes sejam removidos junto com o linux-imagepacote?

Pelo que entendi, um processo em tempo real significa que o processo obterá a CPU assim que precisar. O kernel é responsável por essa tarefa com seu mecanismo de agendamento interno.

Por outro lado, a afinidade de processo significa que o processo terá uma CPU dedicada para si mesmo e não será gerenciado pelo agendador do kernel. Então, se entendi corretamente, é ainda melhor do que ser um processo em tempo real. É como programar para um Arduino, mas apenas com uma CPU muito mais rápida. Além disso, no meu entendimento para afinidade de processo, precisamos de pelo menos uma CPU dual core e devemos deixar pelo menos uma CPU para o próprio sistema operacional. Então, com a ajuda da afinidade de processo, um programa que foi escrito para um Arduino pode ser portado para uma placa Linux como o Raspberry Pi Zero 2 W (que tem uma CPU quad-core) e teria todos os benefícios de um microcontrolador apenas com uma CPU mais rápida.

Meu entendimento está correto?

Estou tentando hackear o kernel do Linux e adicionar/modificar alguns arquivos de cabeçalho no formato include/linux. No entanto, quando eu gero o arquivo de patch usando diff:

diff -uprN -X linux/Documentation/dontdiff \
        linux-5.15 linux-srctree > patch.p1

Encontro alterações em include/linuxnão incluídas em patch.p1. Em seguida, examino dontdiffo arquivo e encontro as seguintes linhas (em torno da linha 158), o que significa que ele exclui include/linuxdo arquivo de patch.

*lex.*.c
linux
logo_*.c

Então, por que dontdiffinclui linux? Como salvar alterações em arquivos de patch para cabeçalhos include/linux? Muito obrigado.

Estou investigando o impacto da memória ao conteinerizar dois processos que dependem do mesmo objeto compartilhado. Minha principal dúvida é se o objeto compartilhado será carregado na memória duas vezes ou não.

Essa pergunta já foi feita antes, mas as respostas não eram completas e contradiziam meus experimentos. Vou citar o que já encontrei:

Carregamento de bibliotecas compartilhadas e uso de RAM --> Use -fPIC para seu .so

Os contêineres docker compartilham RAM para arquivos mapeados na memória da mesma camada, mas de uma imagem diferente? --> Sim, mas depende da sua configuração. Você pode provar isso verificando o dispositivo e o id do inode do objeto compartilhado carregado. Nenhuma indicação de qual configuração usar.

https://stackoverflow.com/questions/35863608/shared-library-in-containers --> Sim, depende do seu driver de armazenamento. Os drivers de armazenamento aufs, overlay ou overlay2 oferecem suporte a isso.

https://stackoverflow.com/questions/63145223/about-loading-dynamic-library-in-container --> Cada contêiner é sua própria unidade de execução. Nenhum compartilhamento ocorre. Contradizendo com o anterior.

Usei a seguinte configuração:

• camada base --> Contém o SO e dois objetos compartilhados (G e S - Pré-compilados usando -fPIC)
• camada dependsOnG --> Começa da base, contém o executável que depende apenas de G (pré-compilado)
• camada dependsOnGandS --> Começa da base, contém o executável que depende de G e S (pré-compilado)

Driver de armazenamento: Sobreposição

Abaixo você pode ver as informações de grep glib /proc/PID/maps. Os PIDs são os processos dos executáveis ​​dentro do contêiner.

| /proc/17/maps:7efd3b630000-7efd41980000 | r-xp | 00000000 | 00:a2             | 16802420 | /app/libglib.so |
| /proc/17/maps:7efd41980000-7efd41b7f000 | ---p | 06350000 | 00:a2             | 16802420 | /app/libglib.so |
| /proc/17/maps:7efd41b7f000-7efd41b80000 | r--p | 0634f000 | 00:a2             | 16802420 | /app/libglib.so |
| /proc/17/maps:7efd41b80000-7efd41b81000 | rw-p | 06350000 | 00:a2             | 16802420 | /app/libglib.so |

| /proc/39/maps:7fca97208000-7fca9d558000 | r-xp | 00000000 | 00:bb             | 16802420 | /app/libglib.so |
| /proc/39/maps:7fca9d558000-7fca9d757000 | ---p | 06350000 | 00:bb             | 16802420 | /app/libglib.so |
| /proc/39/maps:7fca9d757000-7fca9d758000 | r--p | 0634f000 | 00:bb             | 16802420 | /app/libglib.so |
| /proc/39/maps:7fca9d758000-7fca9d759000 | rw-p | 06350000 | 00:bb             | 16802420 | /app/libglib.so |

Se eu interpretar o resultado corretamente, os dois processos visualizam arquivos completamente diferentes (o ID do dispositivo é diferente), portanto, o objeto compartilhado será carregado duas vezes na memória (parece consistente com o que vejo com o comando free).

De acordo com as informações que encontrei online, isso não deveria acontecer.

Tenho as seguintes perguntas:

1. O objeto compartilhado deve ser carregado apenas uma vez?
2. O driver de armazenamento de sobreposição suporta essa funcionalidade?
3. Devo construir minhas imagens/contêineres de uma maneira diferente? (Fiz os mesmos experimentos usando volumes em vez de camadas comuns e, de fato, os arquivos eram idênticos, no entanto, não é bem isso que eu quero)

Desde já, obrigado!

Não preciso de “ajuda” para inserir nouveauou instalar drivers proprietários. A questão é sobre nvidiafb. Obrigado.

Estou usando a GPU nvidia GT710 no Linux 6.9-rc2. Eu queria usar o nvidiafbdriver simples para minha GPU antiga. Nesse sistema, só preciso do framebuffer, nada mais (sem DRI). Mas nvidiafbnão funciona, trava.

# modprobe nvidiafb
Killed
#

nvidiafb: Device ID: 10de1287
Console: switching to colour dummy device 80x25
nvidiafb 0000:03:00.0: vgaarb: deactivate vga console
nvidiafb: CRTC0 analog not found
nvidiafb: CRTC1 analog not found                            
nvidiafb: Unable to detect display type...
...Using default of CRT
nvidiafb: Unable to detect which CRTCNumber...
...Defaulting to CRTCNumber 0                               
nvidiafb: Using CRT on CRTC 0                               
fbcon: NV28 (fb0) is primary device

divide error: 0000 [#1] PREEMPT_RT SMP                     
CPU: 0 PID: 194915 Comm: modprobe Tainted: G           OE      6.9.0-rc2-home-rt+ #3                                                                    Hardware name: OEM X79G/X79G, BIOS 4.6.5 08/02/2022
RIP: 0010:nvGetClocks+0x18f/0x290 [nvidiafb]
Code: 0f 84 91 00 00 00 3d 30 03 00 00 0f 84 86 00 00 00 41 8b 89 04 05 00 00 0f b6 c5 44 0f b6 c9 c1 e9 10 0f af c2 31 d2 83 e1 0f <41> f7 f1 d3 e8 89 06 48 8b 87 a8 12 00 00 8b 88 00 05 00 00 0f b6
RSP: 0018:ffffa681b17e74e0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff921541eb4518 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffa681b17e7520 RDI: ffff921541eb4420
RBP: ffffa681b17e74e8 R08: ffffa681b17e7524 R09: 0000000000000000                                                                                           R10: ffff921541eb4420 R11: 00000000002e18c8 R12: 0000000000000020                                                                                           R13: 0000000000000008 R14: 0000000000000008 R15: 0000000000000068
FS:  00007fa3af639c40(0000) GS:ffff922406200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2f8401f000 CR3: 00000010275bc001 CR4: 00000000001706f0
Call Trace:
<TASK>
  ? show_regs+0x6b/0x80
  ? __die_body+0x24/0x70
  ? die+0x42/0x70
  ? do_trap+0xde/0x100
  ? do_error_trap+0x73/0xa0
  ? nvGetClocks+0x18f/0x290 [nvidiafb]
  ? exc_divide_error+0x3f/0x60
  ? nvGetClocks+0x18f/0x290 [nvidiafb]
  ? asm_exc_divide_error+0x1f/0x30
  ? nvGetClocks+0x18f/0x290 [nvidiafb]
  NVCalcStateExt+0x1da/0x9b0 [nvidiafb]
  ? set_inverse_trans_unicode+0xd0/0x100
  ? kmalloc_trace+0xac/0x280
  nvidiafb_set_par+0x4a3/0xa40 [nvidiafb]
  fbcon_init+0x2af/0x600                                       
  visual_init+0xf2/0x190                                       
  do_bind_con_driver+0x1d2/0x4a0  
  do_take_over_console+0x144/0x240
  ? vprintk_default+0x21/0x30
  do_fbcon_takeover+0x78/0x130                               
  do_fb_registered+0x139/0x270
  fbcon_fb_registered+0x3b/0x90                              
  ? fb_add_videomode+0x81/0xf0
  register_framebuffer+0x20a/0x300                           
  nvidiafb_probe+0x6a4/0xad0 [nvidiafb]
  ? rt_spin_unlock+0x1c/0x50                                
  local_pci_probe+0x4f/0xb0
  pci_device_probe+0xcc/0x280
  really_probe+0xff/0x390
  __driver_probe_device+0x8a/0x170
  driver_probe_device+0x23/0xb0
  __driver_attach+0xc9/0x190                                 
  ? __pfx___driver_attach+0x10/0x10
  bus_for_each_dev+0x80/0xd0                                 
  driver_attach+0x22/0x30
  bus_add_driver+0x123/0x230
  driver_register+0x68/0x130
  ? __pfx_nvidiafb_init+0x10/0x10 [nvidiafb]
  __pci_register_driver+0x6e/0x80                             
  nvidiafb_init+0x37/0x50 [nvidiafb]                         
  do_one_initcall+0x4c/0x310                                 
  ? do_init_module+0x28/0x270                                
  ? kmalloc_trace+0xac/0x280
  do_init_module+0x6a/0x270                                  
  load_module+0x221b/0x22e0
  init_module_from_file+0x9c/0xe0                            
  ? init_module_from_file+0x9c/0xe0                        
  idempotent_init_module+0x173/0x230                         
  __x64_sys_finit_module+0x61/0xc0                           
  do_syscall_64+0x79/0x120                                 
  ? ksys_mmap_pgoff+0x11c/0x260                              
  ? syscall_exit_to_user_mode+0x87/0x1c0
  ? do_syscall_64+0x85/0x120                                 
  ? do_syscall_64+0x85/0x120
  entry_SYSCALL_64_after_hwframe+0x71/0x79
RIP: 0033:0x7fa3af75988d
Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 b5 0f 00 f7 d8 64 89 01 48                                                      RSP: 002b:00007ffe8864c978 EFLAGS: 00000246 ORIG_RAX: 0000000000000139                                                                                      RAX: ffffffffffffffda RBX: 0000563b56dcbf80 RCX: 00007fa3af75988d                                                                                           RDX: 0000000000000000 RSI: 0000563b56dbacd2 RDI: 0000000000000005                                                                                           RBP: 0000000000040000 R08: 0000000000000000 R09: 0000000000000002                                                                                            R10: 0000000000000005 R11: 0000000000000246 R12: 0000563b56dbacd2                                                                                           R13: 0000563b56dcc1b0 R14: 0000563b56dcc950 R15: 0000563b56dc5110                                                                                            
</TASK>                                                    Modules linked in: nvidiafb(+) vgastate fb_ddc vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) ip6t_REJECT nf_reject_ipv6 ip6t_rt ipt_REJECT nf_reject_ipv4 xt_recent nft_limit xt_limit xt_addrtype xt_tcpudp xt_pkttype nft_chain_nat xt_MASQUERADE xt_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink binfmt_misc intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_realtek snd_hda_codec_generic snd_hda_scodec_component snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel snd_intel_dspcfg input_leds snd_intel_sdw_acpi kvm joydev snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq rapl snd_seq_device intel_cstate snd_timer serio_raw pcspkr snd ioatdma soundcore dca mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua parport_pc ppdev lp parport efi_pstore ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy
  async_pq async_xor async_tx raid1 raid0 gpu_sched drm_gpuvm drm_exec mxm_wmi video wmi i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper cdc_ether usbnet drm hid_generic psmouse r8152 usbhid crct10dif_pclmul crc32_pclmul uas ghash_clmulni_intel sha512_ssse3 usb_storage hid sha256_ssse3 ahci sha1_ssse3 mii r8169 i2c_i801 libahci lpc_ich i2c_smbus realtek aesni_intel crypto_simd cryptd
---[ end trace 0000000000000000 ]---                       
RIP: 0010:nvGetClocks+0x18f/0x290 [nvidiafb]
Code: 0f 84 91 00 00 00 3d 30 03 00 00 0f 84 86 00 00 00 41 8b 89 04 05 00 00 0f b6 c5 44 0f b6 c9 c1 e9 10 0f af c2 31 d2 83 e1 0f <41> f7 f1 d3 e8 89 06 48 8b 87 a8 12 00 00 8b 88 00 05 00 00 0f b6                                                     
RSP: 0018:ffffa681b17e74e0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff921541eb4518 RCX: 0000000000000000                                                                                          RDX: 0000000000000000 RSI: ffffa681b17e7520 RDI: ffff921541eb4420                                                                                          
RBP: ffffa681b17e74e8 R08: ffffa681b17e7524 R09: 0000000000000000
R10: ffff921541eb4420 R11: 00000000002e18c8 R12: 0000000000000020                                                                                           
R13: 0000000000000008 R14: 0000000000000008 R15: 0000000000000068                                                                                         
FS:  00007fa3af639c40(0000) GS:ffff922406200000(0000) knlGS:0000000000000000                                                                                
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2f8401f000 CR3: 00000010275bc001 CR4: 00000000001706f0

note: modprobe[194915] exited with preempt_count 2

Qual é o problema exato que impede que ele funcione corretamente com minha GPU? A divisão em nvGetClocks+0x18f/0x290está em video/fbdev/nvidia/nv_hw.c, provavelmente aqui (linha 213) . Como a parte divisora ​​da divisão acaba sendo zero, com esta GPU específica (não as outras, mais antigas)?

Obrigado.

Usar lshwpara consultar meu adaptador USB WiFi mostra o seguinte:

$ lshw -C network
  *-network                 
       description: Wireless interface
       physical id: 12
       bus info: usb@3:7
       logical name: ...
       serial: ...
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rtw_8822bu driverversion=6.5.0-28-generic firmware=N/A ip=... link=yes multicast=yes wireless=IEEE 802.11

O adaptador funciona bem. No entanto, estou confuso com driver=rtw_8822bu. Até onde eu sei, não há nenhum modelo de kernel chamado rtw_8822bu.koem meu sistema; em vez disso, eu tenho rtw88_8822bu.ko,

/usr/lib/modules/6.5.0-28-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822bu.ko

que também aparece usando lsmod:

$ lsmod | grep rtw
rtw88_8822bu           12288  0
rtw88_usb              24576  1 rtw88_8822bu
rtw88_8822b           229376  1 rtw88_8822bu
rtw88_core            356352  2 rtw88_usb,rtw88_8822b
mac80211             1720320  3 rtw88_core,rtw88_usb,rtl8xxxu
cfg80211             1323008  3 rtw88_core,mac80211,rtl8xxxu

Pergunta : Por que lshwaparece driver=rtw_8822buquando o módulo do kernel no sistema é nomeado rtw88_8822bu. De onde vem o nome anterior?

Ao tentar inicializar a partir de um NixOS live usb com 23.11, gnome para x86_64:

Em uma placa-mãe Asus C236 WSI com este BIOS:

$ ls -l /sys/class/dmi/id/bios*                                                                                                                                                 
-r--r--r-- 1 root root 4096 Apr 24 09:59 /sys/class/dmi/id/bios_date
-r--r--r-- 1 root root 4096 Apr 24 09:59 /sys/class/dmi/id/bios_release
-r--r--r-- 1 root root 4096 Apr 24 09:01 /sys/class/dmi/id/bios_vendor
-r--r--r-- 1 root root 4096 Apr 24 09:56 /sys/class/dmi/id/bios_version
$ cat /sys/class/dmi/id/bios*                                                                                                                                                   
10/21/2015
5.11
American Megatrends Inc.
P1.00

a tela de inicialização fica presa na primeira linha com:

Probing EDD (edd=off to disable)... ok

Na máquina virtual Kali, atribuí a memória 4G, assim;

Mas há um problema. Instalei o kernel de autoconstrução no convidado para hackear a memória.

# uname -a
Linux 15ud490-gx76k 6.8.4+ #8 SMP PREEMPT_DYNAMIC Sat Apt 6 15:49:20 KST 2024 x86_64 x86_64 x86_64 GNU/Linux

E quero ver uma área de fim de memória, digitada como abaixo.

Diz que o tamanho da memória é 16*0x336000 bytes. Então inferi o tamanho da memória com os resultados (no host).

$ python3
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 16*0x07fff0
8388352
>>> 16*0x07fff0/1024/1024
7.999755859375
>>> 16*0x335ff0/1024/1024
51.374755859375
>>> 16*0x336000/1024/1024
51.375
>>> 521000/1024/1024
0.49686431884765625
>>> (1024*1024*4+521000+3288)*1024/1024/1024/1024 # Convert into gigabytes
4.5

Dei a memória 4G para convidado mas ela tem 4,5GiB conforme acima. A troca é 1G, então é um absurdo.

Onde está a fonte de memória 0,5G ?????