IBM eserver xSeries 440, Быстрая справка

Страница: 11 / 34

Chapter 2. Hints and tips
7
Linux
For additional information, see “Network operating systems” on page 21.
Linux operating-system clock drifts from the system real-time clock
(RTC)
USB keyboard and trackpoint mouse with SuSe Linux, version 8.0
Description: The Linux operating-system clock drifts or loses time when the service
processor is in a Remote Console session. The longer the Remote Console session, the
more the clock is skewed. This occurs with any supported version of the Linux operating
system.
Linux tics their operating-system clock roughly 100 times a second. If you are in a Remote
Console session during this same time frame, there are anywhere from 8 to 60 SMI (System
Management Interrupts) events occurring (depending on the activity). Due to these events,
some of the Linux timer tics are getting missed and thus the time shift.
Notes:
1. The system real-time clock is operating correctly; only the Linux operating-system clock
is losing time.
2. SMI are used to do the remote video updates through the service processor.
Workaround: Synchronize the Linux operating-system clock to the system RTC.
There are two options:
• Periodically restart the server. This will cause the Linux operating-system clock to sync up
with the system RTC.
• Use a time server on the network to periodically synchronize the Linux operating-system
clock to the time server.
For more information: See Tip H176196 at http://www.ibm.com/pc/support/.
Description: The USB keyboard and Trackpoint mouse work fine during installation; however,
after reboot one of them might cease to function properly.
Note: Unplugging and re plugging the device (into the rear USB slots) might fix the problem.
Known configuration affected: An xSeries 440 server with the following installed:
• A Trackpoint USB Space Saver Keyboard, option part number 22P5150, replacement
part number (FRU) 24P0340
• The usb-uhci device driver for the VIA USB UHCI controller
• SuSe Linux, version 8.0
This behavior occurs due to new timing code for USB that was introduced into the kernel. This
issue is being investigated and should be resolved in the third quarter of 2002.
Workaround: Use a PS/2
®
keyboard.
For more information: See Tip H176029 at http://www.ibm.com/pc/support/.