8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi, all:
Is there any shell command to show which interrupt handler handle which interrupt number in the system?
li,kunlun (5 Replies)
Discussion started by: liklstar
5 Replies
2. UNIX for Advanced & Expert Users
I receive the following warning messages on a very new machine which has FreeBSD 8.1 x64 installed on it:
Interrupt storm detected on "irq 20" throttling interrupt source
It is unclear what this means and what its origins are (motherboard? CPU? RAM?).
I can start the desktop and the message is... (4 Replies)
Discussion started by: figaro
4 Replies
3. Solaris
Hi,
Is there any way if a normal user in a non global zone can check the resources assigned to the zone ? like max-locked-memory etc.
2. Is it possible to disable the max-locked-memory for a particular zone without rebooting a zone ? (1 Reply)
Discussion started by: fugitive
1 Replies
4. Solaris
Can anyone answer my questions
1. Whats the difference between project.max-locked-memory and max-rss.
And out these 2 which is the preferred way of limiting the physical memory in a project or zone.
2. How to restrict the swap memory in projects (0 Replies)
Discussion started by: fugitive
0 Replies
5. Solaris
I 've 2 questions regarding resource pools and projects,
1. My system has 5 zones and 2 pools configured.
Now, how can i check which zone is running with with pool with the ps command , not with zonecfg command.
2. How can i check a process is running under which project ? (1 Reply)
Discussion started by: fugitive
1 Replies
6. Solaris
Hi
When I create a new project:
For example: projadd -K "project.max-shm-memory=(priv,16GB,deny)" project_name
I need to associate this project to a user in /etc/user_attr:
User_name::::project=project_name
Otherwise, id -p shows reveals that the user has project default.
Is there... (0 Replies)
Discussion started by: melanie_pfefer
0 Replies
7. High Performance Computing
Gurus,
I have several questions :
1. Does Solaris 10/OpenSolaris has some kind of web based management tools ?
Currently I am using WebMin. It worked fine, however I am very curious to use
the tools provided by Sun Microsystem.
Please advise for package name and how to activate.... (0 Replies)
Discussion started by: Zepiroth
0 Replies
8. Linux
Hi all,
we have a big problem, we are running an IA-64 linux system, with 8 CPUs and some GB of RAM, for user usage.
The user are compiling and testing programs on this system, and this caused some problems.
Sometimes, a user program used the hole memory, blocks the other users, and also... (1 Reply)
Discussion started by: malcom
1 Replies
ACPIEC(4) BSD Kernel Interfaces Manual ACPIEC(4)
NAME
acpiec -- ACPI Embedded Controller
SYNOPSIS
acpiec* at acpi?
acpiecdt* at acpi?
DESCRIPTION
The acpiec driver supports ACPI Embedded Controllers.
An ACPI Embedded Controller (EC) is typically a small microprocessor that is responsible for various tasks related to ACPI. The primary task
is to handle ACPI specific interrupts, which are mapped to so-called ACPI General Purpose Events (GPEs). Other possible functions include
embedded access to other buses such as the iic(4).
The ACPI specific events range from user initiated events to events triggered by the hardware. When such an event occurs, typically either a
System Management Interrupt (SMI) or a System Control Interrupt (SCI) is raised. The latter is an active, visible, shareable, level inter-
rupt. On most Intel chipsets SCI is hardwired to the interrupt number 9. The main task of an EC is to raise a system control interrupt.
All GPEs generate SCIs. A typical example of the internal wiring of GPEs could involve gpio(4): when, e.g., the AC adapter is connected, a
certain GPIO line becomes active, a given GPE is flagged, and a SCI interrupt is raised by the EC, leading to execution of ACPI machine code
in order to locate the handler associated with the event. A corresponding driver, acpiacad(4) in this case, will finally finish the process-
ing of the event.
Due to the reasons described above, majority of ACPI specific drivers are dysfunctional without acpiec. It is therefore recommended that
acpiec is always enabled, even though it may not be required on some older systems.
SEE ALSO
acpi(4)
HISTORY
The acpiec driver appeared in NetBSD 1.6.
CAVEATS
Many machines depend on early attachment of acpiec. In such cases the information required by acpiec should be available as a separate and
optional Embedded Controller Descriptor Table (ECDT). If an ECDT is not available or early attachment can not be carried out due other rea-
sons, the initialization of the whole acpi(4) subsystem may be problematic.
BSD
February 27, 2010 BSD