System Freeze under 10.7 (not video related..)

I'm experiencing problem with system freezes that are not video related.
I've had several instances so far whereby my system freezes (the mouse cursor still reacts, but nothing is selectable) either at the Finder or the most recent when browsing apps in Launch Pad. The only fix is a hard restart. The only similarity to some of the posts re video is that my mac employs graphics switching, and I assume this is utilised when launching Launch Pad?
Doing a hard restart also starts Spotlight reindexing my HD. Something which was only done a few days ago when Lion was installed. Doing a normal restart at this point stops Spotlight indexing when returning to the finder.
Is anyone seeing the same behaviour on thier systems and has anyone found a cure? I've read that resetting the PRAM has helped some.

Okay, (I think) I've found a way around the first annoyance - there's an option in Time Machine preferences to lock documents after a certain length of time. Even though I never use Time Machine (I use an easier alternative) this option still controls things. Turning off that bit (it's on bit default) made thinks better.
I've yet to find a way around the second problem, any help will be appreciated.

Similar Messages

System freezes, likely due to overheating video card.

I have a Mac Pro (Intel Quad Core, 3ghz), with the OEM Radeon X1900. Recently the machine has been hanging pretty regularly over the past few months. It starts with pixel artifacts extending across certain windows. This phenomenon increases if I am doing some more intense graphic work (video editting, rendering, etc).
I've run through a several system utilities to ensure the integrity of the OS. As far as I can tell, disks and OS are fine.
The only solution I've found so far, is to keep the case open as I am working. This isn't ideal, as it's messing up the airflow over the other boards in the machine. it also let's a lot of dust in (though, maybe no more than normal!)
If it is in fact the card, is there a reasonable replacement, or even an upgrade that I should consider that would solve the problem? I would either want a very inexpensive direct replacement - and save my money for a new machine in the next year or so. OR get one that would be compatible with the latest system as well as mine.
Thoughts are appreciated!
Stephen

How do you know it's overheating you haven't posted any temperatures. If you don't know what they are then download and install iStatPro and then post the temps your system is showing. From those we can give you advice on whether your system is running hot or not.
Also you posted in an iMac forum, you may want to post in the correct forum which would be the Mac Pro forum.

MSI P67A-G43 (MS-7673) System Freezes and then will NOT Restart

Hello Everyone,
I was hoping someone out there might know what is going on with my system. My issue began about a week ago when my computer simply froze while in use. After realizing the system was not responding I hit the reset button and tried to restart, however the computer restarted to a black screen (NO words) and went no further. I turned off the power supply to force a shut down, turned it back on and then tried to restart again, only this time the computer went into a cycle where the lights flash, the fans run for 2-3 seconds, but the “all clear” beeps never sound and then everything turns off. The only way to stop the cycle is to cut the power. Because this cycle happened when I first built the computer (as a result of an improperly connected cable) I thought something inside the case might be lose, so I opened it up, removed everything and then put it back together.
This time when I started the system I got a screen that said “Previous overclocking has failed…” Now I have never tried to overclock my computer, nor do I know how, so I do not understand WHY my computer would give such a message. After this message however, the computer did actually restart and take me to windows, however the computer inevitably freezes again after use, sometimes after only a few seconds, sometimes after a few hours.
Furthermore, once I shut down the computer and try to restart it, it almost always goes into the cycle of trying to restart, but failing. When it does get past the ‘all clear’ beeps I get the failed overclocking message again. I did just discover a “super-charger.exe” MSI application that was trying to run every time I started the computer and I uninstalled the application, I’m not sure if that had something to do with the overclocking or not. I also took out 3 of the 4 memory sticks and I am running on just 1. For the moment (while I write this post) the computer is working but could very well freeze again at any time, though just now it did start up withOUT the overclocking message and went right to windows.
Thanks for taking the time to read through my problem. This issue has been going on for more then a week, ANY help would be VERY much appreciated!

If it is fine with one stick RAM, add the second so that both blue slots are used. If ok, then remove the second stick & replace it with one of the other sticks. If ok, try the last stick. If any of the tests fail with any of the sticks in the second slot, you found the bad one.

System freezes and then will not reboot

About two weeks ago I opened my MacBook Pro, just before a business trip only to find that it would not start, just a grey screen, if I left it long enough then the apple logo appeared and the loading circle, but that is as far as I got. As I was flying to Dubai and that is where I bought it I took it back to the MacStore there. They said that I would have to reinstall the operating system. After two hours attempting this they sent me away with the discs that I had to borrow from them and said I should do it myself. I flew on to Saudi ad attempted the reinstall there. It failed due to a software error. I attempted the process again, with the erase option, same result. A friend used the install disc utilities menu to check the hard drive when I was informed that the hard drive had failed.
I went to what I thought was an authorised Apple dealer CTS (Computer Technology Services of Jeddah and they replaced the hard drive. It worked for about 2 hours and then froze and refused to restart. The computer was quite hot. Once left to cool it would then restart but not until then, but each time I do this the time it runs is less and less. I have replacement batteries from the recall, so that is not the problem, but I only obtained them after the hard drive replacement.
I do not appear to be able to get any support from Apple as they say the computer is out of warranty - I don't understand why as I bought it in May from what I thought was an authorised retailer in Dubai. I live in Iran and there is virtually no support here, just other ex-pats with Macs.
The other problems that I have is that since the change of hard drive all of my music and programs have been de-authorised. The Mac also seems to corrupt programs I keep having to reload them from my back up LaCie hard drive (which fortunately I did a full back up to just before the thing failed.
I cannot even think where to go for help. I am actually thinking of buying a replacement and attempting to replace the original hard drive into it as what ever the problem was it does not appear to have been fixed by the replacement.
frustrated in Iran

Hi Tim! Sorry that you're having so much trouble with your MBP.
I have not had this issue with my MBP but from your discription it sounds like what happened to my G4 - namely the RAM went bad. I installed 3rd party RAM and it worked OK for a few weeks, then the G4 started to balk at starting, not always but most of the time, then finally I could not get pass the grey screen, it just stopped there.
I contacted a friend of mine and he immediately asked if I had an extra RAM in it and told me to remove it then reboot. That proved to be the solution. I didn't think of it because I thought the RAM would be bad from the get-go not go bad over the course of a month or so. Let me know if this might be your case.

I have an ipod touch 3G and i cannot update my system becouse under about is not there what can i do and also it has ios 4.3.3?

I have a ipod touch 3G and I have ios 4.3.3 and under about I don't have the system hardware update! what can I do?

If your iDevice is using a version of iOS lower than 5, you will need to use iTunes on your syncing computer to perform the upgrade. Use the Apple link below as a guide for the upgrade.
http://support.apple.com/kb/HT4972
Also read the instructions from the section entitled "Update your device using iTunes" at the link below.
http://support.apple.com/kb/HT4623
Information regarding transferring purchases from your iDevice to iTunes on your syncing computer can be found at the link below.
http://support.apple.com/kb/ht1848

System freezes due to hard disk problems only on Linux (not windows)

Intro/context:
Recently i've bought (about 2 months) a new laptop, a Lenovo G50-70, which came with Windows 8.1. As i had no interest on that OS, i formatted the disk and installed only Arch Linux. During that time i experienced system freezes which i had no idea why they were happening. As time went by, i found disk errors on system logs related to hard drive. I searched those errors and almost everything i found was that my hard drive had problems, so i decided to use my warranty. But first, i installed the original OS back again. And after using it a couple of weeks, i didn't experiencie any problem with my hard drive (on Linux it was really frequent). Now i've installed Arch Linux back, along with original Windows 8.1, having dual boot. There is no disk problem when using Windows, but when on Arch, i have the same errors and problems i used to have. So i assume it may be related to kernel or some confniguration issue.
I also haven't noticed any relation between system freezes and system use. I mean, it can happen either under light or heavy use.
tl dr: system freezes randomly for some minutes when using linux due to hard drive problems. The problem doesn't happen on windows.
What i've done so far:
The first period i was on Arch, i run smart (long and short), fsck, and hdparm tests. And nothing (no errors). Searched for bad blocks, and nothing. When back on windows, i also run tests on hdd and found no problems, except some sector reallocation not-that-nice indicators. These problems occured at the end of the first arch installation period. But still i currently experience no problem on windows.
I've also tried setting libata: noncq, 3.0G, noacpi, noapic kernel parameters, and had no result.
Changed BIOS setting from AHCI to Legacy, and no result. Also updated BIOS and no result.
I found no firmware update for this hard drive.
So i don't know what other thing i can try. I want to emphasize that there is no problem, no freezing, when running Windows, so i don't think it's a hard drive issue.
Info:
Hard drive is a Toshiba 2.5" HDD MQ01ABD100 5400 rpm.
Some logs i've recollected all this time:
journalctl -xfa --system
abr 21 13:51:13 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 13:51:24 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 21 13:51:24 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 7
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 13:51:24 echoes kernel: ata1.00: status: { DRDY }
abr 21 13:51:24 echoes kernel: ata1: hard resetting link
abr 21 13:51:24 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 13:51:24 echoes kernel: ata1.00: configured for UDMA/100
abr 21 13:51:24 echoes kernel: ata1: EH complete
abr 21 14:01:40 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 23 pio 512 in
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 22 pio 512 in
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 18
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:01:51 echoes udisksd[627]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_Y44MT611T: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
dmesg
[55661.023028] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 frozen
[55661.023034] ata1.00: failed command: READ FPDMA QUEUED
[55661.023040] ata1.00: cmd 60/08:78:18:08:c0/00:00:4b:00:00/40 tag 15 ncq 4096 in
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[55661.023042] ata1.00: status: { DRDY }
[55661.023046] ata1: hard resetting link
[55666.358537] ata1: link is slow to respond, please be patient (ready=0)
[55671.053813] ata1: COMRESET failed (errno=-16)
[55671.053819] ata1: hard resetting link
[55676.389438] ata1: link is slow to respond, please be patient (ready=0)
[55678.897149] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[55681.320305] ata1.00: configured for UDMA/100
[55681.320319] ata1.00: device reported invalid CHS sector 0
[55681.320349] ata1: EH complete
[55729.969443] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
[55729.969588] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
dmesg
[102884.889930] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[102884.890305] systemd[1]: Unit systemd-journald.service entered failed state.
[102884.890333] systemd[1]: systemd-journald.service failed.
[102885.560745] systemd-coredump[28916]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.5bf9a012fed048ce8975998cf3c3c20e.6705.1427990901000000.
[102885.860957] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/system.journal corrupted or uncleanly shut down, renaming and replacing.
[102921.797810] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[104179.117363] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[104179.117369] ata1.00: failed command: READ FPDMA QUEUED
[104179.117375] ata1.00: cmd 60/08:00:48:88:8b/00:00:4d:00:00/40 tag 0 ncq 4096 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[104179.117377] ata1.00: status: { DRDY }
[104179.117381] ata1: hard resetting link
[104184.453382] ata1: link is slow to respond, please be patient (ready=0)
[104189.149114] ata1: COMRESET failed (errno=-16)
[104189.149121] ata1: hard resetting link
[104189.469276] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104189.952982] ata1.00: configured for UDMA/100
[104189.952989] ata1.00: device reported invalid CHS sector 0
[104189.953004] ata1: EH complete
[104508.223792] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[104508.223798] ata1.00: failed command: SMART
[104508.223803] ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 2
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[104508.223806] ata1.00: status: { DRDY }
[104508.223810] ata1: hard resetting link
[104509.984601] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104510.698126] ata1.00: configured for UDMA/100
[104510.698157] ata1: EH complete
One of the latest and worse
journalctl -xfa --system
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:00:e0:d6:75/00:00:00:00:00/40 tag 0 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:08:08:d8:75/00:00:00:00:00/40 tag 1 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:10:30:d9:75/00:00:00:00:00/40 tag 2 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:18:58:da:75/00:00:00:00:00/40 tag 3 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:20:e8:e5:75/00:00:00:00:00/40 tag 4 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:28:80:db:75/00:00:00:00:00/40 tag 5 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:30:68:dd:75/00:00:00:00:00/40 tag 6 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:38:90:de:75/00:00:00:00:00/40 tag 7 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:40:b8:df:75/00:00:00:00:00/40 tag 8 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:48:90:e1:75/00:00:00:00:00/40 tag 9 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:50:98:e3:75/00:00:00:00:00/40 tag 10 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:58:c0:e4:75/00:00:00:00:00/40 tag 11 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/c8:78:28:b9:2a/0b:00:4e:00:00/40 tag 15 ncq 1544192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:80:b0:4b:c0/00:00:4f:00:00/40 tag 16 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:88:90:4b:80/00:00:50:00:00/40 tag 17 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:90:98:22:81/00:00:50:00:00/40 tag 18 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:98:00:0e:00/00:00:5f:00:00/40 tag 19 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a0:00:08:80/00:00:5f:00:00/40 tag 20 ncq 4096 out
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a8:80:08:80/00:00:5f:00:00/40 tag 21 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:b0:08:0b:81/00:00:5f:00:00/40 tag 22 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:b8:70:c8:75/00:00:00:00:00/40 tag 23 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c0:20:c9:75/00:00:00:00:00/40 tag 24 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c8:88:c9:75/00:00:00:00:00/40 tag 25 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d0:58:ca:75/00:00:00:00:00/40 tag 26 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d8:a0:ce:75/00:00:00:00:00/40 tag 27 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e0:68:d3:75/00:00:00:00:00/40 tag 28 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e8:90:d4:75/00:00:00:00:00/40 tag 29 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:f0:b8:d5:75/00:00:00:00:00/40 tag 30 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 12 88 d7 c0 00 04 d0 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 310958016
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 36311758 (offset 8388608 size 2695168 starting block 38869906)
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995128
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995129
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995130
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995131
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995132
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995133
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995134
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995135
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995136
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995137
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4b dd 39 88 00 01 78 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1272789384
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 34999445 (offset 0 size 192512 starting block 159098720)
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4e 2a b3 e8 00 05 40 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1311421416
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 35001016 (offset 0 size 2232320 starting block 163927845)
abr 22 12:57:11 echoes kernel: ata1: EH complete
abr 22 12:57:11 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 22 12:57:11 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 22 12:57:11 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 25
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1: EH complete
Current smart status:
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.1-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD100
Serial Number: Y44MT611T
LU WWN Device Id: 5 000039 5e1a80e85
Firmware Version: AX1P5E
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun May 3 16:42:06 2015 ART
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 234) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1671
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 306
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 152
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 699
10 Spin_Retry_Count 0x0033 106 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 300
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 216
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14
193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 14140
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 16/44)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 19
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 515
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 190
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Vendor (0x50) Completed without error 00% 611 -
# 2 Short offline Completed without error 00% 611 -
# 3 Short offline Completed without error 00% 597 -
# 4 Vendor (0x50) Completed without error 00% 583 -
# 5 Short offline Completed without error 00% 583 -
# 6 Vendor (0x50) Completed without error 00% 575 -
# 7 Short offline Completed without error 00% 575 -
# 8 Short offline Completed without error 00% 547 -
# 9 Extended offline Completed without error 00% 529 -
#10 Short offline Completed without error 00% 355 -
#11 Short offline Completed without error 00% 355 -
#12 Extended offline Aborted by host 70% 355 -
#13 Short offline Completed without error 00% 319 -
#14 Vendor (0x50) Completed without error 00% 13 -
#15 Short offline Completed without error 00% 13 -
#16 Short offline Completed without error 00% 12 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Kernels used have been from 3.9 to current: Linux echoes 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
Last edited by jesu (2015-05-03 19:42:53)

