Failed to create commande process
Hi,
in 10G R2 on Win 2003 server,
I created a (host) job in DB Control (OEM) it should do the following on the host :
dir d:But it fails with :
Error : Failed to create commande processI found the following and verified it was already done:
If you are running your 10g database on Windoz system then
Go to start->Administrative tools->Local security policy
and under security settings->Local Policies->User Rights Assignment
double click on Log on as a batch job
in there add the os user to that group
This then should fix the error, its a 10g bugand despite of that , my job does not run.
Any idea ?
Thank you.
Manually creating and submitting job may help you. See thread Re: RMAN in scheduler
Regards
Similar Messages
-
Hi all,
we have a huge Java (JRE 6.0.310.5) app that works fine on the Win 8 CTP, but on RP:
Failed to create new process "C:\Program Files (x86)\...\jre\bin\javaw.exe" - Invalid Argument
Thanks for any insight
G.Hi,
Based on the error message 'Caused by: com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, only role administrators is allowed to access JMX' , this note shall solve this issue:
948970 - Caller J2EE_GUEST not authorized, only role administrators
Also check if the ADSUSER and ADS_AGENT have the correct password and the respective roles.
944221 - Error analysis for problems in form processing (ADS)
Which is your NW version?
Regards,
Lucas Comassetto. -
Failed to create a user with Mac Mini Server, the message "Failed to process the command writesettings" in the module "servermgr_sharing"
I have a Mac Mini with OS X Server 10.8.5 and Server 2.2.1 and have a problem to share the public folder.
When I enter the Server application to indicate that I want to share the public folder on the network and assign user I get the following message appears
And I can not share the folder.
If I go from my i-mac get mac mini server view and access the public folder, but I can not open any of the files there.
That I can do to fix this?
thank you very much -
Failed to create Process mutex
When trying to start the FMS services using FMSMaster.exe -console using the command promt I am repeatedly getting the "Failed to create process mutex"
Please help.Hi Asa
Thanks for your answer.
Bad news are good news - at least I know what is going on.
But I am pretty sure it is a bug. Probably, in the passing parameters into the CreateMutex function.
The funny thing, FMSHttpd works under DOMAIN account, but FMS does not.
I hope you can raise an issue for the next version of FMS.
The problem is that in the Enterprise network we have to store data files on the Network Access Storage. In this case we will be able not worry where to install FMS.
For now, we have to put all files onto the server, where FMS is installed. Not good....
Anyway, Thanks for you answer. And hope your team will fix this issue. -
Hello,
I get the following error (in the logs) right after hitting the install button within the iTunes 64bit installation program:
Executing: C:\Users\Travis\AppData\Local\Temp\IXP651.TMP\SetupAdmin.exe /evt EFEB /pid 3872 /mon 448 460
ShellExecuteEx( C:\Users\Travis\AppData\Local\Temp\IXP651.TMP\SetupAdmin.exe /evt EFEB /pid 3872 /mon 448 460 ) failed to create process. GetLastError() = 2L
ExitCode = 2L
InstallPackages exiting. ==> 2L
MSI (c) (50:1C) [04:47:57:639]: Leaked MSIHANDLE (11) of type 790540 for thread 3796
MSI (c) (50:1C) [04:47:57:639]: Leaked MSIHANDLE (10) of type 790541 for thread 3796
MSI (c) (50:1C) [04:47:57:639]: Note: 1: 2769 2: InstallPackages 3: 2
DEBUG: Error 2769: Custom Action InstallPackages did not close 2 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: InstallPackages, 2,
CustomAction InstallPackages returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 4:47:57: InstallPackages. Return value 3.
MSI (c) (50:24) [04:47:57:639]: Doing action: SetupCompleteError
Action 4:47:57: SetupCompleteError.
Action start 4:47:57: SetupCompleteError.
DEBUG: Error 2836: The control Back on the dialog SetupCompleteError can not take focus
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2836. The arguments are: SetupCompleteError, Back,
Action 4:47:57: SetupCompleteError. Dialog created
I have cleaned out the temp folder for the account in question and uninstalled prior version of iTunes.
What can I do to get past this error and install iTunes?
Thank you in advance for your time.Pls check: http://forums.adobe.com/message/5864897
Level: Easy to solve.
Cause: This is because Chinese (or any non-English) windows (Microsoft's responsibility!) cannot read special letter such as copyright / registration symbol from so-called "non-Unicode program" (actually, this microsoft-invented term just means any software with english-as-medium of installation instruction/ path). It happens all the time when installing softwares. I just don't know why microsoft does not fix it.
Solution:
Control Panel > Clock, Language, and Region > Region and Language> Administrative tab > Language for non-Unicode programs > Change system locale > Change Chinese (or any non-English setting) to English
This allows non-Unicode programs to run on your computer using the specified language.
Option: You may change the "region and language" back to original setting after sucessful installation.
Refs:
http://support.muse.adobe.com/thread/1280610?tstart=0
http://windows.microsoft.com/is-is/windows/change-system-locale#1TC=windows-7 -
Oracle EM Grid Control Error: Failed to run command in process
I am trying to change "Backup Settings". After entering the Host Credentials, when I click the OK button, I receive the following error message.
Validation Error
Examine and correct the following errors, then retry the operation:
Error - Connection to host as user <user> failed.ERROR: Failed to run command in process
Any Suggestions? Thanks in advance!Hi,
If you are using linux/windows the hostname credentials should be the user who has installed the oracle 10g database software, if Windosw the user you are using need to be member of the ora_dba group and have Local Security privilege 'Log on as a batch job'.
What you need to do is go to start----> Programs----> admin tools----> Local security policy --->local policies ---> user rights assignments
In the list to your right, look for 'Log on as a batch job', double click and add the same OS local user you using to access OEM web to the group.
I hope this will solve your problem.
Cheers,
Francisco Munoz Alvarez
http://www.oraclenz.com -
SCCM 2012 SP1 Install fails at splash screen: Failed to create process of setupWpf.exe
Hello,
I can't seem to get past the initial install screen. When I click install I receive what is shown in the screen shot. The error in question is "Failed to create process of SetupWpf.exe" This is what I get after i click install. The error above
that one "WinHttpReceiveresponse failed 80072ee7" is what I get when I tried to download the latest updates from the splash screen. It was on like update 44 of 56 when it failed but I am not sure I need to pursue that one. I cant even get the insall
going.
Phil BalderosI am also having the same issue..
I can start the sccm 2012 installation piror to installing SQL 2012 SP1. Once SQL installation is complete, and try to install sccm 2012 -> issue occur. Is this a sql issue, or a sccm 2012 issue.. I have download the SQL 2012 and SCCM 2012 FROM MS
twics.. I have rebuilt my lab twice already ...
Any help, not sure what step I am missing....
Hello Yuyut,
This issue is related to CM12 (not nessarly a widly known issue) perhaps something with the ISO. The copy I was using was from our MSDN subscription which kept failing. I downloaded it twice and still same issue. Since I am setting this up as a lab
for testing purposes I just ended up downloaded the 180 day evaluation and has worked for me so far. So again this is not related to SQL as I have noticed.
Thorsten did mention on this thred that I should check permissons of the account I was trying to install it from. That was not my issue but you could give that a look also.
Phil
Phil Balderos -
Startx on a vmware is throwing a "failed to create screen resources"
The Bottom line error is:
Fatal server error:
[ 1431.076] (EE) failed to create screen resources(EE)
I am trying to get a browsers running on my new Arch Linux, so I can cut and paste better for questions. I have installed xorg, chromium, firefox. If I try and start "startx", it say the server did not start. I think it is the failed to create screen resources.
I have edit the video settings to give it 32meg of memory. Also I hack the .vmx file to enable the 3d opttion. I have installed all the vmtools (open version) Again, new to Arch Linux so I sure it is something stupid.
Not sure if it helps but here are the errors when I try and run the browsers.
chromium
[320:320:1121/142755:Error:browser_main_loop.cc(209) Gtk: cannot open display:
firefox
(process:354): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Error: no display specified
Entire log Xorg.0.log
[ 1430.963]
X.Org X Server 1.16.2
Release Date: 2014-11-10
[ 1430.965] X Protocol Version 11, Revision 0
[ 1430.965] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 1430.967] Current Operating System: Linux PingBuild 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64
[ 1430.967] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=36544952-8a9a-41c9-b169-87189310b752 rw quiet
[ 1430.969] Build Date: 10 November 2014 07:52:13PM
[ 1430.970]
[ 1430.970] Current version of pixman: 0.32.6
[ 1430.972] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 1430.972] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1430.975] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 21 12:53:21 2014
[ 1430.976] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 1430.976] (==) No Layout section. Using the first Screen section.
[ 1430.976] (==) No screen section available. Using defaults.
[ 1430.976] (**) |-->Screen "Default Screen Section" (0)
[ 1430.976] (**) | |-->Monitor "<default monitor>"
[ 1430.976] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 1430.976] (==) Automatically adding devices
[ 1430.976] (==) Automatically enabling devices
[ 1430.976] (==) Automatically adding GPU devices
[ 1430.976] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 1430.976] Entry deleted from font path.
[ 1430.976] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 1430.976] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 1430.976] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 1430.976] (II) Loader magic: 0x818d80
[ 1430.976] (II) Module ABI versions:
[ 1430.976] X.Org ANSI C Emulation: 0.4
[ 1430.976] X.Org Video Driver: 18.0
[ 1430.976] X.Org XInput driver : 21.0
[ 1430.976] X.Org Server Extension : 8.0
[ 1430.979] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 1430.979] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 1430.983] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 1431.010] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xd8000000/67108864, 0xd0800000/8388608, I/O @ 0x000010d0/16, BIOS @ 0x????????/32768
[ 1431.010] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 1431.010] (II) LoadModule: "glx"
[ 1431.011] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 1431.016] (II) Module glx: vendor="X.Org Foundation"
[ 1431.016] compiled for 1.16.2, module version = 1.0.0
[ 1431.016] ABI class: X.Org Server Extension, version 8.0
[ 1431.016] (==) AIGLX enabled
[ 1431.016] (==) Matched vmware as autoconfigured driver 0
[ 1431.016] (==) Matched vmware as autoconfigured driver 1
[ 1431.016] (==) Matched modesetting as autoconfigured driver 2
[ 1431.016] (==) Matched fbdev as autoconfigured driver 3
[ 1431.016] (==) Matched vesa as autoconfigured driver 4
[ 1431.016] (==) Assigned the driver to the xf86ConfigLayout
[ 1431.016] (II) LoadModule: "vmware"
[ 1431.017] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[ 1431.044] (II) Module vmware: vendor="X.Org Foundation"
[ 1431.044] compiled for 1.16.0, module version = 13.0.2
[ 1431.044] Module class: X.Org Video Driver
[ 1431.044] ABI class: X.Org Video Driver, version 18.0
[ 1431.044] (II) LoadModule: "modesetting"
[ 1431.044] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 1431.044] (II) Module modesetting: vendor="X.Org Foundation"
[ 1431.044] compiled for 1.16.0, module version = 0.9.0
[ 1431.044] Module class: X.Org Video Driver
[ 1431.044] ABI class: X.Org Video Driver, version 18.0
[ 1431.044] (II) LoadModule: "fbdev"
[ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 1431.045] (II) Module fbdev: vendor="X.Org Foundation"
[ 1431.045] compiled for 1.16.0, module version = 0.4.4
[ 1431.045] Module class: X.Org Video Driver
[ 1431.045] ABI class: X.Org Video Driver, version 18.0
[ 1431.045] (II) LoadModule: "vesa"
[ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 1431.045] (II) Module vesa: vendor="X.Org Foundation"
[ 1431.045] compiled for 1.16.0, module version = 2.3.2
[ 1431.045] Module class: X.Org Video Driver
[ 1431.045] ABI class: X.Org Video Driver, version 18.0
[ 1431.045] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
[ 1431.045] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 1431.045] (II) FBDEV: driver for framebuffer: fbdev
[ 1431.045] (II) VESA: driver for VESA chipsets: vesa
[ 1431.045] (++) using VT number 1
[ 1431.045] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 1431.045] (WW) Falling back to old probe method for modesetting
[ 1431.045] (WW) Falling back to old probe method for fbdev
[ 1431.045] (II) Loading sub module "fbdevhw"
[ 1431.045] (II) LoadModule: "fbdevhw"
[ 1431.046] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 1431.046] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 1431.046] compiled for 1.16.2, module version = 0.0.2
[ 1431.046] ABI class: X.Org Video Driver, version 18.0
[ 1431.046] (WW) Falling back to old probe method for vesa
[ 1431.046] (II) vmware(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 1431.046] (--) vmware(0): DRM driver version is 2.6.1
[ 1431.046] (==) vmware(0): Depth 24, (--) framebuffer bpp 32
[ 1431.046] (==) vmware(0): RGB weight 888
[ 1431.046] (==) vmware(0): Default visual is TrueColor
[ 1431.046] (--) vmware(0): Min width 1, Max Width 8192.
[ 1431.046] (--) vmware(0): Min height 1, Max Height 8192.
[ 1431.047] (II) vmware(0): Output Virtual1 has no monitor section
[ 1431.047] (II) vmware(0): Output Virtual2 has no monitor section
[ 1431.047] (II) vmware(0): Output Virtual3 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual4 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual5 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual6 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual7 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual8 has no monitor section
[ 1431.048] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 1431.048] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
[ 1431.049] (II) vmware(0): Printing probed modes for output Virtual1
[ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
[ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1431.049] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1431.049] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 1431.049] (II) vmware(0): EDID for output Virtual2
[ 1431.049] (II) vmware(0): EDID for output Virtual3
[ 1431.049] (II) vmware(0): EDID for output Virtual4
[ 1431.049] (II) vmware(0): EDID for output Virtual5
[ 1431.049] (II) vmware(0): EDID for output Virtual6
[ 1431.049] (II) vmware(0): EDID for output Virtual7
[ 1431.049] (II) vmware(0): EDID for output Virtual8
[ 1431.049] (II) vmware(0): Output Virtual1 connected
[ 1431.049] (II) vmware(0): Output Virtual2 disconnected
[ 1431.049] (II) vmware(0): Output Virtual3 disconnected
[ 1431.049] (II) vmware(0): Output Virtual4 disconnected
[ 1431.049] (II) vmware(0): Output Virtual5 disconnected
[ 1431.049] (II) vmware(0): Output Virtual6 disconnected
[ 1431.049] (II) vmware(0): Output Virtual7 disconnected
[ 1431.049] (II) vmware(0): Output Virtual8 disconnected
[ 1431.049] (II) vmware(0): Using exact sizes for initial modes
[ 1431.049] (II) vmware(0): Output Virtual1 using initial mode 800x600
[ 1431.049] (II) vmware(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 1431.049] (==) vmware(0): DPI set to (96, 96)
[ 1431.049] (II) Loading sub module "fb"
[ 1431.049] (II) LoadModule: "fb"
[ 1431.049] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 1431.050] (II) Module fb: vendor="X.Org Foundation"
[ 1431.050] compiled for 1.16.2, module version = 1.0.0
[ 1431.050] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1431.050] (II) Loading sub module "dri2"
[ 1431.050] (II) LoadModule: "dri2"
[ 1431.050] (II) Module "dri2" already built-in
[ 1431.050] (II) UnloadModule: "modesetting"
[ 1431.050] (II) Unloading modesetting
[ 1431.050] (II) UnloadModule: "fbdev"
[ 1431.050] (II) Unloading fbdev
[ 1431.050] (II) UnloadSubModule: "fbdevhw"
[ 1431.050] (II) Unloading fbdevhw
[ 1431.050] (II) UnloadModule: "vesa"
[ 1431.050] (II) Unloading vesa
[ 1431.050] (==) Depth 24 pixmap format is 32 bpp
[ 1431.050] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[ 1431.064] (II) vmware(0): Gallium3D XA version: 2.2.0.
[ 1431.064] (II) vmware(0): Path of drm device is "/dev/dri/card0".
[ 1431.064] (II) vmware(0): [DRI2] Setup complete
[ 1431.064] (II) vmware(0): [DRI2] DRI driver: vmwgfx
[ 1431.064] (--) vmware(0): Render acceleration is enabled.
[ 1431.064] (==) vmware(0): Rendercheck mode is disabled.
[ 1431.064] (--) vmware(0): Direct rendering (3D) is enabled.
[ 1431.064] (==) vmware(0): Direct presents are disabled.
[ 1431.064] (==) vmware(0): Hardware only presents are disabled.
[ 1431.064] (==) vmware(0): Backing store enabled
[ 1431.064] (==) vmware(0): Silken mouse enabled
[ 1431.064] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 1431.064] (==) vmware(0): DPMS enabled
[ 1431.064] (--) RandR disabled
[ 1431.075] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context
[ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1431.075] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 1431.075] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1431.075] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1431.075] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1431.075] (II) AIGLX: Loaded and initialized vmwgfx
[ 1431.075] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1431.076] (EE)
Fatal server error:
[ 1431.076] (EE) failed to create screen resources(EE)
[ 1431.076] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 1431.076] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 1431.076] (EE)
[ 1431.076] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 1431.076] (WW) vmware(0): drmDropMaster failed: Invalid argument
[ 1431.079] (EE) Server terminated with error (1). Closing log file.
Journal since boot
-- Logs begin at Wed 2014-11-19 16:23:50 CST, end at Fri 2014-11-21 14:25:54 CST. --
Nov 21 14:17:03 PingBuild kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xfeff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:00.0: [8086:7190] type 00 class 0x060000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: [8086:7191] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.0: [8086:7110] type 00 class 0x060100
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: [8086:7111] type 00 class 0x01018a
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: reg 0x20: [io 0x10c0-0x10cf]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: [8086:7113] type 00 class 0x068000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1000-0x103f] claimed by PIIX4 ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1040-0x104f] claimed by PIIX4 SMB
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: [15ad:0740] type 00 class 0x088000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x10: [io 0x1080-0x10bf]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x14: [mem 0xd0000000-0xd0001fff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: [15ad:0405] type 00 class 0x030000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x10: [io 0x10d0-0x10df]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x14: [mem 0xd8000000-0xdbffffff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x18: [mem 0xd0800000-0xd0ffffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x00007fff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: [1000:0030] type 00 class 0x010000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x10: [io 0x1400-0x14ff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x14: [mem 0xd0040000-0xd005ffff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x1c: [mem 0xd0020000-0xd003ffff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x00003fff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: [15ad:0790] type 01 class 0x060401
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [32] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [33] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [34] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [35] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [36] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [37] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [38] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [39] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [40] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [41] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [42] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [43] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [44] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [45] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [46] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [47] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [48] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [49] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [50] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [51] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [52] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [53] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [54] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [55] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [56] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [57] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [58] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [59] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [60] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [61] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [62] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [63] registered
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: [8086:100f] type 00 class 0x020000
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x10: [mem 0xd1020000-0xd103ffff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x18: [mem 0xd1000000-0xd100ffff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x20: [io 0x2000-0x203f]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000cc000-0x000cffff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xc0000000-0xfebfffff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0d00-0xfeff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xd3e00000-0xd3efffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xdd400000-0xdd4fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PCI bridge to [bus 1a]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xd4200000-0xd42fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xdd600000-0xdd6fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PCI bridge to [bus 1b]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [io 0x7000-0x7fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd2700000-0xd27fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd4700000-0xd47fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PCI bridge to [bus 1c]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [io 0xb000-0xbfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd2b00000-0xd2bfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd4a00000-0xd4afffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PCI bridge to [bus 1d]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0xf000-0xffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd2f00000-0xd2ffffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd4c00000-0xd4cfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PCI bridge to [bus 1e]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd3300000-0xd33fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd4e00000-0xd4efffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PCI bridge to [bus 1f]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd3700000-0xd37fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd5000000-0xd50fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PCI bridge to [bus 20]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd3b00000-0xd3bfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd5200000-0xd52fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PCI bridge to [bus 21]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd3f00000-0xd3ffffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd5400000-0xd54fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PCI bridge to [bus 22]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd4300000-0xd43fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd5600000-0xd56fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *9 10 11 14 15)
Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 14 15)
Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 14 15)
Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
Nov 21 14:17:03 PingBuild kernel: ACPI: Enabled 2 GPEs in block 00 to 0F
Nov 21 14:17:03 PingBuild kernel: vgaarb: setting as boot device: PCI:0000:00:0f.0
Nov 21 14:17:03 PingBuild kernel: vgaarb: device added: PCI:0000:00:0f.0,decodes=io+mem,owns=io+mem,locks=none
Nov 21 14:17:03 PingBuild kernel: vgaarb: loaded
Nov 21 14:17:03 PingBuild kernel: vgaarb: bridge control possible 0000:00:0f.0
Nov 21 14:17:03 PingBuild kernel: PCI: Using ACPI for IRQ routing
Nov 21 14:17:03 PingBuild kernel: PCI: pci_cache_line_size set to 64 bytes
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: can't claim BAR 13 [io 0xf000-0xffff]: no compatible bridge window
Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0xbfef0000-0xbfffffff]
Nov 21 14:17:03 PingBuild kernel: NetLabel: Initializing
Nov 21 14:17:03 PingBuild kernel: NetLabel: domain hash size = 128
Nov 21 14:17:03 PingBuild kernel: NetLabel: protocols = UNLABELED CIPSOv4
Nov 21 14:17:03 PingBuild kernel: NetLabel: unlabeled traffic allowed by default
Nov 21 14:17:03 PingBuild kernel: HPET: 16 timers in total, 0 timers will be used for per-cpu timer
Nov 21 14:17:03 PingBuild kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
Nov 21 14:17:03 PingBuild kernel: hpet0: 16 comparators, 64-bit 14.318180 MHz counter
Nov 21 14:17:03 PingBuild kernel: Switched to clocksource hpet
Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI init
Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1000-0x103f] could not be reserved
Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1040-0x104f] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x0cf0-0x0cf1] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f13 (active)
Nov 21 14:17:03 PingBuild kernel: system 00:04: [mem 0xfed00000-0xfed003ff] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:04: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:08: [dma 2]
Nov 21 14:17:03 PingBuild kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0700 (active)
Nov 21 14:17:03 PingBuild kernel: system 00:09: [io 0x1060-0x107f] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xe0000000-0xefffffff] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xd0200000-0xd03fffff] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI: found 10 devices
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [io 0x1000-0x0fff] to [bus 06] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [io 0x1000-0x0fff] to [bus 07] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [io 0x1000-0x0fff] to [bus 08] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [io 0x1000-0x0fff] to [bus 09] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [io 0x1000-0x0fff] to [bus 0a] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [io 0x1000-0x0fff] to [bus 0e] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [io 0x1000-0x0fff] to [bus 0f] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [io 0x1000-0x0fff] to [bus 10] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [io 0x1000-0x0fff] to [bus 11] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [io 0x1000-0x0fff] to [bus 12] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [io 0x1000-0x0fff] to [bus 16] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [io 0x1000-0x0fff] to [bus 17] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [io 0x1000-0x0fff] to [bus 18] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [io 0x1000-0x0fff] to [bus 19] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [io 0x1000-0x0fff] to [bus 1a] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0x1000-0x0fff] to [bus 1d] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [io 0x1000-0x0fff] to [bus 1e] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [io 0x1000-0x0fff] to [bus 1f] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [io 0x1000-0x0fff] to [bus 20] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [io 0x1000-0x0fff] to [bus 21] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [io 0x1000-0x0fff] to [bus 22] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: BAR 6: assigned [mem 0xc0000000-0xc0007fff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: BAR 6: assigned [mem 0xc0008000-0xc000bfff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: BAR 6: assigned [mem 0xd1010000-0xd101ffff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: briTrilby wrote:
Thanks, that all sounds correct to me, unfortunalte I can't provide more help as I've never used vmware. But a couple pointers for pacman use:
There is no need to use that pipe, `pacman -Q <searchterm>` will work.
The reason you don't see the mouse package is that grep is case sensitive. `pacman -Q | grep -i vmware` should also show the mouse package, but this would be much easier as `pacman -Qs vmware` which allows pacman to do the search. Pacman's search is case-insensitive by default and is a bit more effient that listing all packages and grepping through them.
Got it. Yes using the 'vmware' the vmmouse shows up. Also searching 'svga' shows Mesa DRI drivers. That is another advantage for letting pacman search, since my search term was svga and what was dispalayed did not have that in the string, pacman search can see behind the covers. :-)
All this learning is good, now if I could just figure out why 'startx' is failing to create screen resource. ;-)
Question, does it matter what tty it starts on? I am using 0 (obvious from the log name), could that be an issue? Just thinking out loud. -
Hello -
I'm hoping someone could help me with this problem. I've searched so many websites trying to resolve this issue and it seems no matter what I try I keep getting the same error message.
I've followed the steps in setting up SCCM 07 from this web site which was very nicely done! I've also followed the directions on Microsofts Tech Net website on how to configure WebDav and IIS settings.
I'm working on a Virtual Windows Server 2008 32-bit OS, SP2, SCCM 07 SP2, IIS7
Here is the message I get in the log files:
Message ID: 4963
Process ID: 4364
Thread ID: 7996
Componet: SMS_MP_CONTROL_MANAGER
MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.
Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties.
Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties.
Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.
I could be completely wrong but I read somewhere that with the latest version of IIS doesn't install these user accounts. I checked to see if those accounts existed and they didn't.
I've tried what this one website mentioned:
http://myitforum.com...-directory.aspx
- Remove the MP role from the Site Server. Watch the MPSetup.log to ensure that the removal is complete.
- Uninstall the IIS component from the OS of the Site Server.
- Reboot the Site Server.
- Run ccmdelcert.exe from the SMS Toolkit.
- Reinstall the IIS component (with BITS) on the OS of the Site Server.
- Go into the IIS manager and allow WebDav.
- Add the MP role to the Site Server. Watch the MPSetup.log to ensure that the installation completes correctly.
These steps didn't seem to work, probably because it was for SMS 2003.
Here is the MPmsi log file:
<11-24-2009 17:39:28> SMSMP Setup Started....
<11-24-2009 17:39:28> Parameters: C:\PROGRA~1\MICROS~3\bin\i386\ROLESE~1.EXE /install /siteserver:DELGADO SMSMP
<11-24-2009 17:39:28> Installing Pre Reqs for SMSMP
<11-24-2009 17:39:28> ======== Installing Pre Reqs for Role SMSMP ========
<11-24-2009 17:39:28> Found 1 Pre Reqs for Role SMSMP
<11-24-2009 17:39:28> Pre Req MSXML60 found.
<11-24-2009 17:39:28> No versions of MSXML60 are installed. Would install new MSXML60.
<11-24-2009 17:39:28> Enabling MSI logging. msxml6.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6MSI.log
<11-24-2009 17:39:28> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\00000409\msxml6.msi
<11-24-2009 17:39:30> msxml6.msi exited with return code: 0
<11-24-2009 17:39:30> msxml6.msi Installation was successful.
<11-24-2009 17:39:30> ======== Completed Installion of Pre Reqs for Role SMSMP ========
<11-24-2009 17:39:30> Installing the SMSMP
<11-24-2009 17:39:30> Passed OS version check.
<11-24-2009 17:39:30> IIS Service is installed.
<11-24-2009 17:39:30> checking WebDAV configuraitons
<11-24-2009 17:39:30> WebDAV is configured
<11-24-2009 17:39:30> No versions of SMSMP are installed. Installing new SMSMP.
<11-24-2009 17:39:30> Enabling MSI logging. mp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<11-24-2009 17:39:30> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<11-24-2009 17:40:24> mp.msi exited with return code: 1603
<11-24-2009 17:40:24> Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<11-24-2009 17:40:24> Fatal MSI Error - mp.msi could not be installed.
Component Services (DCOMCNFG) is running properly, no error messages when I was browsing around.
Any advice would be greatly appricated!
Thanks!Just read the post below
http://social.technet.microsoft.com/Forums/en-AU/configmgrswdist/thread/5638cdf2-09d3-4750-995e-ae60973e86b8
<Remember to copy tasks from task scheduler to some different location because it gets wiped off in process)
Imp. Note: Running ccmclean /all on SCCM is one of these unsupported things.
Remove the MP as a site system role (if it is still installed), wait for it to finish
2.
Remove IIS completely
4.
Reboot
5.
Stop the Task Scheduler Service
6.
Rename the %windir%\Tasks folder to something else (or move it)
7.
Start the Task Scheduler Service (this will recreate the %windir%\Tasks folder)
8.
Optional: Enable auditing on the \inetpub\wwwroot folder (and subfolders). Make sure to set local security policy to trap failures of file access. We will need this in case we see
the same security failure.
9.
Reinstall IIS, BITS, WebDAV
10.
Insure BITS and WebDAV are enabled
11.
Reinstall the MP
Server Engineer -
Webutil failed to create temporary folder using Get_work_area()
Friends,
We have been migrating from 6i to 10g AS 3-tier environment. We have been using get_work_area() procedure to create temporary folders to transfer report output PDF files for printing. Intially we could able to transfer the files and from there we used webutil_host.blocking to issue the print command. It was working fine. Now webutil is failing to create the temporary folder in the server which was mapped as c:\temp in the webutil.cfg file. We are unable to find the reason behind this failure. Please put your comments for this.
Apart from this if anybody is having solution to print the file to the local printer, please provide the step for that approach.
Regards,
KBIn case /tmp directory is automatically deleted, is it possible to configure a custom directory for alsbTempJars dir in OSB to assure it is never deleted?Add the -Djava.io.tmpdir=newTempDir parameter in the JAVA_PROPERTIES section of the setDomainEnv.sh script. This new location should be outside of the /tmp dir to avoid being cleared by any process.
I think best soultion would be to have alsbTempJars automatically created whenever /tmp is purged.Doing it on the fly may not be possible however you may anytime raise an enhancement request with support and if prod dev approves it, you may get a fix.
Regards,
Anuj -
SDDM + nvidia-340xx = black screen - Failed to create OpenGL context
When I'm trying to use SDDM I see nothing but black screen (I see sddm and Xorg running).
It used to work some time ago, but one day it stopped.
I'm using nvidia-340xx drivers:
[travnick@travnick-lap ~]$ yaourt -Qs nvidia
community/cuda 7.0.28-2
NVIDIA's GPU programming toolkit
multilib/lib32-libvdpau 1.1-1
Nvidia VDPAU library
multilib/lib32-nvidia-340xx-libgl 340.76-1
NVIDIA drivers libraries symlinks (32-bit)
multilib/lib32-nvidia-340xx-utils 340.76-1
NVIDIA drivers utilities (32-bit)
extra/libcl 1.1-4
OpenCL library and ICD loader from NVIDIA
extra/libvdpau 1.1-1
Nvidia VDPAU library
extra/nvidia-340xx 340.76-9
NVIDIA drivers for linux, 340xx legacy branch
extra/nvidia-340xx-libgl 340.76-2
NVIDIA drivers libraries symlinks
extra/nvidia-340xx-utils 340.76-2
NVIDIA drivers utilities
extra/opencl-nvidia-340xx 340.76-2
OpenCL implemention for NVIDIA
journalctl says:
[travnick@travnick-lap ~]$ sudo journalctl -b |grep sddm
[sudo] hasło użytkownika travnick:
maj 22 16:29:14 travnick-lap sddm[1090]: Signal received: SIGUSR1
maj 22 16:29:15 travnick-lap sddm-helper[1126]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
maj 22 16:29:15 travnick-lap systemd-logind[1084]: New session c1 of user sddm.
maj 22 16:29:15 travnick-lap systemd[1]: Started Session c1 of user sddm.
maj 22 16:29:15 travnick-lap systemd[1]: Starting Session c1 of user sddm.
maj 22 16:29:15 travnick-lap systemd[1128]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
maj 22 16:29:15 travnick-lap systemd[1128]: systemd 219 running in user mode for user 999/sddm. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
maj 22 16:29:15 travnick-lap systemd[1128]: /var/lib/sddm/.config/systemd/user
maj 22 16:29:15 travnick-lap systemd[1128]: /var/lib/sddm/.local/share/systemd/user
maj 22 16:29:20 travnick-lap sddm-greeter[1132]: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1, profile 0)
maj 22 16:29:21 travnick-lap systemd-coredump[1140]: Process 1132 (sddm-greeter) of user 999 dumped core.
maj 22 16:30:33 travnick-lap polkitd[1102]: Operator of unix-process:4785:11656 FAILED to authenticate to gain authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.10 [systemctl restart sddm] (owned by unix-user:travnick)
maj 22 16:30:45 travnick-lap sudo[4792]: travnick : TTY=tty2 ; PWD=/home/travnick ; USER=root ; COMMAND=/usr/bin/systemctl restart sddm
maj 22 16:30:45 travnick-lap sddm[1090]: Signal received: SIGTERM
maj 22 16:30:47 travnick-lap sddm[4800]: Signal received: SIGUSR1
maj 22 16:30:47 travnick-lap sddm-helper[4807]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
maj 22 16:30:47 travnick-lap systemd[1]: Started Session c3 of user sddm.
maj 22 16:30:47 travnick-lap systemd-logind[1084]: New session c3 of user sddm.
maj 22 16:30:47 travnick-lap systemd[1]: Starting Session c3 of user sddm.
maj 22 16:30:48 travnick-lap sddm-greeter[4809]: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1, profile 0)
maj 22 16:30:48 travnick-lap systemd-coredump[4817]: Process 4809 (sddm-greeter) of user 999 dumped core.
maj 22 16:31:07 travnick-lap sudo[4819]: travnick : TTY=tty2 ; PWD=/home/travnick ; USER=root ; COMMAND=/usr/bin/systemctl stop sddm
maj 22 16:31:07 travnick-lap sddm[4800]: Signal received: SIGTERM
maj 22 16:31:21 travnick-lap sudo[4832]: travnick : TTY=tty2 ; PWD=/home/travnick ; USER=root ; COMMAND=/usr/bin/systemctl disable sddm
Last edited by travnick (2015-06-02 23:25:58)It's working for me, I'm on 340xx nvidia drivers and using sddm+plasma. I even have nouveau installed in parallel (blacklisted).
I don't know if it makes any difference, but I'm using the -ck variant of the kernel and the nvidia driver. libgl part is still the same though:
$ pacman -Qs nvidia
local/lib32-libcl 1.1-1
OpenCL library and ICD loader from NVIDIA (32-bit)
local/lib32-nvidia-340xx-libgl 340.76-1
NVIDIA drivers libraries symlinks (32-bit)
local/lib32-nvidia-340xx-utils 340.76-1
NVIDIA drivers utilities (32-bit)
local/libcl 1.1-4
OpenCL library and ICD loader from NVIDIA
local/libvdpau 1.1-1
Nvidia VDPAU library
local/nvidia-340xx-ck-k10 340.76-11 (ck-k10)
NVIDIA drivers for linux-ck, 340xx legacy branch.
local/nvidia-340xx-libgl 340.76-2
NVIDIA drivers libraries symlinks
local/nvidia-340xx-utils 340.76-2
NVIDIA drivers utilities
local/opencl-nvidia-340xx 340.76-2
OpenCL implemention for NVIDIA
local/xf86-video-nouveau 1.0.11-3 (xorg-drivers xorg)
Open Source 2D acceleration driver for nVidia cards -
Operations Manager failed to start a process + UAC
Ok, I understand that there are perhaps tens of thousands of these posts, but I've not found one after an hour searching that seems to meet up with what I'm seeing.
Seeing this show up on a handful of servers, and I don't see the correlation with the servers having this issue and things they have in common. I'm seeing it on all of our Lync Front-End servers, and then on a few terminal servers. I'm going to give the
error for the Lync servers here though.
The process started at 9:00:25 AM failed to create System.PropertyBagData, no errors detected in the output. The process exited with 0
Command executed: "C:\Windows\system32\cscript.exe" /nologo "GetSQL2012DBFilesFreeSpace.vbs" "FE-05\RTCLOCAL" "FE-05.home.ku.edu" "RTCLOCAL"
Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 9359\180265\
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2012.Monitoring.DBFileSpaceMonitor
Instance name: tempdb2
Instance ID: {1FFB1DA7-414F-CAA1-E3EC-07AC097A2CED}
Management group: ITES
So since I've been working through all these little annoying warnings and trying to sort them out I decided to run the script.
<Collection><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.28
55484-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Conve
rsionType>PerformanceData</ConversionType><Property Name="Database" VariantType=
"8">master</Property><Property Name="FileId" VariantType="3">1</Property><Proper
ty Name="FreeSpaceMB" VariantType="5">37646.0621050745</Property><Property Name=
"FreeSpacePercent" VariantType="5">99.9912017130836</Property><Property Name="Fr
eeSpaceAutoGrowMB" VariantType="5">0.6875</Property><Property Name="FreeSpaceAut
oGrowPercent" VariantType="5">17.1875</Property></DataItem><DataItem type="Syste
m.PropertyBagData" time="2014-06-04T09:23:23.2855484-05:00" sourceHealthServiceI
d="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</Conver
sionType><Property Name="Database" VariantType="8">master</Property><Property Na
me="FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" VariantType
="5">39248.5533834203</Property><Property Name="FreeSpacePercent" VariantType="5
">99.9991440853338</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5
">0.414063</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">5
5.2084</Property></DataItem><DataItem type="System.PropertyBagData" time="2014-0
6-04T09:23:23.2905518-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDD
A89CEB89"><ConversionType>PerformanceData</ConversionType><Property Name="Databa
se" VariantType="8">tempdb</Property><Property Name="FileId" VariantType="3">1</
Property><Property Name="FreeSpaceMB" VariantType="5">36681.1775486072</Property
><Property Name="FreeSpacePercent" VariantType="5">99.9923331676945</Property><P
roperty Name="FreeSpaceAutoGrowMB" VariantType="2">0</Property><Property Name="F
reeSpaceAutoGrowPercent" VariantType="2">0</Property></DataItem><DataItem type="
System.PropertyBagData" time="2014-06-04T09:23:23.2905518-05:00" sourceHealthSer
viceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</C
onversionType><Property Name="Database" VariantType="8">tempdb</Property><Proper
ty Name="FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" Varian
tType="5">38307.2356943516</Property><Property Name="FreeSpacePercent" VariantTy
pe="5">99.9940044295872</Property><Property Name="FreeSpaceAutoGrowMB" VariantTy
pe="2">0</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="2">0</
Property></DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:
23:23.2915509-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89
"><ConversionType>PerformanceData</ConversionType><Property Name="Database" Vari
antType="8">tempdb</Property><Property Name="FileId" VariantType="3">3</Property
><Property Name="FreeSpaceMB" VariantType="5">39745.5</Property><Property Name="
FreeSpacePercent" VariantType="5">99.988679245283</Property><Property Name="Free
SpaceAutoGrowMB" VariantType="5">120.5</Property><Property Name="FreeSpaceAutoGr
owPercent" VariantType="5">96.4</Property></DataItem><DataItem type="System.Prop
ertyBagData" time="2014-06-04T09:23:23.2915509-05:00" sourceHealthServiceId="9F1
D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionTy
pe><Property Name="Database" VariantType="8">tempdb</Property><Property Name="Fi
leId" VariantType="3">4</Property><Property Name="FreeSpaceMB" VariantType="5">3
9746.375</Property><Property Name="FreeSpacePercent" VariantType="5">99.99088050
31447</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">121.375</Pr
operty><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">97.1</Property>
</DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.291
5509-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Conver
sionType>PerformanceData</ConversionType><Property Name="Database" VariantType="
8">tempdb</Property><Property Name="FileId" VariantType="3">5</Property><Propert
y Name="FreeSpaceMB" VariantType="5">39745.875</Property><Property Name="FreeSpa
cePercent" VariantType="5">99.9896226415094</Property><Property Name="FreeSpaceA
utoGrowMB" VariantType="5">120.875</Property><Property Name="FreeSpaceAutoGrowPe
rcent" VariantType="5">96.7</Property></DataItem><DataItem type="System.Property
BagData" time="2014-06-04T09:23:23.2915509-05:00" sourceHealthServiceId="9F1D980
F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><
Property Name="Database" VariantType="8">tempdb</Property><Property Name="FileId
" VariantType="3">6</Property><Property Name="FreeSpaceMB" VariantType="5">39744
.875</Property><Property Name="FreeSpacePercent" VariantType="5">99.987106918239
</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">119.875</Propert
y><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">95.9</Property></Dat
aItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.2915509-
05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionT
ype>PerformanceData</ConversionType><Property Name="Database" VariantType="8">te
mpdb</Property><Property Name="FileId" VariantType="3">7</Property><Property Nam
e="FreeSpaceMB" VariantType="5">39744.9375</Property><Property Name="FreeSpacePe
rcent" VariantType="5">99.9872641509434</Property><Property Name="FreeSpaceAutoG
rowMB" VariantType="5">119.9375</Property><Property Name="FreeSpaceAutoGrowPerce
nt" VariantType="5">95.95</Property></DataItem><DataItem type="System.PropertyBa
gData" time="2014-06-04T09:23:23.2915509-05:00" sourceHealthServiceId="9F1D980F-
BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><Pr
operty Name="Database" VariantType="8">tempdb</Property><Property Name="FileId"
VariantType="3">8</Property><Property Name="FreeSpaceMB" VariantType="5">39742.2
5</Property><Property Name="FreeSpacePercent" VariantType="5">99.9805031446541</
Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">117.25</Property><
Property Name="FreeSpaceAutoGrowPercent" VariantType="5">93.8</Property></DataIt
em><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.2915509-05:
00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType
>PerformanceData</ConversionType><Property Name="Database" VariantType="8">tempd
b</Property><Property Name="FileId" VariantType="3">9</Property><Property Name="
FreeSpaceMB" VariantType="5">39744.5625</Property><Property Name="FreeSpacePerce
nt" VariantType="5">99.986320754717</Property><Property Name="FreeSpaceAutoGrowM
B" VariantType="5">119.5625</Property><Property Name="FreeSpaceAutoGrowPercent"
VariantType="5">95.65</Property></DataItem><DataItem type="System.PropertyBagDat
a" time="2014-06-04T09:23:23.2975503-05:00" sourceHealthServiceId="9F1D980F-BA02
-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><Proper
ty Name="Database" VariantType="8">model</Property><Property Name="FileId" Varia
ntType="3">1</Property><Property Name="FreeSpaceMB" VariantType="5">39630.875</P
roperty><Property Name="FreeSpacePercent" VariantType="5">99.9944806182969</Prop
erty><Property Name="FreeSpaceAutoGrowMB" VariantType="5">0.875</Property><Prope
rty Name="FreeSpaceAutoGrowPercent" VariantType="5">28.5714285714286</Property><
/DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.2975
503-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Convers
ionType>PerformanceData</ConversionType><Property Name="Database" VariantType="8
">model</Property><Property Name="FileId" VariantType="3">2</Property><Property
Name="FreeSpaceMB" VariantType="5">39248.5690084203</Property><Property Name="Fr
eeSpacePercent" VariantType="5">99.9991838953776</Property><Property Name="FreeS
paceAutoGrowMB" VariantType="5">0.429688</Property><Property Name="FreeSpaceAuto
GrowPercent" VariantType="5">57.2917333333333</Property></DataItem><DataItem typ
e="System.PropertyBagData" time="2014-06-04T09:23:23.3025532-05:00" sourceHealth
ServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData
</ConversionType><Property Name="Database" VariantType="8">msdb</Property><Prope
rty Name="FileId" VariantType="3">1</Property><Property Name="FreeSpaceMB" Varia
ntType="5">37585.1339389847</Property><Property Name="FreeSpacePercent" VariantT
ype="5">99.9579465372616</Property><Property Name="FreeSpaceAutoGrowMB" VariantT
ype="5">0.875</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5
">5.2434456928839</Property></DataItem><DataItem type="System.PropertyBagData" t
ime="2014-06-04T09:23:23.3025532-05:00" sourceHealthServiceId="9F1D980F-BA02-D35
1-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><Property N
ame="Database" VariantType="8">msdb</Property><Property Name="FileId" VariantTyp
e="3">2</Property><Property Name="FreeSpaceMB" VariantType="5">36542.9860732182<
/Property><Property Name="FreeSpacePercent" VariantType="5">99.9936081094063</Pr
operty><Property Name="FreeSpaceAutoGrowMB" VariantType="5">17.289063</Property>
<Property Name="FreeSpaceAutoGrowPercent" VariantType="5">88.0971363057325</Prop
erty></DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:2
3.3075515-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><C
onversionType>PerformanceData</ConversionType><Property Name="Database" VariantT
ype="8">xds</Property><Property Name="FileId" VariantType="3">1</Property><Prope
rty Name="FreeSpaceMB" VariantType="5">39628.25</Property><Property Name="FreeSp
acePercent" VariantType="5">99.990537949132</Property><Property Name="FreeSpaceA
utoGrowMB" VariantType="5">4.25</Property><Property Name="FreeSpaceAutoGrowPerce
nt" VariantType="5">53.125</Property></DataItem><DataItem type="System.PropertyB
agData" time="2014-06-04T09:23:23.3085531-05:00" sourceHealthServiceId="9F1D980F
-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><P
roperty Name="Database" VariantType="8">xds</Property><Property Name="FileId" Va
riantType="3">2</Property><Property Name="FreeSpaceMB" VariantType="5">39630.109
375</Property><Property Name="FreeSpacePercent" VariantType="5">99.9952295493541
</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">6.109375</Proper
ty><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">76.3671875</Propert
y></DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.3
135527-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Conv
ersionType>PerformanceData</ConversionType><Property Name="Database" VariantType
="8">rtcdyn</Property><Property Name="FileId" VariantType="3">1</Property><Prope
rty Name="FreeSpaceMB" VariantType="5">199127.125</Property><Property Name="Free
SpacePercent" VariantType="5">99.9915262322741</Property><Property Name="FreeSpa
ceAutoGrowMB" VariantType="5">983.125</Property><Property Name="FreeSpaceAutoGro
wPercent" VariantType="5">98.3125</Property></DataItem><DataItem type="System.Pr
opertyBagData" time="2014-06-04T09:23:23.3135527-05:00" sourceHealthServiceId="9
F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</Conversion
Type><Property Name="Database" VariantType="8">rtcdyn</Property><Property Name="
FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" VariantType="5"
>15768.585938</Property><Property Name="FreeSpacePercent" VariantType="5">99.649
8100227502</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">1944.5
85938</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">97.229
2969</Property></DataItem><DataItem type="System.PropertyBagData" time="2014-06-
04T09:23:23.3195540-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA8
9CEB89"><ConversionType>PerformanceData</ConversionType><Property Name="Database
" VariantType="8">rtc</Property><Property Name="FileId" VariantType="3">1</Prope
rty><Property Name="FreeSpaceMB" VariantType="5">198878.4375</Property><Property
Name="FreeSpacePercent" VariantType="5">99.8666480034548</Property><Property Na
me="FreeSpaceAutoGrowMB" VariantType="5">734.4375</Property><Property Name="Free
SpaceAutoGrowPercent" VariantType="5">73.44375</Property></DataItem><DataItem ty
pe="System.PropertyBagData" time="2014-06-04T09:23:23.3195540-05:00" sourceHealt
hServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceDat
a</ConversionType><Property Name="Database" VariantType="8">rtc</Property><Prope
rty Name="FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" Varia
ntType="5">15659.34375</Property><Property Name="FreeSpacePercent" VariantType="
5">98.9594524140546</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="
5">1835.34375</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5
">91.7671875</Property></DataItem></Collection>
As you can see a boatload of data is returned, then I realized that my command prompt was running in admin mode. When I ran the same command not in admin mode, there was no data returned, which seems to fit with the error. The script ran but no data came
back.
So, my question is, should I disable UAC on all my front end servers? Or, is there a better runas account to use? I believe I chose the default LocalSystem for everybody since it doesn't require as much effort.
Any feedback is welcome :)
Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.comThe agent should use LocalSystem and it is very rare to use a different account to run the agent service. This is probably a need to configure a run as account to be used by the SQL Discovery. SQL Server 2012 is much more locked down than previous versions
of SQL, so unless you gave localsystem admin rights to your instance of SQL running on this box, this script will always come back with nothing. check out kevin holmans article on how to configure run as accounts for the SQL MP, to address this issue.
http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx
hope this helps!
Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG)
Please remember to click “Mark as Answer” on the post that helps you!
my new blog om2012.wordpress.com -
SCOM failed to start a process - logical disk checks
Hey, I'm getting started with SCOM 2012 R2 and I'm having some weird warning alerts reported for many Windows 2008 servers. If I close the alert, it just comes back a little later.
I tried to research it quite a bit but I'm not really even sure where to start because I'm so new to the product.
What is the best place to debug something like this? Any suggested parameters for the vbs file?
I followed a guide on testing wmi via wbemtest and it listed my drive letters.
Servers are fully windows updated.
Disabled antivirus scanning of the SCOM related processes and folders
I think the script is part of the Windows Logical Drives MP and my version is 1.2.1.5
I tried to find the .vbs file it references, but it is not anywhere on the machine generating the alert.
I exported the .vbs file file and unescaped it from the SCOM server but I have no idea what parameters it wants lol
The process started at 11:02:53 PM failed to create System.PropertyBagData.
Errors found in output:C:\Program Files\Microsoft Monitoring
Agent\Agent\Health Service State\Monitoring Host Temporary Files
1807\9626\CollectLogicalDiskStatistics.vbs(94, 9) (null): Data error (cyclic
redundancy check). Command executed:
"C:\Windows\system32\cscript.exe" /nologo "CollectLogicalDiskStatistics.vbs"
falseWorking Directory: C:\Program Files\Microsoft Monitoring
Agent\Agent\Health Service State\Monitoring Host Temporary Files
1807\9626\One or more workflows were affected by this.
Workflow name:
Windows.LogicalDrives.CollectFreeSpace.RuleInstance name:
C:Instance ID: {374D942F-352C-C10B-68D9-7A50C3C279E0}Hi Shaddie,
Can you check that the Agent that is installed on the target system is Healthy?
What you could do as well, on the affected system, is stop the Microsoft Monitoring Agent service, and re-name the Health Service folder (located at C:\Program Files\System Center Operations Manager\Agent\Health Service State).
Re-name that folder, then restart the Microsoft Monitoring Agent service. This will cause the Agent to re-download the discovery and monitoring rules, etc.
Also, see the following TechNet article, even though it is for SCOM 2007, some of the steps might still apply: http://blogs.technet.com/b/kevinholman/archive/2009/06/29/getting-lots-of-script-failed-to-run-alerts-wmi-probe-failed-execution-backward-compatibility-script-error.aspx
Please remember to click “Mark as Answer” on the post that helps you.
AdinE MCSE, MCSA, MCITP, MCTS; (Specializing in System Center and Private Cloud)
LinkedIn: http://ca.linkedin.com/in/adinermie
Website: http://AdinErmie.Wordpress.com -
INDEX failed to create while Import using datapump
Hi DBA's
database 11.2.01
OS : Solaris 10
I am trying to Import the data using the following command.
impdp system/******* SCHEMAS=EIMS DIRECTORY=expdp_dir DUMPFILE=eimsexp.dmp*
but it fails import index and error out, but the tables and data imported.
I checked in the metalink and followed the Note id (During Data Pump Import Index Creation Fails With: ORA-39083 and ORA-14102 errors OR ORA-39083 ORA-02158 and ORA-39112 errors [ID 1066635.1]) , but no luck.
Kindly advice me.
ERROR
ORA-39083: Object type INDEX failed to create with error:
ORA-14102: only one LOGGING or NOLOGGING clause may be specified
Failing sql is:
CREATE UNIQUE INDEX "EIMS"."PK_MDS_PSTN_LEVEL" ON "EIMS"."MDS_PSTN_LEVEL" ("REGION_CODE", "AREA_CODE", "LEVEL_NO", "EXCHANGE_CODE") PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" PARALLEL 1
ORA-39083: Object type INDEX failed to create with error:
ORA-14102: only one LOGGING or NOLOGGING clause may be specified
Best Regards,
SGDear Hussein,
Yes i applied the patch, still i am getting the same error and again i followed one more note (Impdp Failed With Error Ora-39083, 0ra-01403 On Index_statistics (Doc ID 755253.1))
in that note i given option "exclude=index", then i got in different error.
We are in the process of doing testing on Tablespace Encryption.
We are having two instances one is dev and uat instance.
we are creating Encryption tablespace on uat instance and trying to import the data from dev instance only from particular user.
We completed the followings.
1. Created tablespace Encryption.
2. Created user and assigned the tablespace to the user EIMS1.
3. Took export from the dev instance using the following command.
expdp system/******** SCHEMAS=EIMS DIRECTORY=expdp_dir DUMPFILE=eimsexp.dmp
4. Importing data from
impdp system/******** REMAP_SCHEMA=EIMS:EIMS1 DIRECTORY=expdp_dir exclude=index DUMPFILE=eimsexp.dmp
Error
====
ORA-39083: Object type CONSTRAINT failed to create with error:
ORA-14102: only one LOGGING or NOLOGGING clause may be specified
Failing sql is:
ALTER TABLE "EIMS1"."DOCS" ADD PRIMARY KEY ("ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" ENABLE
ORA-39083: Object type CONSTRAINT failed to create with error:
ORA-14102: only one LOGGING or NOLOGGING clause may be specified
before i used to get the bellow errors
==========================
ALTER TABLE "EIMS1"."TST1" ADD CONSTRAINT "ADMACHINEDEPLOYMENTSTATUS_PK" PRIMARY KEY ("MID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" ENABLE
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39083: Object type INDEX_STATISTICS failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
DECLARE I_N VARCHAR2(60); I_O VARCHAR2(60); c DBMS_METADATA.T_VAR_COLL; df varchar2(21) := 'YYYY-MM-DD:HH24:MI:SS'; BEGIN DELETE FROM "SYS"."IMPDP_STATS"; c(1) := 'ID'; DBMS_METADATA.GET_STAT_INDNAME('EIMS1','DOCS',c,1,i_o,i_n); INSERT INTO "SYS"."IMPDP_STATS" (type,version,flags,c1,c2,c3,c5,n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,d1,cl1) VALUES ('I',5,0,I_N,NUL
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MDS_PSTN_LEVEL" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_AMT_REQUEST_PRIORITY" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_AMT_REQUEST_QUEUE" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH02_REQUEST_PRIORITY" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH03_REQUEST_PRIORITY" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH03_REQUEST_QUEUE" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH04_REQUEST_PRIORITY" creation failed
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1049 error(s) at 20:43:02
Thanks
SG -
Failed to create the volume shadow copy inside of virtual machine 'SBS-SVR'
Hi there,
Currently only partial backups are being completed.
I receive the following error:
Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {B8818795-2E27-44A3-85AB-D4C3DDBD288E}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 5
Failure Result: 80042336
Application Result: 80004005
Application Message: (null)
Component: 9E70CA9C-B992-425D-B091-95B76763BE39
Logical Path: (null)
Component Result: 800423F3
Component Message: Failed to create the volume shadow copy inside of virtual machine 'SBS-SVR'. (Virtual machine ID 9E70CA9C-B992-425D-B091-95B76763BE39)
File Spec: C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\\9E70CA9C-B992-425D-B091-95B76763BE39.xml Recursive: 0
File Spec: C:\Users\Public\Documents\Hyper-V\Virtual hard disks\\SBS-SVR-SYSTEM_404D40C1-A532-4272-AE8B-251C4A03B4F3.avhdx Recursive: 0
File Spec: C:\Users\Public\Documents\Hyper-V\Virtual hard disks\\SBS-SVR-SYSTEM.vhdx Recursive: 0
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: 9E70CA9C-B992-425D-B091-95B76763BE39
Caption : Backup Using Child Partition Snapshot\SBS-SVR
Logical Path:
Error : 80780175
Error Message : Component was skipped from volume shadow copy.
Detailed Error : 800423F3
Detailed Error Message : The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
The success file is as follows:
Backup of volume \\?\Volume{72ec559c-60ca-11e2-93e8-806e6f6e6963}\ succeeded.
Backup of volume C: succeeded.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: Host Component
Caption : Host Component
Logical Path:
In the event logs: application, i found this:
The backup operation that started at '2014-05-18T11:00:22.221374600Z' has failed to back up volume(s) ''. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Some errors that are occuring that may be linked are:
Event Viewer, Application and Service Logs, Microsoft, Windows, Hyper-V-VMMS (the below is occuring every 2 minutes)
Failed to register the service principal name 'Hyper-V Replica Service'.
Failed to register the service principal name 'Microsoft Virtual System Migration Service'.
Failed to register the service principal name 'Microsoft Virtual Console Service'.
Upon some research I tried the following without much luck:
http://support.microsoft.com/kb/2761899
http://social.technet.microsoft.com/wiki/contents/articles/1340.hyper-v-troubleshooting-event-id-14050-vmms.aspx
Specs:
Microsoft Windows Server 2012 Standard x64
6.2.9200
ProLiant ML350e Gen8
VM: Microsoft® Windows Server® 2008 Standard FE x64
6.0.6002 Service Pack 2
Look forward to any help.
JohnHi John,
Please run “vssadmin list writers” command to check the VSS writer status. There is a similar thread, please go through it to help troubleshoot this issue:
Windows 2012 Backup for HyperV failed with error code '0x80780049'
http://social.technet.microsoft.com/Forums/windowsserver/en-US/f1a0c9c6-7b4c-409c-b4da-c145b8b59eb1/windows-2012-backup-for-hyperv-failed-with-error-code-0x80780049?forum=winserverhyperv
Regards,
Mandy
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.
Maybe you are looking for
-
I plugged my Iphone 4s in my computer last night to sync and it asked me if I wanted to do an update, so I clicked to start the update. When I woke up this morning my phone is frozen with the display having the blue circle itunes on the top and botto
-
Applying XSLT to XSLT result in Java
I want to apply a 2nd XSLT to results of ProcessXSL. I started from JDeveloper sample code: TransformedShoppingCart.java. After I have applied one XSL I want to apply another. Code snip: //Up to here have read in an xml file, //parsed it and read an
-
Release strategy retrigger for all non significant changes
HI, My client has the below requirement: The Purchase requsitions and Purchase orders are released by different approval authorities. Any change made to any field like material short text, cost centre, payment terms, material long text, etc. the syte
-
Interactive booklet of "The Open Door" doesnt work
The interactive booklet of Evanescence's "The Open Door" doesnt seem to work. Everytime I open it, all I see is black. Can someone help me find a way to help it work?
-
I am trying to develop a simple front end with SJSC that calls a report prepared with Crystal Reports XI. However when I attempt to open the file from Page1.java, CRXI stops at an "Unexpected error determining relative path". The file with the report