Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

9. Known Issues

9.1. All Architectures
复制链接

  • 当​​​​​​​使​​​​​​​用​​​​​​​新​​​​​​​的​​​​​​​磁​​​​​​​盘​​​​​​​加​​​​​​​密​​​​​​​特​​​​​​​性​​​​​​​对​​​​​​​根​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​进​​​​​​​行​​​​​​​加​​​​​​​密​​​​​​​时​​​​​​​，您​​​​​​​将​​​​​​​在​​​​​​​关​​​​​​​系​​​​​​​系​​​​​​​统​​​​​​​时​​​​​​​在​​​​​​​控​​​​​​​制​​​​​​​台​​​​​​​看​​​​​​​到​​​​​​​以​​​​​​​下​​​​​​​出​​​​​​​错​​​​​​​信​​​​​​​息​​​​​​​： 
    Stopping disk encryption [FAILED]
    Copy to Clipboard Toggle word wrap
    可​​​​​​​完​​​​​​​全​​​​​​​忽​​​​​​​略​​​​​​​此​​​​​​​信​​​​​​​息​​​​​​​，会​​​​​​​成​​​​​​​功​​​​​​​完​​​​​​​成​​​​​​​关​​​​​​​闭​​​​​​​进​​​​​​​程​​​​​​​。​​​​​​​
  • When using an encrypted device, the following error message may be reported during bootup: 
    insmod: error inserting '/lib/aes_generic.ko': -1 File exists
    Copy to Clipboard Toggle word wrap
    This message can safely be ignored.
  • 在​​​​​​​多​​​​​​​路​​​​​​​径​​​​​​​顶​​​​​​​部​​​​​​​使​​​​​​​用​​​​​​​多​​​​​​​设​​​​​​​备​​​​​​​（MD）阵​​​​​​​列​​​​​​​安​​​​​​​装​​​​​​​将​​​​​​​导​​​​​​​致​​​​​​​机​​​​​​​器​​​​​​​无​​​​​​​法​​​​​​​引​​​​​​​导​​​​​​​。​​​​​​​对​​​​​​​内​​​​​​​部​​​​​​​提​​​​​​​供​​​​​​​阵​​​​​​​列​​​​​​​的​​​​​​​储​​​​​​​存​​​​​​​区​​​​​​​域​​​​​​​网​​​​​​​络​​​​​​​（SAN）设​​​​​​​备​​​​​​​没​​​​​​​有​​​​​​​影​​​​​​​响​​​​​​​。​​​​​​​
  • When a large number of LUNs are added to a node, multipath can significantly increase the time it takes for udev to create device nodes for them. If you experience this problem, you can correct it by deleting the following line in /etc/udev/rules.d/40-multipath.rules: 
    KERNEL!="dm-[0-9]*", ACTION=="add", PROGRAM=="/bin/bash -c '/sbin/lsmod | /bin/grep ^dm_multipath'", RUN+="/sbin/multipath -v0 %M:%m"
    Copy to Clipboard Toggle word wrap
    This line causes udev to run multipath every time a block device is added to the node. Even with this line removed, multipathd will still automatically create multipath devices, and multipath will still be called during the boot process, for nodes with multipathed root filesystems. The only change is that multipath devices will not be automatically created when multipathd is not running, which should not be a problem for the vast majority of multipath users.
  • 当​​​​​​​您​​​​​​​从​​​​​​​红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 5.3 以​​​​​​​前​​​​​​​的​​​​​​​版​​​​​​​本​​​​​​​升​​​​​​​级​​​​​​​时​​​​​​​，您​​​​​​​可​​​​​​​能​​​​​​​遇​​​​​​​到​​​​​​​以​​​​​​​下​​​​​​​错​​​​​​​误​​​​​​​： 
    Updating  : mypackage                 ################### [ 472/1655]
rpmdb: unable to lock mutex: Invalid argument
    Copy to Clipboard Toggle word wrap
    导​​​​​​​致​​​​​​​锁​​​​​​​定​​​​​​​问​​​​​​​题​​​​​​​的​​​​​​​原​​​​​​​因​​​​​​​是​​​​​​​ glibc 中​​​​​​​的​​​​​​​共​​​​​​​享​​​​​​​ futex 锁​​​​​​​定​​​​​​​在​​​​​​​ 5.2 和​​​​​​​ 5.3 的​​​​​​​ futex 中​​​​​​​进​​​​​​​行​​​​​​​了​​​​​​​改​​​​​​​进​​​​​​​。​​​​​​​因​​​​​​​此​​​​​​​根​​​​​​​据​​​​​​​ 5.2 glibc 运​​​​​​​行​​​​​​​的​​​​​​​程​​​​​​​序​​​​​​​则​​​​​​​无​​​​​​​法​​​​​​​根​​​​​​​据​​​​​​​以​​​​​​​ 5.3 glibc 为​​​​​​​基​​​​​​​础​​​​​​​运​​​​​​​行​​​​​​​的​​​​​​​程​​​​​​​序​​​​​​​正​​​​​​​常​​​​​​​执​​​​​​​行​​​​​​​共​​​​​​​享​​​​​​​ futex 锁​​​​​​​定​​​​​​​。​​​​​​​
    这​​​​​​​个​​​​​​​特​​​​​​​定​​​​​​​出​​​​​​​错​​​​​​​信​​​​​​​息​​​​​​​是​​​​​​​某​​​​​​​个​​​​​​​软​​​​​​​件​​​​​​​包​​​​​​​调​​​​​​​用​​​​​​​ rpm 作​​​​​​​为​​​​​​​其​​​​​​​安​​​​​​​装​​​​​​​脚​​​​​​​本​​​​​​​一​​​​​​​部​​​​​​​分​​​​​​​的​​​​​​​副​​​​​​​作​​​​​​​用​​​​​​​。​​​​​​​该​​​​​​​执​​​​​​​行​​​​​​​升​​​​​​​级​​​​​​​的​​​​​​​ rpm 事​​​​​​​件​​​​​​​在​​​​​​​整​​​​​​​个​​​​​​​升​​​​​​​级​​​​​​​过​​​​​​​程​​​​​​​中​​​​​​​使​​​​​​​用​​​​​​​以​​​​​​​前​​​​​​​的​​​​​​​ glibc，但​​​​​​​脚​​​​​​​本​​​​​​​中​​​​​​​启​​​​​​​动​​​​​​​ rpm 事​​​​​​​件​​​​​​​的​​​​​​​是​​​​​​​新​​​​​​​的​​​​​​​ glibc。​​​​​​​
    To avoid this error, upgrade glibc first in a separate run: 
    # yum update glibc
