我在 dmesg 中遇到此错误

“虚假的 8259A 中断：IRQ7。”

我已经尝试过这些解决方案

通过 grub 禁用 iommu

在 bios 中禁用 iommu

根本不起作用

有谁知道更多吗？谢谢

系统是

华硕 Pro B550M-C

CPU 是 AMD Ryzen 3 3200G，配备 Radeon Vega Graphics

内存 64GB

磁盘是 raid 中的串行 ata (zfs)

发行版是 Debian 12

内核是 6.1.0-28-amd64

系统运行正常，什么都没发生，我只想知道是否有可能“解决”这个消息

编辑1

cat /proc/interrupts 报告此问题

   5:          0          0          0          0  IR-IO-APIC    5-edge      parport0
   7:          0          0          0          2  IR-IO-APIC    7-fasteoi   pinctrl_amd

这行关于虚假中断

 SPU:          0          0          0          0   Spurious interrupts

我已经使用 Pop!_OS 一段时间了，最​​近买了蓝牙耳机。它安装在没有集成蓝牙的台式电脑上。我买了一个据说不错的蓝牙适配器。

蓝牙可以识别我的 Nintendo Wii U Pro 控制器，而之前的加密狗则无法识别，但无法识别耳机。

启动 Windows 时，它可以识别两个外围设备，并且都能正常工作。

最后，我设置了一个可启动的 Pop!_OS 闪存驱动器并进入实时会话。结果发现两个设备都被检测到并且运行正常。不过，在我的 Pop!_OS 安装中，我使用的是 Cinnamon DE。

我应该做些什么？

我的规格：

这是有人让我尝试的一些蓝牙相关控制台命令的输出：

