AskOverflow.Dev

AskOverflow.Dev Logo AskOverflow.Dev Logo

AskOverflow.Dev Navigation

  • 主页
  • 系统&网络
  • Ubuntu
  • Unix
  • DBA
  • Computer
  • Coding
  • LangChain

Mobile menu

Close
  • 主页
  • 系统&网络
    • 最新
    • 热门
    • 标签
  • Ubuntu
    • 最新
    • 热门
    • 标签
  • Unix
    • 最新
    • 标签
  • DBA
    • 最新
    • 标签
  • Computer
    • 最新
    • 标签
  • Coding
    • 最新
    • 标签
主页 / unix / 问题

问题[kernel](unix)

Martin Hope
ancoling67
Asked: 2025-03-04 16:25:34 +0800 CST

内核 6.13.* 和待机问题

  • 5

使用任何版本的内核 6.13.* 后,我都会遇到问题,例如从晚上 9 点到第二天早上 6 点。

通过 USB-C 基座连接的所有设备(HDMI 显示器除外)和蓝牙鼠标均无法工作,即使我断开并重新连接基座也是如此。我真的必须重新启动笔记本电脑。有人遇到同样的问题吗?

内核 6.13.1,2,3,4,5 存在问题

内核 6.12.9 正常

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

在此处输入图片描述

kernel
  • 1 个回答
  • 45 Views
Martin Hope
TrottingDeer
Asked: 2024-12-28 08:20:49 +0800 CST

在联想 Yoga Aura Edition 电脑上启动 Kali Live 时出现持续错误

  • 5

我遇到这个问题已经有一段时间了,我以为新的 Linux 内核版本会修复它,但是没有。

我不知道错误是什么,我怀疑是与 BIOS 兼容性有关,但我无法在这台电脑上启动 Kali 或任何其他 Linux 操作系统。以下是启动时抛出的错误消息。(计算:83HM0001US)

错误消息

kernel
  • 4 个回答
  • 46 Views
Martin Hope
Rob
Asked: 2024-12-26 08:56:50 +0800 CST

模块和头文件没有随 linux-image 一起被删除

  • 6

旧内核文件正在堆积如山,我想删除除当前版本和之前两个版本之外的所有文件以清除一些空间。

当我运行时apt autoremove,旧内核不被识别为可以删除。

所以我看了一下/etc/apt/apt.conf.d/01autoremove,似乎所有linux-image包裹都包含在内NeverAutoRemove,这解释了为什么它们没有被领取apt autoremove。内容如下:

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";
  };
};

我还看到所有图像,标题和模块(使用带有linux-surface内核的 Pop!_OS)都标记为手动安装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

因此我尝试使用以下命令手动删除一个最旧的软件包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

不过,这留下了标头和模块包。我看到它们列VersionedKernelPackages在自动移除配置下,但我的理解是自动移除应该默认只保留最后几个版本。

检查剩余标题和模块的依赖关系仅显示对成功删除的linux-image包的依赖:

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

还有哪些因素可能导致这些包裹无法随linux-image包裹一起被移除?

kernel
  • 1 个回答
  • 19 Views
Martin Hope
Parsa99
Asked: 2024-11-03 18:59:34 +0800 CST

实时进程与进程亲和性

  • 6
悬赏将于 3 天后到期。回答此问题可获得+100声誉悬赏。Parsa99 正在寻找来自信誉良好的来源的答案。

据我所知,实时进程意味着进程会在需要时立即获得 CPU。内核通过其内部调度机制负责此任务。

另一方面,进程亲和性意味着进程将获得一个专用的 CPU,并且不会由内核调度程序管理。所以,如果我理解正确的话,它甚至比实时进程更好。这就像为 Arduino 编程,但只是使用更快的 CPU。此外,据我了解,对于进程亲和性,我们至少需要一个双核 CPU,并且我们必须为操作系统本身留出至少一个 CPU。因此,借助进程亲和性,为 Arduino 编写的程序可以移植到 Linux 主板(如 Raspberry Pi Zero 2 W,它具有四核 CPU),并且可以享受微控制器的所有优势,但 CPU 更快。

我的理解正确吗?

kernel
  • 1 个回答
  • 80 Views
Martin Hope
Kalman
Asked: 2024-07-23 11:22:23 +0800 CST

如何使用“diff”保存对“include/linux”中内核头文件的补丁文件的更改?

  • 5

我正在尝试破解Linux内核并添加/修改了一些头文件include/linux。但是,当我使用以下命令生成补丁文件时diff:

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

我发现更改include/linux未包含在内patch.p1。然后我查看dontdiff文件并找到以下几行(大约 158 行),这意味着它include/linux从补丁文件中排除。

*lex.*.c
linux
logo_*.c

那么为什么要dontdiff包含linux?如何保存对补丁文件中标题的更改include/linux?非常感谢。

kernel
  • 1 个回答
  • 25 Views
Martin Hope
A.G
Asked: 2024-07-21 02:10:36 +0800 CST

不同容器中的可执行文件是否共享在同一个公共图像层中定义的共享对象?

  • 7

我正在调查将两个依赖于同一共享对象的进程容器化对内存的影响。我的主要问题是共享对象是否会在内存中加载两次。

这个问题之前已经有人问过了,但是答案并不完整,而且与我的实验相矛盾。我将引用我已经遇到的情况:

共享库的加载和 RAM 的使用--> 对 .so 使用 -fPIC

docker 容器是否共享从同一层但不同映像映射的文件内存的 RAM? --> 是的,但取决于您的设置。您可以通过检查已加载共享对象的设备和 inode id 来证明这一点。没有指示要使用什么设置。

https://stackoverflow.com/questions/35863608/shared-library-in-containers --> 是的,取决于您的存储驱动程序。aufs、overlay 或 overlay2 存储驱动程序支持此功能。

https://stackoverflow.com/questions/63145223/about-loading-dynamic-library-in-container --> 每个容器都是自己的执行单元。不发生共享。与前文相矛盾。

我使用了以下设置:

  • 基础层 --> 包含操作系统和两个共享对象 (G 和 S - 使用 -fPIC 预编译)
  • DependsOnG 层 --> 从基础层开始,包含仅依赖于 G 的可执行文件(预编译)
  • DependsOnGandS 层 --> 从基础层开始,包含依赖于 G 和 S 的可执行文件(预编译)

存储驱动程序:Overlay

下面您可以看到来自 grep glib /proc/PID/maps 的信息。PID 是容器内可执行文件的进程。

| /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 |

如果我正确地解释了结果,那么两个进程将查看完全不同的文件(设备 ID 不同),因此共享对象将在内存中加载两次(似乎与我使用 free 命令看到的一致)。

根据我在网上找到的信息,这种情况不应该发生。

我有以下问题:

  1. 共享对象是否应该仅加载一次?
  2. 覆盖存储驱动程序是否支持此功能?
  3. 我应该以不同的方式构建我的图像/容器吗?(我使用卷而不是公共层进行了相同的实验,并且文件确实是相同的,但这并不是我想要的)

提前致谢!

kernel
  • 2 个回答
  • 109 Views
Martin Hope
melonfsck
Asked: 2024-06-01 21:30:09 +0800 CST

nvidiafb 除法错误 (GT710)

  • 5

我不需要插入nouveau或安装专有驱动程序的“帮助”。问题是关于nvidiafb.谢谢。


我在 Linux 6.9-rc2 上使用 nvidia GT710 GPU。我想nvidiafb为我的旧 GPU 使用简单的驱动程序。在该系统上,我只需要帧缓冲区,不需要其他任何东西(没有 DRI)。但nvidiafb不起作用,它崩溃了。

# 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

到底是什么问题导致它无法与我的 GPU 一起正常工作?处的划分nvGetClocks+0x18f/0x290位于video/fbdev/nvidia/nv_hw.c,可能在这里(第 213 行)。对于这个特定的 GPU(而不是其他较旧的 GPU),除法的除数部分如何最终为零?

谢谢。

kernel
  • 1 个回答
  • 92 Views
Martin Hope
jII
Asked: 2024-05-02 21:58:16 +0800 CST

lshw 的驱动程序名称和内核模块名称有什么区别?

  • 7

使用lshw查询我的 WiFi USB 适配器显示以下内容:

$ 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

适配器工作正常。然而,我很困惑driver=rtw_8822bu。据我所知,我的系统上没有调用内核模型rtw_8822bu.ko,相反,我有rtw88_8822bu.ko,

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

它还显示使用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

问:为什么系统中的内核模块命名时会lshw显示。以前的名字是从哪里来的?driver=rtw_8822burtw88_8822bu

kernel
  • 1 个回答
  • 48 Views
