Failover Cluster Quorum Disk is fallen off the shared volume
Hi, we had a Cluster that was holding 40+ VMs and was originally setup with the building 1GB Ethernet adapter, we yesterday installed Qlogic 10 GB NIC teaming for both of the nodes and reconfigured the network on both nodes. However now the Quorum disk
is not a part of Cluster Shared Volume How can I add that disk back to the shared volum please?
Hi Riaz,
Add a quorum disk is easy so please let us know if there is any specific error occurs during the steps provided in following thread:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/0566ede4-55bb-4694-a134-104fac2a7052/replace-quorum-disk-on-failover-cluster-on-different-lun?forum=winserverClustering
If you have any feedback on our support, please send to [email protected]
Similar Messages
-
[SOLVED]suspend fails NVRM: GPU at 0000:01:00.0 has fallen off the bus
Hi All,
After a update of my laptop, it does not fully wakes after going into suspend. It does not react to numlock anymore. I have to push the power button for 10 seconds to shut it down.
/var/log/everything.log, normal operations:
Jul 21 03:42:38 localhost dhcpcd[1029]: wlan0: sending IPv6 Router Solicitation
Jul 21 03:42:38 localhost dhcpcd[1029]: wlan0: sendmsg: Cannot assign requested address
Jul 21 03:42:38 localhost dhcpcd[1029]: wlan0: no IPv6 Routers available
Jul 21 03:42:45 localhost dbus[533]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jul 21 03:42:45 localhost dbus[533]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jul 21 03:42:45 localhost acpid: client connected from 1134[0:1000]
Jul 21 03:42:45 localhost acpid: 1 client rule loaded
Jul 21 03:42:46 localhost NetworkManager[559]: <info> (wlan0): IP6 addrconf timed out or failed.
Jul 21 03:42:46 localhost NetworkManager[559]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jul 21 03:42:46 localhost NetworkManager[559]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jul 21 03:42:46 localhost NetworkManager[559]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 21 03:42:50 localhost acpid: client connected from 1134[0:1000]
Jul 21 03:42:50 localhost acpid: 1 client rule loaded
Jul 21 03:42:55 localhost kernel: [ 48.812457] fuse init (API version 7.18)
Jul 21 03:42:59 localhost dbus[533]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
Jul 21 03:42:59 localhost udisksd[1209]: udisks daemon version 1.94.0 starting
Jul 21 03:42:59 localhost dbus[533]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Jul 21 03:42:59 localhost udisksd[1209]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jul 21 04:01:01 localhost /USR/SBIN/CROND[1363]: (root) CMD (run-parts /etc/cron.hourly)
Jul 21 04:01:01 localhost anacron[1369]: Anacron started on 2012-07-21
Jul 21 04:01:01 localhost anacron[1369]: Will run job `cron.daily' in 42 min.
Jul 21 04:01:01 localhost anacron[1369]: Jobs will be executed sequentially
Jul 21 04:21:01 localhost -- MARK --
/var/log/everything.log, after starting suspend:
Jul 21 04:21:13 localhost kernel: [ 2346.821030] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:21:13 localhost kernel: [ 2347.000872] EXT4-fs (sda8): re-mounted. Opts: commit=0
Jul 21 04:25:10 localhost kernel: [ 2349.512404] PM: Syncing filesystems ... done.
Jul 21 04:25:10 localhost kernel: [ 2349.514874] PM: Preparing system for mem sleep
Jul 21 04:25:10 localhost kernel: [ 2349.514891] Freezing user space processes ... (elapsed 0.01 seconds) done.
Jul 21 04:25:10 localhost kernel: [ 2349.526541] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Jul 21 04:25:10 localhost kernel: [ 2349.539896] PM: Entering mem sleep
Jul 21 04:25:10 localhost kernel: [ 2349.539930] Suspending console(s) (use no_console_suspend to debug)
Jul 21 04:25:10 localhost kernel: [ 2349.573787] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 21 04:25:10 localhost kernel: [ 2349.611052] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:10 localhost kernel: [ 2349.613512] sd 0:0:0:0: [sda] Stopping disk
Jul 21 04:25:10 localhost kernel: [ 2350.236650] PM: suspend of devices complete after 696.314 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.236925] PM: late suspend of devices complete after 0.270 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.237272] r8169 0000:08:00.0: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.266603] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.303271] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.326605] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.343218] ehci_hcd 0000:00:1a.7: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.379942] uhci_hcd 0000:00:1a.2: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.403292] uhci_hcd 0000:00:1a.1: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.426606] uhci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.426678] PM: noirq suspend of devices complete after 189.749 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.427140] ACPI: Preparing to enter system sleep state S3
Jul 21 04:25:10 localhost kernel: [ 2350.519991] PM: Saving platform NVS memory
Jul 21 04:25:10 localhost kernel: [ 2350.520810] Disabling non-boot CPUs ...
Jul 21 04:25:10 localhost kernel: [ 2350.623205] CPU 1 is now offline
Jul 21 04:25:10 localhost kernel: [ 2350.623688] Extended CMOS year: 2000
Jul 21 04:25:10 localhost kernel: [ 2350.623688] ACPI: Low-level resume complete
Jul 21 04:25:10 localhost kernel: [ 2350.623688] PM: Restoring platform NVS memory
Jul 21 04:25:10 localhost kernel: [ 2350.623688] Extended CMOS year: 2000
Jul 21 04:25:10 localhost kernel: [ 2350.623688] Enabling non-boot CPUs ...
Jul 21 04:25:10 localhost kernel: [ 2350.630554] Booting Node 0 Processor 1 APIC 0x1
Jul 21 04:25:10 localhost kernel: [ 2350.641916] NMI watchdog: enabled, takes one hw-pmu counter.
Jul 21 04:25:10 localhost kernel: [ 2350.645407] CPU1 is up
Jul 21 04:25:10 localhost kernel: [ 2350.647122] ACPI: Waking up from system sleep state S3
Jul 21 04:25:10 localhost kernel: [ 2350.653227] uhci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.659889] uhci_hcd 0000:00:1a.1: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.666555] uhci_hcd 0000:00:1a.2: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.683204] ehci_hcd 0000:00:1a.7: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.689888] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.696556] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.713204] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.715075] PM: noirq resume of devices complete after 67.761 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.715286] PM: early resume of devices complete after 0.105 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.715344] uhci_hcd 0000:00:1a.0: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715373] usb usb1: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715391] uhci_hcd 0000:00:1a.1: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715421] usb usb2: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715437] uhci_hcd 0000:00:1a.2: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715465] usb usb3: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715480] ehci_hcd 0000:00:1a.7: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715521] uhci_hcd 0000:00:1d.0: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715540] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X
Jul 21 04:25:10 localhost kernel: [ 2350.715550] usb usb4: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715571] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715601] usb usb5: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715611] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715623] ehci_hcd 0000:00:1d.7: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715639] usb usb6: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715647] pci 0000:00:1e.0: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715663] ata_piix 0000:00:1f.2: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715667] ata_piix 0000:00:1f.5: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715690] r8169 0000:08:00.0: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.723377] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:10 localhost kernel: [ 2350.723395] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:10 localhost kernel: [ 2350.816609] r8169 0000:08:00.0: eth0: link down
Jul 21 04:25:10 localhost kernel: [ 2351.111777] ata4: SATA link down (SStatus 0 SControl 300)
Jul 21 04:25:10 localhost kernel: [ 2351.128460] ata3: SATA link down (SStatus 0 SControl 300)
Jul 21 04:25:10 localhost kernel: [ 2351.199920] usb 2-1: reset low-speed USB device number 2 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2351.263475] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jul 21 04:25:10 localhost kernel: [ 2351.276859] firewire_core 0000:1a:00.0: rediscovered device fw0
Jul 21 04:25:10 localhost kernel: [ 2351.283960] ata2.00: configured for UDMA/100
Jul 21 04:25:10 localhost kernel: [ 2351.739942] usb 2-2: reset low-speed USB device number 3 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.129932] usb 8-2: reset high-speed USB device number 2 using ehci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.359839] usb 6-1: reset full-speed USB device number 2 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.784239] usb 6-1.1: reset full-speed USB device number 3 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.883229] btusb 6-1.1:1.0: no reset_resume for driver btusb?
Jul 21 04:25:10 localhost kernel: [ 2352.883233] btusb 6-1.1:1.1: no reset_resume for driver btusb?
Jul 21 04:25:10 localhost kernel: [ 2352.941243] usb 6-1.2: reset full-speed USB device number 4 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.969919] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 21 04:25:10 localhost kernel: [ 2353.101249] usb 6-1.3: reset full-speed USB device number 5 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2353.181194] ata1.00: configured for UDMA/133
Jul 21 04:25:10 localhost kernel: [ 2353.181463] sd 0:0:0:0: [sda] Starting disk
Jul 21 04:25:10 localhost kernel: [ 2353.436737] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jul 21 04:25:10 localhost kernel: [ 2358.057138] PM: resume of devices complete after 7341.844 msecs
Jul 21 04:25:10 localhost kernel: [ 2358.057602] PM: Finishing wakeup.
Jul 21 04:25:10 localhost kernel: [ 2358.057604] Restarting tasks ... done.
Jul 21 04:25:10 localhost kernel: [ 2358.064234] video LNXVIDEO:00: Restoring backlight state
Jul 21 04:25:11 localhost kernel: [ 2358.233575] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:11 localhost kernel: [ 2358.272368] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:11 localhost kernel: [ 2358.309721] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:11 localhost kernel: [ 2358.349601] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:13 localhost kernel: [ 2360.644416] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:25:13 localhost kernel: [ 2360.648163] EXT4-fs (sda8): re-mounted. Opts: commit=0
Jul 21 04:25:13 localhost acpid: client 1134[0:1000] has disconnected
Jul 21 04:25:13 localhost acpid: client 1134[0:1000] has disconnected
Jul 21 04:25:13 localhost acpid: client connected from 1134[0:1000]
Jul 21 04:25:13 localhost acpid: 1 client rule loaded
Jul 21 04:25:26 localhost kernel: [ 2373.415894] NVRM: Xid (0000:01:00): 8, Channel 0000007e
Jul 21 04:25:26 localhost kernel: [ 2373.700350] hrtimer: interrupt took 91847280 ns
Jul 21 04:25:26 localhost kernel: [ 2373.700352] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
Jul 21 04:28:36 localhost kernel: [ 2563.568752] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:28:36 localhost kernel: [ 2563.573610] EXT4-fs (sda8): re-mounted. Opts: commit=0
What does this message mean?
Jul 21 04:25:26 localhost kernel: [ 2373.700352] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
What can i do to solve this?
Best regards,
Cedric
Last edited by cdwijs (2012-08-09 18:33:34)I did a quick google search. This page suggested that I set my videocard in persistend mode:
http://scientificlinuxforum.org/index.p … topic=1469
So i did the following:
]# /usr/bin/nvidia-smi -pm 1
Enabled persistence mode for GPU 0000:01:00.0.
All done.
# /usr/bin/nvidia-smi -q
==============NVSMI LOG==============
Timestamp : Sat Jul 21 04:58:55 2012
Driver Version : 302.17
Attached GPUs : 1
GPU 0000:01:00.0
Product Name : GeForce 9600M GS
Display Mode : N/A
Persistence Mode : Enabled
Driver Model
Current : N/A
Pending : N/A
Serial Number : N/A
GPU UUID : N/A
VBIOS Version : 62.94.8D.00.0B
Inforom Version
OEM Object : N/A
ECC Object : N/A
Power Management Object : N/A
PCI
Bus : 0x01
Device : 0x00
Domain : 0x0000
Device Id : 0x064810DE
Bus Id : 0000:01:00.0
Sub System Id : 0x02C01028
GPU Link Info
PCIe Generation
Max : N/A
Current : N/A
Link Width
Max : N/A
Current : N/A
Fan Speed : N/A
Performance State : N/A
Memory Usage
Total : 511 MB
Used : 30 MB
Free : 480 MB
Compute Mode : Default
Utilization
Gpu : N/A
Memory : N/A
Ecc Mode
Current : N/A
Pending : N/A
ECC Errors
Volatile
Single Bit
Device Memory : N/A
Register File : N/A
L1 Cache : N/A
L2 Cache : N/A
Total : N/A
Double Bit
Device Memory : N/A
Register File : N/A
L1 Cache : N/A
L2 Cache : N/A
Total : N/A
Aggregate
Single Bit
Device Memory : N/A
Register File : N/A
L1 Cache : N/A
L2 Cache : N/A
Total : N/A
Double Bit
Device Memory : N/A
Register File : N/A
L1 Cache : N/A
L2 Cache : N/A
Total : N/A
Temperature
Gpu : 61 C
Power Readings
Power Management : N/A
Power Draw : N/A
Power Limit : N/A
Clocks
Graphics : N/A
SM : N/A
Memory : N/A
Max Clocks
Graphics : N/A
SM : N/A
Memory : N/A
Compute Processes : Not Supported
This did not solve the issue. The laptop goes into suspend (the power LED starts blinking), but when the power button is then briefly pressed, the machine does power-up, but after hearing 2 clicks from the speaker, i get a black screen, a full-running CPU fan, and no reaction to numlock.
/var/log/everything.log:
Jul 21 04:30:13 localhost NetworkManager[565]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 21 04:50:40 localhost -- MARK --
Jul 21 04:54:46 localhost kernel: [ 1516.765698] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:54:46 localhost kernel: [ 1516.942964] EXT4-fs (sda8): re-mounted. Opts: commit=0
Jul 21 04:55:02 localhost kernel: [ 1519.654895] PM: Syncing filesystems ... done.
Jul 21 04:55:02 localhost kernel: [ 1519.657049] PM: Preparing system for mem sleep
Jul 21 04:55:02 localhost kernel: [ 1519.657066] Freezing user space processes ... (elapsed 0.01 seconds) done.
Jul 21 04:55:02 localhost kernel: [ 1519.669943] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Jul 21 04:55:02 localhost kernel: [ 1519.683296] PM: Entering mem sleep
Jul 21 04:55:02 localhost kernel: [ 1519.683337] Suspending console(s) (use no_console_suspend to debug)
Jul 21 04:55:02 localhost kernel: [ 1519.717139] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 21 04:55:02 localhost kernel: [ 1519.749832] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1519.786781] sd 0:0:0:0: [sda] Stopping disk
Jul 21 04:55:02 localhost kernel: [ 1520.410064] PM: suspend of devices complete after 726.343 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.410337] PM: late suspend of devices complete after 0.266 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.410678] r8169 0000:08:00.0: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.440024] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.476689] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.500023] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.516685] ehci_hcd 0000:00:1a.7: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.553353] uhci_hcd 0000:00:1a.2: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.576688] uhci_hcd 0000:00:1a.1: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.603354] uhci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.603426] PM: noirq suspend of devices complete after 193.085 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.603888] ACPI: Preparing to enter system sleep state S3
Jul 21 04:55:02 localhost kernel: [ 1520.693403] PM: Saving platform NVS memory
Jul 21 04:55:02 localhost kernel: [ 1520.694218] Disabling non-boot CPUs ...
Jul 21 04:55:02 localhost kernel: [ 1520.796623] CPU 1 is now offline
Jul 21 04:55:02 localhost kernel: [ 1520.797088] Extended CMOS year: 2000
Jul 21 04:55:02 localhost kernel: [ 1520.797088] ACPI: Low-level resume complete
Jul 21 04:55:02 localhost kernel: [ 1520.797088] PM: Restoring platform NVS memory
Jul 21 04:55:02 localhost kernel: [ 1520.797088] Extended CMOS year: 2000
Jul 21 04:55:02 localhost kernel: [ 1520.797088] Enabling non-boot CPUs ...
Jul 21 04:55:02 localhost kernel: [ 1520.803951] Booting Node 0 Processor 1 APIC 0x1
Jul 21 04:55:02 localhost kernel: [ 1520.815303] NMI watchdog: enabled, takes one hw-pmu counter.
Jul 21 04:55:02 localhost kernel: [ 1520.816608] CPU1 is up
Jul 21 04:55:02 localhost kernel: [ 1520.818293] ACPI: Waking up from system sleep state S3
Jul 21 04:55:02 localhost kernel: [ 1520.823322] uhci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.829975] uhci_hcd 0000:00:1a.1: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.836638] uhci_hcd 0000:00:1a.2: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.853290] ehci_hcd 0000:00:1a.7: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.859971] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.866638] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.883290] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.885162] PM: noirq resume of devices complete after 66.681 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.885372] PM: early resume of devices complete after 0.105 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.885432] uhci_hcd 0000:00:1a.0: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885432] uhci_hcd 0000:00:1a.1: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885465] usb usb1: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885466] usb usb2: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885487] uhci_hcd 0000:00:1a.2: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885490] ehci_hcd 0000:00:1a.7: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885518] usb usb3: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885549] uhci_hcd 0000:00:1d.0: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885582] usb usb4: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885582] snd_hda_intel 0000:00:1b.0: irq 48 for MSI/MSI-X
Jul 21 04:55:02 localhost kernel: [ 1520.885600] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885629] usb usb5: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885648] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885653] ehci_hcd 0000:00:1d.7: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885680] pci 0000:00:1e.0: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885679] usb usb6: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885698] ata_piix 0000:00:1f.2: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885713] ata_piix 0000:00:1f.5: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885736] r8169 0000:08:00.0: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.890553] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1520.891048] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1520.960285] r8169 0000:08:00.0: eth0: link down
Jul 21 04:55:02 localhost kernel: [ 1521.281391] ata3: SATA link down (SStatus 0 SControl 300)
Jul 21 04:55:02 localhost kernel: [ 1521.297666] ata4: SATA link down (SStatus 0 SControl 300)
Jul 21 04:55:02 localhost kernel: [ 1521.332377] Extended CMOS year: 2000
Jul 21 04:55:02 localhost kernel: [ 1521.376657] usb 2-1: reset low-speed USB device number 2 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1521.406940] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jul 21 04:55:02 localhost kernel: [ 1521.427670] ata2.00: configured for UDMA/100
Jul 21 04:55:02 localhost acpid: client 1147[0:1000] has disconnected
Jul 21 04:55:02 localhost acpid: client 1147[0:1000] has disconnected
Jul 21 04:55:02 localhost kernel: [ 1521.453328] firewire_core 0000:1a:00.0: rediscovered device fw0
Jul 21 04:55:02 localhost kernel: [ 1521.915219] usb 2-2: reset low-speed USB device number 3 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1522.303337] usb 8-2: reset high-speed USB device number 2 using ehci_hcd
Jul 21 04:55:02 localhost kernel: [ 1522.533339] usb 6-1: reset full-speed USB device number 2 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1522.955078] usb 6-1.1: reset full-speed USB device number 3 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1523.057065] btusb 6-1.1:1.0: no reset_resume for driver btusb?
Jul 21 04:55:02 localhost kernel: [ 1523.057070] btusb 6-1.1:1.1: no reset_resume for driver btusb?
Jul 21 04:55:02 localhost kernel: [ 1523.113342] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 21 04:55:02 localhost kernel: [ 1523.115078] usb 6-1.2: reset full-speed USB device number 4 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1523.278082] usb 6-1.3: reset full-speed USB device number 5 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1523.321369] ata1.00: configured for UDMA/133
Jul 21 04:55:02 localhost kernel: [ 1523.321637] sd 0:0:0:0: [sda] Starting disk
Jul 21 04:55:02 localhost kernel: [ 1523.613501] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jul 21 04:55:02 localhost kernel: [ 1528.234017] PM: resume of devices complete after 7348.637 msecs
Jul 21 04:55:02 localhost kernel: [ 1528.234472] PM: Finishing wakeup.
Jul 21 04:55:02 localhost kernel: [ 1528.234474] Restarting tasks ... done.
Jul 21 04:55:02 localhost kernel: [ 1528.239320] video LNXVIDEO:00: Restoring backlight state
Jul 21 04:55:02 localhost acpid: client connected from 1147[0:1000]
Jul 21 04:55:02 localhost acpid: 1 client rule loaded
Jul 21 04:55:02 localhost kernel: [ 1528.396372] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1528.433245] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1528.469720] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1528.506634] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:03 localhost kernel: [ 1530.007718] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:55:04 localhost kernel: [ 1530.271879] EXT4-fs (sda8): re-mounted. Opts: commit=0
Jul 21 04:55:55 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset
Jul 21 04:55:55 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu
Interestingly, the message that the GPU has fallen off the bus is no longer present. Something else is going on as well :-)
Best regards,
Cedric -
I experienced a weird problem for which I don't know the reason. A few months ago I had this problem which if I have to describe it, this is how it happens:
While I'm surfing, coding or playing a game, X dies (freezes) and the monitor goes black losing connection with the GPU. I saw the GPU message in dmesg and after a few more times it happened, I opened my PC, disassembled everything to clean the dust. Afterwards everything went okay, back to normal. Today, I experienced the problem again while playing a game and logged in through ssh to get some logs. Here's what I got:
# dmesg
[Mon Jan 5 17:57:32 2015] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
[Mon Jan 5 17:57:32 2015] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
[1538364.433]
X.Org X Server 1.16.3
Release Date: 2014-12-20
[1538364.475] X Protocol Version 11, Revision 0
[1538364.490] Build Operating System: Linux 3.18.1-1-ARCH x86_64
[1538364.505] Current Operating System: Linux archy 3.18.1-1-ARCH #1 SMP PREEMPT Wed Dec 17 15:40:09 CET 2014 x86_64
[1538364.505] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/archy/root rw vga=0x361 resume=/dev/archy/swap initrd=../intel-ucode.img,../initramfs-linux.img
[1538364.537] Build Date: 29 December 2014 01:09:58PM
[1538364.552]
[1538364.567] Current version of pixman: 0.32.6
[1538364.597] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[1538364.597] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[1538364.657] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan 4 14:27:25 2015
[1538364.672] (==) Using config file: "/etc/X11/xorg.conf"
[1538364.687] (==) Using config directory: "/etc/X11/xorg.conf.d"
[1538364.702] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[1538364.702] (==) ServerLayout "Layout0"
[1538364.702] (**) |-->Screen "Screen0" (0)
[1538364.702] (**) | |-->Monitor "Monitor0"
[1538364.702] (**) | |-->Device "Device0"
[1538364.702] (**) |-->Input Device "Keyboard0"
[1538364.702] (**) |-->Input Device "Mouse0"
[1538364.702] (==) Automatically adding devices
[1538364.702] (==) Automatically enabling devices
[1538364.702] (==) Automatically adding GPU devices
[1538364.702] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[1538364.702] Entry deleted from font path.
[1538364.702] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[1538364.702] Entry deleted from font path.
[1538364.702] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[1538364.702] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[1538364.702] Entry deleted from font path.
[1538364.702] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[1538364.702] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[1538364.702] (==) ModulePath set to "/usr/lib/xorg/modules"
[1538364.702] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[1538364.702] (WW) Disabling Keyboard0
[1538364.702] (WW) Disabling Mouse0
[1538364.702] (II) Loader magic: 0x818d80
[1538364.702] (II) Module ABI versions:
[1538364.702] X.Org ANSI C Emulation: 0.4
[1538364.702] X.Org Video Driver: 18.0
[1538364.702] X.Org XInput driver : 21.0
[1538364.702] X.Org Server Extension : 8.0
[1538364.704] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[1538364.704] (II) xfree86: Adding drm device (/dev/dri/card0)
[1538364.704] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[1538364.704] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Invalid argument
[1538364.704] (II) systemd-logind: releasing fd for 226:0
[1538364.705] (--) PCI:*(0:1:0:0) 10de:1245:10b0:0401 rev 161, Mem @ 0xfc000000/33554432, 0xe8000000/134217728, 0xf0000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[1538364.705] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[1538364.705] (II) LoadModule: "glx"
[1538364.706] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[1538364.712] (II) Module glx: vendor="NVIDIA Corporation"
[1538364.713] compiled for 4.0.2, module version = 1.0.0
[1538364.713] Module class: X.Org Server Extension
[1538364.713] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
[1538364.713] (II) LoadModule: "nvidia"
[1538364.713] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[1538364.713] (II) Module nvidia: vendor="NVIDIA Corporation"
[1538364.713] compiled for 4.0.2, module version = 1.0.0
[1538364.713] Module class: X.Org Video Driver
[1538364.713] (II) NVIDIA dlloader X Driver 343.36 Mon Dec 1 15:28:39 PST 2014
[1538364.713] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[1538364.713] (++) using VT number 1
[1538364.713] (--) controlling tty is VT number 1, auto-enabling KeepTty
[1538364.713] (II) Loading sub module "fb"
[1538364.713] (II) LoadModule: "fb"
[1538364.713] (II) Loading /usr/lib/xorg/modules/libfb.so
[1538364.713] (II) Module fb: vendor="X.Org Foundation"
[1538364.713] compiled for 1.16.3, module version = 1.0.0
[1538364.713] ABI class: X.Org ANSI C Emulation, version 0.4
[1538364.713] (II) Loading sub module "wfb"
[1538364.713] (II) LoadModule: "wfb"
[1538364.713] (II) Loading /usr/lib/xorg/modules/libwfb.so
[1538364.713] (II) Module wfb: vendor="X.Org Foundation"
[1538364.713] compiled for 1.16.3, module version = 1.0.0
[1538364.713] ABI class: X.Org ANSI C Emulation, version 0.4
[1538364.713] (II) Loading sub module "ramdac"
[1538364.713] (II) LoadModule: "ramdac"
[1538364.713] (II) Module "ramdac" already built-in
[1538364.714] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[1538364.714] (==) NVIDIA(0): RGB weight 888
[1538364.714] (==) NVIDIA(0): Default visual is TrueColor
[1538364.714] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[1538364.714] (**) NVIDIA(0): Option "NoLogo" "True"
[1538364.714] (**) NVIDIA(0): Enabling 2D acceleration
[1538364.951] (II) NVIDIA(0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1538364.951] (II) NVIDIA(0): Vision stereo.
[1538365.009] (II) NVIDIA(0): NVIDIA GPU GeForce GTS 450 (GF116) at PCI:1:0:0 (GPU-0)
[1538365.009] (--) NVIDIA(0): Memory: 1048576 kBytes
[1538365.009] (--) NVIDIA(0): VideoBIOS: 70.26.23.00.00
[1538365.009] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[1538365.014] (--) NVIDIA(0): Valid display device(s) on GeForce GTS 450 at PCI:1:0:0
[1538365.014] (--) NVIDIA(0): CRT-0
[1538365.014] (--) NVIDIA(0): CRT-1
[1538365.014] (--) NVIDIA(0): DFP-0
[1538365.014] (--) NVIDIA(0): Philips 234CL (DFP-1) (boot, connected)
[1538365.014] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[1538365.014] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[1538365.014] (--) NVIDIA(0): DFP-0: Internal TMDS
[1538365.014] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[1538365.014] (--) NVIDIA(0): Philips 234CL (DFP-1): Internal TMDS
[1538365.014] (--) NVIDIA(GPU-0): Philips 234CL (DFP-1): 225.0 MHz maximum pixel clock
[1538365.014] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[1538365.014] (**) NVIDIA(0): device Philips 234CL (DFP-1) (Using EDID frequencies has
[1538365.014] (**) NVIDIA(0): been enabled on all display devices.)
[1538365.014] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.014] (WW) NVIDIA(GPU-0): "720x576" is specified in the EDID; however, the EDID's
[1538365.014] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.014] (WW) NVIDIA(GPU-0): this mode's VertRefresh (50.0 Hz); ignoring VertRefresh
[1538365.014] (WW) NVIDIA(GPU-0): check for mode "720x576".
[1538365.014] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.014] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[1538365.014] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.014] (WW) NVIDIA(GPU-0): this mode's VertRefresh (50.0 Hz); ignoring VertRefresh
[1538365.015] (WW) NVIDIA(GPU-0): check for mode "1920x1080".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "1280x720" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's VertRefresh (50.0 Hz); ignoring VertRefresh
[1538365.015] (WW) NVIDIA(GPU-0): check for mode "1280x720".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "720x576" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's VertRefresh (50.0 Hz); ignoring VertRefresh
[1538365.015] (WW) NVIDIA(GPU-0): check for mode "720x576".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "720x576" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's VertRefresh (50.0 Hz); ignoring VertRefresh
[1538365.015] (WW) NVIDIA(GPU-0): check for mode "720x576".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's VertRefresh (30.0 Hz); ignoring VertRefresh
[1538365.015] (WW) NVIDIA(GPU-0): check for mode "1920x1080".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid HorizSync range (30.000-83.000 kHz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[1538365.015] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's VertRefresh (25.0 Hz); ignoring VertRefresh
[1538365.015] (WW) NVIDIA(GPU-0): check for mode "1920x1080".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid HorizSync range (30.000-83.000 kHz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's HorizSync (27.0 kHz); ignoring HorizSync check
[1538365.015] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
[1538365.015] (WW) NVIDIA(GPU-0): check for mode "1920x1080".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "720x480" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid HorizSync range (30.000-83.000 kHz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's HorizSync (15.7 kHz); ignoring HorizSync check
[1538365.015] (WW) NVIDIA(GPU-0): for mode "720x480".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "720x480" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid HorizSync range (30.000-83.000 kHz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's HorizSync (15.7 kHz); ignoring HorizSync check
[1538365.015] (WW) NVIDIA(GPU-0): for mode "720x480".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid HorizSync range (30.000-83.000 kHz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[1538365.015] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's VertRefresh (50.0 Hz); ignoring VertRefresh
[1538365.015] (WW) NVIDIA(GPU-0): check for mode "1920x1080".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "720x576" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid HorizSync range (30.000-83.000 kHz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's HorizSync (15.6 kHz); ignoring HorizSync check
[1538365.015] (WW) NVIDIA(GPU-0): for mode "720x576".
[1538365.015] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.015] (WW) NVIDIA(GPU-0): "720x576" is specified in the EDID; however, the EDID's
[1538365.015] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.015] (WW) NVIDIA(GPU-0): this mode's VertRefresh (50.0 Hz); ignoring VertRefresh
[1538365.015] (WW) NVIDIA(GPU-0): check for mode "720x576".
[1538365.016] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.016] (WW) NVIDIA(GPU-0): "720x576" is specified in the EDID; however, the EDID's
[1538365.016] (WW) NVIDIA(GPU-0): valid HorizSync range (30.000-83.000 kHz) would exclude
[1538365.016] (WW) NVIDIA(GPU-0): this mode's HorizSync (15.6 kHz); ignoring HorizSync check
[1538365.016] (WW) NVIDIA(GPU-0): for mode "720x576".
[1538365.016] (WW) NVIDIA(GPU-0): The EDID for Philips 234CL (DFP-1) contradicts itself: mode
[1538365.016] (WW) NVIDIA(GPU-0): "720x576" is specified in the EDID; however, the EDID's
[1538365.016] (WW) NVIDIA(GPU-0): valid VertRefresh range (56.000-76.000 Hz) would exclude
[1538365.016] (WW) NVIDIA(GPU-0): this mode's VertRefresh (50.0 Hz); ignoring VertRefresh
[1538365.016] (WW) NVIDIA(GPU-0): check for mode "720x576".
[1538365.016] (==) NVIDIA(0):
[1538365.016] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[1538365.016] (==) NVIDIA(0): will be used as the requested mode.
[1538365.016] (==) NVIDIA(0):
[1538365.016] (II) NVIDIA(0): Validated MetaModes:
[1538365.016] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[1538365.016] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[1538365.039] (--) NVIDIA(0): DPI set to (95, 94); computed from "UseEdidDpi" X config
[1538365.039] (--) NVIDIA(0): option
[1538365.039] (--) Depth 24 pixmap format is 32 bpp
[1538365.039] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[1538365.039] (II) NVIDIA: access.
[1538365.040] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[1538365.040] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[1538365.041] (II) NVIDIA(0): configuration option may not be set correctly. When the
[1538365.041] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[1538365.041] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[1538365.041] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[1538365.041] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[1538365.041] (II) NVIDIA(0): Config Options in the README.
[1538365.045] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[1538365.117] (==) NVIDIA(0): Disabling shared memory pixmaps
[1538365.117] (==) NVIDIA(0): Backing store enabled
[1538365.117] (==) NVIDIA(0): Silken mouse enabled
[1538365.117] (**) NVIDIA(0): DPMS enabled
[1538365.117] (II) Loading sub module "dri2"
[1538365.117] (II) LoadModule: "dri2"
[1538365.117] (II) Module "dri2" already built-in
[1538365.117] (II) NVIDIA(0): [DRI2] Setup complete
[1538365.117] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[1538365.117] (--) RandR disabled
[1538365.120] (II) Initializing extension GLX
[1538365.145] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[1538365.145] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[1538365.145] (II) LoadModule: "evdev"
[1538365.145] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[1538365.145] (II) Module evdev: vendor="X.Org Foundation"
[1538365.145] compiled for 1.16.2, module version = 2.9.1
[1538365.145] Module class: X.Org XInput Driver
[1538365.145] ABI class: X.Org XInput driver, version 21.0
[1538365.146] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 26 paused 0
[1538365.146] (II) Using input driver 'evdev' for 'Power Button'
[1538365.146] (**) Power Button: always reports core events
[1538365.146] (**) evdev: Power Button: Device: "/dev/input/event5"
[1538365.146] (--) evdev: Power Button: Vendor 0 Product 0x1
[1538365.146] (--) evdev: Power Button: Found keys
[1538365.146] (II) evdev: Power Button: Configuring as keyboard
[1538365.146] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7/event5"
[1538365.146] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[1538365.146] (**) Option "xkb_rules" "evdev"
[1538365.146] (**) Option "xkb_model" "pc104"
[1538365.146] (**) Option "xkb_layout" "us"
[1538365.159] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[1538365.159] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[1538365.160] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 27 paused 0
[1538365.160] (II) Using input driver 'evdev' for 'Power Button'
[1538365.160] (**) Power Button: always reports core events
[1538365.160] (**) evdev: Power Button: Device: "/dev/input/event4"
[1538365.160] (--) evdev: Power Button: Vendor 0 Product 0x1
[1538365.160] (--) evdev: Power Button: Found keys
[1538365.160] (II) evdev: Power Button: Configuring as keyboard
[1538365.160] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input6/event4"
[1538365.160] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[1538365.160] (**) Option "xkb_rules" "evdev"
[1538365.160] (**) Option "xkb_model" "pc104"
[1538365.160] (**) Option "xkb_layout" "us"
[1538365.160] (II) config/udev: Adding drm device (/dev/dri/card0)
[1538365.160] (II) xfree86: Adding drm device (/dev/dri/card0)
[1538365.161] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 28 paused 0
[1538365.161] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Invalid argument
[1538365.161] (II) systemd-logind: releasing fd for 226:0
[1538365.161] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event11)
[1538365.161] (II) No input driver specified, ignoring this device.
[1538365.161] (II) This device may have been added with another device file.
[1538365.161] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event12)
[1538365.161] (II) No input driver specified, ignoring this device.
[1538365.161] (II) This device may have been added with another device file.
[1538365.161] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event13)
[1538365.161] (II) No input driver specified, ignoring this device.
[1538365.161] (II) This device may have been added with another device file.
[1538365.161] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event14)
[1538365.161] (II) No input driver specified, ignoring this device.
[1538365.162] (II) This device may have been added with another device file.
[1538365.162] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event0)
[1538365.162] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[1538365.162] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 28 paused 0
[1538365.162] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[1538365.162] (**) Logitech USB Receiver: always reports core events
[1538365.162] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event0"
[1538365.162] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc521
[1538365.162] (--) evdev: Logitech USB Receiver: Found 20 mouse buttons
[1538365.162] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[1538365.162] (--) evdev: Logitech USB Receiver: Found relative axes
[1538365.162] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[1538365.162] (II) evdev: Logitech USB Receiver: Configuring as mouse
[1538365.162] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[1538365.162] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[1538365.162] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[1538365.162] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/0003:046D:C521.0009/input/input22/event0"
[1538365.162] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 8)
[1538365.162] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[1538365.162] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[1538365.162] (**) Logitech USB Receiver: (accel) acceleration profile 0
[1538365.162] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[1538365.162] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[1538365.162] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[1538365.162] (II) No input driver specified, ignoring this device.
[1538365.162] (II) This device may have been added with another device file.
[1538365.163] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event1)
[1538365.163] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[1538365.163] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 29 paused 0
[1538365.163] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[1538365.163] (**) Logitech USB Receiver: always reports core events
[1538365.163] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event1"
[1538365.163] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc521
[1538365.163] (--) evdev: Logitech USB Receiver: Found 1 mouse buttons
[1538365.163] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[1538365.163] (--) evdev: Logitech USB Receiver: Found relative axes
[1538365.163] (II) evdev: Logitech USB Receiver: Forcing relative x/y axes to exist.
[1538365.163] (--) evdev: Logitech USB Receiver: Found absolute axes
[1538365.163] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[1538365.163] (--) evdev: Logitech USB Receiver: Found keys
[1538365.163] (II) evdev: Logitech USB Receiver: Configuring as mouse
[1538365.163] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[1538365.163] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[1538365.163] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[1538365.163] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[1538365.163] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.1/0003:046D:C521.000A/input/input23/event1"
[1538365.163] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
[1538365.163] (**) Option "xkb_rules" "evdev"
[1538365.163] (**) Option "xkb_model" "pc104"
[1538365.163] (**) Option "xkb_layout" "us"
[1538365.163] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[1538365.163] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[1538365.163] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[1538365.163] (**) Logitech USB Receiver: (accel) acceleration profile 0
[1538365.163] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[1538365.163] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[1538365.164] (II) config/udev: Adding input device Logitech HID compliant keyboard (/dev/input/event2)
[1538365.164] (**) Logitech HID compliant keyboard: Applying InputClass "evdev keyboard catchall"
[1538365.164] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 30 paused 0
[1538365.164] (II) Using input driver 'evdev' for 'Logitech HID compliant keyboard'
[1538365.164] (**) Logitech HID compliant keyboard: always reports core events
[1538365.164] (**) evdev: Logitech HID compliant keyboard: Device: "/dev/input/event2"
[1538365.164] (--) evdev: Logitech HID compliant keyboard: Vendor 0x46d Product 0xc30e
[1538365.164] (--) evdev: Logitech HID compliant keyboard: Found keys
[1538365.164] (II) evdev: Logitech HID compliant keyboard: Configuring as keyboard
[1538365.164] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:046D:C30E.0003/input/input4/event2"
[1538365.164] (II) XINPUT: Adding extended input device "Logitech HID compliant keyboard" (type: KEYBOARD, id 10)
[1538365.164] (**) Option "xkb_rules" "evdev"
[1538365.164] (**) Option "xkb_model" "pc104"
[1538365.164] (**) Option "xkb_layout" "us"
[1538365.164] (II) config/udev: Adding input device Logitech HID compliant keyboard (/dev/input/event3)
[1538365.164] (**) Logitech HID compliant keyboard: Applying InputClass "evdev keyboard catchall"
[1538365.165] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 31 paused 0
[1538365.165] (II) Using input driver 'evdev' for 'Logitech HID compliant keyboard'
[1538365.165] (**) Logitech HID compliant keyboard: always reports core events
[1538365.165] (**) evdev: Logitech HID compliant keyboard: Device: "/dev/input/event3"
[1538365.165] (--) evdev: Logitech HID compliant keyboard: Vendor 0x46d Product 0xc30e
[1538365.165] (--) evdev: Logitech HID compliant keyboard: Found 20 mouse buttons
[1538365.165] (--) evdev: Logitech HID compliant keyboard: Found keys
[1538365.165] (II) evdev: Logitech HID compliant keyboard: Forcing relative x/y axes to exist.
[1538365.165] (II) evdev: Logitech HID compliant keyboard: Configuring as mouse
[1538365.165] (II) evdev: Logitech HID compliant keyboard: Configuring as keyboard
[1538365.165] (**) evdev: Logitech HID compliant keyboard: YAxisMapping: buttons 4 and 5
[1538365.165] (**) evdev: Logitech HID compliant keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[1538365.165] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1/0003:046D:C30E.0004/input/input5/event3"
[1538365.165] (II) XINPUT: Adding extended input device "Logitech HID compliant keyboard" (type: KEYBOARD, id 11)
[1538365.165] (**) Option "xkb_rules" "evdev"
[1538365.165] (**) Option "xkb_model" "pc104"
[1538365.165] (**) Option "xkb_layout" "us"
[1538365.165] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event8)
[1538365.165] (II) No input driver specified, ignoring this device.
[1538365.165] (II) This device may have been added with another device file.
[1538365.165] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event9)
[1538365.165] (II) No input driver specified, ignoring this device.
[1538365.165] (II) This device may have been added with another device file.
[1538365.165] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event10)
[1538365.165] (II) No input driver specified, ignoring this device.
[1538365.165] (II) This device may have been added with another device file.
[1538365.165] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event6)
[1538365.165] (II) No input driver specified, ignoring this device.
[1538365.165] (II) This device may have been added with another device file.
[1538365.165] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event7)
[1538365.165] (II) No input driver specified, ignoring this device.
[1538365.165] (II) This device may have been added with another device file.
[1538365.274] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1538365.274] (II) NVIDIA(GPU-0): Vision stereo.
[1538365.308] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1538365.308] (II) NVIDIA(GPU-0): Vision stereo.
[1548947.132] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1548947.132] (II) NVIDIA(GPU-0): Vision stereo.
[1548947.165] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1548947.165] (II) NVIDIA(GPU-0): Vision stereo.
[1550651.850] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550651.850] (II) NVIDIA(GPU-0): Vision stereo.
[1550652.419] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550652.419] (II) NVIDIA(GPU-0): Vision stereo.
[1550741.435] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550741.435] (II) NVIDIA(GPU-0): Vision stereo.
[1550741.477] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550741.477] (II) NVIDIA(GPU-0): Vision stereo.
[1550748.196] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550748.196] (II) NVIDIA(GPU-0): Vision stereo.
[1550748.237] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550748.237] (II) NVIDIA(GPU-0): Vision stereo.
[1550754.197] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550754.197] (II) NVIDIA(GPU-0): Vision stereo.
[1550755.980] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550755.980] (II) NVIDIA(GPU-0): Vision stereo.
[1550756.023] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550756.023] (II) NVIDIA(GPU-0): Vision stereo.
[1550764.914] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550764.914] (II) NVIDIA(GPU-0): Vision stereo.
[1550764.956] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550764.956] (II) NVIDIA(GPU-0): Vision stereo.
[1550771.497] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550771.497] (II) NVIDIA(GPU-0): Vision stereo.
[1550771.538] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1550771.538] (II) NVIDIA(GPU-0): Vision stereo.
[1556138.380] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1556138.380] (II) NVIDIA(GPU-0): Vision stereo.
[1556138.413] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1556138.413] (II) NVIDIA(GPU-0): Vision stereo.
[1559190.903] (II) config/udev: removing device Logitech USB Receiver
[1559190.903] (II) evdev: Logitech USB Receiver: Close
[1559190.903] (II) UnloadModule: "evdev"
[1559190.903] (II) systemd-logind: releasing fd for 13:64
[1559190.952] (II) config/udev: removing device Logitech USB Receiver
[1559190.952] (II) evdev: Logitech USB Receiver: Close
[1559190.952] (II) UnloadModule: "evdev"
[1559190.952] (II) systemd-logind: releasing fd for 13:65
[1569521.530] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[1569521.530] (II) No input driver specified, ignoring this device.
[1569521.530] (II) This device may have been added with another device file.
[1569521.559] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event0)
[1569521.559] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[1569521.559] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 29 paused 0
[1569521.559] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[1569521.559] (**) Logitech USB Receiver: always reports core events
[1569521.559] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event0"
[1569521.559] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc521
[1569521.559] (--) evdev: Logitech USB Receiver: Found 20 mouse buttons
[1569521.559] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[1569521.559] (--) evdev: Logitech USB Receiver: Found relative axes
[1569521.559] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[1569521.559] (II) evdev: Logitech USB Receiver: Configuring as mouse
[1569521.559] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[1569521.559] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[1569521.559] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[1569521.559] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/0003:046D:C521.000B/input/input24/event0"
[1569521.559] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 8)
[1569521.559] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[1569521.559] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[1569521.559] (**) Logitech USB Receiver: (accel) acceleration profile 0
[1569521.559] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[1569521.559] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[1569521.560] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event1)
[1569521.560] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[1569521.560] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 37 paused 0
[1569521.560] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[1569521.560] (**) Logitech USB Receiver: always reports core events
[1569521.560] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event1"
[1569521.560] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc521
[1569521.560] (--) evdev: Logitech USB Receiver: Found 1 mouse buttons
[1569521.560] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[1569521.560] (--) evdev: Logitech USB Receiver: Found relative axes
[1569521.560] (II) evdev: Logitech USB Receiver: Forcing relative x/y axes to exist.
[1569521.560] (--) evdev: Logitech USB Receiver: Found absolute axes
[1569521.560] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[1569521.560] (--) evdev: Logitech USB Receiver: Found keys
[1569521.560] (II) evdev: Logitech USB Receiver: Configuring as mouse
[1569521.560] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[1569521.560] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[1569521.560] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[1569521.560] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[1569521.560] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.1/0003:046D:C521.000C/input/input25/event1"
[1569521.560] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
[1569521.560] (**) Option "xkb_rules" "evdev"
[1569521.560] (**) Option "xkb_model" "pc104"
[1569521.560] (**) Option "xkb_layout" "us"
[1569521.560] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[1569521.560] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[1569521.560] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[1569521.560] (**) Logitech USB Receiver: (accel) acceleration profile 0
[1569521.560] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[1569521.560] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[1569840.686] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1569840.686] (II) NVIDIA(GPU-0): Vision stereo.
[1569840.776] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1569840.776] (II) NVIDIA(GPU-0): Vision stereo.
[1569841.014] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1569841.014] (II) NVIDIA(GPU-0): Vision stereo.
[1569841.347] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1569841.347] (II) NVIDIA(GPU-0): Vision stereo.
[1569841.380] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1569841.380] (II) NVIDIA(GPU-0): Vision stereo.
[1569844.089] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1569844.089] (II) NVIDIA(GPU-0): Vision stereo.
[1569862.704] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1569862.704] (II) NVIDIA(GPU-0): Vision stereo.
[1569865.088] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1569865.088] (II) NVIDIA(GPU-0): Vision stereo.
[1569865.124] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1569865.124] (II) NVIDIA(GPU-0): Vision stereo.
[1570601.645] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1570601.645] (II) NVIDIA(GPU-0): Vision stereo.
[1570601.678] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1570601.678] (II) NVIDIA(GPU-0): Vision stereo.
[1571210.304] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571210.304] (II) NVIDIA(GPU-0): Vision stereo.
[1571210.337] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571210.337] (II) NVIDIA(GPU-0): Vision stereo.
[1571223.269] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571223.269] (II) NVIDIA(GPU-0): Vision stereo.
[1571232.347] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571232.347] (II) NVIDIA(GPU-0): Vision stereo.
[1571232.398] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571232.398] (II) NVIDIA(GPU-0): Vision stereo.
[1571232.557] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571232.557] (II) NVIDIA(GPU-0): Vision stereo.
[1571232.954] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571232.954] (II) NVIDIA(GPU-0): Vision stereo.
[1571232.987] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571232.987] (II) NVIDIA(GPU-0): Vision stereo.
[1571235.070] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571235.070] (II) NVIDIA(GPU-0): Vision stereo.
[1571244.821] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571244.821] (II) NVIDIA(GPU-0): Vision stereo.
[1571246.208] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571246.208] (II) NVIDIA(GPU-0): Vision stereo.
[1571246.242] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571246.242] (II) NVIDIA(GPU-0): Vision stereo.
[1571995.707] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571995.707] (II) NVIDIA(GPU-0): Vision stereo.
[1571995.740] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1571995.740] (II) NVIDIA(GPU-0): Vision stereo.
[1572958.193] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1572958.193] (II) NVIDIA(GPU-0): Vision stereo.
[1572958.226] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1572958.226] (II) NVIDIA(GPU-0): Vision stereo.
[1572990.958] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1572990.958] (II) NVIDIA(GPU-0): Vision stereo.
[1574042.403] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1574042.403] (II) NVIDIA(GPU-0): Vision stereo.
[1574042.437] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1574042.437] (II) NVIDIA(GPU-0): Vision stereo.
[1574461.211] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1574461.211] (II) NVIDIA(GPU-0): Vision stereo.
[1574461.244] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1574461.244] (II) NVIDIA(GPU-0): Vision stereo.
[1574854.577] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1574854.577] (II) NVIDIA(GPU-0): Vision stereo.
[1574854.611] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1574854.611] (II) NVIDIA(GPU-0): Vision stereo.
[1574920.467] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1574920.467] (II) NVIDIA(GPU-0): Vision stereo.
[1574920.501] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1574920.501] (II) NVIDIA(GPU-0): Vision stereo.
[1575456.776] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1575456.776] (II) NVIDIA(GPU-0): Vision stereo.
[1614848.948] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1614848.948] (II) NVIDIA(GPU-0): Vision stereo.
[1614848.995] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1614848.995] (II) NVIDIA(GPU-0): Vision stereo.
[1614849.072] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1614849.072] (II) NVIDIA(GPU-0): Vision stereo.
[1614849.368] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1614849.368] (II) NVIDIA(GPU-0): Vision stereo.
[1614849.402] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1614849.402] (II) NVIDIA(GPU-0): Vision stereo.
[1614850.513] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1614850.513] (II) NVIDIA(GPU-0): Vision stereo.
[1614860.376] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1614860.377] (II) NVIDIA(GPU-0): Vision stereo.
[1614861.767] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1614861.767] (II) NVIDIA(GPU-0): Vision stereo.
[1614861.801] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1614861.801] (II) NVIDIA(GPU-0): Vision stereo.
[1615455.018] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1615455.018] (II) NVIDIA(GPU-0): Vision stereo.
[1615455.051] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1615455.051] (II) NVIDIA(GPU-0): Vision stereo.
[1615466.381] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1615466.381] (II) NVIDIA(GPU-0): Vision stereo.
[1635286.921] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635286.921] (II) NVIDIA(GPU-0): Vision stereo.
[1635286.968] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635286.968] (II) NVIDIA(GPU-0): Vision stereo.
[1635287.050] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635287.050] (II) NVIDIA(GPU-0): Vision stereo.
[1635287.341] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635287.341] (II) NVIDIA(GPU-0): Vision stereo.
[1635287.374] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635287.374] (II) NVIDIA(GPU-0): Vision stereo.
[1635288.502] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635288.502] (II) NVIDIA(GPU-0): Vision stereo.
[1635300.490] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635300.490] (II) NVIDIA(GPU-0): Vision stereo.
[1635302.609] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635302.609] (II) NVIDIA(GPU-0): Vision stereo.
[1635302.642] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635302.643] (II) NVIDIA(GPU-0): Vision stereo.
[1635587.035] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635587.035] (II) NVIDIA(GPU-0): Vision stereo.
[1635587.068] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635587.068] (II) NVIDIA(GPU-0): Vision stereo.
[1635789.386] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635789.386] (II) NVIDIA(GPU-0): Vision stereo.
[1635789.419] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1635789.419] (II) NVIDIA(GPU-0): Vision stereo.
[1636036.535] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1636036.535] (II) NVIDIA(GPU-0): Vision stereo.
[1636036.568] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1636036.568] (II) NVIDIA(GPU-0): Vision stereo.
[1636273.449] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1636273.449] (II) NVIDIA(GPU-0): Vision stereo.
[1636273.482] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1636273.482] (II) NVIDIA(GPU-0): Vision stereo.
[1636497.080] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1636497.080] (II) NVIDIA(GPU-0): Vision stereo.
[1636497.113] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1636497.113] (II) NVIDIA(GPU-0): Vision stereo.
[1636750.139] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1636750.139] (II) NVIDIA(GPU-0): Vision stereo.
[1636750.172] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1636750.172] (II) NVIDIA(GPU-0): Vision stereo.
[1637086.847] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1637086.847] (II) NVIDIA(GPU-0): Vision stereo.
[1637086.881] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1637086.881] (II) NVIDIA(GPU-0): Vision stereo.
[1637141.213] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1637141.213] (II) NVIDIA(GPU-0): Vision stereo.
[1637141.246] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1637141.246] (II) NVIDIA(GPU-0): Vision stereo.
[1637148.282] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1637148.282] (II) NVIDIA(GPU-0): Vision stereo.
[1637148.316] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1637148.316] (II) NVIDIA(GPU-0): Vision stereo.
[1637297.819] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1637297.819] (II) NVIDIA(GPU-0): Vision stereo.
[1637297.852] (II) NVIDIA(GPU-0): Display (Philips 234CL (DFP-1)) does not support NVIDIA 3D
[1637297.852] (II) NVIDIA(GPU-0): Vision stereo.
[1637382.416] (EE)
[1637382.416] (EE) Backtrace:
[1637382.461] (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x594276]
[1637382.461] (EE) 1: /usr/bin/Xorg.bin (0x400000+0x1983c9) [0x5983c9]
[1637382.461] (EE) 2: /usr/lib/libc.so.6 (0x7f58390c7000+0x33b20) [0x7f58390fab20]
[1637382.461] (EE) 3: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f583228a000+0xe55e1) [0x7f583236f5e1]
[1637382.461] (EE) 4: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f583228a000+0x5c9502) [0x7f5832853502]
[1637382.461] (EE) 5: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f583228a000+0x5cad0a) [0x7f5832854d0a]
[1637382.461] (EE) 6: /usr/bin/Xorg.bin (0x400000+0x1870c7) [0x5870c7]
[1637382.461] (EE) 7: /usr/bin/Xorg.bin (0x400000+0x187a15) [0x587a15]
[1637382.461] (EE) 8: /usr/bin/Xorg.bin (miWideLine+0x46c) [0x589e0c]
[1637382.461] (EE) 9: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f583228a000+0x5ce480) [0x7f5832858480]
[1637382.461] (EE) 10: /usr/bin/Xorg.bin (miPolySegment+0x3e) [0x5815ae]
[1637382.461] (EE) 11: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f583228a000+0x5ce931) [0x7f5832858931]
[1637382.461] (EE) 12: /usr/bin/Xorg.bin (0x400000+0x11cb9d) [0x51cb9d]
[1637382.461] (EE) 13: /usr/bin/Xorg.bin (0x400000+0x33d7a) [0x433d7a]
[1637382.461] (EE) 14: /usr/bin/Xorg.bin (0x400000+0x37807) [0x437807]
[1637382.461] (EE) 15: /usr/bin/Xorg.bin (0x400000+0x3b9a6) [0x43b9a6]
[1637382.461] (EE) 16: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f58390e7040]
[1637382.461] (EE) 17: /usr/bin/Xorg.bin (0x400000+0x25dce) [0x425dce]
[1637382.461] (EE)
[1637382.461] (EE) Segmentation fault at address 0x7f583afcb000
[1637382.461] (EE)
Fatal server error:
[1637382.461] (EE) Caught signal 11 (Segmentation fault). Server aborting
[1637382.461] (EE)
[1637382.461] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[1637382.461] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[1637382.461] (EE)
After a reboot, things are back to normal again, but I never found out the reason for this. I'm open to suggestions what might went wrong.
Current hardware: https://www.smirky.net/info/You're not alone on this it seems, a quick search lead me to an older thread on nVidia forums where several users are complaining about it and links to other threads. Some say that changing minimal powermizer state from 0 to 1 solved it for them (see last post of the thread).
There is also this, and to be honest, it reminds me of random blackscreens I was getting on my 8600m GT and a 260GTX until the screen stayed black not even showing the BIOS screen (PC still booted fine though). In the end I solved it by "baking" my GPUs to re-solder the chip to the mainboard. Both continued to work fine since then. The 8600m GT runs on arch now as you can see from my signature, and no problems with it so far.
May I also add I find the error message sounds hilarious.
edit: found this.
Last edited by Soukyuu (2015-01-07 13:19:45) -
Finder icon fallen off the dock!!!
hi
i have a peculiar bug with the finder icon it seems to have fallen off the dock?
picture here
http://img120.imageshack.us/img120/7756/findericonbugld5.png
anyone else had a similar thing? ive tried relaunching finder but no go, im just about to do a restart to see if that works
cheersrestart did the trick!
whilst im here, ive been trying to compile a script that i can use in salling clicker to switch the default screen to the HDTV so when i use front row it displays on the HDTV
now i thought this would have been quite simple but it turns out the display prefs pane is not scriptable??
with a bit more googling i found this app
http://dl.getdropbox.com/u/28570/Site/TV_Row.html
now this does what i want it to do, but to launch app i still need to get up, go to imac and launch it manually (a great hardship i know ;-))
so now ive been trying to compile a script that launches this app from salling clicker but it has root privilages and for some reason i can launch say mail or safari from terminal but not this app(TV Row)
can anyone help me get thru this?
thanks -
I get an error message in iPhoto when I click on thumbnails of pictures in certain albums. It reads 'the volume for "(file name)" cannot be found. Insert the disk or connect to the server volume and wait for it to appear on the desktop, then try again.' What does this mean and how do I fix it?
It means that you imported the files in Referenced mode and have now remvoed them from the Mac. Put the disk or card back.
For more on iPhoto and file management see this User Tip:
https://discussions.apple.com/docs/DOC-6361 -
How do you turn off the keyboard volume key clicks on macbook pro?
how do you turn off the keyboard volume key clicks on macbook pro?
Thanks for the help!!Thanks! That was easy.
All the Best! -
Hi, I'm having a problem in a VM Guest cluster using Windows Server 2012 R2 and virtual disk sharing enabled.
It's a SQL 2012 cluster, which has around 10 vhdx disks shared this way. all the VHDX files are inside LUNs on a SAN. These LUNs are presented to all clustered members of the Windows Server 2012 R2 Hyper-V cluster, via Cluster Shared Volumes.
Yesterday happened a very strange problem, both the Quorum Disk and the DTC disks got the information completetly erased. The vhdx disks themselves where there, but the info inside was gone.
The SQL admin had to recreated both disks, but now we don't know if this issue was related to the virtualization platform or another event inside the cluster itself.
Right now I'm seen this errors on one of the VM Guest:
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 3/4/2014 11:54:55 AM
Event ID: 1069
Task Category: Resource Control Manager
Level: Error
Keywords:
User: SYSTEM
Computer: ServerDB02.domain.com
Description:
Cluster resource 'Quorum-HDD' of type 'Physical Disk' in clustered role 'Cluster Group' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
<EventID>1069</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-03-04T17:54:55.498842300Z" />
<EventRecordID>14140</EventRecordID>
<Correlation />
<Execution ProcessID="1684" ThreadID="2180" />
<Channel>System</Channel>
<Computer>ServerDB02.domain.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ResourceName">Quorum-HDD</Data>
<Data Name="ResourceGroup">Cluster Group</Data>
<Data Name="ResTypeDll">Physical Disk</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 3/4/2014 11:54:55 AM
Event ID: 1558
Task Category: Quorum Manager
Level: Warning
Keywords:
User: SYSTEM
Computer: ServerDB02.domain.com
Description:
The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
<EventID>1558</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>42</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-03-04T17:54:55.498842300Z" />
<EventRecordID>14139</EventRecordID>
<Correlation />
<Execution ProcessID="1684" ThreadID="2180" />
<Channel>System</Channel>
<Computer>ServerDB02.domain.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="NodeName">ServerDB02</Data>
</EventData>
</Event>
We don't know if this can happen again, what if this happens on disk with data?! We don't know if this is related to the virtual disk sharing technology or anything related to virtualization, but I'm asking here to find out if it is a possibility.
Any ideas are appreciated.
Thanks.
Eduardo RojasHi,
Please refer to the following link:
http://blogs.technet.com/b/keithmayer/archive/2013/03/21/virtual-machine-guest-clustering-with-windows-server-2012-become-a-virtualization-expert-in-20-days-part-14-of-20.aspx#.Ux172HnxtNA
Best Regards,
Vincent Wu
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
Hi,
I just want to know how to assign quorum disk under Sun cluster. Can I use LUN disk that is shared for both node as quorum disk and do I need to bring the disk first to vxvm control before using it as quorum disk? Appreciate any response/advise.
Thanks.No you don't need to bring the disk into VXVM control.
First run scdidadm -L from either node. This will give you a list of shared disk devices. Find one that is shared between the nodes and note its DID. ie d21
scconf -a -q globaldev=d21
Once you have added a quorum disk you can set install mode to off.
scconf -c -q installmodeoff
I would also recommend reading this:
http://docs.sun.com/app/docs/doc/816-3384/6m9lu6fig?q=sun+cluster+add+quorum+disk&a=view
Then reset you quorum count.
scconf -c -q reset -
Failover cluster - get disk path ?
Hi
i have created a failover cluster, with two disk cluster disk1 and cluster disk 2, is there any powershell command which can get me the path of the disk. like return value should be S:/
Thanks
Sid
sidHi sidhanttiwari,
Additional, you can refer the following related article to get more information about your shared storage.
PowerShell for Failover Clustering: CSV Free Disk Space (and other info)
http://blogs.msdn.com/b/clustering/archive/2010/06/19/10027366.aspx
Understanding the state of your Cluster Shared Volumes in Windows Server 2012 R2
http://blogs.msdn.com/b/clustering/archive/2013/12/05/10474312.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
2 Node Failover Cluster - ISCSI Disks as 1 volume?
Hi,
Not sure if I'm in the correct forum. If I am I apologize. I need some advice.
I have created a 2-node failover cluster with 2 HP Blades. I also currently have 2 NAS Servers (HP X1600 24tb servers running 2008 Storage server) -- The ultimate goal would be to combine all of the storage space from the NAS's into 1 volume addressable
by the failover cluster. (As well as disk space from any additional NAS's added in the future.)
Right now, I can add the ISCSI disk space from the NAS Targets as different volumes under cluster shared volumes. Because of the 16TB limit in the ISCSI target, I essentially have 2 ISCSI disks on each NAS. One for 16TB, and the other for 4TB (The
NAS Drives are configured for RAID 5 so there's a 4TB Loss.) So, I have 4 ISCSI disks in the cluster, each as their own volume.
Any thoughts on making the 4 drives addressable as one volume?
Regards,
-EricWe're running Server 2012 Data Center on the cluster nodes.
I was thinking the same about the 3rd party software to do what I'd like it to do. The data is mostly security camera video from our security system. Since its not really critical data, i'm just looking for a way to maximize
the available hard drive space, and make it addressable as one volume or network share...
-Eric
You can build Storage Spaces (simple, not clustered as it would waste 50% of your capacity, MSFT can do mirror and parity with R2 for clustered only) from iSCSI LUs. Dog slow and unsupported but you'll have linear spanned space. See:
Rough Guide To Setting Up A Scale-Out File Server
http://www.aidanfinn.com/?p=13176
Creating Virtual SoFS with shared VHDX
http://www.aidanfinn.com/?p=15145
you don;t need SoFS (obviously) but in this article Aidan creates Storage Spaces from iSCSI LUNs.
Good luck!
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts. -
Hello Community
When you setup a Sharepoint 2013 Server farm
if you want to provide failover clustering, can
the servers that the Sharepoint 2013 Server farm
failover to be located off-site in a different
location (i.e. how far away can the servers the
the primary server in the Sharepoint 2013 Server
farm be away from the failover cluster of backup
Sharepoint 2013 Server farm servers in distance?
Thank you
ShabeautHiya,
this article describes in detail the different aspects of creating a highly available SharePoint 2013 server farm.
Create a high availability architecture and strategy for SharePoint 2013
http://technet.microsoft.com/en-us/library/cc748824%28v=office.15%29.aspx -
How do you turn off the sharing of emails of Lion to iCloud?
Is it possible to turn off the automatic sharing to iCloud in OS10.7? If this is possible I would like to know how.
Yes you are correct, however when you do that it also removes your me email address and its mail from your computer. That should be a preference of the individual user. Just because Apple wants to push everything to the cloud doesnot mean we all want everything to the cloud. In order fo rme to keep that email address I was forced to go to Lion, before you realize it all of your .me email goes to the cloud.
-
Why is my iMac dropping off as shared volume- Back-to-My-Mac
I have a 21.5" iMac 2.5GHz mid 2011, 12GB ram running Lion 10.7.4.
It is connected via ethernet to a gen 5 Airport Extreme, so Airport on the iMac is off. I am also running a MBP .
Both are on iCloud Back-to-My-Mac. When the iMac is awake, it shows up on the MBP as a shared volume. After it goes to sleep, it disappears as a shared volume. Wake for network activity is checked on the iMac. Sometimes it takes a little bit of time, but it always drops off after it goes to sleep.
I don't remember having this problem before. The only thing I have changed is that I had been using a 1st gen Airport Extreme and upgraded to this 5th gen.
I've checked everything I can think of but the problem persists.
Anyone have any thoughts as to why the iMac keeps disappearing?I have a 21.5" iMac 2.5GHz mid 2011, 12GB ram running Lion 10.7.4.
It is connected via ethernet to a gen 5 Airport Extreme, so Airport on the iMac is off. I am also running a MBP .
Both are on iCloud Back-to-My-Mac. When the iMac is awake, it shows up on the MBP as a shared volume. After it goes to sleep, it disappears as a shared volume. Wake for network activity is checked on the iMac. Sometimes it takes a little bit of time, but it always drops off after it goes to sleep.
I don't remember having this problem before. The only thing I have changed is that I had been using a 1st gen Airport Extreme and upgraded to this 5th gen.
I've checked everything I can think of but the problem persists.
Anyone have any thoughts as to why the iMac keeps disappearing? -
Server 2012 Failover Cluster No Disks available / iSCSI
Hi All,
I am testing out the Failover Clustering on Windows Server 2012 with hopes of winding up with a clustered File Server once I am done.
I am starting with a single node in the cluster for testing purposes; I have connected to this cluster a single iSCSI LUN that is 100GB in size.
When I right click on Storage -> Disks and then click 'Add Disk', I get No disks suitable for cluster disks were found.
I get this, even if I add a second server to the cluster, and connect it to the iSCSI drive as well.
Any ideas?Hi All,
I am testing out the Failover Clustering on Windows Server 2012 with hopes of winding up with a clustered File Server once I am done.
I am starting with a single node in the cluster for testing purposes; I have connected to this cluster a single iSCSI LUN that is 100GB in size.
When I right click on Storage -> Disks and then click 'Add Disk', I get No disks suitable for cluster disks were found.
I get this, even if I add a second server to the cluster, and connect it to the iSCSI drive as well.
Any ideas?
For testing purpose you'd better spawn a set of VMs on a single physical Hyper-V host and use shared VHDX as a back clusterd storage. That would be both much easier and much faster then what you do. + it would be trivial move one of the VMs to another physical
host, shared VHDX to CSV on a shared storage and go from Test & Development to production :) See:
Shared VHDX
http://blogs.technet.com/b/storageserver/archive/2013/11/25/shared-vhdx-files-my-favorite-new-feature-in-windows-server-2012-r2.aspx
Virtual File Server with Shared VHDX
http://www.aidanfinn.com/?p=15145
Guest
VM Cluster with Shared VHDX
http://technet.microsoft.com/en-us/library/dn265980.aspx
For a pure iSCSI scenario you may try this step-by-step guide (just skip StarWind config as you do have a shared storage already with your SAN). See:
Configuring HA File Server on Windows Server 2012 for SMB NAS
http://www.starwindsoftware.com/configuring-ha-file-server-on-windows-server-2012-for-smb-nas
Hope this helped a bit :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts. -
It indicates the file for the photo is missing, which may be related to the fact I had to restore my computer recently but I can't get rid of the warning, by the options, cancel, ok, or find photo. I don't know where they have gone, or where to search, other than Finder, which does not list them. They are not that important to me but Ido not know which photos the warnings are about, if I did I could go into the event and delete them.
This happens
1. when you run a Referenced Library - where the files are not copied to the iPhoto Library on import - that means you chose to do the File Management.
2. The files are stoed on another disk (or volume)
3. iPhoto can't find that disk (or volume)
So, the solution is to plug in the disk so that iPhoto can access it.
If you don't have the disk, or the photos concerned, then you have a corrupted Library.
How to proceed from there depends on the actual version of iPhoto you use.
BTW you do know exactly what photos are missing - the message tells you. But I think you'll find that iPhoto needs the file in order to delete it.
Regards
TD
Maybe you are looking for
-
Creation of EBP Purchase Order for Service Products in MM
Hello all, i have created the service master in MM system and then i have replicated the service master to EBP later i tried to create a EBP PO for Service Products through Sourcing from EBP to MM. But i am getting a failure message as "Error during
-
How do I stream movies from my tablet to tv using Appletv?
How do you stream movies from iPad to tv with Apple tv?
-
Intercompany billing - using condition type PI01 = VPRS
In the intercompany billing we are going to configure the condition type PI01 to copy the amount in the condition type VPRS in the order. Can anyone give me a proposal of how to do this?
-
When notified that my bill is available to view I get: The Billing service is unavailable at the moment - however please do use links on this page for other services available. Please accept our apologies for any inconvenience - we'll be back shortly
-
Where is Siri on my iphone 4S???
OK, I go to Settings>General> ....and then there is no tag for Siri. Where it should be, I have "Spotlight Search" Is it somewhere else? Thanks in advance, Braden