Starting udev卡死的问题

最新推荐文章于 2021-05-05 10:59:37 发布
最新推荐文章于 2021-05-05 10:59:37 发布 · 1k 阅读 · 0
文章标签：

#数据库

部署运行你感兴趣的模型镜像

最近公司升级新服务器第硬件，伺机也给自己使用的虚拟系统服务器（VBox+CentOS） 设置为2 个CPU，

 

结果在每次重启服务器的时候杯具了，Starting udev阶段，由于时间有限没有等太长时间，一般几分钟没响应我就reset了。

 

解决方法：degrate！ 将2个CPU降级为单CPU。

 

 

您可能感兴趣的与本文相关的镜像

Stable-Diffusion-3.5

Stable-Diffusion-3.5

图片生成
Stable-Diffusion

Stable Diffusion 3.5 (SD 3.5) 是由 Stability AI 推出的新一代文本到图像生成模型，相比 3.0 版本，它提升了图像质量、运行速度和硬件效率

LVM与Udev的关系分析
LastRitter的专栏
09-12 465
概述 在较新版本（差不多是最近十年）的Linux发新版中，已经广泛使用Udev机制（Udev其实还有很多变种，但基本类似），用于支持设备的热插拔。 ...
redhat5 Starting udev卡死的问题（转载）
zhangmingji的专栏
04-15 792
RHEL5 在VMware Workstation 7中运行时停止在Starting udev的原因 最近在配置多台使用RHEL5 X86_64的虚拟机，由于要做门户开发的实验。发现一个奇怪的现象：VMware中的RHEL5经常停止在Starting udev阶段，由于时间有限没有等太长时间，一般几分钟没响应我就reset了。这时重启几次虚拟机或者修改一下虚拟机的配置，比如改成单cpu单核心...
vmware esxi安装linux启动在Starting udev 停止
weixin_33884611的博客
07-16 528
启动Linux机器，当启动到starting udev停住很久过不去具体解决方法：1.把虚拟机的电源关闭2.然后编辑配置,改为一个CPU3.启动系统4.编辑/etc/grub.conf在kernel一行最后加上clocksource=acpi_pmkernel /vmlinuz-2.6.18-92.el5 ro root=/dev/VolGroup00/LogVol00 ...
linux重起时到starting udev 时就死机
sdfshfh的博客
11-11 3005
linux重起时到starting udev 时就死机
Linux启动停止在Starting udev
weixin_34395205的博客
12-01 1023
转自：http://www.yanduhantan.net.cn/articles/%E5%9C%A8esx4%E4%B8%AD%E8%A3%85redhat-51%E7%9A%84%E6%97%B6%E5%80%99%E5%81%9C%E5%9C%A8starting-udev%E7%9A%84%E9%97%AE%E9%A2%98.html 一、出现问题 在VM...
开机的部分log Welcome to Buildroot 2019.08! [ 1.897088] systemd[1]: Set hostname to <buildroot>. [ 1.911322] systemd[1]: Initializing machine ID from random generator. [ 1.938095] hub 1-1:1.0: USB hub found [ 1.945175] hub 1-1:1.0: 4 ports detected [ 2.265727] usb 1-1.1: new high-speed USB device number 3 using ehci-platform [ 2.286130] systemd[1]: Configuration file /usr/lib/systemd/system/systemd-journald.socket is marked executable. Please remove executable permission bits. Proceeding anyway. [ 2.301862] systemd[1]: Configuration file /usr/lib/systemd/system/systemd-journald.socket is marked world-writable. Please remove world writability permission bits. Proceeding anyway. [ 2.323263] systemd[1]: Configuration file /usr/lib/systemd/system/systemd-journald.service is marked executable. Please remove executable permission bits. Proceeding anyway. [ 2.339083] systemd[1]: Configuration file /usr/lib/systemd/system/systemd-journald.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway. [ 2.357976] systemd[1]: File /usr/lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. [ 2.375630] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.) [ OK ] Reached target Swap. [ OK ] Started Dispatch Password …ts to Console Directory Watch. [ OK ] Reached target Remote File Systems. [ OK ] Listening on Process Core Dump Socket. [ OK ] Created slice system-syslog\x2dng.slice. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on udev Kernel Socket. [ OK ] Created slice User and Session Slice. [ OK ] Listening on Network Service Netlink Socket. [ OK ] Listening on Syslog Socket. [ OK ] Reached target Slices. [ OK ] Listening on udev Control Socket. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Started Forward Password R…uests to Wall Directory Watch. [ OK ] Reached target Paths. [ OK ] Listening on Journal Socket. Starting Journal Service... Starting Remount Root and Kernel File Systems... [ 3.418639] systemd-journald[72]: Configuration file /etc/systemd/journald.conf is marked executable. Please remove executable permission bits. Proceeding anyway. Mounting Kernel Debug File System... [ 3.467024] systemd-journald[72]: Configuration file /etc/systemd/journald.conf is marked world-writable. Please remove world writability permission bits. Proceeding anyway. Mounting Temporary Directory (/tmp)... [ 3.520543] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Starting udev Coldplug all Devices... Mounting Kernel Configuration File System... Starting Apply Kernel Variables... [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Mounted Kernel Debug File System. [ OK ] Mounted Temporary Directory (/tmp). [ OK ] Mounted Kernel Configuration File System. [ OK ] Started Apply Kernel Variables. [ OK ] Started Journal Service. Starting Rebuild Hardware Database... Starting Create System Users... Starting Flush Journal to Persistent Storage... Starting Load/Save Random Seed... [ OK ] Started Create System Users. [ OK ] Started Load/Save Random Seed. [ 4.358833] systemd-journald[72]: Received request to flush runtime journal from PID 1 Starting Create Static Device Nodes in /dev... [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Containers. [ OK ] Reached target Local File Systems. Starting Create Volatile Files and Directories... Starting Rebuild Journal Catalog... [ OK ] Started Create Volatile Files and Directories. Starting Network Time Synchronization... Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Rebuild Journal Catalog. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Network Time Synchronization. [ OK ] Reached target System Time Synchronized. [ OK ] Started udev Coldplug all Devices. [ OK ] Started Rebuild Hardware Database. Starting udev Kernel Device Manager... Starting Update is Completed... [ OK ] Started Update is Completed. [ OK ] Started udev Kernel Device Manager. Starting Network Service... [ OK ] Reached target System Initialization. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting System Logger Daemon "default" instance... [ OK ] Started System Logging Service. [ OK ] Started Console Getty. [ OK ] Started Kernel Log Daemon. Starting Login Service... [ OK ] Started D-Bus System Message Bus. [ OK ] Started Network Service. Starting Network Name Resolution... [ OK ] Started Login Service. [ 12.392540] random: crng init done [ OK ] Started System Logger Daemon "default" instance. [ OK ] Started Network Name Resolution. [ OK ] Found device /dev/ttyS0. Welcome to Buildroot buildroot login: root [ 21.305845] Generic PHY stmmac-0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=stmmac-0:01, irq=POLL) [ 21.392148] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 21.399970] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW Welcome to Buildroot buildroot login: Welcome to Buildroot buildroot login: root
最新发布
07-12
### 问题分析与日志解读 当 Buildroot 配置为使用 systemd 作为初始化系统后，系统在登录界面卡死，通常意味着 systemd 的启动流程未能正确完成，或关键服务未成功启动。根据提供的引用内容和一般调试经验，以下是...
使用VSCode断点精准定位ESP32任务调度异常：实战3步法快速锁定问题根源
这类问题在多核（Dual-Core）并行执行场景下尤为复杂，因任务在CPU0与CPU1间的切换缺乏同步机制，易引发竞态条件。 典型的异常现象包括：IDLE任务长时间运行、预期唤醒任务未进入就绪态、中断服务例程（ISR）延迟过...
多显示器配置异常怎么办？利用441.66驱动诊断Display拓扑问题的4种方法
多显示器配置异常是复杂图形系统中常见的稳定性问题，尤其在使用高性能GPU驱动时更为突出。本文以NVIDIA 441.66驱动为研究对象，系统分析了多显示器拓扑的构建机制及其在实际应用中的故障成因，重点探讨了该版本驱动...
【嵌入式驱动问题定位三板斧】：日志、寄存器、时序数据一键采集的脚本秘籍
嵌入式驱动开发中，问题定位常面临**可见性差、复现难、环境受限**三大挑战。硬件依赖性强、调试接口有限，导致传统gdb难以介入；而问题多发生在特定时序或资源竞争路径下，日志缺失或不完整使得根因追溯困难。 ...
centos 启动的时候卡在了 Starting udev 界面，暂时解决
热门推荐
张拓的博客
07-30 1万+
今天在三汇的atom机器上装elastix，启动的时候卡在了  Starting udev 界面 用单用户模式启动没有问题 解决方法： 用单用户模式启动 vi /boot/grub/grub.conf  title My Call Center-base
[转]Vmware ESX 4上虚拟机 Redhat 5.2（CentOS 5.2）启动在Starting udev 停几个小时
weixin_33785108的博客
02-04 189
转自：http://hi.baidu.com/wa0362/blog/item/efa5dfc2af42973ee4dd3b45.html   最近在vmware ESX上安装的Redhat 5.2或者CentOS 5.2基本上都碰到了这个问题 安装完全完成后启动是在Starting udev会需要几个小时才能过去。 网上找到很多说法比方有说让改"/etc/udev/rules.d/99-...
虚拟机安装Redhat 5企业版卡在starting udev：
11-16 1584
安装RHEL5.1-Server-20071017.0-i386-DVD时有一定概率会卡在starting udev：处，系统比较久不能较好的识别新硬件，将虚拟机设置为单核单线程cpu即可继续安装
linux系统无法启动 udev,centos到了starting udev就进不去了！
weixin_39980575的博客
05-05 1269
helitrope 于 2011-03-08 18:44:11发表:我用光盘update了一下系统，结果问题解决了，但是不知道原因在哪里？今天我用rpm －Va查看了一下损坏的文件，如下所示：[root@localhost xiao]# rpm -Va.......T c /etc/logrotate.d/syslogS.5....T c /root/.bashrc..5....T c /...
(转)vmware esxi 4.1 安装linux 启动在Starting udev 停止
老王
09-06 464
具体解决方法： 当starting udev停住很久过不去的时候就(1)把虚拟机的电源关闭，(2)然后编辑配置,改为单个vCPU(3)启动系统 （4）编辑/etc/grub.conf在kernel一行最后加上clocksource=acpi_pm   参考 http://hi.baidu.com/wa0362/blog/item/efa5dfc2af42973ee4dd3b45.htm...
starting udev :BUG :unable to handle kernel ----fedora9安装在hp pro3000 时报错
ctinglx的专栏
03-02 1315
<br />想在hp pro 3000 上面安装fedora9 但安装是老是出错，安装前要在bios把网卡禁用才能安装，但每次在bios启用网卡时都会出错，<br />原因是网卡模块加载时出错，<br />解决办法：在/lib/modules/2.6.25-14.fc9.i686 下的modules.dep 下把r8169.ko 替换掉（前提是有可替换的，因为以前的机器是装红旗系统的，进去找到），重启，好了，不会在提示starting udev :BUG :unable to handle kernel 。
Linux设备管理：深度探索udev
"掌握udev是关于Linux设备管理的重要概念，它是一个用户空间程序，用于动态管理设备文件，解决了早期Linux设备管理中的不确定性、设备映射问题和设备号限制。" 在Linux系统中，udev是用于管理和控制设备文件的核心...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值