Kubuntu 随机崩溃(Kali 也是如此)

Kubuntu 随机崩溃(Kali 也是如此)

我安装了 Kubuntu,然后又卸载了它,因为我注意到它有时会冻结,每次都必须重新启动。我想我的发行版可能有问题,所以我安装了 Kali。仍然有同样的问题。我不知道如何调试这个。

这是我在重新启动之前收到的堆栈错误journalctl --no-pager -b -p err

juil. 22 20:50:54 pc-240 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20221020/psobject-22>
juil. 22 20:50:54 pc-240 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS06._>
juil. 22 20:50:54 pc-240 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20221020/psobject-22>
juil. 22 20:51:03 pc-240 lightdm[1025]: gkr-pam: unable to locate daemon control file
juil. 22 20:51:03 pc-240 lightdm[901]: pam_systemd(lightdm-greeter:session): Failed to release session: Transpor>

这是崩溃前 syslog 的日志:

2023-07-23T01:32:35.831810+02:00 pc-240 systemd[1112]: Closed pipewire.socket - PipeWire Multimedia System Socket.
2023-07-23T01:32:35.831961+02:00 pc-240 systemd[1112]: Removed slice app.slice - User Application Slice.
2023-07-23T01:32:35.832016+02:00 pc-240 systemd[1112]: Reached target shutdown.target - Shutdown.
2023-07-23T01:32:35.832075+02:00 pc-240 systemd[1112]: Finished systemd-exit.service - Exit the Session.
2023-07-23T01:32:35.832135+02:00 pc-240 systemd[1112]: Reached target exit.target - Exit the Session.
2023-07-23T01:32:35.867762+02:00 pc-240 systemd[1]: [email protected]: Deactivated successfully.
2023-07-23T01:32:35.868273+02:00 pc-240 systemd[1]: Stopped [email protected] - User Manager for UID 125.
2023-07-23T01:32:35.900913+02:00 pc-240 systemd[1]: Stopping [email protected] - User Runtime Directory /run/user/125...
2023-07-23T01:32:35.905911+02:00 pc-240 systemd[1]: run-user-125.mount: Deactivated successfully.
2023-07-23T01:32:35.906538+02:00 pc-240 systemd[1]: [email protected]: Deactivated successfully.
2023-07-23T01:32:35.906689+02:00 pc-240 systemd[1]: Stopped [email protected] - User Runtime Directory /run/user/125.
2023-07-23T01:32:35.907612+02:00 pc-240 systemd[1]: Removed slice user-125.slice - User Slice of UID 125.
2023-07-23T01:32:35.907695+02:00 pc-240 systemd[1]: user-125.slice: Consumed 1.698s CPU time.
2023-07-23T01:32:36.028045+02:00 pc-240 rtkit-daemon[1135]: Supervising 7 threads of 4 processes of 2 users.
2023-07-23T01:32:36.028352+02:00 pc-240 rtkit-daemon[1135]: Supervising 7 threads of 4 processes of 2 users.
2023-07-23T01:32:36.048529+02:00 pc-240 rtkit-daemon[1135]: Supervising 7 threads of 4 processes of 2 users.
2023-07-23T01:32:36.048876+02:00 pc-240 rtkit-daemon[1135]: Supervising 7 threads of 4 processes of 2 users.
2023-07-23T01:32:36.049688+02:00 pc-240 rtkit-daemon[1135]: Supervising 7 threads of 4 processes of 2 users.
2023-07-23T01:32:36.050021+02:00 pc-240 rtkit-daemon[1135]: Supervising 7 threads of 4 processes of 2 users.
2023-07-23T01:32:36.073019+02:00 pc-240 rtkit-daemon[1135]: Successfully made thread 2200 of process 1961 owned by '1000' RT at priority 10.
2023-07-23T01:32:36.073102+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:36.435551+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:36.435834+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:37.067011+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:37.067334+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:37.073361+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:37.073794+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:37.081884+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:37.082252+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:39.278087+02:00 pc-240 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
2023-07-23T01:32:41.636986+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:41.637263+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 2 users.
2023-07-23T01:32:44.193245+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 1 users.
2023-07-23T01:32:44.193456+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 1 users.
2023-07-23T01:32:49.077356+02:00 pc-240 systemd[1]: systemd-fsckd.service: Deactivated successfully.
2023-07-23T01:32:50.403618+02:00 pc-240 systemd-timesyncd[887]: Contacted time server [2a01:b740:a20:4000::1f2]:123 (2.debian.pool.ntp.org).
2023-07-23T01:32:50.404114+02:00 pc-240 systemd-timesyncd[887]: Initial clock synchronization to Sun 2023-07-23 01:32:50.402305 CEST.
2023-07-23T01:32:50.880368+02:00 pc-240 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
2023-07-23T01:32:53.130602+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 1 users.
2023-07-23T01:32:53.130929+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 1 users.
2023-07-23T01:32:53.132649+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 1 users.
2023-07-23T01:32:53.133110+02:00 pc-240 rtkit-daemon[1135]: Supervising 8 threads of 5 processes of 1 users.
2023-07-23T01:32:53.159458+02:00 pc-240 rtkit-daemon[1135]: Successfully made thread 2713 of process 2295 owned by '1000' RT at priority 10.
2023-07-23T01:32:53.159551+02:00 pc-240 rtkit-daemon[1135]: Supervising 9 threads of 6 processes of 1 users.
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@2023-07-23T08:4

