User`s guide

??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????+???????????????????????×?????????????????????????????????????????????????−26217
Known Issues
82 RedHawk Linux Version 5.4 Release Notes
• If you notice that no panels are running on the desktop, usually accompanied by the
following error, a reboot is required. This sometimes occurs after changing runlevels.
Click OK then reboot the system.
Crash Dump Support
On RedHawk systems, the grub kernel option percpu_alloc=4k should not be used in
combination with the crash(1)/kdump(8) support.
Also, as was the case in RedHawk 5.2, the crash(1) mach-c command only displays the
first CPU information properly.
Boot Time lockd Error Message
During the RedHawk boot process, you may see the following error appear on the console:
...
...
Starting kernel logger: [ OK ]
Starting portmap: [ OK ]
FATAL: Module lockd not found.
Starting NFS statd: [ OK ]
Starting system message bus: [ OK ]
Mounting other filesystems: [ OK ]
...
...
This error message does not indicate a true problem. It is simply issued by modprobe because
it cannot find the lockd kernel module. There is no lockd kernel module on RedHawk; the
lockd support is built statically into the kernel, so no module is required.
System Hang Due To Incorrect Usage of rcim_clocksync(1) Utility
If the RCIM is configured as the clocksource device for a system and that system has a
standalone RCIM II or RCIM III, then the rcim_clocksync(1) utility should not be used
to zero or synchronize the tick clock.
In addition, if the RCIM is configured as the clocksource device for a system and that system
has a cable-connected master RCIM II, then the rcim_clocksync(1) utility should not be
used to stop the tick or POSIX clocks, or to disable the cable clock signal.
In these situations, it is recommended to first change the system clocksource to some other
device, such as the TSC clock or HPET timer, before using the rcim_clocksync(1) utility.
For more information about configuring other devices as the system clocksource, see the System
Clocks and Timers chapter in the RedHawk Linux User’s Guide.