Jun 22 06:22:56 pop-os kernel: usb 1-5: Product: Bluetooth 5.3 Radio
Jun 22 06:22:57 pop-os kernel: Bluetooth: Core ver 2.22
Jun 22 06:22:57 pop-os kernel: NET: Registered PF_BLUETOOTH protocol family
Jun 22 06:22:57 pop-os kernel: Bluetooth: HCI device and connection manager initialized
Jun 22 06:22:57 pop-os kernel: Bluetooth: HCI socket layer initialized
Jun 22 06:22:57 pop-os kernel: Bluetooth: L2CAP socket layer initialized
Jun 22 06:22:57 pop-os kernel: Bluetooth: SCO socket layer initialized
Jun 22 06:22:57 pop-os kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Jun 22 06:22:57 pop-os kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Jun 22 06:22:57 pop-os kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
Jun 22 06:22:57 pop-os kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
Jun 22 06:22:57 pop-os kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
Jun 22 06:22:57 pop-os systemd[1]: Starting Bluetooth management mechanism...
Jun 22 06:22:57 pop-os systemd[1]: Starting Bluetooth service...
Jun 22 06:22:57 pop-os bluetoothd[920]: Bluetooth daemon 5.64
Jun 22 06:22:57 pop-os systemd[1]: Started Bluetooth service.
Jun 22 06:22:57 pop-os systemd[1]: Reached target Bluetooth Support.
Jun 22 06:22:57 pop-os bluetoothd[920]: Bluetooth management interface 1.22 initialized
Jun 22 06:22:57 pop-os kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jun 22 06:22:57 pop-os kernel: Bluetooth: BNEP filters: protocol multicast
Jun 22 06:22:57 pop-os kernel: Bluetooth: BNEP socket layer initialized
Jun 22 06:22:57 pop-os NetworkManager[912]: <info>  [1719030177.5407] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-bluetooth.so)
Jun 22 06:22:57 pop-os systemd[1]: Started Bluetooth management mechanism.
Jun 22 06:22:57 pop-os kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
Jun 22 06:22:58 pop-os kernel: Bluetooth: MGMT ver 1.22
Jun 22 06:23:00 pop-os kernel: Bluetooth: RFCOMM TTY layer initialized
Jun 22 06:23:00 pop-os kernel: Bluetooth: RFCOMM socket layer initialized
Jun 22 06:23:00 pop-os kernel: Bluetooth: RFCOMM ver 1.11
Jun 22 14:23:17 pop-os kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Jun 22 14:23:17 pop-os kernel: Bluetooth: hci0: Opcode 0x0c24 failed: -110
Jun 22 14:23:19 pop-os kernel: Bluetooth: hci0: Opcode 0x0c24 failed: -110
Jun 22 14:23:19 pop-os kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Jun 22 14:23:21 pop-os kernel: Bluetooth: hci0: Opcode 0x0c24 failed: -110
Jun 22 14:23:21 pop-os kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Jun 22 14:23:28 pop-os systemd[1]: blueman-mechanism.service: Deactivated successfully.
Jun 22 14:24:52 pop-os systemd[3053]: Starting Bluetooth management applet...
Jun 22 14:24:52 pop-os systemd[1]: Starting Bluetooth management mechanism...
Jun 22 14:24:53 pop-os systemd[1]: Started Bluetooth management mechanism.
Jun 22 14:24:53 pop-os blueman-applet[7494]: blueman-applet 14.24.53 WARNING  PluginManager:147 __load_plugin: Not loading DhcpClient because its conflict has higher priority
Jun 22 14:24:53 pop-os blueman-applet[7494]: blueman-applet 14.24.53 WARNING  PluginManager:147 __load_plugin: Not loading PPPSupport because its conflict has higher priority
Jun 22 14:24:53 pop-os systemd[3053]: Started Bluetooth management applet.
Jun 22 14:24:53 pop-os systemd[3053]: Starting Bluetooth OBEX service...
Jun 22 14:24:53 pop-os systemd[3053]: Started Bluetooth OBEX service.
Jun 22 14:25:23 pop-os systemd[1]: blueman-mechanism.service: Deactivated successfully.
Jun 22 14:28:57 pop-os systemd[3053]: Reached target Bluetooth.
Jun 22 14:28:59 pop-os kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Jun 22 14:28:59 pop-os kernel: Bluetooth: HIDP socket layer initialized
Jun 22 14:28:59 pop-os kernel: wiimote 0005:057E:0330.0005: hidraw4: BLUETOOTH HID v0.01 Gamepad [Nintendo RVL-CNT-01-UC] on 8a:88:4b:80:c2:34
Jun 22 14:28:59 pop-os kernel: input: Nintendo Wii Remote Pro Controller as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-5/1-5:1.0/bluetooth/hci0/hci0:2/0005:057E:0330.0005/input/input21
Jun 22 14:29:00 pop-os upowerd[1082]: treated changed event as add on /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-5/1-5:1.0/bluetooth/hci0/hci0:2/0005:057E:0330.0005/power_supply/wiimote_battery_8c:cd:e8:c0:5d:8d
Jun 22 14:30:46 pop-os bluetoothd[920]: src/agent.c:pincode_reply() Agent /org/bluez/agent/blueman replied with an error: org.freedesktop.DBus.Error.NoReply, Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jun 22 16:56:36 pop-os systemd[3053]: Stopped target Bluetooth.
Jun 22 16:56:36 pop-os systemd[1]: Stopped target Bluetooth Support.
Jun 22 16:56:36 pop-os blueman-applet[7494]: blueman-applet 16.56.36 WARNING  DiscvManager:119 update_menuitems: warning: Adapter is None
Jun 22 16:56:41 pop-os kernel: usb 3-2: Product: Bluetooth 5.3 Radio
Jun 22 16:56:41 pop-os kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Jun 22 16:56:41 pop-os kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Jun 22 16:56:41 pop-os kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
Jun 22 16:56:41 pop-os kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
Jun 22 16:56:41 pop-os kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
Jun 22 16:56:41 pop-os systemd[3053]: Reached target Bluetooth.
Jun 22 16:56:41 pop-os systemd[1]: Reached target Bluetooth Support.
Jun 22 16:56:42 pop-os kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
Jun 22 16:56:42 pop-os kernel: Bluetooth: MGMT ver 1.22
Jun 22 16:56:42 pop-os blueman-applet[7494]: blueman-applet 16.56.42 WARNING  PowerManager:202 on_adapter_property_changed: adapter powered on while in off state, turning bluetooth on
Jun 22 16:56:42 pop-os systemd[1]: Starting Bluetooth management mechanism...
Jun 22 16:56:42 pop-os systemd[1]: Started Bluetooth management mechanism.
Jun 22 16:56:57 pop-os kernel: Bluetooth: hci0: command 0x2005 tx timeout
Jun 22 16:56:57 pop-os kernel: Bluetooth: hci0: Opcode 0x2005 failed: -110
Jun 22 16:56:59 pop-os kernel: Bluetooth: hci0: command 0x2041 tx timeout
Jun 22 16:56:59 pop-os kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
Jun 22 16:57:12 pop-os systemd[1]: blueman-mechanism.service: Deactivated successfully.
Jun 22 17:30:54 pop-os sudo[18184]: davidspira : TTY=pts/0 ; PWD=/home/davidspira ; USER=root ; COMMAND=/usr/bin/journalctl -b -g blue

使用 ACPI 接口，可以获得有关电池寿命的信息。这些信息从何而来？

有没有通过电源插头上的电流积分来计算能力的芯片？这是将电压转换为容量的电池芯片吗？

