Abrupt Shutdown

For the second time today (and never before) my computer suddenly shut down. It starts up again just fine but I cannot understand why this happens. I am appending my console log, perhaps someone can decipher it and let me know what's causing this. I had Safari with several tabs open, Entourage, Hardware Monitor, and I was playing a game of Solitaire when I went down.
Mac OS X Version 10.4.2 (Build 8C46)
2005-11-24 14:22:32 -0500
2005-11-24 14:22:33.563 HP Director (All-in-One)[99] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
(UNKNOWN)
The parser will retry as in 10.2, but the problem should be corrected in the plist.
2005-11-24 14:22:34.458 HP Director (All-in-One)[99] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
(UNKNOWN)
The parser will retry as in 10.2, but the problem should be corrected in the plist.
2005-11-24 14:22:34.468 HP Director (All-in-One)[99] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
(UNKNOWN)
The parser will retry as in 10.2, but the problem should be corrected in the plist.
2005-11-24 14:22:34.490 HP Director (All-in-One)[99] CFLog (0):
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
(UNKNOWN)
The parser will retry as in 10.2, but the problem should be corrected in the plist.
2005-11-24 14:22:36.326 SystemUIServer[93] Permitting load for class iClockMenu
2005-11-24 14:22:36.333 SystemUIServer[93] starting iClock 2 Menu Extra (1) 2.5.2
Nov 24 14:22:37 localhost 722534400: cupsd's bootstrap server port not found
2005-11-24 14:22:37.372 HimmelBar[100] HimmelBar is starting...
Nov 24 14:22:37 localhost mDNSResponder: Attempt to register record with invalid rdata: 262 WD-WMAES3955911.ttp4daemon.tcp.470312426444644. SRV <<INVALID LABEL LEN
2005-11-24 14:22:38.120 SystemUIServer[93] Permitting load for class iASMMenu
2005-11-24 14:22:38.122 SystemUIServer[93] starting iClock ASM Menu Extra...2.5.2
2005-11-24 14:22:38.376 Microsoft Database Daemon[108] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x3f03, name = 'EntourageDD11'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2005-11-24 14:22:38.379 Microsoft Database Daemon[108] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (EntourageDD11)
2005-11-24 14:22:38.404 HimmelBar[100] Filesystem notification will be fired after 3 second(s).
Nov 24 14:22:42 localhost 722534400: cupsd's bootstrap server port not found
2005-11-24 14:22:45.847 Safari[107] * Illegal NSTableView data source (<PHAttachmentController: 0x111b840>[object class: NSString, number of selected objects: 0]). Must implement numberOfRowsInTableView: and tableView:objectValueForTableColumn:row:
Nov 24 14:22:47 Miriam-Gillitts-Computer 722534400: cupsd's bootstrap server port not found
Nov 24 14:22:52 Miriam-Gillitts-Computer 722534400: cupsd's bootstrap server port not found
Nov 24 14:22:55 Miriam-Gillitts-Computer diskarbitrationd[38]: HimmelBar [100]:20483 not responding.
Nov 24 14:22:55 Miriam-Gillitts-Computer diskarbitrationd[38]: SystemUIServer [93]:15875 not responding.
Nov 24 14:22:55 Miriam-Gillitts-Computer diskarbitrationd[38]: SystemUIServer [93]:13347 not responding.
Nov 24 14:22:57 Miriam-Gillitts-Computer 722534400: cupsd's bootstrap server port not found
2005-11-24 14:23:02.160 SystemUIServer[93] internal ip address 0: fe80::211:24ff:fe1e:d1e4
2005-11-24 14:23:02.171 SystemUIServer[93] internal ip address 0: 192.168.2.27
2005-11-24 14:23:04.350 SystemUIServer[93] external ip address: 69.21.249.160
2005-11-24 14:23:04.351 SystemUIServer[93] external ip address: 69.21.249.160
2005-11-24 14:23:04.351 SystemUIServer[93] external ip address: 69.21.249.160
Nov 24 14:23:05 Miriam-Gillitts-Computer 722534400: cupsd's bootstrap server port not found
2005-11-24 14:23:05.610 SystemUIServer[93] internal ip address 0: 192.168.2.27
Nov 24 14:23:10 Miriam-Gillitts-Computer 722534400: cupsd's bootstrap server port not found
Nov 24 14:23:15 Miriam-Gillitts-Computer 722534400: cupsd's bootstrap server port not found
Nov 24 14:23:20 Miriam-Gillitts-Computer 722534400: cupsd's bootstrap server port not found
Nov 24 14:23:25 Miriam-Gillitts-Computer 722534400: cupsd's bootstrap server port not found
All help gratefully received!
Miriam