Martin Hope
fschn
Asked: 2024-04-29 00:47:04 +0800 CST

翻译: NixOS 启动USB卡在探测EDD(将edd设置为关闭以禁用)... 确定

  • 5
尝试使用23.11版本的NixOS live USB启动,针对x86_64架构的GNOME,在华硕C236 WSI主板上,该主板的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* 2015年10月21日 5.11 American Megatrends Inc. P1.00 ``` 启动画面在第一行卡住,显示如下信息: ``` 正在探测EDD(禁用edd=off)... 完成 ```
kernel
  • 1 个回答
  • 10 Views
Martin Hope
PICOPress
Asked: 2024-04-08 23:05:45 +0800 CST

512M内存从哪里来?

  • 3

在虚拟机Kali中,我分配了4G内存,像这样;内存状态

但有一个问题。我在来宾上安装了自建内核来破解内存。

# 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

我想看到内存结束的区域,如下所示。 看着记忆

它说内存的大小是16*0x336000字节。然后我用结果推断内存大小(在主机上)。

$ 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

我给了 guest 内存 4G,但根据上面的情况,它有 4.5GiB。交换是1G所以这是废话。

0.5G内存的来源在哪里????

kernel
  • 2 个回答
  • 53 Views

Sidebar

Stats

  • 问题 205573
  • 回答 270741
  • 最佳答案 135370
  • 用户 68524
  • 热门
  • 回答
  • Marko Smith

    模块 i915 可能缺少固件 /lib/firmware/i915/*

    • 3 个回答
  • Marko Smith

    无法获取 jessie backports 存储库

    • 4 个回答
  • Marko Smith

    如何将 GPG 私钥和公钥导出到文件

    • 4 个回答
  • Marko Smith

    我们如何运行存储在变量中的命令?

    • 5 个回答
  • Marko Smith

    如何配置 systemd-resolved 和 systemd-networkd 以使用本地 DNS 服务器来解析本地域和远程 DNS 服务器来解析远程域?

    • 3 个回答
  • Marko Smith

    dist-upgrade 后 Kali Linux 中的 apt-get update 错误 [重复]

    • 2 个回答
  • Marko Smith

    如何从 systemctl 服务日志中查看最新的 x 行

    • 5 个回答
  • Marko Smith

    Nano - 跳转到文件末尾

    • 8 个回答
  • Marko Smith

    grub 错误:你需要先加载内核

    • 4 个回答
  • Marko Smith

    如何下载软件包而不是使用 apt-get 命令安装它?

    • 7 个回答
  • Martin Hope
    user12345 无法获取 jessie backports 存储库 2019-03-27 04:39:28 +0800 CST
  • Martin Hope
    Carl 为什么大多数 systemd 示例都包含 WantedBy=multi-user.target? 2019-03-15 11:49:25 +0800 CST
  • Martin Hope
    rocky 如何将 GPG 私钥和公钥导出到文件 2018-11-16 05:36:15 +0800 CST
  • Martin Hope
    Evan Carroll systemctl 状态显示:“状态:降级” 2018-06-03 18:48:17 +0800 CST
  • Martin Hope
    Tim 我们如何运行存储在变量中的命令? 2018-05-21 04:46:29 +0800 CST
  • Martin Hope
    Ankur S 为什么 /dev/null 是一个文件?为什么它的功能不作为一个简单的程序来实现? 2018-04-17 07:28:04 +0800 CST
  • Martin Hope
    user3191334 如何从 systemctl 服务日志中查看最新的 x 行 2018-02-07 00:14:16 +0800 CST
  • Martin Hope
    Marko Pacak Nano - 跳转到文件末尾 2018-02-01 01:53:03 +0800 CST
  • Martin Hope
    Kidburla 为什么真假这么大? 2018-01-26 12:14:47 +0800 CST
  • Martin Hope
    Christos Baziotis 在一个巨大的(70GB)、一行、文本文件中替换字符串 2017-12-30 06:58:33 +0800 CST

热门标签

linux bash debian shell-script text-processing ubuntu centos shell awk ssh

Explore

  • 主页
  • 问题
    • 最新
    • 热门
  • 标签
  • 帮助

Footer

AskOverflow.Dev

关于我们

  • 关于我们
  • 联系我们

Legal Stuff

  • Privacy Policy

Language

  • Pt
  • Server
  • Unix

© 2023 AskOverflow.DEV All Rights Reserve