Something i'd noticed both the first time i was on arch and now i've reinstalled it, was that at first i didn't have this problem. I mean, when Arch was just installed. While i was installing and setting up everything.
Now, i'm not 100% sure about this, but i think problems began when using my current user. Disk is partitioned the following way:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 1000M 0 part
├─sda2 8:2 0 260M 0 part /boot
├─sda3 8:3 0 207,7G 0 part
├─sda4 8:4 0 25G 0 part
├─sda5 8:5 0 14,8G 0 part
├─sda6 8:6 0 80,5G 0 part /
├─sda8 8:8 0 599G 0 part /home
└─sda9 8:9 0 2G 0 part [SWAP]
So, i believe problems, for some reason, are related (and were related), both before and now, to the /home partition, /dev/sda8 in this ocassion.
Because of this, i booted into systemd rescue mode, like root, rw, and unmounted /home partition. Despite root-only limitations, i used the system for a couple of hours, started lxqt, browsed the web mainly, and experienced no problem at all.
Now i booted normally, with my regular user, and these problems are experienced just like before (and almost instantly, like 3 or 5 minutes after starting system use).
dmesg this time showed a some different log, though it's not the first time i see this. I just didn't saved that kind of log before.
[ 653.821719] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6 frozen
[ 653.821726] ata1.00: failed command: READ FPDMA QUEUED
[ 653.821732] ata1.00: cmd 60/08:40:60:25:43/00:00:1b:00:00/40 tag 8 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 653.821735] ata1.00: status: { DRDY }
[ 653.821739] ata1: hard resetting link
[ 659.156760] ata1: link is slow to respond, please be patient (ready=0)
[ 663.851604] ata1: COMRESET failed (errno=-16)
[ 663.851610] ata1: hard resetting link
[ 669.186591] ata1: link is slow to respond, please be patient (ready=0)
[ 673.881456] ata1: COMRESET failed (errno=-16)
[ 673.881462] ata1: hard resetting link
[ 679.216481] ata1: link is slow to respond, please be patient (ready=0)
[ 702.743982] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 703.012578] ata1.00: configured for UDMA/100
[ 703.012584] ata1.00: device reported invalid CHS sector 0
[ 703.012599] ata1: EH complete
[ 714.097642] systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
[ 742.443488] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443494] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x2a 2a 00 28 c3 c6 40 00 00 10 00
[ 742.443497] blk_update_request: I/O error, dev sda, sector 683918912
[ 742.443503] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489866)
[ 742.443506] Buffer I/O error on device sda8, logical block 9323208
[ 742.443508] Buffer I/O error on device sda8, logical block 9323209
[ 742.443515] sd 0:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443518] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 28 c3 c6 80 00 00 10 00
[ 742.443520] blk_update_request: I/O error, dev sda, sector 683918976
[ 742.443522] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489874)
[ 742.443524] Buffer I/O error on device sda8, logical block 9323216
[ 742.443526] Buffer I/O error on device sda8, logical block 9323217
[ 742.443531] sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443534] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 28 c3 c6 d0 00 00 10 00
[ 742.443536] blk_update_request: I/O error, dev sda, sector 683919056
[ 742.443538] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489884)
[ 742.443540] Buffer I/O error on device sda8, logical block 9323226
[ 742.443542] Buffer I/O error on device sda8, logical block 9323227
[ 742.443547] sd 0:0:0:0: [sda] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443549] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 28 c3 c7 10 00 00 10 00
[ 742.443551] blk_update_request: I/O error, dev sda, sector 683919120
[ 742.443553] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489892)
[ 742.443555] Buffer I/O error on device sda8, logical block 9323234
[ 742.443557] Buffer I/O error on device sda8, logical block 9323235
[ 756.187685] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[ 756.187986] systemd[1]: Unit systemd-journald.service entered failed state.
[ 756.188116] systemd[1]: systemd-journald.service failed.
[ 756.188474] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 756.189106] systemd[1]: Stopping Flush Journal to Persistent Storage...
[ 756.189143] systemd[1]: Listening on Journal Audit Socket.
[ 756.189801] systemd[1]: Starting Journal Service...
[ 757.525493] systemd-coredump[1038]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.b8610e85f9074a418534aaee0adbac56.141.1430763073000000.lz4.
[ 758.133944] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 758.503041] systemd[1]: Started Journal Service.
[ 759.180771] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 974.867721] ata1.00: exception Emask 0x0 SAct 0x3f80 SErr 0x0 action 0x6 frozen
[ 974.867732] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867742] ata1.00: cmd 61/08:38:68:d3:c5/00:00:1a:00:00/40 tag 7 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867747] ata1.00: status: { DRDY }
[ 974.867751] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867759] ata1.00: cmd 61/08:40:88:d3:c5/00:00:1a:00:00/40 tag 8 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867763] ata1.00: status: { DRDY }
[ 974.867767] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867774] ata1.00: cmd 61/08:48:a0:d3:c5/00:00:1a:00:00/40 tag 9 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867778] ata1.00: status: { DRDY }
[ 974.867781] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867789] ata1.00: cmd 61/20:50:c0:d3:c5/00:00:1a:00:00/40 tag 10 ncq 16384 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867793] ata1.00: status: { DRDY }
[ 974.867796] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867803] ata1.00: cmd 61/10:58:f0:d3:c5/00:00:1a:00:00/40 tag 11 ncq 8192 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867807] ata1.00: status: { DRDY }
[ 974.867810] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867817] ata1.00: cmd 61/08:60:10:d4:c5/00:00:1a:00:00/40 tag 12 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867821] ata1.00: status: { DRDY }
[ 974.867824] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867831] ata1.00: cmd 61/18:68:28:d4:c5/00:00:1a:00:00/40 tag 13 ncq 12288 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867835] ata1.00: status: { DRDY }
[ 974.867841] ata1: hard resetting link
[ 980.202774] ata1: link is slow to respond, please be patient (ready=0)
[ 984.900902] ata1: COMRESET failed (errno=-16)
[ 984.900908] ata1: hard resetting link
[ 990.236024] ata1: link is slow to respond, please be patient (ready=0)
[ 994.930829] ata1: COMRESET failed (errno=-16)
[ 994.930836] ata1: hard resetting link
[ 996.798104] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 997.014012] ata1.00: configured for UDMA/100
[ 997.014020] ata1.00: device reported invalid CHS sector 0
[ 997.014023] ata1.00: device reported invalid CHS sector 0
[ 997.014025] ata1.00: device reported invalid CHS sector 0
[ 997.014026] ata1.00: device reported invalid CHS sector 0
[ 997.014028] ata1.00: device reported invalid CHS sector 0
[ 997.014030] ata1.00: device reported invalid CHS sector 0
[ 997.014031] ata1.00: device reported invalid CHS sector 0
[ 997.014065] ata1: EH complete
There are some sda8 (home) related messages. I also found these messages first time Arch was installed (i think also related to home partition).
root and home partitions are both ext4.

P67a-GD65 System Freezes and Recovers During 3D gaming and Online Video

The Problem:
Temporary system freeze with audio stutter. The system recovers 30sec - 2min later.
Key presses made during freeze will execute after system recovers (ctrl+alt+delete for example)
Usually, but not always, I see an error message in the system tray and I do NOT experience bsod.
This happens seemingly at random from 3D accelerated applications, and web browsing. Games such as BF3 (moderate), WoW (seldom), Planetside 2 (frequently), Minecraft (seldom), Hawken (seldom), etc.
Also happens frequently in both Internet Explorer 9/10, Firefox, Chrome, and Steam store browser. Typically when watching steaming video (youtube, HULU, flow player, etc)
but Pandora audio streaming also seems to create the conditions where this happens.
Error Message:
"Display driver stopped responding and has recovered
Display driver NVIDIA Windows Kernal Mode Driver 314.07 stopped
responding and has successfully recovered"
The problem also shows up in the Windows reliability history with the following data:
Source
Windows
Summary
Video hardware error
Date
‎3/‎6/‎2013 9:11 PM
Status
Not reported
Description
A problem with your video hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name:   LiveKernelEvent
OS Version:   6.1.7601.2.1.0.768.3
Locale ID:   1033
Files that help describe the problem
WD-20130306-2010.dmp
sysdata.xml
WERInternalMetadata.xml
Extra information about the problem
BCCode:   117
BCP1:   FFFFFA8011E0C4E0
BCP2:   FFFFF8800654A198
BCP3:   0000000000000000
BCP4:   0000000000000000
OS Version:   6_1_7601
Service Pack:   1_0
Product:   768_1
My System Hardware:
CPU: Intel i7 2600k @ 4.5ghz
Motherboard: MSI p67a-gd65 (B3 stepping)
Memory: G.SKILL Sniper 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600
GPU: Originally MSI 6950 2GB. Replaced with EVGA 670 FTW 2GB.
PSU: CORSAIR HX Series HX850 850W
HDD: 3x Western Digital WD RE4 WD5003ABYX 500GB in Raid 0
OS: Windows 7 Home Premium SP1 with all updates
Case/Cooling: Silverstone Raven 2E with Thermalright silver arrow cpu heatsink
What I've tried:
Updated all motherboard drivers and bios (4.3) to current versions (no improvement)
Updated display drivers (in safe mode with driver sweeper. No improvement)
Updated Realtek Audio drivers for onboard sound (no improvement)
Updated Intel Rapid Storage drivers (no improvment)
Cleared CMOS and tested system at default settings with no overlock (no improvement)
Flashed 6950 back to 6950 stock bios and removed overclock (no improvement)
Replaced old 6950 with new GTX 670 (problem still occurs in the same exact way)
Tried GPU in 2nd PCIe slot. No improvement.
Checked GPU Temps. GTX 670 fan profile in EVGA Precision X set to keep temp below 70 degrees Celcius. Card maxes at 60 degrees under heavy gaming load.
Complete reformat of raid array with fresh install of Windows (4 different times) Seemed to help for a few days, then freezes came back
Ran OCCT and Prime 95 Torture tests separately for a few hours at stock and OC settings. System stable with core temps of high 50's overclocked, and low 40's stock.
Ran Memtest86 for 10 hours with zero errors.
Used digital multimeter to test 12v rail on PSU. Noted solid 12v reported. Didn't test other rails.
Unplugged PSU cables from motherboard and reattached firmly
Ran HD Tune and Data Life Guard Tools for error checking on hard disks. Zero errors found.
Disabled Windows Aero (no improvement)
Updated Adobe Flash Player to latest setting (no improvement)
Removed Adobe Flash Player (no improvement)
Turned off Adobe Flash hardware acceleration (no improvement)
*EDIT: Forgot that I also adjusted Nvidia driver profiles for apps that have frozen to include power preference to max performance
All of my hardware with the exception of the new 670 was purchased and configured back in February of 2011. This problem first occured in BF3 multiplayer sometime in early 2012,
and has gradually been happening more frequently. Web searches found many individuals with this error, but the solutions are all over the map, and I've tried just about everything that I've found.
I think I've narrowed the problem down to the motherboard, but I just can't find a clear answer or solution. Maybe it's the raid array? I really thought replacing the GPU would solve my trouble here
and I was...NOT happy when it happened again with the new 670 that I scored for $250 after amazon gift cards. I typically get kicked/disconnected during online game play when this happens and I'm ready to be done with it. I was hoping to fix the issue without needing to buy new hardware, but I don't see any other way at this point.
My patience runs thin. Please help!

Quote from: Froggy Gremlin on 11-March-13, 15:28:36
Might want to ask for the special archive to return the mainboard to pre-Ivy support UEFI/BIOS and then test again with everything set to auto/stock/default.
Already tested that before updating to 4.3. I started having the problem on 1.8, then 1.J0, then 4.3.
Quote from: Bernhard on 11-March-13, 15:30:29
Just a shot in the dark.
The length of time that your CPU has been running at the OC could have accelerated the eventual degradation.
Have you tested your CPU in another board or do you have access to a "known good" CPU to test in your system ?
I do not have another 1155 lga board to test the cpu in unfortunately, hence the CPU stress testing. Based upon previous experiences with multiple overclocked systems that I've run at much more aggressive overclocks, I don't believe I'm seeing a processor failure, though I can't rule out the possibility.
Quote from: xmad on 11-March-13, 23:26:01
Quite a few components can cause this.
Do you have a friend that could lend you a psu to test? A weak of failing PSU can often be the cause of something like this?
No I don't have another PSU to test. I did use a digital multimeter to test the 12v rail, as well as the motherboard contacts for testing voltage to the cpu and system They were all right in line with what I'm seeing reported in the bios. I did not test these contacts while the system was under load however, so I may need to do it again.

Bluetooth is neither detected nor working. In the system preferences under BLUETOOTH header it says "No information found". Bluetooth icon is not appearing on desktop either. Please help.

Bluetooth is neither detected nor working. In the system preferences under BLUETOOTH header it says "No information found". Bluetooth icon is not appearing on desktop either. Please help.

Yes....It happens all the time. I also erased my HD and installed Snow Leopard but with no success. Tried lots of REBOOTING but nothing worked for me.As I have already installed the new OSX I think there is no need to go through the below procedure. What do you suggest?
Before you go through the ritual of reinstalling the entire system just try to do a "factory reset" of your bluetooth environment. To do this you need to run the Bluetooth Explorer which is a utility installed as part of XCode.
1. Launch Bluetooth Explorer.
2. Select the "Modify Software & Device Configuration" from the Utilities menu.
3. Keep the first 4 checkboxes checked (one will say "Full factory reset").
4. Click "Perform actions" button (lower right of window).
5. Reboot (possibly the Reboot NOW button will work, if not just do a normal reboot).
Hopefully that will clear your problem(s) so you can re-pair your bluetooth devices.
Good luck.

Trying to set up iCloud onmy iMac and the iCloud icon does not appear in System Preferences under "Internet

I am trying to set up iCloud on my iMac and the iCloud icon does not appear in system preferences under "internet & wireless". How do I proceed. I have already set it up on my iPad & iPhone.

You have to upgrade to Lion for the iCloud preferences to be available.

When i plug in my iPad2, iPhoto comes on not iTunes. I see iPad in system profiler under USB. I have reset, removed and re-downloaded iTunes. When I download iTunes it works until the next time i plug in the iPad2 and then the same thing all over.

When i plug in my iPad2, iPhoto comes on not iTunes. I see iPad in system profiler under USB. I have reset, removed and re-downloaded iTunes. When I download iTunes it works until the next time i plug in the iPad2 and then the same thing all over.

Go through this support doc:
OS: Device not recognised in iTunes
Windows: http://support.apple.com/kb/TS1538

Hi, I am using 10.7.4 and when I use Comand R my system freezes up. I can not repair my startup disk. any ideas?

I am using OnyX and it says I need to repair my startup Disk. When I do Comm +R my system freezes up and I can not do anything. Is there a way to get past this?

If you have a TM backup on an external drive, restart the computer and hold down the option key. You will get a selection of drives. The TM drive has a recovery drive also. I think it will be listed as Mac OSX. Select it and try booting from it. Your internal drive might be bad and not allowing you to start from that recovery drive.

Problems with SpeedStep and Windows Power Management: SYSTEM FREEZES!

I am running an E6600 on my MSI 975X PUE-Mainboard @ 2,4 GHz. I am experiencing a strange problem that seems to be related to EIST and/or Windows Power Management:
As soon as I set Windows Power Management to "Presentation" or any other mode that lets Windows throttle the CPU frequency the system freezes randomly: no bluescreens, no error messages...the only option is to hit the restart button...
However, if the Windows Power Management Option is set to "Desktop" the system runs just fine!
Has anyone else experienced similar problems?
Any suggestions?

@Vaniireg
Thanks for your reply, but I cannot agree. Windows Power Management is needed in order to use Speedstep:
http://www.intel.com/cd/channel/reseller/asmo-na/eng/203838.htm
Intel clearly states that:
"An OS that supports Enhanced Intel SpeedStep technology is required. Current supporting OSs include:, Microsoft Windows* XP SP2 includes native support for Enhanced Intel SpeedStep® technology."
and further:
"Finally Enhanced Intel SpeedStep technology must be turned on in the OS. Currently, for Windows* XP SP2 operating systems Enhanced Intel SpeedStep technology by default is off. To turn it on do the following: Under Control Panel – open Power Options Under the Power Schemes pull down menu To turn Enhanced Intel SpeedStep technology ON select, “Minimal Power Management,” power scheme. To turn Enhanced Intel SpeedStep technology OFF select, “Always On,” power scheme."
If I select the "Minimal Power Management" power scheme, the CPU frequency will drop to about 1,6 GHz and the Voltage (CPU-Z) to 1,136-1,144 V. Whenever I do that the system will eventuelly freeze. Skipping through a video file in Media Player Classic is sometimes enough to cause the system to hang.
If I select the "Always On" power scheme the system will run stable, no freezes will occur, but the CPU will ALWAYS run @2,4 GHz and the voltage WILL NOT be reduced to 1.14 V.
@batcook09:
Unfortunately, a clean re-install of Windows XP Pro did not take care of my problem. I've already tried that. The system is not overclocked and is running with default settings. Speedstep is enabled.
It is interesting to notice, that Dual Core Center always causes my system to freeze, even though Windows Power Management Options are set to "Always On". I read a lot of bad things about this program and that is one more reason for me to avoid using it.
Well, I have forwarded my problem to Intel and MSI Support, maybe they will come up with any solution.
Until then, further suggestions are very welcome...

The system freezes a lot and dmesg gives an error in Nvidia drivers

I faced constant system freezing in Ubuntu under both Unity and Gnome shell. So I came to Arch. In Arch also im facing the same issue. I tried many things in these forums but nothing helped. Please help me. The system hangs constantly and the mouse barely moves. When I press ctrl+alt+f2 it takes several minutes to go to the terminal and then I can reboot. Please help. Here's the output of dmesg :
[ 1.826414] systemd[1]: Starting Login Prompts.
[ 1.826435] systemd[1]: Reached target Login Prompts.
[ 1.826449] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 1.826519] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 1.826533] systemd[1]: Starting Remote File Systems.
[ 1.826547] systemd[1]: Reached target Remote File Systems.
[ 1.826572] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 1.826666] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 1.826685] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 1.826720] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 1.826732] systemd[1]: Starting Paths.
[ 1.826744] systemd[1]: Reached target Paths.
[ 1.826755] systemd[1]: Starting Encrypted Volumes.
[ 1.826767] systemd[1]: Reached target Encrypted Volumes.
[ 1.826780] systemd[1]: Expecting device dev-disk-by\x2duuid-c11bdfb5\x2db15e\x2d473a\x2d8cf8\x2d020715616bde.device...
[ 1.826793] systemd[1]: Expecting device dev-disk-by\x2duuid-8ada8f05\x2d1853\x2d45c7\x2da302\x2d7d11869fd5bd.device...
[ 1.826805] systemd[1]: Expecting device dev-disk-by\x2duuid-E8D0\x2d38A9.device...
[ 1.826816] systemd[1]: Starting Root Slice.
[ 1.834477] systemd[1]: Created slice Root Slice.
[ 1.834493] systemd[1]: Starting User and Session Slice.
[ 1.834670] systemd[1]: Created slice User and Session Slice.
[ 1.834684] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 1.834712] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 1.834724] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ 1.834752] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 1.834764] systemd[1]: Starting Delayed Shutdown Socket.
[ 1.834790] systemd[1]: Listening on Delayed Shutdown Socket.
[ 1.834805] systemd[1]: Starting udev Control Socket.
[ 1.834829] systemd[1]: Listening on udev Control Socket.
[ 1.834843] systemd[1]: Starting udev Kernel Socket.
[ 1.834868] systemd[1]: Listening on udev Kernel Socket.
[ 1.834880] systemd[1]: Starting LVM2 metadata daemon socket.
[ 1.834907] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 1.834921] systemd[1]: Starting Journal Socket.
[ 1.834967] systemd[1]: Listening on Journal Socket.
[ 1.834986] systemd[1]: Starting System Slice.
[ 1.835160] systemd[1]: Created slice System Slice.
[ 1.835179] systemd[1]: Started File System Check on Root Device.
[ 1.835191] systemd[1]: Starting system-systemd\x2dfsck.slice.
[ 1.835379] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[ 1.835393] systemd[1]: Mounting Temporary Directory...
[ 1.835993] systemd[1]: Starting system-getty.slice.
[ 1.836195] systemd[1]: Created slice system-getty.slice.
[ 1.837686] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[ 1.838280] systemd[1]: Starting udev Coldplug all Devices...
[ 1.838810] systemd[1]: Mounting Huge Pages File System...
[ 1.839349] systemd[1]: Mounting POSIX Message Queue File System...
[ 1.841338] systemd[1]: Starting Apply Kernel Variables...
[ 1.841909] systemd[1]: Starting Setup Virtual Console...
[ 1.842552] systemd[1]: Mounting Debug File System...
[ 1.844757] systemd[1]: Started Load Kernel Modules.
[ 1.844789] systemd[1]: Mounting Configuration File System...
[ 1.845225] systemd[1]: Mounted FUSE Control File System.
[ 1.846612] systemd[1]: Starting Set Up Additional Binary Formats...
[ 1.847351] systemd[1]: Starting Journal Service...
[ 1.848175] systemd[1]: Started Journal Service.
[ 1.861600] EXT4-fs (sda6): re-mounted. Opts: data=ordered
[ 1.865901] systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 141 (systemd-binfmt)
[ 1.919562] systemd-udevd[165]: starting version 212
[ 1.974653] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 1.981863] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
[ 1.981873] ACPI: Power Button [PWRB]
[ 1.981971] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[ 1.981976] ACPI: Power Button [PWRF]
[ 1.983340] parport_pc 00:08: reported by Plug and Play ACPI
[ 1.983390] parport0: PC-style at 0x378, irq 5 [PCSPP]
[ 1.983777] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 1.986033] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.986096] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.990191] mei_me 0000:00:16.0: irq 43 for MSI/MSI-X
[ 1.990406] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 1.990820] acpi device:43: registered as cooling_device4
[ 1.990950] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
[ 1.991137] [drm] Initialized drm 1.1.0 20060810
[ 1.993033] wmi: Mapper loaded
[ 2.014083] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20131218/utaddress-258)
[ 2.014092] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.014097] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
[ 2.014103] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.014105] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
[ 2.014110] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.014112] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 2.016081] thermal LNXTHERM:00: registered as thermal_zone0
[ 2.016084] ACPI: Thermal Zone [TZ00] (28 C)
[ 2.016323] thermal LNXTHERM:01: registered as thermal_zone1
[ 2.016325] ACPI: Thermal Zone [TZ01] (30 C)
[ 2.016391] ACPI: Fan [FAN0] (off)
[ 2.016435] ACPI: Fan [FAN1] (off)
[ 2.016476] ACPI: Fan [FAN2] (off)
[ 2.016517] ACPI: Fan [FAN3] (off)
[ 2.016555] ACPI: Fan [FAN4] (off)
[ 2.027162] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20131218/utaddress-258)
[ 2.027171] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.027373] input: PC Speaker as /devices/platform/pcspkr/input/input6
[ 2.036735] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 2.036746] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 2.037012] r8169 0000:03:00.0: irq 44 for MSI/MSI-X
[ 2.037275] r8169 0000:03:00.0 eth0: RTL8168f/8111f at 0xffffc900059b6000, 60:a4:4c:3d:76:fa, XID 08000800 IRQ 44
[ 2.037279] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 2.041327] snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
[ 2.042605] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
[ 2.042682] snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
[ 2.042728] hda_intel: Disabling MSI
[ 2.042735] hda-intel 0000:01:00.1: Handle VGA-switcheroo audio client
[ 2.047515] mousedev: PS/2 mouse device common for all mice
[ 2.058597] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059406] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059423] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059438] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059519] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 2.070989] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 2.071058] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 2.071112] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 2.071164] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 2.071216] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 2.071268] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 2.096085] kvm: disabled by bios
[ 2.113324] ppdev: user-space parallel port driver
[ 2.118467] iTCO_vendor_support: vendor-support=0
[ 2.119501] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[ 2.119535] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460)
[ 2.120228] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 2.122797] asus_wmi: ASUS WMI generic driver loaded
[ 2.123577] asus_wmi: Initialization: 0x0
[ 2.123593] asus_wmi: BIOS WMI version: 0.9
[ 2.123620] asus_wmi: SFUN value: 0x0
[ 2.123943] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input14
[ 2.124655] asus_wmi: Backlight controlled by ACPI video driver
[ 2.139754] systemd-udevd[172]: renamed network interface eth0 to enp3s0
[ 2.159402] Adding 4882428k swap on /dev/sdb6. Priority:-1 extents:1 across:4882428k FS
[ 2.173202] nvidia: module license 'NVIDIA' taints kernel.
[ 2.173206] Disabling lock debugging due to kernel taint
[ 2.179335] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 2.179471] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 0
[ 2.179477] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 337.12 Fri Apr 4 14:51:15 PDT 2014
[ 2.292323] Switched to clocksource tsc
[ 2.369970] EXT4-fs (sdb8): mounted filesystem with ordered data mode. Opts: data=ordered
[ 2.380040] systemd-journald[142]: Received request to flush runtime journal from PID 1
[ 2.398821] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
[ 2.399044] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
[ 2.399180] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
[ 2.704632] r8169 0000:03:00.0 enp3s0: link down
[ 2.704667] r8169 0000:03:00.0 enp3s0: link down
[ 2.704684] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 2.889853] nvidia 0000:01:00.0: irq 46 for MSI/MSI-X
[ 3.436679] NVRM: Your system is not currently configured to drive a VGA console
[ 3.436683] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 3.436686] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 3.436688] NVRM: drivers including, but not limited to, vesafb, may result in
[ 3.436690] NVRM: corruption and stability problems, and is not supported.
[ 4.318649] fuse init (API version 7.22)
[ 5.160446] r8169 0000:03:00.0 enp3s0: link up
[ 5.160458] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 18.971615] NVRM: GPU at 0000:01:00: GPU-3840b413-5a51-9da2-923a-a4cbb4a5005e
[ 18.971628] NVRM: Xid (0000:01:00): 13, 0003 00000000 0000a097 00002410 00000030 00000000

ondoho wrote:
archlinux comes as a barebones system - i guess you installed some sort of desktop environment on top of it.
if you installed the same (unity or gnome shell) that will probably not solve your problem.
if you managed to set up an arch system with a gui, you should be able to provide us with more relevant information, so we can start troubleshooting.
off the top of my head (or hat?) i'd say your hardware can't keep up with a full-fledged desktop environment and you should choose something more lightweight. but that's just guessing.
I tried both gnome and unity. My GPU is Nvidia GT640 2GB DDR3, Motherboard Asus p8b75m, Cpu i3-2100. Ram 8 GB. 64GB SSD (Root is on it), 1 TB HDD (Home is on it). I don'tthink my system can't handle a full DE.

Help!! My iMac 24 screen is going bonkers, then system freezes...

I have been having a problem that is not application-specific, and not Lion specific. This only happens on my 2009 iMac 24 running Lion 10.7.4. (I also run Lion on my 2011 MBP and have not had this problem.) It doesn't matter whether I'm in iTunes, Safari, Logic, Pages... running applications alone or in combination.It doesn't happen right away. It's usually after I've been active on the computer for at least an hour. I will try to describe it the best way I can:
1. I could be browsing Safari, for instance. I'll notice that a small section of my desktop starts "growing" red, green, and/or blue pixels. If left untouched, the pixels overtake about 70% of the display until the computer freezes. Now, if i click anywhere on my screen -- in Safari or on the desktop -- whatever the mouse is pointing at will redraw itself. Meanwhile, the screen starts blinking rapidly and basically, has a tantrumI can't Force Quit, Restart, Shut Down, or any other activity. The only solution is to power it down using the power switch.
2. I'm working on music in Logic Pro. When I have Logic running, it usually spans the entire display. Within the Logic screen I'll see a small section of these red, green, and/or blue pixels. (Well by now, I know what's coming so I immediately save my work before the system freezes.) I quit out of Logic, but the pixels continue to take over my desktop. If left on it's own it starts going berserk as described above. Eventually the system freezes and I have to power down.
This started happening last month. Two things happend last month: (a) I switched my internet service and combined my internet connection with my land line. I had previously been using a dedicated line for internet. (b) My service agreement expired on the iMac... go figure!
If anyone else has experienced this and can offer some solution or workaround it would be greatly appreciated. This is scaring the heck out of me so I am now backing up my backup of my backup. I'm starting to wonder if this is actually Windows somehow cleverly disguised as a Mac.
Gigi

Hi Gigi, not the problem but do this firstanyway...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
If 10.7.0 or later...
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partitiion & use Disk Utility from there.
Then I'd get Lion Cache Cleaner & clear the caches...
http://www.northernsoftworks.com/lioncachecleaner.html
Have you blown the dust out lately?
Get Temperature Monitor to see if it's heat related...
http://www.macupdate.com/info.php/id/12381/temperature-monitor
iStat Menus...
http://bjango.com/mac/istatmenus/
And/or iStat Pro...
http://www.islayer.com/apps/istatpro/
One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
Reboot, test again.
If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed.
Check the System Preferences>Other Row, for 3rd party Pref Panes.

Why does my entire system freeze shortly after I open iTunes?

Hi!
So I have OS X Lion installed on my new iMac 21.5" desktop. I don't know if I'm having an OS problem or an App problem here. Everything seems to run fine (a little sluggish at times though) UNTIL I use iTunes. Within a couple minutes of having iTunes open, the entire system freezes up. I can't do anything except for move the cursor around. If I wait around, every 45 seconds or so, it unfreezes itself only for a brief second or two and then freezes again. After waiting around for several minutes of it doing this, I can eventually manuever around to force quit iTunes.. OR I can simply turn the power off from the back of the iMac and restart... Either way, I haven't even been able to submit crashes to Apple to alert them of a problem. Once iTunes has been force quit, everything runs fine again. I have had this happen at least 15 - 20 times already and am very frustrated! Does anyone have a good idea what's going on here? Any suggestions of what I should do? I haven't contacted Apple about this problem yet.
Also, I've experienced this iTunes problem with both a small library (fewer than 100 songs), and with a very large library (1000s of songs). I usually won't have more than 4 apps opened at one time anyway as to not over burden my system.. So I don't believe I'm having a memory issue here. I've had this problem happen when my iPod was syncing, and when it was not even connected or turned on. I've tried several things including 1) reinstalling Lion, 2) resetting my iPod, 3) having all other items disconnected from my iMac, 4) I verified permissions and performed a disk repair in Disk Utility 5) turned Time Machine off & on... I haven't noticed problems with other applications.. other than once my DVD player froze up for a few seconds (along with the rest of my system) while on the dvd main menu. I really don't use many applications often and Lion is still new to me. So I'm not aware of having problems with other applications yet. Thanks.

Flash Player
Flash Player may cause higher CPU activity when playing a YouTube video.
Possibly related to disabled hardware acceleration.
http://kb2.adobe.com/cps/905/cpsid_90508.html#main_Flash_Player
No Lion verson - http://get.adobe.com/flashplayer/otherversions/
How to install the Java runtime (JRE) | Mac OS 10.7 Lion
http://kb2.adobe.com/cps/909/cpsid_90908.html
You'll need this - Java for OS X Lion

System Freeze under 10.7 (not video related..)

Similar Messages

Maybe you are looking for