我正在使用:

Distributor ID: Kali
Description:    Kali GNU/Linux Rolling
Release:        2023.2
Codename:       kali-rolling

这些是我的分区:

Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10SPZX-80Z
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: C45E29FA-75DD-46C8-AF15-B64B7A5A7CD3

Device     Start        End    Sectors   Size Type
/dev/sda1   2048 1953523711 1953521664 931,5G Microsoft basic data


Disk /dev/sdb: 119,24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: KINGSTON RBUSNS8
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 908CCCBC-7544-495F-81A3-195BE53BCE0A

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048   1050623   1048576   512M EFI System
/dev/sdb2    1050624 248068095 247017472 117,8G Linux filesystem
/dev/sdb3  248068096 250068991   2000896   977M Linux swap

请注意,我以前使用的是 Windows,但出现蓝屏错误。我通过修改注册表中的一些内容解决了这个问题。我去了

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

并将StartDWORD 值设置为 4(默认为 3)。

答案1

快速搜索显示 Windows 上的英特尔电源管理 (intelppm.sys) 存在问题;
该组件与硬件严格相关;

正如我已经在 OP 下评论过的那样,acpi=off可以解决这个问题,但正如你稍后所说,它将 CPU 核心限制为一个;
另一个修复,是禁用或限制 BIOS/UEFI 固件的电源管理(我们不知道您拥有什么机器/硬件,但体面的制造商也允许您或多或少地微调此设置);

第二个可能是由于性能受到影响而临时修复(如前一个),同时您可以寻找合适的解决方案(如果存在)或等待可以帮助您的更新的内核版本;

注意:电源管理是内核(Linux 和 Windows)的一个微妙的方面,因为它与硬件、固件和软件联系在一起:我建议您深入搜索 Linux 上的类似问题,并打开内核错误报告(如果尚不存在)。

答案2

我的投票赞成noacpiacpi=no在线Linuxgrub这些是等效的模块指令。因此,当grub出现时,点击e进行编辑。转到Kernel标记为 的行Linux。删除quiet,这样您就可以看到启动时发生了什么。

输入你的acpi命令,看看事情进展如何。如果顺利,请转到/etc/default/grub并将设置永久化。当然,里面没有任何东西Kali是它应该在的地方,所以你可能需要寻找一下。

我不使用 Kali,因为它不是桌面操作系统,而是渗透测试仪。

相关内容