有时我想检查我使用的硬件组件的确切型号。我真的不关心极端的细节，比如他们在主板上 xyz 位置使用什么品牌的电容器。我只想知道我的主板、内存、视频卡等的确切型号，通常是因为我想购买兼容的硬件或寻找驱动程序。所以基本上我所需要的只是每个重要的硬件一行，显示几乎盒子上说的它进来的内容。

我如何在 Linux 中从命令行执行此操作？

我试过的：

• neofetch是我发现的最好的东西，但它只显示 CPU 和 GPU。它没有说明内存型号或频率、硬盘型号或主板型号。
• lshw打印出 517 行乱码，我永远无法从中看出正反面。这显然是某种技术工具，而不是为那些只想知道他们拥有什么型号的硬件并且懒得打开机箱并用手电筒查看内部的人准备的。

我已经连接了一个旧的 pci buslogic SCSI（我需要进行逆向计算实验）

lspci说

06:06.0 Non-VGA unclassified device [0000]: BusLogic Device [104b:0150]

未加载驱动程序，未识别磁盘。它有故障吗？

我曾尝试使用带 hdmi 端口的集线器连接到我电脑的 USB-C 端口，但这个集线器不起作用。

检查 Internet（和此处）上的其他类似线程，我发现问题可能是相关的 USB-C 端口不支持视频输出（集线器本身有 USB 端口并且它们工作正常）。

那么有没有办法从我的电脑上展示它以保持冷静？我只能使用制造商的文档进行检查吗？

欲了解更多信息：

lsusb -t连接轮毂前：

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 7: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 7: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 7: Dev 2, If 2, Class=Video, Driver=uvcvideo, 480M
    |__ Port 7: Dev 2, If 3, Class=Video, Driver=uvcvideo, 480M
    |__ Port 10: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 10: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M

lsusb -t集线器连接后：

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M
    |__ Port 3: Dev 8, If 0, Class=Hub, Driver=hub/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 7: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 7: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 7: Dev 2, If 2, Class=Video, Driver=uvcvideo, 480M
    |__ Port 7: Dev 2, If 3, Class=Video, Driver=uvcvideo, 480M
    |__ Port 8: Dev 41, If 0, Class=Hub, Driver=hub/5p, 480M
    |__ Port 10: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 10: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M

xrander集线器连接前后的输出：

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 310mm x 170m
   1920x1080     60.01*+  59.93
   1680x1050     59.95    59.88
   1400x1050     59.98
   1600x900      60.00    59.95    59.82
   1280x1024     60.02
   1400x900      59.96    59.88
   1280x960      60.00
   1368x768      60.00    59.88    59.85
   1280x800      59.81    59.91
   1280x720      59.86    60.00    59.74
   1024x768      60.00
   1024x576      60.00    59.90    59.82
   960x540       60.00    59.63    59.82
   800x600       60.32    56.25
   864x486       60.00    59.92    59.57
   640x480       59.94
   720x405       59.51    60.00    58.99
   640x360       59.84    59.32    60.00
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

并xrandr在 HDMI 端口显示器连接后：

Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 310mm x 170mm
   1920x1080     60.01*+  59.93
   1680x1050     59.95    59.88
   1400x1050     59.98
   1600x900      60.00    59.95    59.82
   1280x1024     60.02
   1400x900      59.96    59.88
   1280x960      60.00
   1368x768      60.00    59.88    59.85
   1280x800      59.81    59.91
   1280x720      59.86    60.00    59.74
   1024x768      60.00
   1024x576      60.00    59.90    59.82
   960x540       60.00    59.63    59.82
   800x600       60.32    56.25
   864x486       60.00    59.92    59.57
   640x480       59.94
   720x405       59.51    60.00    58.99
   640x360       59.84    59.32    60.00
HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm
   1920x1080     60.00*+  50.00    59.94
   1680x1050     59.88
   1600x900      60.00
   1280x1024     60.02
   1440x900      59.90
   1280x800      59.91
   1280x720      60.00    50.00    59.94
   1024x768      60.00
   800x600       60.32
   720x576       50.00
   720x480       60.00    59.94
   640x480       60.00    59.94
   720x400       70.08
VIRTUAL1 disconnected (normal left inverted right x axis y axis) 

这个命令：

badblocks -svn /dev/sda

它有什么作用？它只是报告坏块吗？或者它是否以某种方式处理坏块，这样我就不必担心它们？

我阅读了手册man badblocks，但我没有得到-n选项：

       -s     Show  the  progress  of the scan by writing out rough percentage completion of
              the current badblocks pass over the disk.  Note that badblocks may do multiple
              test  passes  over the disk, in particular if the -p or -w option is requested
              by the user.


       -v     Verbose mode.  Will write the number of read errors, write  errors  and  data-
              corruptions to stderr.


       -n     Use  non-destructive read-write mode.  By default only a non-destructive read-
              only test is done.  This option must not be combined with the  -w  option,  as
              they are mutually exclusive.

badblocks -svn /dev/sda持续了将近两天的运行输出：

更新

一些帖子建议在运行后badblocks -svn /dev/sda，硬盘控制器会处理坏块。没有把握。

让硬盘控制器用备用块替换坏块。

https://askubuntu.com/a/490552/507217

如果您以这种方式完全处理了磁盘，则磁盘控制器应该已将所有坏块替换为工作块，并且重新分配的计数将在 SMART 日志中增加。

https://askubuntu.com/a/490549/507217

聪明的

badblocks运行命令后，我通过以下方式检查了 SMART 表：

smartctl --all /dev/sda

请注意，Current_Pending_Sector原始值为56. 28是报道的两倍badblocks。也许他们是相关的。

错误解释

根据这个：

如何解释坏块输出

badblocks错误日志的格式为reading/writing/comparing. 就我而言，所有28错误都是阅读错误。这意味着没有应用程序可以读取这些块。

操作系统日志

我查看了操作系统日志sudo journalctl -xe。实际上，SMART 会抛出有关这些56坏扇区（28坏块）的错误：

smartd [1243]：设备：/dev/sda [SAT]，56 当前不可读（待处理）扇区

结论

我宁愿在为时已晚之前备份数据并更换硬盘。

如果我安装 Kindle（在我的 Ubuntu 机器上），它会显示与书籍、元数据等相关的各种文件和数据库。

但是我没有看到实际的操作系统及其文件——我是看到它们却没有意识到，还是以某种方式隐藏了它们？如何访问实际的操作系统？

（我要找的是日志文件。上次更新搞砸了我的设备，我希望在某个地方有以前固件版本的记录，这样我就可以回滚了。）

我有一台运行 Ubuntu 的 B450 Tomahawk Max，我下载了这个程序 来控制内置的 LED 灯。当我尝试显示纯色时，它会打开和关闭。

例如， sudo ./target/release/msi-rgb 00000000 00000000 FFFFFFFF -ir -ig -ib 将使 LED 发出蓝色脉冲，而不是像预期的那样显示纯蓝色。

如何使 LED 显示纯色？是否可以通过msi-rgb，或者我需要使用不同的程序？

我正在尝试确定我的 CPU 的 Vcor​​e 电压，但失败了。我的 CPU 是华擎 570M Pro主板中的 Ryzen 3700X，使用 Arch Linux（完全更新）。

我下载了lm_sensors包，运行sensors-detect并接受了所有扫描，然后运行watch sensors​​. 当 CPU 空闲且仅运行终端时，我的输出附在下面。

在负载下，唯一变化的电压值是 in0，最高可达 720 mV（在一个内核上 100%）。一些在线指南建议 in0 通常是 Vcor​​e，但是对于这里的情况来说，它太低了。3700X 的正常工作电压介于 0.2 V 和 1.5 V 之间，当单核在最大负载下升压时会达到后者。（根据我的测试，温度和风扇速度看起来是正确的。）

我该怎么做才能正确读取我的 Vcor​​e？谢谢你。

amdgpu-pci-0800
Adapter: PCI adapter
vddgfx:        1.11 V  
fan1:        1471 RPM  (min =    0 RPM, max = 4100 RPM)
edge:         +27.0°C  (crit = +91.0°C, hyst = -273.1°C)
power1:       47.25 W  (cap = 180.00 W)

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +29.8°C  (high = +70.0°C)
Tctl:         +29.8°C  

nct6798-isa-0290
Adapter: ISA adapter
in0:                    96.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                     1.66 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                     3.46 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                     3.33 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                     1.83 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                     1.10 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                     1.20 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                     3.46 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                     3.28 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                     1.66 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                    1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                  624.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                    1.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                  928.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                  904.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                   895 RPM  (min =    0 RPM)
fan2:                  1023 RPM  (min =    0 RPM)
fan3:                   752 RPM  (min =    0 RPM)
fan4:                   629 RPM  (min =    0 RPM)
fan5:                     0 RPM  (min =    0 RPM)
fan6:                  3161 RPM  (min =    0 RPM)
fan7:                     0 RPM  (min =    0 RPM)
SYSTIN:                 +30.0°C  (high = +105.0°C, hyst = +95.0°C)  sensor = thermistor
CPUTIN:                 +26.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                +15.0°C    sensor = thermistor
AUXTIN1:                -61.0°C    sensor = thermistor
AUXTIN2:                +13.0°C    sensor = thermistor
AUXTIN3:                +31.0°C    sensor = thermistor
SMBUSMASTER 1:          +51.0°C  (high = +105.0°C, hyst = +95.0°C)
SMBUSMASTER 0:          +29.5°C  
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled