search for: 00010003

...ied: 0d err:module:import_dll Library FTD2XX.DLL (which is needed by L"C:\\Program Files\\SMA\\Sunny Data Control\\AddOns\\SBeam.dll") not found fixme:tapi:lineInitialize (0x8358ac, 0x10b0000, 0x10b2dfc, "TAPICOMM", 0x8358b0): stub. fixme:tapi:lineGetDevCapsA ((nil), 00000000, 00010003, 00000000, 0x832dcc): stub. fixme:tapi:lineGetDevCapsA ((nil), 00000000, 00010003, 00000000, 0x832dcc): stub. fixme:ras:RasEnumEntriesA ((nil),(null),0xf79068,0x34f5d8,0xf78020),stub! fixme:ras:RasEnumDevicesA ((nil),0x34f60c,0x34f608),stub! fixme:ras:RasEnumDevicesA (0x825de0,0x34f60c,0x34f608),...

...steam and starting fallout with no crashes... This is the Log that NVSE gives when it "fails": Code: nvse loader 010000A0 launching: FalloutNV.exe (C:\Program Files\Steam\SteamApps\common\fallout new vegas\FalloutNV.exe) dwSignature = FEEF04BD dwStrucVersion = 00010000 dwFileVersionMS = 00010003 dwFileVersionLS = 000001C4 dwProductVersionMS = 00010003 dwProductVersionLS = 000001C4 dwFileFlagsMask = 00000017 dwFileFlags = 00000000 dwFileOS = 00000004 dwFileType = 00000001 dwFileSubtype = 00000000 dwFileDateMS = 00000000 dwFileDateLS = 00000000 version = 00010003000001C4 steam exe hook call...

https://bugs.freedesktop.org/show_bug.cgi?id=86641 Bug ID: 86641 Summary: nouveau crashes kernel with nvidia 9400 igp Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Driver/nouveau Assignee:

...orm [0001.358] I> Boot-device: eMMC [0001.362] I> odm data is 1090000 [0001.365] I> Reading GPT from 512 for device 00000003 [0001.371] I> Reading GPT from 8388096 for device 00000003 [0001.377] I> Found 6 partitions in 00000003 device [0001.382] I> Reading GPT from 512 for device 00010003 [0001.388] I> Found 17 partitions in 00010003 device [0001.393] W> No valid slot number is found in scratch register [0001.398] W> Return default slot: _a [0001.402] I> A/B: bin_type (1) slot 0 [0001.405] I> Select partition: kernel-dtb [0001.409] I> Loading partition kernel-dtb a...

...Boot-device: eMMC [0000.264] I> pmic: reset reason (nverc) : 0x0 [0000.268] I> Reading GPT from 512 for device 00000003 [0000.274] I> Reading GPT from 8388096 for device 00000003 [0000.281] I> Found 6 partitions in 00000003 device [0000.286] I> Reading GPT from 512 for device 00010003 [0000.293] I> Found 17 partitions in 00010003 device [0000.298] W> No valid slot number is found in scratch register [0000.303] W> Return default slot: _a [0000.307] I> A/B: bin_type (16) slot 0 [0000.310] I> Select partition: bpmp-fw [0000.314] I> Loading partition bpmp-fw at 0xf...

...2:A166:BEC7 FF02::16 00:04:55.598459 295.598459 13:48:41.527857 (90) njchiaia IPv6 Neighbor Discovery-00000016 ICMPv6 - Multicast Listener Report V2 FE80::31A3:E972:A166:BEC7 FF02::16 00:04:55.598463 295.598463 13:48:41.527861 (88) njchiaia IPv6 Neighbor Discovery-00010003 LLMNR FE80::31A3:E972:A166:BEC7 FF02::1:3 00:04:55.598467 295.598467 13:48:41.527864 (60) njchiaia USC-IANA MC-000016 IGMP 172.16.5.111 224.0.0.22 00:04:55.598470 295.598470 13:48:41.527868 (60) njchiaia USC-IANA MC-000016 IGMP 172.16.5.111 224.0.0.22...

running Version 3.6.23-14.el6_6 I'm having slow save times with folders names ~something.. ie. /www/~bin/content.txt. doing this via a windows share.. when I save file it has a moment (few seconds) of hesitation.. then saves. When I do /www/bin/content.txt. the file saves instantly. Is there anywhere I can change a setting to fix this? or is this a bug. I've looked in the logs

...Boot-device: eMMC [0000.260] I> pmic: reset reason (nverc) : 0x0 [0000.264] I> Reading GPT from 512 for device 00000003 [0000.270] I> Reading GPT from 8388096 for device 00000003 [0000.277] I> Found 6 partitions in 00000003 device [0000.282] I> Reading GPT from 512 for device 00010003 [0000.288] I> Found 17 partitions in 00010003 device [0000.294] W> No valid slot number is found in scratch register [0000.299] W> Return default slot: _a [0000.303] I> A/B: bin_type (16) slot 0 [0000.306] I> Select partition: bpmp-fw [0000.310] I> Loading partition bpmp-fw at 0xf...

.... When this happens, the node that lost connections kills CMAN. The other 3 nodes get into this state: [root at calgb-blade2 ~]# group_tool type level name id state fence 0 default 00010001 FAIL_START_WAIT [1 2 3] dlm 1 clvmd 00010003 FAIL_ALL_STOPPED [1 2 3 4] dlm 1 rgmanager 00020003 FAIL_ALL_STOPPED [1 2 3 4] One of the nodes will be barking about trying to fence the "failed" node (expected, as I don't have real fencing). Nothing (physically) has actually failed. All 4 blades are running th...