Emergency Monitoring

I was browsing through 2 Day + Performance Tuning Guide documentation for 11g Release 2 (11.2) and found this:
http://docs.oracle.com/cd/E11882_01/server.112/e10822/tdppt_transient.htm#CHDIHIEB
From the Performance Home page, select the Performance menu, then select Emergency Monitoring.
I cannot get to that page...
Does that really apply to 11g?
Could that be because I'm using Database Control?
Anyone have been able to reach this page?
Thanks!

Thanks for replying.
That's what I thought...
(Strange that 11g documentation talks about 12c new features without mentionning...)
Regards,

Similar Messages

  • Error -1074388947 with CANOpen Emergency Create

    Hi All,
    I am attempting to control 15 positioning stages using CANOpen. The newest feature intend to add is to add emergency monitoring to handle errors etc. I have tested this with one stage and all seems to be functioning. I am using the CANOpen library functions.
    Unfortunately when I expand to monitoring all 15 stages I get the following error stating that I have exceeded resource memory:
    Error -1074388947 occurred at CANopen Emergency Create.vi
    Possible reason(s):
    NI-CAN:  (Hex 0xBFF6202D) Exceeded resource limit for queues in shared memory between firmware/driver. The ncReadMult function is not allowed. Solutions: Decrease queue lengths in objects; Set read queue length to at least 2; Decrease number of CAN Objects.
    I have attached a VI snippet which shows the process I am using to control the stages. Essentially I am creating a reference to each node (both for SDO and Emergency - I am not using PDO) and then am passing this through my code to refer to the correct stage. I have included a VI snippet to show how I am creating by references.
    In the snippet the 4th element (index 3) in Array 3 shows this error as do all the following arrays in this index. If I change the order of creation - create Emergency loop before SDO create - the error occurs in the same place so the order does not seem to matter.
    Is there anything I can change in the way I initialise my code - or indeed my whole architecture - which could improve this? My hardware is a PCI CAN2 Series2 (legacy board). My application does not require me to monitor all stages separately - is there a way I could monitor them all using just one reference/object? I tried Node 0 but this gave an error.
    Regards and thanks,
    Dave

    Hi Dave,
    It does sound like a similar problem to what Tom linked to, I was going to point to the same resource. I would suggest checking that you're not exceeding the limit; and this KB is also helpful in determining the upper limit: How Large Can I Make the Read and Write Queues for NI-CAN?
    Regards,
    Imtiaz Chowdhury
    Head of Digital Technologies
    Brand786

  • Ibook remote vga monitors switching off after 30 seconds. (EMERGENCY)

    Hi,
    I run teleprompter for a major band. I use two white dual usb ibooks as they will run OS9. The only real pro prompter application for the mac never made it successfully to os X (accuprompt). I use two mini VGA to VGA adapters and run 100 ft of VGA cable to two VGA monitors. For no reason I can think of one day the monitors started going blank after 30 seconds as if they were going to sleep. The machines are set to NEVER sleep as are the displays, for battery AND power adapter use. I get a message on the monitors saying "not in optimum mode" and I usually just pressed the auto adjust button on the samsung (syncmaster 730B) flat screen and it would work fine. Now they both shut off after 30 seconds with no indication on the laptop displays. I swapped out the monitor and it was the same. I swapped out the computers with (sick) older ones and they worked. Apparently something changed on the computers........ at the same time. Puzzling......
    I deleted the entire preferences folder. Rebuilt desktop, reset nvram and such in open firmware. It is not application based as the desktop disappears from the remote samsungs as well. What could be causing this.... what am I overlooking.... I'm wracking my brain..
    many   Mac OS X (10.4.3)  

    How would one check this Dave?
    Just flex the connections; it would probably be pretty obvious if something's starting to break. There might also be corrosion or dirt in the iBook's video connector that could cause a problem, though I wouldn't think the symptoms would be the monitors going to sleep, but it's possible; different monitors react differently to signal loss.
    Dave, I filter power through a "Monster Power Conditioner"
    (http://www.monstercable.com/power/)
    Even with those power conditioners, it might still be possible to be picking up ground loops in the video feed unless you're tying the entire electrical system, stage and offstage, into a single high-quality ground point. Using a passive hum suppressor transformer or wideband isolation transformer on the VGA feeds might be helpful. The Gefen units I mentioned should also break any ground loops that might be present. For additional information on video ground loops, this site may be helpful (though you may already know all this already).
    Good luck.

  • Monitoring Cisco Emergency Responder

    Hi there,
    is there a way of monitoring CER for unallocated phones?
    Searching for snmp + CER shows up tons of replies because snmp is one of the core items of the CER (used to allocate phones), but I could not find which CER parameters can be monitored with a network management system.
    Thanks in advance,
    Kai

    Hi Jaime,
    I checked the release notes of CER. I found following supported switches in 2960 series:
    Catalyst 2960
    Catalyst 2960-C
    Catalyst 2960-S
    Catalyst 2960X
    Catalyst 2960XR
    I don't see 2960-Plus.
    Thanks,
    VJ

  • ORACLE SERVER AND UNIX TP MONITOR-2

    제품 : ORACLE SERVER
    작성날짜 : 1995-01-24
    Subject: Oracle Server and UNIX Transaction Processing Monitors-2
    Page(3/4)
    This file contains commonly asked questions about Oracle7 Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o Oracle Parallel Server and TP Monitors
         o Oracle and DCE-based TP Monitors
         o Other commonly asked questions
    The questions answered in part 3 provide additional detail to the information
    provided in part 1.
    Oracle Parallel Server and TP Monitors
    ======================================
    How does Oracle Parallel Server (OPS) work with TP Monitors?
    If you are using Oracle-managed transactions, there are no special
    considerations. But if you are using TPM-managed transactions, and
    thus need to use the XA interface, then Oracle requires release 7.1.3
    or later and a special version of the Distributed Lock Manager, called
    the session-based lock manager. This version of the DLM is not yet
    available for all platforms. To understand this restriction, let's take
    a look at one of the technical details of XA.
    The XA specification requires that the Resource Manager be able to
    move a transaction from one process to another, and even to be
    able to commit in a separate process. In Oracle, transactions are
    attached to sessions, so that means that we also have to be able to
    move sessions. Therefore, the session/transaction can't have any state
    which is tied to a particular process. The first generation distributed
    lock managers were all built to use the process id as the lock owner,
    which doesn't work for locks which need to move with the transaction.
    Oracle and DCE-based TP Monitors
    ================================
    How does Oracle interface to the Encina TP monitor? To CICS/6000? I've
    heard that they require OSF DCE facilities in order to run?
    Oracle interfaces to Encina and CICS/6000 just as it does to any other
    TP Monitor. The TP Monitor issues XA commands to control transactions, and
    Oracle executes the commands. Encina and CICS/6000 do use DCE features for
    their own operation. However, this use is transparent to the Oracle Server.
    What DCE facilities can Oracle products take advantage of when working with
    a DCE-based TP Monitor?
    The two most commonly mentioned DCE features which might be useful
    to Oracle users are multi-threading and security. We look at these in
    the subsequent questions in this section.
    Encina documentation suggests that a Resource Manager such as Oracle can
    be either single-threaded or multi-threaded? Which way is Oracle XA
    implemented?
    The Oracle XA implementation is single-threaded, as is any Oracle client.
    Within a single process, at most one thread can access Oracle at a time.
    Does that mean that only a single Encina application can access an instance
    of Oracle transactionally at any given moment?
    No. Oracle XA is only single-threaded within a single application server
    process. Multiple applications can access Oracle simultaneously using XA
    by using different application processes. Encina allows
    (1) serial reuse of a single server by different clients. There are
    two options for this. The server can use long term reservation
    but be defined to be in shared or concurrent access mode, which
    allows the server to be used by another client as soon as an RPC
    completes. Alternatively, the server can use default reservation
    and exclusive mode, which allows the server to be used by another
    client as soon as the current transaction ends.
    (2) concurrent execution by multiple servers, even if they are accessing
    the same Oracle database. These may be executing the same or different
    procedures.
    These two features should let you get as much concurrency as you need.
    Why isn't the Oracle XA library multi-threaded?
    The XA specification specifically states that its use of the phrase
    "thread of control" means a process. If an RM were to multi-thread its
    XA, it would be in violation of the specification. This restriction
    was put place in because at the time the specification was written,
    there were numerous thread packages: if the TM used one, the application
    another, and perhaps the RM yet a third, there's no way it could work.
    As threads standards settle down, the later versions of XA will probably
    relax this restriction.
    Will Oracle change if the XA specification changes?
    Very likely. The exact time frame will of course depend on the priority of
    all work items at that time.
    Does Oracle use DCE security via the TP Monitors?
    The integrity of the connection between a DCE TP Monitor client and DCE
    TP Monitor server is protected by the DCE security functionality.
    Theoretically, the TP Monitor could make the DCE-protected client security
    information available to Oracle. Unfortunately, there's no standard way
    for a TP Monitor to pass security information information to a Resource
    Manager such as Oracle. Oracle is leading an effort to extend the X/Open
    model to allow use of the security information provided by the Monitor.
    In the meantime, the basic DCE security features such as encryption are
    useful within TP Monitors.
    Effective use of DCE security would normally also mean that the security of
    the TP Monitor client be passed through the TP Monitor, through the Oracle
    client (application server), to the Oracle Server, and possibly on
    to other Oracle Servers through database links. The ability to transfer
    security information to other processes, called delegation, is missing
    in DCE version 1.0. DCE version 1.1, expected to emerge in late 1994,
    has some delegation features. Oracle is examining these features to see
    how they might be used.
    Are there any special considerations for CICS/6000?
    There are two:
    (1) It is inefficient to run without XA. CICS/6000 is designed to
    use XA. It uses XA so that the CICS server can log on to Oracle
    when it starts, after which it makes that Oracle connection available
    to any transaction it executes. If you don't use XA, the CICS server
    does not itself log on to Oracle so each transaction has to log on
    and log off - a very expensive mode of operation. Also, it is very
    un-cics-like in that the application does the log{on,off} and also
    commits - in a mainframe CICS database program CICS would implicitly
    do these operations. Oracle does not recommend this mode because of the
    performance penalty.
    (2) CICS servers are generic and dynamically load application modules.
    In order for these modules to access the Oracle connection made by
    CICS, the applications must be built with a shared object version of
    the Oracle libraries. This is an installation option on platforms which
    support CICS/6000 and other products using its architecture such as
    CICS 9000.
    Other commonly asked questions
    ==============================
    What other Resource Managers can be included in an Oracle XA transaction?
    Several other relational database vendors have an XA implementation
    available or in progress. There is an XA C-ISAM product from
    Gresham Telecomputing. There are also Resource Managers contained
    within some of the TP Monitors which can be coordinated in the same
    transaction. For example, CICS/6000 has VSAM files and other data
    stores, Encina has its RQS queuing system, and Tuxedo has its /Q queuing
    system.
    What is Recoverable Queuing Service (RQS) and how does it interoperate with
    Oracle7 and Encina? What about /Q?
    Recoverable Queuing Service is a feature provided by Encina which allows
    transactional, distributed queuing (enqueue/dequeue). Tuxedo has a similar
    product called /Q. Because these products are themselves coordinated by the
    TM component of the TP Monitor, their queue operations are atomically
    coordinated with with operations on XA Resource Managers such as Oracle7
    Server. That is, they can atomically put something on one of their queues
    and commit an Oracle transaction, then at some later time dequeue an
    entry atomically with doing some other Oracle transaction. The queue
    system guarantees that the message will not be lost or transmitted twice.
    Can I mix TP Monitor applications with standard Oracle7 Server applications?
    Yes, you can have existing Oracle applications connected to the database
    with alongside TPM applications against the same database. The TPM does
    not manage the whole database, just those transactions which are started
    by the TPM. The Oracle Server will properly handle concurrency control
    between the transactions managed by itself and those managed by the TPM.
    Is Oracle planning to change its tools to be more suitable for TP Monitors?
    With Oracle Procedure Builder 1.5, to be available with CDE2,
    Oracle will provide a foreign function interface that allows you to
    dynamically set up PL/SQL calls that access C functions. In other
    words, you can access C routines in Windows DLLs from within your
    PL/SQL procedures. This will allow PL/SQL under Windows easy access to
    TP Monitor APIs.
    Does Oracle7 Server itself use XA-compliant TPMs as the interface to
    foreign RMs?
    No, for this purpose Oracle Server uses the SQL*Connect products or the new
    Transparent and Procedural Gateway products.
    Does Oracle7 Server use XA to coordinate Oracle7-only distributed
    transactions?
    No, it uses an internal mechanism.
    Can database links be used with XA?
    If an Oracle7 database is running under XA, it can access other Oracle7
    databases through database links, with some restrictions. First, the
    access to the other database must use SQL*Net V2 and be running MTS.
    Second, it must currently be to another Oracle7 database. Assuming those
    restrictions, the Oracle 7 database can do distributed update to another
    Oracle 7 database by using a database link, whether it is started by an
    Oracle application or a TP Monitor application. The TPM will see Oracle
    as only a single RM, but Oracle7 will propagate all the transaction
    commands to the other database, including the two-phase commit. If
    the transaction is started by a TP Monitor application and is using XA,
    it can also update non-Oracle resources managed by the TPM. If it
    is started from an Oracle application, it can only include resources
    managed by Oracle.
    Here's a sample configuration:
    | TPM | | TPM |
    | client | | client |
    | |
    | |
    | TPM |
    | |
    | |
    | Oracle | Forms, Forms, | Oracle | | non-XA | | XA |
    | client | Plus, Plus, | client | | TPM | | TPM |
    --------- Pro, Pro, --------- | server | | server |
    | Financials, Financials, | |(note 1)| ----------
    | etc. etc. | ---------- |
    | | | |
    | SQL | SQL | SQL | XA
    | commit | commit | commit | commit
    | | | |
    | Oracle | | Oracle | | Oracle | | Oracle |
    | server | | server | | server | | server |
    | | | |
    | | | |
    | | | |
    | Database 1 | | Database 2 |
    | | | |
    | A | A
    | | dblink to database 1 | |
    | ------------------------------------ |
    | |
    dblink to database 2
    Note 1: Oracle will work having both XA and non-XA servers but some TPMs
    may have restrictions on this.
    Are multiple direct connections possible from a Pro* program?
    Using XA, you can not only specify multiple direct connections to Oracle7
    databases, you can also update them both in the SAME transaction. The
    way to do this is to use a precompiler feature called a named database.
    When you use a named database, you qualify the SQL statement with the
    database name. For example, you write EXEC SQL AT dbname UPDATE emp ....
    We have a complementary feature in the xa open string to let the user
    associate the name with a particular RM instance, called the DB clause.
    You will also want to use the SqlNet clause in the open string so you
    can give the two different SIDs. This clause does not require the use of
    the SQL*Net product, it is just a naming convention. For more information,
    see Oracle7 Server for UNIX Administrator's Reference Guide.
    Some TP Monitors may not support having multiple Resource Mangers in the
    same server; check with the TPM vendor.
    Is there any collateral available for XA or TP Monitors?
    Oracle At Work 52684.0692
    Oracle7 Server for UNIX Administrator's #A10324-1
    Reference Guide
    Guide to Oracle's Products and Services #A10560
    Oracle7 Server and CICS/6000               #A14200
    Where can I get more information on the DTP model?
    X/Open's address is
    X/Open company Ltd (Publications)
    P O Box 109
    Penn
    High Wycombe
    Bucks HP10 8NP
    Tel: +44 (0)494 813844
    Fax: +44 (0)494 814989
    Request
    G307 Distributed Transaction Processing: Reference Model Version 2
    X/Open Guide G307 ISBN 1-859120-19-9 28cm.44p.pbk.220g.11/93
    Page(4/4)
    This file contains commonly asked questions about Oracle Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o Performance with Oracle Server and TP monitors
         o Performance using Oracle's XA Library
    The questions answered in part 4 provide additional detail to the information
    provided in part 1.
    Performance with Oracle Server and TP Monitors
    ==============================================
    I have heard that Transaction Processing Monitors (TPMs) will increase
    Oracle Server performance. Is this true?
    Several hardware and TPM vendors have made the claim that TPMs
    will increase RDBMS performance. This claim is based on TPC-A
    benchmarks. The key point to understand about TPC-A is that it
    requires, for every transaction-per-second, ten times that many
    users to be connected. For example, to get 600 TPS, you need 6000
    users. The next question will answer in more detail how the the
    three-tier architecture addresses this requirement, but first let's
    look more generally at what TP Monitors can and can't do to improve
    performance.
    TP Monitors can provide better performance:
    (1) When there are more than several hundred users connected.
         This is because of the TP Monitor's role in the three-tier
         architecture, described in the next question. In this
         architecture, terminal handling is offloaded to one or more
         separate machines, freeing up those cycles to do database work.
         Note that this does NOT mean that Oracle itself runs faster,
         just that we've given it more CPU cycles to use.
    (2) When, because of the high potential concurrency of requests,
         significant resource contention exists. Use of a TP Monitor can
         limit the degree of concurrency and thus reduce contention.
    TP Monitors can not provide better performance:
    (1) For existing applications. The applications must be designed
         to fit the TP Monitor architecture.
    (2) For applications which are highly interactive in their use of
         the database. These applications put many messages
         through the transport system, and the TP Monitor is not as
         efficient as SQL*Net for point-to-point communication.
    (3) For CPU intensive single-query decision support. When executing
         a single large command, Oracle query facilities work efficiently,
         especially with the use of Oracle Parallel Query, available in 7.1.
    How does the three-tier solution help TPC-A, or other situations with
    thousands of on-line users?
    The TPC-A test calls for a large number of users to produce a given
    result. In the high-end results we produced in June, 1992, for example,
    6150 terminals were simulated to produce 618 TPC-A transactions.
    Thus, terminal concentration accounts for a large portion of the total
    processing time used.
    First, let's look at how the Multi Threaded Server would work for
    this benchmark. In this case, there are many client processes,
    but only a few server processes, which handle client requests on a
    first-come first serve basis. When they are done with a request,
    they take another client's request.
    ORACLE7 CLIENT/SERVER ARCHITECTURE WITH MULTI THREADED SERVER
    | Client | | Server |
    | __________ |______________|_____ _____________ _____________ |
    | | Client | | SQL*Net | |_|Dispatcher | | | |
    | | Process| | | ____| Process |___| | |
    | |________| | | | __|___________| | | |
    |____________| | | | | | | | |
    | | | | | | Oracle7 | |
    ______________ | | | __|__|____ | Server | |
    | Client | | | | __|_|_____ | | | |
    | __________ | | | | | Shared | |____| | |
    | | Client | | SQL*Net | | | | Server |_|____| | |
    | | Process|_|______________|__| | | Process|_| | | |
    | |________| | | | |________| |___________| |
    |____________| | | |
    | | |
    ______________ | | |
    | Client | | | |
    | __________ | | | |
    | | Client | | SQL*Net | | |
    | | Process|_|______________|____| |
    | |________| | | |
    |____________| | |
    |_______________________________________|
    Client processes = N Dispatcher processes >= 1
    Shared server processes >= 1
    If there are 500 clients in this environment, there will be one or more
    dispatcher processes, dynamically tunable, and one or more shared
    server processes, dynamically tunable, on the server. The reduction
    in the total number of processes handled by the server system
    results in more processing time available for RDBMS activity. Thus
    higher RDBMS transaction throughput can be obtained on the
    server system.
    But the problem for the TPC-A, and for certain large customer
    configurations, is not the only ability of the Oracle Server to
    process transactions, but also the ability of the operating
    system to handle huge numbers of incoming connections.
    There is one incoming connection for each client. Most UNIX
    operating systems have a limit on how many such connections they can
    handle. Even if a particular operating system allows a large number of
    connections, each takes some amount of overhead to manage.
    In order to service all 6150 terminals, we selected a 3-tier hardware
    environment where the middle tier, using a TPM, acted as a terminal
    concentrator. The high-end TPC-A architecture looked like the following.
    The Application Servers, which contain the Pro*C statements used to
    perform the transaction also run on the terminal concentrator machine
    in order to offload as much work from the database serve as possible.
    They send the compiled SQL over SQL*Net to the Oracle7 Server processes.
    ORACLE7 TPS-A CLIENT/SERVER ARCHITECTURE
    | Client | | Terminal | | Server |
    | ________ | | Concentrator | | |
    | | Client | |TPM | | | |
    | | Process|_|_____|__ _____ | | |
    | |________| |Comm | | | | | | |
    |____________| | | | | | | |
    | |__| | | | |
    ____________ | | TPM | | | |
    | Client | | ___| | _______ | | ________ _______ |
    | ________ | | | | |_| |__|_______|__| Oracle | | | |
    | | Client | |TPM | | | | |Appl. | |SQL*Net| | Server |__| | |
    | | Process|_|_____|_| |_____| |Server | | | | Process| | | |
    | |________| |Comm | |_______| | | |________| | | |
    |____________| | | | | | |
    |_______________________| | | | |
    | | | |
    ____________ _______________________ | |Oracle7| |
    | Client | | Terminal | | |Server | |
    | ________ | | Concentrator | | | | |
    | | Client | |TPM | | | | | |
    | | Process|_|_____|__ _____ | | __________ | | |
    | |________| |Comm | | | | _______ |SQL*Net| | Oracle | | | |
    |____________| | | | |_| |__|_______|__| Server |__| | |
    | |__| | |Appl. | | | | Process| | | |
    ____________ | | TPM | |Server | | | |________| |_______| |
    | Client | | ___| | |_______| | | |
    | ________ | | | | | | | |
    | | Client | |TPM | | | | | | |
    | | Process|_|_____|_| |_____| | | |
    | |________| |Comm | | | |
    |____________| | | | |
    |_______________________| |________________________|
    Clients = 6150 Terminal concentrators = 17
    TP Monitor instances = 17
    Application server processes Oracle Server processes
    = 17*8 = 17*8
    The TPM is the software component of the terminal concentrator. In this role
    it offloads terminal handling from the the machine running Oracle Server.
    Since more than one terminal concentrator can be configured, whereas the
    database in this case had to run on a single machine, concentrator machines
    can be added until the performance of the back-end machine was optimized.
    This three-tier solution resulted in the outstanding transaction throughput
    announced with Oracle7 Server. Even with Oracle Parallel Server, it may pay
    to offload the terminal handling so that the cluster can be exclusively used
    for database operations.
    Can you summarize the performance discussion for me?
    Depending on the number of users required, different architectures may be
    used in a client/server environment to maximize performance:
    1) For a small number of users, the traditional Oracle two-task
    architecture can be used. In this case, there is a one-to-one
    correspondence between client processes and server processes. It's
    simple, straightforward, and efficient.
    2) For a large number of users, Multi Threaded Server might be a better
    approach. Although some tuning may be required, Multi Threaded Server
    can handle a relatively large number of users for each machine size
    compared to the traditional Oracle approach. Using this approach,
    customers will be able to handle many hundreds of users on many
    platforms. Furthermore, current Oracle applications can move to this
    environment without change.
    3) For a very large number of users, where transactions are simple and
    terminal input concentration is the overriding performance issue, a
    3-tier architecture incorporating a TPM may be useful. In this case,
    terminal concentration is handled by the TPM in the middle tier. As
         you might expect, it is a more complex environment requiring more
         system management. For existing Oracle customers, significant Oracle
    application modifications will be required.
    Oracle provides all of these choices.
    Performance using Oracle's XA Library
    =====================================
    Are there any performance implications to using the XA library (in other
    words, to using TPM-managed transactions)?
    (1) The XA library imposes some performance penalty. You should use
    TPM-managed transactions only if you actually need them. Even if you
    are getting the one-phase commit optimization, the code path is
    longer because we need to map back and forth between external
    formats and internal ones. Also, prior to 7.1, XA requires you
    to release all cursors at the end of a transaction, which results
    in extra parsing. Even with shared cursors, there is time spent
    looking up the one you need and re-validating it. This has been
    improved for 7.1.
    (2) If you need to use two-phase commit, this will incur additional cost
    since extra I/Os are required. If you do need 2PC, you need to account
    for that when sizing the application.
    (3) Although some TPMs allow parallel execution of services (such as Tuxedo's
    "tpacall"), this will not normally enhance performance unless different
    resource managers are being used. In fact, Oracle Server must serialize
    accesses to the same transaction by the same Oracle instance, and the
    block/resume code will in fact degrade performance in that case compared
    to running the services sequentially.

    hello,
    the role is the same on all plattforms. the reports server takes requests for running reports, spawns an engine that executes the request. in addition to that, the server also provides scheduling services and security features for the reports environment.
    regards,
    the oracle reports team

  • Is it possible to force a fixed Application to open in a Secondary Monitor?

    This is my first time actively using a forum, so forgive me if I'm unclear with my question or if I'm unaware of forum common sense or etiquette.
    I've been running a Multi-Monitor system for awhile now at my office. I ran into a few problems when I first set it up, but was able to resolve many issues with many work-arounds. In truth, this is one of the same major problems I was having before.
    As it says in my details, I have an iMac with a Wacom Cintiq 21UX via Mini DisplayPort to DVI, and an Apple Cinema Display via Arkview USB Display Adapter. I do a lot of graphical work amongst my many tasks, so the Cintiq is typically my main input device. I have it set in a Portrait position, which I prefer greatly over Landscape.
    My problem is that to use many of the graphical applications, Adobe anything, I have to set it as the main monitor. Since Apple doesn't use application containers, at least, not in a way that allows you to drag the main toolbar. This solution, of course, I learned after a lot of struggle. It works and I'm fine with it now, but I've recently been called upon to use Final Cut and Motion for some projects and this problem has again reared its head, but in a different way.
    I've programs set up all over my three screens; sized and set to where I like them and are most efficient, and across multiple Spaces. To properly run Final Cut, a resolution of 1280x800 is strongly recommended. Since I'm running Portrait, mine is set to 1200x1600. I didn't think much of Final Cut's initial warning at the time, since any windows caught outside the screen I was certain I could rescue with a trusty Applescript, written to collect all windows to the main screen. Which I discovered was a problem when running Final Cut from a laptop that was dual-monitored, but once you take away the secondary monitor the Final Cut windows remain floating aimlessly out of screen. They were floating off-screen, as I thought, and fixed it with the applescript. While I was working though, I was confused on where the **** the splice tool went. I looked everywhere in the application I could to find it, but it wasn't until I called a friend and he assured me that the tool actually did exist that I remember the teeny-tiny tool panel that would typically reside next to the timeline. The applescript can't pull it for some reason.
    So my question, *is there a way in which you can change the display an application starts in?* (bolded for ease of discovery in this long post) what would fixedly open in the main display instead opening to a secondary monitor. Or, as consolation, possibly rescuing that tiny tool panel? Early on I tried keeping a shortcut key set to switch the main monitors back and forth, but found that applications will switch with them, applications I didn't want to switch. Plus, the Wacom Pen has to be re-calibrated when the Cintiq is switched to the secondary monitor, and then, of course, re-calibrated again when it's switched back to the main.
    Any help would be greatly appreciated. Thank you.

    All my Monitors are set to their native resolutions, 1280x800 is Final Cut's suggested optimal resolution. My Cintiq is a Tablet Monitor, one that allows you to write or draw upon the screen itself, as such, it's set upon an adjustable stand that will let you place the Tablet Monitor upright, semi-flat against the desk, or anywhere in-between, in addition to 360 degree rotation in its flat position. This means that the Tablet Monitor comes with two native resolutions, one for Landscape and one for Portrait. The Cintiq is purposely designed to allow it to be set in a Portrait position, for the comfort of the User. 1200x1600 is just as native for the Cintiq as 1600x1200. Also, my Office Desktop set-up is, God-willing, a permanent set-up; I don't disconnect Monitors, and they are set to Extended Desktop Mode.
    My aim was to avoid switching back or forth between resolutions or Mirroring. This will work, yes, but having to do it every time I need to use Final Cut, or any other such program with odd monitor requirements, is a hassle. With all the various windows and applications I have running at any one time, I'll be wasting time moving and resizing windows across multiple Spaces back to where they were every time I need to run Final Cut, and re-calibrating the pen to the new resolution. Which is also a little embarrassing when I need to demo a clip for my bosses and co-workers and I have to spend time, in which I could be explaining things, tiding up my desktops. It would be ideal to have it prepared before they got there, (actually, ideal would be not having to prep it in the first place) but not all meetings are scheduled and planned.
    As for windows that get lost in space, that's what the Applescript was for, but apparently that little tool panel, which is wholly more important than it's size suggests, doesn't register as a window and gets left behind.
    So my hoped for solution is a way in which to force a Program that would normally load onto the Main Monitor to instead load on to a chosen Secondary Monitor, one that fills the necessary resolution requirements of said Program. I couldn't care less about the Applications need for the Main Toolbar since I run Secondbar anyhow.
    This isn't a vital emergency though, I'm just trying to find a solution for an annoyance and to make the whole process more efficient. Oh well, C'est la vie.
    Thank you for your reply Dennis.
    Message was edited by: TimR.NSC

  • Fsck problem Diagnosis: Systemd dropping to emergency console

    Title says it all. I have no idea why.
    First, it said fsck was unable and I had to enter fsck /dev/sdaX manually. Then emergency console dropped on me.
    The thing is that if I continue without giving the password thus entering to console, computer loads just fine.
    Probably problems are quoted from the next complete journal are as follows:
    -- The start-up result is done.
    Aug 26 09:54:39 machine kernel: sound hdaudioC0D0: autoconfig: line_outs=1 (0xd/0x0/0x0/0x0/0x0) type:speaker
    Aug 26 09:54:39 machine kernel: sound hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
    Aug 26 09:54:39 machine kernel: sound hdaudioC0D0: hp_outs=1 (0xb/0x0/0x0/0x0/0x0)
    Aug 26 09:54:39 machine kernel: sound hdaudioC0D0: mono: mono_out=0x0
    Aug 26 09:54:39 machine kernel: sound hdaudioC0D0: inputs:
    Aug 26 09:54:39 machine kernel: sound hdaudioC0D0: Internal Mic=0x11
    Aug 26 09:54:39 machine kernel: sound hdaudioC0D0: Mic=0xc
    Aug 26 09:54:40 machine kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input9
    Aug 26 09:54:40 machine kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
    Aug 26 09:54:40 machine kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
    Aug 26 09:54:40 machine kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
    Aug 26 09:54:40 machine systemd-fsck[216]: /dev/sda3: Inodes that were part of a corrupted orphan linked list found.
    Aug 26 09:54:40 machine systemd-fsck[216]: /dev/sda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    Aug 26 09:54:40 machine systemd-fsck[216]: (i.e., without -a or -p options)
    Aug 26 09:54:40 machine systemd-fsck[216]: fsck failed with error code 4.
    Aug 26 09:54:40 machine systemd-fsck[216]: Running request emergency.target/start/replace
    Aug 26 09:54:40 machine systemd[1]: Stopped TLP system startup/shutdown.
    -- Subject: Unit tlp.service has finished shutting down
    Systemd Journal:
    -- Logs begin at Fri 2014-04-18 01:39:00 EEST, end at Tue 2014-08-26 10:24:28 EE
    Aug 26 09:54:35 machine systemd-journal[149]: Runtime journal is using 8.0M (max
    Aug 26 09:54:35 machine systemd-journal[149]: Runtime journal is using 8.0M (max
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys cpuset
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys cpu
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys cpuacct
    Aug 26 09:54:35 machine kernel: Linux version 3.16.1-1-zen (nobody@var-lib-archb
    Aug 26 09:54:35 machine kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux-zen
    Aug 26 09:54:35 machine kernel: e820: BIOS-provided physical RAM map:
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000000000000-0x00000000000
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000000088000-0x00000000000
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001ff
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000020200000-0x00000000400
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000040004000-0x00000000400
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000040005000-0x000000009a0
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009a0bf000-0x000000009a4
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009a4bf000-0x000000009ae
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009aebf000-0x000000009af
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009afbf000-0x000000009af
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009afff000-0x000000009af
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009b000000-0x000000009f9
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000eff
    lines 1-23...skipping...
    -- Logs begin at Fri 2014-04-18 01:39:00 EEST, end at Tue 2014-08-26 10:24:28 EEST. --
    Aug 26 09:54:35 machine systemd-journal[149]: Runtime journal is using 8.0M (max allowed 192.4M, trying to leave 288.7M free of 1.8G available → current limit 192.4M).
    Aug 26 09:54:35 machine systemd-journal[149]: Runtime journal is using 8.0M (max allowed 192.4M, trying to leave 288.7M free of 1.8G available → current limit 192.4M).
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys cpuset
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys cpu
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys cpuacct
    Aug 26 09:54:35 machine kernel: Linux version 3.16.1-1-zen (nobody@var-lib-archbuild-extra-x86_64-heftig-mkpkg-23970) (gcc version 4.9.1 (GCC) ) #1 ZEN SMP PREEMPT Fri Aug 15 22:06:09 UTC 2014
    Aug 26 09:54:35 machine kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux-zen root=UUID=09b369ae-e074-442f-ae02-101a7421b569 rw drm.rnodes=1
    Aug 26 09:54:35 machine kernel: e820: BIOS-provided physical RAM map:
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000087fff] usable
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000000088000-0x00000000000bffff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000040005000-0x000000009a0befff] usable
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009a0bf000-0x000000009a4befff] type 20
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009a4bf000-0x000000009aebefff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009aebf000-0x000000009afbefff] ACPI NVS
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009afbf000-0x000000009affefff] ACPI data
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009afff000-0x000000009affffff] usable
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x000000009b000000-0x000000009f9fffff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x00000000feb00000-0x00000000feb03fff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x00000000ffd80000-0x00000000ffffffff] reserved
    Aug 26 09:54:35 machine kernel: BIOS-e820: [mem 0x0000000100000000-0x000000015f5fffff] usable
    Aug 26 09:54:35 machine kernel: NX (Execute Disable) protection: active
    Aug 26 09:54:35 machine kernel: efi: EFI v2.31 by INSYDE Corp.
    Aug 26 09:54:35 machine kernel: efi: ACPI=0x9affe000 ACPI 2.0=0x9affe014 SMBIOS=0x9aebef98
    Aug 26 09:54:35 machine kernel: efi: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000001000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem01: type=7, attr=0xf, range=[0x0000000000001000-0x000000000006f000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem02: type=4, attr=0xf, range=[0x000000000006f000-0x0000000000070000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem03: type=7, attr=0xf, range=[0x0000000000070000-0x0000000000088000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem04: type=6, attr=0x800000000000000f, range=[0x0000000000088000-0x00000000000a0000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem05: type=2, attr=0xf, range=[0x0000000000100000-0x0000000001048000) (15MB)
    Aug 26 09:54:35 machine kernel: efi: mem06: type=7, attr=0xf, range=[0x0000000001048000-0x0000000002000000) (15MB)
    Aug 26 09:54:35 machine kernel: efi: mem07: type=2, attr=0xf, range=[0x0000000002000000-0x0000000002f48000) (15MB)
    Aug 26 09:54:35 machine kernel: efi: mem08: type=7, attr=0xf, range=[0x0000000002f48000-0x0000000020000000) (464MB)
    Aug 26 09:54:35 machine kernel: efi: mem09: type=0, attr=0xf, range=[0x0000000020000000-0x0000000020200000) (2MB)
    Aug 26 09:54:35 machine kernel: efi: mem10: type=7, attr=0xf, range=[0x0000000020200000-0x0000000037976000) (375MB)
    Aug 26 09:54:35 machine kernel: efi: mem11: type=2, attr=0xf, range=[0x0000000037976000-0x0000000037cb3000) (3MB)
    Aug 26 09:54:35 machine kernel: efi: mem12: type=7, attr=0xf, range=[0x0000000037cb3000-0x0000000040004000) (131MB)
    Aug 26 09:54:35 machine kernel: efi: mem13: type=0, attr=0xf, range=[0x0000000040004000-0x0000000040005000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem14: type=7, attr=0xf, range=[0x0000000040005000-0x0000000068bcb000) (651MB)
    Aug 26 09:54:35 machine kernel: efi: mem15: type=2, attr=0xf, range=[0x0000000068bcb000-0x000000008e6c0000) (602MB)
    Aug 26 09:54:35 machine kernel: efi: mem16: type=4, attr=0xf, range=[0x000000008e6c0000-0x000000008e6e0000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem17: type=7, attr=0xf, range=[0x000000008e6e0000-0x0000000090ca6000) (37MB)
    Aug 26 09:54:35 machine kernel: efi: mem18: type=4, attr=0xf, range=[0x0000000090ca6000-0x00000000916b0000) (10MB)
    Aug 26 09:54:35 machine kernel: efi: mem19: type=7, attr=0xf, range=[0x00000000916b0000-0x00000000918a1000) (1MB)
    Aug 26 09:54:35 machine kernel: efi: mem20: type=1, attr=0xf, range=[0x00000000918a1000-0x00000000918bf000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem21: type=7, attr=0xf, range=[0x00000000918bf000-0x000000009716c000) (88MB)
    Aug 26 09:54:35 machine kernel: efi: mem22: type=4, attr=0xf, range=[0x000000009716c000-0x00000000979ee000) (8MB)
    Aug 26 09:54:35 machine kernel: efi: mem23: type=7, attr=0xf, range=[0x00000000979ee000-0x0000000097cef000) (3MB)
    Aug 26 09:54:35 machine kernel: efi: mem24: type=4, attr=0xf, range=[0x0000000097cef000-0x0000000097d36000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem25: type=7, attr=0xf, range=[0x0000000097d36000-0x0000000097d47000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem26: type=4, attr=0xf, range=[0x0000000097d47000-0x0000000097d87000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem27: type=7, attr=0xf, range=[0x0000000097d87000-0x0000000097d91000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem28: type=4, attr=0xf, range=[0x0000000097d91000-0x0000000097db3000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem29: type=7, attr=0xf, range=[0x0000000097db3000-0x0000000097db5000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem30: type=4, attr=0xf, range=[0x0000000097db5000-0x0000000097db7000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem31: type=7, attr=0xf, range=[0x0000000097db7000-0x0000000097db8000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem32: type=4, attr=0xf, range=[0x0000000097db8000-0x0000000097df9000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem33: type=7, attr=0xf, range=[0x0000000097df9000-0x0000000097e00000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem34: type=4, attr=0xf, range=[0x0000000097e00000-0x0000000097e09000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem35: type=7, attr=0xf, range=[0x0000000097e09000-0x0000000097e0a000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem36: type=4, attr=0xf, range=[0x0000000097e0a000-0x0000000097e17000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem37: type=7, attr=0xf, range=[0x0000000097e17000-0x0000000097e1a000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem38: type=4, attr=0xf, range=[0x0000000097e1a000-0x0000000097f51000) (1MB)
    Aug 26 09:54:35 machine kernel: efi: mem39: type=7, attr=0xf, range=[0x0000000097f51000-0x0000000097f52000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem40: type=4, attr=0xf, range=[0x0000000097f52000-0x0000000097f55000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem41: type=7, attr=0xf, range=[0x0000000097f55000-0x0000000097f58000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem42: type=4, attr=0xf, range=[0x0000000097f58000-0x0000000097f7a000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem43: type=7, attr=0xf, range=[0x0000000097f7a000-0x0000000097f7c000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem44: type=4, attr=0xf, range=[0x0000000097f7c000-0x0000000097fa0000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem45: type=7, attr=0xf, range=[0x0000000097fa0000-0x0000000097faa000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem46: type=4, attr=0xf, range=[0x0000000097faa000-0x0000000097fd7000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem47: type=7, attr=0xf, range=[0x0000000097fd7000-0x0000000097fde000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem48: type=4, attr=0xf, range=[0x0000000097fde000-0x0000000098032000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem49: type=7, attr=0xf, range=[0x0000000098032000-0x0000000098033000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem50: type=4, attr=0xf, range=[0x0000000098033000-0x0000000098049000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem51: type=7, attr=0xf, range=[0x0000000098049000-0x000000009804a000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem52: type=4, attr=0xf, range=[0x000000009804a000-0x0000000098393000) (3MB)
    Aug 26 09:54:35 machine kernel: efi: mem53: type=7, attr=0xf, range=[0x0000000098393000-0x000000009839c000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem54: type=4, attr=0xf, range=[0x000000009839c000-0x00000000983b6000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem55: type=7, attr=0xf, range=[0x00000000983b6000-0x00000000983b8000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem56: type=4, attr=0xf, range=[0x00000000983b8000-0x00000000983bf000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem57: type=7, attr=0xf, range=[0x00000000983bf000-0x00000000983c0000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem58: type=4, attr=0xf, range=[0x00000000983c0000-0x00000000998bf000) (20MB)
    Aug 26 09:54:35 machine kernel: efi: mem59: type=7, attr=0xf, range=[0x00000000998bf000-0x0000000099d1e000) (4MB)
    Aug 26 09:54:35 machine kernel: efi: mem60: type=2, attr=0xf, range=[0x0000000099d1e000-0x0000000099d28000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem61: type=3, attr=0xf, range=[0x0000000099d28000-0x000000009a0bf000) (3MB)
    Aug 26 09:54:35 machine kernel: efi: mem62: type=5, attr=0x800000000000000f, range=[0x000000009a0bf000-0x000000009a4bf000) (4MB)
    Aug 26 09:54:35 machine kernel: efi: mem63: type=6, attr=0x800000000000000f, range=[0x000000009a4bf000-0x000000009a6bf000) (2MB)
    Aug 26 09:54:35 machine kernel: efi: mem64: type=0, attr=0xf, range=[0x000000009a6bf000-0x000000009aebf000) (8MB)
    Aug 26 09:54:35 machine kernel: efi: mem65: type=10, attr=0xf, range=[0x000000009aebf000-0x000000009afbf000) (1MB)
    Aug 26 09:54:35 machine kernel: efi: mem66: type=9, attr=0xf, range=[0x000000009afbf000-0x000000009afff000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem67: type=4, attr=0xf, range=[0x000000009afff000-0x000000009b000000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem68: type=7, attr=0xf, range=[0x0000000100000000-0x000000015f600000) (1526MB)
    Aug 26 09:54:35 machine kernel: efi: mem69: type=0, attr=0x0, range=[0x00000000000a0000-0x00000000000c0000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem70: type=0, attr=0x0, range=[0x000000009b000000-0x000000009fa00000) (74MB)
    Aug 26 09:54:35 machine kernel: efi: mem71: type=11, attr=0x8000000000000001, range=[0x00000000e0000000-0x00000000f0000000) (256MB)
    Aug 26 09:54:35 machine kernel: efi: mem72: type=11, attr=0x8000000000000001, range=[0x00000000feb00000-0x00000000feb04000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem73: type=11, attr=0x8000000000000001, range=[0x00000000fec00000-0x00000000fec01000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem74: type=11, attr=0x8000000000000001, range=[0x00000000fed10000-0x00000000fed1a000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem75: type=11, attr=0x8000000000000001, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem76: type=11, attr=0x8000000000000001, range=[0x00000000fee00000-0x00000000fee01000) (0MB)
    Aug 26 09:54:35 machine kernel: efi: mem77: type=11, attr=0x8000000000000000, range=[0x00000000ffd80000-0x0000000100000000) (2MB)
    Aug 26 09:54:35 machine kernel: SMBIOS 2.7 present.
    Aug 26 09:54:35 machine kernel: DMI: Hewlett-Packard HP Pavilion g6 Notebook PC/183E, BIOS F.25 05/29/2013
    Aug 26 09:54:35 machine kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    Aug 26 09:54:35 machine kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Aug 26 09:54:35 machine kernel: AGP: No AGP bridge found
    Aug 26 09:54:35 machine kernel: e820: last_pfn = 0x15f600 max_arch_pfn = 0x400000000
    Aug 26 09:54:35 machine kernel: MTRR default type: uncachable
    Aug 26 09:54:35 machine kernel: MTRR fixed ranges enabled:
    Aug 26 09:54:35 machine kernel: 00000-9FFFF write-back
    Aug 26 09:54:35 machine kernel: A0000-BFFFF uncachable
    Aug 26 09:54:35 machine kernel: C0000-E7FFF write-protect
    Aug 26 09:54:35 machine kernel: E8000-EFFFF write-combining
    Aug 26 09:54:35 machine kernel: F0000-FFFFF write-protect
    Aug 26 09:54:35 machine kernel: MTRR variable ranges enabled:
    Aug 26 09:54:35 machine kernel: 0 base 000000000 mask F80000000 write-back
    Aug 26 09:54:35 machine kernel: 1 base 080000000 mask FE0000000 write-back
    Aug 26 09:54:35 machine kernel: 2 base 09B000000 mask FFF000000 uncachable
    Aug 26 09:54:35 machine kernel: 3 base 09C000000 mask FFC000000 uncachable
    Aug 26 09:54:35 machine kernel: 4 base 0FFC00000 mask FFFC00000 write-protect
    Aug 26 09:54:35 machine kernel: 5 base 100000000 mask F80000000 write-back
    Aug 26 09:54:35 machine kernel: 6 base 15F600000 mask FFFE00000 uncachable
    Aug 26 09:54:35 machine kernel: 7 base 15F800000 mask FFF800000 uncachable
    Aug 26 09:54:35 machine kernel: 8 base 160000000 mask FE0000000 uncachable
    Aug 26 09:54:35 machine kernel: 9 disabled
    Aug 26 09:54:35 machine kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Aug 26 09:54:35 machine kernel: e820: last_pfn = 0x9b000 max_arch_pfn = 0x400000000
    Aug 26 09:54:35 machine kernel: Scanning 1 areas for low memory corruption
    Aug 26 09:54:35 machine kernel: Base memory trampoline at [ffff88000007e000] 7e000 size 24576
    Aug 26 09:54:35 machine kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    Aug 26 09:54:35 machine kernel: [mem 0x00000000-0x000fffff] page 4k
    Aug 26 09:54:35 machine kernel: BRK [0x02b24000, 0x02b24fff] PGTABLE
    Aug 26 09:54:35 machine kernel: BRK [0x02b25000, 0x02b25fff] PGTABLE
    Aug 26 09:54:35 machine kernel: BRK [0x02b26000, 0x02b26fff] PGTABLE
    Aug 26 09:54:35 machine kernel: init_memory_mapping: [mem 0x15f400000-0x15f5fffff]
    Aug 26 09:54:35 machine kernel: [mem 0x15f400000-0x15f5fffff] page 2M
    Aug 26 09:54:35 machine kernel: BRK [0x02b27000, 0x02b27fff] PGTABLE
    Aug 26 09:54:35 machine kernel: init_memory_mapping: [mem 0x15c000000-0x15f3fffff]
    Aug 26 09:54:35 machine kernel: [mem 0x15c000000-0x15f3fffff] page 2M
    Aug 26 09:54:35 machine kernel: init_memory_mapping: [mem 0x100000000-0x15bffffff]
    Aug 26 09:54:35 machine kernel: [mem 0x100000000-0x15bffffff] page 2M
    Aug 26 09:54:35 machine kernel: BRK [0x02b28000, 0x02b28fff] PGTABLE
    Aug 26 09:54:35 machine kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
    Aug 26 09:54:35 machine kernel: [mem 0x00100000-0x001fffff] page 4k
    Aug 26 09:54:35 machine kernel: [mem 0x00200000-0x1fffffff] page 2M
    Aug 26 09:54:35 machine kernel: init_memory_mapping: [mem 0x20200000-0x40003fff]
    Aug 26 09:54:35 machine kernel: [mem 0x20200000-0x3fffffff] page 2M
    Aug 26 09:54:35 machine kernel: [mem 0x40000000-0x40003fff] page 4k
    Aug 26 09:54:35 machine kernel: BRK [0x02b29000, 0x02b29fff] PGTABLE
    Aug 26 09:54:35 machine kernel: init_memory_mapping: [mem 0x40005000-0x9a0befff]
    Aug 26 09:54:35 machine kernel: [mem 0x40005000-0x401fffff] page 4k
    Aug 26 09:54:35 machine kernel: [mem 0x40200000-0x99ffffff] page 2M
    Aug 26 09:54:35 machine kernel: [mem 0x9a000000-0x9a0befff] page 4k
    Aug 26 09:54:35 machine kernel: init_memory_mapping: [mem 0x9afff000-0x9affffff]
    Aug 26 09:54:35 machine kernel: [mem 0x9afff000-0x9affffff] page 4k
    Aug 26 09:54:35 machine kernel: RAMDISK: [mem 0x37976000-0x37cb2fff]
    Aug 26 09:54:35 machine kernel: ACPI: Early table checksum verification disabled
    Aug 26 09:54:35 machine kernel: ACPI: RSDP 0x000000009AFFE014 000024 (v02 HPQOEM)
    Aug 26 09:54:35 machine kernel: ACPI: XSDT 0x000000009AFFE210 0000AC (v01 HPQOEM SLIC-MPC 00000001 HP 01000013)
    Aug 26 09:54:35 machine kernel: ACPI: FACP 0x000000009AFFB000 00010C (v05 HPQOEM SLIC-MPC 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: DSDT 0x000000009AFE9000 00E963 (v01 HPQOEM INSYDE 00000000 INTL 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: FACS 0x000000009AFBA000 000040
    Aug 26 09:54:35 machine kernel: ACPI: UEFI 0x000000009AFFD000 000236 (v01 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: ASF! 0x000000009AFFC000 0000A5 (v32 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: HPET 0x000000009AFFA000 000038 (v01 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: APIC 0x000000009AFF9000 00008C (v03 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: MCFG 0x000000009AFF8000 00003C (v01 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: WDAT 0x000000009AFE8000 000224 (v01 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: SSDT 0x000000009AFE7000 000E21 (v01 HPQOEM INSYDE 00001000 INTL 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: BOOT 0x000000009AFE5000 000028 (v01 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: ASPT 0x000000009AFE3000 000034 (v07 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: DBGP 0x000000009AFE2000 000034 (v01 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: FPDT 0x000000009AFE0000 000044 (v01 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: MSDM 0x000000009AFDF000 000055 (v03 HPQOEM SLIC-MPC 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: SSDT 0x000000009AFDE000 000968 (v01 HPQOEM INSYDE 00003000 INTL 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: SSDT 0x000000009AFDD000 000B22 (v01 HPQOEM INSYDE 00003000 INTL 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: SSDT 0x000000009AFDA000 001EED (v01 HPQOEM INSYDE 00001000 INTL 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: BGRT 0x000000009AFDC000 000038 (v01 HPQOEM 183E 00000001 HP 00040000)
    Aug 26 09:54:35 machine kernel: ACPI: Local APIC address 0xfee00000
    Aug 26 09:54:35 machine kernel: No NUMA configuration found
    Aug 26 09:54:35 machine kernel: Faking a node at [mem 0x0000000000000000-0x000000015f5fffff]
    Aug 26 09:54:35 machine kernel: Initmem setup node 0 [mem 0x00000000-0x15f5fffff]
    Aug 26 09:54:35 machine kernel: NODE_DATA [mem 0x15f5f7000-0x15f5fbfff]
    Aug 26 09:54:35 machine kernel: [ffffea0000000000-ffffea00057fffff] PMD -> [ffff88015ac00000-ffff88015ebfffff] on node 0
    Aug 26 09:54:35 machine kernel: Zone ranges:
    Aug 26 09:54:35 machine kernel: DMA [mem 0x00001000-0x00ffffff]
    Aug 26 09:54:35 machine kernel: DMA32 [mem 0x01000000-0xffffffff]
    Aug 26 09:54:35 machine kernel: Normal [mem 0x100000000-0x15f5fffff]
    Aug 26 09:54:35 machine kernel: Movable zone start for each node
    Aug 26 09:54:35 machine kernel: Early memory node ranges
    Aug 26 09:54:35 machine kernel: node 0: [mem 0x00001000-0x00087fff]
    Aug 26 09:54:35 machine kernel: node 0: [mem 0x00100000-0x1fffffff]
    Aug 26 09:54:35 machine kernel: node 0: [mem 0x20200000-0x40003fff]
    Aug 26 09:54:35 machine kernel: node 0: [mem 0x40005000-0x9a0befff]
    Aug 26 09:54:35 machine kernel: node 0: [mem 0x9afff000-0x9affffff]
    Aug 26 09:54:35 machine kernel: node 0: [mem 0x100000000-0x15f5fffff]
    Aug 26 09:54:35 machine kernel: On node 0 totalpages: 1020998
    Aug 26 09:54:35 machine kernel: DMA zone: 64 pages used for memmap
    Aug 26 09:54:35 machine kernel: DMA zone: 23 pages reserved
    Aug 26 09:54:35 machine kernel: DMA zone: 3975 pages, LIFO batch:0
    Aug 26 09:54:35 machine kernel: DMA32 zone: 9787 pages used for memmap
    Aug 26 09:54:35 machine kernel: DMA32 zone: 626367 pages, LIFO batch:31
    Aug 26 09:54:35 machine kernel: Normal zone: 6104 pages used for memmap
    Aug 26 09:54:35 machine kernel: Normal zone: 390656 pages, LIFO batch:31
    Aug 26 09:54:35 machine kernel: Reserving Intel graphics stolen memory at 0x9ba00000-0x9f9fffff
    Aug 26 09:54:35 machine kernel: ACPI: PM-Timer IO Port: 0x408
    Aug 26 09:54:35 machine kernel: ACPI: Local APIC address 0xfee00000
    Aug 26 09:54:35 machine kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Aug 26 09:54:35 machine kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Aug 26 09:54:35 machine kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
    Aug 26 09:54:35 machine kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
    Aug 26 09:54:35 machine kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled)
    Aug 26 09:54:35 machine kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled)
    Aug 26 09:54:35 machine kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x00] disabled)
    Aug 26 09:54:35 machine kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x00] disabled)
    Aug 26 09:54:35 machine kernel: ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
    Aug 26 09:54:35 machine kernel: IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
    Aug 26 09:54:35 machine kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Aug 26 09:54:35 machine kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Aug 26 09:54:35 machine kernel: ACPI: IRQ0 used by override.
    Aug 26 09:54:35 machine kernel: ACPI: IRQ2 used by override.
    Aug 26 09:54:35 machine kernel: ACPI: IRQ9 used by override.
    Aug 26 09:54:35 machine kernel: Using ACPI (MADT) for SMP configuration information
    Aug 26 09:54:35 machine kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
    Aug 26 09:54:35 machine kernel: smpboot: Allowing 8 CPUs, 4 hotplug CPUs
    Aug 26 09:54:35 machine kernel: nr_irqs_gsi: 40
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x00088000-0x000bffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x000c0000-0x000fffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x40004000-0x40004fff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x9a0bf000-0x9a4befff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x9a4bf000-0x9aebefff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x9aebf000-0x9afbefff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x9afbf000-0x9affefff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x9b000000-0x9f9fffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0x9fa00000-0xdfffffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xe0000000-0xefffffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xf0000000-0xfeafffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfeb00000-0xfeb03fff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfeb04000-0xfebfffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfed0ffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfed1a000-0xfed1bfff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xfee01000-0xffd7ffff]
    Aug 26 09:54:35 machine kernel: PM: Registered nosave memory: [mem 0xffd80000-0xffffffff]
    Aug 26 09:54:35 machine kernel: e820: [mem 0x9fa00000-0xdfffffff] available for PCI devices
    Aug 26 09:54:35 machine kernel: Booting paravirtualized kernel on bare hardware
    Aug 26 09:54:35 machine kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    Aug 26 09:54:35 machine kernel: PERCPU: Embedded 29 pages/cpu @ffff88015f200000 s86784 r8192 d23808 u262144
    Aug 26 09:54:35 machine kernel: pcpu-alloc: s86784 r8192 d23808 u262144 alloc=1*2097152
    Aug 26 09:54:35 machine kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    Aug 26 09:54:35 machine kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 1005020
    Aug 26 09:54:35 machine kernel: Policy zone: Normal
    Aug 26 09:54:35 machine kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-zen root=UUID=09b369ae-e074-442f-ae02-101a7421b569 rw drm.rnodes=1
    Aug 26 09:54:35 machine kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    Aug 26 09:54:35 machine kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340
    Aug 26 09:54:35 machine kernel: AGP: Checking aperture...
    Aug 26 09:54:35 machine kernel: AGP: No AGP bridge found
    Aug 26 09:54:35 machine kernel: Calgary: detecting Calgary via BIOS EBDA area
    Aug 26 09:54:35 machine kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Aug 26 09:54:35 machine kernel: Memory: 3885380K/4083992K available (5370K kernel code, 890K rwdata, 1696K rodata, 1128K init, 1164K bss, 198612K reserved)
    Aug 26 09:54:35 machine kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    Aug 26 09:54:35 machine kernel: Preemptible hierarchical RCU implementation.
    Aug 26 09:54:35 machine kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Aug 26 09:54:35 machine kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Aug 26 09:54:35 machine kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
    Aug 26 09:54:35 machine kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    Aug 26 09:54:35 machine kernel: NR_IRQS:8448 nr_irqs:744 16
    Aug 26 09:54:35 machine kernel: Console: colour dummy device 80x25
    Aug 26 09:54:35 machine kernel: console [tty0] enabled
    Aug 26 09:54:35 machine kernel: allocated 16777216 bytes of page_cgroup
    Aug 26 09:54:35 machine kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Aug 26 09:54:35 machine kernel: hpet clockevent registered
    Aug 26 09:54:35 machine kernel: tsc: Fast TSC calibration using PIT
    Aug 26 09:54:35 machine kernel: tsc: Detected 2494.477 MHz processor
    Aug 26 09:54:35 machine kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4990.82 BogoMIPS (lpj=8314923)
    Aug 26 09:54:35 machine kernel: pid_max: default: 32768 minimum: 301
    Aug 26 09:54:35 machine kernel: ACPI: Core revision 20140424
    Aug 26 09:54:35 machine kernel: ACPI: All ACPI Tables successfully acquired
    Aug 26 09:54:35 machine kernel: Security Framework initialized
    Aug 26 09:54:35 machine kernel: Yama: becoming mindful.
    Aug 26 09:54:35 machine kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
    Aug 26 09:54:35 machine kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
    Aug 26 09:54:35 machine kernel: Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
    Aug 26 09:54:35 machine kernel: Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys memory
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys devices
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys freezer
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys net_cls
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys blkio
    Aug 26 09:54:35 machine kernel: Initializing cgroup subsys bfqio
    Aug 26 09:54:35 machine kernel: CPU: Physical Processor ID: 0
    Aug 26 09:54:35 machine kernel: CPU: Processor Core ID: 0
    Aug 26 09:54:35 machine kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    Aug 26 09:54:35 machine kernel: mce: CPU supports 7 MCE banks
    Aug 26 09:54:35 machine kernel: CPU0: Thermal monitoring enabled (TM1)
    Aug 26 09:54:35 machine kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
    Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
    tlb_flushall_shift: 2
    Aug 26 09:54:35 machine kernel: Freeing SMP alternatives memory: 20K (ffffffff819fa000 - ffffffff819ff000)
    Aug 26 09:54:35 machine kernel: ftrace: allocating 20549 entries in 81 pages
    Aug 26 09:54:35 machine kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Aug 26 09:54:35 machine kernel: smpboot: CPU0: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (fam: 06, model: 3a, stepping: 09)
    Aug 26 09:54:35 machine kernel: TSC deadline timer enabled
    Aug 26 09:54:35 machine kernel: Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
    Aug 26 09:54:35 machine kernel: ... version: 3
    Aug 26 09:54:35 machine kernel: ... bit width: 48
    Aug 26 09:54:35 machine kernel: ... generic registers: 4
    Aug 26 09:54:35 machine kernel: ... value mask: 0000ffffffffffff
    Aug 26 09:54:35 machine kernel: ... max period: 0000ffffffffffff
    Aug 26 09:54:35 machine kernel: ... fixed-purpose events: 3
    Aug 26 09:54:35 machine kernel: ... event mask: 000000070000000f
    Aug 26 09:54:35 machine kernel: x86: Booting SMP configuration:
    Aug 26 09:54:35 machine kernel: .... node #0, CPUs: #1
    Aug 26 09:54:35 machine kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Aug 26 09:54:35 machine kernel: #2 #3
    Aug 26 09:54:35 machine kernel: x86: Booted up 1 node, 4 CPUs
    Aug 26 09:54:35 machine kernel: smpboot: Total of 4 processors activated (19963.30 BogoMIPS)
    Aug 26 09:54:35 machine kernel: devtmpfs: initialized
    Aug 26 09:54:35 machine kernel: PM: Registering ACPI NVS region [mem 0x9aebf000-0x9afbefff] (1048576 bytes)
    Aug 26 09:54:35 machine kernel: pinctrl core: initialized pinctrl subsystem
    Aug 26 09:54:35 machine kernel: RTC time: 6:54:21, date: 08/26/14
    Aug 26 09:54:35 machine kernel: NET: Registered protocol family 16
    Aug 26 09:54:35 machine kernel: cpuidle: using governor ladder
    Aug 26 09:54:35 machine kernel: cpuidle: using governor menu
    Aug 26 09:54:35 machine kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    Aug 26 09:54:35 machine kernel: ACPI: bus type PCI registered
    Aug 26 09:54:35 machine kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    Aug 26 09:54:35 machine kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    Aug 26 09:54:35 machine kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    Aug 26 09:54:35 machine kernel: PCI: Using configuration type 1 for base access
    Aug 26 09:54:35 machine kernel: ACPI: Added _OSI(Module Device)
    Aug 26 09:54:35 machine kernel: ACPI: Added _OSI(Processor Device)
    Aug 26 09:54:35 machine kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Aug 26 09:54:35 machine kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Aug 26 09:54:35 machine kernel: ACPI: Executed 1 blocks of module-level executable AML code
    Aug 26 09:54:35 machine kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Aug 26 09:54:35 machine kernel: ACPI: Dynamic OEM Table Load:
    Aug 26 09:54:35 machine kernel: ACPI: SSDT 0xFFFF880158F0D000 00083B (v01 PmRef Cpu0Cst 00003001 INTL 20120816)
    Aug 26 09:54:35 machine kernel: ACPI: Dynamic OEM Table Load:
    Aug 26 09:54:35 machine kernel: ACPI: SSDT 0xFFFF880158F59000 000303 (v01 PmRef ApIst 00003000 INTL 20120816)
    Aug 26 09:54:35 machine kernel: ACPI: Dynamic OEM Table Load:
    Aug 26 09:54:35 machine kernel: ACPI: SSDT 0xFFFF880158F11E00 000119 (v01 PmRef ApCst 00003000 INTL 20120816)
    Aug 26 09:54:35 machine kernel: ACPI: Interpreter enabled
    Aug 26 09:54:35 machine kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140424/hwxface-580)
    Aug 26 09:54:35 machine kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140424/hwxface-580)
    Aug 26 09:54:35 machine kernel: ACPI: (supports S0 S3 S4 S5)
    Aug 26 09:54:35 machine kernel: ACPI: Using IOAPIC for interrupt routing
    Aug 26 09:54:35 machine kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Aug 26 09:54:35 machine kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
    Aug 26 09:54:35 machine kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    Aug 26 09:54:35 machine kernel: \_SB_.PCI0:_OSC invalid UUID
    Aug 26 09:54:35 machine kernel: _OSC request data:1 1f 0
    Aug 26 09:54:35 machine kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
    Aug 26 09:54:35 machine kernel: PCI host bridge to bus 0000:00
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [bus 00-fe]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x000f0000-0x000fffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: root bus resource [mem 0x9fa00000-0xfeafffff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:00.0: [8086:0154] type 00 class 0x060000
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:02.0: [8086:0166] type 00 class 0x030000
    Aug 26 09:54:35 machine kernel: pci 0000:00:02.0: reg 0x10: [mem 0xc3000000-0xc33fffff 64bit]
    Aug 26 09:54:35 machine kernel: pci 0000:00:02.0: reg 0x18: [mem 0xb0000000-0xbfffffff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci 0000:00:02.0: reg 0x20: [io 0x5000-0x503f]
    Aug 26 09:54:35 machine kernel: pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
    Aug 26 09:54:35 machine kernel: pci 0000:00:14.0: reg 0x10: [mem 0xc3600000-0xc360ffff 64bit]
    Aug 26 09:54:35 machine kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
    Aug 26 09:54:35 machine kernel: pci 0000:00:16.0: reg 0x10: [mem 0xc3614000-0xc361400f 64bit]
    Aug 26 09:54:35 machine kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
    Aug 26 09:54:35 machine kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xc3619000-0xc36193ff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
    Aug 26 09:54:35 machine kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xc3610000-0xc3613fff 64bit]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.1: [8086:1e12] type 01 class 0x060400
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.1: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: [8086:1e14] type 01 class 0x060400
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
    Aug 26 09:54:35 machine kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xc3618000-0xc36183ff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.0: [8086:1e59] type 00 class 0x060100
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.2: reg 0x10: [io 0x5088-0x508f]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.2: reg 0x14: [io 0x5094-0x5097]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.2: reg 0x18: [io 0x5080-0x5087]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.2: reg 0x1c: [io 0x5090-0x5093]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.2: reg 0x20: [io 0x5060-0x507f]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xc3617000-0xc36177ff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xc3615000-0xc36150ff 64bit]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1f.3: reg 0x20: [io 0x5040-0x505f]
    Aug 26 09:54:35 machine kernel: pci 0000:01:00.0: [1002:6840] type 00 class 0x030000
    Aug 26 09:54:35 machine kernel: pci 0000:01:00.0: reg 0x10: [mem 0xa0000000-0xafffffff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci 0000:01:00.0: reg 0x18: [mem 0xc2000000-0xc201ffff 64bit]
    Aug 26 09:54:35 machine kernel: pci 0000:01:00.0: reg 0x20: [io 0x4000-0x40ff]
    Aug 26 09:54:35 machine kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfffe0000-0xffffffff pref]
    Aug 26 09:54:35 machine kernel: pci 0000:01:00.0: supports D1 D2
    Aug 26 09:54:35 machine kernel: pci 0000:01:00.0: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: PCI bridge to [bus 01-06]
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: bridge window [io 0x4000-0x4fff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: bridge window [mem 0xc2000000-0xc2ffffff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: bridge window [mem 0xa0000000-0xafffffff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci 0000:07:00.0: [1814:3290] type 00 class 0x028000
    Aug 26 09:54:35 machine kernel: pci 0000:07:00.0: reg 0x10: [mem 0xc3510000-0xc351ffff]
    Aug 26 09:54:35 machine kernel: pci 0000:07:00.0: PME# supported from D0 D3hot
    Aug 26 09:54:35 machine kernel: pci 0000:07:00.1: [1814:3298] type 00 class 0x0d1100
    Aug 26 09:54:35 machine kernel: pci 0000:07:00.1: reg 0x10: [mem 0xc3500000-0xc350ffff]
    Aug 26 09:54:35 machine kernel: pci 0000:07:00.1: supports D1
    Aug 26 09:54:35 machine kernel: pci 0000:07:00.1: PME# supported from D0 D1 D3hot
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.0: PCI bridge to [bus 07]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.0: bridge window [mem 0xc3500000-0xc35fffff]
    Aug 26 09:54:35 machine kernel: pci 0000:08:00.0: [10ec:8136] type 00 class 0x020000
    Aug 26 09:54:35 machine kernel: pci 0000:08:00.0: reg 0x10: [io 0x3000-0x30ff]
    Aug 26 09:54:35 machine kernel: pci 0000:08:00.0: reg 0x18: [mem 0xc3404000-0xc3404fff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci 0000:08:00.0: reg 0x20: [mem 0xc3400000-0xc3403fff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci 0000:08:00.0: supports D1 D2
    Aug 26 09:54:35 machine kernel: pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    Aug 26 09:54:35 machine kernel: pci 0000:08:00.0: System wakeup disabled by ACPI
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.1: PCI bridge to [bus 08]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.1: bridge window [io 0x3000-0x3fff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.1: bridge window [mem 0xc3400000-0xc34fffff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci 0000:09:00.0: [10ec:5229] type 00 class 0xff0000
    Aug 26 09:54:35 machine kernel: pci 0000:09:00.0: reg 0x10: [mem 0xc1000000-0xc1000fff]
    Aug 26 09:54:35 machine kernel: pci 0000:09:00.0: supports D1 D2
    Aug 26 09:54:35 machine kernel: pci 0000:09:00.0: PME# supported from D1 D2 D3hot
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: PCI bridge to [bus 09-0e]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: bridge window [io 0x2000-0x2fff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: bridge window [mem 0xc1000000-0xc1ffffff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: bridge window [mem 0xc0000000-0xc0ffffff 64bit pref]
    Aug 26 09:54:35 machine kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    Aug 26 09:54:35 machine kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    Aug 26 09:54:35 machine kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    Aug 26 09:54:35 machine kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    Aug 26 09:54:35 machine kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    Aug 26 09:54:35 machine kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    Aug 26 09:54:35 machine kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    Aug 26 09:54:35 machine kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    Aug 26 09:54:35 machine kernel: ACPI: Enabled 4 GPEs in block 00 to 3F
    Aug 26 09:54:35 machine kernel: ACPI : EC: GPE = 0x1d, I/O: command/status = 0x66, data = 0x62
    Aug 26 09:54:35 machine kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    Aug 26 09:54:35 machine kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
    Aug 26 09:54:35 machine kernel: vgaarb: loaded
    Aug 26 09:54:35 machine kernel: vgaarb: bridge control possible 0000:01:00.0
    Aug 26 09:54:35 machine kernel: vgaarb: no bridge control possible 0000:00:02.0
    Aug 26 09:54:35 machine kernel: PCI: Using ACPI for IRQ routing
    Aug 26 09:54:35 machine kernel: PCI: pci_cache_line_size set to 64 bytes
    Aug 26 09:54:35 machine kernel: e820: reserve RAM buffer [mem 0x00088000-0x0008ffff]
    Aug 26 09:54:35 machine kernel: e820: reserve RAM buffer [mem 0x40004000-0x43ffffff]
    Aug 26 09:54:35 machine kernel: e820: reserve RAM buffer [mem 0x9a0bf000-0x9bffffff]
    Aug 26 09:54:35 machine kernel: e820: reserve RAM buffer [mem 0x9b000000-0x9bffffff]
    Aug 26 09:54:35 machine kernel: e820: reserve RAM buffer [mem 0x15f600000-0x15fffffff]
    Aug 26 09:54:35 machine kernel: NetLabel: Initializing
    Aug 26 09:54:35 machine kernel: NetLabel: domain hash size = 128
    Aug 26 09:54:35 machine kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Aug 26 09:54:35 machine kernel: NetLabel: unlabeled traffic allowed by default
    Aug 26 09:54:35 machine kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    Aug 26 09:54:35 machine kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    Aug 26 09:54:35 machine kernel: Switched to clocksource hpet
    Aug 26 09:54:35 machine kernel: pnp: PnP ACPI init
    Aug 26 09:54:35 machine kernel: ACPI: bus type PNP registered
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0x0680-0x069f] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0x1000-0x100f] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0xffff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0xffff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0x0400-0x0453] could not be reserved
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0x0458-0x047f] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0x0500-0x057f] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0x164e-0x164f] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0x0454-0x0457] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:00: [io 0x0380-0x0387] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    Aug 26 09:54:35 machine kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
    Aug 26 09:54:35 machine kernel: pnp 00:02: Plug and Play ACPI device, IDs HPQ8001 PNP0303 (active)
    Aug 26 09:54:35 machine kernel: pnp 00:03: Plug and Play ACPI device, IDs SYN1e60 SYN1e00 SYN0002 PNP0f13 (active)
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0xfed1c000-0xfed1ffff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0xfed10000-0xfed17fff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0xfed18000-0xfed18fff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0xfed19000-0xfed19fff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0xe0000000-0xefffffff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0xfed20000-0xfed3ffff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0xfed90000-0xfed93fff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0xff000000-0xffffffff] could not be reserved
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0xfee00000-0xfeefffff] could not be reserved
    Aug 26 09:54:35 machine kernel: system 00:04: [mem 0x9fa00000-0x9fa00fff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    Aug 26 09:54:35 machine kernel: system 00:05: [mem 0x20000000-0x201fffff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:05: [mem 0x40004000-0x40004fff] has been reserved
    Aug 26 09:54:35 machine kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
    Aug 26 09:54:35 machine kernel: pnp: PnP ACPI: found 6 devices
    Aug 26 09:54:35 machine kernel: ACPI: bus type PNP unregistered
    Aug 26 09:54:35 machine kernel: pci 0000:01:00.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]: no compatible bridge window
    Aug 26 09:54:35 machine kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xc2020000-0xc203ffff pref]
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: PCI bridge to [bus 01-06]
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: bridge window [io 0x4000-0x4fff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: bridge window [mem 0xc2000000-0xc2ffffff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:01.0: bridge window [mem 0xa0000000-0xafffffff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.0: PCI bridge to [bus 07]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.0: bridge window [mem 0xc3500000-0xc35fffff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.1: PCI bridge to [bus 08]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.1: bridge window [io 0x3000-0x3fff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.1: bridge window [mem 0xc3400000-0xc34fffff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: PCI bridge to [bus 09-0e]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: bridge window [io 0x2000-0x2fff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: bridge window [mem 0xc1000000-0xc1ffffff]
    Aug 26 09:54:35 machine kernel: pci 0000:00:1c.2: bridge window [mem 0xc0000000-0xc0ffffff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 19 [mem 0x000f0000-0x000fffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:00: resource 20 [mem 0x9fa00000-0xfeafffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:01: resource 0 [io 0x4000-0x4fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:01: resource 1 [mem 0xc2000000-0xc2ffffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:01: resource 2 [mem 0xa0000000-0xafffffff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:07: resource 1 [mem 0xc3500000-0xc35fffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:08: resource 0 [io 0x3000-0x3fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:08: resource 2 [mem 0xc3400000-0xc34fffff 64bit pref]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:09: resource 0 [io 0x2000-0x2fff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:09: resource 1 [mem 0xc1000000-0xc1ffffff]
    Aug 26 09:54:35 machine kernel: pci_bus 0000:09: resource 2 [mem 0xc0000000-0xc0ffffff 64bit pref]
    Aug 26 09:54:35 machine kernel: NET: Registered protocol family 2
    Aug 26 09:54:35 machine kernel: TCP established hash table entries: 32768 (order: 6, 262144 bytes)
    Aug 26 09:54:35 machine kernel: TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
    Aug 26 09:54:35 machine kernel: TCP: Hash tables configured (established 32768 bind 32768)
    Aug 26 09:54:35 machine kernel: TCP: reno registered
    Aug 26 09:54:35 machine kernel: UDP hash table entries: 2048 (order: 4, 65536 bytes)
    Aug 26 09:54:35 machine kernel: UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
    Aug 26 09:54:35 machine kernel: NET: Registered protocol family 1
    Aug 26 09:54:35 machine kernel: pci 0000:00:02.0: Boot video device
    Aug 26 09:54:35 machine kernel: PCI: CLS 64 bytes, default 64
    Aug 26 09:54:35 machine kernel: Unpacking initramfs...
    Aug 26 09:54:35 machine kernel: Freeing initrd memory: 3316K (ffff880037976000 - ffff880037cb3000)
    Aug 26 09:54:35 machine kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    Aug 26 09:54:35 machine kernel: software IO TLB [mem 0x9316c000-0x9716c000] (64MB) mapped at [ffff88009316c000-ffff88009716bfff]
    Aug 26 09:54:35 machine kernel: Simple Boot Flag at 0x44 set to 0x1
    Aug 26 09:54:35 machine kernel: RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
    Aug 26 09:54:35 machine kernel: Scanning for low memory corruption every 60 seconds
    Aug 26 09:54:35 machine kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
    Aug 26 09:54:35 machine kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    Aug 26 09:54:35 machine kernel: zbud: loaded
    Aug 26 09:54:35 machine kernel: VFS: Disk quotas dquot_6.5.2
    Aug 26 09:54:35 machine kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    Aug 26 09:54:35 machine kernel: msgmni has been set to 7694
    Aug 26 09:54:35 machine kernel: Key type big_key registered
    Aug 26 09:54:35 machine kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Aug 26 09:54:35 machine kernel: io scheduler noop registered
    Aug 26 09:54:35 machine kernel: io scheduler deadline registered
    Aug 26 09:54:35 machine kernel: io scheduler cfq registered
    Aug 26 09:54:35 machine kernel: io scheduler bfq registered (default)
    Aug 26 09:54:35 machine kernel: BFQ I/O-scheduler version: v7r5
    Aug 26 09:54:35 machine kernel: pcieport 0000:00:01.0: device [8086:0151] has invalid IRQ; check vendor BIOS
    Aug 26 09:54:35 machine kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
    Aug 26 09:54:35 machine kernel: pcieport 0000:00:1c.0: device [8086:1e10] has invalid IRQ; check vendor BIOS
    Aug 26 09:54:35 machine kernel: pcieport 0000:00:1c.1: device [8086:1e12] has invalid IRQ; check vendor BIOS
    Aug 26 09:54:35 machine kernel: pcieport 0000:00:1c.2: device [8086:1e14] has invalid IRQ; check vendor BIOS
    Aug 26 09:54:35 machine kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    Aug 26 09:54:35 machine kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    Aug 26 09:54:35 machine kernel: efifb: probing for efifb
    Aug 26 09:54:35 machine kernel: efifb: framebuffer at 0xb0000000, mapped to 0xffffc90010800000, using 4160k, total 4160k
    Aug 26 09:54:35 machine kernel: efifb: mode is 1366x768x32, linelength=5504, pages=1
    Aug 26 09:54:35 machine kernel: efifb: scrolling: redraw
    Aug 26 09:54:35 machine kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Aug 26 09:54:35 machine kernel: Console: switching to colour frame buffer device 170x48
    Aug 26 09:54:35 machine kernel: fb0: EFI VGA frame buffer device
    Aug 26 09:54:35 machine kernel: intel_idle: MWAIT substates: 0x21120
    Aug 26 09:54:35 machine kernel: intel_idle: v0.4 model 0x3A
    Aug 26 09:54:35 machine kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
    Aug 26 09:54:35 machine kernel: GHES: HEST is not enabled!
    Aug 26 09:54:35 machine kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Aug 26 09:54:35 machine kernel: Linux agpgart interface v0.103
    Aug 26 09:54:35 machine kernel: rtc_cmos 00:01: RTC can wake from S4
    Aug 26 09:54:35 machine kernel: rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
    Aug 26 09:54:35 machine kernel: rtc_cmos 00:01: alarms up to one month, 242 bytes nvram, hpet irqs
    Aug 26 09:54:35 machine kernel: Intel P-state driver initializing.
    Aug 26 09:54:35 machine kernel: Intel pstate controlling: cpu 0
    Aug 26 09:54:35 machine kernel: Intel pstate controlling: cpu 1
    Aug 26 09:54:35 machine kernel: Intel pstate controlling: cpu 2
    Aug 26 09:54:35 machine kernel: Intel pstate controlling: cpu 3
    Aug 26 09:54:35 machine kernel: ledtrig-cpu: registered to indicate activity on CPUs
    Aug 26 09:54:35 machine kernel: TCP: vegas registered
    Aug 26 09:54:35 machine kernel: TCP: yeah registered
    Aug 26 09:54:35 machine kernel: NET: Registered protocol family 10
    Aug 26 09:54:35 machine kernel: NET: Registered protocol family 17
    Aug 26 09:54:35 machine kernel: registered taskstats version 1
    Aug 26 09:54:35 machine kernel: Magic number: 10:491:924
    Aug 26 09:54:35 machine kernel: rtc_cmos 00:01: setting system clock to 2014-08-26 06:54:21 UTC (1409036061)
    Aug 26 09:54:35 machine kernel: PM: Hibernation image not present or could not be loaded.
    Aug 26 09:54:35 machine kernel: Freeing unused kernel memory: 1128K (ffffffff818e0000 - ffffffff819fa000)
    Aug 26 09:54:35 machine kernel: Write protecting the kernel read-only data: 8192k
    Aug 26 09:54:35 machine kernel: Freeing unused kernel memory: 764K (ffff880002541000 - ffff880002600000)
    Aug 26 09:54:35 machine kernel: Freeing unused kernel memory: 352K (ffff8800027a8000 - ffff880002800000)
    Aug 26 09:54:35 machine kernel: CFS CPU scheduler.
    Aug 26 09:54:35 machine kernel: random: systemd-tmpfile urandom read with 18 bits of entropy available
    Aug 26 09:54:35 machine systemd-udevd[58]: starting version 215
    Aug 26 09:54:35 machine kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
    Aug 26 09:54:35 machine kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Aug 26 09:54:35 machine kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
    Aug 26 09:54:35 machine kernel: ACPI: bus type USB registered
    Aug 26 09:54:35 machine kernel: usbcore: registered new interface driver usbfs
    Aug 26 09:54:35 machine kernel: usbcore: registered new interface driver hub
    Aug 26 09:54:35 machine kernel: usbcore: registered new device driver usb
    Aug 26 09:54:35 machine kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Aug 26 09:54:35 machine kernel: ehci-pci: EHCI PCI platform driver
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1a.0: debug port 2
    Aug 26 09:54:35 machine kernel: rtsx_pci 0000:09:00.0: irq 41 for MSI/MSI-X
    Aug 26 09:54:35 machine kernel: rtsx_pci 0000:09:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, pci->irq = 41
    Aug 26 09:54:35 machine kernel: SCSI subsystem initialized
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xc3619000
    Aug 26 09:54:35 machine kernel: libata version 3.00 loaded.
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
    Aug 26 09:54:35 machine kernel: hub 1-0:1.0: USB hub found
    Aug 26 09:54:35 machine kernel: hub 1-0:1.0: 2 ports detected
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1d.0: debug port 2
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1d.0: irq 20, io mem 0xc3618000
    Aug 26 09:54:35 machine kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    Aug 26 09:54:35 machine kernel: hub 2-0:1.0: USB hub found
    Aug 26 09:54:35 machine kernel: hub 2-0:1.0: 2 ports detected
    Aug 26 09:54:35 machine kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
    Aug 26 09:54:35 machine kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
    Aug 26 09:54:35 machine kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
    Aug 26 09:54:35 machine kernel: xhci_hcd 0000:00:14.0: irq 42 for MSI/MSI-X
    Aug 26 09:54:35 machine kernel: hub 3-0:1.0: USB hub found
    Aug 26 09:54:35 machine kernel: hub 3-0:1.0: 4 ports detected
    Aug 26 09:54:35 machine kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
    Aug 26 09:54:35 machine kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
    Aug 26 09:54:35 machine kernel: hub 4-0:1.0: USB hub found
    Aug 26 09:54:35 machine kernel: hub 4-0:1.0: 4 ports detected
    Aug 26 09:54:35 machine kernel: ahci 0000:00:1f.2: version 3.0
    Aug 26 09:54:35 machine kernel: ahci 0000:00:1f.2: irq 43 for MSI/MSI-X
    Aug 26 09:54:35 machine kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    Aug 26 09:54:35 machine kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x11 impl SATA mode
    Aug 26 09:54:35 machine kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
    Aug 26 09:54:35 machine kernel: scsi0 : ahci
    Aug 26 09:54:35 machine kernel: scsi1 : ahci
    Aug 26 09:54:35 machine kernel: scsi2 : ahci
    Aug 26 09:54:35 machine kernel: scsi3 : ahci
    Aug 26 09:54:35 machine kernel: scsi4 : ahci
    Aug 26 09:54:35 machine kernel: scsi5 : ahci
    Aug 26 09:54:35 machine kernel: ata1: SATA max UDMA/133 abar m2048@0xc3617000 port 0xc3617100 irq 43
    Aug 26 09:54:35 machine kernel: ata2: DUMMY
    Aug 26 09:54:35 machine kernel: ata3: DUMMY
    Aug 26 09:54:35 machine kernel: ata4: DUMMY
    Aug 26 09:54:35 machine kernel: ata5: SATA max UDMA/133 abar m2048@0xc3617000 port 0xc3617300 irq 43
    Aug 26 09:54:35 machine kernel: ata6: DUMMY
    Aug 26 09:54:35 machine kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
    Aug 26 09:54:35 machine kernel: ata1: SATA l

    It was already hooked, however, I moved it from the last line to this: `HOOKS="colors base udev autodetect fsck modconf block filesystems keyboard"`
    Not a change. It, I guess only works on the root partition.
    I just ran a `fsck /dev/sdaX` from the emergency console after unmounting it. Problem is solved but the bug is, I guess is still there.
    Thank you anyway.

  • Remote Monitoring Latest Best Practice Architecture

    Hi guys,
    I've developed very few remote monitoring systems in the past. One of them was using a PXI RT and the rest are cRIO. The approach and architecture were based from some of the things I've read from ni.com and this forum. In the process, there were much difficulties and some extensive troubleshooting exercises that I need to do. The results, while the system work and meet the user's requirements, it didn't meet my own expectation. I was hoping that the system can be expanded (adding more cRIO or PXI) with much ease and little or no re-programming effort. Anyway, 2-3 years have passed and opportunities with similar requirements has emerged. So, I would like to get started to think about the architecture at an early stage (ie. now). 
    In my past systems, I've used Shared Variables (SV) a lot - and it gave much much headache too. Some of the troubles I had were:
    1. I can't decide whether to lump all SV in one library and host them in one system, or to separate them into various libraries and systems... neither do I know what's the best approach, as I've read too many 'suggestions' and 'advices',
    2. Some of the SV are from custom control and the control is type-def. When running the VI in RT with these SV in development platform, everything works smoothly but when I compiled and deploy, the program didn't run. After extensive troubleshooting, I found out that this had something to do with these SV - because when I removed the type-def from the custom controls and recreate my SV, everything worked fine. I suspect this may have something to do with how I deploy but after I tried several approach, the problem still persist.
    3. The best and most common of all is unstable connectivity - it work today but that doesn't guarantee it will work tomorrow. When the host PC changes, the same problems resurfaced again. I read somewhere that I need to read or interface with the .alias file but this work some times and other times, the same problem persist.
    Attached is the most common architecture that I've used. I would like to move away from SV as much as possible. If the application is 1:1, there's no problem as I can easily use TCP/IP & Network Stream. However, my doubts and headache comes when the RT:Host communication is either 1:N, N:N or N:1. I've read in ni.com and found out that there are various new approach to this, such as AMC (derivated from UDP), Web Services (or was it HTTP). 
    I really appreciate it if you guys share your thoughts and advices here, please?
    Shazlan
    Attachments:
    Remote Mon Sys - Arch.pdf ‏27 KB

    Nick,
    I was not talking about the mgmt0 interface. The vlan that you are testing will have a link blocked between the two 3750 port-channel if the root is on the nexus vPC pair.
    Logically your topology is like this:
        |                             |
        |   Nexus Pair          |
    3750-1-----------------------3750-2
    Since you have this triangle setup one of the links will be in blocking state for any vlan configured on these devices.
    When you are talking about vPC and L3 are you talking about L3 routing protocols or just intervaln routing.
    Intervlan routing is fine. Running L3 routing protocols over the peer-link and forming an adjaceny with an router upstream using L2 links is not recommended. Teh following link should give you an idea about what I am talking here:
    http://bradhedlund.com/2010/12/16/routing-over-nexus-7000-vpc-peer-link-yes-and-no/
    HSRP is fine.
    As mentioned tracking feature purpose is to avoid block hole of traffic. It completely depends on your network setup. Don't think you would be needing to track all the interfaces.
    JayaKrishna

  • Macbook Pro w/ 30 inch Dell monitor issue SOLVED

    I was amazed at the huge problems Apple apparently had with the bizarre $99 adapter that enables 30 inch dual channel display for the new Mini Displayport machines, including the current Macbook Pros. The reports of problems here were terrible, and I frankly waited six months or more to buy my next machine because of these problems -- Apple should be more careful about products like this.
    I'm happy to report that the Mini Displayport to Displayport cable from Monoprice works GREAT with my Dell 30 inch monitor (the current one, I can't find the number since it's hidden on the back but it's the current model they sell). Fully compatible in both Mac and Windows, video seems fine, and no issues that affect display quality. The only issue I have noticed is, when the monitor goes to sleep and I wake it up again on the Mac side, it displays strange lines. Any change in monitor color or resolution causes this to go away, so all I have to do is go to 16 bit color and back again. On top of everything, the cable is dirt cheap.
    Here it is:
    http://www.monoprice.com/products/product.asp?cid=102&cp_id=10246&cs_id=1024606&pid=6007&seq=1&format=2

    Peter Payne wrote:
    feel free to comment with your own experiences.
    Ok. But, what have you solved?
    First off, the 'huge problems' that you mention pertain to the Apple mini-DisplayPort to Dual Link DVI adapter. There's nothing 'bizarre' about that adapter - it allows you to connect a display requiring a dual-link DVI (i.e. up to 2560x1600) to your MBP. Those issues were not really that common (judging frequency of problems by reading these forums is like judging human health by visiting an Emergency Room - you'd think most of the population was sick or injured). If you went by forum problem reports, you'd never buy any product.
    More importantly, the _cable you linked above is an entirely different product_, a mini-DisplayPort to DisplayPort cable. It has nothing to do with DVI (note that Apple doesn't even make a mini-Dp to DP cable). If your display has a DisplayPort input (as the Dell 30" does) then it's fine. If your display has only DVI input (such as the Apple 30" Cinema Display), the cable you link is useless.
    But, although I find it utterly unsurprising that a mini-DP to DP cable will allow one to connect a mini-DP port on a computer to a DP port on a display, good to know that in that instance, the dirt cheap cable from Monoprice does the job.

  • IDOC Monitoring urgent

    Hi SAPpers,
    Does anybody knows what is IDOC Monitoring?
    The step by step configuration for IDOC monitoring.
    Was is the purpose of that?
    What is the Tcode for monitoring IDOC?
    Thanks will be rewarded

    Hi,
    Use
    You can easily and effectively monitor inbound and outbound processing of IDocs using special reports and graphic displays. An agent can also be notified automatically using a workflow if an “emergency” occurs (active monitoring).
    Features
    The following tools are available for monitoring:
    ·        IDoc Display
    All the other fields of the control record are available as selection criteria as well as partners and messages
    -   IDoc numbers
    -   Ports
    -   IDoc types
    You can display a tree structure of the IDoc directly using the IDoc number. The IDoc list is displayed again if several IDocs are selected.
    ·        IDoc Statistics
    The IDocs are sorted and represented graphically according to predefined status groups. Lists and individual IDocs can be displayed using mouse clicks.
    ·        IDoc Search
    You can select IDocs according to their business content, that is, according to the data contained in the segments.
    ·        Error and Status Processing
    Error and status codes are defined for the IDoc transfer. These codes can be assigned to a workflow task, which informs the agent automatically in a procedure.
    ·        Monitoring the Inbound Queue
    If you can receive IDocs via qRFC, you can monitor the inbound queue using a special transaction.
    ·        Monitoring the Outbound Queue
    If you can send IDocs via qRFC, you can monitor the outbound queue using a special transaction.
    ·        Active Monitoring
    This function provides you with a report that informs you if the number of critical IDocs exceeds a certain threshold.
    Active Monitoring Locate the document in its SAP Library structure
    Use
    This report automatically informs the agents responsible if too many incorrect IDocs are found.
    Integration
    Active monitoring is not used for processing or reimporting of an incorrect IDoc. Exception handling of every incorrect IDoc is responsible for this.
    Activities
    You plan the report to run regularly with a variant. The variant also informs the report of the status values to be selected: If the critical status contains more IDocs than specified in the critical number of IDocs, a message is sent to a predefined recipient.
    The recipient receives the notification in the form of a work item displayed in their Business Workplace. If they execute the work item, the IDoc statistics are displayed with the values determined at the time of evaluation. The agent can display the current status of these IDocs using the Refresh function. The selection criteria which led to the notification are also used for this evaluation.
    Example
    An important customer orders goods using EDI on working days, between 8am and 6pm. These goods are to be delivered at 4pm the next day. To ensure that the delivery is made on time, the ordered quantity must be recorded by midday on the day of delivery. The active monitoring function is to be used at 8am every morning to determine whether there are any orders which could not be processed automatically. The report, therefore, is started at the same time every day and 0 is selected as the critical number of IDocs. The agent responsible is notified if any incorrect IDocs are found and can then manually process the outstanding orders by midday.
    For more information see
    Schedule Monitoring Job (example)
    A processing status is assigned to an IDoc during processing (e.g. Status03: Data Transfer to Port OK). These status values are in turn assigned to a higher level status group (e.g. Output: IDoc Transfer Successful). This assignment to a status group is referred to as Qualification. You can change the assignment of status values to status groups in the Edit Status Values transaction.
    Procedure
           1.      To edit the status groups, choose the ALE customizing transaction SALE ® Set-Up System Monitoring ® Set-Up IDoc Status Display ® Edit IDoc Status Values (WE47).
    A list of statuses which have been defined is displayed.
           2.      If necessary, choose This graphic is explained in the accompanying text. By double-clicking on the status that you wish to assign a different status group, the detail screen is displayed.
           3.      The status group is displayed in the Qualification field. Use the F4 input help for an explanation of the numbers.
           4.      Select Save.
    ExampleExample
    Status 25 (processing despite syntax error (outbound)) is assigned status group 1 = “Outbound: IDoc generated". Replace 1 with 5 for “Outbound: IDoc Interface error".
    Chek Tcodes in WE02 OR WE05
    Regards,
    Phani,
    Points If Helpful.

  • Early 2009 MacPro with GTX 285 (Mac Edition) - Dual Monitor Setup

    Hey Guys - I tried going through the forum to find this, and I think I see some common responses, but wanted to detail my question and make sure I have it right.
    I have a MacPro (early 2009) with the EVGA GeForce GTX 285 Mac Edition GPU. I replaced the GT120 that came with the MacPro. I was initially planning on attaching two monitors to the GTX 285, but I have heard rumors that for smoother performance, I should hook up the GT120 as well and hook up one monitor to that one.
    However, I am reading posts regarding other configurations (4870 and GT120, etc), and it seems like there are different responses. Basically, I am looking for better performance for graphics demanding application (gaming, photo-edit, movie, etc).
    Thanks for your time and responses ahead of time.

    I'm so happy that you're soooo happy. If you were so so happy, I would be disappointed. Blessed? You honor me Japamac-san. I have not bestowed blessings in years, it must have been accidental. Well, I am getting old, there's a reason people move away from me on the subway. I'm glad you interpreted it that way.
    Well, ok, the cats out of the bag. I do expect 10.6.2 to do something significant for this card. For gosh sake something has to one day justify this investment...
    Both EVGA and Nvidia say it's all up to Apple.
    Apple says,... well Apple never says anything,.. but since they sell it on their website one would think it was in their interest to do their best. It's really not nice to sell one card as a 200 dollar option, granted 350 by itself, and another for well over 400 that is only marginally better. It's like looking for a Ford, changing your mind for the Porsche, and ending up getting a Ford with a Porsche sticker on it. This card wails in Windows, how can Apple deny that performance to it's own OS?
    While OS changes are incremental one doesn't necessarily expect that all things related to the industry will be. CUDA and Open CL are emerging technologies, but the 285 is real and out there. And it has been for quite some time now. Perhaps more honest marketing campaigns are needed, something like, "Here's the best video card for the Mac out there in existence, you'll just have to wait a few years to see that for yourself, maybe".
    Nah, it's not right, you buy a product for what it is, not for what it could be. If it gets better over time that's great, but right from the start it should be worth the price. The 285 hasn't been that yet.
    And we 285 owners waited for Snow, with all the talk of Apple's unleashing the power of the GPU. It came and the card ran slower. 10.6.1,... well at least the OS ran better. 10.6.2, well I can't say much about it, but if one can believe what they read, it looks like Apple is at least aware of certain things to be especially worked on. The question for me is to what degree they fine tune things. Can it really be as difficult to create a driver for Nvidia cards, unlike the drivers for ATIs which seem to work with such ease? It's almost like Apple and ATI are intrinsically bound somehow. For instance, with the 285 a new game like COD4 runs just perfectly for me with a 30" monitor, but another game under Rosetta runs not too well at all. Put the 4870 in and COD4 runs very well but not as good as the 285. The Rosetta game however runs great with the ATI. It's things like that I find to be very weird.
    If the history of OS X has shown us anything
    The history of anything only shows me we learn nothing from it. That's my biggest fear in this case, but I'm encouraged by what I hear.
    Expecting 10.6.1 or even 10.6.2, .3, or even .4 to be perfect
    That's an odd thing isn't it? How long would car companies last if they fine tuned their cars by analyzing how they failed and crashed for their customers on the road? "Yo, Edsel, I think we need a way to stop them once they're going".
    Yet as much as we pay for our computers and equipment we realize that the companies are using us as their R&D Depts. It's an interesting cycle, we're sold things that don't work well, give feedback to make them work well, and next time we buy the better product and it starts all over again.
    Well, it's been an interesting chat, full of sound and fury, signifying... well, probably something.

  • Battery Monitor problems

    I have a problem with battery monitor. My MacBook shows a charge of 30%, then suddenly goes into emergency sleep mode. If you plug the power in immediately, the system awakes again but the battery monitor then shows something like 7% charge.
    I have done everything in the knowledge base about battery problems. Letting it completely cycle (drain), reset pram, etc. I have bought two new batteries, but both act the same. The system goes into emergency sleep mode suddenly, no warning about a low battery and it happens when the charge left according to BM is around 30%.
    For me, this behaviour started with 10.5 (fresh install). Before that, the system was very reliable in this repect. It would give a ample warning. Not anymore.
    I have tried everything at the hardware level. I think it is safe to conclude that it is more likely a software problem that started with 10.5. Does anybody recognize this and is there anything I could do that is not in the knowledge base already?

    Thanks, but that didn't help much. The only thing resetting the SMC seemed to do was to make the battery "remaining charge" more accurate. Basically, it now tells me after unplugging with a full charge that I have 15 minutes remaining. The "battery low warning" also now appears. But my battery life is even more dismal than ever. Also, I just checked the system profile. Here's my battery stats NOW:
    Manufacturer: Sony
    Device name: ASMB012
    Pack Lot Code: 0003
    PCB Lot Code: 0000
    Firmware Version: 102a
    Hardware Revision: 0500
    Cell Revision: 0303
    Charge Information:
    Charge remaining (mAh): 263
    Fully charged: No
    Charging: No
    Full charge capacity (mAh): 473
    Health Information:
    Cycle count: 205
    Condition: Check battery
    Battery Installed: Yes
    Amperage (mA): -1991
    Voltage (mV): 11514
    Notice the full charge capacity has dropped significantly in just a couple weeks and in just 7 cycles!! This is ridiculous. Also note the amperage. A negative amperage? Odd.
    As mentioned above, I used to have well over 3 hours of battery life THE DAY BEFORE I upgraded to 10.5.5. These battery problems started the second 10.5.5 was installed. As far as I'm concerned 10.5.5 killed by battery somehow. I will be calling Apple and demanding a replacement. I can't think of any other options at this point.
    The other odd thing that happened after resetting the SMC was that I left the computer for a couple hours (powered on, AC) and when I cam back the screen was flashing on and off. Like the auto dim control went haywire...light, dark, light, dark, .... It returned to normal the second I moved the mouse. This is yet another oddity I never had until upgrading to 10.5.5.
    Message was edited by: Graek

  • Preview Monitor and Exporting Quality Issues

    Hello, in a previous life I was a video editor from the world of Avid and I just picked up Premiere for an emergency side mission at my current place of employment and I have run into a couple issues with CS4.
    1. The preview monitor for the Sequence displays a lower quality of the video that comes from the uploaded Clip and it also does not play back at a steady frame rate. However, when I look at the Clip in the secondary preview monitor that is reserved for clips, titles, etc, the video quality is as high as what is expected. How do get the sequence monitor to playback at the quality the clips are uploaded as and how do I get the playback to do so at a steady 30fps?
    2. My exporting experience was based around dubbing directly to Beta tapes and I never really had to do any digital file exporting. I need some tips on what to export a Sequence as that will retain a high amount of the quality while also keeping the file size to what will fit on a disk. The video length in this case would never be more than 5 minutes as I am only working on sales videos. Also, the file needs to be playable in Windows Media Player.
    Thank you in advance for any help on these issues.

    Please provide
    these details to help us help you.
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

  • Monitoring /var/adm/messages

    Hello to all,
    we are developing system for monitoring of the servers trough reading of the /var/adm/messages file.
    Since there are numerous messages in this file we are wondering what regular expressions to use in order to extract serious/critical alerts from this file.
    Does anybody have set of regular expressions to search for in this file for serious/critical events?
    Thanks in advance.
    Dejan

    Hi ,
    You can try to play whit /etc/syslog.conf . In this way you can made a filter for emergency and critical problem and redirect it to a specific file .
    For example , the following line will redirect all the the emargency and critical message to /var/adm/message.critical
    *.emerg;*.crit;* /var/adm/message.critical
    I hope this help to develop your tool
    xavier

  • Install KDEMOD, cant find a battery monitor applet

    Hi there,
    I'm new to Arch... I've been an Ubuntu user for about two years now. I was attracted to Arch one very specific thing:
    Rolling-Release... It just sucks to be stuck with the same old apps when everyone else (including the windows crowd) has cutting-edge features. So this just rocks in my book. I read that stability in Arch is good enough despite being extremely up-to-date so great.
    While doing my research I of course tried gentoo... Which I dislike so much after being left without a computer for 2 days straight while emerge downloaded, compiled and installed gnome. I have a slow connection (200mbps)... Maybe if downloads where asyncronous to compiling it would be slightly better.
    I'm also in love of apt-get. That's way I wouldn't give any distro a chance if they didn't offer a GREAT package manager. Pacman surpasses my expectations, I might have found a new love lol. It's lots faster than apt-get for installing programs, and so far I haven't got dependency errors.
    Now KISS just rocks... for some things. I enjoyed a lot working on my .conf files. I had done a bit of it on ubuntu but there it is pretty much authomatized. As I said, I like it because it gives you more control and forces you to gain some knowledge of the system. And KDEMOD is awesome beacause of it, no bloat alright!
    BUT: Where's my frigging Battery Monitor???!!! I live in fear my battery will die on me anytime... I usually consult it via /proc, but still, that isn't good enough. I think there should be a kdemod-utils-laptop or something to provide this kind of things... Any suggestions as what to do???

    darn it, my first post should've been something better lol
    Well the package in kdemod is called:
    kdemod-kdeutils-klaptopdaemon
    It works now

Maybe you are looking for

  • Can I make a bootcamp Partition on the HDD on an iMac 21.5" with SSD and HDD

    I am planning to buy an iMac 21.5" . I am not sure yet, whether to get one with ssd and hdd pre-installed. But I would like to, cause it's much faster. In the manual of the boot camp it says that if you have more than one internal hard drive and you

  • Excel process does not end properly

    Hello All. I am using excel in my program writing data into it an excel workbook and then later on reading data from it. I have written down the code of closing excel worlkbook and shutting down excel application hence releasing the handles for it. B

  • Saveing projects

    What is the proper format for saving a video project to play on a tv from a thumb drive?  Thank you!

  • Accounting document not made for Intercompany

    Hi Friends, My question is for interoffice customers sometimes need to fill in the Transportation code i.e., in Invoice Header data - "Foriegn Trade/Customs":   Tab - "Handling" Tab:ModeOfTrnsprt-Border - 3 (Road)                                     

  • Strange yellow color cast after CS4 install

    I just ran into a strange problem helping a friend install PS CS4. Everything seemed to go fine, but now all of a sudden his images are displayed with a strong yellow tint. I don't mean a slight color cast, I mean a STRONG yellow tint. The images app