09-28-2010
The IRQ value seems unusually high; perhaps an APIC IRQ?
Try booting with "irqpoll" option.
Also, run "dmesg" after you get the error and see if you get any further info.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Help! My mouse gave up the ghost, so I connected a USB wheel mouse, and chose it from the list in Suse's Yast2. Also installed it in Windows 98 on the same machine. It works fine in both linux and Windows 98, except for this fact:
I have to reinstall it every time I boot into Linux.... (1 Reply)
Discussion started by: Sonshyne5
1 Replies
2. UNIX for Dummies Questions & Answers
Hi Guru's,
How do I find and set the login idle time setting in HP-UX 32?
Thanks in advance,
Mani (1 Reply)
Discussion started by: jvmani
1 Replies
3. Shell Programming and Scripting
Matez,
I have a list of process id's in a text file. I want to know how to find the idle time of a process which are more than 300secs and kill them accordingly.
Could you please help me to get these details. I want to write a shell script with this.
Thanks..Krish :) (36 Replies)
Discussion started by: Krrishv
36 Replies
4. Shell Programming and Scripting
Does anyone know how do you determine the user idle time of stdin in order to log the user out for being idle too long. I would like to write a c program to do this but I it is not clear upon how to determine idle time from keyboard input. (9 Replies)
Discussion started by: cpaquette
9 Replies
5. UNIX for Advanced & Expert Users
Hi All
I need to find the idle time of a user... but my OS seems to be not supporting finger
$ finger
-sh: finger: command not found
I need to find the idle time and perform some other operations... So is there any other way i can find the idle time of a user...
$ uname -a... (2 Replies)
Discussion started by: Whiteboard
2 Replies
6. HP-UX
HP-UX B.11.23 ia64
Hi everyone,
First of all I am new member to this forum. Thankyou all for this forum, it helped me many times.
Coming to my question,I am writing a C program to find the log info of the users who are currently logged in(precisely what who -u do).
I am able to get... (0 Replies)
Discussion started by: bhiku matre
0 Replies
7. UNIX for Advanced & Expert Users
I need to find the idle time on a machine in the manner: How long time ago somebody did the last action with mouse or keyboard? Unfortunately "w" doesn't do this. It produced the following output on a machine a user was actually working on with an application:
15# w
15:55:28 up 15 days, ... (1 Reply)
Discussion started by: elbrand
1 Replies
8. SCO
hi
I've configured X Server using Video Configuration Manager on SCO 5.0.6, but the keyboard and mouse are freezing after 5 minutes on the graphical login mask.
---------- Post updated at 01:59 PM ---------- Previous update was at 02:43 AM ----------
BTW I finished the configuration,... (2 Replies)
Discussion started by: ccc
2 Replies
9. Shell Programming and Scripting
Hello..
I have many sleepy users on my Solaris box and need to kill them if they are idle for more than 45 minutes for example...I know who -u gives and the idle time but unable to make a awk line to get the condition perfect. Please help...:wall: (9 Replies)
Discussion started by: wimaxpole
9 Replies
10. Shell Programming and Scripting
I want to get average idle time of the server using mpstat. The problem I am having is %idle is not in same columns in all the versions of linux.
example 1:
example 2:
I tried below command as generalized solution but as Average as one less column output is not proper.
I am... (1 Reply)
Discussion started by: kumarjohn
1 Replies
HPET(4) BSD Kernel Interfaces Manual HPET(4)
NAME
hpet -- High Precision Event Timer driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device acpi
The following tunables are settable from the loader(8):
hint.hpet.X.allowed_irqs
is a 32bit mask. Each set bit allows driver to use respective IRQ, if BIOS also set respective capability bit in comparator's configuration
register. Default value is 0xffff0000, except some known broken hardware.
hint.hpet.X.clock
controls event timers functionality support. Setting to 0, disables it. Default value is 1.
hint.hpet.X.legacy_route
controls "LegacyReplacement Route" mode. If enabled, HPET will steal IRQ0 of i8254 timer and IRQ8 of RTC. Before using it, make sure that
respective drivers are not using interrupts, by setting also:
hint.attimer.0.clock=0
hint.atrtc.0.clock=0
Default value is 0.
hint.hpet.X.per_cpu
controls how much per-CPU event timers should driver attempt to register. This functionality requires every comparator in a group to have
own unshared IRQ, so it depends on hardware capabilities and interrupts configuration. Default value is 1.
DESCRIPTION
This driver uses High Precision Event Timer hardware (part of the chipset, usually enumerated via ACPI) to supply kernel with one time
counter and several (usually from 3 to 8) event timers. This hardware includes single main counter with known increment frequency (10MHz or
more), and several programmable comparators (optionally with automatic reload feature). When value of the main counter matches current value
of any comparator, interrupt can be generated. Depending on hardware capabilities and configuration, interrupt can be delivered as regular
I/O APIC interrupt (ISA or PCI) in range from 0 to 31, or as Front Side Bus interrupt, alike to PCI MSI interrupts, or in so called "Lega-
cyReplacement Route" HPET can steal IRQ0 of i8254 and IRQ8 of the RTC. Interrupt can be either edge- or level-triggered. In last case they
could be safely shared with PCI IRQs. Driver prefers to use FSB interrupts, if supported, to avoid sharing. If it is not possible, it uses
single sharable IRQ from PCI range. Other modes (LegacyReplacement and ISA IRQs) require special care to setup, but could be configured man-
ually via device hints.
Event timers provided by the driver support both one-shot an periodic modes and irrelevant to CPU power states.
Depending on hardware capabilities and configuration, driver can expose each comparator as separate event timer or group them into one or
several per-CPU event timers. In last case interrupt of every of those comparators within group is bound to specific CPU core. This is possi-
ble only when each of these comparators has own unsharable IRQ.
SEE ALSO
acpi(4), apic(4), atrtc(4), attimer(4), eventtimers(4), timecounters(4)
HISTORY
The hpet driver first appeared in FreeBSD 6.3. Support for event timers was added in FreeBSD 9.0.
BSD
September 14, 2010 BSD