Hi again, Miriam —
Thanks for your response. Glad you enjoyed Thanksgiving (me, too).
Given this repeated behavior — with no glaring software-related cause — I think at this point it would be worthwhile checking hardware.
If I owned an iMac G5 and were facing these circumstances, I think I'd try the iMac Troubleshooting Assistant (it's 24-7); and if necessary, call AppleCare as soon as feasible. (I'm presuming that your iMac G5 is within warranty or that you have an AppleCare Protection Plan in force, so this call is free.) My experience is that these folks are generally very helpful — and, if nothing else, it's worhtwhile opening a case number about the situation, in case you need it later. In the meantime, being prepared by trying everything reasonable is a good idea. So here are my suggestions — please note that some may depend on which iMac G5 model you have:
  (1) Confirm that your iMac G5's power cord hasn't inadvertently become unseated (see Article 86817 for details on this problem).
  (2) Reset the System Management Unit (SMU) according to the instructions in Article 301733. Quoting from the article:
"The SMU... is a microcontroller chip on the logic board that controls all power functions for your computer. If your computer is experiencing any power issue, resetting the SMU may resolve it. The SMU controls several functions, including:
    • Telling the computer when to turn on, turn off, sleep, wake, idle, and so on.
    • Handling system resets from various commands.
    • Controlling the fans.
Note that resetting the SMU does not reset the PRAM." (But your symptoms don't indicate PRAM problems.)
  (3) Run Apple Hardware Test (AHT) to test several hardware components — including logic board, memory, modem, sound circuitry, video, and AirPort card. If you're not familiar with this, here's how: option-boot to your Install Disc (the one with "Apple Hardware Test" in very small print on the label). When you see icons representing viable startup volumes, select AHT and continue. (You may need to have a USB mouse handy if you normally use Bluetooth and it doesn't work properly — but it should.) Follow instructions to run the "Extended Tests." Note that this may take 15-30 minutes (or more, in some cases) — and that the final (video) tests look funny (sequencing screen color and plaid displays). Note all results carefully.
That should be adequate before calling — but, if you're comfortable proceeding, you may  want to —
  (4) Check your iMac G5's diagnostic LEDs.
  (5) Something that seems unlikely — but I'll mention, just in case: If your iMac G5 is a first-generation model, does its serial number fall within one of the following ranges? (Given in  menu »» About this Mac by clicking twice where you see "Version 10.4.2.") Serial Number ranges:
    • W8435xxxxxx - W8522xxxxxx
    • QP435xxxxxx - QP522xxxxxx
    • CK435xxxxxx - CK522xxxxxx
    • YD435xxxxxx - YD522xxxxxx
If so, please consult this document.
  (6) Please also read Article 302212 — although it may not apply to your iMac G5 model. (Note that OS X 10.4.3 is required.)
Again, Miriam — I wish you the best of good luck. I'd be interested to hear back how things work out for you.
Sincerely,
Dean
Edit: Gee, Miriam, I just read in another thread that you've had to have your iMac G5's logic board replaced previously. Everything I've suggested is probably "old hat" to you...

Similar Messages

  • What is causing a PowerMac G5/2.3GHz Dual Processor sudden abrupt shutdowns

    Hi all
    I am posting in hope that someone out there can help me solve this very puzzling problem.
    The machine: A PowerMac dual processor G5/2.3GHz (early 2005). 1.5G RAM. 250G HD. SuperDrive. Radeon 9650.
    The problem: When under some load, this machine will suddenly and abruptly shutdown as though someone pulled the power cord. There is no warning. Just a soft click, and it powers off. The machine can be manually restarted after the sudden shutdown with no problems.
    This problem is very replicable. (eg go to a particular website, play an embedded video, and boom, the machine shutsdown. Each and every time.) It was replicated at an Apple Store and at two Apple Authorized Service Providers.
    System.log said "PMU forced shutdown, cause = -122"
    Before the sudden shutdown, the machine seemed to be operating normally. The fans did not noticeably speed up. Activity Monitor showed no more than 50% CPU activity for each CPU. Temperature on both CPU was around at 70C before the sudden shutdown. Temperature and activity on both CPU goes up and down in tendem.
    If I use the Energy Saver system preference to change "Processor performance" to "Reduced", the problem goes away. (As measured by going to the same website and playing the same video. Even playing 5 videos simultaneously did not cause a sudden shutdown.)
    What have I done #1: I have reformat the hard drive with a 7-pass security wipe, followed by a clean-install of Tiger which was then brought up-to-date using Software Update. I then installed Safari 4.0.3. No other software is on the machine except Tiger and Safari. (Later installed Hardware Monitor to get me a handle on the temperatures.) The problem persisted.
    What have I done #2: I then installed a new PRAM battery and reset PMU using the switch on the motherboard. Resetting the PMU also resetted the PRAM. The problem persisted.
    What have I done #3: I then took the machine to an Apple Store. They found that they can replicate the problem easily. But, after 3 days of running the Apple Service Diagnostic, the diagnostic software didn't find any problem. They also did a thermal re-calibration. That didn't help either. Without an error code from the diagnostic software, the only "solution" the Apple Genius offered was to start swapping CPU, power supply and mother board at my expense. And even then, he has no idea which component to start swapping first. (Two independent Apple Authorized Service Providers offered the same non-diagnosis and roughly the same "solution".)
    Has anyone encountered such a problem before? What was the solution?
    How about an educated guess as to what's wrong?
    I want to, if possible, and if reasonable, repair this machine.
    Thanks in advance.
    Lara

    This sounds almost exactly like the problem I have. My G5 is also an Early 05 2.3G. I tried every tip I found on the forums from UPS vs. wall socket to stock RAM vs. 3rd party to booting from external HDs, etc.. I currently have 10.5.8 on it and it's running using the "Reduced" processor setting in Energy Saver prefs.
    I have also made a trip to The Apple Store where the AS folks ran their diagnostics but were usable to replicate my problem. I understand they "can't fix it if it ain't broke".
    Aside from the "Reduced" setting work-around has ANYONE actually solved this problem definitively? Although I have no interest in spending $1000 to fix this, I can't imagine disposing of it on Ebay.
    Assuming this is a hardware issue, this would mark the first insurmountable failure of any of the 10 or so Macs I have owned.
    Anyone? Anyone?

  • Oracle error after abrupt shutdown of server

    Hi..
    Today i was taking online backup using sapdba. During backup server abruptly shutdown due to power failure.
    Now i am trying to restart the server but it terminates with error code "2".
    Here is my startdb.log
    First trying to shutdown the database - May be,
    the database is in the nomount or mount state
    Wed Apr 29 22:23:50 IST 2009
    starting database
    SQL*Plus: Release 9.2.0.3.0 - Production on Wed Apr 29 22:23:50 2009
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Connected to an idle instance.
    ORACLE instance started.
    Total System Global Area  463963864 bytes
    Fixed Size               730840 bytes
    Variable Size            268435456 bytes
    Database Buffers       193462272 bytes
    Redo Buffers              1335296 bytes
    Database mounted.
    ORA-01113: file 2 needs media recovery
    ORA-01110: data file 2: '/oracle/PRD/sapdata3/prd_1/prd.data1'
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.3.0 - 64bit Production
    With the Partitioning option
    JServer Release 9.2.0.3.0 - Production
    Wed Apr 29 22:23:56 IST 2009
    Connect to the database to verify, that the database is now open
    R3trans check finished with return code: 12
    ERROR: Startup of database failed
        Notify Database Administrator.
    /usr/sap/PRD/SYS/exe/run/startdb: Terminating with error code 2
    It is asking for media recovery due to tablespace in BACKUP mode.
    I tried with command ALTER TABLESPACE '------' END BACKUP.
    but is give error like----
    Alter tablespace PSAPPRD end backup;
    Alter tablespace PSAPPRD end backup
    ERROR at line 1:
    ORA-01199: file 70 is not in online backup mode
    ORA-01110: data file 70: '/oracle/PRD/sapdata5/prd_54/prd.data54'
    ORA-01199: file 71 is not in online backup mode
    ORA-01110: data file 71: '/oracle/PRD/sapdata5/prd_55/prd.data55'
    ORA-01199: file 72 is not in online backup mode
    ORA-01110: data file 72: '/oracle/PRD/sapdata5/prd_56/prd.data56'
    ORA-01199: file 73 is not in online backup mode
    ORA-01110: data file 73: '/oracle/PRD/sapdata5/prd_57/prd.data57'
    ORA-01199: file 74 is not in online backup mode
    ORA-01110: data file 74: '/oracle/PRD/sapdata5/prd_58/prd.data58'
    ORA-01199: file 75 is not in online backup mode
    ORA-01110: data file 75: '/oracle/PRD/sapdata5/prd_59/prd.data59'
    ORA-01199: file 76 is not in online backup mode
    ORA-01110: data file 76: '/oracle/PRD/sapdata5/prd_60/prd.data60'
    ORA-01199: file 77 is not in online backup mode
    ORA-01110: data file 77: '/oracle/PRD/sapdata5/prd_61/prd.data61'
    ORA-01199: file 78 is not in online backup mode
    ORA-01110: data file 78: '/oracle/PRD/sapdata5/prd_62/prd.data6
    Now what i can do further.  file '2' is saying for media recovery but in this case i got a information form oracle site that media recovery should be avoided.
    Please help!
    Thanks in advance
    Regards.
    Raju

    hi. stefan,
    i got the following info from given query.
    DbFile                        File# Status
    /oracle/PRD/sapdata1/system_1/          1 NOT ACTIVE
    /oracle/PRD/sapdata3/prd_1/prd          2 ACTIVE
    /oracle/PRD/sapdata3/prd_2/prd          3 NOT ACTIVE
    /oracle/PRD/sapdata3/prd_3/prd          4 NOT ACTIVE
    /oracle/PRD/sapdata3/prd_4/prd          5 NOT ACTIVE
    /oracle/PRD/sapdata4/prd_5/prd          6 NOT ACTIVE
    /oracle/PRD/sapdata4/prd_6/prd          7 NOT ACTIVE
    /oracle/PRD/sapdata4/prd_7/prd          8 NOT ACTIVE
    /oracle/PRD/sapdata4/prd_8/prd          9 NOT ACTIVE
    /oracle/PRD/sapdata4/prd_9/prd            10 NOT ACTIVE
    /oracle/PRD/sapdata1/prd620_1/            11 NOT ACTIVE
    after that i ran the command as per your suggestion -but got the following--
    alter database datafile '/oracle/PRD/sapdata3/prd_1/prd.data1' end backup;
    alter database datafile '/oracle/PRD/sapdata3/prd_1/prd.data1' end backup
    ERROR at line 1:
    ORA-01235: END BACKUP failed for 1 file(s) and succeeded for 0
    ORA-01122: database file 2 failed verification check
    ORA-01110: data file 2: '/oracle/PRD/sapdata3/prd_1/prd.data1'
    ORA-01208: data file is an old version - not accessing current version
    Now what should i do.
    Please help!.
    Regards.
    Raju

  • Human Task form data needs to be refreshed in case of abrupt shutdown.

    Hi Everyone,
    I've got an interesting challenge in my BPM process and was hoping for some guidance.
    I'm using the 11g SOA suite. A BPM process within my application is designed such
    1. A start node passes a String to a service task
    2.The service task makes a call to a webservice operation and passes a payload to a human task
    3. The human task has an ADF form built on it and a user can add data to this form in addition to the payload it recd in step 2. When the human task is updated, we have partial submits that invoke webservices to update this data in the database.
    Now here's the challenge : If the form is abruptly closed, how do I refresh the data in my form so that it contains the changes made by the user. Do BPM processes auntomatically buffer such data? Or is there way in which I can loop back to the previous step of calling the webservice? All that my form has now is the payload from step 2, I'm resisiting writing a webservice call to refresh data in my form as I can't define what would trigger this webservice call.
    Also, another thought I had was that this is a BPM process made of synchronous calls throughout. How can I rectify this so that data is always up to date in the form? Adapters come to mind, but not too sure how. Any guidance is much appreciated.
    Many thanks,
    Preethi.

    Hi,
    First thoughts:
    I know you say that the data is not in a database, but I think that's the best place for a list like you're describing. Is there a reason why you don't want it in a database?
    If it can't be in a database, you could put it in a file and read the file to build your list. That should be pretty easy to do. For changes to the list you maintain the file instead of the hardcoding in the application.

  • RMI Service and FR Service abrupt shutdown

    Hi guys,
    I got problem with my BI 931 services, and it's weird since the behavior is randomly happen.
    The FR Server services and RMI services sometimes abrupt shut down, this is development server so the users are minimal (some cases no one using it at all).
    The architecture is like below (all of them are VMWares)
    1 essbase 931 server
    1 HBI Services server + SQL Server 2000
    1 HBI UIServices server
    It can't be network problem because DB and the services is under the same machine.
    Through the logs and found some errors but I think below err desc has the highest possibilities;
    Mon, 22 Sep 2008 13:55:10.0000000 [BRACKISH:9548] (IT_ATLI2_IOP:105) W - ATLI2 Failure occurred on connection to 10.10.11.109.3005: WSARecv() failed in TCPConnectionImpl::dispatch_failed() with: An existing connection was forcibly closed by the remote host.
    < Started by Process Monitor's I/O thead - Type-->BIID(0) >
    Wed, 08 Oct 2008 12:21:46.0000000 [BRACKISH:11748] (IT_ATLI2_IP:101) W - ATLI2 failure receiving data with minor_code 0 occurred in TCPConnectionImpl::dispatch_failed()
    < Started by Process Monitor's I/O thead - Type-->BIID(0) >
    Anybody can help or give me clue? Quite desperate here.
    Thanks
    Daniel -

    Anyone??

  • Abrupt shutdown of master node causes problem

    A service in usmbcom1 (LMID ) makes tpacall to a service which is
    present in
    both usmbapp1 ( master node LMID ) and usmbapp2 ( slave node LMID
    ) ( HERE
    usmbcom1 , usmbapp1 and usmbapp2 are LMIDs whereas the
    corresponding physical m/cs unames are usmbd5 , usmbd3 and usmbd4
    They are separate sun boxes) . LDBAL = Y and tpacall is done at
    25 / sec.
    Now there are 2 scenarios.
    1. While tpacall is in progress we kill the servers in usmbapp1
    using
    kill command ( not kill -9) . Then clean up the ipcs. Only
    few ( 3-5 out of a
    total of 5000 ) messages were lost . This is understandable since
    messages
    which were already in the queue got lost). The rest of the messages
    were
    processes by usmbapp2.
    2. In this case we switched off the sun box usmbapp1 ( m/c name
    usmbd3)
    while tpacall was in progress. This time we lost approx 50% of
    the
    messages. However if we go to the slave m/c i.e usmbapp2 and manually
    make it master ( tmadmin ... master) ., then from that point of
    time we stopped
    losing messages.
    Does that mean manual intervention is necessary if DBBL goes
    down? Is there anything which I am missing out while configuring
    the system?

    Hi Scott,
    You did understand the scenario and the problems.
    The answers are quite convincing.
    Actually the QA team here are doing failover testing
    and they have both these ( kill and m/c shutdown)
    as their test cases.
    However I would like to know about what you meant
    by High Availability Solutions.
    Do you also mean that if I shutdown my master m/c
    then no event would be written in the ULOG of slave,
    which can be monitored and used to convert the slave
    into master programatically ( I mean thru tpadmcall)
    Thanks
    Somashish
    Scott Orshan <[email protected]> wrote:
    Hi,
    I'm not sure if I completely comprehend your situation,
    but let me take
    a guess.
    When you killed the processes (including the Bridge),
    which by the way
    is a bad thing to do to TUXEDO, TCP notified the other
    connected nodes
    that the connection had dropped. This happens fairly quickly.
    But if you just turn off a machine, TCP may not detect
    it until it times
    out, which can take several minutes. Since TUXEDO was
    doing Round Robin
    load balancing, half the requests were sent to the Bridge,
    with a
    destination of the dead machine.
    To answer your final question, the DBBL has to be migrated
    manually,
    unless you are using one of our High Availability solutions
    that uses an
    external monitor.
    The reason is that it is very hard to distinguish between
    a network
    failure or slowdown, and a real failure of the Master
    node. And it would
    be very bad to have two machines in the domain acting
    as the Master.
         Scott Orshan
         BEA Systems
    Somashish Gupta wrote:
    A service in usmbcom1 (LMID ) makes tpacall to a servicewhich is
    present in
    both usmbapp1 ( master node LMID ) and usmbapp2 ( slavenode LMID
    ) ( HERE
    usmbcom1 , usmbapp1 and usmbapp2 are LMIDs whereas the
    corresponding physical m/cs unames are usmbd5 , usmbd3and usmbd4
    They are separate sun boxes) . LDBAL = Y and tpacallis done at
    25 / sec.
    Now there are 2 scenarios.
    1. While tpacall is in progress we kill the serversin usmbapp1
    using
    kill command ( not kill -9) . Then clean up theipcs. Only
    few ( 3-5 out of a
    total of 5000 ) messages were lost . This is understandablesince
    messages
    which were already in the queue got lost). The restof the messages
    were
    processes by usmbapp2.
    2. In this case we switched off the sun box usmbapp1( m/c name
    usmbd3)
    while tpacall was in progress. This time we lost approx50% of
    the
    messages. However if we go to the slave m/c i.e usmbapp2and manually
    make it master ( tmadmin ... master) ., then from thatpoint of
    time we stopped
    losing messages.
    Does that mean manual intervention is necessary if DBBLgoes
    down? Is there anything which I am missing out whileconfiguring
    the system?

  • Tomcat abrupt shutdown!

    Hi all
    I have installed tomcat 4 version. My application need to run 24/7 around the clock. But sometimes tomcat shutting down abruptly!!
    I was unable to find the reason!! Does any one faced this problem?
    Regards
    Abhilash

    Look at the server log, and tell us about the stack trace printed there.

  • Zufällige abrupte Shutdowns bei Lenovo D30 Workstation

    Hallo zusammen, bei meiner D30 treten immer wieder zufällige und nicht reproduzierbare Shutdowns auf, als wenn jemand den Stecker ziehen würde...kein Herunterfahren, einfach "OFF".Manchmal werden die Bildschirme einfach schwarz, manchmal kann ich für einen Bruckteil einer Sekunde einen Bluescreen erkennen, der allerdings nur so kurz erscheint, dass man keine Chance hat etwas zu lesen. Die Shutdowns treten völlig unvermittelt manchmal beim normalen Arbeiten (Cinema 4D, Adobe After Effects, Premiere...) auf, manchmal aber auch im Ruhezustand wenn kein Programm geöffnet ist.Interessanterweise sind diese Abstürze noch nie unter Vollast z.b. beim Rendern in C4D aufgetreten... das kann natürlich Zufall sein, ist mir nur aufgefallen. Manchmal läuft der Rechner den ganzen Tag ohne einen Absturz, manchal passiert das 2-3 mal hintereinander...Hat hier irgendjemand eine Idee, was das sein könnte? Ich nutze folgende Konfiguration:Lenovo D30 (435484G) mit Win7 Pro SP1BIOS-Version/-Datum: LENOVO A3KT30AUS, 01.10.2013CPU: 2x XEON E5-2696v2RAM: 128GB (alle 16 Steckplätze mit je 8GB belegt)Grafik: Palit Geforce GTX 970HDs: 4Stk. SSDs, 2 Stk. herkömmliche HDsSoundkarte: USB extern SPL Crimson Vielen Dank und liebe GrüßeUdo 

    Hallo zusammen, die Abstürze haben sich leider gehäuft, woraufhin ich das Betriebsystem neu aufgesetzt habe (win7pro).Läuft jetzt wieder stabiler, hab aber trotzdem noch hin und wieder Freezes oder Komplettabstürze wie oben beschrieben. In der Ereignisanzeige ist dabei fast immer folgender Fehler kurz vor dem Absturz vorhanden: iaStorS; EreignisID 143Das Gerät "\Device\RaidPort1" versucht, mehr als 8 Busse zu verwenden. Die maximal unterstützte Anzahl wird dabei überschritten. Verwenden Sie die aktuelle Dokumentation des Herstellers Ihres Speichercontrollers, um zu ermitteln, ob dieses Gerät und dieser Treiber für die Verwendung mit diesem Betriebssystem bestimmt sind. Soweit ich das verstehe ist das ein Festplatten-Controlller Problem, aktuelle Chipsatz-Treiber und neues Bios sind installiert...Hab ihr einen Tipp?   

  • 865PENeo2 FIS2R: abrupt shutdowns on heavy load

    Hello,
    I've build the system detailed below a few days ago and I have the following problem. When the system is under heavy load it suddenly shutdown like if the power cord was disconnected (although it is firmly connected). It has happen several times especially when rendering an MPEG2 file from a DV video using Pinnacle Studio 8, not at the start but some time later (could be even an after an hour of rendering). The computer wont start again pushing the power button on the case, I have to unplug the power cable and replug it, then the computers boots normally (but without pushing the power button the first time).
    I wonder if someone can help me understand what is the problem. I first though it could be an overheat but I've measured the temps and on heavy load CPU is at 57C and system at 54C.
    Maybe its my PSU: 13A on 12V is maybe not enough to drive 4 HDD + others.
    Any help is appreciated.

    13A on the 12V is definitely not enough to power your system PLUS the 4 hard drives. There is a power calculator somewhere in this forum. Use it to calculate what power ratings you need.
    Edit: Here's the link to the Power Supply Calculator
    Here's what the recommended power supply needs to have according to the calculator BUT you need one with a powerful 12A rail (look at Enermax power supplies):
    note: i guessed on some things, like the floppy and fans
    Recommended PSU: 491W (182W on +3.3v & +5v rails) for:
    -1 x Motherboard without onboard devices
    -3 x Fans (including PSU fans)
    -8 x Memory (128MB DDR)
    -1 x Graphic Card
    -1 x with powerful 3D Accelerator
    -1 x PCI Sound
    -1 x PCI Network Card
    -4 x HDD
    -1 x CD-RW
    -1 x DVD
    -1 x Floppy
    -1 x Keyboard
    -1 x Mouse
    -CPU: Intel P4 (2.6D GHz 0.13 µm µPGA478 @ 1.525 V with HTT)
    In the meantime, I recommend unplugging all of those extra hard drives before your Power supply fails (i don't know if it could happen, but i would just to be sure).

  • Booting with 3.14.* results in unexpected shutdown

    Problem description: Computer boots normally up until the moment before NVIDIA splash and entering login screen (quiet disabled shows no errors), but upon trying to do so suffers abrupt shutdown.
    Some cases the computer screen goes blank, followed by a short period of nothing until the fans start running at max.
    Adding "acpi=off"  to GRUB stops both above-mentioned events, instead the boot processs is simply halted at the same point with screen not being cleared and nothing else happening.
    The computer is an ASUS G55VW laptop, Intel i7 CPU, NVIDIA GTX660M (without Optimus).
    I'm running the stock kernel and the problem has persisted with all core versions of 3.14.* Downgrading NVIDIA from 337.* to 334.* has had no effect (337 depends on >3.14)
    Relevant journalctl (which tells me nothing): (Alternatively, pastebin link)
    -- Logs begin at Wed 2014-03-05 03:33:14 CET, end at Sun 2014-05-04 17:12:33 CEST. --
    May 01 16:01:14 arch systemd-journal[177]: Runtime journal is using 8.0M (max allowed 397.1M, trying to leave 595.7M free of 3.8G available → current limit 397.1M).
    May 01 16:01:14 arch systemd-journal[177]: Runtime journal is using 8.0M (max allowed 397.1M, trying to leave 595.7M free of 3.8G available → current limit 397.1M).
    May 01 16:01:14 arch kernel: Initializing cgroup subsys cpuset
    May 01 16:01:14 arch kernel: Initializing cgroup subsys cpu
    May 01 16:01:14 arch kernel: Initializing cgroup subsys cpuacct
    May 01 16:01:14 arch kernel: Linux version 3.14.2-1-ARCH (nobody@var-lib-archbuild-testing-x86_64-tobias) (gcc version 4.9.0 (GCC) ) #1 SMP PREEMPT Sun Apr 27 11:28:44 CEST 2014
    May 01 16:01:14 arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7919229d-db26-4075-ac4b-97d2fa5fc984 rw quiet
    May 01 16:01:14 arch kernel: e820: BIOS-provided physical RAM map:
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dd6f5fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000dd6f6000-0x00000000dd6f7fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000dd6f8000-0x00000000dd704fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000dd705000-0x00000000ddd05fff] ACPI NVS
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd06000-0x00000000ddd08fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd09000-0x00000000ddd1ffff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd20000-0x00000000ddd25fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd26000-0x00000000ddd27fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd28000-0x00000000ddd31fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd32000-0x00000000ddec4fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddec5000-0x00000000ddec8fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddec9000-0x00000000ddf12fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf13000-0x00000000ddf37fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf38000-0x00000000ddf3afff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf3b000-0x00000000ddf3cfff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf3d000-0x00000000ddf53fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf54000-0x00000000ddf59fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf5a000-0x00000000ddf61fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf62000-0x00000000ddf62fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf63000-0x00000000ddf71fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf72000-0x00000000ddf72fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf73000-0x00000000ddf7dfff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf7e000-0x00000000ddf82fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf83000-0x00000000ddfaefff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfaf000-0x00000000ddfaffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfb0000-0x00000000ddfbffff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfc0000-0x00000000ddfe7fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfe8000-0x00000000ddffbfff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddffc000-0x00000000ddffcfff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddffd000-0x00000000ddffdfff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddffe000-0x00000000ddffffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de000000-0x00000000de001fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de002000-0x00000000de006fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de007000-0x00000000de01afff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de01b000-0x00000000de5e2fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de5e3000-0x00000000de862fff] ACPI NVS
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de863000-0x00000000de867fff] ACPI data
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de868000-0x00000000de868fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de869000-0x00000000de8abfff] ACPI NVS
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de8ac000-0x00000000decbefff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000decbf000-0x00000000deff3fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000deff4000-0x00000000deffffff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021f3fffff] usable
    May 01 16:01:14 arch kernel: NX (Execute Disable) protection: active
    May 01 16:01:14 arch kernel: efi: EFI v2.31 by American Megatrends
    May 01 16:01:14 arch kernel: efi: ACPI=0xde839000 ACPI 2.0=0xde839000 SMBIOS=0xf04c0 MPS=0xfd4d0
    May 01 16:01:14 arch kernel: efi: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000008000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem01: type=7, attr=0xf, range=[0x0000000000008000-0x000000000005d000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem02: type=4, attr=0xf, range=[0x000000000005d000-0x0000000000060000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem03: type=3, attr=0xf, range=[0x0000000000060000-0x000000000009f000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem04: type=6, attr=0x800000000000000f, range=[0x000000000009f000-0x00000000000a0000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem05: type=7, attr=0xf, range=[0x0000000000100000-0x0000000001000000) (15MB)
    May 01 16:01:14 arch kernel: efi: mem06: type=2, attr=0xf, range=[0x0000000001000000-0x000000000205b000) (16MB)
    May 01 16:01:14 arch kernel: efi: mem07: type=7, attr=0xf, range=[0x000000000205b000-0x00000000379d4000) (857MB)
    May 01 16:01:14 arch kernel: efi: mem08: type=2, attr=0xf, range=[0x00000000379d4000-0x0000000037ce2000) (3MB)
    May 01 16:01:14 arch kernel: efi: mem09: type=7, attr=0xf, range=[0x0000000037ce2000-0x000000009dbfb000) (1631MB)
    May 01 16:01:14 arch kernel: efi: mem10: type=2, attr=0xf, range=[0x000000009dbfb000-0x00000000d2732000) (843MB)
    May 01 16:01:14 arch kernel: efi: mem11: type=1, attr=0xf, range=[0x00000000d2732000-0x00000000d274f000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem12: type=7, attr=0xf, range=[0x00000000d274f000-0x00000000d276c000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem13: type=4, attr=0xf, range=[0x00000000d276c000-0x00000000d293d000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem14: type=7, attr=0xf, range=[0x00000000d293d000-0x00000000d2949000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem15: type=4, attr=0xf, range=[0x00000000d2949000-0x00000000d29a2000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem16: type=7, attr=0xf, range=[0x00000000d29a2000-0x00000000d2ac9000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem17: type=4, attr=0xf, range=[0x00000000d2ac9000-0x00000000dc390000) (152MB)
    May 01 16:01:14 arch kernel: efi: mem18: type=7, attr=0xf, range=[0x00000000dc390000-0x00000000dc393000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem19: type=4, attr=0xf, range=[0x00000000dc393000-0x00000000dc3cd000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem20: type=7, attr=0xf, range=[0x00000000dc3cd000-0x00000000dc3ce000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem21: type=4, attr=0xf, range=[0x00000000dc3ce000-0x00000000dd07f000) (12MB)
    May 01 16:01:14 arch kernel: efi: mem22: type=7, attr=0xf, range=[0x00000000dd07f000-0x00000000dd6d1000) (6MB)
    May 01 16:01:14 arch kernel: efi: mem23: type=2, attr=0xf, range=[0x00000000dd6d1000-0x00000000dd6dd000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem24: type=3, attr=0xf, range=[0x00000000dd6dd000-0x00000000dd6f6000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem25: type=6, attr=0x800000000000000f, range=[0x00000000dd6f6000-0x00000000dd6f8000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem26: type=3, attr=0xf, range=[0x00000000dd6f8000-0x00000000dd705000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem27: type=10, attr=0xf, range=[0x00000000dd705000-0x00000000ddd06000) (6MB)
    May 01 16:01:14 arch kernel: efi: mem28: type=5, attr=0x800000000000000f, range=[0x00000000ddd06000-0x00000000ddd09000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem29: type=3, attr=0xf, range=[0x00000000ddd09000-0x00000000ddd20000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem30: type=5, attr=0x800000000000000f, range=[0x00000000ddd20000-0x00000000ddd26000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem31: type=3, attr=0xf, range=[0x00000000ddd26000-0x00000000ddd28000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem32: type=5, attr=0x800000000000000f, range=[0x00000000ddd28000-0x00000000ddd32000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem33: type=3, attr=0xf, range=[0x00000000ddd32000-0x00000000ddec5000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem34: type=5, attr=0x800000000000000f, range=[0x00000000ddec5000-0x00000000ddec9000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem35: type=3, attr=0xf, range=[0x00000000ddec9000-0x00000000ddf13000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem36: type=5, attr=0x800000000000000f, range=[0x00000000ddf13000-0x00000000ddf1a000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem37: type=6, attr=0x800000000000000f, range=[0x00000000ddf1a000-0x00000000ddf27000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem38: type=5, attr=0x800000000000000f, range=[0x00000000ddf27000-0x00000000ddf38000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem39: type=3, attr=0xf, range=[0x00000000ddf38000-0x00000000ddf3b000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem40: type=5, attr=0x800000000000000f, range=[0x00000000ddf3b000-0x00000000ddf3d000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem41: type=3, attr=0xf, range=[0x00000000ddf3d000-0x00000000ddf54000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem42: type=5, attr=0x800000000000000f, range=[0x00000000ddf54000-0x00000000ddf5a000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem43: type=3, attr=0xf, range=[0x00000000ddf5a000-0x00000000ddf62000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem44: type=5, attr=0x800000000000000f, range=[0x00000000ddf62000-0x00000000ddf63000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem45: type=3, attr=0xf, range=[0x00000000ddf63000-0x00000000ddf72000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem46: type=5, attr=0x800000000000000f, range=[0x00000000ddf72000-0x00000000ddf73000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem47: type=3, attr=0xf, range=[0x00000000ddf73000-0x00000000ddf7e000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem48: type=5, attr=0x800000000000000f, range=[0x00000000ddf7e000-0x00000000ddf83000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem49: type=3, attr=0xf, range=[0x00000000ddf83000-0x00000000ddfaf000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem50: type=5, attr=0x800000000000000f, range=[0x00000000ddfaf000-0x00000000ddfb0000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem51: type=3, attr=0xf, range=[0x00000000ddfb0000-0x00000000ddfc0000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem52: type=5, attr=0x800000000000000f, range=[0x00000000ddfc0000-0x00000000ddfe8000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem53: type=3, attr=0xf, range=[0x00000000ddfe8000-0x00000000ddffc000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem54: type=5, attr=0x800000000000000f, range=[0x00000000ddffc000-0x00000000ddffd000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem55: type=3, attr=0xf, range=[0x00000000ddffd000-0x00000000ddffe000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem56: type=5, attr=0x800000000000000f, range=[0x00000000ddffe000-0x00000000de000000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem57: type=3, attr=0xf, range=[0x00000000de000000-0x00000000de002000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem58: type=5, attr=0x800000000000000f, range=[0x00000000de002000-0x00000000de007000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem59: type=3, attr=0xf, range=[0x00000000de007000-0x00000000de01b000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem60: type=6, attr=0x800000000000000f, range=[0x00000000de01b000-0x00000000de09c000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem61: type=5, attr=0x800000000000000f, range=[0x00000000de09c000-0x00000000de0b9000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem62: type=6, attr=0x800000000000000f, range=[0x00000000de0b9000-0x00000000de0bf000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem63: type=6, attr=0x800000000000000f, range=[0x00000000de0bf000-0x00000000de0c1000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem64: type=6, attr=0x800000000000000f, range=[0x00000000de0c1000-0x00000000de0e3000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem65: type=0, attr=0xf, range=[0x00000000de0e3000-0x00000000de437000) (3MB)
    May 01 16:01:14 arch kernel: efi: mem66: type=0, attr=0xf, range=[0x00000000de437000-0x00000000de578000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem67: type=0, attr=0xf, range=[0x00000000de578000-0x00000000de57e000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem68: type=0, attr=0xf, range=[0x00000000de57e000-0x00000000de5e3000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem69: type=10, attr=0xf, range=[0x00000000de5e3000-0x00000000de699000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem70: type=10, attr=0xf, range=[0x00000000de699000-0x00000000de863000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem71: type=9, attr=0xf, range=[0x00000000de863000-0x00000000de868000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem72: type=4, attr=0xf, range=[0x00000000de868000-0x00000000de869000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem73: type=10, attr=0xf, range=[0x00000000de869000-0x00000000de8ac000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem74: type=4, attr=0xf, range=[0x00000000de8ac000-0x00000000de9fa000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem75: type=3, attr=0xf, range=[0x00000000de9fa000-0x00000000dec96000) (2MB)
    May 01 16:01:14 arch kernel: efi: mem76: type=4, attr=0xf, range=[0x00000000dec96000-0x00000000deca6000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem77: type=3, attr=0xf, range=[0x00000000deca6000-0x00000000decb8000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem78: type=4, attr=0xf, range=[0x00000000decb8000-0x00000000decbf000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem79: type=6, attr=0x800000000000000f, range=[0x00000000decbf000-0x00000000deff4000) (3MB)
    May 01 16:01:14 arch kernel: efi: mem80: type=4, attr=0xf, range=[0x00000000deff4000-0x00000000df000000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem81: type=7, attr=0xf, range=[0x0000000100000000-0x000000021f400000) (4596MB)
    May 01 16:01:14 arch kernel: efi: mem82: type=11, attr=0x8000000000000001, range=[0x00000000f8000000-0x00000000fc000000) (64MB)
    May 01 16:01:14 arch kernel: efi: mem83: type=11, attr=0x8000000000000001, range=[0x00000000fec00000-0x00000000fec01000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem84: type=11, attr=0x8000000000000001, range=[0x00000000fed00000-0x00000000fed04000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem85: type=11, attr=0x8000000000000001, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem86: type=11, attr=0x8000000000000001, range=[0x00000000fee00000-0x00000000fee01000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem87: type=11, attr=0x8000000000000001, range=[0x00000000ff000000-0x0000000100000000) (16MB)
    May 01 16:01:14 arch kernel: SMBIOS 2.7 present.
    May 01 16:01:14 arch kernel: DMI: ASUSTeK COMPUTER INC. G55VW/G55VW, BIOS G55VW.217 11/05/2012
    May 01 16:01:14 arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    May 01 16:01:14 arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    May 01 16:01:14 arch kernel: No AGP bridge found
    May 01 16:01:14 arch kernel: e820: last_pfn = 0x21f400 max_arch_pfn = 0x400000000
    May 01 16:01:14 arch kernel: MTRR default type: uncachable
    May 01 16:01:14 arch kernel: MTRR fixed ranges enabled:
    May 01 16:01:14 arch kernel: 00000-9FFFF write-back
    May 01 16:01:14 arch kernel: A0000-BFFFF uncachable
    May 01 16:01:14 arch kernel: C0000-CFFFF write-protect
    May 01 16:01:14 arch kernel: D0000-DFFFF uncachable
    May 01 16:01:14 arch kernel: E0000-FFFFF write-protect
    May 01 16:01:14 arch kernel: MTRR variable ranges enabled:
    May 01 16:01:14 arch kernel: 0 base 000000000 mask E00000000 write-back
    May 01 16:01:14 arch kernel: 1 base 200000000 mask FF0000000 write-back
    May 01 16:01:14 arch kernel: 2 base 210000000 mask FF8000000 write-back
    May 01 16:01:14 arch kernel: 3 base 218000000 mask FFC000000 write-back
    May 01 16:01:14 arch kernel: 4 base 21C000000 mask FFE000000 write-back
    May 01 16:01:14 arch kernel: 5 base 21E000000 mask FFF000000 write-back
    May 01 16:01:14 arch kernel: 6 base 21F000000 mask FFFC00000 write-back
    May 01 16:01:14 arch kernel: 7 base 0E0000000 mask FE0000000 uncachable
    May 01 16:01:14 arch kernel: 8 base 0DFC00000 mask FFFC00000 uncachable
    May 01 16:01:14 arch kernel: 9 disabled
    May 01 16:01:14 arch kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    May 01 16:01:14 arch kernel: e820: update [mem 0xdfc00000-0xffffffff] usable ==> reserved
    May 01 16:01:14 arch kernel: e820: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
    May 01 16:01:14 arch kernel: found SMP MP-table at [mem 0x000fd830-0x000fd83f] mapped at [ffff8800000fd830]
    May 01 16:01:14 arch kernel: Scanning 1 areas for low memory corruption
    May 01 16:01:14 arch kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    May 01 16:01:14 arch kernel: [mem 0x00000000-0x000fffff] page 4k
    May 01 16:01:14 arch kernel: BRK [0x01b39000, 0x01b39fff] PGTABLE
    May 01 16:01:14 arch kernel: BRK [0x01b3a000, 0x01b3afff] PGTABLE
    May 01 16:01:14 arch kernel: BRK [0x01b3b000, 0x01b3bfff] PGTABLE
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x21f200000-0x21f3fffff]
    May 01 16:01:14 arch kernel: [mem 0x21f200000-0x21f3fffff] page 2M
    May 01 16:01:14 arch kernel: BRK [0x01b3c000, 0x01b3cfff] PGTABLE
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x21c000000-0x21f1fffff]
    May 01 16:01:14 arch kernel: [mem 0x21c000000-0x21f1fffff] page 2M
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x200000000-0x21bffffff]
    May 01 16:01:14 arch kernel: [mem 0x200000000-0x21bffffff] page 2M
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x00100000-0xdd6f5fff]
    May 01 16:01:14 arch kernel: [mem 0x00100000-0x001fffff] page 4k
    May 01 16:01:14 arch kernel: [mem 0x00200000-0xdd5fffff] page 2M
    May 01 16:01:14 arch kernel: [mem 0xdd600000-0xdd6f5fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xdd6f8000-0xdd704fff]
    May 01 16:01:14 arch kernel: [mem 0xdd6f8000-0xdd704fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddd09000-0xddd1ffff]
    May 01 16:01:14 arch kernel: [mem 0xddd09000-0xddd1ffff] page 4k
    May 01 16:01:14 arch kernel: BRK [0x01b3d000, 0x01b3dfff] PGTABLE
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddd26000-0xddd27fff]
    May 01 16:01:14 arch kernel: [mem 0xddd26000-0xddd27fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddd32000-0xddec4fff]
    May 01 16:01:14 arch kernel: [mem 0xddd32000-0xddec4fff] page 4k
    May 01 16:01:14 arch kernel: BRK [0x01b3e000, 0x01b3efff] PGTABLE
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddec9000-0xddf12fff]
    May 01 16:01:14 arch kernel: [mem 0xddec9000-0xddf12fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf38000-0xddf3afff]
    May 01 16:01:14 arch kernel: [mem 0xddf38000-0xddf3afff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf3d000-0xddf53fff]
    May 01 16:01:14 arch kernel: [mem 0xddf3d000-0xddf53fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf5a000-0xddf61fff]
    May 01 16:01:14 arch kernel: [mem 0xddf5a000-0xddf61fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf63000-0xddf71fff]
    May 01 16:01:14 arch kernel: [mem 0xddf63000-0xddf71fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf73000-0xddf7dfff]
    May 01 16:01:14 arch kernel: [mem 0xddf73000-0xddf7dfff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf83000-0xddfaefff]
    May 01 16:01:14 arch kernel: [mem 0xddf83000-0xddfaefff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddfb0000-0xddfbffff]
    May 01 16:01:14 arch kernel: [mem 0xddfb0000-0xddfbffff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddfe8000-0xddffbfff]
    May 01 16:01:14 arch kernel: [mem 0xddfe8000-0xddffbfff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddffd000-0xddffdfff]
    May 01 16:01:14 arch kernel: [mem 0xddffd000-0xddffdfff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde000000-0xde001fff]
    May 01 16:01:14 arch kernel: [mem 0xde000000-0xde001fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde007000-0xde01afff]
    May 01 16:01:14 arch kernel: [mem 0xde007000-0xde01afff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde868000-0xde868fff]
    May 01 16:01:14 arch kernel: [mem 0xde868000-0xde868fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde8ac000-0xdecbefff]
    May 01 16:01:14 arch kernel: [mem 0xde8ac000-0xde9fffff] page 4k
    May 01 16:01:14 arch kernel: [mem 0xdea00000-0xdebfffff] page 2M
    May 01 16:01:14 arch kernel: [mem 0xdec00000-0xdecbefff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xdeff4000-0xdeffffff]
    May 01 16:01:14 arch kernel: [mem 0xdeff4000-0xdeffffff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
    May 01 16:01:14 arch kernel: [mem 0x100000000-0x1ffffffff] page 2M
    May 01 16:01:14 arch kernel: RAMDISK: [mem 0x379d4000-0x37ce1fff]
    May 01 16:01:14 arch kernel: ACPI: RSDP 00000000de839000 000024 (v02 _ASUS_)
    May 01 16:01:14 arch kernel: ACPI: XSDT 00000000de839080 00007C (v01 _ASUS_ Notebook 01072009 AMI 00010013)
    May 01 16:01:14 arch kernel: ACPI: FACP 00000000de849e28 00010C (v05 _ASUS_ Notebook 01072009 AMI 00010013)
    May 01 16:01:14 arch kernel: ACPI: DSDT 00000000de839190 010C93 (v02 _ASUS_ Notebook 00000013 INTL 20091112)
    May 01 16:01:14 arch kernel: ACPI: FACS 00000000de860080 000040
    May 01 16:01:14 arch kernel: ACPI: APIC 00000000de849f38 000092 (v03 _ASUS_ Notebook 01072009 AMI 00010013)
    May 01 16:01:14 arch kernel: ACPI: FPDT 00000000de849fd0 000044 (v01 _ASUS_ Notebook 01072009 AMI 00010013)
    May 01 16:01:14 arch kernel: ACPI: ECDT 00000000de84a018 0000C1 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
    May 01 16:01:14 arch kernel: ACPI: MCFG 00000000de84a0e0 00003C (v01 _ASUS_ Notebook 01072009 MSFT 00000097)
    May 01 16:01:14 arch kernel: ACPI: SLIC 00000000de84a120 000176 (v01 _ASUS_ Notebook 01072009 ASUS 00000001)
    May 01 16:01:14 arch kernel: ACPI: HPET 00000000de84a298 000038 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84a2d0 00066E (v01 AhciR1 AhciTab1 00001000 INTL 20091112)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84a940 00049E (v01 AhciR2 AhciTab2 00001000 INTL 20091112)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84ade0 00090A (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84b6f0 000A92 (v01 PmRef CpuPm 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Local APIC address 0xfee00000
    May 01 16:01:14 arch kernel: No NUMA configuration found
    May 01 16:01:14 arch kernel: Faking a node at [mem 0x0000000000000000-0x000000021f3fffff]
    May 01 16:01:14 arch kernel: Initmem setup node 0 [mem 0x00000000-0x21f3fffff]
    May 01 16:01:14 arch kernel: NODE_DATA [mem 0x21f3ef000-0x21f3f3fff]
    May 01 16:01:14 arch kernel: [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880216a00000-ffff88021e9fffff] on node 0
    May 01 16:01:14 arch kernel: Zone ranges:
    May 01 16:01:14 arch kernel: DMA [mem 0x00001000-0x00ffffff]
    May 01 16:01:14 arch kernel: DMA32 [mem 0x01000000-0xffffffff]
    May 01 16:01:14 arch kernel: Normal [mem 0x100000000-0x21f3fffff]
    May 01 16:01:14 arch kernel: Movable zone start for each node
    May 01 16:01:14 arch kernel: Early memory node ranges
    May 01 16:01:14 arch kernel: node 0: [mem 0x00001000-0x0009efff]
    May 01 16:01:14 arch kernel: node 0: [mem 0x00100000-0xdd6f5fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xdd6f8000-0xdd704fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddd09000-0xddd1ffff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddd26000-0xddd27fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddd32000-0xddec4fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddec9000-0xddf12fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf38000-0xddf3afff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf3d000-0xddf53fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf5a000-0xddf61fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf63000-0xddf71fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf73000-0xddf7dfff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf83000-0xddfaefff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddfb0000-0xddfbffff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddfe8000-0xddffbfff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddffd000-0xddffdfff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xde000000-0xde001fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xde007000-0xde01afff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xde868000-0xde868fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xde8ac000-0xdecbefff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xdeff4000-0xdeffffff]
    May 01 16:01:14 arch kernel: node 0: [mem 0x100000000-0x21f3fffff]
    May 01 16:01:14 arch kernel: On node 0 totalpages: 2085210
    May 01 16:01:14 arch kernel: DMA zone: 64 pages used for memmap
    May 01 16:01:14 arch kernel: DMA zone: 28 pages reserved
    May 01 16:01:14 arch kernel: DMA zone: 3998 pages, LIFO batch:0
    May 01 16:01:14 arch kernel: DMA32 zone: 14135 pages used for memmap
    May 01 16:01:14 arch kernel: DMA32 zone: 904636 pages, LIFO batch:31
    May 01 16:01:14 arch kernel: Normal zone: 18384 pages used for memmap
    May 01 16:01:14 arch kernel: Normal zone: 1176576 pages, LIFO batch:31
    May 01 16:01:14 arch kernel: ACPI: PM-Timer IO Port: 0x408
    May 01 16:01:14 arch kernel: ACPI: Local APIC address 0xfee00000
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    May 01 16:01:14 arch kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    May 01 16:01:14 arch kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    May 01 16:01:14 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    May 01 16:01:14 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    May 01 16:01:14 arch kernel: ACPI: IRQ0 used by override.
    May 01 16:01:14 arch kernel: ACPI: IRQ2 used by override.
    May 01 16:01:14 arch kernel: ACPI: IRQ9 used by override.
    May 01 16:01:14 arch kernel: Using ACPI (MADT) for SMP configuration information
    May 01 16:01:14 arch kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
    May 01 16:01:14 arch kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
    May 01 16:01:14 arch kernel: nr_irqs_gsi: 40
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdd6f6000-0xdd6f7fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdd705000-0xddd05fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddd06000-0xddd08fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddd20000-0xddd25fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddd28000-0xddd31fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddec5000-0xddec8fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf13000-0xddf37fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf3b000-0xddf3cfff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf54000-0xddf59fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf62000-0xddf62fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf72000-0xddf72fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf7e000-0xddf82fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddfaf000-0xddfaffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddfc0000-0xddfe7fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddffc000-0xddffcfff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddffe000-0xddffffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde002000-0xde006fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde01b000-0xde5e2fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde5e3000-0xde862fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde863000-0xde867fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde869000-0xde8abfff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdecbf000-0xdeff3fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdf000000-0xf7ffffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
    May 01 16:01:14 arch kernel: e820: [mem 0xdf000000-0xf7ffffff] available for PCI devices
    May 01 16:01:14 arch kernel: Booting paravirtualized kernel on bare hardware
    May 01 16:01:14 arch kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    May 01 16:01:14 arch kernel: PERCPU: Embedded 29 pages/cpu @ffff88021f000000 s87040 r8192 d23552 u262144
    May 01 16:01:14 arch kernel: pcpu-alloc: s87040 r8192 d23552 u262144 alloc=1*2097152
    May 01 16:01:14 arch kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    May 01 16:01:14 arch kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2052599
    May 01 16:01:14 arch kernel: Policy zone: Normal
    May 01 16:01:14 arch kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7919229d-db26-4075-ac4b-97d2fa5fc984 rw quiet
    May 01 16:01:14 arch kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    May 01 16:01:14 arch kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340
    May 01 16:01:14 arch kernel: Checking aperture...
    May 01 16:01:14 arch kernel: No AGP bridge found
    May 01 16:01:14 arch kernel: Calgary: detecting Calgary via BIOS EBDA area
    May 01 16:01:14 arch kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    May 01 16:01:14 arch kernel: Memory: 7948780K/8340840K available (5229K kernel code, 857K rwdata, 1632K rodata, 1120K init, 1288K bss, 392060K reserved)
    May 01 16:01:14 arch kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    May 01 16:01:14 arch kernel: Preemptible hierarchical RCU implementation.
    May 01 16:01:14 arch kernel: RCU dyntick-idle grace-period acceleration is enabled.
    May 01 16:01:14 arch kernel: Dump stacks of tasks blocking RCU-preempt GP.
    May 01 16:01:14 arch kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
    May 01 16:01:14 arch kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    May 01 16:01:14 arch kernel: NR_IRQS:8448 nr_irqs:744 16
    May 01 16:01:14 arch kernel: Console: colour dummy device 80x25
    May 01 16:01:14 arch kernel: console [tty0] enabled
    May 01 16:01:14 arch kernel: allocated 33554432 bytes of page_cgroup
    May 01 16:01:14 arch kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    May 01 16:01:14 arch kernel: hpet clockevent registered
    May 01 16:01:14 arch kernel: tsc: Fast TSC calibration using PIT
    May 01 16:01:14 arch kernel: tsc: Detected 2294.759 MHz processor
    May 01 16:01:14 arch kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4591.74 BogoMIPS (lpj=7649196)
    May 01 16:01:14 arch kernel: pid_max: default: 32768 minimum: 301
    May 01 16:01:14 arch kernel: ACPI: Core revision 20131218
    May 01 16:01:14 arch kernel: ACPI: All ACPI Tables successfully acquired
    May 01 16:01:14 arch kernel: Security Framework initialized
    May 01 16:01:14 arch kernel: Yama: becoming mindful.
    May 01 16:01:14 arch kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    May 01 16:01:14 arch kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    May 01 16:01:14 arch kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: Initializing cgroup subsys memory
    May 01 16:01:14 arch kernel: Initializing cgroup subsys devices
    May 01 16:01:14 arch kernel: Initializing cgroup subsys freezer
    May 01 16:01:14 arch kernel: Initializing cgroup subsys net_cls
    May 01 16:01:14 arch kernel: Initializing cgroup subsys blkio
    May 01 16:01:14 arch kernel: CPU: Physical Processor ID: 0
    May 01 16:01:14 arch kernel: CPU: Processor Core ID: 0
    May 01 16:01:14 arch kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    May 01 16:01:14 arch kernel: mce: CPU supports 9 MCE banks
    May 01 16:01:14 arch kernel: CPU0: Thermal monitoring enabled (TM1)
    May 01 16:01:14 arch 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
    May 01 16:01:14 arch kernel: Freeing SMP alternatives memory: 20K (ffffffff819f0000 - ffffffff819f5000)
    May 01 16:01:14 arch kernel: ftrace: allocating 20026 entries in 79 pages
    May 01 16:01:14 arch kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    May 01 16:01:14 arch kernel: smpboot: CPU0: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz (fam: 06, model: 3a, stepping: 09)
    May 01 16:01:14 arch kernel: TSC deadline timer enabled
    May 01 16:01:14 arch kernel: Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
    May 01 16:01:14 arch kernel: ... version: 3
    May 01 16:01:14 arch kernel: ... bit width: 48
    May 01 16:01:14 arch kernel: ... generic registers: 4
    May 01 16:01:14 arch kernel: ... value mask: 0000ffffffffffff
    May 01 16:01:14 arch kernel: ... max period: 0000ffffffffffff
    May 01 16:01:14 arch kernel: ... fixed-purpose events: 3
    May 01 16:01:14 arch kernel: ... event mask: 000000070000000f
    May 01 16:01:14 arch kernel: x86: Booting SMP configuration:
    May 01 16:01:14 arch kernel: .... node #0, CPUs: #1
    May 01 16:01:14 arch kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    May 01 16:01:14 arch kernel: #2 #3 #4 #5 #6 #7
    May 01 16:01:14 arch kernel: x86: Booted up 1 node, 8 CPUs
    May 01 16:01:14 arch kernel: smpboot: Total of 8 processors activated (36730.98 BogoMIPS)
    May 01 16:01:14 arch kernel: devtmpfs: initialized
    May 01 16:01:14 arch kernel: PM: Registering ACPI NVS region [mem 0xdd705000-0xddd05fff] (6295552 bytes)
    May 01 16:01:14 arch kernel: PM: Registering ACPI NVS region [mem 0xde5e3000-0xde862fff] (2621440 bytes)
    May 01 16:01:14 arch kernel: PM: Registering ACPI NVS region [mem 0xde869000-0xde8abfff] (274432 bytes)
    May 01 16:01:14 arch kernel: pinctrl core: initialized pinctrl subsystem
    May 01 16:01:14 arch kernel: RTC time: 14:01:11, date: 05/01/14
    May 01 16:01:14 arch kernel: NET: Registered protocol family 16
    May 01 16:01:14 arch kernel: cpuidle: using governor ladder
    May 01 16:01:14 arch kernel: cpuidle: using governor menu
    May 01 16:01:14 arch kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    May 01 16:01:14 arch kernel: ACPI: bus type PCI registered
    May 01 16:01:14 arch kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    May 01 16:01:14 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    May 01 16:01:14 arch kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    May 01 16:01:14 arch kernel: PCI: Using configuration type 1 for base access
    May 01 16:01:14 arch kernel: bio: create slab <bio-0> at 0
    May 01 16:01:14 arch kernel: ACPI: Added _OSI(Module Device)
    May 01 16:01:14 arch kernel: ACPI: Added _OSI(Processor Device)
    May 01 16:01:14 arch kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    May 01 16:01:14 arch kernel: ACPI: Added _OSI(Processor Aggregator Device)
    May 01 16:01:14 arch kernel: ACPI : EC: EC description table is found, configuring boot EC
    May 01 16:01:14 arch kernel: ACPI: Executed 1 blocks of module-level executable AML code
    May 01 16:01:14 arch kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de590018 000853 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Dynamic OEM Table Load:
    May 01 16:01:14 arch kernel: ACPI: SSDT (null) 000853 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de591a98 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Dynamic OEM Table Load:
    May 01 16:01:14 arch kernel: ACPI: SSDT (null) 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de592c18 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Dynamic OEM Table Load:
    May 01 16:01:14 arch kernel: ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Interpreter enabled
    May 01 16:01:14 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-580)
    May 01 16:01:14 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
    May 01 16:01:14 arch kernel: ACPI: (supports S0 S3 S4 S5)
    May 01 16:01:14 arch kernel: ACPI: Using IOAPIC for interrupt routing
    May 01 16:01:14 arch kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    May 01 16:01:14 arch kernel: ACPI: No dock devices found.
    May 01 16:01:14 arch kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
    May 01 16:01:14 arch kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    May 01 16:01:14 arch kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME]
    May 01 16:01:14 arch kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability]
    May 01 16:01:14 arch kernel: PCI host bridge to bus 0000:00
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0xdfc00000-0xfeafffff]
    May 01 16:01:14 arch kernel: pci 0000:00:00.0: [8086:0154] type 00 class 0x060000
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
    May 01 16:01:14 arch kernel: pci 0000:00:14.0: reg 0x10: [mem 0xf7300000-0xf730ffff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
    May 01 16:01:14 arch kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf731b000-0xf731b00f 64bit]
    May 01 16:01:14 arch kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
    May 01 16:01:14 arch kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7318000-0xf73183ff]
    May 01 16:01:14 arch kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
    May 01 16:01:14 arch kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7310000-0xf7313fff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: [8086:1e12] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: [8086:1e16] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: [8086:1e18] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
    May 01 16:01:14 arch kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7317000-0xf73173ff]
    May 01 16:01:14 arch kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1f.0: [8086:1e57] type 00 class 0x060100
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf070-0xf077]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf060-0xf063]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf050-0xf057]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf040-0xf043]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf020-0xf03f]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7316000-0xf73167ff]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: PME# supported from D3hot
    May 01 16:01:14 arch kernel: pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
    May 01 16:01:14 arch kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7315000-0xf73150ff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: [10de:0fd4] type 00 class 0x030000
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
    May 01 16:01:14 arch kernel: pci 0000:01:00.1: [10de:0e1b] type 00 class 0x040300
    May 01 16:01:14 arch kernel: pci 0000:01:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: [168c:0032] type 00 class 0x028000
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: reg 0x10: [mem 0xf7200000-0xf727ffff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: reg 0x30: [mem 0xf7280000-0xf728ffff pref]
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: supports D1 D2
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xf7200000-0xf72fffff]
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: [1969:1083] type 00 class 0x020000
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7100000-0xf713ffff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: reg 0x18: [io 0xd000-0xd07f]
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: PCI bridge to [bus 04]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [mem 0xf7100000-0xf71fffff]
    May 01 16:01:14 arch kernel: acpiphp: Slot [1] registered
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: PCI bridge to [bus 05]
    May 01 16:01:14 arch kernel: acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 *4 5 6 7 10 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *10 12)
    May 01 16:01:14 arch kernel: ACPI: Enabled 3 GPEs in block 00 to 3F
    May 01 16:01:14 arch kernel: ACPI : EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
    May 01 16:01:14 arch kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    May 01 16:01:14 arch kernel: vgaarb: loaded
    May 01 16:01:14 arch kernel: vgaarb: bridge control possible 0000:01:00.0
    May 01 16:01:14 arch kernel: PCI: Using ACPI for IRQ routing
    May 01 16:01:14 arch kernel: PCI: pci_cache_line_size set to 64 bytes
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdd6f6000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdd705000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddd20000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddd28000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddec5000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf13000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf3b000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf54000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf62000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf72000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf7e000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddfaf000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddfc0000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddffc000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddffe000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xde002000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xde01b000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xde869000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdecbf000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdf000000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0x21f400000-0x21fffffff]
    May 01 16:01:14 arch kernel: NetLabel: Initializing
    May 01 16:01:14 arch kernel: NetLabel: domain hash size = 128
    May 01 16:01:14 arch kernel: NetLabel: protocols = UNLABELED CIPSOv4
    May 01 16:01:14 arch kernel: NetLabel: unlabeled traffic allowed by default
    May 01 16:01:14 arch kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    May 01 16:01:14 arch kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    May 01 16:01:14 arch kernel: Switched to clocksource hpet
    May 01 16:01:14 arch kernel: pnp: PnP ACPI init
    May 01 16:01:14 arch kernel: ACPI: bus type PNP registered
    May 01 16:01:14 arch kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    May 01 16:01:14 arch kernel: pnp 00:01: [dma 4]
    May 01 16:01:14 arch kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
    May 01 16:01:14 arch kernel: pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
    May 01 16:01:14 arch kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
    May 01 16:01:14 arch kernel: system 00:04: [io 0x0680-0x069f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x1000-0x100f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0xffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0xffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x0400-0x0453] could not be reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x0458-0x047f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x0500-0x057f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x164e-0x164f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 01 16:01:14 arch kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
    May 01 16:01:14 arch kernel: system 00:06: [io 0x0454-0x0457] has been reserved
    May 01 16:01:14 arch kernel: system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    May 01 16:01:14 arch kernel: system 00:07: [io 0x04d0-0x04d1] has been reserved
    May 01 16:01:14 arch kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 01 16:01:14 arch kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0c04 (active)
    May 01 16:01:14 arch kernel: system 00:09: [io 0x0240-0x0259] has been reserved
    May 01 16:01:14 arch kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 01 16:01:14 arch kernel: pnp 00:0a: Plug and Play ACPI device, IDs ETD0101 SYN0a00 SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
    May 01 16:01:14 arch kernel: pnp 00:0b: Plug and Play ACPI device, IDs ATK3001 PNP030b (active)
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed1c000-0xfed1ffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed10000-0xfed17fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed18000-0xfed18fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed19000-0xfed19fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xf8000000-0xfbffffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed20000-0xfed3ffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed90000-0xfed93fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed45000-0xfed8ffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xff000000-0xffffffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfee00000-0xfeefffff] could not be reserved
    May 01 16:01:14 arch kernel: system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 01 16:01:14 arch kernel: pnp: PnP ACPI: found 13 devices
    May 01 16:01:14 arch kernel: ACPI: bus type PNP unregistered
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [io 0x1000-0x0fff] to [bus 05] add_size 1000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 05] add_size 200000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff] to [bus 05] add_size 200000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: BAR 14: assigned [mem 0xdfc00000-0xdfdfffff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: BAR 15: assigned [mem 0xdfe00000-0xdfffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: BAR 13: assigned [io 0x2000-0x2fff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xf7200000-0xf72fffff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: PCI bridge to [bus 04]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [mem 0xf7100000-0xf71fffff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: PCI bridge to [bus 05]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [io 0x2000-0x2fff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0xdfc00000-0xdfdfffff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0xdfe00000-0xdfffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 11 [mem 0xdfc00000-0xfeafffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    May 01 16:01:14 arch kernel: pci_bus 0000:01: resource 1 [mem 0xf6000000-0xf70fffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:01: resource 2 [mem 0xe0000000-0xf1ffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci_bus 0000:03: resource 1 [mem 0xf7200000-0xf72fffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:04: resource 0 [io 0xd000-0xdfff]
    May 01 16:01:14 arch kernel: pci_bus 0000:04: resource 1 [mem 0xf7100000-0xf71fffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:05: resource 0 [io 0x2000-0x2fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:05: resource 1 [mem 0xdfc00000-0xdfdfffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:05: resource 2 [mem 0xdfe00000-0xdfffffff 64bit pref]
    May 01 16:01:14 arch kernel: NET: Registered protocol family 2
    May 01 16:01:14 arch kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    May 01 16:01:14 arch kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    May 01 16:01:14 arch kernel: TCP: Hash tables configured (established 65536 bind 65536)
    May 01 16:01:14 arch kernel: TCP: reno registered
    May 01 16:01:14 arch kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: NET: Registered protocol family 1
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: Boot video device
    May 01 16:01:14 arch kernel: PCI: CLS 64 bytes, default 64
    May 01 16:01:14 arch kernel: Unpacking initramfs...
    May 01 16:01:14 arch kernel: Freeing initrd memory: 3128K (ffff8800379d4000 - ffff880037ce2000)
    May 01 16:01:14 arch kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    May 01 16:01:14 arch kernel: software IO TLB [mem 0xce76c000-0xd276c000] (64MB) mapped at [ffff8800ce76c000-ffff8800d276bfff]
    May 01 16:01:14 arch kernel: RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
    May 01 16:01:14 arch kernel: Scanning for low memory corruption every 60 seconds
    May 01 16:01:14 arch kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    May 01 16:01:14 arch kernel: zbud: loaded
    May 01 16:01:14 arch kernel: VFS: Disk quotas dquot_6.5.2
    May 01 16:01:14 arch kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    May 01 16:01:14 arch kernel: msgmni has been set to 15880
    May 01 16:01:14 arch kernel: Key type big_key registered
    May 01 16:01:14 arch kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    May 01 16:01:14 arch kernel: io scheduler noop registered
    May 01 16:01:14 arch kernel: io scheduler deadline registered
    May 01 16:01:14 arch kernel: io scheduler cfq registered (default)
    May 01 16:01:14 arch kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
    May 01 16:01:14 arch kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    May 01 16:01:14 arch kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    May 01 16:01:14 arch kernel: efifb: probing for efifb
    May 01 16:01:14 arch kernel: efifb: framebuffer at 0xf1000000, mapped to 0xffffc90004e80000, using 1920k, total 1920k
    May 01 16:01:14 arch kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
    May 01 16:01:14 arch kernel: efifb: scrolling: redraw
    May 01 16:01:14 arch kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    May 01 16:01:14 arch kernel: Console: switching to colour frame buffer device 100x37
    May 01 16:01:14 arch kernel: fb0: EFI VGA frame buffer device
    May 01 16:01:14 arch kernel: intel_idle: MWAIT substates: 0x21120
    May 01 16:01:14 arch kernel: intel_idle: v0.4 model 0x3A
    May 01 16:01:14 arch kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
    May 01 16:01:14 arch kernel: GHES: HEST is not enabled!
    May 01 16:01:14 arch kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    May 01 16:01:14 arch kernel: Linux agpgart interface v0.103
    May 01 16:01:14 arch kernel: rtc_cmos 00:05: RTC can wake from S4
    May 01 16:01:14 arch kernel: rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
    May 01 16:01:14 arch kernel: rtc_cmos 00:05: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
    May 01 16:01:14 arch kernel: Intel P-state driver initializing.
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 0
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 1
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 2
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 3
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 4
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 5
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 6
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 7
    May 01 16:01:14 arch kernel: ledtrig-cpu: registered to indicate activity on CPUs
    May 01 16:01:14 arch kernel: TCP: cubic registered
    May 01 16:01:14 arch kernel: NET: Registered protocol family 10
    May 01 16:01:14 arch kernel: NET: Registered protocol family 17
    May 01 16:01:14 arch kernel: registered taskstats version 1
    May 01 16:01:14 arch kernel: Magic number: 14:512:29
    May 01 16:01:14 arch kernel: rtc_cmos 00:05: setting system clock to 2014-05-01 14:01:11 UTC (1398952871)
    May 01 16:01:14 arch kernel: PM: Hibernation image not present or could not be loaded.
    May 01 16:01:14 arch kernel: Freeing unused kernel memory: 1120K (ffffffff818d8000 - ffffffff819f0000)
    May 01 16:01:14 arch kernel: Write protecting the kernel read-only data: 8192k
    May 01 16:01:14 arch kernel: Freeing unused kernel memory: 904K (ffff88000151e000 - ffff880001600000)
    May 01 16:01:14 arch kernel: Freeing unused kernel memory: 416K (ffff880001798000 - ffff880001800000)
    May 01 16:01:14 arch kernel: random: systemd-tmpfile urandom read with 1 bits of entropy available
    May 01 16:01:14 arch systemd-udevd[77]: starting version 212
    May 01 16:01:14 arch kernel: i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    May 01 16:01:14 arch kernel: ACPI: bus type USB registered
    May 01 16:01:14 arch kernel: usbcore: registered new interface driver usbfs
    May 01 16:01:14 arch kernel: usbcore: registered new interface driver hub
    May 01 16:01:14 arch kernel: usbcore: registered new device driver usb
    May 01 16:01:14 arch kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controlle

    There are actually a couple of other topics about this issue. If you are looking for an answer as to what the problem is, then nobody seem to be able to provide an answer. Nvidia claim it is a bug in the kernel acpi calls, but have not been forthcoming to explain that further. There is a lengthy topic on nvidia forums.
    However, for a way to get things working again, read this topic: https://bbs.archlinux.org/viewtopic.php?id=180085

  • Abrupt Failing Battery and Kernel Panic?

    About 3 days ago I experienced the first problem. My battery hit 0% and instead of my powerbook sleeping it just died.
    On Reboot I got a "Mac OS X Unexpectedly Quit" dialog.. (unresolved kernel trap?), so I decided to reboot and reset the APU and PRAM. I received the kernel panic screen shortly after my desktop loaded which was alarming, so I restarted and received the kernel panic screen yet again. Thinking maybe it was due to heat I let the thing cool down for a while and restarted and it was fine.
    However, I'm now going on my 5th abrupt powerdown when I hit 0%. I even tested it with nothing running and it just dies, and doesn't sleep.
    The 12" powerbook is 18 months old and has 632 recharge cycles on it (I do web development and tend to move around while I work, guess I should have sat still and plugged in eh?).
    I figure the abrupt shutdown is telling me I need a new battery, and checking it has 1939 of 4400mAh of its original capacity.
    Interestingly enough I get about 1.5 hours of battery life still depending on usage, though it seems it likes to shudown and not sleep when it gets low.
    My question is why the kernel panics and why is it failing so quickly all of a sudden?

    Same thing going here with a two year old 1GHz 12". I was looking at the battery level display and it was 43% when it just died. I was ripping a cd and updating my iPod when it happened. The first time it happened there was a complete PRAM reset. The last couple times no messages or anything, and not sleeping, just shutting off without warning. I'm showing well over 400 cycles and about 1160 mAh full charge capacity. It's happened three times in the last month, and it started after I let my son play Lego Star Wars on the machine. I taught him to put the pb up on some popsicle sticks to help cooling, as it was very hot.

  • Application got locked when power failure(abnormal shutdown)

    hi all,,,
    I am developing swings application where user needs to login by giving valid Uname and password(only one user at a time,multiple users not allowed) and im storing this data(Uname and pwd) and status(looged in/not) in xml,my app is working fine when we closed the application normally,for this i had written an event when clicked on close button(by using boolean).
    My problem is when there is power failure/system crashes,the application is getting locked when user tries to login.
    can any help me in this..wat can i do to solve this?

    I found that problem
    i hope your application will be running in a network drive and only one user can login at a time.
    so u need to track the abrupt shutdown.

  • Exception caused by 'shutdown immediate'

    Hi,
    I am using a PL/SQL to delete or update tables.
    When Oracle is issued with 'Shutdown immediate' or 'Shutdown abort' or if Oracle is abruptly shutdown, I have to rollback the transactions. Although, I have not written a rollback command, Oracle automatically rolls back. This is the desired behaviour. This happens as desired in my machine. In Production environment, I believe the shutdown has thrown an exception. The logic I had entered in the exception block where we update an error table is visible in the Production environment. I could not recreate this exception in my system. I am not sure what exception Oracle throws on abrupt shutdown. So, I plan to write an exception block as a precaution. Do you please know what exceptions are possible ones if there is a abrupt shutdown.
    Regards,
    Raj

    > Do you please know what exceptions are possible ones if there is a abrupt shutdown.
    There is no exception thrown.
    SHUTDOWN ABORT is like disconnecting the power cord & no subsequent action occurs.

  • DPS 6.3.1.1 - Issues while connecting through SSL

    Hello !!
    I have a issue where my application client reported that they are unable to connect to the LDAP using SSL. Where as everything works fine in LDAP (non secured)
    This is how our deployment looks.
    Clients <=> Load Balancer <=> DPS (2 instance) <=> DS (2 masters)
    The DPS is configured with DSP (data source pool) (with proportional algorithm of 50:50 to backend data sources). Client Affinity ("read-write-affinity-after-any") is configured for this DSP. The DSP is attached with 2 data sources.
    So when the client connected in a secured port using LDAPS, they are unable to authenticate/search against this environment. No issues were found in DS logs for any of the bind/search requests. But in DPS, we noticed below log which i want to get clarification on.
    Note: I have removed the hostnames/Ip where ever applicable from the logs.
    =====================================================
    [04/May/2011:12:24:39 -0400] - PROFILE - INFO - conn=1255260 assigned to connection handler cn=default connection handler, cn=connection handlers,cn=config
    [04/May/2011:12:24:39 -0400] - CONNECT - INFO - conn=1255260 client=x.x.x.x:52461 server=x.x.x.x:636 protocol=LDAPS
    [04/May/2011:12:24:39 -0400] - OPERATION - INFO - conn=1255260 op=0 BIND dn="uid=app_id,ou=applications,dc=example,dc=com" method="SIMPLE" version=3
    [04/May/2011:12:24:39 -0400] - SERVER_OP - INFO - conn=1255260 op=0 BIND dn="uid=app_id,ou=Applications,dc=example,dc=com" method="SIMPLE" version=3 s_msgid=3 s_conn=ds_Master2:26560
    [04/May/2011:12:24:39 -0400] - SERVER_OP - INFO - conn=1255260 op=0 BIND RESPONSE err=0 msg="" s_conn=ds_Master2:26560
    [04/May/2011:12:24:39 -0400] - PROFILE - INFO - conn=1255260 assigned to connection handler cn=CH_ENV_catch-all_LDAPS,cn=connection handlers,cn=config
    [04/May/2011:12:24:39 -0400] - OPERATION - INFO - conn=1255260 op=0 BIND RESPONSE err=0 msg="" etime=0
    [04/May/2011:12:24:39 -0400] - OPERATION - INFO - conn=1255260 op=1 msgid=2 SEARCH base="ou=people,dc=example,dc=com" scope=2 filter="(uid=abcdef)" attrs="*"
    [04/May/2011:12:24:39 -0400] - SERVER_OP - INFO - conn=1255260 op=1 SEARCH base="ou=people,dc=example,dc=com" scope=2 filter="(uid=abcdef)" attrs="*" s_msgid=498 s_conn=ds_Master1:26072
    [04/May/2011:12:24:39 -0400] - SERVER_OP - INFO - conn=1255260 op=1 SEARCH RESPONSE err=0 msg="" nentries=0 s_conn=ds_Master1:26072
    [04/May/2011:12:24:39 -0400] - OPERATION - INFO - conn=1255260 op=1 SEARCH RESPONSE err=0 msg="" nentries=0 etime=0
    *[04/May/2011:12:24:39 -0400] - DISCONNECT - INFO - conn=1255260 reason="other" msg="Exception caught while polling client connection LDAPS.x.x.x.x.52461 -- javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?"*
    =======================================================
    If noticed in the above logs, the initial Bind request via LDAPS is routed to Master 2. But the susequent search request (for user abcdef) is routed to Master 1.
    And finally the DISCONNECT operation came (last line) without a proper unbind.
    Is this alternate routing a expected behavior when client affinity is turned ON ? Is this exception causing the application's search failures ?
    Please shed some pointers on this..
    Thanks.
    Edited by: Prasee on May 6, 2011 8:07 AM

    Pls see inside:
    Thanks for the reply. Yes the client is a loadbalancer in this case. So does it mean that this behavior (sending request to 2 different DS in a same connection) is expected ? I have few additional queries that arise from your reply :-)
    Loadbalancing algorithm takes precedence "if the request that starts client affinity has not yet occurred"
    Since its the load balancer that connects to DPS for any/every request every time., How do the DPS know whether a request that starts client affinity has occurred / not occurred ?Well, client affinity starts with a certain operation (not by establishing the client<->dps connection) as specified by your client affinity policy. In your case ("client-affinity-policy:read-write-affinity-after-any") it starts for all operations after the first read or write operation. DPS is not a (network) connection based router - so it does not route the client connection to the data source but forwards the client operations (request) on dedicated bind,read,write,.. connections to a data source selected by your load balancing and/or client affinity policy.
    In our case, Its the same connection (conn=1255260) that receives bind and search request from the client. So when a connection is established, the client affinity should have got enabled and sent the bind request to Master 2 initially, so for the next search request, shouldn't it be sent to Master 2 again ?No, see above.
    >
    Sorry for these questions, I am basically trying to understand more on how client affinity works when a load balancer is in between.
    Coming to the exception,
    [04/May/2011:12:24:39 -0400] - DISCONNECT - INFO - conn=1255260 reason="other" msg="Exception caught while polling client connection LDAPS.x.x.x.x.52461 -- javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?"
    Does this abrupt shutdown of connection means the search response would have got dropped before reaching the end client (application) ?Yes, that may be possible ...
    >
    Thanks for your help !!

  • Users can't add items to their agendas - Module errors

    There was a server crash recently and now some users are getting errors when
    they try to connect or make any updates to their Calendar. Some of the errors
    that are getting displayed to a pop up box are:
    <P>
    "Module agenda fr.cpp label 4334"<br>
    "Module agenda vw.cpp label 124,service error #0x13201"
    <P>
    Whenever the server is abruptly shutdown, there is the likely probability that
    there has been some database corruption, especially when errors start appearing
    on the client.<br>
    There is a tool, called /users/unison/bin/unidbfix that will need to be executed
    when the server is down that will clean up the database. Please refer to the
    Calendar Server Administrators Guide for details on this command, as it should
    be used VERY CAREFULLY.
    <P>
    If problems still persist afterwards, check which version of the tool that you
    are using:<br>
         # unidbfix -v<br>
         A.01.20<br>
    and contact Technical Support with this information and the dbfix.log that the
    tool creates.

    Welcome to Apple Discussions.
    The Dock did not return to default on that command?
    Try again and also delete username/Library/Preferences/com.apple.finder.plist
    If it's still no-go create a new User go to System Preferences >> Accounts >> "+" (make it an admin acct) and test the Dock in this new account, if it works the problem is isolated to your User and not systemwide.
    Let us know.
    EDIT: Also are you running any enhancement software?
    -mj
    Message was edited by: macjack

Maybe you are looking for

  • Problem WIth Variant in a report program

    I have a z report program with couple of variants , the problem is the varaints display onlt name of the variant and description when the varaint button is pressed. The changed by , date etc details are not getting displayed. Thanks Arun

  • Need help on macbook pro 15

    Sorry i realise i post my previous post in the wrong forum section, hence im bringing it here. Mod please delete my previous thread. Hi this is my first time using mbp or even the whole mac system, im running on bootcamp and recently i've been buying

  • Display of GL account in MIGO

    Dear All, When i issue goods to a cost centre  in MIRO, can i set the GL account number to pick automatically and the field myst be in DISplay mode, i mean the user does not make any entry in the GL number field, once the cost centre number is entere

  • Issue Tracker app - how to make one page public

    Hi all, We have installed and made a few tweaks to the Issue Tracker demo app, and are finding it very useful! We have just a handful of users that have logins for the application, and it is working well for them. We would like to make a modification

  • Query Syntax

    Hi Guys, Is there any where for me to lookup information of syntax that used in queries? I know stored procedure and able to write simply query with no problem But i encounter a syntax from other partner like: $[ORDR.DocNum] $[38.1.0] /* SELECT FROM