# yum update
    Copy to Clipboard Toggle word wrap
    You will also see this error if you downgrade glibc to an earlier version on an installed 5.3 system.
  • 红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 5 中​​​​​​​的​​​​​​​ mvapich 和​​​​​​​ mvapich2 被​​​​​​​编​​​​​​​译​​​​​​​为​​​​​​​只​​​​​​​支​​​​​​​持​​​​​​​ InfiniBand/iWARP 互​​​​​​​联​​​​​​​。​​​​​​​因​​​​​​​此​​​​​​​它​​​​​​​们​​​​​​​不​​​​​​​会​​​​​​​在​​​​​​​以​​​​​​​太​​​​​​​网​​​​​​​或​​​​​​​者​​​​​​​其​​​​​​​它​​​​​​​网​​​​​​​络​​​​​​​互​​​​​​​联​​​​​​​运​​​​​​​行​​​​​​​。​​​​​​​
  • 一​​​​​​​个​​​​​​​系​​​​​​​统​​​​​​​中​​​​​​​如​​​​​​​果​​​​​​​有​​​​​​​两​​​​​​​个​​​​​​​以​​​​​​​上​​​​​​​的​​​​​​​加​​​​​​​密​​​​​​​块​​​​​​​设​​​​​​​备​​​​​​​，anaconda 有​​​​​​​一​​​​​​​个​​​​​​​选​​​​​​​项​​​​​​​可​​​​​​​通​​​​​​​过​​​​​​​全​​​​​​​局​​​​​​​密​​​​​​​码​​​​​​​短​​​​​​​语​​​​​​​，但​​​​​​​初​​​​​​​始​​​​​​​化​​​​​​​脚​​​​​​​本​​​​​​​不​​​​​​​支​​​​​​​持​​​​​​​此​​​​​​​特​​​​​​​性​​​​​​​。​​​​​​​当​​​​​​​引​​​​​​​导​​​​​​​该​​​​​​​系​​​​​​​统​​​​​​​时​​​​​​​，需​​​​​​​要​​​​​​​您​​​​​​​为​​​​​​​所​​​​​​​有​​​​​​​加​​​​​​​密​​​​​​​设​​​​​​​备​​​​​​​输​​​​​​​入​​​​​​​每​​​​​​​个​​​​​​​单​​​​​​​独​​​​​​​的​​​​​​​密​​​​​​​码​​​​​​​短​​​​​​​语​​​​​​​。​​​​​​​
  • When upgrading openmpi using yum, the following warning may be returned: 
    cannot open `/tmp/openmpi-upgrade-version.*' for reading: No such file or directory
    Copy to Clipboard Toggle word wrap
    The message is harmless and can be safely ignored.
  • 配​​​​​​​置​​​​​​​ IRQ SMP 亲​​​​​​​和​​​​​​​力​​​​​​​对​​​​​​​那​​​​​​​些​​​​​​​使​​​​​​​用​​​​​​​没​​​​​​​有​​​​​​​ MSI 向​​​​​​​量​​​​​​​掩​​​​​​​码​​​​​​​能​​​​​​​力​​​​​​​的​​​​​​​信​​​​​​​息​​​​​​​信​​​​​​​号​​​​​​​中​​​​​​​断​​​​​​​（MSI）没​​​​​​​有​​​​​​​影​​​​​​​响​​​​​​​。​​​​​​​类​​​​​​​似​​​​​​​的​​​​​​​设​​​​​​​备​​​​​​​示​​​​​​​例​​​​​​​包​​​​​​​括​​​​​​​使​​​​​​​用​​​​​​​ bnx2 驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​的​​​​​​​ Broadcom NetXtreme 以​​​​​​​太​​​​​​​网​​​​​​​设​​​​​​​备​​​​​​​。​​​​​​​
    如​​​​​​​果​​​​​​​您​​​​​​​需​​​​​​​要​​​​​​​为​​​​​​​这​​​​​​​样​​​​​​​的​​​​​​​设​​​​​​​备​​​​​​​配​​​​​​​置​​​​​​​ IRQ，请​​​​​​​在​​​​​​​ /etc/modprobe.d/ 中​​​​​​​生​​​​​​​成​​​​​​​一​​​​​​​个​​​​​​​包​​​​​​​含​​​​​​​以​​​​​​​下​​​​​​​行​​​​​​​的​​​​​​​文​​​​​​​件​​​​​​​来​​​​​​​禁​​​​​​​用​​​​​​​ MSI： 
    		  options bnx2 disable_msi=1
    Copy to Clipboard Toggle word wrap
    另​​​​​​​外​​​​​​​，您​​​​​​​可​​​​​​​以​​​​​​​使​​​​​​​用​​​​​​​内​​​​​​​核​​​​​​​引​​​​​​​导​​​​​​​参​​​​​​​数​​​​​​​ pci=nomsi 完​​​​​​​全​​​​​​​禁​​​​​​​用​​​​​​​ MSI。​​​​​​​
  • 更​​​​​​​新​​​​​​​的​​​​​​​ /etc/udev/rules.d/50-udev.rules 文​​​​​​​件​​​​​​​中​​​​​​​有​​​​​​​一​​​​​​​个​​​​​​​故​​​​​​​障​​​​​​​可​​​​​​​妨​​​​​​​碍​​​​​​​为​​​​​​​在​​​​​​​其​​​​​​​名​​​​​​​称​​​​​​​中​​​​​​​有​​​​​​​大​​​​​​​于​​​​​​​ 9 数​​​​​​​字​​​​​​​的​​​​​​​磁​​​​​​​带​​​​​​​设​​​​​​​备​​​​​​​生​​​​​​​成​​​​​​​持​​​​​​​久​​​​​​​的​​​​​​​名​​​​​​​称​​​​​​​。​​​​​​​例​​​​​​​如​​​​​​​：无​​​​​​​法​​​​​​​为​​​​​​​名​​​​​​​为​​​​​​​ nst12 磁​​​​​​​带​​​​​​​设​​​​​​​备​​​​​​​生​​​​​​​成​​​​​​​持​​​​​​​久​​​​​​​名​​​​​​​称​​​​​​​。​​​​​​​
    要​​​​​​​解​​​​​​​决​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​，请​​​​​​​在​​​​​​​ /etc/udev/rules.d/50-udev.rules 中​​​​​​​每​​​​​​​次​​​​​​​出​​​​​​​现​​​​​​​字​​​​​​​符​​​​​​​串​​​​​​​ nst[0-9] 时​​​​​​​都​​​​​​​添​​​​​​​加​​​​​​​星​​​​​​​号​​​​​​​（*）。​​​​​​​
  • smartctl 工​​​​​​​具​​​​​​​无​​​​​​​法​​​​​​​正​​​​​​​确​​​​​​​在​​​​​​​ SATA 设​​​​​​​备​​​​​​​中​​​​​​​读​​​​​​​取​​​​​​​ SMART 参​​​​​​​数​​​​​​​。​​​​​​​
  • 在​​​​​​​ openmpi 和​​​​​​​ lam 早​​​​​​​先​​​​​​​版​​​​​​​本​​​​​​​中​​​​​​​的​​​​​​​错​​​​​​​误​​​​​​​可​​​​​​​能​​​​​​​妨​​​​​​​碍​​​​​​​您​​​​​​​升​​​​​​​级​​​​​​​这​​​​​​​些​​​​​​​软​​​​​​​件​​​​​​​包​​​​​​​。​​​​​​​这​​​​​​​个​​​​​​​故​​​​​​​障​​​​​​​显​​​​​​​示​​​​​​​以​​​​​​​下​​​​​​​错​​​​​​​误​​​​​​​（在​​​​​​​试​​​​​​​图​​​​​​​升​​​​​​​级​​​​​​​ openmpi 或​​​​​​​者​​​​​​​ lam 时​​​​​​​）： 
    error: %preun(openmpi-[version]) scriptlet failed, exit status 2
    Copy to Clipboard Toggle word wrap
    因​​​​​​​此​​​​​​​，您​​​​​​​需​​​​​​​要​​​​​​​手​​​​​​​动​​​​​​​删​​​​​​​除​​​​​​​ openmpi 和​​​​​​​ lam 的​​​​​​​老​​​​​​​版​​​​​​​本​​​​​​​以​​​​​​​便​​​​​​​安​​​​​​​装​​​​​​​最​​​​​​​新​​​​​​​的​​​​​​​版​​​​​​​本​​​​​​​。​​​​​​​要​​​​​​​做​​​​​​​到​​​​​​​这​​​​​​​一​​​​​​​点​​​​​​​，请​​​​​​​使​​​​​​​用​​​​​​​以​​​​​​​下​​​​​​​命​​​​​​​令​​​​​​​：
    rpm -qa | grep '^openmpi-\|^lam-' | xargs rpm -e --noscripts --allmatches
  • When using dm-multipath, if features "1 queue_if_no_path" is specified in /etc/multipath.conf then any process that issues I/O will hang until one or more paths are restored.
    To avoid this, set no_path_retry [N] in /etc/multipath.conf (where [N] is the number of times the system should retry a path). When you do, remove the features "1 queue_if_no_path" option from /etc/multipath.conf as well.
    If you need to use "1 queue_if_no_path" and experience the issue noted here, use dmsetup to edit the policy at runtime for a particular LUN (i.e. for which all the paths are unavailable).
    To illustrate: run dmsetup message [device] 0 "fail_if_no_path", where [device] is the multipath device name (e.g. mpath2; do not specify the path) for which you want to change the policy from "queue_if_no_path" to "fail_if_no_path".
  • 不​​​​​​​支​​​​​​​持​​​​​​​启​​​​​​​用​​​​​​​同​​​​​​​一​​​​​​​内​​​​​​​核​​​​​​​模​​​​​​​块​​​​​​​的​​​​​​​多​​​​​​​个​​​​​​​安​​​​​​​装​​​​​​​版​​​​​​​本​​​​​​​。​​​​​​​除​​​​​​​此​​​​​​​以​​​​​​​外​​​​​​​，解​​​​​​​析​​​​​​​内​​​​​​​核​​​​​​​模​​​​​​​块​​​​​​​方​​​​​​​法​​​​​​​中​​​​​​​的​​​​​​​一​​​​​​​个​​​​​​​错​​​​​​​误​​​​​​​有​​​​​​​时​​​​​​​会​​​​​​​导​​​​​​​致​​​​​​​启​​​​​​​用​​​​​​​同​​​​​​​一​​​​​​​内​​​​​​​核​​​​​​​模​​​​​​​块​​​​​​​的​​​​​​​老​​​​​​​版​​​​​​​本​​​​​​​。​​​​​​​
    红​​​​​​​帽​​​​​​​建​​​​​​​议​​​​​​​您​​​​​​​在​​​​​​​安​​​​​​​装​​​​​​​现​​​​​​​有​​​​​​​内​​​​​​​核​​​​​​​模​​​​​​​块​​​​​​​的​​​​​​​较​​​​​​​新​​​​​​​版​​​​​​​本​​​​​​​时​​​​​​​应​​​​​​​该​​​​​​​首​​​​​​​先​​​​​​​删​​​​​​​除​​​​​​​旧​​​​​​​的​​​​​​​版​​​​​​​本​​​​​​​。​​​​​​​
  • 在​​​​​​​配​​​​​​​置​​​​​​​了​​​​​​​ NFS 的​​​​​​​ IBM Bladecenter QS21 或​​​​​​​者​​​​​​​ QS22 中​​​​​​​执​​​​​​​行​​​​​​​ kdump 会​​​​​​​失​​​​​​​败​​​​​​​。​​​​​​​要​​​​​​​避​​​​​​​免​​​​​​​这​​​​​​​个​​​​​​​错​​​​​​​误​​​​​​​，请​​​​​​​在​​​​​​​ /etc/kdump.conf 中​​​​​​​指​​​​​​​定​​​​​​​ NFS 转​​​​​​​储​​​​​​​目​​​​​​​标​​​​​​​。​​​​​​​
  • IBM T60 笔​​​​​​​记​​​​​​​本​​​​​​​电​​​​​​​脑​​​​​​​会​​​​​​​在​​​​​​​挂​​​​​​​起​​​​​​​以​​​​​​​及​​​​​​​插​​​​​​​到​​​​​​​底​​​​​​​座​​​​​​​上​​​​​​​时​​​​​​​完​​​​​​​全​​​​​​​断​​​​​​​电​​​​​​​。​​​​​​​要​​​​​​​避​​​​​​​免​​​​​​​这​​​​​​​种​​​​​​​情​​​​​​​况​​​​​​​，请​​​​​​​使​​​​​​​用​​​​​​​参​​​​​​​数​​​​​​​ acpi_sleep=s3_bios 引​​​​​​​导​​​​​​​系​​​​​​​统​​​​​​​。​​​​​​​
  • IBM Bladecenter 的​​​​​​​ QLogic iSCSI Expansion Card 可​​​​​​​提​​​​​​​供​​​​​​​以​​​​​​​太​​​​​​​网​​​​​​​和​​​​​​​ iSCSI 功​​​​​​​能​​​​​​​。​​​​​​​网​​​​​​​卡​​​​​​​的​​​​​​​某​​​​​​​些​​​​​​​部​​​​​​​分​​​​​​​可​​​​​​​由​​​​​​​两​​​​​​​个​​​​​​​功​​​​​​​能​​​​​​​共​​​​​​​享​​​​​​​。​​​​​​​但​​​​​​​目​​​​​​​前​​​​​​​ qla3xxx 和​​​​​​​ qla4xxx 驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​独​​​​​​​立​​​​​​​支​​​​​​​持​​​​​​​以​​​​​​​太​​​​​​​网​​​​​​​和​​​​​​​ iSCSI 功​​​​​​​能​​​​​​​。​​​​​​​这​​​​​​​两​​​​​​​个​​​​​​​驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​都​​​​​​​不​​​​​​​支​​​​​​​持​​​​​​​同​​​​​​​时​​​​​​​使​​​​​​​用​​​​​​​以​​​​​​​太​​​​​​​网​​​​​​​和​​​​​​​ iSCSI 功​​​​​​​能​​​​​​​。​​​​​​​
    由​​​​​​​于​​​​​​​这​​​​​​​种​​​​​​​限​​​​​​​制​​​​​​​，成​​​​​​​功​​​​​​​复​​​​​​​位​​​​​​​（通​​​​​​​过​​​​​​​连​​​​​​​续​​​​​​​的​​​​​​​ ifdown/ifup 命​​​​​​​令​​​​​​​）可​​​​​​​能​​​​​​​会​​​​​​​使​​​​​​​设​​​​​​​备​​​​​​​停​​​​​​​滞​​​​​​​。​​​​​​​要​​​​​​​避​​​​​​​免​​​​​​​这​​​​​​​种​​​​​​​情​​​​​​​况​​​​​​​，请​​​​​​​在​​​​​​​执​​​​​​​行​​​​​​​ ifup 后​​​​​​​，在​​​​​​​发​​​​​​​出​​​​​​​ ifdown 命​​​​​​​令​​​​​​​前​​​​​​​有​​​​​​​一​​​​​​​个​​​​​​​ 10 秒​​​​​​​钟​​​​​​​的​​​​​​​间​​​​​​​隔​​​​​​​。​​​​​​​同​​​​​​​时​​​​​​​，还​​​​​​​要​​​​​​​在​​​​​​​执​​​​​​​行​​​​​​​ ifdown 后​​​​​​​，在​​​​​​​发​​​​​​​出​​​​​​​ ifup 命​​​​​​​令​​​​​​​前​​​​​​​也​​​​​​​有​​​​​​​ 10 秒​​​​​​​钟​​​​​​​的​​​​​​​间​​​​​​​隔​​​​​​​。​​​​​​​这​​​​​​​个​​​​​​​间​​​​​​​隔​​​​​​​可​​​​​​​在​​​​​​​发​​​​​​​出​​​​​​​ ifup 命​​​​​​​令​​​​​​​时​​​​​​​给​​​​​​​出​​​​​​​充​​​​​​​分​​​​​​​的​​​​​​​稳​​​​​​​定​​​​​​​时​​​​​​​间​​​​​​​并​​​​​​​重​​​​​​​新​​​​​​​启​​​​​​​动​​​​​​​所​​​​​​​有​​​​​​​功​​​​​​​能​​​​​​​。​​​​​​​
  • 安​​​​​​​装​​​​​​​了​​​​​​​ Cisco Aironet MPI-350 无​​​​​​​线​​​​​​​网​​​​​​​卡​​​​​​​的​​​​​​​笔​​​​​​​记​​​​​​​本​​​​​​​可​​​​​​​能​​​​​​​会​​​​​​​在​​​​​​​使​​​​​​​用​​​​​​​有​​​​​​​线​​​​​​​以​​​​​​​太​​​​​​​端​​​​​​​口​​​​​​​进​​​​​​​行​​​​​​​网​​​​​​​络​​​​​​​安​​​​​​​装​​​​​​​的​​​​​​​过​​​​​​​程​​​​​​​中​​​​​​​，不​​​​​​​能​​​​​​​获​​​​​​​取​​​​​​​ DHCP 地​​​​​​​址​​​​​​​。​​​​​​​
    要​​​​​​​解​​​​​​​决​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​，可​​​​​​​以​​​​​​​使​​​​​​​用​​​​​​​本​​​​​​​地​​​​​​​介​​​​​​​质​​​​​​​进​​​​​​​行​​​​​​​安​​​​​​​装​​​​​​​。​​​​​​​或​​​​​​​者​​​​​​​，在​​​​​​​安​​​​​​​装​​​​​​​之​​​​​​​前​​​​​​​您​​​​​​​可​​​​​​​以​​​​​​​在​​​​​​​笔​​​​​​​记​​​​​​​本​​​​​​​的​​​​​​​ BIOS 里​​​​​​​禁​​​​​​​用​​​​​​​无​​​​​​​线​​​​​​​网​​​​​​​卡​​​​​​​（完​​​​​​​成​​​​​​​安​​​​​​​装​​​​​​​后​​​​​​​，您​​​​​​​可​​​​​​​以​​​​​​​再​​​​​​​启​​​​​​​用​​​​​​​它​​​​​​​）。​​​​​​​
  • 在​​​​​​​红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 5.3 中​​​​​​​无​​​​​​​法​​​​​​​在​​​​​​​引​​​​​​​导​​​​​​​时​​​​​​​记​​​​​​​录​​​​​​​到​​​​​​​ /var/log/boot.log。​​​​​​​
  • 如​​​​​​​果​​​​​​​ X 正​​​​​​​在​​​​​​​运​​​​​​​行​​​​​​​且​​​​​​​使​​​​​​​用​​​​​​​ vesa 之​​​​​​​外​​​​​​​的​​​​​​​驱​​​​​​​动​​​​​​​，系​​​​​​​统​​​​​​​可​​​​​​​能​​​​​​​没​​​​​​​有​​​​​​​成​​​​​​​功​​​​​​​地​​​​​​​重​​​​​​​启​​​​​​​至​​​​​​​ kexec/kdump 内​​​​​​​核​​​​​​​。​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​只​​​​​​​存​​​​​​​在​​​​​​​于​​​​​​​ ATI Rage XL 图​​​​​​​形​​​​​​​芯​​​​​​​片​​​​​​​组​​​​​​​里​​​​​​​。​​​​​​​
    如​​​​​​​果​​​​​​​ X 运​​​​​​​行​​​​​​​在​​​​​​​安​​​​​​​装​​​​​​​了​​​​​​​ ATI Rage XL 的​​​​​​​系​​​​​​​统​​​​​​​上​​​​​​​，为​​​​​​​了​​​​​​​成​​​​​​​功​​​​​​​地​​​​​​​重​​​​​​​启​​​​​​​至​​​​​​​ kexec/kdump 内​​​​​​​核​​​​​​​，请​​​​​​​确​​​​​​​保​​​​​​​它​​​​​​​使​​​​​​​用​​​​​​​ vesa 驱​​​​​​​动​​​​​​​。​​​​​​​
  • 当​​​​​​​在​​​​​​​安​​​​​​​装​​​​​​​了​​​​​​​ nVidia CK804 芯​​​​​​​片​​​​​​​组​​​​​​​的​​​​​​​机​​​​​​​器​​​​​​​上​​​​​​​使​​​​​​​用​​​​​​​红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 5.2 时​​​​​​​，您​​​​​​​可​​​​​​​能​​​​​​​会​​​​​​​收​​​​​​​到​​​​​​​如​​​​​​​下​​​​​​​的​​​​​​​内​​​​​​​核​​​​​​​信​​​​​​​息​​​​​​​： 
    kernel: assign_interrupt_mode Found MSI capability
kernel: pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
    Copy to Clipboard Toggle word wrap
    这​​​​​​​些​​​​​​​信​​​​​​​息​​​​​​​指​​​​​​​出​​​​​​​某​​​​​​​些​​​​​​​ PCI-E 端​​​​​​​口​​​​​​​没​​​​​​​有​​​​​​​请​​​​​​​求​​​​​​​ IRQ。​​​​​​​但​​​​​​​这​​​​​​​些​​​​​​​信​​​​​​​息​​​​​​​不​​​​​​​会​​​​​​​以​​​​​​​任​​​​​​​何​​​​​​​方​​​​​​​式​​​​​​​影​​​​​​​响​​​​​​​机​​​​​​​器​​​​​​​的​​​​​​​操​​​​​​​作​​​​​​​。​​​​​​​
  • 当​​​​​​​您​​​​​​​以​​​​​​​根​​​​​​​用​​​​​​​户​​​​​​​身​​​​​​​份​​​​​​​登​​​​​​​录​​​​​​​时​​​​​​​不​​​​​​​会​​​​​​​自​​​​​​​动​​​​​​​挂​​​​​​​载​​​​​​​可​​​​​​​拆​​​​​​​卸​​​​​​​存​​​​​​​储​​​​​​​设​​​​​​​备​​​​​​​（比​​​​​​​如​​​​​​​ CD 和​​​​​​​ DVD）。​​​​​​​因​​​​​​​此​​​​​​​，您​​​​​​​将​​​​​​​需​​​​​​​要​​​​​​​用​​​​​​​图​​​​​​​形​​​​​​​文​​​​​​​件​​​​​​​管​​​​​​​理​​​​​​​程​​​​​​​序​​​​​​​手​​​​​​​动​​​​​​​挂​​​​​​​载​​​​​​​这​​​​​​​样​​​​​​​的​​​​​​​设​​​​​​​备​​​​​​​。​​​​​​​
    另​​​​​​​外​​​​​​​您​​​​​​​还​​​​​​​可​​​​​​​以​​​​​​​运​​​​​​​行​​​​​​​以​​​​​​​下​​​​​​​命​​​​​​​令​​​​​​​将​​​​​​​设​​​​​​​备​​​​​​​挂​​​​​​​载​​​​​​​到​​​​​​​ /media： 
    mount /dev/[device name] /media
    Copy to Clipboard Toggle word wrap
  • 当​​​​​​​在​​​​​​​配​​​​​​​置​​​​​​​的​​​​​​​存​​​​​​​储​​​​​​​系​​​​​​​统​​​​​​​中​​​​​​​删​​​​​​​除​​​​​​​ LUN 时​​​​​​​，不​​​​​​​会​​​​​​​在​​​​​​​主​​​​​​​机​​​​​​​中​​​​​​​有​​​​​​​所​​​​​​​反​​​​​​​应​​​​​​​。​​​​​​​在​​​​​​​这​​​​​​​种​​​​​​​情​​​​​​​况​​​​​​​下​​​​​​​，当​​​​​​​使​​​​​​​用​​​​​​​ dm-multipath 时​​​​​​​，lvm 可​​​​​​​能​​​​​​​会​​​​​​​挂​​​​​​​起​​​​​​​，因​​​​​​​为​​​​​​​ LUN 现​​​​​​​在​​​​​​​已​​​​​​​经​​​​​​​无​​​​​​​效​​​​​​​了​​​​​​​。​​​​​​​
    如​​​​​​​果​​​​​​​出​​​​​​​现​​​​​​​这​​​​​​​种​​​​​​​情​​​​​​​况​​​​​​​，请​​​​​​​删​​​​​​​除​​​​​​​所​​​​​​​有​​​​​​​设​​​​​​​备​​​​​​​和​​​​​​​ /etc/lvm/.cache 文​​​​​​​件​​​​​​​中​​​​​​​指​​​​​​​定​​​​​​​无​​​​​​​效​​​​​​​ LUN 的​​​​​​​ mpath 链​​​​​​​接​​​​​​​条​​​​​​​目​​​​​​​。​​​​​​​
    找​​​​​​​出​​​​​​​这​​​​​​​些​​​​​​​条​​​​​​​目​​​​​​​是​​​​​​​什​​​​​​​么​​​​​​​，运​​​​​​​行​​​​​​​以​​​​​​​下​​​​​​​命​​​​​​​令​​​​​​​：
    ls -l /dev/mpath | grep [stale LUN]
    例​​​​​​​如​​​​​​​：如​​​​​​​果​​​​​​​ [stale LUN] 是​​​​​​​ 3600d0230003414f30000203a7bc41a00，则​​​​​​​会​​​​​​​出​​​​​​​现​​​​​​​以​​​​​​​下​​​​​​​结​​​​​​​果​​​​​​​： 
    lrwxrwxrwx 1 root root 7 Aug  2 10:33 /3600d0230003414f30000203a7bc41a00 -> ../dm-4
lrwxrwxrwx 1 root root 7 Aug  2 10:33 /3600d0230003414f30000203a7bc41a00p1 -> ../dm-5
    Copy to Clipboard Toggle word wrap
    就​​​​​​​是​​​​​​​说​​​​​​​ 3600d0230003414f30000203a7bc41a00 与​​​​​​​两​​​​​​​个​​​​​​​ mpath 链​​​​​​​接​​​​​​​匹​​​​​​​配​​​​​​​，它​​​​​​​们​​​​​​​是​​​​​​​：dm-4 和​​​​​​​ dm-5。​​​​​​​
    因​​​​​​​此​​​​​​​，要​​​​​​​删​​​​​​​除​​​​​​​ /etc/lvm/.cache 文​​​​​​​件​​​​​​​中​​​​​​​的​​​​​​​以​​​​​​​下​​​​​​​各​​​​​​​行​​​​​​​： 
    /dev/dm-4 
/dev/dm-5 
/dev/mapper/3600d0230003414f30000203a7bc41a00
/dev/mapper/3600d0230003414f30000203a7bc41a00p1
/dev/mpath/3600d0230003414f30000203a7bc41a00
/dev/mpath/3600d0230003414f30000203a7bc41a00p1
    Copy to Clipboard Toggle word wrap
  • 如​​​​​​​果​​​​​​​某​​​​​​​个​​​​​​​路​​​​​​​径​​​​​​​是​​​​​​​一​​​​​​​个​​​​​​​锁​​​​​​​定​​​​​​​的​​​​​​​设​​​​​​​备​​​​​​​，运​​​​​​​行​​​​​​​带​​​​​​​ -ll 选​​​​​​​项​​​​​​​的​​​​​​​ multipath 命​​​​​​​令​​​​​​​可​​​​​​​能​​​​​​​导​​​​​​​致​​​​​​​命​​​​​​​令​​​​​​​停​​​​​​​滞​​​​​​​。​​​​​​​请​​​​​​​注​​​​​​​意​​​​​​​：如​​​​​​​果​​​​​​​有​​​​​​​时​​​​​​​设​​​​​​​备​​​​​​​没​​​​​​​有​​​​​​​反​​​​​​​应​​​​​​​后​​​​​​​，驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​并​​​​​​​不​​​​​​​会​​​​​​​让​​​​​​​请​​​​​​​求​​​​​​​失​​​​​​​败​​​​​​​。​​​​​​​
    这​​​​​​​是​​​​​​​由​​​​​​​清​​​​​​​除​​​​​​​编​​​​​​​码​​​​​​​造​​​​​​​成​​​​​​​的​​​​​​​，那​​​​​​​些​​​​​​​编​​​​​​​码​​​​​​​会​​​​​​​一​​​​​​​直​​​​​​​等​​​​​​​到​​​​​​​检​​​​​​​查​​​​​​​程​​​​​​​序​​​​​​​完​​​​​​​成​​​​​​​或​​​​​​​者​​​​​​​失​​​​​​​败​​​​​​​为​​​​​​​止​​​​​​​。​​​​​​​要​​​​​​​在​​​​​​​不​​​​​​​挂​​​​​​​起​​​​​​​该​​​​​​​命​​​​​​​令​​​​​​​的​​​​​​​情​​​​​​​况​​​​​​​下​​​​​​​显​​​​​​​示​​​​​​​当​​​​​​​前​​​​​​​的​​​​​​​ multipath 状​​​​​​​态​​​​​​​，请​​​​​​​使​​​​​​​用​​​​​​​ multipath -l 命​​​​​​​令​​​​​​​。​​​​​​​
  • 从​​​​​​​ pm-utils 的​​​​​​​红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 5.2 的​​​​​​​ ß 版​​​​​​​本​​​​​​​升​​​​​​​级​​​​​​​ pm-utils 会​​​​​​​失​​​​​​​败​​​​​​​，并​​​​​​​导​​​​​​​致​​​​​​​以​​​​​​​下​​​​​​​出​​​​​​​错​​​​​​​信​​​​​​​息​​​​​​​： 
    error: unpacking of archive failed on file /etc/pm/sleep.d: cpio: rename
    Copy to Clipboard Toggle word wrap
    要​​​​​​​防​​​​​​​止​​​​​​​此​​​​​​​现​​​​​​​象​​​​​​​的​​​​​​​发​​​​​​​生​​​​​​​，请​​​​​​​在​​​​​​​升​​​​​​​级​​​​​​​前​​​​​​​删​​​​​​​除​​​​​​​ /etc/pm/sleep.d/ 目​​​​​​​录​​​​​​​。​​​​​​​如​​​​​​​果​​​​​​​ /etc/pm/sleep.d/ 中​​​​​​​含​​​​​​​有​​​​​​​文​​​​​​​件​​​​​​​，您​​​​​​​可​​​​​​​将​​​​​​​那​​​​​​​些​​​​​​​文​​​​​​​件​​​​​​​转​​​​​​​移​​​​​​​到​​​​​​​ /etc/pm/hooks/。​​​​​​​
  • 对​​​​​​​ Mellanox MT25204 进​​​​​​​行​​​​​​​的​​​​​​​硬​​​​​​​件​​​​​​​测​​​​​​​试​​​​​​​证​​​​​​​明​​​​​​​在​​​​​​​这​​​​​​​样​​​​​​​高​​​​​​​负​​​​​​​载​​​​​​​的​​​​​​​情​​​​​​​况​​​​​​​下​​​​​​​会​​​​​​​出​​​​​​​现​​​​​​​内​​​​​​​部​​​​​​​错​​​​​​​误​​​​​​​。​​​​​​​当​​​​​​​ ib_mthca 驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​报​​​​​​​告​​​​​​​在​​​​​​​此​​​​​​​硬​​​​​​​件​​​​​​​中​​​​​​​出​​​​​​​现​​​​​​​灾​​​​​​​难​​​​​​​性​​​​​​​错​​​​​​​误​​​​​​​时​​​​​​​，它​​​​​​​通​​​​​​​常​​​​​​​和​​​​​​​不​​​​​​​充​​​​​​​分​​​​​​​的​​​​​​​完​​​​​​​成​​​​​​​队​​​​​​​列​​​​​​​深​​​​​​​度​​​​​​​有​​​​​​​关​​​​​​​，这​​​​​​​种​​​​​​​现​​​​​​​象​​​​​​​是​​​​​​​由​​​​​​​用​​​​​​​户​​​​​​​应​​​​​​​用​​​​​​​程​​​​​​​序​​​​​​​生​​​​​​​成​​​​​​​的​​​​​​​大​​​​​​​量​​​​​​​未​​​​​​​完​​​​​​​成​​​​​​​的​​​​​​​工​​​​​​​作​​​​​​​请​​​​​​​求​​​​​​​造​​​​​​​成​​​​​​​的​​​​​​​。​​​​​​​
    虽​​​​​​​然​​​​​​​该​​​​​​​驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​可​​​​​​​重​​​​​​​新​​​​​​​设​​​​​​​定​​​​​​​该​​​​​​​硬​​​​​​​件​​​​​​​并​​​​​​​从​​​​​​​该​​​​​​​事​​​​​​​件​​​​​​​中​​​​​​​恢​​​​​​​复​​​​​​​，但​​​​​​​在​​​​​​​出​​​​​​​错​​​​​​​时​​​​​​​的​​​​​​​所​​​​​​​有​​​​​​​存​​​​​​​在​​​​​​​的​​​​​​​连​​​​​​​接​​​​​​​都​​​​​​​会​​​​​​​丢​​​​​​​失​​​​​​​。​​​​​​​这​​​​​​​通​​​​​​​常​​​​​​​会​​​​​​​导​​​​​​​致​​​​​​​在​​​​​​​用​​​​​​​户​​​​​​​应​​​​​​​用​​​​​​​程​​​​​​​序​​​​​​​的​​​​​​​重​​​​​​​新​​​​​​​分​​​​​​​段​​​​​​​故​​​​​​​障​​​​​​​。​​​​​​​进​​​​​​​一​​​​​​​步​​​​​​​说​​​​​​​，如​​​​​​​果​​​​​​​在​​​​​​​出​​​​​​​错​​​​​​​时​​​​​​​正​​​​​​​在​​​​​​​运​​​​​​​行​​​​​​​ opensm，那​​​​​​​么​​​​​​​就​​​​​​​必​​​​​​​须​​​​​​​重​​​​​​​新​​​​​​​手​​​​​​​动​​​​​​​启​​​​​​​动​​​​​​​它​​​​​​​才​​​​​​​能​​​​​​​恢​​​​​​​复​​​​​​​正​​​​​​​常​​​​​​​操​​​​​​​作​​​​​​​。​​​​​​​
  • 当​​​​​​​在​​​​​​​某​​​​​​​个​​​​​​​客​​​​​​​户​​​​​​​端​​​​​​​中​​​​​​​安​​​​​​​装​​​​​​​红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 5.3 时​​​​​​​，会​​​​​​​将​​​​​​​该​​​​​​​客​​​​​​​户​​​​​​​端​​​​​​​配​​​​​​​置​​​​​​​为​​​​​​​明​​​​​​​确​​​​​​​使​​​​​​​用​​​​​​​一​​​​​​​个​​​​​​​ dom0 提​​​​​​​供​​​​​​​的​​​​​​​临​​​​​​​时​​​​​​​安​​​​​​​装​​​​​​​内​​​​​​​核​​​​​​​。​​​​​​​安​​​​​​​装​​​​​​​完​​​​​​​成​​​​​​​后​​​​​​​，它​​​​​​​就​​​​​​​可​​​​​​​以​​​​​​​使​​​​​​​用​​​​​​​其​​​​​​​自​​​​​​​身​​​​​​​的​​​​​​​引​​​​​​​导​​​​​​​装​​​​​​​载​​​​​​​程​​​​​​​序​​​​​​​。​​​​​​​但​​​​​​​只​​​​​​​能​​​​​​​将​​​​​​​客​​​​​​​户​​​​​​​端​​​​​​​的​​​​​​​第​​​​​​​一​​​​​​​次​​​​​​​重​​​​​​​启​​​​​​​强​​​​​​​制​​​​​​​执​​​​​​​行​​​​​​​为​​​​​​​关​​​​​​​机​​​​​​​才​​​​​​​可​​​​​​​行​​​​​​​。​​​​​​​
    因​​​​​​​此​​​​​​​，当​​​​​​​在​​​​​​​客​​​​​​​户​​​​​​​端​​​​​​​安​​​​​​​装​​​​​​​末​​​​​​​尾​​​​​​​出​​​​​​​现​​​​​​​重​​​​​​​启​​​​​​​按​​​​​​​钮​​​​​​​时​​​​​​​，点​​​​​​​击​​​​​​​它​​​​​​​关​​​​​​​闭​​​​​​​客​​​​​​​户​​​​​​​端​​​​​​​，而​​​​​​​不​​​​​​​要​​​​​​​重​​​​​​​启​​​​​​​。​​​​​​​这​​​​​​​是​​​​​​​可​​​​​​​预​​​​​​​见​​​​​​​的​​​​​​​动​​​​​​​作​​​​​​​。​​​​​​​
    请​​​​​​​注​​​​​​​意​​​​​​​：当​​​​​​​您​​​​​​​在​​​​​​​此​​​​​​​之​​​​​​​后​​​​​​​引​​​​​​​导​​​​​​​该​​​​​​​客​​​​​​​户​​​​​​​端​​​​​​​，它​​​​​​​就​​​​​​​会​​​​​​​使​​​​​​​用​​​​​​​其​​​​​​​自​​​​​​​身​​​​​​​的​​​​​​​引​​​​​​​导​​​​​​​装​​​​​​​载​​​​​​​程​​​​​​​序​​​​​​​。​​​​​​​
  • 如​​​​​​​果​​​​​​​安​​​​​​​装​​​​​​​了​​​​​​​任​​​​​​​何​​​​​​​ KDE 或​​​​​​​者​​​​​​​ qt 开​​​​​​​发​​​​​​​软​​​​​​​件​​​​​​​包​​​​​​​（例​​​​​​​如​​​​​​​：qt-devel），那​​​​​​​么​​​​​​​在​​​​​​​ compiz 源​​​​​​​ RPM 中​​​​​​​运​​​​​​​行​​​​​​​ rpmbuild 会​​​​​​​失​​​​​​​败​​​​​​​。​​​​​​​这​​​​​​​是​​​​​​​由​​​​​​​于​​​​​​​ compiz 配​​​​​​​置​​​​​​​脚​​​​​​​本​​​​​​​中​​​​​​​的​​​​​​​一​​​​​​​个​​​​​​​ bug 所​​​​​​​致​​​​​​​。​​​​​​​
    要​​​​​​​解​​​​​​​决​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​，请​​​​​​​在​​​​​​​试​​​​​​​图​​​​​​​从​​​​​​​其​​​​​​​源​​​​​​​ RPM 构​​​​​​​建​​​​​​​ compiz 软​​​​​​​件​​​​​​​包​​​​​​​前​​​​​​​删​​​​​​​除​​​​​​​所​​​​​​​有​​​​​​​ KDE 或​​​​​​​者​​​​​​​ qt 开​​​​​​​发​​​​​​​软​​​​​​​件​​​​​​​包​​​​​​​。​​​​​​​
  • 如​​​​​​​果​​​​​​​您​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​装​​​​​​​备​​​​​​​的​​​​​​​是​​​​​​​ ATI Radeon R500 或​​​​​​​者​​​​​​​ R600 显​​​​​​​卡​​​​​​​，在​​​​​​​安​​​​​​​装​​​​​​​后​​​​​​​ firstboot 将​​​​​​​不​​​​​​​会​​​​​​​运​​​​​​​行​​​​​​​。​​​​​​​该​​​​​​​系​​​​​​​统​​​​​​​将​​​​​​​直​​​​​​​接​​​​​​​进​​​​​​​入​​​​​​​图​​​​​​​形​​​​​​​登​​​​​​​录​​​​​​​屏​​​​​​​幕​​​​​​​，而​​​​​​​完​​​​​​​全​​​​​​​跳​​​​​​​过​​​​​​​ firstboot。​​​​​​​如​​​​​​​果​​​​​​​您​​​​​​​试​​​​​​​图​​​​​​​手​​​​​​​动​​​​​​​运​​​​​​​行​​​​​​​ firstboot（例​​​​​​​如​​​​​​​从​​​​​​​一​​​​​​​个​​​​​​​ failsafe 终​​​​​​​端​​​​​​​中​​​​​​​），X 会​​​​​​​话​​​​​​​将​​​​​​​会​​​​​​​崩​​​​​​​溃​​​​​​​。​​​​​​​
    这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​是​​​​​​​由​​​​​​​ ATI Radeon R500/R600 硬​​​​​​​件​​​​​​​使​​​​​​​用​​​​​​​的​​​​​​​驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​引​​​​​​​起​​​​​​​的​​​​​​​。​​​​​​​这​​​​​​​些​​​​​​​显​​​​​​​卡​​​​​​​使​​​​​​​用​​​​​​​的​​​​​​​默​​​​​​​认​​​​​​​驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​仍​​​​​​​是​​​​​​​停​​​​​​​留​​​​​​​在​​​​​​​技​​​​​​​术​​​​​​​预​​​​​​​览​​​​​​​阶​​​​​​​段​​​​​​​。​​​​​​​要​​​​​​​解​​​​​​​决​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​，请​​​​​​​备​​​​​​​份​​​​​​​您​​​​​​​的​​​​​​​ /etc/X11/xorg.conf 文​​​​​​​件​​​​​​​，然​​​​​​​后​​​​​​​将​​​​​​​ X 配​​​​​​​置​​​​​​​为​​​​​​​使​​​​​​​用​​​​​​​支​​​​​​​持​​​​​​​的​​​​​​​ vesa 驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​，而​​​​​​​不​​​​​​​是​​​​​​​使​​​​​​​用​​​​​​​以​​​​​​​下​​​​​​​命​​​​​​​令​​​​​​​：
    system-config-display --reconfig --set-driver=vesa
    您​​​​​​​现​​​​​​​在​​​​​​​可​​​​​​​以​​​​​​​运​​​​​​​行​​​​​​​ firstboot 了​​​​​​​。​​​​​​​要​​​​​​​切​​​​​​​换​​​​​​​回​​​​​​​您​​​​​​​原​​​​​​​来​​​​​​​的​​​​​​​设​​​​​​​置​​​​​​​，请​​​​​​​恢​​​​​​​复​​​​​​​您​​​​​​​的​​​​​​​原​​​​​​​始​​​​​​​ /etc/X11/xorg.conf 文​​​​​​​件​​​​​​​。​​​​​​​
  • 如​​​​​​​果​​​​​​​您​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​使​​​​​​​用​​​​​​​ TSC 计​​​​​​​时​​​​​​​器​​​​​​​，gettimeofday 系​​​​​​​统​​​​​​​调​​​​​​​用​​​​​​​可​​​​​​​能​​​​​​​会​​​​​​​逆​​​​​​​时​​​​​​​针​​​​​​​。​​​​​​​这​​​​​​​是​​​​​​​因​​​​​​​为​​​​​​​某​​​​​​​个​​​​​​​溢​​​​​​​出​​​​​​​问​​​​​​​题​​​​​​​导​​​​​​​致​​​​​​​ TSC 计​​​​​​​时​​​​​​​器​​​​​​​在​​​​​​​某​​​​​​​些​​​​​​​情​​​​​​​况​​​​​​​下​​​​​​​显​​​​​​​著​​​​​​​向​​​​​​​前​​​​​​​跳​​​​​​​越​​​​​​​。​​​​​​​发​​​​​​​生​​​​​​​这​​​​​​​种​​​​​​​情​​​​​​​况​​​​​​​时​​​​​​​，TSC 将​​​​​​​进​​​​​​​行​​​​​​​自​​​​​​​我​​​​​​​修​​​​​​​正​​​​​​​，但​​​​​​​将​​​​​​​最​​​​​​​终​​​​​​​及​​​​​​​时​​​​​​​一​​​​​​​个​​​​​​​后​​​​​​​退​​​​​​​移​​​​​​​动​​​​​​​。​​​​​​​
    这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​对​​​​​​​时​​​​​​​间​​​​​​​敏​​​​​​​感​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​尤​​​​​​​为​​​​​​​重​​​​​​​要​​​​​​​，比​​​​​​​如​​​​​​​那​​​​​​​些​​​​​​​用​​​​​​​来​​​​​​​传​​​​​​​输​​​​​​​系​​​​​​​统​​​​​​​和​​​​​​​数​​​​​​​据​​​​​​​库​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​。​​​​​​​因​​​​​​​此​​​​​​​，如​​​​​​​果​​​​​​​您​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​需​​​​​​​要​​​​​​​准​​​​​​​确​​​​​​​计​​​​​​​时​​​​​​​，红​​​​​​​帽​​​​​​​强​​​​​​​烈​​​​​​​建​​​​​​​议​​​​​​​您​​​​​​​将​​​​​​​内​​​​​​​核​​​​​​​设​​​​​​​置​​​​​​​为​​​​​​​使​​​​​​​用​​​​​​​另​​​​​​​一​​​​​​​个​​​​​​​计​​​​​​​时​​​​​​​器​​​​​​​（例​​​​​​​如​​​​​​​ HPET）。​​​​​​​
  • 试​​​​​​​图​​​​​​​运​​​​​​​行​​​​​​​ sniff 可​​​​​​​能​​​​​​​会​​​​​​​造​​​​​​​成​​​​​​​错​​​​​​​误​​​​​​​。​​​​​​​这​​​​​​​是​​​​​​​因​​​​​​​为​​​​​​​ dogtail 中​​​​​​​没​​​​​​​有​​​​​​​安​​​​​​​装​​​​​​​所​​​​​​​需​​​​​​​软​​​​​​​件​​​​​​​包​​​​​​​。​​​​​​​
    要​​​​​​​避​​​​​​​免​​​​​​​这​​​​​​​个​​​​​​​现​​​​​​​象​​​​​​​，请​​​​​​​手​​​​​​​动​​​​​​​安​​​​​​​装​​​​​​​以​​​​​​​下​​​​​​​软​​​​​​​件​​​​​​​包​​​​​​​：
    • librsvg2
    • ghostscript-fonts
    • pygtk2-libglade
  • Thin Provisioning (also known as "virtual provisioning") will be first released with EMC Symmetrix DMX3 and DMX4. Please refer to the EMC Support Matrix and Symmetrix Enginuity code release notes for further details.
  • 在​​​​​​​ /etc/multipath.conf 中​​​​​​​，将​​​​​​​ max_fds 设​​​​​​​置​​​​​​​为​​​​​​​ unlimited 可​​​​​​​让​​​​​​​ multipathd 守​​​​​​​护​​​​​​​进​​​​​​​程​​​​​​​无​​​​​​​法​​​​​​​支​​​​​​​持​​​​​​​启​​​​​​​动​​​​​​​。​​​​​​​因​​​​​​​此​​​​​​​，您​​​​​​​应​​​​​​​该​​​​​​​使​​​​​​​用​​​​​​​足​​​​​​​够​​​​​​​高​​​​​​​的​​​​​​​数​​​​​​​值​​​​​​​，而​​​​​​​不​​​​​​​是​​​​​​​这​​​​​​​个​​​​​​​设​​​​​​​置​​​​​​​。​​​​​​​
  • SystemTap 目​​​​​​​前​​​​​​​使​​​​​​​用​​​​​​​ GCC 来​​​​​​​侦​​​​​​​测​​​​​​​用​​​​​​​户​​​​​​​空​​​​​​​间​​​​​​​事​​​​​​​件​​​​​​​。​​​​​​​但​​​​​​​ GCC 无​​​​​​​法​​​​​​​为​​​​​​​参​​​​​​​数​​​​​​​提​​​​​​​供​​​​​​​带​​​​​​​准​​​​​​​确​​​​​​​位​​​​​​​置​​​​​​​列​​​​​​​表​​​​​​​信​​​​​​​息​​​​​​​的​​​​​​​ debugger。​​​​​​​在​​​​​​​有​​​​​​​些​​​​​​​情​​​​​​​况​​​​​​​下​​​​​​​，GCC 还​​​​​​​无​​​​​​​法​​​​​​​在​​​​​​​一​​​​​​​些​​​​​​​参​​​​​​​数​​​​​​​中​​​​​​​提​​​​​​​供​​​​​​​可​​​​​​​视​​​​​​​性​​​​​​​。​​​​​​​因​​​​​​​此​​​​​​​，侦​​​​​​​测​​​​​​​用​​​​​​​户​​​​​​​空​​​​​​​间​​​​​​​的​​​​​​​ SystemTap 脚​​​​​​​本​​​​​​​可​​​​​​​能​​​​​​​会​​​​​​​返​​​​​​​回​​​​​​​不​​​​​​​准​​​​​​​确​​​​​​​的​​​​​​​读​​​​​​​取​​​​​​​。​​​​​​​
  • IBM T41 笔​​​​​​​记​​​​​​​本​​​​​​​电​​​​​​​脑​​​​​​​模​​​​​​​型​​​​​​​无​​​​​​​法​​​​​​​正​​​​​​​常​​​​​​​进​​​​​​​入​​​​​​​挂​​​​​​​起​​​​​​​模​​​​​​​式​​​​​​​，因​​​​​​​此​​​​​​​挂​​​​​​​起​​​​​​​模​​​​​​​式​​​​​​​仍​​​​​​​会​​​​​​​消​​​​​​​耗​​​​​​​电​​​​​​​池​​​​​​​寿​​​​​​​命​​​​​​​。​​​​​​​这​​​​​​​是​​​​​​​因​​​​​​​为​​​​​​​红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 5 不​​​​​​​包​​​​​​​含​​​​​​​ radeonfb 模​​​​​​​块​​​​​​​。​​​​​​​
    要​​​​​​​解​​​​​​​决​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​，请​​​​​​​将​​​​​​​名​​​​​​​为​​​​​​​ hal-system-power-suspend 的​​​​​​​脚​​​​​​​本​​​​​​​添​​​​​​​加​​​​​​​到​​​​​​​ /usr/share/hal/scripts/ 中​​​​​​​，并​​​​​​​包​​​​​​​含​​​​​​​以​​​​​​​下​​​​​​​行​​​​​​​： 
    	
chvt 1
radeontool light off
radeontool dac off
    Copy to Clipboard Toggle word wrap
    这​​​​​​​个​​​​​​​脚​​​​​​​本​​​​​​​将​​​​​​​确​​​​​​​保​​​​​​​ IBM T41 笔​​​​​​​记​​​​​​​本​​​​​​​电​​​​​​​脑​​​​​​​正​​​​​​​常​​​​​​​进​​​​​​​入​​​​​​​挂​​​​​​​起​​​​​​​模​​​​​​​式​​​​​​​。​​​​​​​要​​​​​​​确​​​​​​​保​​​​​​​系​​​​​​​统​​​​​​​可​​​​​​​正​​​​​​​常​​​​​​​恢​​​​​​​复​​​​​​​一​​​​​​​般​​​​​​​操​​​​​​​作​​​​​​​。​​​​​​​在​​​​​​​同​​​​​​​一​​​​​​​目​​​​​​​录​​​​​​​中​​​​​​​还​​​​​​​要​​​​​​​添​​​​​​​加​​​​​​​ restore-after-standby，其​​​​​​​中​​​​​​​包​​​​​​​含​​​​​​​以​​​​​​​下​​​​​​​行​​​​​​​： 
    	
radeontool dac on
radeontool light on
chvt 7
    Copy to Clipboard Toggle word wrap
  • 如​​​​​​​果​​​​​​​载​​​​​​​入​​​​​​​了​​​​​​​ edac 模​​​​​​​块​​​​​​​，BIOS 内​​​​​​​存​​​​​​​包​​​​​​​括​​​​​​​将​​​​​​​无​​​​​​​法​​​​​​​工​​​​​​​作​​​​​​​。​​​​​​​这​​​​​​​是​​​​​​​因​​​​​​​为​​​​​​​ edac 模​​​​​​​块​​​​​​​清​​​​​​​除​​​​​​​了​​​​​​​ BIOS 用​​​​​​​来​​​​​​​报​​​​​​​告​​​​​​​内​​​​​​​存​​​​​​​错​​​​​​​误​​​​​​​的​​​​​​​注​​​​​​​册​​​​​​​。​​​​​​​
    当​​​​​​​前​​​​​​​的​​​​​​​红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​更​​​​​​​新​​​​​​​模​​​​​​​型​​​​​​​会​​​​​​​指​​​​​​​导​​​​​​​内​​​​​​​核​​​​​​​默​​​​​​​认​​​​​​​载​​​​​​​入​​​​​​​所​​​​​​​有​​​​​​​可​​​​​​​用​​​​​​​模​​​​​​​块​​​​​​​（包​​​​​​​括​​​​​​​ edac 模​​​​​​​块​​​​​​​）。​​​​​​​如​​​​​​​果​​​​​​​您​​​​​​​想​​​​​​​要​​​​​​​确​​​​​​​保​​​​​​​在​​​​​​​您​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​中​​​​​​​可​​​​​​​有​​​​​​​ BIOS 内​​​​​​​存​​​​​​​报​​​​​​​告​​​​​​​，您​​​​​​​需​​​​​​​要​​​​​​​手​​​​​​​动​​​​​​​将​​​​​​​ edac 模​​​​​​​块​​​​​​​列​​​​​​​入​​​​​​​黑​​​​​​​名​​​​​​​单​​​​​​​。​​​​​​​要​​​​​​​做​​​​​​​到​​​​​​​这​​​​​​​一​​​​​​​点​​​​​​​，请​​​​​​​将​​​​​​​以​​​​​​​下​​​​​​​行​​​​​​​添​​​​​​​加​​​​​​​到​​​​​​​ /etc/modprobe.conf 中​​​​​​​： 
    	
blacklist edac_mc
blacklist i5000_edac
blacklist i3000_edac
blacklist e752x_edac
    Copy to Clipboard Toggle word wrap
  • 红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 可​​​​​​​侦​​​​​​​测​​​​​​​某​​​​​​​个​​​​​​​基​​​​​​​础​​​​​​​块​​​​​​​失​​​​​​​败​​​​​​​的​​​​​​​在​​​​​​​线​​​​​​​增​​​​​​​长​​​​​​​或​​​​​​​者​​​​​​​缩​​​​​​​小​​​​​​​。​​​​​​​但​​​​​​​没​​​​​​​有​​​​​​​方​​​​​​​法​​​​​​​可​​​​​​​自​​​​​​​动​​​​​​​侦​​​​​​​测​​​​​​​到​​​​​​​某​​​​​​​个​​​​​​​设​​​​​​​备​​​​​​​的​​​​​​​大​​​​​​​小​​​​​​​的​​​​​​​改​​​​​​​变​​​​​​​。​​​​​​​因​​​​​​​此​​​​​​​需​​​​​​​要​​​​​​​一​​​​​​​些​​​​​​​手​​​​​​​动​​​​​​​步​​​​​​​骤​​​​​​​来​​​​​​​识​​​​​​​别​​​​​​​这​​​​​​​些​​​​​​​并​​​​​​​对​​​​​​​位​​​​​​​于​​​​​​​给​​​​​​​定​​​​​​​设​​​​​​​备​​​​​​​中​​​​​​​的​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​重​​​​​​​新​​​​​​​定​​​​​​​义​​​​​​​大​​​​​​​小​​​​​​​。​​​​​​​当​​​​​​​侦​​​​​​​测​​​​​​​到​​​​​​​重​​​​​​​新​​​​​​​定​​​​​​​义​​​​​​​大​​​​​​​小​​​​​​​的​​​​​​​块​​​​​​​设​​​​​​​备​​​​​​​时​​​​​​​，会​​​​​​​在​​​​​​​系​​​​​​​统​​​​​​​日​​​​​​​志​​​​​​​中​​​​​​​出​​​​​​​现​​​​​​​类​​​​​​​似​​​​​​​如​​​​​​​下​​​​​​​的​​​​​​​信​​​​​​​息​​​​​​​： 
    VFS: busy inodes on changed media or resized disk sdi
    Copy to Clipboard Toggle word wrap
    如​​​​​​​果​​​​​​​增​​​​​​​加​​​​​​​块​​​​​​​设​​​​​​​备​​​​​​​，那​​​​​​​么​​​​​​​这​​​​​​​个​​​​​​​信​​​​​​​息​​​​​​​就​​​​​​​可​​​​​​​被​​​​​​​忽​​​​​​​略​​​​​​​。​​​​​​​但​​​​​​​是​​​​​​​如​​​​​​​果​​​​​​​在​​​​​​​没​​​​​​​有​​​​​​​首​​​​​​​先​​​​​​​减​​​​​​​少​​​​​​​在​​​​​​​块​​​​​​​设​​​​​​​备​​​​​​​中​​​​​​​的​​​​​​​设​​​​​​​置​​​​​​​，那​​​​​​​么​​​​​​​在​​​​​​​较​​​​​​​少​​​​​​​块​​​​​​​设​​​​​​​备​​​​​​​时​​​​​​​，该​​​​​​​设​​​​​​​备​​​​​​​中​​​​​​​的​​​​​​​数​​​​​​​据​​​​​​​将​​​​​​​崩​​​​​​​溃​​​​​​​。​​​​​​​
    只​​​​​​​能​​​​​​​在​​​​​​​完​​​​​​​整​​​​​​​ LUN（或​​​​​​​者​​​​​​​块​​​​​​​设​​​​​​​备​​​​​​​）中​​​​​​​创​​​​​​​建​​​​​​​的​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​中​​​​​​​进​​​​​​​行​​​​​​​在​​​​​​​线​​​​​​​大​​​​​​​小​​​​​​​调​​​​​​​整​​​​​​​。​​​​​​​如​​​​​​​果​​​​​​​在​​​​​​​该​​​​​​​块​​​​​​​设​​​​​​​备​​​​​​​中​​​​​​​有​​​​​​​分​​​​​​​区​​​​​​​表​​​​​​​，那​​​​​​​么​​​​​​​则​​​​​​​必​​​​​​​须​​​​​​​卸​​​​​​​载​​​​​​​该​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​以​​​​​​​更​​​​​​​新​​​​​​​分​​​​​​​区​​​​​​​表​​​​​​​。​​​​​​​
  • 如​​​​​​​果​​​​​​​您​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​挂​​​​​​​载​​​​​​​了​​​​​​​ GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​，在​​​​​​​从​​​​​​​一​​​​​​​个​​​​​​​节​​​​​​​点​​​​​​​访​​​​​​​问​​​​​​​缓​​​​​​​冲​​​​​​​的​​​​​​​内​​​​​​​节​​​​​​​点​​​​​​​并​​​​​​​在​​​​​​​不​​​​​​​同​​​​​​​的​​​​​​​节​​​​​​​点​​​​​​​取​​​​​​​消​​​​​​​链​​​​​​​接​​​​​​​时​​​​​​​，节​​​​​​​点​​​​​​​将​​​​​​​挂​​​​​​​起​​​​​​​。​​​​​​​当​​​​​​​这​​​​​​​种​​​​​​​情​​​​​​​况​​​​​​​发​​​​​​​生​​​​​​​时​​​​​​​，挂​​​​​​​起​​​​​​​的​​​​​​​节​​​​​​​点​​​​​​​将​​​​​​​无​​​​​​​法​​​​​​​使​​​​​​​用​​​​​​​直​​​​​​​到​​​​​​​您​​​​​​​通​​​​​​​过​​​​​​​正​​​​​​​常​​​​​​​群​​​​​​​集​​​​​​​恢​​​​​​​复​​​​​​​机​​​​​​​制​​​​​​​将​​​​​​​其​​​​​​​保​​​​​​​护​​​​​​​并​​​​​​​恢​​​​​​​复​​​​​​​过​​​​​​​来​​​​​​​。​​​​​​​所​​​​​​​有​​​​​​​在​​​​​​​挂​​​​​​​起​​​​​​​的​​​​​​​节​​​​​​​点​​​​​​​受​​​​​​​阻​​​​​​​滞​​​​​​​进​​​​​​​程​​​​​​​的​​​​​​​栈​​​​​​​跟​​​​​​​踪​​​​​​​中​​​​​​​还​​​​​​​将​​​​​​​出​​​​​​​现​​​​​​​ gfs2_dinode_dealloc 和​​​​​​​ shrink_dcache_memory。​​​​​​​
    这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​对​​​​​​​单​​​​​​​一​​​​​​​节​​​​​​​点​​​​​​​ GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​没​​​​​​​有​​​​​​​影​​​​​​​响​​​​​​​。​​​​​​​
  • The following message may be encountered during system boot: 
    Could not detect stabilization, waiting 10 seconds.
Reading all physical volumes.  This may take a while...
    Copy to Clipboard Toggle word wrap
    This delay (which may be up to 10 seconds, dependant on the hardware configuration) is necessary to ensure that the kernel has completed scanning the disks.
  • 目​​​​​​​前​​​​​​​在​​​​​​​ ipmitool 中​​​​​​​使​​​​​​​用​​​​​​​的​​​​​​​ User Payload Access 允​​​​​​​许​​​​​​​您​​​​​​​配​​​​​​​置​​​​​​​设​​​​​​​备​​​​​​​，但​​​​​​​不​​​​​​​允​​​​​​​许​​​​​​​您​​​​​​​在​​​​​​​当​​​​​​​前​​​​​​​设​​​​​​​置​​​​​​​中​​​​​​​对​​​​​​​那​​​​​​​些​​​​​​​设​​​​​​​备​​​​​​​进​​​​​​​行​​​​​​​搜​​​​​​​索​​​​​​​。​​​​​​​
  • 在​​​​​​​ kickstart 文​​​​​​​件​​​​​​​中​​​​​​​使​​​​​​​用​​​​​​​ swap --grow 参​​​​​​​数​​​​​​​而​​​​​​​不​​​​​​​同​​​​​​​时​​​​​​​设​​​​​​​置​​​​​​​ --maxsize 参​​​​​​​数​​​​​​​会​​​​​​​使​​​​​​​ anaconda 强​​​​​​​行​​​​​​​限​​​​​​​制​​​​​​​交​​​​​​​换​​​​​​​分​​​​​​​区​​​​​​​的​​​​​​​最​​​​​​​大​​​​​​​值​​​​​​​。​​​​​​​它​​​​​​​不​​​​​​​允​​​​​​​许​​​​​​​增​​​​​​​大​​​​​​​交​​​​​​​换​​​​​​​分​​​​​​​区​​​​​​​以​​​​​​​适​​​​​​​应​​​​​​​设​​​​​​​备​​​​​​​的​​​​​​​需​​​​​​​要​​​​​​​。​​​​​​​
    对​​​​​​​于​​​​​​​物​​​​​​​理​​​​​​​内​​​​​​​存​​​​​​​小​​​​​​​于​​​​​​​ 2GB 的​​​​​​​系​​​​​​​统​​​​​​​，强​​​​​​​制​​​​​​​的​​​​​​​限​​​​​​​制​​​​​​​是​​​​​​​物​​​​​​​理​​​​​​​内​​​​​​​存​​​​​​​大​​​​​​​小​​​​​​​的​​​​​​​两​​​​​​​倍​​​​​​​。​​​​​​​对​​​​​​​于​​​​​​​超​​​​​​​过​​​​​​​ 2GB 内​​​​​​​存​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​，强​​​​​​​制​​​​​​​的​​​​​​​限​​​​​​​制​​​​​​​是​​​​​​​物​​​​​​​理​​​​​​​内​​​​​​​存​​​​​​​的​​​​​​​大​​​​​​​小​​​​​​​再​​​​​​​加​​​​​​​ 2GB。​​​​​​​
  • The gfs2_convert program may not free up all blocks from the GFS metadata that are no longer used under GFS2. These unused metadata blocks will be discovered and freed the next time gfs2_fsck is run on the file system. It is recommended that gfs2_fsck be run after the filesystem has been converted to free the unused blocks. These unused blocks will be flagged by gfs2_fsck with messages such as: 
    Ondisk and fsck bitmaps differ at block 137 (0x89) 
Ondisk status is 1 (Data) but FSCK thinks it should be 0 (Free)
Metadata type is 0 (free)
    Copy to Clipboard Toggle word wrap
    These messages do not indicate corruption in the GFS2 file system, they indicate blocks that should have been freed, but were not. The number of blocks needing to be freed will vary depending on the size of the file system and block size. Many file systems will not encounter this issue at all. Large file systems may have a small number of blocks (typically less than 100).

9.2. x86 Architectures
复制链接

  • When running the bare-metal (non-Virtualized) kernel, the X server may not be able to retrieve EDID information from the monitor. When this occurs, the graphics driver will be unable to display resolutions highers than 800x600.
    要​​​​​​​解​​​​​​​决​​​​​​​这​​​​​​​个​​​​​​​问​​​​​​​题​​​​​​​，请​​​​​​​在​​​​​​​ /etc/X11/xorg.conf 文​​​​​​​件​​​​​​​的​​​​​​​ ServerLayout 部​​​​​​​分​​​​​​​添​​​​​​​加​​​​​​​以​​​​​​​下​​​​​​​这​​​​​​​行​​​​​​​： 
    Option "Int10Backend" "x86emu"
    Copy to Clipboard Toggle word wrap
  • Recording needs to be manually enabled on Dell M4300 and M6300. To do this, perform the following steps:
    1. 打​​​​​​​开​​​​​​​ alsamixer。​​​​​​​
    2. 按​​​​​​​ Tab 键​​​​​​​切​​​​​​​换​​​​​​​至​​​​​​​ 查​​​​​​​看​​​​​​​ 字​​​​​​​段​​​​​​​的​​​​​​​ [Capture] 部​​​​​​​分​​​​​​​（位​​​​​​​于​​​​​​​菜​​​​​​​单​​​​​​​的​​​​​​​左​​​​​​​上​​​​​​​部​​​​​​​分​​​​​​​）。​​​​​​​
    3. 按​​​​​​​ Space 键​​​​​​​。​​​​​​​
    4. 要​​​​​​​确​​​​​​​定​​​​​​​启​​​​​​​用​​​​​​​了​​​​​​​记​​​​​​​录​​​​​​​，ADCMux 字​​​​​​​段​​​​​​​上​​​​​​​面​​​​​​​的​​​​​​​文​​​​​​​字​​​​​​​部​​​​​​​分​​​​​​​应​​​​​​​该​​​​​​​显​​​​​​​示​​​​​​​ L R CAPTUR。​​​​​​​
  • If encryption is enabled on the boot device during system installation, the following message will be logged during system boot: 
    padlock: VIA PadLock not detected.
    Copy to Clipboard Toggle word wrap
    This message can safely be ignored.

9.3. x86_64 Architectures
复制链接

  • Some machines that use NVIDIA graphics cards may display corrupted graphics or fonts when using the graphical installer or during a graphical login. To work around this, switch to a virtual console and back to the original X host.
  • On an IBM T61 laptop, Red Hat recommends that you refrain from clicking the glxgears window (when glxgears is run). Doing so can lock the system.
    要​​​​​​​防​​​​​​​止​​​​​​​这​​​​​​​种​​​​​​​情​​​​​​​况​​​​​​​发​​​​​​​生​​​​​​​，请​​​​​​​在​​​​​​​ /etc/X11/xorg.conf 文​​​​​​​件​​​​​​​的​​​​​​​ Device 部​​​​​​​分​​​​​​​添​​​​​​​加​​​​​​​以​​​​​​​下​​​​​​​这​​​​​​​行​​​​​​​： 
    Option "Tiling" "0"
    Copy to Clipboard Toggle word wrap
  • Recording needs to be manually enabled on Dell M4300 and M6300. To do this, perform the following steps:
    1. 打​​​​​​​开​​​​​​​ alsamixer。​​​​​​​
    2. 按​​​​​​​ Tab 键​​​​​​​切​​​​​​​换​​​​​​​至​​​​​​​ 查​​​​​​​看​​​​​​​ 字​​​​​​​段​​​​​​​的​​​​​​​ [Capture] 部​​​​​​​分​​​​​​​（位​​​​​​​于​​​​​​​菜​​​​​​​单​​​​​​​的​​​​​​​左​​​​​​​上​​​​​​​部​​​​​​​分​​​​​​​）。​​​​​​​
    3. 按​​​​​​​ Space 键​​​​​​​。​​​​​​​
    4. 要​​​​​​​确​​​​​​​定​​​​​​​启​​​​​​​用​​​​​​​了​​​​​​​记​​​​​​​录​​​​​​​，ADCMux 字​​​​​​​段​​​​​​​上​​​​​​​面​​​​​​​的​​​​​​​文​​​​​​​字​​​​​​​部​​​​​​​分​​​​​​​应​​​​​​​该​​​​​​​显​​​​​​​示​​​​​​​ L R CAPTUR。​​​​​​​
  • 如​​​​​​​果​​​​​​​您​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​使​​​​​​​用​​​​​​​ Intel 945GM 显​​​​​​​卡​​​​​​​，请​​​​​​​必​​​​​​​要​​​​​​​使​​​​​​​用​​​​​​​ i810 驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​。​​​​​​​您​​​​​​​需​​​​​​​要​​​​​​​使​​​​​​​用​​​​​​​默​​​​​​​认​​​​​​​的​​​​​​​ intel 驱​​​​​​​动​​​​​​​程​​​​​​​序​​​​​​​。​​​​​​​
  • 在​​​​​​​双​​​​​​​-GPU 笔​​​​​​​记​​​​​​​本​​​​​​​电​​​​​​​脑​​​​​​​中​​​​​​​，如​​​​​​​果​​​​​​​一​​​​​​​个​​​​​​​图​​​​​​​形​​​​​​​芯​​​​​​​片​​​​​​​是​​​​​​​基​​​​​​​于​​​​​​​ Intel 的​​​​​​​，该​​​​​​​ Intel 图​​​​​​​形​​​​​​​模​​​​​​​式​​​​​​​则​​​​​​​无​​​​​​​法​​​​​​​驱​​​​​​​动​​​​​​​任​​​​​​​何​​​​​​​其​​​​​​​它​​​​​​​外​​​​​​​置​​​​​​​电​​​​​​​子​​​​​​​连​​​​​​​接​​​​​​​（包​​​​​​​括​​​​​​​ HDMI、​​​​​​​DVI 和​​​​​​​ DisplayPort）。​​​​​​​这​​​​​​​是​​​​​​​ Intel GPU 的​​​​​​​一​​​​​​​个​​​​​​​硬​​​​​​​件​​​​​​​限​​​​​​​制​​​​​​​。​​​​​​​如​​​​​​​果​​​​​​​您​​​​​​​需​​​​​​​要​​​​​​​外​​​​​​​置​​​​​​​数​​​​​​​字​​​​​​​连​​​​​​​接​​​​​​​，请​​​​​​​将​​​​​​​该​​​​​​​系​​​​​​​统​​​​​​​配​​​​​​​置​​​​​​​为​​​​​​​使​​​​​​​用​​​​​​​独​​​​​​​立​​​​​​​图​​​​​​​形​​​​​​​芯​​​​​​​片​​​​​​​（在​​​​​​​ BIOS 中​​​​​​​）。​​​​​​​

9.4. PowerPC Architectures
复制链接

  • When using Alt-SysRq-W to debug, the following warning message will appear: 
    Badness in smp_call_function at arch/powerpc/kernel/smp.c:223
    Copy to Clipboard Toggle word wrap
    之​​​​​​​后​​​​​​​，系​​​​​​​统​​​​​​​也​​​​​​​会​​​​​​​警​​​​​​​告​​​​​​​将​​​​​​​挂​​​​​​​起​​​​​​​。​​​​​​​这​​​​​​​个​​​​​​​信​​​​​​​息​​​​​​​应​​​​​​​该​​​​​​​被​​​​​​​忽​​​​​​​略​​​​​​​，因​​​​​​​为​​​​​​​它​​​​​​​不​​​​​​​会​​​​​​​导​​​​​​​致​​​​​​​系​​​​​​​统​​​​​​​挂​​​​​​​起​​​​​​​。​​​​​​​
  • Recording needs to be manually enabled on Dell M4300 and M6300. To do this, perform the following steps:
    1. 打​​​​​​​开​​​​​​​ alsamixer。​​​​​​​
    2. 按​​​​​​​ Tab 键​​​​​​​切​​​​​​​换​​​​​​​至​​​​​​​ 查​​​​​​​看​​​​​​​ 字​​​​​​​段​​​​​​​的​​​​​​​ [Capture] 部​​​​​​​分​​​​​​​（位​​​​​​​于​​​​​​​菜​​​​​​​单​​​​​​​的​​​​​​​左​​​​​​​上​​​​​​​部​​​​​​​分​​​​​​​）。​​​​​​​
    3. 按​​​​​​​ Space 键​​​​​​​。​​​​​​​
    4. 要​​​​​​​确​​​​​​​定​​​​​​​启​​​​​​​用​​​​​​​了​​​​​​​记​​​​​​​录​​​​​​​，ADCMux 字​​​​​​​段​​​​​​​上​​​​​​​面​​​​​​​的​​​​​​​文​​​​​​​字​​​​​​​部​​​​​​​分​​​​​​​应​​​​​​​该​​​​​​​显​​​​​​​示​​​​​​​ L R CAPTUR。​​​​​​​
  • The size of the PPC kernel image is too large for OpenFirmware to support. Consequently, network booting will fail, resulting in the following error message: 
    Please wait, loading kernel...
/pci@8000000f8000000/ide@4,1/disk@0:2,vmlinux-anaconda: No such file or directory
boot:
    Copy to Clipboard Toggle word wrap
    To work around this:
    1. Boot to the OpenFirmware prompt, by pressing the '8' key when the IBM splash screen is displayed.
    2. 运​​​​​​​行​​​​​​​以​​​​​​​下​​​​​​​命​​​​​​​令​​​​​​​： 
      setenv real-base 2000000
      Copy to Clipboard Toggle word wrap
    3. 使​​​​​​​用​​​​​​​该​​​​​​​命​​​​​​​令​​​​​​​引​​​​​​​导​​​​​​​至​​​​​​​系​​​​​​​统​​​​​​​管​​​​​​​理​​​​​​​服​​​​​​​务​​​​​​​（SMS）： 
      0> dev /packages/gui obe
      Copy to Clipboard Toggle word wrap

9.5. s390x Architectures
复制链接

  • When running Red Hat Enterprise Linux 5.2 on a z/VM that has more than 2GB of guest storage defined, invalid data can be read from and written to any FCP and OSA device attached in QDIO mode with the Queued-I/O assist (QIOASSIST) option enabled. If your system has any such devices attached, Red Hat recommends that you download and install the corresponding z/VM Program Temporary Fix (PTF) from the following link:
    http://www-1.ibm.com/support/docview.wss?uid=isg1VM64306
  • It is not possible to directly read and convert a z/VM dump into a file. Instead, you should first copy the dump from the z/VM reader into a Linux file system using vmur and convert the dump into a Linux-readable file using vmconvert.
  • The IBM System z does not provide a traditional Unix-style physical console. As such, Red Hat Enterprise Linux 5.2 for the IBM System z does not support the firstboot functionality during initial program load.
    要​​​​​​​为​​​​​​​用​​​​​​​于​​​​​​​ IBM System z 的​​​​​​​红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 5.2 进​​​​​​​行​​​​​​​正​​​​​​​确​​​​​​​的​​​​​​​初​​​​​​​始​​​​​​​化​​​​​​​设​​​​​​​置​​​​​​​，请​​​​​​​在​​​​​​​安​​​​​​​装​​​​​​​后​​​​​​​运​​​​​​​行​​​​​​​以​​​​​​​下​​​​​​​命​​​​​​​令​​​​​​​：
    • /usr/bin/setup — 由​​​​​​​ setuptool 软​​​​​​​件​​​​​​​包​​​​​​​提​​​​​​​供​​​​​​​。​​​​​​​
    • /usr/bin/rhn_register — 由​​​​​​​ rhen-setup 软​​​​​​​件​​​​​​​包​​​​​​​提​​​​​​​供​​​​​​​。​​​​​​​

9.6. ia64 Architecture
复制链接

  • Some Itanium systems cannot properly produce console output from the kexec purgatory code. This code contains instructions for backing up the first 640k of memory after a crash.
    虽​​​​​​​然​​​​​​​ purgatory 控​​​​​​​制​​​​​​​台​​​​​​​输​​​​​​​出​​​​​​​对​​​​​​​判​​​​​​​断​​​​​​​问​​​​​​​题​​​​​​​很​​​​​​​有​​​​​​​帮​​​​​​​助​​​​​​​，但​​​​​​​ kdump 正​​​​​​​常​​​​​​​工​​​​​​​作​​​​​​​并​​​​​​​不​​​​​​​需​​​​​​​要​​​​​​​它​​​​​​​。​​​​​​​因​​​​​​​此​​​​​​​，如​​​​​​​果​​​​​​​您​​​​​​​的​​​​​​​ Itanium 系​​​​​​​统​​​​​​​在​​​​​​​进​​​​​​​行​​​​​​​ kdump 操​​​​​​​作​​​​​​​时​​​​​​​复​​​​​​​位​​​​​​​，可​​​​​​​通​​​​​​​过​​​​​​​在​​​​​​​ /etc/sysconfig/kdump 文​​​​​​​件​​​​​​​的​​​​​​​ KEXEC_ARGS 变​​​​​​​量​​​​​​​中​​​​​​​添​​​​​​​加​​​​​​​ --noio 选​​​​​​​项​​​​​​​来​​​​​​​禁​​​​​​​止​​​​​​​在​​​​​​​ purgatory 进​​​​​​​行​​​​​​​控​​​​​​​制​​​​​​​台​​​​​​​输​​​​​​​出​​​​​​​。​​​​​​​
  • Running perftest will fail if different CPU speeds are detected. As such, you should disable CPU speed scaling before running perftest.
  • When the kdump kernel is booted, the following error will appear in the boot log: 
    mknod: /tmp/initrd.[numbers]/dev/efirtc: No such file or directory
    Copy to Clipboard Toggle word wrap
    这​​​​​​​个​​​​​​​错​​​​​​​误​​​​​​​是​​​​​​​由​​​​​​​于​​​​​​​要​​​​​​​在​​​​​​​错​​​​​​​误​​​​​​​路​​​​​​​径​​​​​​​中​​​​​​​创​​​​​​​建​​​​​​​ efirtc 的​​​​​​​异​​​​​​​常​​​​​​​请​​​​​​​求​​​​​​​引​​​​​​​起​​​​​​​的​​​​​​​。​​​​​​​但​​​​​​​当​​​​​​​启​​​​​​​动​​​​​​​了​​​​​​​ kdump 时​​​​​​​，还​​​​​​​会​​​​​​​在​​​​​​​ initramfs 中​​​​​​​静​​​​​​​态​​​​​​​创​​​​​​​建​​​​​​​那​​​​​​​个​​​​​​​有​​​​​​​问​​​​​​​题​​​​​​​的​​​​​​​设​​​​​​​备​​​​​​​路​​​​​​​径​​​​​​​。​​​​​​​因​​​​​​​此​​​​​​​在​​​​​​​运​​​​​​​行​​​​​​​时​​​​​​​创​​​​​​​建​​​​​​​设​​​​​​​备​​​​​​​节​​​​​​​点​​​​​​​是​​​​​​​多​​​​​​​余​​​​​​​的​​​​​​​、​​​​​​​无​​​​​​​害​​​​​​​的​​​​​​​、​​​​​​​且​​​​​​​应​​​​​​​该​​​​​​​不​​​​​​​会​​​​​​​影​​​​​​​响​​​​​​​到​​​​​​​ kdump 性​​​​​​​能​​​​​​​。​​​​​​​
  • Some systems may be unable to boot the kdump kernel properly. In such cases, use the machvec=dig kernel parameter.
  • Recording needs to be manually enabled on Dell M4300 and M6300. To do this, perform the following steps:
    1. 打​​​​​​​开​​​​​​​ alsamixer。​​​​​​​
    2. 按​​​​​​​ Tab 键​​​​​​​切​​​​​​​换​​​​​​​至​​​​​​​ 查​​​​​​​看​​​​​​​ 字​​​​​​​段​​​​​​​的​​​​​​​ [Capture] 部​​​​​​​分​​​​​​​（位​​​​​​​于​​​​​​​菜​​​​​​​单​​​​​​​的​​​​​​​左​​​​​​​上​​​​​​​部​​​​​​​分​​​​​​​）。​​​​​​​
    3. 按​​​​​​​ Space 键​​​​​​​。​​​​​​​
    4. 要​​​​​​​确​​​​​​​定​​​​​​​启​​​​​​​用​​​​​​​了​​​​​​​记​​​​​​​录​​​​​​​，ADCMux 字​​​​​​​段​​​​​​​上​​​​​​​面​​​​​​​的​​​​​​​文​​​​​​​字​​​​​​​部​​​​​​​分​​​​​​​应​​​​​​​该​​​​​​​显​​​​​​​示​​​​​​​ L R CAPTUR。​​​​​​​
  • 在​​​​​​​ Intel 基​​​​​​​于​​​​​​​ Itanium 的​​​​​​​系​​​​​​​统​​​​​​​中​​​​​​​以​​​​​​​ enforcing 模​​​​​​​式​​​​​​​运​​​​​​​行​​​​​​​ SELinux，必​​​​​​​须​​​​​​​打​​​​​​​开​​​​​​​ allow_unconfined_execmem_dyntrans 或​​​​​​​者​​​​​​​ allow_execmem 布​​​​​​​尔​​​​​​​值​​​​​​​以​​​​​​​便​​​​​​​允​​​​​​​许​​​​​​​ IA-32 执​​​​​​​行​​​​​​​层​​​​​​​（ia32el 服​​​​​​​务​​​​​​​）正​​​​​​​确​​​​​​​操​​​​​​​作​​​​​​​。​​​​​​​如​​​​​​​果​​​​​​​关​​​​​​​闭​​​​​​​ allow_unconfined_execmem_dyntrans 布​​​​​​​尔​​​​​​​值​​​​​​​，但​​​​​​​打​​​​​​​开​​​​​​​ allow_execmem 布​​​​​​​尔​​​​​​​值​​​​​​​，如​​​​​​​红​​​​​​​帽​​​​​​​企​​​​​​​业​​​​​​​版​​​​​​​ Linux 5 默​​​​​​​认​​​​​​​所​​​​​​​设​​​​​​​置​​​​​​​，ia32el 服​​​​​​​务​​​​​​​支​​​​​​​持​​​​​​​ 32 位​​​​​​​模​​​​​​​拟​​​​​​​，但​​​​​​​如​​​​​​​果​​​​​​​两​​​​​​​个​​​​​​​布​​​​​​​尔​​​​​​​值​​​​​​​都​​​​​​​关​​​​​​​闭​​​​​​​了​​​​​​​，模​​​​​​​拟​​​​​​​将​​​​​​​失​​​​​​​败​​​​​​​。​​​​​​​
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat