VISA-relat​ed LV freeze

I'm having an issue with LabVIEW crashing when opening or running a VI that has a VISA resource constant on the block diagram.  Once this problem occurs, even rebooting the OS does not fix the problem.  It is not until I reinstall the VISA drivers that the problem is fixed, although the fix is only short-term.  I've isolated the problem to where I can open up a new VI, drop a VISA resource constant on the block diagram, and crash LabVIEW.
I am using a USB hub as well as USB-to-serial devices.
Here's what I'm running:
LV 7.1.1
Win XP SP3
NI-VISA 4.5

Have you tried this?
The problem with LabVIEW freezing is probably due to network problems and perhaps some firewall issues. This is a known issue and a workaround to get a working solution is to use a string constant or control instead of a VISA resource name constant or control.
The resource name should adhere to the following format: GPIBx::y::INSTR, where x is the GPIB Interface Number, and y is the Primary Address.
You should then be able to perform basic VISA write and read functions, as well as other functions such as the lock asynchronous and unlock.
National Instruments

Similar Messages

  • VISA Ressource Name Constant freezes Labview

    I have a compelte new project.
    If I drop a VISA Ressource Name Constant from the I/O Pannel onto the work
    area, my compelte LabVIew freezes.
    This happens only with the Hardware attached.
    The VISA interactive control works fine !
    Does anybody have a clue why ? Is the access and resonse times to long ? Is
    it a IRQ or Labview peoblem ? Why VISA interactive control works without
    problems ?
    Please Help !
    Thanks for your effort !
    1. viGetAttribute (0x0015D988,0x3FFF018F,VI_TRUE)
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:29:58.774 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    2. viGetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:29:58.774 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    3. viSetAttribute (0x0015D988,0x3FFF0190,2 (0x2))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:29:58.774 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    4. viFindRsrc (0x0015D988,"?*INSTR",0x0015D9C8,4 (0x4),"COM1")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:29:58.774 Call Duration: 00:00:09.114
    Status: 0 (VI_SUCCESS)
    5. viFindNext (0x0015D9C8,"COM3")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:07.888 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    6. viFindNext (0x0015D9C8,"LPT1")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:07.888 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    7. viFindNext (0x0015D9C8,"GPIB0::5::INSTR")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:07.888 Call Duration: 00:00:00.010
    Status: 0 (VI_SUCCESS)
    8. viClose (0x0015D9C8)
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:07.898 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    9. viSetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:07.898 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    10. viGetAttribute (0x0015D988,0x3FFF018F,VI_TRUE)
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:07.898 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    11. viGetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:07.898 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    12. viSetAttribute (0x0015D988,0x3FFF0190,2 (0x2))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:07.898 Call Duration: 00:00:00.010
    Status: 0 (VI_SUCCESS)
    13. viFindRsrc (0x0015D988,"?*INSTR",0x0015D9C8,4 (0x4),"COM1")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:07.908 Call Duration: 00:00:09.063
    Status: 0 (VI_SUCCESS)
    14. viFindNext (0x0015D9C8,"COM3")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:16.971 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    15. viFindNext (0x0015D9C8,"LPT1")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:16.971 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    16. viFindNext (0x0015D9C8,"GPIB0::5::INSTR")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:16.971 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    17. viClose (0x0015D9C8)
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:16.971 Call Duration: 00:00:00.010
    Status: 0 (VI_SUCCESS)
    18. viSetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:16.981 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    19. viGetAttribute (0x0015D988,0x3FFF018F,VI_TRUE)
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:16.991 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    20. viGetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:16.991 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    21. viSetAttribute (0x0015D988,0x3FFF0190,2 (0x2))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:16.991 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    22. viFindRsrc (0x0015D988,"?*INSTR",0x0015D9C8,4 (0x4),"COM1")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:16.991 Call Duration: 00:00:09.053
    Status: 0 (VI_SUCCESS)
    23. viFindNext (0x0015D9C8,"COM3")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:26.044 Call Duration: 00:00:00.010
    Status: 0 (VI_SUCCESS)
    24. viFindNext (0x0015D9C8,"LPT1")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:26.054 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    25. viFindNext (0x0015D9C8,"GPIB0::5::INSTR")
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:26.054 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    26. viClose (0x0015D9C8)
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:26.054 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    27. viSetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:26.054 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    28. viGetAttribute (0x0015D988,0x3FFF018F,VI_TRUE)
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:26.054 Call Duration: 00:00:00.010
    Status: 0 (VI_SUCCESS)
    29. viGetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:26.064 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    30. viSetAttribute (0x0015D988,0x3FFF0190,2 (0x2))
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:26.064 Call Duration: 00:00:00.000
    Status: 0 (VI_SUCCESS)
    31. viFindRsrc (0x0015D988,"?*INSTR",0x0012F128,0x0012F130,0x0012F01C)
    Process ID: 0x000003F8 Thread ID: 0x000005A0
    Start Time: 11:30:26.064
    Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

    Sascha:
    NI-VISA 2.x has a couple of entries in the visaconf.ini file that we have found occasionally get into a weird state. Look in the [VISA-CONFIG] section for lines that start with "RefreshFindList" and "AlwaysRefresh". Both of these should be set to 0. If they happen to be set to 1, you can manually set them back to 0.
    This would cause a symptom similar to what you describe, where LabVIEW continually polls NI-VISA and thinks it needs to continually refresh its list, which it does by calling viFindRsrc. This seemingly infinite loop continues as long as a VISA refnum is visible, on either the front panel or block diagram.
    This has been fixed for the upcoming version, NI-VISA 3.0.
    Dan Mondrik
    Senior Software Engineer, NI-VISA
    National In
    struments

  • 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.

  • 1Ghz TiBook - Random freezing. Logic board fault?

    Hi all,
    perhaps one of you might be able to help troubleshoot this, because it's seriously driving me up the wall! I bought a used 1Ghz Titanium (DVI) recently and I'm finding that it freezes randomly when in use, requiring a comand+control restart. I've almost always experienced it in Safari, but also once in Entourage, illustrator and also in MacOS 9.2.2 Finder. Essentially what happens is that the cursor freezes and the powerbook no longer responds to keystrokes or trackpad input. I've tried an external mouse but that doesn't fix things either. The display is still lit but any moving graphics/video are frozen on screen. If music is playing in iTunes it cuts out leaving the last second of sound looping. Shortly after freezing I sometimes hear the fan come on, so perhaps there is a part of the powerbook still working after the crash (?). Also, I can select/deselect the caps lock and number lock keys and the green LEDs switch on and off, so perhaps it's not completely dead? The moment of the freeze almost always coincides with a mouse/trackpad click on the scroll bar, menu, safari menu bar, dock icon, form submit button, etc. It will on occasion freeze overnight when there is no mousing at all. generally though I can leave it playing iTunes all night and when I start using it in the morning it'll freeze when I collect my email or something.
    the frequency of the freezing is semi-random; I have gone for roughly 48hrs of constant use without incident and then suddenly 2-4 crashes in short succession (ie, within about 10 mins of each other). Generally it freezes about 2 or 3 times a day. They do often come regular clumps.
    Initially I thought it was Safari, or the OSX 10.4.5 installation that came with the powerbook, but I removed the entire HD and replaced it with the working drive from my Pismo and had exactly the same symptoms. Realising it was hardware related I did the usual drill of swapping, re-seating and removing ram, etc - but no dice. I've run Apple Hardware Test in a couple of 18hr loops but they return a glowing report about my hardware! techtool does likewise. I took it to the new Apple Centre in London where they ran their (apparently more powerful) AHT CD for 73 loops over 3 hours. Again, no reported errors!
    I've read the long 'trackpad cable thread', and opened my powerbook to see if pinching the cable is an issue, but it's clearly not. I have lots of clearance around my trackpad cable and it's not in contact with any part of the case. I've even applied pressure all around the palmrest and the outside of my powerbook case hoping to induce a freeze but that doesn't seem to do anything.
    What should I do next? when the powerbook works it's fine, but I'm at a loss as to what's causing the freezing. As a performing musician playing to hundreds of people a fault like this renders my powerbook useless since it must be absolutely stable and bullet-proof on stage.
    thanks for reading and I'm grateful for any advice.
    TiBook 1Ghz (DVI)   Mac OS X (10.3.9)   9600/350

    hi there,
    thanks for the welcome. i've been visiting here for a while and find all the posts very useful.
    the trackpad issue is an odd one; my powerbook doesn't seem to show the classic symptoms of weird startup chimes or jerky cursor movement, etc in the other thread. I nonetheless opened up the powerbook praying that I'd find a pinched cable since that would have been so easy to fix. unfortunately there's nothing about it that looks problematic.
    I had also suspected heat as being an issue and searched this forum a couple of times for related posts, but couldn't find anything. When I opened the powerbook i checked the fans for obstructions and blew out any dust i could see (i didn't have compressed gas). Again, they looked fairly normal to me - i didn't spot anything obvious like a trapped cable. As far as I can tell all 3 fans come on OK. First one of them and then after some time another one or two turn on after the powerbook has been running a while. (Is it actually possible to determine whether or not they're all working?)
    It's difficult to say whether heat is actually related to the freezing. certainly I often notice the fans come on before a freeze, or right afterwards, but just as many times that's not the case. what is consistant however is that the freeze occurs the instance a cursor selection is clicked.
    would you say this would be resolved by a logic board swap, because I know someone selling one. On the other hand, I'm a little confused by all the error-free reports I get when I run the Apple Hardware Test for extened loops.
    thanks again for your help!

  • Labview freeze when accessing a custom menu with data on the clipboard

    This one has got me stumped:  When selecting a custom menu item with data on the clipboard the GUI freezes.  Freezes are longer for more data and longer for older versions of Labview.  I wrote the test code, attached, but the example "Menu Selection Demo.vi" shows the same behavior.
    Running Labview 2011 here are some freeze delays for my laptop (a bit slower machine) with various amounts of text data on the clipboard:
    Clipboard size        Delay
    1.3MB                   2.1 sec
    2.6MB                   4.9 sec
    3.8MB                   17.2 sec
    14MB                    253.3 sec
    The delay appears to be non-linear.  A doubling of the clipboard data size more than doubles the delay and a tripling of the clipboard data size produces a delay of almost 10X!  Things are also much, much worse on my ancient version 8.2.1 (over a 40 second freeze for 1.3MB and it goes up from there).
    Note that the freeze also occurs on programs with a custom menu when exiting.  This would seem to suggest it might have something to do with the timeout, but why timeout should vary with clipboard size and not with the value wired to it makes this feel even more like a bug in the custom menu functionality.
    This seems to be related to known issues in Labview 2011 #39604 49UBP4LE (http://www.ni.com/white-paper/13168/en#39604_by_Da​te) that was first reported in version 8.2.1.  This known issue relates to Labview freezing when large amounts of data are copied from Labview to the clipboard.  No fix has been implemented since this was originally reported in 2007.
    This freeze also occurs when shortcuts to menu items (such as Ctrl + L) are used when large amounts of data are on the clip board.
    Thus far this has been 100% repeatable and I have not been able to find a way around it.  I also haven't found anything else similar on the forums or on the web.  It appears to be a GUI freeze with Labview still running in the background, which is also odd.
    My work-arounds at this point are either to not use the clipboard (bad), programatically clear the clipboard several times each second (worse) or remove all custom menu functionality and replace those functions with onscreen controls.  So, for now, I'm removing custom menu items because my users need the clipboard and I can't have massive delays making my data acquisition code look crashed.
    Any ideas would be helpful.  This one has me scratching my head...
    Attachments:
    Menu_Clipboard_Lv2011.vi ‏17 KB

    Well, doing Microsoft Word, Excel and what else on a computer that is used to run an important production test, is a very bad idea. There is no way that you can guarantee, that one of these applications is not causing some interruption to the currently running time critical task. Word and Excel and just about any other computer application can crash, lock up the computer or eat your breakfast while you are doing seemingly harmless things.
    The issue with the clipboard in LabVIEW is indeed a problem that exists for a long time and I hope they fix it sometime, but the fact remains, that you should NEVER use a computer for other tasks while you run a test or other manufacturing related application on it, when a failure of that application can cost you more than a few pennies.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Need help identifying problem (lockup/freezing in Warcraft III & CS)

    my macbook pro:
    Model Name: MacBook Pro 15"
    Model Identifier: MacBookPro1,1
    Processor Name: Intel Core Duo
    Processor Speed: 2 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache (per processor): 2 MB
    Memory: 1 GB
    Bus Speed: 667 MHz
    Boot ROM Version: MBP11.0055.B08
    SMC Version: 1.2f10
    Serial Number: W862318KVWY
    Sudden Motion Sensor:
    State: Enabled
    It freezes and has black screens during games in which apple Q and force quit doesn't work. I would need to restart the comp. when it freezes the sound would stutter, repeating whatever the game had playing.
    things I tried but the macbook pro still froze:
    running the game off USB storage device(so i think HD is fine)
    wiping HD and reinstalling OS, updating everything and playing it on both USB and the installation of game (not 3rd party apps)
    opening the macbook pro and cleaning out the dust (didn't take anything out, just blew dust off)
    resetting RAM with apple options P R
    took RAM out and put it back in
    ran apple hardware test (everything was okay)
    running a different game (Counter-Strike on CrossOver and still froze)
    Disk Warrior 4 (only minor repairs and it froze in the test game after i ran DW4)
    booting system from an external and running the game from USB
    things to note:
    although sometimes when it freezes, the temperatures are really high - even with fan control (70-80C) but, i've reproduced the lock up with the temperatures at 60C, so i don't think its a heat problem (thermal paste and whatnot)
    sometimes in safari, quicktime, itunes, or just on desktop picture i would see a single, horizontal, 1 pixel-height distorted line running across the screen, which i can take screenshots of. no idea what's causing it but it could have some relation with the freezing/lockups
    some days it will run without problems for the entire day, just to see lockups the very next day. I think it could be random.
    help please..

    =\ no one....

  • EA2/EA1 - SQL Developer freeze in file editor

    I had a PL/SQL local file open (.pkb) with a database connection selected and compiled the file. There was a compilation error and when I went to correct it, SQL Developer froze (before my typing had updated the file).
    I had the console open and it shows the following exception, which I assume is relate to the freeze:
    Exception in thread "AWT-EventQueue-0" oracle.classloader.util.AnnotatedNoClassDefFoundError:
    Missing class: oracle.bali.xml.addin.XMLSourceNode
    Dependent class: oracle.jdeveloper.compare.StreamDecoder
    Loader: main:11.0
    Code-Source: /C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar
    Configuration: system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar
    The missing class is not available from any code-source or loader in the system.
    at oracle.classloader.PolicyClassLoader.handleClassNotFound (PolicyClassLoader.java:2159) [C:/Program%20Files/Oracle/SQLDeveloper150EA1/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@10719543]
    at oracle.classloader.PolicyClassLoader.internalLoadClass (PolicyClassLoader.java:1716) [C:/Program%20Files/Oracle/SQLDeveloper150EA1/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@10719543]
    at oracle.classloader.PolicyClassLoader.access$000 (PolicyClassLoader.java:143) [C:/Program%20Files/Oracle/SQLDeveloper150EA1/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@10719543]
    at oracle.classloader.PolicyClassLoader$LoadClassAction.run (PolicyClassLoader.java:326) [C:/Program%20Files/Oracle/SQLDeveloper150EA1/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@10719543]
    at java.security.AccessController.doPrivileged (Native method) [unknown, by unknown]
    at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1675) [/C:/Program%20Files/Oracle/SQLDeveloper150EA1/j2ee/home/lib/pcl.jar, by
    sun.misc.Launcher$AppClassLoader@10719543]
    at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1657) [/C:/Program%20Files/Oracle/SQLDeveloper150EA1/j2ee/home/lib/pcl.jar, by
    sun.misc.Launcher$AppClassLoader@10719543]
    at java.lang.ClassLoader.loadClassInternal (ClassLoader.java:319) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at oracle.jdeveloper.compare.StreamDecoder.getDefaultEncoding (StreamDecoder.java:68) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdeveloper.compare.URLContributor.<init> (URLContributor.java:81) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdeveloper.compare.URLContributor.<init> (URLContributor.java:60) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.LocalHistoryEntry$LocalHistoryContributor.<init> (LocalHistoryEntry.java:79) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.LocalHistoryEntry.getCompareContributor (LocalHistoryEntry.java:56) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.updateCompareView (HistoryViewer.java:1022) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.mav$updateCompareView (HistoryViewer.java:171) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer$HistorySelectionListener.valueChanged (HistoryViewer.java:861) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at javax.swing.DefaultListSelectionModel.fireValueChanged (DefaultListSelectionModel.java:187) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at javax.swing.DefaultListSelectionModel.fireValueChanged (DefaultListSelectionModel.java:167) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at javax.swing.DefaultListSelectionModel.fireValueChanged (DefaultListSelectionModel.java:214) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at javax.swing.DefaultListSelectionModel.changeSelection (DefaultListSelectionModel.java:408) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at javax.swing.DefaultListSelectionModel.changeSelection (DefaultListSelectionModel.java:417) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at javax.swing.DefaultListSelectionModel.setSelectionInterval (DefaultListSelectionModel.java:441) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at javax.swing.JTable.setRowSelectionInterval (JTable.java:1414) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at oracle.jdevimpl.history.HistoryViewer.updateStatusCount0 (HistoryViewer.java:638) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.updateStatusCount (HistoryViewer.java:620) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.updateStatusCount (HistoryViewer.java:598) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.mav$updateStatusCount (HistoryViewer.java:171) [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer$5.run (HistoryViewer.java:442)
    [C:/Program Files/Oracle/SQLDeveloper150EA1/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA1\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at java.awt.event.InvocationEvent.dispatch (InvocationEvent.java:209) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at java.awt.EventQueue.dispatchEvent (EventQueue.java:461) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy (EventDispatchThread.java:242) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at java.awt.EventDispatchThread.pumpEventsForHierarchy (EventDispatchThread.java:163) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at java.awt.EventDispatchThread.pumpEvents (EventDispatchThread.java:157) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at java.awt.EventDispatchThread.pumpEvents (EventDispatchThread.java:149) [jre bootstrap, by jre.bootstrap:1.5.0_06]
    at java.awt.EventDispatchThread.run (EventDispatchThread.java:110) [jrebootstrap, by jre.bootstrap:1.5.0_06]

    I have just gotten basically the same exception on the console with EA2 using JDK 1.6.0_04. This time I had an SQL file open and had just looked at the history and switched back to the SQL tab to run a query.
    Is the history tab trying to do something that is not yet being shipped with EA2?
    Exception in thread "AWT-EventQueue-0" oracle.classloader.util.AnnotatedNoClassDefFoundError:
    Missing class: oracle.bali.xml.addin.XMLSourceNode
    Dependent class: oracle.jdeveloper.compare.StreamDecoder
    Loader: main:11.0
    Code-Source: /C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar
    Configuration: system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar
    The missing class is not available from any code-source or loader in the system.
    at oracle.classloader.PolicyClassLoader.handleClassNotFound (PolicyClassLoader.java:2159) [C:/Program%20Files/Oracle/SQLDeveloper150EA2/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@3526198]
    at oracle.classloader.PolicyClassLoader.internalLoadClass (PolicyClassLoader.java:1716) [C:/Program%20Files/Oracle/SQLDeveloper150EA2/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@3526198]
    at oracle.classloader.PolicyClassLoader.access$000 (PolicyClassLoader.java:143) [C:/Program%20Files/Oracle/SQLDeveloper150EA2/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@3526198]
    at oracle.classloader.PolicyClassLoader$LoadClassAction.run (PolicyClassLoader.java:326) [C:/Program%20Files/Oracle/SQLDeveloper150EA2/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@3526198]
    at java.security.AccessController.doPrivileged (Native method) [unknown, by unknown]
    at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1675) [C:/Program%20Files/Oracle/SQLDeveloper150EA2/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@3526198]
    at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1657) [C:/Program%20Files/Oracle/SQLDeveloper150EA2/j2ee/home/lib/pcl.jar, by sun.misc.Launcher$AppClassLoader@3526198]
    at java.lang.ClassLoader.loadClassInternal (ClassLoader.java:319) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at oracle.jdeveloper.compare.StreamDecoder.getDefaultEncoding (StreamDecoder.java:68) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdeveloper.compare.URLContributor.<init> (URLContributor.java:81) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdeveloper.compare.URLContributor.<init> (URLContributor.java:60) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.LocalHistoryEntry$LocalHistoryContributor.<init> (LocalHistoryEntry.java:79) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.LocalHistoryEntry.getCompareContributor (LocalHistoryEntry.java:56) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.updateCompareView (HistoryViewer.java:1022) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.mav$updateCompareView (HistoryViewer.java:171) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer$HistorySelectionListener.valueChanged (HistoryViewer.java:861) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at javax.swing.DefaultListSelectionModel.fireValueChanged (DefaultListSelectionModel.java:167) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at javax.swing.DefaultListSelectionModel.fireValueChanged (DefaultListSelectionModel.java:147) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at javax.swing.DefaultListSelectionModel.fireValueChanged (DefaultListSelectionModel.java:194) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at javax.swing.DefaultListSelectionModel.changeSelection (DefaultListSelectionModel.java:388) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at javax.swing.DefaultListSelectionModel.changeSelection (DefaultListSelectionModel.java:398) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at javax.swing.DefaultListSelectionModel.setSelectionInterval (DefaultListSelectionModel.java:442) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at javax.swing.JTable.setRowSelectionInterval (JTable.java:2072) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at oracle.jdevimpl.history.HistoryViewer.updateStatusCount0 (HistoryViewer.java:638) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.updateStatusCount (HistoryViewer.java:620) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.updateStatusCount (HistoryViewer.java:598) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer.mav$updateStatusCount (HistoryViewer.java:171) [C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at oracle.jdevimpl.history.HistoryViewer$5.run (HistoryViewer.java:442)[C:/Program Files/Oracle/SQLDeveloper150EA2/jdev/extensions/oracle.jdeveloper.history.jar (from system property C:\Program Files\Oracle\SQLDeveloper150EA2\jdev\extensions\oracle.jdeveloper.history.jar), by main:11.0]
    at java.awt.event.InvocationEvent.dispatch (InvocationEvent.java:209) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at java.awt.EventQueue.dispatchEvent (EventQueue.java:597) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at java.awt.EventDispatchThread.pumpOneEventForFilters (EventDispatchThread.java:273) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at java.awt.EventDispatchThread.pumpEventsForFilter (EventDispatchThread.java:183) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at java.awt.EventDispatchThread.pumpEventsForHierarchy (EventDispatchThread.java:173) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at java.awt.EventDispatchThread.pumpEvents (EventDispatchThread.java:168) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at java.awt.EventDispatchThread.pumpEvents (EventDispatchThread.java:160) [jre bootstrap, by jre.bootstrap:1.6.0_04]
    at java.awt.EventDispatchThread.run (EventDispatchThread.java:121) [jrebootstrap, by jre.bootstrap:1.6.0_04]

  • IMac (iSight) - random freezing

    My iMac seems to freeze rather randomly, but only while I'm gaming - I was playing NOLF2 and suddenly the screen froze, I could still hear the music and voices, then after a short while it faded into an empty blue screen and stayed there, there was no fan noise or anything. Same thing happened with Lego Star Wars demo. Only thing mentioned in the log files during the freeze was that the power button was pressed (which I did).
    This hasn't happened in normal use, yesterday I let the iTunes visualizer run for over 2 hours full screen without any freezing.
    I ran the extended Apple hardware test a few times, and it said everything is ok (it was a fairly interesting experience to my ears btw), Disk Utility reported that there was nothing to repair, and Memtest passed all the tests. I also have no 3rd party RAM. Could there be something wrong with my iMac, or is it just the two games to blame?
    iMac G5   Mac OS X (10.4.3)   20" iSight - 1 gb RAM - 250 gb HD

    Back on this topic...
    I've done the Repair Disk after every freeze/crash, but the disk always passes the test - just like the extended hardware test passes (ran it multiple times). Oh and I have nearly 200 gigs of free space on my HD.
    When this freezing occurs, Force quitting does not work at all, only thing that does work is holding down the power button.
    I'm getting the freezing with Zoo Tycoon 2 as well, but today when I was playing the game in a window, instead of the regular freezing, the screen went black, the sound was looping and the fans started blowing at full speed. This very same thing also happened with Marble Blast Gold and Myst IV.
    Like I said, my iMac works great with everything else, it's just gaming that seems to be the problem.
    When I phoned Apple, the support person was completely clueless what might be going on. First I thought the games were coded improperly or something, but since this happens with almost every game I have, I'm starting to feel there's something horribly wrong on my computer. I've tried everything from resetting the PRAM, running maintenance utilities and even re-installing Tiger with erase and install, and nothing has helped. Going from 10.4.2 to 10.4.3 certainly doesn't help either. The log files don't really show anything related to the freeze, except yesterday these two popped up when the game froze:
    Jan 07 18:49:25 [1818] kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application "Finder" for over 1 second. Server has re-enabled them.
    Jan 07 18:49:56 [1818] kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application "Dock" for over 1 second. Server has re-enabled them.
    Am I the only one with this problem?

  • SAP Freeze

    Dear sir,
    I have problem on SAP Production Server.
    We sometimes encountered a freeze, ranging from 1-10 minutes in office hour.
    When this happens, SAP just freeze, and we have to wait for some times before it is usable again.
    It happened again today.
    After that I go to tcode SM21 and check the log there.
    I found this log, (does it have anything to do with the error?)
    Documentation for system log message R4 7 :
    The user is deleted after an internal error.  The specified error
    number has the following meaning:
    Delete session 001 after error 050
    thxxmode   1384 001050     ThResFr    delete
    002: Initialization error        003: Receive error
    004: Send error                  005: Internal error
    006: Storage error               007: Rollin error
    008: Rollout error               009: Commit error
    010: Semaphore error             011: Signal received
    012: Error after restart         013: Error during connect to DB
    014: Error during roll init.     015: Error during page init.
    016: Error in OS-spec.init.      017: Error in SAP init.
    018: Error during rollback       019: SAP-DEXT call
    020: Deleted by administrator    021: Terminal output overflow
    022: APPC output overflow        023: Work process has been restarted
    Contact SAP Support.
    Thanks before

    I'm not sure the error you posted is related to your freeze.
    What happens on OS level? Open a telnet/ssh session and execute
    top d1c
    and keep that up. What do you see when the system freezes?
    Markus

  • QT 7.1.6 freezing and other problems

    Hello everybody,
    I continue to see postings relating to QT freezing while audio still plays and various work arounds people have come up with.
    Please remember to call Apple and report the problem. The more people that call and get a case number (yes, that is important) the more Apple will become aware of how widespread the problem is.
    While Apple hosts these discussion forums it does not necessarily mean they are aware of the problems we are having and discussing.
    I wrote down all the troubleshooting I did so I did not forget anything when I called Apple and reported my problem with iMovie after updating my system and QT. I was immediately given a case number and have been in contact with product specialists. Initally they thought it was the Security Patch but I quickly zeroed in on QT 7.1.6 as my problem. I finally did an Archive and Install and updated all software except Security Patch 2007-004 v1.1 and QuickTime 7.1.6. I downloaded and installed QuickTime 7.1.5. My system is functioning very well now.
    Sue
    iMac G5 20 inch   Mac OS X (10.4.9)  

    It might not be widespread and I never said it represented a majority of people but there is enough chatter to indicate a problem more widespread than just me.
    I just wanted to alert people that the best way to inform Apple of a problem is to call them and get a case number. When I worked for education my SE always reminded me to call Apple and not just report a problem to him.
    Just because you had no problem doesn't mean that everyone else who has a problem did not install correctly. I worked with Apple to zero into the QT 7.1.6 upgrade. I would never have seen the problem except I decided to do an iMovie project and that showed up the video freeze.
    Sue

  • Osx lion regularly freezes

    the pattern i have noticed so far, is that freezes occur more often when there is a lot of activity ( like when making a backup using timemachine, or when, after booting up,  i open my browser and open several ( 8 - 10 ) tabs for reading.
    the freezes occur in 2 variants:
      (A) i notice i cannot type anymore, all windows start displaying the rainbow cursor, but i can navigate to other windows, and move them.
      (B) everything freezes, even the clock stops.
    usualy freeze (B) is preceeded by freeze (A).
    then sometimes even my mouse cursor stops moving.
    sometimes i notice that when one window stops responding, i can go to a terminal window, and type things, as long as this does not
    require filesystem access, so i can edit on a line, but as soon as i type enter the terminal freezes too.
    the only logfile which gives information seemingly related to the freezes, is 'windowserver.log'
    i see many lines ' kCGErrorFailure: CGXNextSurface : Invalid window ...'  and sometimes
    kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application ...
    disable_update_likely_unbalanced: UI updates still disabled by application ...
    reenable_update_for_connection: UI updates were finally reenabled by application ...
    the application being whatever app i was working in at that moment, like GoogleChrome, or Terminal.
    the freezes usually last between 30 seconds and 1 minute, occasionally a bit longer.
    it can be hours without any problems, and then a period of freezing every few minutes.
    my system is a macbookpro8,2  running osx 10.7.1
    i have replaced my optical drive with a SSD.
    the SSD contains osxlion and has fulldisk encryption using filevault.
    the 'old' disk contains osx snowleopard.
    when i boot snowleopard i do not see any of these problems.
    i wonder if the SSD could be the culprit?  and is there any way to see if diskaccesses are taking too long, freezing the entire OS?
    or am i looking at a common osx lion problem?
    willem

    I have the same thing going on too. On my system Outlook is the one causing the hangups. I do have an SSD.
    Dec 03 10:00:31  [111] kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application "Microsoft Outlook" for over 1.00 seconds. Server has re-enabled them.
    Dec 03 10:00:45  [111] disable_update_likely_unbalanced: UI updates still disabled by application "Microsoft Outlook" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
    Dec 03 10:01:00  [111] reenable_update_for_connection: UI updates were finally reenabled by application "Microsoft Outlook" after 30.02 seconds (server forcibly re-enabled them after 1.00 seconds)

  • Desktop provider freeze

    Hi All,
    I get a very serious problem with my desktop provider (running VirtualBox 2.0.10 on Solaris 10u7). More or less randomly, the host freeze (generally when few desktops are started simultaneously). I have no other solutions than rebooting the server (the server does not even respond to a ping).
    I have seen after a search on google that this problem arise from time to time with VirtualBox. I have seen however no mention of this problem with VDI.
    One of the symptom related to the freeze was a lot of network traffic (like for instance running the Virtualbox manager through X-Windows). This was not the case during the last freeze, since the Virtual machines (Windows Vista Business) were started from SunRays terminals managed by the VDI software.
    The desktop provider is a Sun X2250 running Solaris 10u7 with all patches applied.
    Any ideas or suggestions would be greatly appreciated.
    regards,
    rhino64

    Hi All,
    I have discovered a little more on what happens with the freeze of the host running the virtual machines.
    In fact it seems not to be a freeze but simply a stop. After a while (random from few minutes to few hours), the machine running virtual hosts does not respond any more, only restart solves the problem (either through ILOM console or physically on server). Nothing in the logs except this log produced by the "last" command:
    root      sshd         vdi.local.colleg Wed Sep  9 09:59 - 09:59  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:59 - 09:59  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:59 - 09:59  (00:00)
    reboot    system boot                   Wed Sep  9 09:58
    reboot    system down                   Wed Sep  9 09:53
    root      sshd         vdi.local.colleg Wed Sep  9 09:53 - 09:53  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:53 - 09:53  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:53 - 09:53  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:52 - 09:52  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:52 - 09:52  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:52 - 09:52  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:52 - 09:52  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:52 - 09:52  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:52 - 09:52  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:52 - 09:52  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:52 - 09:52  (00:00)
    root      sshd         vdi.local.colleg Wed Sep  9 09:52 - 09:52  (00:00)9:58 was the time when the machine was manually power on again. For each freeze I have the same pattern. It seems that the VDI machine stops the desktop provider machine (why ?).
    In the cacao file, I get the following messages around the moment of stop:
    INFO: thr#344 Starting Job[3397]: CLONE for [Vista, DESKTOP_NAME: Vista0000000008]
    Sep 9, 2009 9:42:21 AM com.sun.vda.service.core.jobs.Job run
    INFO: thr#338 Starting Job[3398]: CLONE for [Vista, DESKTOP_NAME: Vista0000000009]
    Sep 9, 2009 9:49:10 AM com.sun.vda.service.core.jobs.Job run
    INFO: thr#348 Starting Job[3399]: DESKTOP_ACTION for [Vista, DESKTOP_UUID: 357]
    Sep 9, 2009 9:50:28 AM com.sun.vda.service.core.jobs.Job run
    INFO: thr#348 Starting Job[3400]: CLONE for [Vista, DESKTOP_NAME: Vista0000000002]
    Sep 9, 2009 9:53:57 AM com.sun.vda.service.client.ClientRequestWorker run
    WARNING: thr#351 Failed executing vda-client request: query(token=pseudo.0021283b0fa6): User credentials not provided
    Sep 9, 2009 9:54:00 AM com.sun.vda.service.client.ClientRequestWorker run
    WARNING: thr#351 Failed executing vda-client request: query(token=pseudo.0021283b0fa6): User credentials not provided
    Sep 9, 2009 9:54:00 AM com.sun.vda.service.client.ClientRequestWorker run
    WARNING: thr#351 Failed executing vda-client request: query(token=pseudo.0021283b0fa6): User credentials not provided
    Sep 9, 2009 9:54:00 AM com.sun.vda.service.client.ClientRequestWorker run
    WARNING: thr#351 Failed executing vda-client request: query(token=pseudo.0021283b0fa6): User credentials not provided
    Sep 9, 2009 9:54:01 AM com.sun.vda.service.client.ClientRequestWorker run
    WARNING: thr#351 Failed executing vda-client request: query(token=pseudo.0021283b0fa6): User credentials not provided
    Sep 9, 2009 9:54:01 AM com.sun.vda.service.client.ClientRequestWorker run
    WARNING: thr#351 Failed executing vda-client request: query(token=pseudo.0021283b0fa6): User credentials not provided
    Sep 9, 2009 9:54:01 AM com.sun.vda.service.client.ClientRequestWorker run
    WARNING: thr#351 Failed executing vda-client request: query(token=pseudo.0021283b0fa6): User credentials not provided
    Sep 9, 2009 9:54:01 AM com.sun.vda.service.client.ClientRequestWorker run
    WARNING: thr#351 Failed executing vda-client request: query(token=pseudo.0021283b0fa6): User credentials not provided
    Sep 9, 2009 9:54:02 AM com.sun.vda.service.client.ClientRequestWorker run
    WARNING: thr#351 Failed executing vda-client request: query(token=pseudo.0021283b0fa6): User credentials not provided
    Sep 9, 2009 9:54:23 AM com.sun.vda.service.core.jobs.Job runAny ideas would be greatly appreciated,
    thanks,
    rhino64

  • Firefox tab freeze or content shakes

    Hello
    I have two issues I think are related.
    sometimes Firefox freeze on one tab when I click on a Firefox/thunderbird link or sometimes when I look a a youtube video, it is random. When it freeze I can click on another tab and have the correct title for it but the conten stay frozen on the same tab.
    Sometimes it does not freeze but the web content shakes itself and stop shaking when I open a new tab.
    I have tried safe mode : same issue.
    I have created a new profile : same issue.
    Thanks

    The bug still continues even with the bookmarks firefox toolbar disabled.

  • Freezing video and notes

    most times, when i play a video on my iPod, it will freeze for a couple of seconds, then continue with no sound. how do i correct this. also, how do i add notes to my iPod.

    The latest software may be related to the freezing video.
    Try using an older version of the iPod updater and restore the iPod.
    Restoring Your iPod
    As for the notes, make sure the files are saved as .txt files.
    btabz

  • Samsung q530 freezes after inactivity

    I've experienced a big problem with this laptop. Earlier the screen would go to sleep and the network go down. I then added these options to xorg.conf and it seem to have worked, cause now the screen doesn't go black after a while.
    Section "ServerLayout"
    Option "BlankTime" "0"
    Option "StandbyTime" "0"
    Option "SuspendTime" "0"
    Option "OffTime" "0"
    EndSection
    The problem I'm having now is that the computer freezes if I leave it during the night (laptop lid open). I think I recall this happening before so I'm not really sure if the two things are related. The freeze is total, I can't do anything save pull the power cable.
    The only thing I find in the logs are the kernel.log
    Feb 27 23:32:47 localhost kernel: wlc_prec_enq_head: No where to go, prec == 4
    Feb 27 23:32:47 localhost kernel: wlc_prec_enq_head: No where to go, prec == 4
    Feb 27 23:32:47 localhost kernel: wlc_prec_enq_head: No where to go, prec == 4
    Feb 27 23:32:47 localhost kernel: wlc_prec_enq_head: No where to go, prec == 4
    Feb 27 23:32:47 localhost kernel: wlc_prec_enq_head: No where to go, prec == 4
    Feb 27 23:32:47 localhost kernel: wlc_prec_enq_head: No where to go, prec == 4
    Feb 28 03:29:30 localhost kernel: wlc_prec_enq_head: No where to go, prec == 4
    Feb 28 03:29:30 localhost kernel: wlc_prec_enq_head: No where to go, prec == 4
    Feb 28 03:29:30 localhost kernel: wlc_prec_enq_head: No where to go, prec == 4
    Feb 28 03:29:Feb 28 09:23:20 localhost kernel: Initializing cgroup subsys cpuset
    Feb 28 09:23:20 localhost kernel: Initializing cgroup subsys cpu
    As you can see it spits out several: localhost kernel: wlc_prec_enq_head: No where to go, prec == 4 every second from some time around when I leave it and go to bed up to 03:29:30 in the night. So any ideas where to go from here?

    We also have the same problem.  Sometimes we get the message "usb camera and mic disconnected"; sometimes it's the the mic or the camera that freezes and sometimes both.
    I seem to be trapped in a cycle of Samsung saying it's a Skype problem and vice versa.
    Only bought the TV so I could skype relatives.  Looking like it's going to be returned if there is no solution.

Maybe you are looking for