HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- DL585G2 + RHEL4 U4 x86-64
Operating System - Linux
1826075
Members
3420
Online
109690
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2007 07:54 PM
01-17-2007 07:54 PM
The server has the latest updates from RH, the last BIOS and the last PSP installed. The Linux x86_64 HPET option is set in BIOS, and the pci=nommconf is set in GRUB. We still get this message in dmesg:
ipmi message handler version v33
ipmi device interface version v33
IPMI System Interface driver version v33, KCS version v33, SMIC version v33, BT version v33
ipmi_si: Searching for PCI Vendor 0x103c, Device 0x3302
ipmi_si: Trying "kcs" at memory address 0xf7bf0000
ACPI: PCI interrupt 0000:01:04.6[A] -> GSI 16 (level, high) -> IRQ 201
ipmi_si: Found PCI BMC at BAR address 0xf7bf0000
ipmi_si: Using PCI Plug and Play interrupt 201
IPMI kcs interface [0] initialized
cpqci: module license 'Proprietary' taints kernel.
ACPI: PCI interrupt 0000:01:04.2[B] -> GSI 17 (level, high) -> IRQ 209
warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip __do_softirq+0x4d/0xd0
Anyone with an idea why "Your time source seems to be instable or some driver is hogging interupts" shows up?
ipmi message handler version v33
ipmi device interface version v33
IPMI System Interface driver version v33, KCS version v33, SMIC version v33, BT version v33
ipmi_si: Searching for PCI Vendor 0x103c, Device 0x3302
ipmi_si: Trying "kcs" at memory address 0xf7bf0000
ACPI: PCI interrupt 0000:01:04.6[A] -> GSI 16 (level, high) -> IRQ 201
ipmi_si: Found PCI BMC at BAR address 0xf7bf0000
ipmi_si: Using PCI Plug and Play interrupt 201
IPMI kcs interface [0] initialized
cpqci: module license 'Proprietary' taints kernel.
ACPI: PCI interrupt 0000:01:04.2[B] -> GSI 17 (level, high) -> IRQ 209
warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip __do_softirq+0x4d/0xd0
Anyone with an idea why "Your time source seems to be instable or some driver is hogging interupts" shows up?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2007 04:54 AM
01-19-2007 04:54 AM
Solution
The symptom looks like a match to this redhat bugzilla report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=159733
The kernel complains about lost ticks when it should not be complaining.
It is due to be corrected in RHEL 4 U5.
(The message is currently common and harmless. But if there really was a problem that justified the lost ticks warning this problem would mask it.)
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=159733
The kernel complains about lost ticks when it should not be complaining.
It is due to be corrected in RHEL 4 U5.
(The message is currently common and harmless. But if there really was a problem that justified the lost ticks warning this problem would mask it.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2007 05:38 AM
01-19-2007 05:38 AM
Re: DL585G2 + RHEL4 U4 x86-64
Thx, nice to know it's harmless, and will be fixed in U5.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP