Cpu1 above threshold?

From what I've searched on the forums it might be my graphics card? I'm running a dell e1405 with an intel 945GM graphics card using the xf86-video-intel driver. I was unaware of this error that is apparent now.. "CPU1: Temperature above thresold, cpu clock throttled (total events = 220499)" because I only see it when I switch out of X into teminal... My fan is running constantly and only using for the most part under 10% on both CPUs but you can feel the heat off it as if I was playing a game.
What should I do?
EDIT:
I just did ran dell's diagnostic software and nothing was wrong with the CPU.. Also looked at the BIOS to see if it showed my CPU temp. anywhere but didn't so I assumed that it just didn't keep track of the temperature... but that can't be right because my fan sped up immediatly when the system restarted and during the diagnostics it eventually slowed down.. now it doesn't display the error?
Last edited by Kazuma (2010-01-24 20:46:37)

Hey, okay i had this issue too but it was nothing to do with the cpu i don't think. I had it for ages but nothing happened until my machine went crazy and started locking up and a bunch of other issues. I took my computer apart cleaned the fan intake for the cpu and noticed that my graphics card was baking.
I never turned on the power scaling options for my nvidia graphics card after using the official drivers it was baking everything in my case for ages. Turned them on and I haven't had any messages since and everything works waaaaay better because i turned on some other optimisation stuff for the card as well. If you have a big graphics card, check the options make sure power scaling for heat is on should be fine.

Similar Messages

  • WiSM Issue - More than three APs working at the power above threshold

    According to the RRM document: http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a008072c759.shtml , for each AP, the 3rd loudest AP should be heard at the power equal or lower than the threshold (default -65dbm or -70dbm according to different codes). But in our enviroment, I can see it is not true. Many APs have more than three neighbours heard at above threshold. Is it true in your enviroment as well?
    Thanks!
    Zhenning

    It's the way I have deployed the network. When the number of access point increases (though in diff channel) chances of interference increases leading to decreased performance. So Adjust the power settings and the number of access points accordingly.

  • Swap space used is above threshold of 90

    Hi all,
    i am facing an issues in linux box which is Swap space used is above threshold of 90
    [oracle@gbaheovl21 scripts]$ free
                 total       used       free     shared    buffers     cached
    Mem:       8388608    8354400      34208          0      32748    4354904
    -/+ buffers/cache:    3966748    4421860
    Swap:      6257992    5816940     441052
    scripts]$ sar -r
    07:00:01    kbmemfree kbmemused  %memused kbbuffers  kbcached kbswpfree kbswpused  %swpused  kbswpcad
    07:10:01        15868   8372740     99.81     16348   4356644    479720   5778272     92.33    767516
    07:20:01        93232   8295376     98.89     17624   4304864    433200   5824792     93.08    773240
    07:30:01        29092   8359516     99.65     22664   4328688    442496   5815496     92.93    800512
    07:40:01        39700   8348908     99.53     28584   4348424    441392   5816600     92.95    768592
    Average:        57576   8331032     99.31     56029   4292652    349858   5908134     94.41    775742
    Is their any fix to this issue with out reboot ? please any one help me on this ?

    Hi ,
    sorry for that , i am pasting the info below.
    Linux venkat.gb.com 2.6.18-238.el5xen #1 SMP Sun Dec 19 14:42:02 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
    it is a Oracle virtual linux and here few databases are running
    [root@ ~]# sysctl vm.swappiness
    vm.swappiness = 60
    [root@~]# df /dev/shm
    Filesystem           1K-blocks      Used Available Use% Mounted on
    tmpfs                  4194304    249220   3945084   6% /dev/shm
    [root@ ~]# ipcs -um
    ------ Shared Memory Status --------
    segments allocated 31
    pages allocated 2099310
    pages resident  1003699
    pages swapped   881584
    Swap performance: 0 attempts     0 successes
    [root@ ~]# cat /proc/meminfo
    MemTotal:      8388608 kB
    MemFree:         29556 kB
    Buffers:         39224 kB
    Cached:        4458580 kB
    SwapCached:     625964 kB
    Active:        6728908 kB
    Inactive:       548592 kB
    HighTotal:           0 kB
    HighFree:            0 kB
    LowTotal:      8388608 kB
    LowFree:         29556 kB
    SwapTotal:     6257992 kB
    SwapFree:       512504 kB
    Dirty:            3360 kB
    Writeback:           0 kB
    AnonPages:     2442472 kB
    Mapped:        3943420 kB
    Slab:           256204 kB
    PageTables:     525464 kB
    NFS_Unstable:        0 kB
    Bounce:              0 kB
    CommitLimit:  10452296 kB
    Committed_AS: 21157240 kB
    VmallocTotal: 34359738367 kB
    VmallocUsed:     34920 kB
    VmallocChunk: 34359703427 kB
    thanks
    Venkat

  • "CPU#0 Tempature above threshold"

    I am running Arch Linux with the ArchLinux supplied 2.6.2 kernel.  When I try to compile a new kernel, I get the message repeatedly on every terminal, and CPU usage shoots up to 100% (according to IceWM).
    Here is what the kernel tells me:
    CPU#0:  Tempature above threshold
    CPU#0:  Running in modulated clock mode
    I see those messages repediately (like 3 times a second), and every once and a while I get compiler messages on what is being compiled.  It seems to be compiling fine, but those messages are on every terminal, making it unable to do anything!  What's the problem!  I need help!

    I cleaned out the computer (it was pretty hot), and it still displayed the message, but it wasn't as bad.  Maybe they should cut down on those messages, and say when they start and stop, but not every blinking second!

  • HubTransport UnHealty - Total.Shadow.Queue.Length.Above.Threshold.Monitor - What to check?

    Hi To all,
    looking at Exchange 2013 ServerHealth  i have the "HubTransport" in unhealth state related to this
    item:
    Total.Shadow.Queue.Length.Above.Threshold.Monitor
    I cannot find more information about this issue...
    Many thanks for help! :)
    r.

    Hi,
    Found nothing in the public resource, neither.
    Is there any error/warning/information in the event viewer?
    Please also check the detailed error message in the Monitor if it is possible.
    Did this cause other issues, some like mailflow issue etc.?
    If everything going well, I suggest disable the Alert.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • CPUx: Temperature above threshold, cpu clock throttled

    My cousin (Windows) computer suicided... it stopped
    booting without any apparent reason.
    He asked my help and we stored every important data in an
    external drive using an arch linux installed in a usb key
    (thanks to every wiki writer).
    I thought it could be an hardware problem so I started
    stress with with a command line like:
    stress --cpu 2 --io 1 --vm 1 --hdd 1
    (pwd was in a Windows mounted partition)
    it is already one hour the program goes. I got the error
    of the title few times:
    CPUx: Temperature above threshold, cpu clock throttled
    for both CPUs. I thought it was normal, after all
    the cpu might overheat under stress and it slows down
    to protect itself...
    But suddenly I got a doubt, it is really the CPU that
    slows down itself (so it is an hardware feature) or it is
    linux that slows it down (so it is a kernel feature)? In
    this second case do anyone knows if Windows do anything
    similar?
    Secondly in the error log I can see:
    EDID checksum is invalid, remainder is 210
    Raw EDID:
    <hex dump omitted>
    I sought in the Internet, but I could not understand what
    it means nor if it is dangerous... can anyone help me?
    Thanks

    The BIOS is usually responsible for setting thresholds and has settings to halt the computer when those thresholds are too high.
    Since the program is testing stress, I'm guessing the software is throttling the CPU so the system does not shutoff and the test can still process.
    I would highly suggest checking your BIOS's tempertature thresholds, as well as the fan speed settings (BIOS or software).
    I would also find out what a normal temperature for the CPU is and do some testing on what different loads do to the temperature.

  • Optical Receive Power Warning - Operating above threshold

    As we know, 
    we cannot configure the optical transmit power of the SFP. Though we can check the receive power level received by peer through the command:
    show interface transceiver detail
    However, logs have been displaying:
    Aug 20 06:45:14.434: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/25: Rx power high warning; Operating value:  -1.7 dBm, Threshold value:  -3.0 dBm.
    Checking it:
               Optical            High Alarm  High Warn  Low Warn   Low Alarm
               Receive Power      Threshold   Threshold  Threshold  Threshold
    Port       (dBm)              (dBm)       (dBm)      (dBm)      (dBm)
    Gi1/0/25    -1.7         +       1.0        -3.0       -19.0      -23.0
    WIll this have a big impact on my switch? Especially the SFP module
    Factors like damage, etc.
    Also, how will it affect network performance, both the health and operation of my devices
    Your ideas are greatly appreciated (and if you can back it up with docs, it'd would be helpful too! ^_^)

    It seems your distant end is sending a relatively high output power and/or you have a very short fiber connection with very little loss. Since you are only in the 'warn' range you are not likely to cause any damage to the receiving SFP or affect network operation adversely.  You do have the option of adding an optical attenuator to the link to make the operating range more within specification.

  • Trigger above threshold value

    Hi
    I'm trying to trigger a data save with multiple input channels when one
    of my input signals exceeds a given level for the first time.  The
    data save should only end when a stop button is activated - i.e. not
    re-start each time the threshold level is exceeded. I have been trying
    to do this by connecting a Curve Control Block to the start input of my
    Save block, which is set to retriggerabe, but my measurement then
    restarts each time the given level is exceeded.
    Do I need to use a different method, or just change some parameters?
    Thanks,
    Helen

    Hello Helen,
    I made some small modifications to your scheme.
    Firstly, you have to connect the "Condition1" block to the systemtact
    as well. Otherwise it wont be stopped by the stoptrigger and the whole
    scheme can not be terminated with the button.
    Secondly, the lamp indicator is a bit trcky to use. This is because it
    is not, as you might expect, simply a boolean indicator. Actually it
    can display more than 2 states - each state in a different color.
    You have to edit the value range for the incoming data and chose which
    values are represented in which colors. (Dialog Signaldarstellung ->
    Darstellung -> Zustände) in the german version.
    Set the indicator to display until 0 in black and until 1 in red and it will work correctly in this case.
    Regards
    Message Edited by IngoS on 11-18-2005 03:03 PM
    Ingo Schumacher
    Systems Engineer Sound&VibrationNational Instruments Germany
    Attachments:
    sample_mod.DAC ‏50 KB

  • ISE Config Backup Failure - Data filesystem full above threshold

    Hi,
    Both the config and operational backups were working until earlier last month. Now the config backup is failing with the following error. No configuration or repository settings were changed.
    ISE 1.2.0.899 Patch 8 - Clustered with persona Node 1 = PAN, SMN, PSN .... Node 2 = SAN, PMN, PSN
    CLI history says the same:
    The local repository (disk:/) is looking good. The "/" filesystem is taking 77% space.
    Although it may not be relevant. Data Purging is set to 30 days in the GUI and Operations -> Reports -> Data Purging Audit indicates its running daily with success i.e. threshold_space = 80GB, used_space = 3GB.
    Is there a way to clean "/" filesystem ? It is filling up by roughly 1% every 5 days ? Note: the same on Node 2 is only 24% full.
    Any ideas on how to get the config backup issue resolved ?
    P.S. If images don't appear inline, please see the attachment
    Thanks,
    Rick.

    922963 wrote:
    Hi JK,
    Thanks for response. Yes, I am worried that it may not be enough. How about if I increase memory to 32GB, ie. I have two servers, both with 32GB? Will it be sufficient in case of one physical server fail for 8GB data?
    What is the point in having the 3rd physical box if two boxes have enough memory/capacity? You know, we need to pay licence according to no of CPU.
    thanks,
    HenryHi Henry,
    actually the recommended minimum number of physical boxes is 4 so that the witness protocol participants can all be on separate machines.
    But a minimum of 3 is highly recommended for a number of reasons related to partitioning:
    1. If you have only 2, then you are much more vulnerable to split brain scenarios (should for some reason the two servers not be able to communicate with each other, it is harder to decide which half should be the winner). In short how do you decide which box is unable to communicate with the rest of the cluster if there are only 2 boxes?
    2. You can't ensure a balanced and also machine safe partition distribution if you have a mismatching number of nodes on only 2 boxes. It would either be balanced or machine safe, but you can't get both at the same time. And you will either have mismatching number of nodes at startup or have mismatching number of nodes after one node failure.
    Best regards,
    Robert

  • Change CPU temperature threshold

    Is it possible to change or set the temperature threshold for the cpu clock throttle?
        Feb 22 13:04:28 -toshiba kernel: CPU1: Core temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
        Feb 22 13:04:28 -toshiba kernel: CPU1: Core temperature/speed normal
        Feb 22 13:04:28 -toshiba kernel: CPU7: Package temperature/speed normal
        Feb 22 13:04:28 -toshiba kernel: CPU0: Core temperature/speed normal
        Feb 22 13:04:28 -toshiba kernel: CPU4: Package temperature/speed normal
        Feb 22 13:04:28 -toshiba kernel: CPU3: Package temperature/speed normal
        Feb 22 13:04:28 -toshiba kernel: CPU5: Package temperature/speed normal
        Feb 22 13:04:28 -toshiba kernel: CPU6: Package temperature/speed normal
        Feb 22 13:04:28 -toshiba kernel: CPU2: Package temperature/speed normal
        Feb 22 13:04:28 -toshiba kernel: CPU0: Package temperature/speed normal
        Feb 22 13:04:28 -toshiba kernel: CPU1: Package temperature/speed normal

    Works fine booted under Windows.  The tablet is known to run "hot", but well under TJ max.  RealTemp in Windows shows it hoving around 49C idle and up to 80C, with well within limits and matches all other Lenovo Helix's posting their temp results online.  Hot, yes, but acceptable.
    When I get time I'll go back in and view the sensors.  I suspect one or two things:
    * Sensors are outta wack, giving false numbers.
    * The kernel driver is too conservative and it thinks an 70C temp is bad or something.  <- harder to prove.
    The BIOS handles everything fine.  When I disable PState in Windows (force everything to 100), temps range from 62C to 81C at all times.  Still within specifications.  This is BIOS-controlled cooling controlling the fans.
    ^- this is what I want for Arch.  Controlling PState is great, but if there's a problem I want it to get out of the way and just let the BIOS handle things.  Don't force it.
    I'm quite surprised Arch attempts to handle this on its own automagically without some special configuration or wiki page to set it up.
    Last edited by eduncan911 (Today 05:56:17)

  • List View Threshold and using OR in list view

    I've read the white papers, searched the blogs, but I don't quite understand why I am getting the 'only showing latest results...' yellow bar due to list threhshold with following scenario:
    List has 9000 items (so above threshold).
    ALL 4 columns below are indexed!
    I have a view called 'My Items' such that:
    Show all items when
    UserColumn1 = [Me] OR
    UserColumn2 = [Me] OR
    UserColumn3 = [Me] OR
    UserColumn4 = [Me]
    All of the 4 user columns are indexed, but I'm thinking that since I have OR's in they query vs ANDs that it is causing the view to trip up and display the 'only giving you recent...' yellow filter bar.
    Any thoughts?
    Am i correct in my thinking that because of the OR's, SharePoint has to go back to the database and pull data 4 times.
    There are only 20 items where UserColumn1 is me, 10 where UserColumn2 is me, and 3 where UserColumn3 is me and only 1 item where UserColumn4 is me, so there are only total of 34 items, so I know its not because the first indexed column is returning more
    than 5000 items.
    Any advice/links to using 'OR' in view is much appreciated, I couldn't find anything.
    Herschel

    The problem is the "or" and the list view threshold.  When using an OR the query has to retrieve ALL the items to make sure it gets all the Or clauses.  Once it has all the items then it filters based on the "or".  If you
    use an"and" you can be sure that all the results will be represented by the result set that is derived from the first column.  So the query can be limited to that and then trimmed of additional results after retrieval.  When using Ors there
    is no way to limit the query Set.  What you want it to do is limit the results to 4 query sets that it then combines.  It doesn't work that way.  When using 'or' you will always try to retrieve ALL the results whether the columns are indexed
    or not.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Performance Counter monitors stay unhealthy even when values drop below thresholds

    I'm investigating some (SCOM 2012) alerts on our Exchange 2013 (SP1) environment:
    Malware filtering is taking too long (90th percentile)
    Mailbox Transport Submission is not keeping up with the work...
    Queue Alert: Internal Aggregate Delivery Queue (Normal Priority) exceeds threshold
    The total number of messages in shadow queues exceeds 1500
    All the monitors are Performance Counter based monitors. When I investigate those performance counters (found via the Crimson Channels in the Eventlogs ../ActiveMonitoring/Monitordefinition) all affected counters have already dropped below threshold values
    but the associated Health Sets stay unhealthy
    IE: Get-ServerHealth -Identity '<Server>' -HealthSet '<HealthSet>'  still reports Total.Shadow.Queue.Length.Above.Threshold.Monitor as UnHealthy while perfmon reports values way below 1500 for that particular server.
    How to (re)evaluate the monitors ?

    For investigation purposes I've added some perfmoncounters in SCOM
    Another server now alerts 'Total number of messages in shadow queues exceeds 1500'. On the specific server the treshold never reached 1500; it was about 5 at the time the alert fired ?!?
    Now it seems the alerts fire for no reason and cannot be reset (I want Managed Availability to reset the alert, not scom)
    The XML of Eventlog\Applications and Serviices/Microsoft/Exchange/ActiveMonitoring/MonitorDefinition/
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Microsoft-Exchange-ActiveMonitoring" Guid="{ECD64F52-A3BC-47B8-B681-A11B7A1C8770}" />
    <EventID>7</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>7</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-08T12:08:40.460212000Z" />
    <EventRecordID>15316181</EventRecordID>
    <Correlation />
    <Execution ProcessID="38980" ThreadID="30424" />
    <Channel>Microsoft-Exchange-ActiveMonitoring/MonitorDefinition</Channel>
    <Computer>XXXX</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    - <UserData>
    - <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
    <Id>577</Id>
    <AssemblyPath>C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Office.Datacenter.ActiveMonitoringLocal.dll</AssemblyPath>
    <TypeName>Microsoft.Office.Datacenter.ActiveMonitoring.OverallConsecutiveSampleValueAboveThresholdMonitor</TypeName>
    <Name>Total.Shadow.Queue.Length.Above.Threshold.Monitor</Name>
    <WorkItemVersion>[null]</WorkItemVersion>
    <ServiceName>HubTransport</ServiceName>
    <DeploymentId>0</DeploymentId>
    <ExecutionLocation>[null]</ExecutionLocation>
    <CreatedTime>2014-07-08T12:08:40.4602120Z</CreatedTime>
    <Enabled>1</Enabled>
    <TargetPartition>[null]</TargetPartition>
    <TargetGroup>[null]</TargetGroup>
    <TargetResource />
    <TargetExtension>[null]</TargetExtension>
    <TargetVersion>[null]</TargetVersion>
    <RecurrenceIntervalSeconds>0</RecurrenceIntervalSeconds>
    <TimeoutSeconds>30</TimeoutSeconds>
    <StartTime>2014-07-08T12:08:40.4602120Z</StartTime>
    <UpdateTime>2014-07-08T12:04:53.7722193Z</UpdateTime>
    <MaxRetryAttempts>0</MaxRetryAttempts>
    <ExtensionAttributes>[null]</ExtensionAttributes>
    <SampleMask>EDS/Performance Counter/MSExchangeTransport Shadow Redundancy Host Info\Shadow Queue Length\_total</SampleMask>
    <MonitoringIntervalSeconds>600</MonitoringIntervalSeconds>
    <MinimumErrorCount>0</MinimumErrorCount>
    <MonitoringThreshold>1500</MonitoringThreshold>
    <SecondaryMonitoringThreshold>1</SecondaryMonitoringThreshold>
    <ServicePriority>2</ServicePriority>
    <ServiceSeverity>0</ServiceSeverity>
    <IsHaImpacting>0</IsHaImpacting>
    <CreatedById>50</CreatedById>
    <InsufficientSamplesIntervalSeconds>28800</InsufficientSamplesIntervalSeconds>
    <StateAttribute1Mask>[null]</StateAttribute1Mask>
    <FailureCategoryMask>0</FailureCategoryMask>
    <ComponentName>ServiceComponents/HubTransport/High</ComponentName>
    <StateTransitionsXml>[null]</StateTransitionsXml>
    <AllowCorrelationToMonitor>0</AllowCorrelationToMonitor>
    <ScenarioDescription>[null]</ScenarioDescription>
    <SourceScope>[null]</SourceScope>
    <TargetScopes>[null]</TargetScopes>
    <Version>65536</Version>
    </EventXML>
    </UserData>
    </Event>

  • Averaging 100 consecutive measurements below a threshold value

    Hi,
    I have just started labview programming. I'm having difficulties with programming just this very simple code. I've been breaking my head all night. I will appreciate a speedy response.
    How can I make a code that would enable averaging 100 consecutive measurements that are below a certain threshold value in labview?
    Thanks.
    Solved!
    Go to Solution.

    Try the attached.  The key is the shift registers -- the integer (blue) is a counter of below-threshold measurement and it resets to 0 if there is an above-threshold meas.  The result is saved whenever the counter gets above 100 (indicating >=100 consecutive "good" values). This also stops the internal while loop and the external loop causes the shift registers to reinitialize.  I added a "set file position" function so the values will append rather than overwrite the file.  You'll probably need to insert a carriage return into the string that gets written to file so the values will appear on separate lines.  I also changed your data types to DBL -- they were I32 (integer) which does not seem to jive with your indication you were taking analog measurements.
    Attachments:
    Average.vi ‏13 KB

  • [SOLVED] system very slow after upgrade

    I did today pacman -Syu after some time. I have Dell D630 laptop, Core 2 Duo 2x1.8GHz, 2GB RAM, VGA: Intel X3100. Now the whole system is really slow. I mean REALLY slow. Even opening terminal (urxvt) takes time. Browsing is slow. Mplayer can not handle 720p .mkv playback enymore. cpufreq-info shows both cores uses max. 1.8 GHz  frequency under load. I tried top/htop/atop/iotop/powertop but found no suspicious process eating resources. Messages from error.log:
    Mar 29 23:16:05 tortuga kernel: ata4.01: failed to resume link (SControl 0)
    Mar 29 23:16:05 tortuga kernel: vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance
    Mar 29 23:16:05 tortuga kernel: vboxdrv: counter framework which can generate NMIs is active. You have to prevent
    Mar 29 23:16:05 tortuga kernel: vboxdrv: the usage of hardware performance counters by
    Mar 29 23:16:05 tortuga kernel: vboxdrv: echo 2 > /proc/sys/kernel/perf_counter_paranoid
    I googled botth messages and as far as I can understand they are not source/symptom of my slowness.
    If anybody have hint where to search, any advice will be really helpfull, because I am truly lost...
    dmesg
    # dmesg
    Linux version 2.6.32-ARCH (thomas@evey) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Mon Mar 15 20:08:25 UTC 2010
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    NSC Geode by NSC
    Cyrix CyrixInstead
    Centaur CentaurHauls
    Transmeta GenuineTMx86
    Transmeta TransmetaCPU
    UMC UMC UMC UMC
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
    BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
    BIOS-e820: 0000000000100000 - 000000007f680400 (usable)
    BIOS-e820: 000000007f680400 - 0000000080000000 (reserved)
    BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved)
    BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
    BIOS-e820: 00000000fed18000 - 00000000fed1c000 (reserved)
    BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
    BIOS-e820: 00000000feda0000 - 00000000feda6000 (reserved)
    BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
    BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
    DMI 2.4 present.
    last_pfn = 0x7f680 max_arch_pfn = 0x100000
    MTRR default type: uncachable
    MTRR fixed ranges enabled:
    00000-9FFFF write-back
    A0000-BFFFF uncachable
    C0000-CFFFF write-protect
    D0000-EFFFF uncachable
    F0000-FFFFF write-protect
    MTRR variable ranges enabled:
    0 base 000000000 mask F80000000 write-back
    1 base 07F800000 mask FFF800000 uncachable
    2 base 07F700000 mask FFFF00000 uncachable
    3 disabled
    4 disabled
    5 disabled
    6 disabled
    7 disabled
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    e820 update range: 0000000000002000 - 0000000000006000 (usable) ==> (reserved)
    Scanning 1 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000002000 (usable)
    modified: 0000000000002000 - 0000000000006000 (reserved)
    modified: 0000000000006000 - 000000000009f000 (usable)
    modified: 000000000009f000 - 00000000000a0000 (reserved)
    modified: 0000000000100000 - 000000007f680400 (usable)
    modified: 000000007f680400 - 0000000080000000 (reserved)
    modified: 00000000f8000000 - 00000000fc000000 (reserved)
    modified: 00000000fec00000 - 00000000fec10000 (reserved)
    modified: 00000000fed18000 - 00000000fed1c000 (reserved)
    modified: 00000000fed20000 - 00000000fed90000 (reserved)
    modified: 00000000feda0000 - 00000000feda6000 (reserved)
    modified: 00000000fee00000 - 00000000fee10000 (reserved)
    modified: 00000000ffe00000 - 0000000100000000 (reserved)
    initial memory mapped : 0 - 01800000
    init_memory_mapping: 0000000000000000-00000000377fe000
    0000000000 - 0000400000 page 4k
    0000400000 - 0037400000 page 2M
    0037400000 - 00377fe000 page 4k
    kernel direct mapping tables up to 377fe000 @ 7000-c000
    RAMDISK: 7f363000 - 7f66fa7a
    Allocated new RAMDISK: 00100000 - 0040ca7a
    Move RAMDISK from 000000007f363000 - 000000007f66fa79 to 00100000 - 0040ca79
    ACPI: RSDP 000fbb00 00024 (v02 DELL )
    ACPI: XSDT 7f681e00 00064 (v01 DELL M08 27D70717 ASL 00000061)
    ACPI: FACP 7f681c9c 000F4 (v04 DELL M08 27D70717 ASL 00000061)
    ACPI: DSDT 7f682400 0613B (v02 INT430 SYSFexxx 00001001 INTL 20050624)
    ACPI: FACS 7f690c00 00040
    ACPI: HPET 7f681f00 00038 (v01 DELL M08 00000001 ASL 00000061)
    ACPI: APIC 7f682000 00068 (v01 DELL M08 27D70717 ASL 00000047)
    ACPI: ASF! 7f681c00 0007E (v32 DELL M08 27D70717 ASL 00000061)
    ACPI: MCFG 7f681fc0 0003E (v16 DELL M08 27D70717 ASL 00000061)
    ACPI: SLIC 7f68209c 00024 (v01 DELL M08 27D70717 ASL 00000061)
    ACPI: TCPA 7f682300 00032 (v01 00000000 ASL 00000000)
    ACPI: SSDT 7f680731 004CC (v01 PmRef CpuPm 00003000 INTL 20050624)
    ACPI: Local APIC address 0xfee00000
    1150MB HIGHMEM available.
    887MB LOWMEM available.
    mapped low ram: 0 - 377fe000
    low ram: 0 - 377fe000
    node 0 low ram: 00000000 - 377fe000
    node 0 bootmap 00008000 - 0000ef00
    (9 early reservations) ==> bootmem [0000000000 - 00377fe000]
    #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
    #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
    #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
    #3 [0001000000 - 000152f024] TEXT DATA BSS ==> [0001000000 - 000152f024]
    #4 [000009f000 - 0000100000] BIOS reserved ==> [000009f000 - 0000100000]
    #5 [0001530000 - 0001536188] BRK ==> [0001530000 - 0001536188]
    #6 [0000007000 - 0000008000] PGTABLE ==> [0000007000 - 0000008000]
    #7 [0000100000 - 000040ca7a] NEW RAMDISK ==> [0000100000 - 000040ca7a]
    #8 [0000008000 - 000000f000] BOOTMAP ==> [0000008000 - 000000f000]
    Zone PFN ranges:
    DMA 0x00000000 -> 0x00001000
    Normal 0x00001000 -> 0x000377fe
    HighMem 0x000377fe -> 0x0007f680
    Movable zone start PFN for each node
    early_node_map[3] active PFN ranges
    0: 0x00000000 -> 0x00000002
    0: 0x00000006 -> 0x0000009f
    0: 0x00000100 -> 0x0007f680
    On node 0 totalpages: 521755
    free_area_init_node: node 0, pgdat c13dbe60, node_mem_map c1538000
    DMA zone: 32 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 3963 pages, LIFO batch:0
    Normal zone: 1744 pages used for memmap
    Normal zone: 221486 pages, LIFO batch:31
    HighMem zone: 2302 pages used for memmap
    HighMem zone: 292228 pages, LIFO batch:31
    Using APIC driver default
    ACPI: PM-Timer IO Port: 0x1008
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    ACPI: IRQ0 used by override.
    ACPI: IRQ2 used by override.
    ACPI: IRQ9 used by override.
    Enabling APIC mode: Flat. Using 1 I/O APICs
    Using ACPI (MADT) for SMP configuration information
    ACPI: HPET id: 0x8086a201 base: 0xfed00000
    SMP: Allowing 2 CPUs, 0 hotplug CPUs
    nr_irqs_gsi: 24
    PM: Registered nosave memory: 0000000000002000 - 0000000000006000
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
    Allocating PCI resources starting at 80000000 (gap: 80000000:78000000)
    Booting paravirtualized kernel on bare hardware
    NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
    PERCPU: Embedded 14 pages/cpu @c2800000 s34680 r0 d22664 u2097152
    pcpu-alloc: s34680 r0 d22664 u2097152 alloc=1*4194304
    pcpu-alloc: [0] 0 1
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 517677
    Kernel command line: root=/dev/group1/arch ro
    PID hash table entries: 4096 (order: 2, 16384 bytes)
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Initializing CPU#0
    Initializing HighMem for node 0 (000377fe:0007f680)
    Memory: 2060220k/2087424k available (2797k kernel code, 25764k reserved, 1185k data, 412k init, 1178120k highmem)
    virtual kernel memory layout:
    fixmap : 0xfff1e000 - 0xfffff000 ( 900 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
    lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
    .init : 0xc13e4000 - 0xc144b000 ( 412 kB)
    .data : 0xc12bb55a - 0xc13e3a08 (1185 kB)
    .text : 0xc1000000 - 0xc12bb55a (2797 kB)
    Checking if this processor honours the WP bit even in supervisor mode...Ok.
    SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Hierarchical RCU implementation.
    NR_IRQS:512
    Extended CMOS year: 2000
    Console: colour VGA+ 80x25
    console [tty0] enabled
    hpet clockevent registered
    HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Fast TSC calibration using PIT
    Detected 1795.296 MHz processor.
    Calibrating delay loop (skipped), value calculated using timer frequency.. 3592.20 BogoMIPS (lpj=5984320)
    Security Framework initialized
    Mount-cache hash table entries: 512
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 2048K
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 0
    mce: CPU supports 6 MCE banks
    CPU0: Thermal monitoring enabled (TM2)
    using mwait in idle threads.
    Performance Events: Core2 events, Intel PMU driver.
    ... version: 2
    ... bit width: 40
    ... generic registers: 2
    ... value mask: 000000ffffffffff
    ... max period: 000000007fffffff
    ... fixed-purpose events: 3
    ... event mask: 0000000700000003
    Checking 'hlt' instruction... OK.
    ACPI: Core revision 20090903
    ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    CPU0: Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz stepping 0d
    Booting processor 1 APIC 0x1 ip 0x6000
    Initializing CPU#1
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 2048K
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 1
    CPU1: Thermal monitoring enabled (TM2)
    CPU1: Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz stepping 0d
    checking TSC synchronization [CPU#0 -> CPU#1]: passed.
    Brought up 2 CPUs
    Total of 2 processors activated (7184.82 BogoMIPS).
    CPU0 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 0 1
    CPU1 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 1 0
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: MCFG configuration 0: base f8000000 segment 0 buses 0 - 63
    PCI: MCFG area at f8000000 reserved in E820
    PCI: Using MMCONFIG for extended config space
    PCI: Using configuration type 1 for base access
    bio: create slab <bio-0> at 0
    ACPI: EC: Look up EC in DSDT
    ACPI: SSDT 7f690c80 00043 (v01 LMPWR DELLLOM 00001001 INTL 20050624)
    ACPI: Interpreter enabled
    ACPI: (supports S0 S3 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    ACPI: ACPI Dock Station Driver: 3 docks/bays found
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:02.0: reg 10 64bit mmio: [0xfea00000-0xfeafffff]
    pci 0000:00:02.0: reg 18 64bit mmio pref: [0xe0000000-0xefffffff]
    pci 0000:00:02.0: reg 20 io port: [0xefe8-0xefef]
    pci 0000:00:02.1: reg 10 64bit mmio: [0xfeb00000-0xfebfffff]
    pci 0000:00:1a.0: reg 20 io port: [0x6f20-0x6f3f]
    pci 0000:00:1a.1: reg 20 io port: [0x6f00-0x6f1f]
    pci 0000:00:1a.7: reg 10 32bit mmio: [0xfed1c400-0xfed1c7ff]
    pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    pci 0000:00:1a.7: PME# disabled
    pci 0000:00:1b.0: reg 10 64bit mmio: [0xfe9fc000-0xfe9fffff]
    pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:1b.0: PME# disabled
    pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.0: PME# disabled
    pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.1: PME# disabled
    pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.5: PME# disabled
    pci 0000:00:1d.0: reg 20 io port: [0x6f80-0x6f9f]
    pci 0000:00:1d.1: reg 20 io port: [0x6f60-0x6f7f]
    pci 0000:00:1d.2: reg 20 io port: [0x6f40-0x6f5f]
    pci 0000:00:1d.7: reg 10 32bit mmio: [0xfed1c000-0xfed1c3ff]
    pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    pci 0000:00:1d.7: PME# disabled
    pci 0000:00:1f.0: quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
    pci 0000:00:1f.0: quirk: region 1080-10bf claimed by ICH6 GPIO
    pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0900 (mask 007f)
    pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 0c80 (mask 003f)
    pci 0000:00:1f.1: reg 10 io port: [0x1f0-0x1f7]
    pci 0000:00:1f.1: reg 14 io port: [0x3f4-0x3f7]
    pci 0000:00:1f.1: reg 18 io port: [0x170-0x177]
    pci 0000:00:1f.1: reg 1c io port: [0x374-0x377]
    pci 0000:00:1f.1: reg 20 io port: [0x6fa0-0x6faf]
    pci 0000:00:1f.2: reg 10 io port: [0x6eb0-0x6eb7]
    pci 0000:00:1f.2: reg 14 io port: [0x6eb8-0x6ebb]
    pci 0000:00:1f.2: reg 18 io port: [0x6ec0-0x6ec7]
    pci 0000:00:1f.2: reg 1c io port: [0x6ec8-0x6ecb]
    pci 0000:00:1f.2: reg 20 io port: [0x6ee0-0x6eef]
    pci 0000:00:1f.2: reg 24 io port: [0xeff0-0xefff]
    pci 0000:00:1f.2: PME# supported from D3hot
    pci 0000:00:1f.2: PME# disabled
    pci 0000:00:1f.3: reg 10 32bit mmio: [0xfe9fbf00-0xfe9fbfff]
    pci 0000:00:1f.3: reg 20 io port: [0x10c0-0x10df]
    pci 0000:0c:00.0: reg 10 32bit mmio: [0xfe8ff000-0xfe8fffff]
    pci 0000:0c:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:0c:00.0: PME# disabled
    pci 0000:00:1c.1: bridge 32bit mmio: [0xfe800000-0xfe8fffff]
    pci 0000:09:00.0: reg 10 64bit mmio: [0xfe7f0000-0xfe7fffff]
    pci 0000:09:00.0: PME# supported from D3hot D3cold
    pci 0000:09:00.0: PME# disabled
    pci 0000:00:1c.5: bridge 32bit mmio: [0xfe700000-0xfe7fffff]
    pci 0000:03:01.0: reg 10 32bit mmio: [0x000000-0x000fff]
    pci 0000:03:01.0: supports D1 D2
    pci 0000:03:01.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:03:01.0: PME# disabled
    pci 0000:03:01.4: reg 10 32bit mmio: [0xfe6ff000-0xfe6fffff]
    pci 0000:03:01.4: reg 14 32bit mmio: [0xfe6fe800-0xfe6fefff]
    pci 0000:03:01.4: supports D1 D2
    pci 0000:03:01.4: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:03:01.4: PME# disabled
    pci 0000:00:1e.0: transparent bridge
    pci 0000:00:1e.0: bridge 32bit mmio: [0xfe600000-0xfe6fffff]
    pci_bus 0000:00: on NUMA node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *10
    ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 11) *3
    ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
    vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    vgaarb: loaded
    PCI: Using ACPI for IRQ routing
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    Switching to clocksource tsc
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp 00:0b: io resource (0x1000-0x1005) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
    pnp 00:0b: io resource (0x1008-0x100f) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
    pnp 00:0c: io resource (0x1006-0x1007) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
    pnp 00:0c: io resource (0x100a-0x1059) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
    pnp 00:0c: io resource (0x1060-0x107f) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
    pnp 00:0c: io resource (0x1010-0x102f) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
    pnp: PnP ACPI: found 14 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:05: ioport range 0xc80-0xcaf has been reserved
    system 00:05: ioport range 0xcc0-0xcff could not be reserved
    system 00:08: iomem range 0xfed00000-0xfed003ff has been reserved
    system 00:0a: ioport range 0xcb0-0xcbb has been reserved
    system 00:0a: iomem range 0xfed40000-0xfed44fff has been reserved
    system 00:0b: ioport range 0x900-0x97f has been reserved
    system 00:0b: ioport range 0x4d0-0x4d1 has been reserved
    system 00:0c: ioport range 0xf400-0xf4fe has been reserved
    system 00:0c: ioport range 0x1080-0x10bf has been reserved
    system 00:0c: ioport range 0x10c0-0x10df has been reserved
    system 00:0c: ioport range 0x809-0x809 has been reserved
    system 00:0d: iomem range 0x0-0x9efff could not be reserved
    system 00:0d: iomem range 0x9f000-0x9ffff could not be reserved
    system 00:0d: iomem range 0xc0000-0xcffff could not be reserved
    system 00:0d: iomem range 0xe0000-0xfffff could not be reserved
    system 00:0d: iomem range 0x100000-0x7f6803ff could not be reserved
    system 00:0d: iomem range 0x7f680400-0x7f6fffff has been reserved
    system 00:0d: iomem range 0x7f700000-0x7f7fffff has been reserved
    system 00:0d: iomem range 0x7f700000-0x7fefffff could not be reserved
    system 00:0d: iomem range 0xffe00000-0xffffffff has been reserved
    system 00:0d: iomem range 0xffa00000-0xffbfffff has been reserved
    system 00:0d: iomem range 0xfec00000-0xfec0ffff could not be reserved
    system 00:0d: iomem range 0xfee00000-0xfee0ffff has been reserved
    system 00:0d: iomem range 0xfed20000-0xfed3ffff has been reserved
    system 00:0d: iomem range 0xfed45000-0xfed8ffff has been reserved
    system 00:0d: iomem range 0xfeda0000-0xfeda3fff has been reserved
    system 00:0d: iomem range 0xfeda4000-0xfeda4fff has been reserved
    system 00:0d: iomem range 0xfeda5000-0xfeda5fff has been reserved
    system 00:0d: iomem range 0xfeda6000-0xfeda6fff has been reserved
    system 00:0d: iomem range 0xfed18000-0xfed1bfff has been reserved
    system 00:0d: iomem range 0xf8000000-0xfbffffff has been reserved
    pci 0000:00:1c.0: PCI bridge, secondary bus 0000:0b
    pci 0000:00:1c.0: IO window: 0x2000-0x2fff
    pci 0000:00:1c.0: MEM window: 0x84000000-0x841fffff
    pci 0000:00:1c.0: PREFETCH window: 0x00000084200000-0x000000843fffff
    pci 0000:00:1c.1: PCI bridge, secondary bus 0000:0c
    pci 0000:00:1c.1: IO window: 0x3000-0x3fff
    pci 0000:00:1c.1: MEM window: 0xfe800000-0xfe8fffff
    pci 0000:00:1c.1: PREFETCH window: 0x00000084400000-0x000000845fffff
    pci 0000:00:1c.5: PCI bridge, secondary bus 0000:09
    pci 0000:00:1c.5: IO window: 0x4000-0x4fff
    pci 0000:00:1c.5: MEM window: 0xfe700000-0xfe7fffff
    pci 0000:00:1c.5: PREFETCH window: 0x00000084600000-0x000000847fffff
    pci 0000:03:01.0: CardBus bridge, secondary bus 0000:04
    pci 0000:03:01.0: IO window: 0x005000-0x0050ff
    pci 0000:03:01.0: IO window: 0x005400-0x0054ff
    pci 0000:03:01.0: PREFETCH window: 0x80000000-0x83ffffff
    pci 0000:03:01.0: MEM window: 0x88000000-0x8bffffff
    pci 0000:00:1e.0: PCI bridge, secondary bus 0000:03
    pci 0000:00:1e.0: IO window: 0x5000-0x5fff
    pci 0000:00:1e.0: MEM window: 0xfe600000-0xfe6fffff
    pci 0000:00:1e.0: PREFETCH window: 0x80000000-0x83ffffff
    pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    pci 0000:00:1c.0: setting latency timer to 64
    pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:1c.1: setting latency timer to 64
    pci 0000:00:1c.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:1c.5: setting latency timer to 64
    pci 0000:00:1e.0: setting latency timer to 64
    pci 0000:03:01.0: enabling device (0000 -> 0003)
    pci 0000:03:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    pci_bus 0000:00: resource 0 io: [0x00-0xffff]
    pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
    pci_bus 0000:0b: resource 0 io: [0x2000-0x2fff]
    pci_bus 0000:0b: resource 1 mem: [0x84000000-0x841fffff]
    pci_bus 0000:0b: resource 2 pref mem [0x84200000-0x843fffff]
    pci_bus 0000:0c: resource 0 io: [0x3000-0x3fff]
    pci_bus 0000:0c: resource 1 mem: [0xfe800000-0xfe8fffff]
    pci_bus 0000:0c: resource 2 pref mem [0x84400000-0x845fffff]
    pci_bus 0000:09: resource 0 io: [0x4000-0x4fff]
    pci_bus 0000:09: resource 1 mem: [0xfe700000-0xfe7fffff]
    pci_bus 0000:09: resource 2 pref mem [0x84600000-0x847fffff]
    pci_bus 0000:03: resource 0 io: [0x5000-0x5fff]
    pci_bus 0000:03: resource 1 mem: [0xfe600000-0xfe6fffff]
    pci_bus 0000:03: resource 2 pref mem [0x80000000-0x83ffffff]
    pci_bus 0000:03: resource 3 io: [0x00-0xffff]
    pci_bus 0000:03: resource 4 mem: [0x000000-0xffffffff]
    pci_bus 0000:04: resource 0 io: [0x5000-0x50ff]
    pci_bus 0000:04: resource 1 io: [0x5400-0x54ff]
    pci_bus 0000:04: resource 2 pref mem [0x80000000-0x83ffffff]
    pci_bus 0000:04: resource 3 mem: [0x88000000-0x8bffffff]
    NET: Registered protocol family 2
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    pci 0000:00:02.0: Boot video device
    Unpacking initramfs...
    Freeing initrd memory: 3122k freed
    apm: BIOS not found.
    Scanning for low memory corruption every 60 seconds
    audit: initializing netlink socket (disabled)
    type=2000 audit(1269905228.550:1): initialized
    highmem bounce pool size: 64 pages
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 1730
    alg: No test for stdrng (krng)
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pcieport 0000:00:1c.0: irq 24 for MSI/MSI-X
    pcieport 0000:00:1c.0: setting latency timer to 64
    pcieport 0000:00:1c.1: irq 25 for MSI/MSI-X
    pcieport 0000:00:1c.1: setting latency timer to 64
    pcieport 0000:00:1c.5: irq 26 for MSI/MSI-X
    pcieport 0000:00:1c.5: setting latency timer to 64
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    input: Macintosh mouse button emulation as /devices/virtual/input/input0
    PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    Using IPI No-Shortcut mode
    PM: Resume from disk failed.
    registered taskstats version 1
    Initalizing network drop monitor service
    Freeing unused kernel memory: 412k freed
    input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
    SCSI subsystem initialized
    libata version 3.00 loaded.
    ata_piix 0000:00:1f.1: version 2.13
    ata_piix 0000:00:1f.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    ata_piix 0000:00:1f.1: setting latency timer to 64
    scsi0 : ata_piix
    scsi1 : ata_piix
    ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x6fa0 irq 14
    ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x6fa8 irq 15
    ata_piix 0000:00:1f.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
    ata2: port disabled. ignoring.
    ata_piix 0000:00:1f.2: setting latency timer to 64
    scsi2 : ata_piix
    scsi3 : ata_piix
    ata3: SATA max UDMA/133 cmd 0x6eb0 ctl 0x6eb8 bmdma 0x6ee0 irq 17
    ata4: SATA max UDMA/133 cmd 0x6ec0 ctl 0x6ec8 bmdma 0x6ee8 irq 17
    ata1.00: ATAPI: PBDS DVD+/-RW DS-8W1P, BD1B, max UDMA/33
    ata1.00: configured for UDMA/33
    scsi 0:0:0:0: CD-ROM PBDS DVD+-RW DS-8W1P BD1B PQ: 0 ANSI: 5
    ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3.01: SATA link down (SStatus 0 SControl 300)
    ata3.00: ATA-7: ST9160823AS, 3.ADC, max UDMA/133
    ata3.00: 312581808 sectors, multi 8: LBA48 NCQ (depth 0/32)
    ata3.00: configured for UDMA/133
    scsi 2:0:0:0: Direct-Access ATA ST9160823AS 3.AD PQ: 0 ANSI: 5
    ata4.01: failed to resume link (SControl 0)
    ata4.00: SATA link down (SStatus 0 SControl 300)
    ata4.01: SATA link down (SStatus 0 SControl 0)
    sd 2:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
    sd 2:0:0:0: [sda] Write Protect is off
    sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1 sda2 sda3
    sd 2:0:0:0: [sda] Attached SCSI disk
    sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:0:0: Attached scsi CD-ROM sr0
    device-mapper: uevent: version 1.0.3
    device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: [email protected]
    padlock: VIA PadLock not detected.
    EXT4-fs (dm-4): INFO: recovery required on readonly filesystem
    EXT4-fs (dm-4): write access will be enabled during recovery
    EXT4-fs (dm-4): orphan cleanup on readonly fs
    EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79470
    EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79469
    EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79468
    EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79467
    EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79466
    EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 48873
    EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 14902
    EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 115506
    EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 2598
    EXT4-fs (dm-4): 9 orphan inodes deleted
    EXT4-fs (dm-4): recovery complete
    EXT4-fs (dm-4): mounted filesystem with ordered data mode
    rtc_cmos 00:03: RTC can wake from S4
    rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    udev: starting version 151
    fuse init (API version 7.13)
    ACPI: SSDT 7f681138 00244 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
    ACPI: SSDT 7f680bfd 004B6 (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
    Monitor-Mwait will be used to enter C-1 state
    Monitor-Mwait will be used to enter C-2 state
    Monitor-Mwait will be used to enter C-3 state
    Marking TSC unstable due to TSC halts in idle
    processor LNXCPU:00: registered as cooling_device0
    ACPI: SSDT 7f68137c 000C4 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
    ACPI: SSDT 7f6810b3 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
    Switching to clocksource hpet
    processor LNXCPU:01: registered as cooling_device1
    dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
    thermal LNXTHERM:01: registered as thermal_zone0
    ACPI: Thermal Zone [THM] (95 C)
    sr 0:0:0:0: Attached scsi generic sg0 type 5
    sd 2:0:0:0: Attached scsi generic sg1 type 0
    ACPI: AC Adapter [AC] (on-line)
    input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
    ACPI: Lid Switch [LID]
    input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
    ACPI: Power Button [PBTN]
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 22 (level, low) -> IRQ 22
    ehci_hcd 0000:00:1a.7: setting latency timer to 64
    ehci_hcd 0000:00:1a.7: EHCI Host Controller
    ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:1a.7: debug port 1
    iTCO_vendor_support: vendor-support=0
    ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
    ehci_hcd 0000:00:1a.7: irq 22, io mem 0xfed1c400
    Linux agpgart interface v0.103
    ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 4 ports detected
    ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    ehci_hcd 0000:00:1d.7: setting latency timer to 64
    ehci_hcd 0000:00:1d.7: EHCI Host Controller
    ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
    ehci_hcd 0000:00:1d.7: debug port 1
    ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
    ehci_hcd 0000:00:1d.7: irq 20, io mem 0xfed1c000
    ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 6 ports detected
    ACPI: Battery Slot [BAT0] (battery present)
    input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4
    ACPI: Sleep Button [SBTN]
    ACPI: WMI: Mapper loaded
    ACPI: Battery Slot [BAT1] (battery absent)
    tg3.c:v3.102 (September 1, 2009)
    tg3 0000:09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    tg3 0000:09:00.0: setting latency timer to 64
    i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
    agpgart-intel 0000:00:00.0: Intel 965GM Chipset
    agpgart-intel 0000:00:00.0: detected 7676K stolen memory
    iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060)
    iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
    eth0: Tigon3 [partno(BCM95755m) rev a002] (PCI Express) MAC address 00:1c:23:1c:0d:5b
    eth0: attached PHY is 5755 (10/100/1000Base-T Ethernet) (WireSpeed[1])
    eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
    eth0: dma_rwctrl[76180000] dma_mask[64-bit]
    uhci_hcd: USB Universal Host Controller Interface driver
    uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    uhci_hcd 0000:00:1a.0: setting latency timer to 64
    uhci_hcd 0000:00:1a.0: UHCI Host Controller
    uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:1a.0: irq 20, io base 0x00006f20
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
    uhci_hcd 0000:00:1a.1: setting latency timer to 64
    uhci_hcd 0000:00:1a.1: UHCI Host Controller
    uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
    uhci_hcd 0000:00:1a.1: irq 21, io base 0x00006f00
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    uhci_hcd 0000:00:1d.0: setting latency timer to 64
    uhci_hcd 0000:00:1d.0: UHCI Host Controller
    uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
    uhci_hcd 0000:00:1d.0: irq 20, io base 0x00006f80
    usb usb5: configuration #1 chosen from 1 choice
    hub 5-0:1.0: USB hub found
    hub 5-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
    uhci_hcd 0000:00:1d.1: setting latency timer to 64
    uhci_hcd 0000:00:1d.1: UHCI Host Controller
    uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
    uhci_hcd 0000:00:1d.1: irq 21, io base 0x00006f60
    usb usb6: configuration #1 chosen from 1 choice
    hub 6-0:1.0: USB hub found
    hub 6-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
    uhci_hcd 0000:00:1d.2: setting latency timer to 64
    uhci_hcd 0000:00:1d.2: UHCI Host Controller
    uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
    uhci_hcd 0000:00:1d.2: irq 22, io base 0x00006f40
    usb usb7: configuration #1 chosen from 1 choice
    hub 7-0:1.0: USB hub found
    hub 7-0:1.0: 2 ports detected
    [drm] Initialized drm 1.1.0 20060810
    cfg80211: Calling CRDA to update world regulatory domain
    input: DualPoint Stick as /devices/platform/i8042/serio1/input/input5
    input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input6
    yenta_cardbus 0000:03:01.0: CardBus bridge found [1028:01f9]
    yenta_cardbus 0000:03:01.0: O2: res at 0x94/0xD4: 00/ea
    yenta_cardbus 0000:03:01.0: O2: enabling read prefetch/write burst
    i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    i915 0000:00:02.0: setting latency timer to 64
    i915 0000:00:02.0: irq 27 for MSI/MSI-X
    [drm] set up 7M of stolen space
    iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
    iwl3945: Copyright(c) 2003-2009 Intel Corporation
    iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    iwl3945 0000:0c:00.0: setting latency timer to 64
    yenta_cardbus 0000:03:01.0: ISA IRQ mask 0x0cb8, PCI irq 19
    yenta_cardbus 0000:03:01.0: Socket status: 30000006
    pci_bus 0000:03: Raising subordinate bus# of parent bus (#03) from #04 to #07
    yenta_cardbus 0000:03:01.0: pcmcia: parent PCI bridge I/O window: 0x5000 - 0x5fff
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0x5000-0x5fff: clean.
    yenta_cardbus 0000:03:01.0: pcmcia: parent PCI bridge Memory window: 0xfe600000 - 0xfe6fffff
    yenta_cardbus 0000:03:01.0: pcmcia: parent PCI bridge Memory window: 0x80000000 - 0x83ffffff
    firewire_ohci 0000:03:01.4: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    iwl3945 0000:0c:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
    iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
    iwl3945 0000:0c:00.0: irq 28 for MSI/MSI-X
    usb 5-1: new low speed USB device using uhci_hcd and address 2
    firewire_ohci: Added fw-ohci device 0000:03:01.4, OHCI version 1.10
    phy0: Selected rate control algorithm 'iwl-3945-rs'
    usb 5-1: configuration #1 chosen from 1 choice
    vboxdrv: Trying to deactivate the NMI watchdog permanently...
    vboxdrv: Successfully done.
    vboxdrv: Found 2 processor cores.
    vboxdrv: fAsync=0 offMin=0x19e offMax=0x5df
    vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    vboxdrv: Successfully loaded version 3.1.4_OSE (interface 0x00100001).
    usb 7-1: new full speed USB device using uhci_hcd and address 2
    usbcore: registered new interface driver hiddev
    input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input7
    generic-usb 0003:046D:C025.0001: input,hidraw0: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1/input0
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    firewire_core: created device fw0: GUID 384fc00038f52070, S400
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean.
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean.
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff:
    usb 7-1: configuration #1 chosen from 1 choice
    clean.
    hub 7-1:1.0: USB hub found
    hub 7-1:1.0: 4 ports detected
    usb 7-1.2: new full speed USB device using uhci_hcd and address 3
    [drm] TV-16: set mode NTSC 480i 0
    usb 7-1.2: configuration #1 chosen from 1 choice
    [drm] LVDS-8: set mode 1280x800 1f
    CPU0: Temperature above threshold, cpu clock throttled (total events = 1)
    Disabling lock debugging due to kernel taint
    CPU0: Temperature/speed normal
    Console: switching to colour frame buffer device 160x50
    fb0: inteldrmfb frame buffer device
    registered panic notifier
    input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:01/input/input8
    ACPI: Video Device [VID1] (multi-head: yes rom: no post: no)
    ACPI Warning for \_SB_.PCI0.VID2._DOD: Return Package has no elements (empty) (20090903/nspredef-433)
    input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:02/input/input9
    ACPI: Video Device [VID2] (multi-head: yes rom: no post: no)
    [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
    HDA Intel 0000:00:1b.0: setting latency timer to 64
    input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10
    input: HDA Intel Mic at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
    input: HDA Intel HP Out at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
    loop: module loaded
    EXT4-fs (dm-2): mounted filesystem with ordered data mode
    EXT4-fs (dm-3): mounted filesystem with ordered data mode
    iwl3945 0000:0c:00.0: firmware: requesting iwlwifi-3945-2.ucode
    iwl3945 0000:0c:00.0: loaded firmware version 15.32.2.9
    Registered led device: iwl-phy0::radio
    Registered led device: iwl-phy0::assoc
    Registered led device: iwl-phy0::RX
    Registered led device: iwl-phy0::TX
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    ADDRCONF(NETDEV_UP): wlan0: link is not ready
    tg3 0000:09:00.0: irq 29 for MSI/MSI-X
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    tg3: eth0: Link is up at 100 Mbps, full duplex.
    tg3: eth0: Flow control is on for TX and on for RX.
    ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [drm] TV-16: set mode NTSC 480i 0
    [drm] TV-16: set mode NTSC 480i 0
    [drm] TV-16: set mode NTSC 480i 0
    [drm] TV-16: set mode NTSC 480i 0
    CE: hpet increasing min_delta_ns to 15000 nsec
    eth0: no IPv6 routers present
    CE: hpet increasing min_delta_ns to 22500 nsec
    Registered led device: iwl-phy0::radio
    Registered led device: iwl-phy0::assoc
    Registered led device: iwl-phy0::RX
    Registered led device: iwl-phy0::TX
    ADDRCONF(NETDEV_UP): wlan0: link is not ready
    tg3 0000:09:00.0: PME# enabled
    tg3 0000:09:00.0: PME# disabled
    tg3 0000:09:00.0: irq 29 for MSI/MSI-X
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    tg3 0000:09:00.0: PME# enabled
    tg3 0000:09:00.0: PME# disabled
    tg3 0000:09:00.0: irq 29 for MSI/MSI-X
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    tg3: eth0: Link is up at 100 Mbps, full duplex.
    tg3: eth0: Flow control is on for TX and on for RX.
    ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    eth0: no IPv6 routers present
    usb 5-1: USB disconnect, address 2
    usb 5-1: new low speed USB device using uhci_hcd and address 3
    usb 5-1: configuration #1 chosen from 1 choice
    input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input13
    generic-usb 0003:046D:C025.0002: input,hidraw0: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1/input0
    usb 5-1: USB disconnect, address 3
    usb 5-1: new low speed USB device using uhci_hcd and address 4
    usb 5-1: configuration #1 chosen from 1 choice
    input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input14
    generic-usb 0003:046D:C025.0003: input,hidraw0: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1/input0
    Machine check events logged
    CE: hpet increasing min_delta_ns to 33750 nsec
    input input14: event field not found
    input input14: event field not found
    usb 5-1: USB disconnect, address 4
    usb 5-1: new low speed USB device using uhci_hcd and address 5
    usb 5-1: configuration #1 chosen from 1 choice
    input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input15
    generic-usb 0003:046D:C025.0004: input,hidraw0: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1/input0
    ps -Af
    # ps -Af
    UID PID PPID C STIME TTY TIME CMD
    root 1 0 0 Mar29 ? 00:00:00 init [5]
    root 2 0 0 Mar29 ? 00:00:00 [kthreadd]
    root 3 2 0 Mar29 ? 00:00:00 [migration/0]
    root 4 2 0 Mar29 ? 00:00:00 [ksoftirqd/0]
    root 5 2 0 Mar29 ? 00:00:00 [watchdog/0]
    root 6 2 0 Mar29 ? 00:00:00 [migration/1]
    root 7 2 0 Mar29 ? 00:00:00 [ksoftirqd/1]
    root 8 2 0 Mar29 ? 00:00:00 [watchdog/1]
    root 9 2 0 Mar29 ? 00:00:00 [events/0]
    root 10 2 0 Mar29 ? 00:00:00 [events/1]
    root 11 2 0 Mar29 ? 00:00:00 [khelper]
    root 12 2 0 Mar29 ? 00:00:00 [async/mgr]
    root 13 2 0 Mar29 ? 00:00:00 [pm]
    root 14 2 0 Mar29 ? 00:00:00 [sync_supers]
    root 15 2 0 Mar29 ? 00:00:00 [bdi-default]
    root 16 2 0 Mar29 ? 00:00:00 [kblockd/0]
    root 17 2 0 Mar29 ? 00:00:00 [kblockd/1]
    root 18 2 0 Mar29 ? 00:00:00 [kacpid]
    root 19 2 0 Mar29 ? 00:00:00 [kacpi_notify]
    root 20 2 0 Mar29 ? 00:00:00 [kacpi_hotplug]
    root 21 2 0 Mar29 ? 00:00:00 [kseriod]
    root 24 2 0 Mar29 ? 00:00:00 [khungtaskd]
    root 25 2 0 Mar29 ? 00:00:00 [kswapd0]
    root 26 2 0 Mar29 ? 00:00:00 [ksmd]
    root 27 2 0 Mar29 ? 00:00:00 [aio/0]
    root 28 2 0 Mar29 ? 00:00:00 [aio/1]
    root 29 2 0 Mar29 ? 00:00:00 [crypto/0]
    root 30 2 0 Mar29 ? 00:00:00 [crypto/1]
    root 732 2 0 Mar29 ? 00:00:01 [ata/0]
    root 771 2 0 Mar29 ? 00:00:00 [ata/1]
    root 800 2 0 Mar29 ? 00:00:00 [ata_aux]
    root 836 2 0 Mar29 ? 00:00:02 [scsi_eh_0]
    root 884 2 0 Mar29 ? 00:00:00 [scsi_eh_1]
    root 930 2 0 Mar29 ? 00:00:00 [scsi_eh_2]
    root 931 2 0 Mar29 ? 00:00:00 [scsi_eh_3]
    root 968 2 0 Mar29 ? 00:00:00 [kstriped]
    root 971 2 0 Mar29 ? 00:00:00 [kdmflush]
    root 974 2 0 Mar29 ? 00:00:00 [kdmflush]
    root 977 2 0 Mar29 ? 00:00:00 [kdmflush]
    root 980 2 0 Mar29 ? 00:00:00 [kdmflush]
    root 1014 2 0 Mar29 ? 00:00:00 [kdmflush]
    root 1015 2 0 Mar29 ? 00:00:01 [kcryptd_io]
    root 1016 2 2 Mar29 ? 00:01:10 [kcryptd]
    root 1025 2 0 Mar29 ? 00:00:00 [jbd2/dm-4-8]
    root 1026 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
    root 1027 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
    root 1060 1 0 Mar29 ? 00:00:00 /sbin/udevd --daemon
    root 1591 2 0 Mar29 ? 00:00:01 [flush-254:4]
    root 1747 2 0 Mar29 ? 00:00:00 [kondemand/0]
    root 1795 2 0 Mar29 ? 00:00:00 [kondemand/1]
    root 1920 2 0 Mar29 ? 00:00:00 [kconservative/0]
    root 1961 2 0 Mar29 ? 00:00:00 [kconservative/1]
    root 2168 2 0 Mar29 ? 00:00:00 [kpsmoused]
    root 2563 2 0 Mar29 ? 00:00:00 [ksuspend_usbd]
    root 2591 2 0 Mar29 ? 00:00:00 [khubd]
    root 2961 2 0 Mar29 ? 00:00:00 [i915/0]
    root 2962 2 0 Mar29 ? 00:00:00 [i915/1]
    root 2974 2 0 Mar29 ? 00:00:00 [pccardd]
    root 2996 2 0 Mar29 ? 00:00:00 [iwl3945]
    root 3004 2 0 Mar29 ? 00:00:01 [phy0]
    root 3073 2 0 Mar29 ? 00:00:00 [usbhid_resumer]
    root 3336 2 0 Mar29 ? 00:00:00 [hd-audio0]
    root 4143 2 0 Mar29 ? 00:00:00 [kdmflush]
    root 4144 2 0 Mar29 ? 00:00:00 [kcryptd_io]
    root 4145 2 0 Mar29 ? 00:00:00 [kcryptd]
    root 4170 2 0 Mar29 ? 00:00:00 [jbd2/dm-2-8]
    root 4171 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
    root 4172 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
    root 4173 2 0 Mar29 ? 00:00:00 [jbd2/dm-3-8]
    root 4174 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
    root 4175 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
    root 4180 1 0 Mar29 ? 00:00:00 /sbin/mount.ntfs-3g /dev/sda1 /mnt/win -o rw,noexec,nosuid,nodev,users,uid=1001,gid=100,fmask=0113,dmask=000
    root 4448 1 0 Mar29 ? 00:00:00 supervising syslog-ng
    root 4449 4448 0 Mar29 ? 00:00:00 /usr/sbin/syslog-ng
    root 4458 1 0 Mar29 ? 00:00:00 /usr/sbin/acpid
    dbus 4472 1 1 Mar29 ? 00:00:27 /usr/bin/dbus-daemon --system
    hal 4475 1 0 Mar29 ? 00:00:04 /usr/sbin/hald
    root 4476 4475 0 Mar29 ? 00:00:00 hald-runner
    root 4504 4476 0 Mar29 ? 00:00:00 hald-addon-input: Listening on /dev/input/event4 /dev/input/event3 /dev/input/event9 /dev/input/event8 /dev/
    root 4508 4476 0 Mar29 ? 00:00:00 /usr/lib/hal/hald-addon-rfkill-killswitch
    root 4520 4476 0 Mar29 ? 00:00:03 hald-addon-storage: polling /dev/sr0 (every 2 sec)
    root 4521 4476 0 Mar29 ? 00:00:00 /usr/lib/hal/hald-addon-cpufreq
    hal 4522 4476 0 Mar29 ? 00:00:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
    root 4851 1 0 Mar29 ? 00:00:00 /usr/sbin/crond -S -l info
    root 4863 1 1 Mar29 ? 00:00:37 /usr/bin/python -O /usr/share/wicd/daemon/wicd-daemon.py
    ntp 4877 1 0 Mar29 ? 00:00:00 /usr/sbin/ntpd -s
    root 4894 4863 0 Mar29 ? 00:00:25 /usr/bin/python -O /usr/share/wicd/daemon/monitor.py
    mpd 4908 1 0 Mar29 ? 00:00:00 /usr/bin/mpd /etc/mpd.conf
    root 4916 1 0 Mar29 ? 00:00:00 truecrypt -t -k /etc/dropboxkey --protect-hidden=no --password= --fs-options=umask=0002,uid=dropbox,gid=drop
    root 4918 1 0 Mar29 ? 00:00:00 truecrypt -t -k /etc/dropboxkey --protect-hidden=no --password= --fs-options=umask=0002,uid=dropbox,gid=drop
    root 4925 2 0 Mar29 ? 00:00:00 [loop0]
    root 4928 2 0 Mar29 ? 00:00:00 [kdmflush]
    root 4929 2 0 Mar29 ? 00:00:00 [kcryptd_io]
    root 4930 2 0 Mar29 ? 00:00:00 [kcryptd]
    root 4947 1 0 Mar29 tty1 00:00:00 /sbin/agetty 38400 tty1 linux
    root 4948 1 0 Mar29 tty2 00:00:00 /sbin/agetty 38400 tty2 linux
    root 4949 1 0 Mar29 tty3 00:00:00 /sbin/agetty 38400 tty3 linux
    root 4950 1 0 Mar29 tty6 00:00:00 /bin/login -f
    zed 4951 4950 0 Mar29 tty6 00:00:00 -bash
    zed 4993 4951 0 Mar29 tty6 00:00:00 /bin/sh /usr/bin/startx
    zed 5010 4993 0 Mar29 tty6 00:00:00 xinit /home/zed/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth.LXTS3D7lp0
    root 5011 5010 10 Mar29 tty4 00:04:27 /usr/bin/X -nolisten tcp
    zed 5020 5010 0 Mar29 tty6 00:00:00 ck-launch-session openbox-session
    root 5022 1 0 Mar29 ? 00:00:00 /usr/sbin/console-kit-daemon --no-daemon
    zed 5095 5020 0 Mar29 tty6 00:00:03 /usr/bin/openbox
    zed 5099 5095 0 Mar29 tty6 00:00:00 gnome-session
    root 5106 1 0 Mar29 ? 00:00:00 /usr/sbin/ntpd -s
    zed 5109 1 0 Mar29 ? 00:00:00 /usr/bin/ssh-agent
    zed 5113 1 0 Mar29 tty6 00:00:00 dbus-launch --exit-with-session gnome-session
    zed 5114 1 0 Mar29 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
    root 5118 1 0 Mar29 ? 00:00:00 /usr/lib/DeviceKit/devkit-power-daemon
    zed 5122 1 0 Mar29 ? 00:00:00 /usr/lib/GConf/gconfd-2
    zed 5140 1 0 Mar29 tty6 00:00:00 gnome-keyring-daemon --start
    zed 5142 5099 0 Mar29 tty6 00:00:06 gnome-panel
    zed 5152 1 0 Mar29 ? 00:00:00 /usr/lib/gvfs/gvfsd
    zed 5157 1 0 Mar29 ? 00:00:00 /usr/lib/gvfs//gvfs-fuse-daemon /home/zed/.gvfs
    zed 5161 5099 0 Mar29 tty6 00:00:00 /usr/lib/gnome-disk-utility/gdu-notification-daemon
    zed 5162 5099 0 Mar29 tty6 00:00:08 /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py
    zed 5163 5099 0 Mar29 tty6 00:00:00 /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1
    zed 5165 1 0 Mar29 ? 00:00:00 /usr/lib/bonobo/bonobo-activation-server --ac-activate --ior-output-fd=18
    root 5167 1 0 Mar29 ? 00:00:00 /usr/lib/polkit-1/polkitd
    root 5170 1 0 Mar29 ? 00:00:00 /usr/lib/DeviceKit/devkit-disks-daemon
    root 5171 5170 0 Mar29 ? 00:00:02 devkit-disks-daemon: polling /dev/sr0
    zed 5188 1 0 Mar29 ? 00:00:01 /usr/lib/gnome-applets/mixer_applet2 --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory --oaf-ior-fd=18
    zed 5190 1 0 Mar29 ? 00:00:00 /usr/lib/gnome-panel/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory
    zed 5192 1 0 Mar29 ? 00:00:00 /usr/lib/gnome-applets/battstat-applet-2 --oaf-activate-iid=OAFIID:GNOME_BattstatApplet_Factory --oaf-ior-fd
    zed 5200 1 0 Mar29 ? 00:00:18 /usr/lib/gnome-panel/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior-fd=19
    zed 5202 1 0 Mar29 ? 00:00:00 /usr/lib/gvfs/gvfs-gdu-volume-monitor
    zed 5208 1 0 Mar29 ? 00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
    zed 5215 1 0 Mar29 ? 00:00:03 python /usr/lib/hamster-applet/hamster-applet --oaf-activate-iid=OAFIID:Hamster_Applet_Factory --oaf-ior-fd=
    zed 5218 1 0 Mar29 ? 00:00:01 /usr/lib/gnome-panel/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=32
    zed 5236 1 0 Mar29 ? 00:00:00 /usr/lib/evolution-data-server-1.2/evolution-data-server-2.28 --oaf-activate-iid=OAFIID:GNOME_Evolution_Data
    root 5257 4476 0 Mar29 ? 00:00:00 /usr/lib/hal/hald-addon-leds
    root 5270 4863 0 Mar29 ? 00:00:00 [dhcpcd] <defunct>
    root 5291 1 0 Mar29 ? 00:00:00 /sbin/dhcpcd eth0 -h tortuga
    zed 5295 5095 0 Mar29 tty6 00:00:02 urxvt -fn -*-terminus-medium-*-*-*-16-*-*-*-*-*-iso8859-2 -e sudo su -
    root 5297 5295 0 Mar29 pts/0 00:00:00 su -
    root 5299 5297 0 Mar29 pts/0 00:00:06 -bash
    zed 5364 5095 16 Mar29 tty6 00:07:00 /usr/lib/chromium/chromium
    zed 5365 5364 0 Mar29 tty6 00:00:18 /usr/lib/chromium/chromium
    zed 5366 5364 0 Mar29 tty6 00:00:00 /usr/lib/chromium/chromium --type=zygote
    zed 5390 5366 0 Mar29 tty6 00:00:03 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=DnsImpact/_default_enabled_prefet
    zed 5395 5366 0 Mar29 tty6 00:00:04 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=DnsImpact/_default_enabled_prefet
    zed 5406 5366 0 Mar29 tty6 00:00:06 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=DnsImpact/_default_enabled_prefet
    zed 5411 5366 0 Mar29 tty6 00:00:04 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=DnsImpact/_default_enabled_prefet
    zed 5479 5366 7 Mar29 tty6 00:03:10 /usr/lib/chromium/chromium --type=renderer --lang=en-US --force-fieldtest=CacheSize/CacheSizeGroup_3/DnsImpa
    dropbox 5492 1 0 Mar29 ? 00:00:10 /home/dropbox/.dropbox-dist/dropbox
    zed 5543 1 0 Mar29 ? 00:00:00 kdeinit4: kdeinit4 Running...
    zed 5545 5543 0 Mar29 ? 00:00:00 kdeinit4: klauncher [kdeinit] --fd=8
    zed 5548 1 0 Mar29 ? 00:00:02 kdeinit4: kded4 [kdeinit]
    zed 5562 5543 0 Mar29 ? 00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp
    zed 5567 1 0 Mar29 ? 00:00:01 /usr/bin/knotify4
    root 5572 1060 0 Mar29 ? 00:00:00 /sbin/udevd --daemon
    zed 5717 1 0 Mar29 ? 00:00:00 /usr/lib/gamin/gam_server
    zed 6126 5366 2 Mar29 tty6 00:00:28 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=CacheSize/CacheSizeGroup_3/DnsImp
    root 6459 1 0 Mar29 ? 00:00:00 /usr/lib/sa/sadc -F -L -S DISK 600 6 -
    root 6518 1060 0 00:01 ? 00:00:00 /sbin/udevd --daemon
    root 6804 2 0 00:10 ? 00:00:00 [flush-254:6]
    root 6807 5299 0 00:10 pts/0 00:00:00 ps -Af
    Edit: typo
    Edit2: I found the source of slowness - removing vboxdrv module restores system performance. How to get VirtualBox working I will try to solve somewhere else.
    Last edited by stabele (2010-03-30 20:40:52)

    sand_man wrote:X is running at 25% cpu on average
    Your's and mine problems are probably not connected, I had low CPU utilization from all sources (including X), but system was dead slow anyway.

  • Troubleshoot recent overheating + immediate shutdowns (hard/software?)

    Since last Friday, I've been experiencing frequent, instant shutdowns due to overheating. I've had these occur before, but generally when running intensive computations in R. I'd initiate a script at bedtime, and wake up to find my computer off (shut down in the night). I learned to put a small book under it, run a fan next to it, or literally place it on it's side, resting on the non-fan edge and the lid to expose the whole bottom to "breathe." Recently, however, I have incessant, unexpected, immediate shutdowns during "normal use" (terminal, browser with, say, 4-10 non-video-playing tabs open), or even just updating with pacman.
    Unfortunately, use of some proprietary software along with needing some IE-specific sites at work had me in Windows 7 for ~1.5 weeks non-stop. This is really unusual for me, and I prefer to live in Arch as much as possible. Because of this, I didn't get to notice if this would have gradually increased in frequency or started abruptly. The behavior is drastically and noticeably different than anything I've experienced, completely kills the use of Linux for me, and I'd really like to identify if this is something to do with software, or if I'm experiencing a hardware failure of some sort (loose thermal gel?). I did a mess of trials this weekend, with results below. Thanks for any input or suggestions.
    System details
    - HP 8540w workstation
    - Intel i7 Q720 (4 physical cores, 8 virtual)
    - Nvidia Quadro FX 1800M
    - Using nvidia (334.21-4), nvidia-utils (334.21-4), nvidia-libgl (334.21-7)
    - Relevant BIOS options (as far as I can tell):
    --- Multi-core: turns off all physical cores other than the first
    --- Intel HT Technology: hyperthreading support (appears to turn off all virtual/hyperthreaded cores)
    --- Virtualization (unsure if relevant, but affects dmesg output for kvm abilities)
    $ uname -a
    Linux bigBang 3.14.0-5-ARCH #1 SMP PREEMPT Fri Apr 11 21:02:33 CEST 2014 x86_64 GNU/Linux
    $ sudo cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    ondemand # same for all other cpus, 1-7
    I have acpi installed, but not acpid, laptop tools, cpupower, or others mentioned in the power management or CPU frequency scaling Wiki articles.
    Edit: Oops! I caught that I actually did have cpupower installed, from way back in 2012, and removed it last night. I don't recall ever setting it up, and issuing `locate cpupower` now that it's gone doesn't get any hits, so I'm thinking this means I never created a config file for it (which would have yielded, I think, a file.pacsave upon removal). Sorry for the mixup!
    Assume everything else is "stock" (in other words, no kernel options appended, etc.). This is pretty much a "vanilla" Arch system other than the applications I've installed. Feel free to ask follow up questions if I've missed something relevant.
    System messages
    Here are examples of the errors I'm seeing:
    $ dmesg | grep -i mce
    [ 0.040954] mce: CPU supports 9 MCE banks
    [18912.069281] mce: [Hardware Error]: Machine check events logged
    [19662.531507] mce: [Hardware Error]: Machine check events logged
    [20112.808818] mce: [Hardware Error]: Machine check events logged
    $ dmesg | grep -i temper
    [ 367.990859] CPU6: Core temperature above threshold, cpu clock throttled (total events = 1)
    [ 367.990862] CPU7: Core temperature above threshold, cpu clock throttled (total events = 1)
    [ 367.991919] CPU6: Core temperature/speed normal
    [ 367.991922] CPU7: Core temperature/speed normal
    [ 668.175622] CPU6: Core temperature above threshold, cpu clock throttled (total events = 508)
    [ 668.175623] CPU7: Core temperature above threshold, cpu clock throttled (total events = 508)
    [ 668.176683] CPU6: Core temperature/speed normal
    [ 668.176685] CPU7: Core temperature/speed normal
    Here are my limits, per lm_sensors:
    $ sensors
    coretemp-isa-0000
    Adapter: ISA adapter
    Core 0: +57.0°C (high = +84.0°C, crit = +100.0°C)
    Core 1: +57.0°C (high = +84.0°C, crit = +100.0°C)
    Core 2: +57.0°C (high = +84.0°C, crit = +100.0°C)
    Core 3: +57.0°C (high = +84.0°C, crit = +100.0°C)
    I installed the mcelog package, which shows messages like this:
    Hardware event. This is not a software error.
    Apr 14 21:36:50 bigBang mcelog[10019]: MCE 0
    Apr 14 21:36:50 bigBang mcelog[10019]: CPU 5 THERMAL EVENT TSC 1b184fe88d88
    Apr 14 21:36:50 bigBang mcelog[10019]: TIME 1397511379 Mon Apr 14 16:36:19 2014
    Apr 14 21:36:50 bigBang mcelog[10019]: Processor 5 heated above trip temperature. Throttling enabled.
    Apr 14 21:36:50 bigBang mcelog[10019]: Please check your system cooling. Performance will be impacted
    Apr 14 21:36:50 bigBang mcelog[10019]: STATUS 880003c3 MCGSTATUS 0
    Apr 14 21:36:50 bigBang mcelog[10019]: MCGCAP 1c09 APICID 5 SOCKETID 0
    Apr 14 21:36:50 bigBang mcelog[10019]: CPUID Vendor Intel Family 6 Model 30
    Apr 14 21:36:50 bigBang mcelog[10019]: Hardware event. This is not a software error.
    Apr 14 21:36:50 bigBang mcelog[10019]: MCE 1
    Apr 14 21:36:50 bigBang mcelog[10019]: CPU 4 THERMAL EVENT TSC 1b184fe8a5da
    Apr 14 21:36:50 bigBang mcelog[10019]: TIME 1397511379 Mon Apr 14 16:36:19 2014
    Apr 14 21:36:50 bigBang mcelog[10019]: Processor 4 heated above trip temperature. Throttling enabled.
    Apr 14 21:36:50 bigBang mcelog[10019]: Please check your system cooling. Performance will be impacted
    Apr 14 21:36:50 bigBang mcelog[10019]: STATUS 880003c3 MCGSTATUS 0
    Apr 14 21:36:50 bigBang mcelog[10019]: MCGCAP 1c09 APICID 4 SOCKETID 0
    Apr 14 21:36:50 bigBang mcelog[10019]: CPUID Vendor Intel Family 6 Model 30
    Apr 14 21:36:50 bigBang mcelog[10019]: Hardware event. This is not a software error.
    Method
    In updating my AUR-built packages, I got repeated shutdowns when trying to build pandoc-static, a pretty compiling-heavy package. I googled around quite a bit about thermal events, with nothing conclusively sticking out as the solution. Honestly, it reduced to trying pcie_aspm=0 or pcie_aspm=force -- that's really about all I could find! I thought I would try various things and log the temperature and frequency while trying to build pandoc-static. Here was my final summary of trials conducted:
    Key:
    - bios virt: "Virtualization Technology" turned on in BIOS?
    - bios multi: "Multi-Core" turned on in BIOS?
    - intel ht: "Intel HT Technology" turned on in BIOS?
    - X: started X with `startx` or run from TTY1?
    - cores: which CPUs were active (as per the scheme in /sys/devices/system/cpu/cpu*)?
    - success: did pandoc-static build successfully (1), or did the machine hard kill itself (0)?
    | log id | kernel | pcie_aspm | bios virt | bios multi | intel ht | X? | cores | success? | note |
    |--------+----------+-----------------+-----------+------------+----------+----+---------------+----------+-----------------------|
    | 4 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | [0-5] | 1 | |
    | 5 | 3.14.0-5 | pcie_aspm=0 | 1 | 1 | 1 | 1 | all | 0 | |
    | 6 | 3.14.0-5 | pcie_aspm=force | 1 | 1 | 1 | 1 | all | 0 | |
    | 7 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | all | 1 | |
    | 8 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | 0, 2, 4, 6 | 0 | |
    | 9 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | 0, 1, 3, 5, 7 | 0 | can't turn off core 0 |
    | 10 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | [0-5] | 1 | replicate (4) |
    | 11 | 3.10.36 | default | 1 | 1 | 1 | 1 | all | 0 | |
    | 12 | 3.14.0-5 | default | 1 | 1 | 1 | 0 | all | 0 | |
    | 13 | 3.14.0-5 | default | 0 | 1 | 1 | 1 | all | 0 | |
    | 14 | 3.14.0-5 | default | 0 | 0 | 1 | 1 | 0-1 | 1 | |
    | 15 | 3.14.0-5 | default | 0 | 1 | 0 | 1 | 0-3 | 0 | |
    | 16 | 3.10.36 | default | 1 | 1 | 1 | 0 | all | 0 | |
    | 17 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | all | 0 | |
    | 18 | 3.14.0-5 | default | 1 | 1 | 1 | 1 | [0-5] | 1 | replicate (4) |
    For instances where only certain cores were enabled, the following method was used:
    # echo 0 > /sys/devices/system/cpu/cpu6/online
    The effect was verified in the output of dmesg for each core:
    [ 2024.174235] kvm: disabling virtualization on CPU6
    [ 2030.187053] kvm: disabling virtualization on CPU7
    I tried a couple without X to rule out an Nvidia issue, as I also have a recent issue of closing my lid not suspending anymore. This is apparently an Nvidia issue, so I thought I'd at least try to rule it out. I threw in the LTS kernel just to see if I noticed any differences (I didn't).
    In each case, I used the following procedure:
    - Fresh boot
    - Open one instance of urxvt with three tabs (or three TTYs if running one of the two non-X trials)
    - run a cpu-logging script as root in one tab, a dmesg logging script from a regular user tab, and `yaourt pandoc-static` from a third tab
    - if the machine hard killed, move on. If not, stop the logger, reboot, and start over (applying any BIOS changes when necessary)
    All trials except 16, 17, and 18 were run at my house in the dining room, with the laptop resting on a small book (not obscuring the fan ports underneath). The last three were run today at work, and I put a similarly sized book under the laptop to try and replicate conditions reasonably well.
    I wrote a kludgy script (I'm no bash guy...) to collect the data in csv format. It's called by another script (not shown) that runs a continuous while loop every 10 seconds.
    #!/bin/sh
    temp0=`sensors | grep "Core 0" | awk '{print $3}' | sed s/"+"// | sed s/"°C"//`
    temp1=`sensors | grep "Core 1" | awk '{print $3}' | sed s/"+"// | sed s/"°C"//`
    temp2=`sensors | grep "Core 2" | awk '{print $3}' | sed s/"+"// | sed s/"°C"//`
    temp3=`sensors | grep "Core 3" | awk '{print $3}' | sed s/"+"// | sed s/"°C"//`
    for i in 0 1 2 3 4 5 6 7
    do
    eval cpu$i=`cat /sys/devices/system/cpu/cpu$i/cpufreq/cpuinfo_cur_freq`
    done
    time=`date +%H:%M:%S`
    top=`ps aux | awk '{print $11, $3}' | sort -k2rn | head -n 3`
    top=`echo $top | sed s/" "/", "/g`
    echo "$time, $temp0, $temp1, $temp2, $temp3, $cpu0, $cpu1, $cpu2, $cpu3, $cpu4, $cpu5, $cpu6, $cpu7, $top" >> /home/jwhendy/temp-freq.log
    I also output the results of `dmesg | grep -i mce` and `dmesg | grep -i temper` to two separate files every 10 seconds.
    Results
    The result of most interest came when I noticed that it was always cpu6 and cpu7 that showed up in dmesg logs. I found the trick above about disabling specific cores, and decided to try it... the build succeeded! I replicated this effect three different times, which I find significant given that almost nothing else succeeded.
    I used R and the ggplot2 package to plot the results, and here are two replicates of "default" Arch 3.14.0 (no changes) vs. the three runs in which I've disabled cores 6-7:
    Note the absence of the rapid spikes > 90C, which are entirely the blue lines in the left two plots. That color is for the "Core 3" temperature reported by lm_sensors (fourth core), which I take it is responsible for cpu6 and cpu7. Subjectively, I noticed that the laptop ran with much lower fan speeds, they kicked in later in the build, and simply ran less with cpu6/7 off. Frequencies appear to jump around with both, showing a pretty even spread of them cycling. The plots don't make it very clear, but the first default run succeeded, while the second one hard shutdown. Again, all three with cpu6/7 off succeeded.
    Discussion
    Case closed? Is this definitely a hardware issue? I'm still not sure, and that's where I'd like some assistance. Having replicated three successes with cpu6 and cpu7 off, I felt pretty confident. But from my current boot (with cpu6/7 off), I checked dmesg after running rsync for a couple hours catching up on backups!
    [18661.079071] CPU4: Core temperature above threshold, cpu clock throttled (total events = 1)
    [18661.079072] CPU5: Core temperature above threshold, cpu clock throttled (total events = 1)
    [18661.080133] CPU4: Core temperature/speed normal
    [18661.080135] CPU5: Core temperature/speed normal
    [19598.570458] CPU5: Core temperature above threshold, cpu clock throttled (total events = 182)
    [19598.570459] CPU4: Core temperature above threshold, cpu clock throttled (total events = 182)
    [19598.571517] CPU4: Core temperature/speed normal
    [19598.571520] CPU5: Core temperature/speed normal
    [20015.016963] CPU4: Core temperature above threshold, cpu clock throttled (total events = 221)
    [20015.016965] CPU5: Core temperature above threshold, cpu clock throttled (total events = 221)
    [20015.019037] CPU4: Core temperature/speed normal
    [20015.019040] CPU5: Core temperature/speed normal
    Also, note that run #15 above (disabling hyperthreading in BIOS) turns off cpu4-7, however the dmesg temp logs show that cpu3 was reporting temperature overages and that trial resulted in a hard shutdown. I'm not confident in how the system numbers the cpus (cpu0 and cpu1 are the hyperthreads for the first physical core? Is this always the case?). If numbering is consistent and this means that cpu6 and cpu7 are both hyperthreads of two different cores, this is also perplexing, since runs #8 and #9 turned off odd and even (respectively) cores yet saw no improvement. Both reported one of the suspect cpus (6 for even run, 7 for the odd), and both hard killed, #8 before it could even log any high spikes.
    - Here's a plot of those two runs
    There's also the issue that this never happens on Windows, or at least the forced shutdowns don't occur. Perhaps there are warnings or logs somewhere showing the same issue, but it's controlling the issue somehow. I'd love suggestions to check; if there aren't any errors reported, that shifts the evidence back to a potential software issue.
    Lastly, mcelog says flat out "This is not a software error." Now, I hear that... but I don't understand why changing which hyperthreads are online should change which cores overheat (always the highest numbered one). Or, say, could disabling those cores just disable the associated temperature sensor and it's still just as hot in that area, but it's not being measured/reported?
    For now, turning off cpu6 and cpu7 at least gives me a system that doesn't die on me with every action, so Arch remains usable. I've read a bunch of posts on this that frankly aren't much help. They range in content from "One cpu is ~10C higher than others" (to which people say, "Don't worry about it") to advice to simply go in an manually change the cpu temperature threshold values (seems like a horrible idea to me), to aspm fiddling (which seems like it was supposedly fixed in Linux 3.0+ if not before), and changing governors (I'm on ondemand, not performance, which seems reasonable).
    I typed a lot above, and that's because I would like the best chance I have to know what this is related to. Alright, 'nuff of the problem. Onto the solution. Many thanks for reading, and any assistance/suggestions you can provide.
    Last edited by jwhendy (2014-04-15 16:08:56)

    @ewaller: thanks for the feedback! Yeah, this was one of my more obsessive ones for sure. I admit that data collection and analysis is both a part of my job, and a hobby
    Re. Windows: subjectively, I think Windows runs with the fan much less (but always has, not a recent thing). It's also much slower and far less responsive (issue something like alt+tab to change windows and wait 1-3 full seconds for it to catch up). I could run something intensive in Win7 and check the logs to see if anything similar shows up (could Win7 just be controlling it somehow?). What surprises me is that Arch is catching that the cpus are over critical and throttling them, but they seem to spike so fast from ~80C to 100C that it can't do anything but hard kill.
    Re. hardware: thanks for your take. I plan to take this apart and brush/blow any dust out, so I'll take a look while I'm in there for anything obviously loose or weird.
    Re. what's changed: I've wondered that myself and am just drawing a blank. I tried to check for over-temp reports in journalctl, but unfortunately, have SystemMaxUse=250M in /etc/systemd/journald.conf. It appears that all of my experiments this weekend purged older entries, so journalctl starts at 2014-04-12 -- bummer. Still, I haven't changed anything major that I'm aware of. Just booted up, started doing normal stuff (updating packages, chromium, etc.), and I noticed the fan ramp up like crazy. Then that horrid "peeew" sound when the computer kills itself. Thought it was a fluke, but happened again and again.
    Re. pacman logs: here's my pacman log for what I think is a relevant period. Prior to 2014-04-09, the previous entry was 2014-03-31 (that period was the living-in-Windows time I mentioned). I omitted some more recent entries since the problem was already present as of Apr 09-10, and a majority of more recent entries are related to trying to get nouveau to work with acceleration (lots of installing/un-installing nvidia/nouveau to troubleshoot that issue -- in progress!).
    [2014-04-09 17:48] [PACMAN] Running 'pacman -Syu'
    [2014-04-09 17:48] [PACMAN] synchronizing package lists
    [2014-04-09 17:48] [PACMAN] starting full system upgrade
    [2014-04-09 17:54] [PACMAN] upgraded apr-util (1.5.3-3 -> 1.5.3-4)
    [2014-04-09 17:54] [PACMAN] upgraded readline (6.3-3 -> 6.3.003-2)
    [2014-04-09 17:54] [PACMAN] upgraded bash (4.3-3 -> 4.3.008-2)
    [2014-04-09 17:54] [PACMAN] upgraded boost-libs (1.55.0-4 -> 1.55.0-5)
    [2014-04-09 17:54] [PACMAN] upgraded openssl (1.0.1.f-2 -> 1.0.1.g-1)
    [2014-04-09 17:54] [PACMAN] upgraded ca-certificates (20140223-2 -> 20140325-1)
    [2014-04-09 17:54] [PACMAN] upgraded cpupower (3.13-2 -> 3.14-1)
    [2014-04-09 17:54] [PACMAN] upgraded cups-filters (1.0.50-1 -> 1.0.52-1)
    [2014-04-09 17:54] [PACMAN] installed libavc1394 (0.5.4-2)
    [2014-04-09 17:54] [PACMAN] installed libiec61883 (1.2.0-4)
    [2014-04-09 17:54] [PACMAN] installed gstreamer0.10-good-plugins (0.10.31-5)
    [2014-04-09 17:54] [PACMAN] upgraded farstream-0.1 (0.1.2-3 -> 0.1.2-4)
    [2014-04-09 17:54] [PACMAN] upgraded fftw (3.3.3-2 -> 3.3.4-1)
    [2014-04-09 17:54] [PACMAN] upgraded sqlite (3.8.4.2-1 -> 3.8.4.3-1)
    [2014-04-09 17:54] [PACMAN] upgraded nss (3.15.5-2 -> 3.16-1)
    [2014-04-09 17:54] [PACMAN] upgraded flashplugin (11.2.202.346-1 -> 11.2.202.350-1)
    [2014-04-09 17:54] [PACMAN] upgraded ghostscript (9.10-3 -> 9.14-1)
    [2014-04-09 17:54] [PACMAN] upgraded gnutls (3.2.12.1-1 -> 3.2.13-1)
    [2014-04-09 17:54] [PACMAN] upgraded groff (1.22.2-5 -> 1.22.2-6)
    [2014-04-09 17:54] [PACMAN] upgraded hplip (3.14.3-2 -> 3.14.4-1)
    [2014-04-09 17:55] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
    [2014-04-09 17:55] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Starting build: 3.13.8-1-ARCH
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Image generation successful
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Starting build: 3.13.8-1-ARCH
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2014-04-09 17:55] [ALPM-SCRIPTLET] ==> Image generation successful
    [2014-04-09 17:55] [PACMAN] upgraded linux (3.13.7-1 -> 3.13.8-1)
    [2014-04-09 17:55] [PACMAN] upgraded linux-headers (3.13.7-1 -> 3.13.8-1)
    [2014-04-09 17:55] [PACMAN] upgraded man-pages (3.63-1 -> 3.64-1)
    [2014-04-09 17:55] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
    [2014-04-09 17:55] [PACMAN] upgraded pacman-mirrorlist (20140107-1 -> 20140405-1)
    [2014-04-09 17:55] [PACMAN] upgraded python2-numpy (1.8.0-3 -> 1.8.1-1)
    [2014-04-09 17:55] [PACMAN] upgraded r (3.0.2-2 -> 3.0.3-1)
    [2014-04-09 17:55] [PACMAN] upgraded xorg-xauth (1.0.8-1 -> 1.0.9-1)
    [2014-04-09 17:55] [PACMAN] upgraded yajl (2.0.4-2 -> 2.1.0-1)
    [2014-04-09 18:03] [PACMAN] Running 'pacman --color auto -Sy'
    [2014-04-09 18:03] [PACMAN] synchronizing package lists
    [2014-04-10 13:45] [PACMAN] Running 'pacman --color auto -Sy'
    [2014-04-10 13:45] [PACMAN] synchronizing package lists
    [2014-04-10 13:45] [PACMAN] Running 'pacman -Syu'
    [2014-04-10 13:45] [PACMAN] synchronizing package lists
    [2014-04-10 13:45] [PACMAN] starting full system upgrade
    [2014-04-10 13:46] [PACMAN] upgraded kmod (16-1 -> 17-1)
    [2014-04-10 13:46] [PACMAN] upgraded libsystemd (212-1 -> 212-2)
    [2014-04-10 13:46] [PACMAN] upgraded coreutils (8.22-3 -> 8.22-4)
    [2014-04-10 13:46] [PACMAN] upgraded libutil-linux (2.24.1-4 -> 2.24.1-6)
    [2014-04-10 13:46] [PACMAN] upgraded util-linux (2.24.1-4 -> 2.24.1-6)
    [2014-04-10 13:46] [PACMAN] upgraded systemd (212-1 -> 212-2)
    [2014-04-10 13:46] [PACMAN] upgraded chromium (33.0.1750.152-1 -> 34.0.1847.116-1)
    [2014-04-10 13:46] [PACMAN] upgraded x265 (0.8-2 -> 0.9-1)
    [2014-04-10 13:46] [PACMAN] upgraded ffmpeg (1:2.2-2 -> 1:2.2-3)
    [2014-04-10 13:47] [PACMAN] upgraded git (1.9.1-1 -> 1.9.2-1)
    [2014-04-10 13:47] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
    [2014-04-10 13:47] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Starting build: 3.14.0-4-ARCH
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Image generation successful
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Starting build: 3.14.0-4-ARCH
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2014-04-10 13:47] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2014-04-10 13:48] [ALPM-SCRIPTLET] ==> Image generation successful
    [2014-04-10 13:48] [PACMAN] upgraded linux (3.13.8-1 -> 3.14-4)
    [2014-04-10 13:48] [PACMAN] upgraded linux-headers (3.13.8-1 -> 3.14-4)
    [2014-04-10 13:48] [PACMAN] upgraded lirc-utils (1:0.9.0-70 -> 1:0.9.0-71)
    [2014-04-10 13:48] [PACMAN] upgraded nvidia (334.21-2 -> 334.21-4)
    [2014-04-10 13:48] [PACMAN] upgraded systemd-sysvcompat (212-1 -> 212-2)
    [2014-04-10 13:51] [PACMAN] Running 'pacman -Syu'
    [2014-04-10 13:51] [PACMAN] synchronizing package lists
    [2014-04-10 13:51] [PACMAN] starting full system upgrade
    [2014-04-10 13:51] [PACMAN] Running 'pacman -Sc'
    [2014-04-10 14:16] [PACMAN] Running 'pacman --color auto -Sy'
    [2014-04-10 14:16] [PACMAN] synchronizing package lists
    [2014-04-10 14:21] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.K0M/chromium-libpdf-1:34.0.1847.116-1-x86_64.pkg.tar.xz'
    [2014-04-10 14:21] [PACMAN] upgraded chromium-libpdf (1:33.0.1750.149-1 -> 1:34.0.1847.116-1)
    [2014-04-10 14:26] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.R9f/dropbox-2.6.25-1-x86_64.pkg.tar.xz'
    [2014-04-10 14:26] [PACMAN] upgraded dropbox (2.6.13-1 -> 2.6.25-1)
    [2014-04-10 15:41] [PACMAN] Running 'pacman -Syu'
    [2014-04-10 15:41] [PACMAN] synchronizing package lists
    [2014-04-10 15:41] [PACMAN] Running 'pacman --color auto -Sy'
    [2014-04-10 15:41] [PACMAN] synchronizing package lists
    [2014-04-10 15:43] [PACMAN] Running 'pacman --color auto -S -u'
    [2014-04-10 15:43] [PACMAN] starting full system upgrade
    [2014-04-10 15:43] [PACMAN] upgraded libjpeg-turbo (1.3.0-4 -> 1.3.1-1)
    [2014-04-10 15:43] [PACMAN] upgraded mpd (0.18.9-1 -> 0.18.10-1)
    [2014-04-10 15:43] [PACMAN] upgraded python2-urwid (1.2.0-2 -> 1.2.1-1)
    [2014-04-10 15:43] [PACMAN] Running 'pacman --color auto -S --asdeps --needed extra/itstool'
    [2014-04-10 15:44] [PACMAN] installed itstool (2.0.2-1)
    [2014-04-10 15:53] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.Ikd/evince-gtk-3.12.0-1-x86_64.pkg.tar.xz'
    [2014-04-10 15:53] [PACMAN] upgraded evince-gtk (3.10.3-1 -> 3.12.0-1)
    [2014-04-10 16:08] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.7Bs/jdk-8u0-1-x86_64.pkg.tar.xz'
    [2014-04-10 16:11] [PACMAN] Running 'pacman -S lm_sensors'
    [2014-04-10 16:12] [ALPM-SCRIPTLET] ==> Updating desktop MIME database...
    [2014-04-10 16:12] [ALPM-SCRIPTLET] ==> Updating MIME database...
    [2014-04-10 16:12] [ALPM-SCRIPTLET] ==> Updating icon cache...
    [2014-04-10 16:12] [PACMAN] upgraded jdk (7.51-1 -> 8u0-1)
    [2014-04-10 16:12] [PACMAN] Running 'pacman --color auto -S --asdeps --needed extra/cabal-install extra/ghc community/alex community/happy'
    [2014-04-10 16:13] [PACMAN] installed cabal-install (1.18.0.2-1)
    [2014-04-10 16:13] [PACMAN] installed ghc (7.6.3-1)
    [2014-04-10 16:13] [PACMAN] installed alex (3.1.3-1)
    [2014-04-10 16:13] [PACMAN] installed happy (1.19.3-1)
    [2014-04-10 16:14] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-jwhendy/PKGDEST.DcA/zukitwo-themes-20140329-1-any.pkg.tar.xz'
    [2014-04-10 16:14] [PACMAN] upgraded zukitwo-themes (20131210-1 -> 20140329-1)
    [2014-04-10 16:14] [PACMAN] Running 'pacman -Syu'
    [2014-04-10 16:14] [PACMAN] synchronizing package lists
    [2014-04-10 16:15] [PACMAN] starting full system upgrade
    [2014-04-10 16:16] [PACMAN] Running 'pacman -Rsc itstool happy ghc alex cabal-install'
    [2014-04-10 16:16] [PACMAN] removed cabal-install (1.18.0.2-1)
    [2014-04-10 16:16] [PACMAN] removed alex (3.1.3-1)
    [2014-04-10 16:16] [PACMAN] removed ghc (7.6.3-1)
    [2014-04-10 16:16] [PACMAN] removed happy (1.19.3-1)
    [2014-04-10 16:16] [PACMAN] removed itstool (2.0.2-1)
    [2014-04-10 17:40] [PACMAN] Running 'pacman -Rsc gnome-themes-standard unixobdc'
    [2014-04-10 17:40] [PACMAN] Running 'pacman -Rsc gnome-themes-standard unixodbc'
    [2014-04-10 17:40] [PACMAN] removed unixodbc (2.3.2-1)
    [2014-04-10 17:40] [PACMAN] removed gnome-themes-standard (3.10.0-1)
    [2014-04-10 17:40] [PACMAN] removed cantarell-fonts (0.0.15-1)
    [2014-04-10 17:40] [PACMAN] Running 'pacman -Sc'
    [2014-04-11 12:51] [PACMAN] Running 'pacman -S gnome-themes-standard'
    [2014-04-11 12:52] [PACMAN] installed cantarell-fonts (0.0.15-1)
    [2014-04-11 12:52] [PACMAN] installed gnome-themes-standard (3.10.0-1)
    I found a post about the graphics driver affecting the laptop temperature, which is prompting me to re-run the test above with nouveau. Unfortunately, I can't startx without noaccel=1 and I get horrible performance with this.The solution there was to use the kernel option `radeon.dpm=1`, which for nvidia appears to be to use DPMS, which I seem to have, so perhaps that isn't relevant/related?
    $ grep -i dpms /var/log/Xorg.0.log
    [ 52.969] Initializing built-in extension DPMS
    [ 56.794] (==) NVIDIA(0): DPMS enabled
    While I was looking for how far back the overheating went, I also stumbled across some other errors in journalctl like this:
    Apr 15 08:10:07 bigBang kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Apr 15 08:10:07 bigBang kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
    Apr 15 08:10:07 bigBang kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Apr 15 08:10:07 bigBang kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
    Apr 15 08:10:07 bigBang kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Apr 15 08:10:07 bigBang kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
    Apr 15 08:10:07 bigBang kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Apr 15 08:10:07 bigBang kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20131218/utaddress-258)
    This post mentions a similar warning, but doesn't really get resolved. Here's another bug about that, which is both recent and also unresolved (active). The bug, however, says nothing about what effect it actually has! I'm not sure if there's anything undesirable about it other than an ugly warning...
    Action items for me
    - Try with nouveau (X and no-X)
    - I'll be trying one of these utilities on Windows 7 shortly to see if the cpu temp is reported there.
    Thanks again for the response/suggestions!

Maybe you are looking for

  • Blu-ray creation causes windows blue screen crash

    I am testing Premier Elements 7 for the creation of best quality DVD and Blu ray disks. Source is AVCHD 1920x1080i and I have managed to create a number of DVD's and one Bluray without problem. My latest trial creating a Bluray disk failed at about 9

  • How to turn on Beats Audio?

    Hi, I just bought HP Pavilion Elite pc, with beats audio. how do I turn on the beats audio or the speakers on the pc? is there a built in speaker with the PC? I tried to press fn+B but nothing happened... many thanks

  • Boolean User Properties always returns TRUE

    Hi, I am trying to get some propeties from the user on the AD and I found out with the following issue, all the boolean attributes always return TRUE as value. The Code that I am using to extract them is the following foreach ($objUser in $objUsers)

  • Brand new iPad Mini for $250! Legit?

    http://discountordernow.com/products/Apple-iPad-mini-16GB%2C-Wi%252dFi%2C-7.9in- %252d-White-%26-Silver-%28Latest-Model%29.html

  • Version 3.0.5

    Is it possible to compress to flash with verision 3.0.5? IF so how does one do that? Is flash better quality then quicktime? Thanks!