Clock failure
Computer returned after logic board replaced for video issue. Now clock will not keep time when computer off. Has to be reset each time. Reverts to time at previous start up. Battery replaced but problem continues.
Asanga
iMac G5 Mac OS X (10.3.9)
Hi Asanga.
Some of the "first generation" machines were also 17" 1.8 GHz models.
In your case, in fact, I think we can be certain that it is actually a "first generation" machine if you are running OSX 10.3.9. The "Second Generation" models came with OSX 10.4.
To reset the SMU you therefore have to follow the instructions detailed in the second dot point of paragraph 9 of http://docs.info.apple.com/article.html?artnum=300908 . This involves removing the back of your computer and pressing a button, rather than the simpler process involved for the 2nd generation model.
Cheers
Rod.
Similar Messages
-
FX5600-VTDR128 /MSI Clock Failure!!
Hi,
I need some help with my VGA Card. I just purchased the FX5600-VTDR128 and when I try to use the MSI Clock feature I recieve a message that displays "Load nvgpio.dll fail" ! It shows my Core Clock(MHz) @ 2D (54) MHz and 3D (?) MHz/ Memory Clock @ (100) MHz. This is not even close to the stock speeds from the MSI Site on this crad (• GPU Core Clock: 325MHz, Memory Clock: 550MHz) http://www.msicomputer.com/product/vga/vga_detail.asp?model=FX5600-VTDR128 . I even installed PowerStrip to view the cards current speeds and gives me a (275) MHz in 3D as default and (550) MHz for Memory. I have installed the latest drive from NVidia as well as the latest MSI has to offer with no luck. :angryfire:I have tried using driver cleaner and installing each driver again as well.
System Spec
Mainboard:
Asus A7N8X Deluxe REV 1.xx Bios REV 1005
CPU:
AMD XP 3000+ Barton
Power Supply:
Antec True 430
Memory:
3x256 mb Corsair XMS PC3200 LLPT Ultra Low Latecy
Optical's:
Pioneer DVR-A05 DVD/CDR
56x Rom
Hard Disk:
WD Special Edition 120gb
etc,etc,etcIf you want to be able to have the hidden fuctions, create a file with notepad and put this in it.
quote:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWARENVIDIA CorporationGlobalNVTweak]
"Coolbits"=dword:ffffffff
"NvCplEnableHardwarePage"=dword:00000001
"NvCplEnableAGPSettingsPage"=dword:00000001
Save it as agpsetting.reg to your desktop or anywhere you like. Then run it and it will give you all the hidden options from nVidia which include extra Resolution settings for your desktop and overclocking for both the memory and core. -
[GAVE UP] Failure to initialize graphics device [Thinkpad 530W,Nvidia]
Hello,
I fail to use `nvidia` as graphics driver for my xorg on a Thinkpad 530W laptop using Nvidia Quadro 2000M and intel graphics card. Using instead `intel` or `vesa` work. This following logs are with optimus enabled, but I tried the same things with only the nvidia graphics card enabled in the bios and I also fail to load the nvidia driver.
I followed the advice at
https://wiki.archlinux.org/index.php/NV … IA_Optimus
for xorg not to be confused by the presense of two graphics cards.
Do you have any ideas how I get the nvidia card to run? Should I try Bumblebee? But can this even help if already only the nvidia card by itself makes problem? Do you need any more information?
Thanks, for any advice,
Holger
This is a fresh install on a new laptop and I am new to Arch (but with Linux for a long time).
Here are the logs:
XOrg.log
[ 6.236]
X.Org X Server 1.14.4
Release Date: 2013-10-31
[ 6.236] X Protocol Version 11, Revision 0
[ 6.236] Build Operating System: Linux 3.11.6-1-ARCH x86_64
[ 6.236] Current Operating System: Linux ho-think 3.12.2-1-ARCH #1 SMP PREEMPT Fri Nov 29 21:14:15 CET 2013 x86_64
[ 6.236] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=267f069c-11da-4d2a-88fa-00cab4e28149 rw quiet resume=/dev/sda6
[ 6.236] Build Date: 01 November 2013 05:10:48PM
[ 6.236]
[ 6.236] Current version of pixman: 0.32.4
[ 6.236] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 6.236] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 6.237] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 5 23:50:52 2013
[ 6.239] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 6.239] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 6.239] (==) No Layout section. Using the first Screen section.
[ 6.239] (==) No screen section available. Using defaults.
[ 6.239] (**) |-->Screen "Default Screen Section" (0)
[ 6.239] (**) | |-->Monitor "<default monitor>"
[ 6.240] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 6.240] (**) | |-->Device "Nvidia Card"
[ 6.240] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 6.240] (==) Automatically adding devices
[ 6.240] (==) Automatically enabling devices
[ 6.240] (==) Automatically adding GPU devices
[ 6.242] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 6.242] Entry deleted from font path.
[ 6.244] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 6.244] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 6.244] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 6.244] (II) Loader magic: 0x7fdc20
[ 6.244] (II) Module ABI versions:
[ 6.244] X.Org ANSI C Emulation: 0.4
[ 6.244] X.Org Video Driver: 14.1
[ 6.244] X.Org XInput driver : 19.1
[ 6.244] X.Org Server Extension : 7.0
[ 6.244] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 6.245] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 6.246] (--) PCI:*(0:0:2:0) 8086:0166:17aa:21f5 rev 9, Mem @ 0xf1400000/4194304, 0xe0000000/268435456, I/O @ 0x00006000/64
[ 6.246] (--) PCI: (0:1:0:0) 10de:0ffb:17aa:21f5 rev 161, Mem @ 0xf0000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
[ 6.246] Initializing built-in extension Generic Event Extension
[ 6.246] Initializing built-in extension SHAPE
[ 6.246] Initializing built-in extension MIT-SHM
[ 6.246] Initializing built-in extension XInputExtension
[ 6.246] Initializing built-in extension XTEST
[ 6.246] Initializing built-in extension BIG-REQUESTS
[ 6.246] Initializing built-in extension SYNC
[ 6.246] Initializing built-in extension XKEYBOARD
[ 6.246] Initializing built-in extension XC-MISC
[ 6.246] Initializing built-in extension SECURITY
[ 6.247] Initializing built-in extension XINERAMA
[ 6.247] Initializing built-in extension XFIXES
[ 6.247] Initializing built-in extension RENDER
[ 6.247] Initializing built-in extension RANDR
[ 6.247] Initializing built-in extension COMPOSITE
[ 6.247] Initializing built-in extension DAMAGE
[ 6.247] Initializing built-in extension MIT-SCREEN-SAVER
[ 6.247] Initializing built-in extension DOUBLE-BUFFER
[ 6.247] Initializing built-in extension RECORD
[ 6.247] Initializing built-in extension DPMS
[ 6.247] Initializing built-in extension X-Resource
[ 6.247] Initializing built-in extension XVideo
[ 6.247] Initializing built-in extension XVideo-MotionCompensation
[ 6.247] Initializing built-in extension XFree86-VidModeExtension
[ 6.247] Initializing built-in extension XFree86-DGA
[ 6.247] Initializing built-in extension XFree86-DRI
[ 6.247] Initializing built-in extension DRI2
[ 6.247] (II) "glx" will be loaded by default.
[ 6.247] (II) LoadModule: "dri2"
[ 6.247] (II) Module "dri2" already built-in
[ 6.247] (II) LoadModule: "glamoregl"
[ 6.275] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 6.475] (II) Module glamoregl: vendor="X.Org Foundation"
[ 6.475] compiled for 1.14.2, module version = 0.5.1
[ 6.475] ABI class: X.Org ANSI C Emulation, version 0.4
[ 6.475] (II) LoadModule: "glx"
[ 6.475] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 6.517] (II) Module glx: vendor="NVIDIA Corporation"
[ 6.517] compiled for 4.0.2, module version = 1.0.0
[ 6.517] Module class: X.Org Server Extension
[ 6.517] (II) NVIDIA GLX Module 331.20 Wed Oct 30 17:36:48 PDT 2013
[ 6.517] Loading extension GLX
[ 6.517] (II) LoadModule: "nvidia"
[ 6.517] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 6.549] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 6.549] compiled for 4.0.2, module version = 1.0.0
[ 6.549] Module class: X.Org Video Driver
[ 6.549] (II) NVIDIA dlloader X Driver 331.20 Wed Oct 30 17:16:53 PDT 2013
[ 6.549] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 6.549] (++) using VT number 7
[ 6.553] (II) Loading sub module "fb"
[ 6.554] (II) LoadModule: "fb"
[ 6.554] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 6.557] (II) Module fb: vendor="X.Org Foundation"
[ 6.557] compiled for 1.14.4, module version = 1.0.0
[ 6.557] ABI class: X.Org ANSI C Emulation, version 0.4
[ 6.557] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 6.557] (II) Loading sub module "wfb"
[ 6.557] (II) LoadModule: "wfb"
[ 6.557] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 6.559] (II) Module wfb: vendor="X.Org Foundation"
[ 6.559] compiled for 1.14.4, module version = 1.0.0
[ 6.559] ABI class: X.Org ANSI C Emulation, version 0.4
[ 6.559] (II) Loading sub module "ramdac"
[ 6.559] (II) LoadModule: "ramdac"
[ 6.559] (II) Module "ramdac" already built-in
[ 6.559] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 6.559] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 6.559] (==) NVIDIA(0): RGB weight 888
[ 6.559] (==) NVIDIA(0): Default visual is TrueColor
[ 6.559] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 6.559] (**) NVIDIA(0): Enabling 2D acceleration
[ 11.161] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 11.161] (EE) NVIDIA(GPU-0): check your system's kernel log for additional error
[ 11.161] (EE) NVIDIA(GPU-0): messages and refer to Chapter 8: Common Problems in the
[ 11.161] (EE) NVIDIA(GPU-0): README for additional information.
[ 11.161] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
[ 11.161] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 11.161] (II) UnloadModule: "nvidia"
[ 11.161] (II) UnloadSubModule: "wfb"
[ 11.161] (II) UnloadSubModule: "fb"
[ 11.161] (EE) Screen(s) found, but none have a usable configuration.
[ 11.161] (EE)
Fatal server error:
[ 11.161] (EE) no screens found(EE)
[ 11.161] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 11.161] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 11.162] (EE)
[ 11.167] (EE) Server terminated with error (1). Closing log file.
dmesg with the nvidia failure at the end:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.12.2-1-ARCH (tobias@T-POWA-LX) (gcc version 4.8.2 (GCC) ) #1 SMP PREEMPT Fri Nov 29 21:14:15 CET 2013
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=267f069c-11da-4d2a-88fa-00cab4e28149 rw quiet resume=/dev/sda6
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000040005000-0x00000000a6b2ffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000a6b30000-0x00000000bae9efff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bae9f000-0x00000000baf9efff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000baf9f000-0x00000000baffefff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000bafff000-0x00000000bf9fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed08000-0x00000000fed08fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000043e5fffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000043e600000-0x000000043e7fffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.7 present.
[ 0.000000] DMI: LENOVO 2447DW0/2447DW0, BIOS G5ET93WW (2.53 ) 05/24/2013
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] No AGP bridge found
[ 0.000000] e820: last_pfn = 0x43e600 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0FFC00000 mask FFFC00000 write-protect
[ 0.000000] 1 base 000000000 mask F80000000 write-back
[ 0.000000] 2 base 080000000 mask FC0000000 write-back
[ 0.000000] 3 base 0BC000000 mask FFC000000 uncachable
[ 0.000000] 4 base 0BB000000 mask FFF000000 uncachable
[ 0.000000] 5 base 100000000 mask F00000000 write-back
[ 0.000000] 6 base 200000000 mask E00000000 write-back
[ 0.000000] 7 base 400000000 mask FC0000000 write-back
[ 0.000000] 8 base 43F000000 mask FFF000000 uncachable
[ 0.000000] 9 base 43E800000 mask FFF800000 uncachable
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820: last_pfn = 0xa6b30 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [mem 0x000f0100-0x000f010f] mapped at [ffff8800000f0100]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000097000] 97000 size 24576
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] BRK [0x01b32000, 0x01b32fff] PGTABLE
[ 0.000000] BRK [0x01b33000, 0x01b33fff] PGTABLE
[ 0.000000] BRK [0x01b34000, 0x01b34fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x43e400000-0x43e5fffff]
[ 0.000000] [mem 0x43e400000-0x43e5fffff] page 2M
[ 0.000000] BRK [0x01b35000, 0x01b35fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x43c000000-0x43e3fffff]
[ 0.000000] [mem 0x43c000000-0x43e3fffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x400000000-0x43bffffff]
[ 0.000000] [mem 0x400000000-0x43bffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0x1fffffff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0x1fffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x20200000-0x40003fff]
[ 0.000000] [mem 0x20200000-0x3fffffff] page 2M
[ 0.000000] [mem 0x40000000-0x40003fff] page 4k
[ 0.000000] BRK [0x01b36000, 0x01b36fff] PGTABLE
[ 0.000000] BRK [0x01b37000, 0x01b37fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x40005000-0xa6b2ffff]
[ 0.000000] [mem 0x40005000-0x401fffff] page 4k
[ 0.000000] [mem 0x40200000-0xa69fffff] page 2M
[ 0.000000] [mem 0xa6a00000-0xa6b2ffff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x100000000-0x3ffffffff]
[ 0.000000] [mem 0x100000000-0x3ffffffff] page 2M
[ 0.000000] RAMDISK: [mem 0x379be000-0x37cd6fff]
[ 0.000000] ACPI: RSDP 00000000000f0120 00024 (v02 LENOVO)
[ 0.000000] ACPI: XSDT 00000000baffe170 000BC (v01 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: FACP 00000000bafe6000 0010C (v05 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: DSDT 00000000bafe8000 10A68 (v01 LENOVO TP-G5 00002530 INTL 20061109)
[ 0.000000] ACPI: FACS 00000000baf54000 00040
[ 0.000000] ACPI: SLIC 00000000baffd000 00176 (v01 LENOVO TP-G5 00002530 PTL 00000001)
[ 0.000000] ACPI: TCPA 00000000baffc000 00032 (v02 PTL LENOVO 06040000 LNVO 00000001)
[ 0.000000] ACPI: SSDT 00000000baffb000 00408 (v01 LENOVO TP-SSDT2 00000200 INTL 20061109)
[ 0.000000] ACPI: SSDT 00000000baffa000 00033 (v01 LENOVO TP-SSDT1 00000100 INTL 20061109)
[ 0.000000] ACPI: SSDT 00000000baff9000 00797 (v01 LENOVO SataAhci 00001000 INTL 20061109)
[ 0.000000] ACPI: HPET 00000000bafe4000 00038 (v01 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: APIC 00000000bafe3000 00098 (v01 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: MCFG 00000000bafe2000 0003C (v01 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: ECDT 00000000bafe1000 00052 (v01 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: FPDT 00000000bafe0000 00064 (v01 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: ASF! 00000000bafe7000 000A5 (v32 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: UEFI 00000000bafdf000 0003E (v01 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: UEFI 00000000bafde000 00042 (v01 PTL COMBUF 00000001 PTL 00000001)
[ 0.000000] ACPI: MSDM 00000000bafdd000 00055 (v03 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: SSDT 00000000bafdc000 00D23 (v01 PmRef Cpu0Ist 00003000 INTL 20061109)
[ 0.000000] ACPI: SSDT 00000000bafdb000 00A83 (v01 PmRef CpuPm 00003000 INTL 20061109)
[ 0.000000] ACPI: UEFI 00000000bafda000 002A6 (v01 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: DBG2 00000000bafd9000 000E9 (v00 LENOVO TP-G5 00002530 PTL 00000002)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000043e5fffff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x43e5fffff]
[ 0.000000] NODE_DATA [mem 0x43e5ed000-0x43e5f1fff]
[ 0.000000] [ffffea0000000000-ffffea0010ffffff] PMD -> [ffff88042e200000-ffff88043dbfffff] on node 0
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal [mem 0x100000000-0x43e5fffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x0009cfff]
[ 0.000000] node 0: [mem 0x00100000-0x1fffffff]
[ 0.000000] node 0: [mem 0x20200000-0x40003fff]
[ 0.000000] node 0: [mem 0x40005000-0xa6b2ffff]
[ 0.000000] node 0: [mem 0x100000000-0x43e5fffff]
[ 0.000000] On node 0 totalpages: 4083403
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3996 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 10597 pages used for memmap
[ 0.000000] DMA32 zone: 678191 pages, LIFO batch:31
[ 0.000000] Normal zone: 53144 pages used for memmap
[ 0.000000] Normal zone: 3401216 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000
[ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x40004000-0x40004fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xa6b30000-0xbae9efff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbae9f000-0xbaf9efff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbaf9f000-0xbaffefff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbafff000-0xbf9fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xbfa00000-0xf7ffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfed07fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed08000-0xfed08fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed09000-0xfed0ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed1a000-0xfed1bfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xffbfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xffc00000-0xffffffff]
[ 0.000000] e820: [mem 0xbfa00000-0xf7ffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff88043e200000 s86464 r8192 d24128 u262144
[ 0.000000] pcpu-alloc: s86464 r8192 d24128 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4019577
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=267f069c-11da-4d2a-88fa-00cab4e28149 rw quiet resume=/dev/sda6
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 15995556K/16333612K available (5121K kernel code, 807K rwdata, 1708K rodata, 1144K init, 1288K bss, 338056K reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
[ 0.000000] NR_IRQS:8448 nr_irqs:744 16
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 65536000 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.003333] tsc: Detected 2694.031 MHz processor
[ 0.000002] Calibrating delay loop (skipped), value calculated using timer frequency.. 5390.56 BogoMIPS (lpj=8980103)
[ 0.000005] pid_max: default: 32768 minimum: 301
[ 0.000027] Security Framework initialized
[ 0.000034] AppArmor: AppArmor disabled by boot time parameter
[ 0.000035] Yama: becoming mindful.
[ 0.000923] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
[ 0.004551] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.006146] Mount-cache hash table entries: 256
[ 0.006298] Initializing cgroup subsys memory
[ 0.006306] Initializing cgroup subsys devices
[ 0.006307] Initializing cgroup subsys freezer
[ 0.006309] Initializing cgroup subsys net_cls
[ 0.006310] Initializing cgroup subsys blkio
[ 0.006329] CPU: Physical Processor ID: 0
[ 0.006330] CPU: Processor Core ID: 0
[ 0.006334] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.006663] mce: CPU supports 9 MCE banks
[ 0.006675] CPU0: Thermal monitoring enabled (TM1)
[ 0.006685] Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
tlb_flushall_shift: 1
[ 0.006786] Freeing SMP alternatives memory: 20K (ffffffff819e9000 - ffffffff819ee000)
[ 0.007682] ACPI: Core revision 20130725
[ 0.013359] ACPI: All ACPI Tables successfully acquired
[ 0.014627] ftrace: allocating 20311 entries in 80 pages
[ 0.023669] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.056667] smpboot: CPU0: Intel(R) Core(TM) i7-3740QM CPU @ 2.70GHz (fam: 06, model: 3a, stepping: 09)
[ 0.056673] TSC deadline timer enabled
[ 0.056680] Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
[ 0.056686] ... version: 3
[ 0.056687] ... bit width: 48
[ 0.056688] ... generic registers: 4
[ 0.056689] ... value mask: 0000ffffffffffff
[ 0.056689] ... max period: 0000ffffffffffff
[ 0.056690] ... fixed-purpose events: 3
[ 0.056691] ... event mask: 000000070000000f
[ 0.093731] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.080104] smpboot: Booting Node 0, Processors # 1 # 2 # 3 # 4 # 5 # 6 # 7 OK
[ 0.215283] Brought up 8 CPUs
[ 0.215286] smpboot: Total of 8 processors activated (43121.51 BogoMIPS)
[ 0.221817] devtmpfs: initialized
[ 0.225267] PM: Registering ACPI NVS region [mem 0xbae9f000-0xbaf9efff] (1048576 bytes)
[ 0.225908] RTC time: 22:50:45, date: 12/05/13
[ 0.225941] NET: Registered protocol family 16
[ 0.226022] cpuidle: using governor ladder
[ 0.226024] cpuidle: using governor menu
[ 0.226046] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 0.226048] ACPI: bus type PCI registered
[ 0.226050] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.226221] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.226224] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[ 0.230705] PCI: Using configuration type 1 for base access
[ 0.231329] bio: create slab <bio-0> at 0
[ 0.231442] ACPI: Added _OSI(Module Device)
[ 0.231443] ACPI: Added _OSI(Processor Device)
[ 0.231444] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.231445] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.232701] ACPI: EC: EC description table is found, configuring boot EC
[ 0.236337] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.272341] ACPI: SSDT 00000000bae3a018 00A01 (v01 PmRef Cpu0Cst 00003001 INTL 20061109)
[ 0.272660] ACPI: Dynamic OEM Table Load:
[ 0.272661] ACPI: SSDT (null) 00A01 (v01 PmRef Cpu0Cst 00003001 INTL 20061109)
[ 0.288532] ACPI: SSDT 00000000bae3ba98 00303 (v01 PmRef ApIst 00003000 INTL 20061109)
[ 0.288874] ACPI: Dynamic OEM Table Load:
[ 0.288876] ACPI: SSDT (null) 00303 (v01 PmRef ApIst 00003000 INTL 20061109)
[ 0.301731] ACPI: SSDT 00000000bae39d98 00119 (v01 PmRef ApCst 00003000 INTL 20061109)
[ 0.302048] ACPI: Dynamic OEM Table Load:
[ 0.302049] ACPI: SSDT (null) 00119 (v01 PmRef ApCst 00003000 INTL 20061109)
[ 0.316012] ACPI: Interpreter enabled
[ 0.316018] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130725/hwxface-571)
[ 0.316022] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130725/hwxface-571)
[ 0.316034] ACPI: (supports S0 S3 S4 S5)
[ 0.316035] ACPI: Using IOAPIC for interrupt routing
[ 0.316057] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.316633] ACPI: ACPI Dock Station Driver: 2 docks/bays found
[ 0.328772] ACPI: Power Resource [PUBS] (on)
[ 0.332509] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.332575] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *7 9 10 11)
[ 0.332638] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.332701] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11)
[ 0.332763] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 *7 9 10 11)
[ 0.332812] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
[ 0.332874] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.332936] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11)
[ 0.332972] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
[ 0.333055] acpi PNP0A08:00: Requesting ACPI _OSC control (0x1d)
[ 0.333132] acpi PNP0A08:00: ACPI _OSC request failed (AE_SUPPORT), returned control mask: 0x0d
[ 0.333133] acpi PNP0A08:00: ACPI _OSC control for PCIe not granted, disabling ASPM
[ 0.333260] PCI host bridge to bus 0000:00
[ 0.333262] pci_bus 0000:00: root bus resource [bus 00-3f]
[ 0.333264] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.333265] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.333267] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.333268] pci_bus 0000:00: root bus resource [mem 0xbfa00000-0xfebfffff]
[ 0.333270] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed4bfff]
[ 0.333277] pci 0000:00:00.0: [8086:0154] type 00 class 0x060000
[ 0.333338] pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
[ 0.333365] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.333416] pci 0000:00:02.0: [8086:0166] type 00 class 0x030000
[ 0.333426] pci 0000:00:02.0: reg 0x10: [mem 0xf1400000-0xf17fffff 64bit]
[ 0.333432] pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.333436] pci 0000:00:02.0: reg 0x20: [io 0x6000-0x603f]
[ 0.333514] pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
[ 0.333534] pci 0000:00:14.0: reg 0x10: [mem 0xf3a20000-0xf3a2ffff 64bit]
[ 0.333603] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 0.333630] pci 0000:00:14.0: System wakeup disabled by ACPI
[ 0.333664] pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
[ 0.333686] pci 0000:00:16.0: reg 0x10: [mem 0xf3a35000-0xf3a3500f 64bit]
[ 0.333761] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 0.333815] pci 0000:00:16.3: [8086:1e3d] type 00 class 0x070002
[ 0.333833] pci 0000:00:16.3: reg 0x10: [io 0x60b0-0x60b7]
[ 0.333842] pci 0000:00:16.3: reg 0x14: [mem 0xf3a3c000-0xf3a3cfff]
[ 0.333964] pci 0000:00:19.0: [8086:1502] type 00 class 0x020000
[ 0.333981] pci 0000:00:19.0: reg 0x10: [mem 0xf3a00000-0xf3a1ffff]
[ 0.333989] pci 0000:00:19.0: reg 0x14: [mem 0xf3a3b000-0xf3a3bfff]
[ 0.333997] pci 0000:00:19.0: reg 0x18: [io 0x6080-0x609f]
[ 0.334058] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[ 0.334085] pci 0000:00:19.0: System wakeup disabled by ACPI
[ 0.334117] pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
[ 0.334137] pci 0000:00:1a.0: reg 0x10: [mem 0xf3a3a000-0xf3a3a3ff]
[ 0.334226] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[ 0.334254] pci 0000:00:1a.0: System wakeup disabled by ACPI
[ 0.334287] pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
[ 0.334302] pci 0000:00:1b.0: reg 0x10: [mem 0xf3a30000-0xf3a33fff 64bit]
[ 0.334368] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.334400] pci 0000:00:1b.0: System wakeup disabled by ACPI
[ 0.334427] pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
[ 0.334502] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.334557] pci 0000:00:1c.1: [8086:1e12] type 01 class 0x060400
[ 0.334632] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.334687] pci 0000:00:1c.2: [8086:1e14] type 01 class 0x060400
[ 0.334762] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[ 0.334792] pci 0000:00:1c.2: System wakeup disabled by ACPI
[ 0.334829] pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
[ 0.334849] pci 0000:00:1d.0: reg 0x10: [mem 0xf3a39000-0xf3a393ff]
[ 0.334936] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 0.334965] pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 0.334997] pci 0000:00:1f.0: [8086:1e55] type 00 class 0x060100
[ 0.335148] pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601
[ 0.335165] pci 0000:00:1f.2: reg 0x10: [io 0x60a8-0x60af]
[ 0.335173] pci 0000:00:1f.2: reg 0x14: [io 0x60bc-0x60bf]
[ 0.335181] pci 0000:00:1f.2: reg 0x18: [io 0x60a0-0x60a7]
[ 0.335188] pci 0000:00:1f.2: reg 0x1c: [io 0x60b8-0x60bb]
[ 0.335195] pci 0000:00:1f.2: reg 0x20: [io 0x6060-0x607f]
[ 0.335203] pci 0000:00:1f.2: reg 0x24: [mem 0xf3a38000-0xf3a387ff]
[ 0.335246] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.335294] pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
[ 0.335309] pci 0000:00:1f.3: reg 0x10: [mem 0xf3a34000-0xf3a340ff 64bit]
[ 0.335329] pci 0000:00:1f.3: reg 0x20: [io 0xefa0-0xefbf]
[ 0.335425] pci 0000:01:00.0: [10de:0ffb] type 00 class 0x030000
[ 0.335432] pci 0000:01:00.0: reg 0x10: [mem 0xf0000000-0xf0ffffff]
[ 0.335439] pci 0000:01:00.0: reg 0x14: [mem 0xc0000000-0xcfffffff 64bit pref]
[ 0.335445] pci 0000:01:00.0: reg 0x1c: [mem 0xd0000000-0xd1ffffff 64bit pref]
[ 0.335450] pci 0000:01:00.0: reg 0x24: [io 0x5000-0x507f]
[ 0.335454] pci 0000:01:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref]
[ 0.341690] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.341695] pci 0000:00:01.0: bridge window [io 0x5000-0x5fff]
[ 0.341700] pci 0000:00:01.0: bridge window [mem 0xf0000000-0xf10fffff]
[ 0.341706] pci 0000:00:01.0: bridge window [mem 0xc0000000-0xd1ffffff 64bit pref]
[ 0.341865] pci 0000:02:00.0: [1180:e823] type 00 class 0x088001
[ 0.341884] pci 0000:02:00.0: MMC controller base frequency changed to 50Mhz.
[ 0.341910] pci 0000:02:00.0: reg 0x10: [mem 0xf3101000-0xf31010ff]
[ 0.342112] pci 0000:02:00.0: supports D1 D2
[ 0.342113] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.342242] pci 0000:02:00.3: [1180:e832] type 00 class 0x0c0010
[ 0.342268] pci 0000:02:00.3: reg 0x10: [mem 0xf3100000-0xf31007ff]
[ 0.342472] pci 0000:02:00.3: supports D1 D2
[ 0.342474] pci 0000:02:00.3: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.348460] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.348465] pci 0000:00:1c.0: bridge window [io 0x4000-0x4fff]
[ 0.348469] pci 0000:00:1c.0: bridge window [mem 0xf3100000-0xf39fffff]
[ 0.348475] pci 0000:00:1c.0: bridge window [mem 0xf1800000-0xf1ffffff 64bit pref]
[ 0.348567] pci 0000:03:00.0: [8086:4238] type 00 class 0x028000
[ 0.348614] pci 0000:03:00.0: reg 0x10: [mem 0xf3000000-0xf3001fff 64bit]
[ 0.348839] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
[ 0.355042] pci 0000:00:1c.1: PCI bridge to [bus 03]
[ 0.355054] pci 0000:00:1c.1: bridge window [mem 0xf3000000-0xf30fffff]
[ 0.355151] acpiphp: Slot [1] registered
[ 0.355157] pci 0000:00:1c.2: PCI bridge to [bus 04-0b]
[ 0.355162] pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff]
[ 0.355165] pci 0000:00:1c.2: bridge window [mem 0xf2800000-0xf2ffffff]
[ 0.355171] pci 0000:00:1c.2: bridge window [mem 0xf2000000-0xf27fffff 64bit pref]
[ 0.356013] ACPI: Enabled 4 GPEs in block 00 to 3F
[ 0.356023] ACPI: \_SB_.PCI0: notify handler is installed
[ 0.356059] Found 1 acpi root devices
[ 0.356106] ACPI: EC: GPE = 0x11, I/O: command/status = 0x66, data = 0x62
[ 0.356165] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.356169] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
[ 0.356170] vgaarb: loaded
[ 0.356171] vgaarb: bridge control possible 0000:01:00.0
[ 0.356172] vgaarb: no bridge control possible 0000:00:02.0
[ 0.356199] PCI: Using ACPI for IRQ routing
[ 0.357682] PCI: pci_cache_line_size set to 64 bytes
[ 0.357820] e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
[ 0.357822] e820: reserve RAM buffer [mem 0x40004000-0x43ffffff]
[ 0.357823] e820: reserve RAM buffer [mem 0xa6b30000-0xa7ffffff]
[ 0.357824] e820: reserve RAM buffer [mem 0x43e600000-0x43fffffff]
[ 0.357892] NetLabel: Initializing
[ 0.357893] NetLabel: domain hash size = 128
[ 0.357894] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.357904] NetLabel: unlabeled traffic allowed by default
[ 0.357921] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 0.357925] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[ 0.360952] Switched to clocksource hpet
[ 0.364213] pnp: PnP ACPI init
[ 0.364226] ACPI: bus type PNP registered
[ 0.364530] system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved
[ 0.364532] system 00:00: [mem 0x000c0000-0x000c3fff] could not be reserved
[ 0.364534] system 00:00: [mem 0x000c4000-0x000c7fff] could not be reserved
[ 0.364535] system 00:00: [mem 0x000c8000-0x000cbfff] has been reserved
[ 0.364537] system 00:00: [mem 0x000cc000-0x000cffff] has been reserved
[ 0.364538] system 00:00: [mem 0x000d0000-0x000d3fff] has been reserved
[ 0.364540] system 00:00: [mem 0x000d4000-0x000d7fff] has been reserved
[ 0.364541] system 00:00: [mem 0x000d8000-0x000dbfff] has been reserved
[ 0.364545] system 00:00: [mem 0x000dc000-0x000dffff] has been reserved
[ 0.364546] system 00:00: [mem 0x000e0000-0x000e3fff] could not be reserved
[ 0.364548] system 00:00: [mem 0x000e4000-0x000e7fff] could not be reserved
[ 0.364549] system 00:00: [mem 0x000e8000-0x000ebfff] could not be reserved
[ 0.364551] system 00:00: [mem 0x000ec000-0x000effff] could not be reserved
[ 0.364552] system 00:00: [mem 0x000f0000-0x000fffff] could not be reserved
[ 0.364554] system 00:00: [mem 0x00100000-0xbf9fffff] could not be reserved
[ 0.364555] system 00:00: [mem 0xfec00000-0xfed3ffff] could not be reserved
[ 0.364557] system 00:00: [mem 0xfed4c000-0xffffffff] could not be reserved
[ 0.364560] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.364624] pnp 00:01: disabling [mem 0xfffff000-0xffffffff] because it overlaps 0000:01:00.0 BAR 6 [mem 0xfff80000-0xffffffff pref]
[ 0.364643] system 00:01: [io 0x0400-0x047f] could not be reserved
[ 0.364644] system 00:01: [io 0x0500-0x057f] has been reserved
[ 0.364646] system 00:01: [io 0x0800-0x080f] has been reserved
[ 0.364647] system 00:01: [io 0x15e0-0x15ef] has been reserved
[ 0.364649] system 00:01: [io 0x1600-0x167f] has been reserved
[ 0.364651] system 00:01: [mem 0xf8000000-0xfbffffff] has been reserved
[ 0.364652] system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 0.364654] system 00:01: [mem 0xfed10000-0xfed13fff] has been reserved
[ 0.364655] system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
[ 0.364657] system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
[ 0.364658] system 00:01: [mem 0xfed45000-0xfed4bfff] has been reserved
[ 0.364661] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.364703] pnp 00:02: Plug and Play ACPI device, IDs PNP0103 (active)
[ 0.364710] pnp 00:03: [dma 4]
[ 0.364723] pnp 00:03: Plug and Play ACPI device, IDs PNP0200 (active)
[ 0.364738] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
[ 0.364763] pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 0.364782] pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.364803] pnp 00:07: Plug and Play ACPI device, IDs LEN0071 PNP0303 (active)
[ 0.364824] pnp 00:08: Plug and Play ACPI device, IDs LEN0015 PNP0f13 (active)
[ 0.364860] pnp 00:09: Plug and Play ACPI device, IDs SMO1200 PNP0c31 (active)
[ 0.365288] pnp: PnP ACPI: found 10 devices
[ 0.365290] ACPI: bus type PNP unregistered
[ 0.371588] pci 0000:01:00.0: no compatible bridge window for [mem 0xfff80000-0xffffffff pref]
[ 0.371620] pci 0000:01:00.0: BAR 6: assigned [mem 0xf1000000-0xf107ffff pref]
[ 0.371622] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.371624] pci 0000:00:01.0: bridge window [io 0x5000-0x5fff]
[ 0.371627] pci 0000:00:01.0: bridge window [mem 0xf0000000-0xf10fffff]
[ 0.371629] pci 0000:00:01.0: bridge window [mem 0xc0000000-0xd1ffffff 64bit pref]
[ 0.371632] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.371635] pci 0000:00:1c.0: bridge window [io 0x4000-0x4fff]
[ 0.371640] pci 0000:00:1c.0: bridge window [mem 0xf3100000-0xf39fffff]
[ 0.371644] pci 0000:00:1c.0: bridge window [mem 0xf1800000-0xf1ffffff 64bit pref]
[ 0.371650] pci 0000:00:1c.1: PCI bridge to [bus 03]
[ 0.371655] pci 0000:00:1c.1: bridge window [mem 0xf3000000-0xf30fffff]
[ 0.371663] pci 0000:00:1c.2: PCI bridge to [bus 04-0b]
[ 0.371666] pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff]
[ 0.371671] pci 0000:00:1c.2: bridge window [mem 0xf2800000-0xf2ffffff]
[ 0.371675] pci 0000:00:1c.2: bridge window [mem 0xf2000000-0xf27fffff 64bit pref]
[ 0.371681] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 0.371683] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 0.371684] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.371686] pci_bus 0000:00: resource 7 [mem 0xbfa00000-0xfebfffff]
[ 0.371687] pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed4bfff]
[ 0.371688] pci_bus 0000:01: resource 0 [io 0x5000-0x5fff]
[ 0.371690] pci_bus 0000:01: resource 1 [mem 0xf0000000-0xf10fffff]
[ 0.371691] pci_bus 0000:01: resource 2 [mem 0xc0000000-0xd1ffffff 64bit pref]
[ 0.371693] pci_bus 0000:02: resource 0 [io 0x4000-0x4fff]
[ 0.371694] pci_bus 0000:02: resource 1 [mem 0xf3100000-0xf39fffff]
[ 0.371695] pci_bus 0000:02: resource 2 [mem 0xf1800000-0xf1ffffff 64bit pref]
[ 0.371697] pci_bus 0000:03: resource 1 [mem 0xf3000000-0xf30fffff]
[ 0.371698] pci_bus 0000:04: resource 0 [io 0x3000-0x3fff]
[ 0.371700] pci_bus 0000:04: resource 1 [mem 0xf2800000-0xf2ffffff]
[ 0.371701] pci_bus 0000:04: resource 2 [mem 0xf2000000-0xf27fffff 64bit pref]
[ 0.371726] NET: Registered protocol family 2
[ 0.371936] TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
[ 0.372200] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.372304] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.372320] TCP: reno registered
[ 0.372335] UDP hash table entries: 8192 (order: 6, 262144 bytes)
[ 0.372381] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
[ 0.372455] NET: Registered protocol family 1
[ 0.372464] pci 0000:00:02.0: Boot video device
[ 0.372838] PCI: CLS 64 bytes, default 64
[ 0.372874] Unpacking initramfs...
[ 0.419708] Freeing initrd memory: 3172K (ffff8800379be000 - ffff880037cd7000)
[ 0.419712] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.419714] software IO TLB [mem 0xa2b30000-0xa6b30000] (64MB) mapped at [ffff8800a2b30000-ffff8800a6b2ffff]
[ 0.419965] Scanning for low memory corruption every 60 seconds
[ 0.420184] audit: initializing netlink socket (disabled)
[ 0.420191] type=2000 audit(1386283845.413:1): initialized
[ 0.430696] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.431915] zbud: loaded
[ 0.432021] VFS: Disk quotas dquot_6.5.2
[ 0.432054] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.432181] msgmni has been set to 31247
[ 0.432413] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.432453] io scheduler noop registered
[ 0.432454] io scheduler deadline registered
[ 0.432473] io scheduler cfq registered (default)
[ 0.432595] pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
[ 0.432864] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.432875] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.432907] vesafb: mode is 1920x1080x32, linelength=7680, pages=0
[ 0.432908] vesafb: scrolling: redraw
[ 0.432909] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.433568] vesafb: framebuffer at 0xe0000000, mapped to 0xffffc90005c80000, using 8128k, total 8128k
[ 0.566342] Console: switching to colour frame buffer device 240x67
[ 0.698577] fb0: VESA VGA frame buffer device
[ 0.698590] intel_idle: MWAIT substates: 0x21120
[ 0.698591] intel_idle: v0.4 model 0x3A
[ 0.698592] intel_idle: lapic_timer_reliable_states 0xffffffff
[ 0.698765] GHES: HEST is not enabled!
[ 0.698809] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.719500] 0000:00:16.3: ttyS0 at I/O 0x60b0 (irq = 19, base_baud = 115200) is a 16550A
[ 0.719641] Linux agpgart interface v0.103
[ 0.719702] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[ 0.721201] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.721210] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.721298] mousedev: PS/2 mouse device common for all mice
[ 0.721324] rtc_cmos 00:06: RTC can wake from S4
[ 0.721444] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
[ 0.721474] rtc_cmos 00:06: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 0.721482] Intel P-state driver initializing.
[ 0.721492] Intel pstate controlling: cpu 0
[ 0.721502] Intel pstate controlling: cpu 1
[ 0.721510] Intel pstate controlling: cpu 2
[ 0.721520] Intel pstate controlling: cpu 3
[ 0.721532] Intel pstate controlling: cpu 4
[ 0.721541] Intel pstate controlling: cpu 5
[ 0.721549] Intel pstate controlling: cpu 6
[ 0.721558] Intel pstate controlling: cpu 7
[ 0.721630] drop_monitor: Initializing network drop monitor service
[ 0.721685] TCP: cubic registered
[ 0.721757] NET: Registered protocol family 10
[ 0.721886] NET: Registered protocol family 17
[ 0.721894] Key type dns_resolver registered
[ 0.722224] registered taskstats version 1
[ 0.722596] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 0.723178] Magic number: 9:534:855
[ 0.723283] rtc_cmos 00:06: setting system clock to 2013-12-05 22:50:46 UTC (1386283846)
[ 0.723323] PM: Checking hibernation image partition /dev/sda6
[ 0.726752] PM: Hibernation image not present or could not be loaded.
[ 0.727429] Freeing unused kernel memory: 1144K (ffffffff818cb000 - ffffffff819e9000)
[ 0.727431] Write protecting the kernel read-only data: 8192k
[ 0.729430] Freeing unused kernel memory: 1012K (ffff880001503000 - ffff880001600000)
[ 0.730122] Freeing unused kernel memory: 340K (ffff8800017ab000 - ffff880001800000)
[ 0.737327] systemd-udevd[79]: starting version 208
[ 0.753625] ACPI: bus type USB registered
[ 0.753654] usbcore: registered new interface driver usbfs
[ 0.753672] usbcore: registered new interface driver hub
[ 0.753762] usbcore: registered new device driver usb
[ 0.754364] sdhci: Secure Digital Host Controller Interface driver
[ 0.754367] sdhci: Copyright(c) Pierre Ossman
[ 0.754471] pcieport 0000:00:1c.0: driver skip pci_set_master, fix it!
[ 0.754490] SCSI subsystem initialized
[ 0.754718] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.755262] ehci-pci: EHCI PCI platform driver
[ 0.755386] ehci-pci 0000:00:1a.0: setting latency timer to 64
[ 0.755406] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 0.755414] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 0.755427] ehci-pci 0000:00:1a.0: debug port 2
[ 0.756165] libata version 3.00 loaded.
[ 0.759355] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[ 0.759370] ehci-pci 0000:00:1a.0: irq 16, io mem 0xf3a3a000
[ 0.767505] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 0.767646] hub 1-0:1.0: USB hub found
[ 0.767652] hub 1-0:1.0: 3 ports detected
[ 0.767804] ehci-pci 0000:00:1d.0: setting latency timer to 64
[ 0.767809] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 0.767812] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 0.767823] ehci-pci 0000:00:1d.0: debug port 2
[ 0.771708] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 0.771720] ehci-pci 0000:00:1d.0: irq 23, io mem 0xf3a39000
[ 0.780896] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 0.780996] hub 2-0:1.0: USB hub found
[ 0.781000] hub 2-0:1.0: 3 ports detected
[ 0.781193] xhci_hcd 0000:00:14.0: setting latency timer to 64
[ 0.781197] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 0.781202] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[ 0.781297] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[ 0.781317] xhci_hcd 0000:00:14.0: irq 41 for MSI/MSI-X
[ 0.781456] hub 3-0:1.0: USB hub found
[ 0.781467] hub 3-0:1.0: 4 ports detected
[ 0.781705] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 0.781708] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[ 0.781799] hub 4-0:1.0: USB hub found
[ 0.781807] hub 4-0:1.0: 4 ports detected
[ 0.791001] ahci 0000:00:1f.2: version 3.0
[ 0.791067] ahci 0000:00:1f.2: irq 42 for MSI/MSI-X
[ 0.791088] ahci 0000:00:1f.2: SSS flag set, parallel bus scan disabled
[ 0.804224] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x17 impl SATA mode
[ 0.804231] ahci 0000:00:1f.2: flags: 64bit ncq ilck stag pm led clo pio slum part ems sxs apst
[ 0.804239] ahci 0000:00:1f.2: setting latency timer to 64
[ 0.820938] firewire_ohci 0000:02:00.3: added OHCI v1.10 device as card 0, 4 IR + 4 IT contexts, quirks 0x11
[ 0.820989] sdhci-pci 0000:02:00.0: SDHCI controller found [1180:e823] (rev 5)
[ 0.821107] mmc0: SDHCI controller on PCI [0000:02:00.0] using DMA
[ 0.824627] scsi0 : ahci
[ 0.824773] scsi1 : ahci
[ 0.824907] scsi2 : ahci
[ 0.825041] scsi3 : ahci
[ 0.825234] scsi4 : ahci
[ 0.825350] scsi5 : ahci
[ 0.825384] ata1: SATA max UDMA/133 abar m2048@0xf3a38000 port 0xf3a38100 irq 42
[ 0.825387] ata2: SATA max UDMA/133 abar m2048@0xf3a38000 port 0xf3a38180 irq 42
[ 0.825390] ata3: SATA max UDMA/133 abar m2048@0xf3a38000 port 0xf3a38200 irq 42
[ 0.825391] ata4: DUMMY
[ 0.825406] ata5: SATA max UDMA/133 abar m2048@0xf3a38000 port 0xf3a38300 irq 42
[ 0.825406] ata6: DUMMY
[ 1.074138] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 1.144102] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.145449] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.145455] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.146823] ata1.00: ATA-8: HGST HTS725050A7E630, GH2ZB550, max UDMA/133
[ 1.146827] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.148298] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.148304] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.149813] ata1.00: configured for UDMA/133
[ 1.150087] scsi 0:0:0:0: Direct-Access ATA HGST HTS725050A7 GH2Z PQ: 0 ANSI: 5
[ 1.198525] hub 1-1:1.0: USB hub found
[ 1.198715] hub 1-1:1.0: 6 ports detected
[ 1.307453] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 1.320895] firewire_core 0000:02:00.3: created device fw0: GUID 3c970effbe0ba2ff, S400
[ 1.420670] tsc: Refined TSC clocksource calibration: 2693.881 MHz
[ 1.431513] hub 2-1:1.0: USB hub found
[ 1.431588] hub 2-1:1.0: 8 ports detected
[ 1.467351] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.471615] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded
[ 1.473091] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded
[ 1.476312] ata2.00: ATAPI: HL-DT-ST DVDRAM GT80N, LT20, max UDMA/133
[ 1.480154] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded
[ 1.481633] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded
[ 1.484853] ata2.00: configured for UDMA/133
[ 1.493873] scsi 1:0:0:0: CD-ROM HL-DT-ST DVDRAM GT80N LT20 PQ: 0 ANSI: 5
[ 1.590645] usb 3-2: new low-speed USB device number 2 using xhci_hcd
[ 1.611303] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 1.611311] usb 3-2: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 1.613287] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.623187] usbcore: registered new interface driver usbhid
[ 1.623191] usbhid: USB HID core driver
[ 1.623948] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/input/input2
[ 1.624086] hid-generic 0003:046D:C505.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-2/input0
[ 1.624501] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/input/input3
[ 1.624758] hid-generic 0003:046D:C505.0002: input,hidraw1: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-2/input1
[ 1.677468] usb 1-1.3: new full-speed USB device number 3 using ehci-pci
[ 1.813904] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.814517] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.814523] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.814902] ata3.00: ATA-8: SAMSUNG MZMPC032HBCD-000L1, CXM13L1Q, max UDMA/133
[ 1.814908] ata3.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.815417] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.815424] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.815843] ata3.00: configured for UDMA/133
[ 1.815996] scsi 2:0:0:0: Direct-Access ATA SAMSUNG MZMPC032 CXM1 PQ: 0 ANSI: 5
[ 1.827413] usb 1-1.4: new full-speed USB device number 4 using ehci-pci
[ 1.980746] usb 1-1.6: new high-speed USB device number 5 using ehci-pci
[ 2.133788] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.138079] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 2.138084] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 2.138107] sd 2:0:0:0: [sdb] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB)
[ 2.138214] sd 0:0:0:0: [sda] Write Protect is off
[ 2.138218] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.138263] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.138291] sd 2:0:0:0: [sdb] Write Protect is off
[ 2.138294] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 2.138365] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.139366] sdb: sdb1
[ 2.139583] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 2.140832] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 2.140834] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.140984] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 2.150609] usb 2-1.5: new low-speed USB device number 3 using ehci-pci
[ 2.217042] raid6: sse2x1 6045 MB/s
[ 2.222964] sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
[ 2.224086] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.242780] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input4
[ 2.242927] hid-generic 0003:046D:C051.0003: input,hidraw2: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1.5/input0
[ 2.273683] raid6: sse2x2 9288 MB/s
[ 2.330330] raid6: sse2x4 13180 MB/s
[ 2.330331] raid6: using algorithm sse2x4 (13180 MB/s)
[ 2.330332] raid6: using ssse3x2 recovery algorithm
[ 2.330416] xor: automatically using best checksumming function:
[ 2.363659] avx : 27280.800 MB/sec
[ 2.365888] bio: create slab <bio-1> at 1
[ 2.366416] Btrfs loaded
[ 2.366872] btrfs: device fsid 267f069c-11da-4d2a-88fa-00cab4e28149 devid 1 transid 2746 /dev/sdb1
[ 2.420417] Switched to clocksource tsc
[ 2.749348] btrfs: device fsid f6907d81-f46f-4911-8600-858e8b6bd1a0 devid 1 transid 3707 /dev/sda5
[ 3.007064] PM: Starting manual resume from disk
[ 3.007067] PM: Hibernation image partition 8:6 present
[ 3.007068] PM: Looking for hibernation image.
[ 3.007178] PM: Image not found (code -22)
[ 3.007183] PM: Hibernation image not present or could not be loaded.
[ 3.014955] btrfs: device fsid 267f069c-11da-4d2a-88fa-00cab4e28149 devid 1 transid 2746 /dev/sdb1
[ 3.015285] btrfs: disk space caching is enabled
[ 3.028402] Btrfs detected SSD devices, enabling SSD mode
[ 3.211825] systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
[ 3.212136] systemd[1]: Set hostname to <ho-think>.
[ 3.252550] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 3.252605] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 3.252618] systemd[1]: Starting Remote File Systems.
[ 3.252629] systemd[1]: Reached target Remote File Systems.
[ 3.252638] systemd[1]: Starting LVM2 metadata daemon socket.
[ 3.252667] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 3.252675] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ 3.252701] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 3.252709] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 3.252724] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 3.252731] systemd[1]: Starting Delayed Shutdown Socket.
[ 3.252748] systemd[1]: Listening on Delayed Shutdown Socket.
[ 3.252758] systemd[1]: Starting Journal Socket.
[ 3.252795] systemd[1]: Listening on Journal Socket.
[ 3.253090] systemd[1]: Starting Apply Kernel Variables...
[ 3.253532] systemd[1]: Starting Journal Service...
[ 3.253811] systemd[1]: Started Journal Service.
[ 3.287546] systemd-journald[182]: Vacuuming done, freed 0 bytes
[ 3.390618] btrfs: use ssd allocation scheme
[ 3.390622] btrfs: disk space caching is enabled
[ 3.400329] systemd-udevd[218]: starting version 208
[ 3.490322] input: PC Speaker as /devices/platform/pcspkr/input/input5
[ 3.491089] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 3.491746] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input6
[ 3.491865] ACPI: Lid Switch [LID]
[ 3.492466] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \_SB_.PCI0.LPC_.PMIO 1 (20130725/utaddress-251)
[ 3.492471] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.492475] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.LPC_.LPIO 1 (20130725/utaddress-251)
[ 3.492490] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.492491] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \_SB_.PCI0.LPC_.LPIO 1 (20130725/utaddress-251)
[ 3.492494] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.492495] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 3.493000] pps_core: LinuxPPS API ver. 1 registered
[ 3.493002] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 3.493659] ACPI: Requesting acpi_cpufreq
[ 3.493823] PTP clock support registered
[ 3.494020] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input7
[ 3.494025] ACPI: Sleep Button [SLPB]
[ 3.494069] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
[ 3.494071] ACPI: Power Button [PWRF]
[ 3.494675] mei_me 0000:00:16.0: setting latency timer to 64
[ 3.494714] mei_me 0000:00:16.0: irq 43 for MSI/MSI-X
[ 3.494990] ACPI: AC Adapter [AC] (on-line)
[ 3.495691] tpm_tis 00:09: 1.2 TPM (device-id 0x0, rev-id 78)
[ 3.498616] Non-volatile memory driver v1.3
[ 3.498683] [drm] Initialized drm 1.1.0 20060810
[ 3.499437] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
[ 3.502565] ACPI: Battery Slot [BAT0] (battery present)
[ 3.502633] thinkpad_acpi: ThinkPad ACPI Extras v0.24
[ 3.502635] thinkpad_acpi: http://ibm-acpi.sf.net/
[ 3.502636] thinkpad_acpi: ThinkPad BIOS G5ET93WW (2.53 ), EC unknown
[ 3.502637] thinkpad_acpi: Lenovo ThinkPad W530, model 2447DW0
[ 3.504741] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 3.504742] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[ 3.504806] e1000e 0000:00:19.0: setting latency timer to 64
[ 3.504855] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 3.504869] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
[ 3.505719] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
[ 3.505814] thinkpad_acpi: radio switch found; radios are enabled
[ 3.507612] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[ 3.507614] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
[ 3.508991] wmi: Mapper loaded
[ 3.510574] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[ 3.512202] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
[ 3.512859] thermal LNXTHERM:00: registered as thermal_zone0
[ 3.512862] ACPI: Thermal Zone [THM0] (51 C)
[ 3.512964] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
[ 3.513826] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input9
[ 3.519211] cfg80211: Calling CRDA to update world regulatory domain
[ 3.529719] Intel(R) Wireless WiFi driver for Linux, in-tree:
[ 3.529721] Copyright(c) 2003-2013 Intel Corporation
[ 3.529746] pcieport 0000:00:1c.1: driver skip pci_set_master, fix it!
[ 3.529786] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 3.529839] iwlwifi 0000:03:00.0: irq 45 for MSI/MSI-X
[ 3.541982] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x17
[ 3.557020] media: Linux media interface: v0.10
[ 3.559314] Bluetooth: Core ver 2.16
[ 3.559324] NET: Registered protocol family 31
[ 3.559325] Bluetooth: HCI device and connection manager initialized
[ 3.559331] Bluetooth: HCI socket layer initialized
[ 3.559332] Bluetooth: L2CAP socket layer initialized
[ 3.559338] Bluetooth: SCO socket layer initialized
[ 3.559760] Linux video capture interface: v2.00
[ 3.561090] btrfs: device fsid 267f069c-11da-4d2a-88fa-00cab4e28149 devid 1 transid 2747 /dev/sdb1
[ 3.563306] tpm_tis 00:09: TPM is disabled/deactivated (0x6)
[ 3.565201] usbcore: registered new interface driver btusb
[ 3.565757] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b2ea)
[ 3.567801] iTCO_vendor_support: vendor-support=0
[ 3.568229] input: Integrated Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input11
[ 3.568341] usbcore: registered new interface driver uvcvideo
[ 3.568342] USB Video Class driver (1.1.1)
[ 3.568802] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[ 3.568825] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460)
[ 3.568884] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 3.575973] microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x17
[ 3.579387] microcode: CPU2 sig=0x306a9, pf=0x10, revision=0x17
[ 3.580314] microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x17
[ 3.580610] nvidia: module license 'NVIDIA' taints kernel.
[ 3.580612] Disabling lock debugging due to kernel taint
[ 3.580964] microcode: CPU4 sig=0x306a9, pf=0x10, revision=0x17
[ 3.581262] microcode: CPU5 sig=0x306a9, pf=0x10, revision=0x17
[ 3.581662] microcode: CPU6 sig=0x306a9, pf=0x10, revision=0x17
[ 3.581969] microcode: CPU7 sig=0x306a9, pf=0x10, revision=0x17
[ 3.582235] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 3.585585] nvidia 0000:01:00.0: enabling device (0000 -> 0003)
[ 3.585626] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 3.585753] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 0
[ 3.585756] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 331.20 Wed Oct 30 17:43:35 PDT 2013
[ 3.590299] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm
[ 3.604935] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 3.604939] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 3.604940] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 3.604942] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
[ 3.604991] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 3.611807] kvm: disabled by bios
[ 3.622449] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 3.643289] systemd-udevd[222]: renamed network interface wlan0 to wlp3s0
[ 3.699041] e1000e 0000:00:19.0 eth0: registered PHC clock
[ 3.699043] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 3c:97:0e:be:0b:a2
[ 3.699045] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 3.699088] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 1000FF-0FF
[ 3.699268]I decided to use nouveau instead of nvidia and now I got my external an internal display working.
-
Is Mail.app one of the "erratic" behavior apps with a reset system clock?
I am hoping someone can help with a fine detail of mail.app (v2.1.3) behavior.
I had an incident where an iMac sent out 200+ smtp hits a minute and was tossed of the network for presumed zombie spaming.
I think I have actually tracked the problem to an unfortunate conjunction of circumstances that is actually innocent (if still annoying)
Let me set up the story:
1. This is a common use computer, so Mail is not configured (except that it is --I'll get to that in a moment) and
2. Safari will invoke Mail when you click on an "email link"
Mostly everyone just quits mail if they goof and click an email link.
BUT some time ago at least one person invoked Mail and composed a message. This message, naturally, remained in the outbox ever since. That person learned that they can't send email that way, so ever since they just cmd-Q Mail.
BUT Before this person learned, they walked through the mail-config and told mail to try hitting smtp.mac.com:"nonExistantUser".
So that covers the lead-up. Two days ago, mail was invoked via a Safari link, BUT it wasn't quit, it was sent to the background.
Where it undoubtedly tried to send the outbox repeatedly until it was kicked off the network.
Here is what I don't understand:
Under this scenario of a mis-configured .mac address, will mail repeatedly try and fail to smtp at the maximum possible rate?
OR
Is the one other factor I am about to describe responsible?
The one other factor:
The clock battery is dead and there was a power failure at 4am that day.
The system clock reset to 1969.
Of course, nobody reset it.
Is mail.app one of the apps that the finder message warns "may behave erratically"?
(a GROSS simplification) does it have a bit of code like:
1 check time-of-last-send-mail-attempt
check newest-item-in-outbox
if newest-item more recent then last-send-attempt
do send-mail and record time-of-last-send-mail-attempt
and go to 1
else wait X minutes and go to 1
which, if the clock was mis-set to 1969 would always record a last-send-attempt prior to anything in the outbox and trigger a send loop.
Does anyone know if either Mail is tenacious about sending to a bad .mac address, or gets ridiculous under this circumstance for bad-clock-set?
MarcI am hoping someone can help with a fine detail of mail.app (v2.1.3) behavior.
I had an incident where an iMac sent out 200+ smtp hits a minute and was tossed of the network for presumed zombie spaming.
I think I have actually tracked the problem to an unfortunate conjunction of circumstances that is actually innocent (if still annoying)
Let me set up the story:
1. This is a common use computer, so Mail is not configured (except that it is --I'll get to that in a moment) and
2. Safari will invoke Mail when you click on an "email link"
Mostly everyone just quits mail if they goof and click an email link.
BUT some time ago at least one person invoked Mail and composed a message. This message, naturally, remained in the outbox ever since. That person learned that they can't send email that way, so ever since they just cmd-Q Mail.
BUT Before this person learned, they walked through the mail-config and told mail to try hitting smtp.mac.com:"nonExistantUser".
So that covers the lead-up. Two days ago, mail was invoked via a Safari link, BUT it wasn't quit, it was sent to the background.
Where it undoubtedly tried to send the outbox repeatedly until it was kicked off the network.
Here is what I don't understand:
Under this scenario of a mis-configured .mac address, will mail repeatedly try and fail to smtp at the maximum possible rate?
OR
Is the one other factor I am about to describe responsible?
The one other factor:
The clock battery is dead and there was a power failure at 4am that day.
The system clock reset to 1969.
Of course, nobody reset it.
Is mail.app one of the apps that the finder message warns "may behave erratically"?
(a GROSS simplification) does it have a bit of code like:
1 check time-of-last-send-mail-attempt
check newest-item-in-outbox
if newest-item more recent then last-send-attempt
do send-mail and record time-of-last-send-mail-attempt
and go to 1
else wait X minutes and go to 1
which, if the clock was mis-set to 1969 would always record a last-send-attempt prior to anything in the outbox and trigger a send loop.
Does anyone know if either Mail is tenacious about sending to a bad .mac address, or gets ridiculous under this circumstance for bad-clock-set?
Marc -
Failure to fix my cable for over a year and a half! HELP!
Failure to fix my cable for over a year and a half! HELP!
I regretfully have to inform you that I might have to discontinue using Comcast, for the following reasons if I cannot et you to resolve these issues. It should be noted that this is something that I do not want to have to do. However, basically I have no choice.
1. Repeated and Constant Internet Issues and Poor TV Quality for over a year.
2. A substandard quality of service, just even compared to my next door neighbors who has Comcast. The service has issues daily. Not a week has gone bye without an issue either small or large.
3. Constant and repeated interrupt of service and an overall low quality of product. Time Outs, High Ping rates into the 100s and 200s, Cable Light Off, Poor Quality of TV picture, fuzzy, Digital Blocking even on non-digital channels with or without box, Occasional CB Radio chatter over interment connection <-(the odd one).
4. The constant run around from the employee’s at Comcast and Service Department who either are unable to fix my problem, or unwilling to fix my problem, or have no one qualified to fix the problem. The amount of service calls and tech support personal I have had come to my house and had to call is so numerous I cannot even recall the amount.
5. Paying full price for a substandard quality and product while others around me do not have too. Including my next door neighbor which does not seem to have an issue.
The Story-
I purchased this house over a year and a half ago. Note; I did think it was odd that the pervious owner of this house had Comcast TV, but a DSL internet connection (I know now why he had to do that). In a brief conversation with him recently when he was visiting our next door neighbors he told me of how he had the same issues and had to switch to DSL.
I am, and always have been an avid Cable user and in particular for the Internet as the Broadband just makes it so much more enjoyable. I used Time Warner Cable for over 7-years prior to “having to” use Comcast with great service and good connection and a highly enjoyable time over the internet playing games and surfing the web. I have to use the words :“having too”, as you are the only Broad Band Internet connection in my area currently (I moved to the Burbs, not the Boonies) so I still don’t understand why my choices are limited. Must be nice to have a Monopoly though. : ), and I am starting to think this maybe part of my problems and why nothing is being done.
In any case, my internet use is for entertainment only. Surfing the Web, playing video games, Online Classes, and whatnot. Nothing life treating, or a must have service and basically, fun for the family, not for frustration. I like to use Cable as I never have to worry about the line cutting out or losing connection. This used to be the case, but with Comcast I do have to worry about this, and it happens often. Simply put: it is NOT always ON as advertised, at least for me.
The Issues-
From day one, I have had nothing but repeated and constant issues with my internet service. I don’t even think I had Comcast a week before I had to make my fist service call. See I was used to another Cable service and silly me expected my cable to work. From there it was all downhill. I have had so many service calls its actually outlandish and would be funny if it was someone else. Its like a TV sitcom actually.
Each and every service call goes the same way. Tech comes out, stands around, recognizes the problem and leaves. No fixes mind you, and the reasons are below.
Recent History-
With the internet on the fritz again and only seeming to get worse I decided to call and have someone come out and check it. A preemptive strike on my part in other words, before it totally blew out like it does and taking days for it to come back on. I have been dealing with this for over a year getting kind of frustrated with the whole process.
I talk to the service department and they also see the issue (sporadic interrupt of service and poor quality). With so many problems and the list ever growing most likely on my report the service guy said he would send a Line Tech out to check my problem on Monday (the ninth).
I think to myself finally some progress and it only took a year, a real Line Tech my issue is sure to be solved.
Unfortunately, the apparent Line Tech does and did the same as every other tech sent to the house. Set around for 20 or so minutes futzing around with the computer. Notes the issue of single loss and poor TV quality makes some notes and says sign here. *take note of paragraph below about Line Tech.
Around Thursday, I call up the service department basically asking if and when my service problems will be fixed. With little shock and surprise I was told that nothing is scheduled the last service call the Line Tech was not really a Line Tech and I should have been called back and or at least informed of that a Line Tech was not scheduled to be sent. This is normal by the way.
The Phone Tech checked my service and found that an issue did exist and proceeded to tell my that he would advise his supervisor of the issue. He also stated that if someone had not called me by 6:00PM this coming Saturday, that I could call and he would expedite matters.
Tick-Tock-Tick-Tock-Tick-Tock-Tick-Tock
Saturday at 6:20PM I call up the service department, punch in my phone number and low and behold I’m sent immediately to the Clams Department instead of the Service Department LOL.
After explaining the issue to the Clams Department (my thinking is at this point is; why pay for it if its not working and they wont fix it) I am transferred to the Service Department after a brief expiation of the issue. I guess I am a little late with my bill, but can you blame me?
The Run Around-
Talking to a new service persona again which is the same with ever tech sent to the house (Never the same one twice). Apparently nothing is on my report about this call I made earlier, or he does not note it.
The new service tech while helpful and curious taking the brunt of my frustrations at this point goes through the same procedures that I have been through so many times now I know them by hart. I acknowledge the fact ahead of time to myself that my tone although frustrated is nothing personal, and the service tech should not take it personally. Its just that at this point I’m beyond frustrated. I try to be as understanding and curious as I can while he tries to help me.
I explain the repeated problems and what is going on. In this instants the service tech mentions something about some service package (come kind of other signal maybe being sent to the modem).
At the time my internet is somewhat working with only a few time outs and just above normal pings so I cant really blame him for not seeing an issue. I’m mainly calling just to find out why I didn’t receive a phone call, or get another appointment to have this checked into.
My service was cutting out right before I called, which is why I called. The service tech just happened to check my service while it was working for 20 or so minutes. : P
Although, I am sure the Tech knew what he was doing and seemed very knowledgeable and probably thought he had resolved an issue that has been plaguing me for over a year now I knew nothing had changed. (this has happened before by the way same exact procedure in fact, and must be part of the training).
I’m trying to hold my volume down and not get too upset. Its not the techs fault and probably does not know I have gone through this procedure before. I want to try to explain this but he is busy trying to work his magic. I remain calm, but I even made the statement that I would probably be calling him back in 15-minutes. I try to end the conversation and phone call as politely as I can. Its not his fault, his just trying to do a job.
Anthony
Case Number: 053300005
Well not even five minutes later you will never guess what………… Pings start dropping and the internet is cutting out on me.
The Problem-
The problem has been defined as a Line Issue, and an On and Off interrupt of service. At this point even the TV is being affected. From the first time I called (like over a year ago) the issue is defined to me as an On OFF issue.
The Problem trying to get this fix-
You apparently have no Line Techs.
The Pole near my house is apparently a Forbidden Area that no one must go near. LOL
You cannot get these people to go near it apparently. They only classify the problem and go away never to be seen nor heard from again.
Now honestly I can understand with employee issues seeing this happening from time to time, but not for over a year and with service calls up in the tens and twenties…..
Worst of All-
I think the worst part of all of this is I have become so used to the poor and substandard quality of service. So used to it that I only call or complain when its totally out or is visually not working correctly and can be tested. I don’t call and complain because its not working as Advertised, because in fact it really never did or does.
I also, don’t call a lot of the times because of dealing with the service department. If its working at that moment they cannot define the problems. Not really anyone’s fault as it looks like its working even if the pings are in the 200 range or currently no time outs are accruing. I mean at least its working, and they say Speed is not Guaranteed anyway.
The Forgotten and Unanswered Questions-
I don’t know about the rest of you but sometimes while talking to people I forget to ask questions or the question does not come to mind until the conversation is over with. In any case, the Phone Service Tech said that what he did should have been done along time ago.
However, if my cable was somehow magically fixed by what he did I still have these questions;
1.What happened to my Service Call and why did no one call my by 6:00PM today?
-I waited around for the call actually, and I really would like to get this issue resolved.
2. Why is my TV picture still bad?
3. Although my internet seemed to be working today and only cut out once for a brief period of time why did the supposed fix of the Phone Tech double and even triple my pings, and still occasionally cuts out?
This is usually when I can tell its going to start acting up as the interrupts become more frequent and growing in intensity and length. I always have them anyway I am used to it.
However, on the other hand, I am already seeing time outs and interrupts and should I be paying full price for a lower quality of service compared just to my next door neighbor ?
This is a very hard question for me to ask myself. I like using Cable rather than a Dialup Service, but there is also the whole principle to the matter as well.
*Should I pay full price for a service that is substandard to everyone else’s?
*Should I pay full price for the same connecting I used to get a discount for, because of the poor quality?
*Should I call and complain everyday and turn this into a daily ritual? I cant keep taking time off from work to wait for someone who does nothing except stand around and futz with the computer for 20mintes and recognize the issue.
*Should I have to complain so much and go through the process which is like pulling teeth to get you guys to do something about it?
Maybe this is all my fault, and I am doing something wrong. What do I have to do to get this fixed? I don’t want to have to get DSL, so someone please help me. What am I doing wrong. I cannot keep taking time off from work to have someone come out only to recognize I have an issue and never fix it.
To Whomever at Comcast:
Is it so wrong of me to want, after a year of having repeated service calls with no resolution to the issue to ask, and request, that the cable service provided to me is the same as everyone else’s?
If you handed noticed-
Well if you haven’t noticed by now I am really tying to get this situation fixed and resolved. Mostly because, it is to the point where I am going to have to stop using Comcast and get DSL, or AOL or something because its more reliable. Which I really don’t want to do in the first place cable is supposed to be reliable and always on and faster.
A little over a year not and I am running out of options though.
Seriously Cant anyone help?
Message was edited by: Anon1245678Part/3-
Swami
Wed/Jan/18
An eventful day-
Just a few minutes ago, got a phone call from the Comcast Cable GUY (2:20pm). He then Says he’s been working on trying to find the problem from 1 O’clock. Apparently, and maybe the case, (it was a brief conversation and he will get back to me later) but maybe some part has gone bad somewhere and he said he was waiting on a phone call from someone else.
In any case, he said that they are trying to clear up the problem and that its been running better sense the Jan/14.….? Not here it hasn’t. LOL We also had a brief discussion about how due to my repeated use of the internet that maybe I notices this more than other people do. My next door neighbor does not seem to have any issues last time I talk to them. But the guy said someone who lives on Broadway (few streets over) has been having issues too so maybe its this part.
I said; So I should see some improvement today… silence…and a brief pause….. After I find out what the problem is Ill come over and discuss it with you so you know exactly what is going on.
I do have a feeling I am going to be told this is going to take weeks to fix or at least awhile. Apparently a Part is needed maybe. Ill have to wait until the guy shows and gives me a full explanation though.
I called my wife and told her of the event and she is pretty emphatic about returning the TV cable box as the TV picture is better without it and she only really looks at the local or 3-like 70 anyway. She was like “Bad Part?” well its been bad for over a year then! We should get a refund for the whole year then… Sorry Comcast she is on a Refund Kick… I just want it to work.
Part/4-
The Tech Supervisor Mark, showed up at my door and tried to explain the issues. I felt kind of bad cause I probably know he got Chewed on along with some other people probably. At least they sent someone older and who looked like he had more experience and knew what he was talking about and could actually find the issue.
I tried to be as apologetic as I could, and tried to explain that its just because this has been such a persistent issue over the past year and a half, and I have had way too many service calls for this not to be fix by now. I even went so far as to explain; it’s a new year and we are trying to get this problem finally fixed. I was also quick to mention how nice it was outside and that at least it was a good day to run around outside. I would have felt really bad if it was raining or snowing out, but it was a nice day probably upper 60s and sunny.
We briefly discussed the issues and he said he and some others (I guess) had been working t the Head End fixing some issues… Which actually might have fixed my TV picture, seems better right now currently though. Currently NO digital Blocking on any channels currently, but as I said, it’s a sporadic issue popping up one day and going away the next or the problem lasting weeks and months then nothing for a few days and weeks.
Mark, tried to explain that maybe the problem that I might been having (apparently along with a few others) was that a Temporary Line was connected on the MAIN. Basically 1” Main Line Cable run it to cable like that’s in your house (cant remember but off hand I think its 5, 10 or 15 gauge cable) and back to 1” Main Line Cable. It was all a little technical, I just nodded and said yes, and at least you might have found the issue right?
He didn’t know how long that had been like that, and I said; probably for over three years as the previous owner had issues too, or at least sense I had bought this house about a year and a half.
I went so far as to showed him some print screens of some of the issues I have been having, and I know he noticed all the yellow recites in my computer room. : P Unfortunately, I deleted all my old Print Screen saves when the guy last Monday (ninth) showed up and said he would fix the line, or at least track it down. I only had one from the previous night to show him or something.
In any case, while discussing this Mark, said the guy that came out the other Monday never filled out a work order or something like that. I basically tried to explain that is the kind of thing I have been dealing with for little over a year. Tech after Tech after Tech; as I looked at all the yellow recites on top of my computer desk.
Mark also, basically said, I should have pretty fast cable considering I only have two nodes and then basically it runs back to Comcast, or something like that. However, that Temporary Line is probably causing the issues. No definite date on a fix, but maybe 24-hours or a few days, but the matter had been expedited or something like that. *Cross fingers*
That’s the real issue with this cable, its sporadic, and comes and goes. I’m pretty sure they are going to try to replace that line, but you know what….. I have heard that before actually. I have actually heard that for over a year now. Even the expedited part. : P
Mark tried to thank me for pointing out this issue, and made some comment about how its actually helping them….but………. I can kind of tell he had been getting yelled at or something by someone. It was not obvious, but I could tell.
I felt kind of bad about that, but… That happens when you work for someone, and the people who work for you (below you) don’t do what they are supposed too.
I kind of tried to briefly explain to Mark about the issue again and that usually by the time a Supervisor gets out the issue has cleared up for a time….. Odd how that works by the way. But basically I got the old…well it looks like its working ok now and you should have seen some improvements over the last few days… thingy..
We started talking about that Temporary Line being connected again and I walked Mark to the door and we said our goodbyes and I apologized again for being such a pain in the about this whole matter.
Part/5-
I called the wife and told here about everything. The first thing she asked is; is it fixed? She is still not happy especially when I tired to explain what the issue was and probably was and that at least maybe they found it.
I have no idea of what kind of onward action maybe on my part in the end if things don’t get better. Its like trying to argue with the old Bell Telephone Company when that was the only phone company in the US and no other phone companies existed.
I hope to one day, be a satisfied Comcast Customer, but to date I have yet to feel that way, at least with the Internet in any case and that’s only because I really don’t watch TV.
I am also, hoping when, and if, some LINE is replaced somewhere that I see some drastic improvement along with apparently a lot of other people in my community and a lot less issues also. I still don’t believe that I should be just setting for; Ok well at least its ON now, or the light has finally stopped flashing.
All a SNAFU?
That’s highly questionable at this point, and I have to be honest with you. This is going on a year and a half of dealing with this. This SNAFU, could be the case, but it seems more like policy, or a standing Comcast Company Directive actually if you want my honest opinion. I don’t know what the Maintenance Budget is for my area, but you might want to consider doubling it, or tripling it.
I really don’t care actually when this is fixed, as long as the issue is fixed. I cannot make a final judgment until it is finally fixed and go on and try to take further action onward from that point.
Thus far I have only been given an explanation. I don’t know if anyone at Comcast realize exactly how many times I have had an explanation given too me though (either on the phone with a service tech or from an actual person “tech” at my house). The list is extensive of the actual explanations I have had over the past year and a half, but my favorite one is; squirrels.
Part/6-
We are still waiting on phone calls from people who said they would call us back today and check what’s going on. Both of us, (me and the wife) are slowly losing momentum again as this whole issue gets dragged out for weeks and weeks at a time.
She is tired and I’m tired too, and Comcast is warring us down again it looks like. My wife was like; “do I have to call them, I really didn’t have a good day anyway and I’m tired. They were supposed to call us anyway, lets wait.”
I tried to make a phone call (half heartedly, I myself as I’m tired too) as Carla (at my local Comcast office) wanted to know how the service call went, but after repeated attempts and being shuffled off to Billing, and then being put on hold : P ……and its actually getting close to dinner time. Maybe after dinner if I don’t just fall asleep first.
So, in the end its still hang on for a few more days, and or, wait to have the problem fixed. Your guess is as good as mine, people. More Smoke and Mirrors or an actual Fix. Your guess is as good as mine.
As for me, I’m going to bed, I’m worn out. Maybe a new line to replace that temporary one, maybe just saying I might get a new line to replace that temporary one.
The Saga continues. Maybe it will end someday. -
I'm having strange random connection failures. Are there ineffieciency in my config?
I've been having strange, random connection failures and I'm trying to eliminate possible causes.
What happens is while I'm browsing on the net over wifi, a link will at random not connect to the site, but instead fault to the ISP error page. It happens with highly reliable sites like google, or ebay, or whatever. If I direct connect to the cable modem, the problem site is immediately available.
I'm sitting <6 feet from a 871W router (with antenna). There's one router in my building and others are at my neighbors.
Below is the conf file. Just to imagine how rediculious this problem is, here's a screen shot from a web page. This shows a web page I visited, and after clicking on a link (an embedded youtube video), the error showed up within the page itself.
Why would only some URLs fail to connect? Is there inefficiencies in my config?
Building configuration...
Current configuration : 4750 bytes
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname TooterTurtle
boot-start-marker
boot-end-marker
logging buffered 51200 warnings
no logging console
aaa new-model
aaa authentication login default local
aaa authorization exec default local
aaa session-id common
clock timezone NewYork -5
clock summer-time NewYork date Apr 6 2003 2:00 Oct 26 2003 2:00
dot11 syslog
dot11 ssid TooterTurtle
vlan 2
authentication open
authentication key-management wpa
guest-mode
wpa-psk ascii 0 [my wifi password]
no ip source-route
no ip gratuitous-arps
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.10.1 192.168.10.10
ip dhcp excluded-address 10.0.0.1 10.0.0.10
ip dhcp pool vlan1
import all
network 192.168.10.0 255.255.255.0
dns-server 192.168.10.1
default-router 192.168.10.1
domain-name Ethernet
ip dhcp pool vlan2
import all
network 10.0.0.0 255.255.255.0
domain-name WiFi
dns-server 10.0.0.1
default-router 10.0.0.1
ip dhcp pool MrWizard
host 192.168.10.100 255.255.255.0
hardware-address 0011.0917.66fa
client-name MrWizard
ip dhcp pool MasterShake
host 192.168.10.101 255.255.255.0
hardware-address 0022.681c.fbcc
client-name mastershake
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
no ip bootp server
ip domain name mydomain.com
ip ddns update method ccp_ddns1
HTTP
add [zone edit account and url]
remove [zone edit account and url]
username admin privilege 15 secret 5 [encrypted secret]
archive
log config
hidekeys
no ip ftp passive
ip ssh version 1
bridge irb
interface FastEthernet0
description AdminInterface
interface FastEthernet1
description MrWizard
interface FastEthernet2
description Belkin
interface FastEthernet3
interface FastEthernet4
description ComcastCableModem
ip address dhcp
ip verify unicast source reachable-via rx allow-default 100
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat outside
ip virtual-reassembly
speed auto
full-duplex
interface Dot11Radio0
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
encryption vlan 1 mode ciphers tkip
encryption vlan 2 mode ciphers tkip
ssid TooterTurtle
speed basic-1.0 basic-2.0 basic-5.5 basic-6.0 basic-9.0 basic-11.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
station-role root
interface Dot11Radio0.1
description TootersWiFi
encapsulation dot1Q 2
no cdp enable
bridge-group 2
bridge-group 2 subscriber-loop-control
bridge-group 2 spanning-disabled
bridge-group 2 block-unknown-source
no bridge-group 2 source-learning
no bridge-group 2 unicast-flooding
interface Vlan1
description EthernetOnly
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
ip virtual-reassembly
bridge-group 1
interface Vlan2
description WiFiOnly
no ip address
bridge-group 2
interface BVI1
description EthernetOnly
ip address 192.168.10.1 255.255.255.0
ip nat inside
ip virtual-reassembly
interface BVI2
description WiFiOnly
ip address 10.0.0.1 255.255.255.0
ip nat inside
ip virtual-reassembly
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 FastEthernet4
ip http server
ip http authentication local
no ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip dns server
ip nat inside source list 101 interface FastEthernet4 overload
ip nat inside source list 102 interface FastEthernet4 overload
ip nat inside source static tcp 192.168.10.100 80 interface FastEthernet4 80
ip access-list extended vlan1
deny ip 10.0.0.0 0.0.0.255 any
permit ip any any
access-list 100 permit udp any any eq bootpc
access-list 101 permit ip 192.168.10.0 0.0.0.255 any
access-list 102 permit ip 10.0.0.0 0.0.0.255 any
no cdp run
control-plane
bridge 1 protocol ieee
bridge 1 route ip
bridge 2 protocol ieee
bridge 2 route ip
line con 0
no modem enable
line aux 0
line vty 0 4
transport input telnet ssh
transport output telnet ssh
scheduler max-task-time 5000
endI removed the ip router 0 0 to no great effect, which I consider to be a win.
I'm guessing that since overload is what--I understand--translates the one outside to the many inside IPs, that the suggestion to have only one overload configured means I should combine the two ip ranges into one.
I deleted 10.0.0.0 network. Changed the bridge references to 1 and vlan references to 1. Now wifi and ethernet should all be using the same internal network? That's the idea, right? Any more fat?
[EDITED]
dot11 syslog
dot11 ssid TooterTurtle
vlan 1
authentication open
authentication key-management wpa
guest-mode
wpa-psk ascii 0 [my passphrase]
no ip source-route
no ip gratuitous-arps
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.10.1 192.168.10.10
ip dhcp pool vlan1
import all
network 192.168.10.0 255.255.255.0
dns-server 192.168.10.1
default-router 192.168.10.1
domain-name Ethernet
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
no ip bootp server
ip domain name [my url]
ip ddns update method ccp_ddns1
HTTP
add http:...[zoneedit]
remove http:[zoneedit]
no ip ftp passive
ip ssh version 1
bridge irb
interface FastEthernet0
description AdminInterface
interface FastEthernet1
description MrWizard
interface FastEthernet2
description Belkin
interface FastEthernet3
interface FastEthernet4
description ComcastCableModem
ip address dhcp
ip verify unicast source reachable-via rx allow-default 100
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat outside
ip virtual-reassembly
speed auto
full-duplex
interface Dot11Radio0
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
encryption vlan 1 mode ciphers tkip
ssid TooterTurtle
speed basic-1.0 basic-2.0 basic-5.5 basic-6.0 basic-9.0 basic-11.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
station-role root
interface Dot11Radio0.1
description TootersWiFi
encapsulation dot1Q 2
no cdp enable
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Vlan1
description EthernetOnly
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
ip virtual-reassembly
bridge-group 1
interface BVI1
description EthernetOnly
ip address 192.168.10.1 255.255.255.0
ip nat inside
ip virtual-reassembly
ip forward-protocol nd
ip http server
ip http authentication local
no ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip dns server
ip nat inside source list 101 interface FastEthernet4 overload
ip nat inside source static tcp 192.168.10.100 80 interface FastEthernet4 80
ip access-list extended vlan1
permit ip any any
access-list 100 permit udp any any eq bootpc
access-list 101 permit ip 192.168.10.0 0.0.0.255 any
no cdp run
control-plane
bridge 1 protocol ieee
bridge 1 route ip -
I need help diagnosing an issue where TCP communications breaks down between my host (Windows) and a PXI (LabVIEW RT 2010).
The bottom-line questions are these:
1...Are there circumstances in which TCP WRITE, given a string of say, 10 characters, will write more than zero and fewer than 10 characters to the connection? If so, what are those circumstances?
2...Is it risky to use a timeout value of 1 mSec? Further thought seems to say that I won't get a 1000 uSec timeout if we're using a 1-mSec timebase, but I don't know if that's true in the PXI.
Background:
On the PXI, I'm running a 100-Hz PID loop, controlling an engine. I measure the speed and torque, and control the speed and throttle. Along the way, I'm measuring 200 channels of misc stuff (analog, CAN, TCP instruments) at 10 Hz and sending gobs of info to the host (200 chans * 8 = 1600 bytes every 0.1 sec)
The host sends commands, the PXI responds.
The message protocol is a fixed-header, variable payload type: a message is a fixed 3-byte header, consisting of a U8 OpCode, and a U16 PAYLOAD SIZE field. I flatten some structure to a string, measure its size, and prepend the header and send it as one TCP WRITE. I receive in two TCP READs: one for the header, then I unflatten the header, read the PAYLOAD SIZE and then another read for that many more bytes.
The payload can thus be zero bytes: a TCP READ with a byte count of zero is legal and will succeed without error.
A test starts with establishing a connection, some configuration stuff, and then sampling starts. The 10-Hz data stream is shown on the host screen at 2-Hz as numeric indicators, or maybe selected channels in a chart.
At some point the user starts RECORDING, and the 10-Hz data goes into a queue for later writing to a file. This is while the engine is being driven thru a prescribed cycle of speed/torque target points.
The recording lasts for 20 or in some cases 40 minutes (24000 samples) and then recording stops, but sampling doesn't. Data is still coming in and charted. The user can then do some special operations, related to calibration checks and leak checks, and those results are remembered. Finally, they hit the DONE button, and the whole mess gets written to a file.
All of this has worked fine for several years, but as the system is growing (more devices, more channels, more code), a problem has cropped up: the two ends are occasionally getting out of synch.
The test itself, and all the configuration stuff before, is working perfectly. The measurement immediately after the test is good. At some point after that, it goes south. The log shows the PXI sending results for operations that were not requested. The data in those results is garbage; 1.92648920e-299 and such numbers, resulting from interpreting random stuff as a DBL.
After I write the file, the connection is broken, the next test re-establishes it, and all is well again.
In chasing all this, I've triple-checked that all my SENDs are MEASURING the size of the payload before sending it. Two possibilities have come up:
1... There is a message with a payload over 64k. If my sender were presented with a string of length 65537, it would convert that to a U16 of value 1, and the receiver would expect 1 byte. The receiver would then expect another header, but this data comes instead, and we're off the rails.
I don't believe that's happening. Most of the messages are fewer than 20 bytes payload, the data block is 1600 or so, I see no evidence for such a thing to happen.
2... The PXI is failing, under certain circumstances, to send the whole message given to TCP WRITE. If it sent out a header promising 20 more bytes, but only delivered 10, then the receiver would see the header and expect 20 more. 10 would come immediately, but whatever the NEXT message was, it's header would be construed as part of the payload of the first message, and we're off the rails.
Unfortunately, I am not checking the error return from TCP write, since it never failed in my testing here (I know, twenty lashes for me).
It also occurs to me that I am giving it a 1-mSec timeout value, since I'm in a 100-Hz loop. Perhaps I should have separated the TCP stuff into a separate thread. In any case, maybe I don't get a full 1000 uSec, due to clock resolution issues.
That means that TCP WRITE cannot get the data written before the TIMEOUT expires, but it has written part of it.
I suspect, but the logs don't prove, that the point of failure is when they hit the DONE button. The general CPU usage on the PXI is 2-5% but at that point there are 12-15 DAQ domain managers to be shutting down, so the instantaneous CPU load is high. If that happens to coincide with a message going out, well, maybe the problem crops up. It doesn't happen every time.
So I repeat the two questions:
1...Are there circumstances in which TCP WRITE, given a string of say, 10 characters, will write more than zero and fewer than 10 characters to the connection? If so, what are those circumstances?
2...Is it risky to use a timeout value of 1 mSec? Further thought seems to say that I won't get a 1000 uSec timeout if we're using a 1-mSec timebase, but I don't know if that's true in the PXI.
Thanks,
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks
Solved!
Go to Solution.There are a couple of issues at play here, and both are working together to cause your issue(s).
1) LV RT will suspend the TCP thread when your CPU utilization goes up to 100%. When this happens, your connection to the outside world simply goes away and your communications can get pretty screwed up. (More here)
Unless you create some form of very robust resend and timeout strategy your only other solution would be to find a way to keep your CPU from maxing out. This may be through the use of some scheduler to limit how many processes are running at a particular time or other code optimization. Any way you look at it, 100% CPU = Loss of TCP comms.
2) The standard method of TCP communication shown in all examples I have seen to date uses a similar method to transfer data where a header is sent with the data payload size to follow.
<packet 1 payload size (2 bytes)><packet 1 payload..........><packet 2 payload size (2 bytes)><packet 2 payload.......................>
On the Rx side, the header is read, the payload size extracted then a TCP read is set with the desired size. Under normal circumstances this works very well and is a particularly efficent method of transferring data. When you suspend the TCP thread during a Rx operation, this header can get corrupted and pass the TCP Read a bad payload size due to a timeout on the previous read. As an example the header read expects 20 bytes but due to the TCP thread suspension only gets 10 before the timeout. The TCP Read returns only those 10 bytes, leaving the other 10 bytes in the Rx buffer for the next read operation. The subsequent TCP Read now gets the first 2 bytes from the remaining data payload (10 bytes) still in the buffer. This gives you a further bad payload read size and the process continues OR if you happen to get a huge number back, when you try to allocate a gigantic TCP receive buffer, you get an out of memory error.
The issue now is that your communications are out of sync. The Rx end is not interpeting the correct bytes as the header thus this timeout or bad data payload behavior can continue for quite a long time. I have found that occasionally (although very rare) the system will fall back into sync however it really is a crap shoot at this point.
I more robust way of dealing with the communication issue is to change your TCP read to terminate on a CRLF as opposed to the number of bytes or timeout (The TCP Read has an enum selctor for switching the mode. In this instance, whenever a CRLF is seen, the TCP Read will immediately terminate and return data. If the payload is corrupted, then it will fail to be parsed correctly or would encounter a checksum failure and be discarded or a resend request issued. In either case, the communications link will automatically fall back into sync between the Tx and Rx side. The one other thing that you must do is to encode your data to ensure that no CRLF characters exist in the payload. Base64 encode/decode works well. You do give up some bandwith due to the B64 strings being longer, however the fact that the comm link is now self syncing is normally a worthwhile sacrifice.
When running on any other platform other than RT, the <header><payload> method of transmitting data works fine as TCP guarantees transmission of the data, however on RT platforms due to the suspension of the TCP thread on high CPU excursions this method fails miserably. -
Mac Mini - Screensaver starting on its own and clock is fast ...
Hi there experts ....
I've got a 4 month old Mac mini
Model Identifier: Macmini3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.53 GHz
I've noticed for the past couple of months the clock is 4 minutes fast ....
And the screeensaver is coming on by itself out of nowhere ...
I/ve run disk repair ... Maintenance ... put screensaver to never and even disabled front row screensaver
I've reset pram and nvram ... ANy clues ....?So even if you put the screensaver to never it still starts on its own?
Also you clock runs faster by 4mins?
I smell an OS issue. Partition your drive and install a fresh OS onto it. If it works(no problem there) then restore the partition into 1 drive. Zero out the drive and put a fresh OS in it
**back it up first
If the fresh OS on the new partition still fails. it could be a hardware failure. -
Sleekbook 6 Recovery fails with P2PP burnboot check failure
I have an HP Sleekbook 6-1019nr laptop. I just purchased System Restore media for this notebook. The system originally came with Win 7 Home. I received the restore media, connected the device to an External USB DVD drive to the unit and started the restore Process. No errors were found until the very end and then i got a message indicating the restore failed and would like to review the log.
I am posting the log for reference. i have seen other indicate in the forms to change the BIOS clock to 2012 to resolve this issue and reimage, which i have tried but the error persists.
The only error I can see is the wallpaper failed to load...I don't see any other failures in the log but maybe I am not seeing another error.
Looking for some assistance. I can provide additional details but I am stuck as to my next step. If the media is the issue, i want to get it reported to HP.
P2PP BurnBoot Check Failed
Possible Causes:
1. Yellow-Bang occured at Device Manager
2. Some silent-install failure of applications
3. Found failed at PININST_BBV
4. Found failed at PININST_BBV2
5. Found Memory Dump file
Suggestion:
1. Checking REGDEV_BB.LOG for drivers
2. Checking BBApps.log for applications
3. Checking MEMDUMP_BBV.log for memory dump file
Note(for ODM):
If you know which component failed in preinstall process
after checking above files, please OTS it to the component owner.
Otherwise, suggest to contact TWN PDC NB-PreinPM or create PIN-Log and OTS it with OTS Category Image
[RegistryDevicesCheck]
Result=PASSED
[PININST_BBV]
PININST (Mini-FBI) starts at: 20:38:48 Sunday, December 14, 2014
[RunOnceThese_CMD#1]
LAUNCHED=> "CMD.exe /c C:\System.sav\Util\WMIWirelessOn.exe"
START=> 20:38:50 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:39:05 Sunday, December 14, 2014
RESULT=> Command finished in 15 seconds.
>==============================================================================
[RunOnceThese_CMD#2]
LAUNCHED=> "c:\SwSetup\ocamrk\ocamrk.cmd"
START=> 20:39:05 Sunday, December 14, 2014
END=> 20:39:07 Sunday, December 14, 2014
RESULT=> Command finished in 2 seconds.
>==============================================================================
[RunOnceThese_CMD#3]
LAUNCHED=> "CMD.exe /c MOVE c:\System.sav\FactoryUpdate\boot.wim c:\System.sav\2ndCap"
START=> 20:39:07 Sunday, December 14, 2014
END=> 20:39:07 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunOnceThese_CMD#4]
LAUNCHED=> "CMD.exe /c C:\System.sav\Util\Pre-BBV1.CMD"
START=> 20:39:07 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:39:25 Sunday, December 14, 2014
RESULT=> Command finished in 18 seconds.
>==============================================================================
[RunThese_CMD#1]
LAUNCHED=> "CMD.exe /C C:\System.sav\Util\TDCTWKs\ChangeVol.cmd"
START=> 20:39:27 Sunday, December 14, 2014
END=> 20:39:28 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#2]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\VGA_A_BBV.CMD"
START=> 20:39:28 Sunday, December 14, 2014
END=> 20:41:21 Sunday, December 14, 2014
RESULT=> Command finished in 113 seconds.
>==============================================================================
[RunThese_CMD#3]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\LAN_BBV.CMD"
START=> 20:41:21 Sunday, December 14, 2014
END=> 20:42:29 Sunday, December 14, 2014
RESULT=> Command finished in 68 seconds.
>==============================================================================
[RunThese_CMD#4]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\Audio_BBV.CMD"
START=> 20:42:29 Sunday, December 14, 2014
END=> 20:45:13 Sunday, December 14, 2014
RESULT=> Command finished in 164 seconds.
>==============================================================================
[RunThese_CMD#5]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\Cardreader_BBV.CMD"
START=> 20:45:13 Sunday, December 14, 2014
END=> 20:45:24 Sunday, December 14, 2014
RESULT=> Command finished in 11 seconds.
>==============================================================================
[RunThese_CMD#6]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\TouchPad_BBV.CMD"
START=> 20:45:24 Sunday, December 14, 2014
END=> 20:45:56 Sunday, December 14, 2014
RESULT=> Command finished in 32 seconds.
>==============================================================================
[RunThese_CMD#7]
LAUNCHED=> "CMD.exe /c C:\System.sav\Util\WMIDetectTest2.bat"
START=> 20:45:56 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:45:57 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#8]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\TDCWIDI_BBV.CMD"
START=> 20:45:57 Sunday, December 14, 2014
END=> 20:45:58 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#9]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\WLAN_B_BBV.CMD"
START=> 20:45:58 Sunday, December 14, 2014
END=> 20:47:08 Sunday, December 14, 2014
RESULT=> Command finished in 70 seconds.
>==============================================================================
[RunThese_CMD#10]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\WLAN_A_BBV.CMD"
START=> 20:47:08 Sunday, December 14, 2014
END=> 20:47:08 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#11]
LAUNCHED=> "cscript.exe c:\SwSetup\powerset\sys_mem_check.vbs"
START=> 20:47:08 Sunday, December 14, 2014
END=> 20:47:08 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#12]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\BCBT4_BBV.CMD"
START=> 20:47:08 Sunday, December 14, 2014
END=> 20:48:25 Sunday, December 14, 2014
RESULT=> Command finished in 77 seconds.
>==============================================================================
[RunThese_CMD#13]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPDGF_BBV.CMD"
START=> 20:48:25 Sunday, December 14, 2014
END=> 20:48:37 Sunday, December 14, 2014
RESULT=> Command finished in 12 seconds.
>==============================================================================
[RunThese_CMD#14]
LAUNCHED=> "c:\System.sav\Util\InstallEFIBits.cmd"
START=> 20:48:37 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:48:42 Sunday, December 14, 2014
RESULT=> Command finished in 5 seconds.
>==============================================================================
[RunThese_CMD#15]
LAUNCHED=> "cmd.exe /c C:\System.sav\Util\TDC\OOBE\CompName.cmd"
START=> 20:48:42 Sunday, December 14, 2014
END=> 20:48:43 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#16]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\ARBH40_BBV.CMD"
START=> 20:48:43 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:48:43 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#17]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPQL_BBV.CMD"
START=> 20:48:43 Sunday, December 14, 2014
END=> 20:48:43 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#18]
LAUNCHED=> "C:\System.sav\Util\VPC_QFE.cmd"
START=> 20:48:43 Sunday, December 14, 2014
END=> 20:48:43 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#19]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\IE9_BBV.CMD"
START=> 20:48:43 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:48:44 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#20]
LAUNCHED=> "CMD.exe /c C:\System.sav\bbv\QFEList32.cmd"
START=> 20:48:44 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:48:49 Sunday, December 14, 2014
RESULT=> Command finished in 5 seconds.
>==============================================================================
[RunThese_CMD#21]
LAUNCHED=> "C:\SWSetup\ESUW7\ESURun.bat"
START=> 20:48:49 Sunday, December 14, 2014
END=> 20:49:01 Sunday, December 14, 2014
RESULT=> Command finished in 12 seconds.
>==============================================================================
[RunThese_CMD#22]
LAUNCHED=> "C:\System.sav\Util\_RTEND.CMD"
START=> 20:49:01 Sunday, December 14, 2014
END=> 20:49:01 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
PININST (Mini-FBI) exits at: 20:49:04 Sunday, December 14, 2014
[Mini-FBI]
Result=PASSED
[PININST_BBV2]
PININST (Mini-FBI) starts at: 20:50:11 Sunday, December 14, 2014
[RunOnceThese_CMD#1]
LAUNCHED=> "C:\SYSTEM.SAV\UTIL\CLEANFBI.CMD"
START=> 20:50:13 Sunday, December 14, 2014
END=> 20:50:13 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunOnceThese_CMD#2]
LAUNCHED=> "CMD.exe /c C:\System.sav\2ndCap\2ndCPrep.cmd"
START=> 20:50:13 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:50:17 Sunday, December 14, 2014
RESULT=> Command finished in 4 seconds.
>==============================================================================
[RunOnceThese_CMD#3]
LAUNCHED=> "CMD.exe /c C:\System.sav\Util\Pre-BBV2.CMD"
START=> 20:50:17 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:50:39 Sunday, December 14, 2014
RESULT=> Command finished in 22 seconds.
>==============================================================================
[RunThese_CMD#1]
LAUNCHED=> "C:\System.sav\Util\RemoveEFIBits.cmd"
START=> 20:50:41 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:50:41 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#2]
LAUNCHED=> "C:\System.sav\OSEnhReg\SETUP.cmd"
START=> 20:50:41 Sunday, December 14, 2014
END=> 20:50:41 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#3]
LAUNCHED=> "cscript.exe c:\System.sav\Util\webcam.vbs"
START=> 20:50:41 Sunday, December 14, 2014
END=> 20:50:42 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#4]
LAUNCHED=> "C:\SWSetup\ESUW7\ESUDelete.bat"
START=> 20:50:42 Sunday, December 14, 2014
END=> 20:50:42 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#5]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPSecA_BBV.CMD"
START=> 20:50:42 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:50:42 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#6]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\VUDU_BBV.CMD"
START=> 20:50:42 Sunday, December 14, 2014
END=> 20:50:42 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#7]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\URLOffer_bbv.CMD"
START=> 20:50:42 Sunday, December 14, 2014
END=> 20:51:10 Sunday, December 14, 2014
RESULT=> Command finished in 28 seconds.
>==============================================================================
[RunThese_CMD#8]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\BTBUS_BBV.CMD"
START=> 20:51:10 Sunday, December 14, 2014
END=> 20:51:12 Sunday, December 14, 2014
RESULT=> Command finished in 2 seconds.
>==============================================================================
[RunThese_CMD#9]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\IEHome_BBV.CMD"
START=> 20:51:12 Sunday, December 14, 2014
END=> 20:51:13 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#10]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPPlus_BBV.CMD"
START=> 20:51:13 Sunday, December 14, 2014
END=> 20:51:14 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#11]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPOSD_BBV.CMD"
START=> 20:51:14 Sunday, December 14, 2014
END=> 20:51:14 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#12]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPMKT_BBV.CMD"
START=> 20:51:14 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:51:15 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#13]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPAA_BBV.CMD"
START=> 20:51:15 Sunday, December 14, 2014
END=> 20:51:15 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#14]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\Ebay_bbv.CMD"
START=> 20:51:15 Sunday, December 14, 2014
END=> 20:51:17 Sunday, December 14, 2014
RESULT=> Command finished in 2 seconds.
>==============================================================================
[RunThese_CMD#15]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\Ceement_BBV.CMD"
START=> 20:51:17 Sunday, December 14, 2014
END=> 20:51:17 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#16]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\YouCam_BBV.CMD"
START=> 20:51:17 Sunday, December 14, 2014
END=> 20:54:13 Sunday, December 14, 2014
RESULT=> Command finished in 176 seconds.
>==============================================================================
[RunThese_CMD#17]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\WinLive_BBV.CMD"
START=> 20:54:13 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:54:14 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#18]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\Snfish_BBV.CMD"
START=> 20:54:14 Sunday, December 14, 2014
END=> 20:54:16 Sunday, December 14, 2014
RESULT=> Command finished in 2 seconds.
>==============================================================================
[RunThese_CMD#19]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\Norton180_BBV.CMD"
START=> 20:54:16 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:54:16 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#20]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\NorIS_DV_BBV.CMD"
START=> 20:54:16 Sunday, December 14, 2014
END=> 20:55:14 Sunday, December 14, 2014
RESULT=> Command finished in 58 seconds.
>==============================================================================
[RunThese_CMD#21]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\LoJack_BBV.CMD"
START=> 20:55:14 Sunday, December 14, 2014
END=> 20:55:14 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#22]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\RM4Win.CMD"
START=> 20:55:14 Sunday, December 14, 2014
END=> 20:55:14 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#23]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPSWFK_bbv.cmd"
START=> 20:55:14 Sunday, December 14, 2014
END=> 20:55:14 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#24]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPCOSE_bbv.cmd"
START=> 20:55:14 Sunday, December 14, 2014
END=> 20:55:15 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#25]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPSPIP12_bbv.cmd"
START=> 20:55:15 Sunday, December 14, 2014
END=> 20:55:40 Sunday, December 14, 2014
RESULT=> Command finished in 25 seconds.
>==============================================================================
[RunThese_CMD#26]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\hppm_bbv.CMD"
START=> 20:55:40 Sunday, December 14, 2014
END=> 20:56:04 Sunday, December 14, 2014
RESULT=> Command finished in 24 seconds.
>==============================================================================
[RunThese_CMD#27]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPMroom_BBV.CMD"
START=> 20:56:04 Sunday, December 14, 2014
END=> 20:56:05 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#28]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPLB_BBV.CMD"
START=> 20:56:05 Sunday, December 14, 2014
END=> 20:56:12 Sunday, December 14, 2014
RESULT=> Command finished in 7 seconds.
>==============================================================================
[RunThese_CMD#29]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPDOC_BBV.CMD"
START=> 20:56:12 Sunday, December 14, 2014
END=> 20:56:18 Sunday, December 14, 2014
RESULT=> Command finished in 6 seconds.
>==============================================================================
[RunThese_CMD#30]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPCM41_bbv.CMD"
START=> 20:56:18 Sunday, December 14, 2014
END=> 20:56:19 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#31]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\DVD2D3D_BBV.CMD"
START=> 20:56:19 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:56:27 Sunday, December 14, 2014
RESULT=> Command finished in 8 seconds.
>==============================================================================
[RunThese_CMD#32]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\Costco_BBV.CMD"
START=> 20:56:27 Sunday, December 14, 2014
END=> 20:56:28 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#33]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\BIOS_BBV.CMD"
START=> 20:56:28 Sunday, December 14, 2014
END=> 20:56:48 Sunday, December 14, 2014
RESULT=> Command finished in 20 seconds.
>==============================================================================
[RunThese_CMD#34]
LAUNCHED=> "C:\System.sav\Util\WallpaperInstallBOM.cmd"
START=> 20:56:48 Sunday, December 14, 2014
END=> 20:56:49 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#35]
LAUNCHED=> "C:\SWSetup\Wallpaper\Disk1\Wallpaper.exe"
START=> 20:56:49 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:56:49 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#36]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\BBarIE9_BBV.CMD"
START=> 20:56:49 Sunday, December 14, 2014
END=> 20:57:05 Sunday, December 14, 2014
RESULT=> Command finished in 16 seconds.
>==============================================================================
[RunThese_CMD#37]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\AFlash_BBV.CMD"
START=> 20:57:05 Sunday, December 14, 2014
END=> 20:57:05 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#38]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\SymHPE_BBV.CMD"
START=> 20:57:05 Sunday, December 14, 2014
END=> 20:57:06 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#39]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HOSTEND.cmd"
START=> 20:57:06 Sunday, December 14, 2014
END=> 20:57:06 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#40]
LAUNCHED=> "cmd.exe /c c:\System.sav\Util\TDC\OOBE\BKG.cmd"
START=> 20:57:06 Sunday, December 14, 2014
Pre-Process=> disabled WOW64 File Redirection....
Post-Process=> enabled WOW64 File Redirection....
END=> 20:57:07 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#41]
LAUNCHED=> "C:\System.sav\Util\_RTEND.CMD"
START=> 20:57:07 Sunday, December 14, 2014
END=> 20:57:07 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#42]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPSF_bbv.CMD"
START=> 20:57:07 Sunday, December 14, 2014
END=> 20:57:07 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#43]
LAUNCHED=> "C:\System.sav\Util\TDC\MCPP\HPCM41_REG.CMD"
START=> 20:57:07 Sunday, December 14, 2014
END=> 20:57:07 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#44]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\DTICON_BBV.CMD"
START=> 20:57:07 Sunday, December 14, 2014
END=> 20:57:10 Sunday, December 14, 2014
RESULT=> Command finished in 3 seconds.
>==============================================================================
[RunThese_CMD#45]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\STARTMENU_BBV.CMD"
START=> 20:57:10 Sunday, December 14, 2014
END=> 20:57:10 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
[RunThese_CMD#46]
LAUNCHED=> "C:\system.sav\Util\TDC\MCPP\HOTSTART_BBV.CMD"
START=> 20:57:10 Sunday, December 14, 2014
END=> 20:57:10 Sunday, December 14, 2014
RESULT=> Command finished in less than 1 seconds.
>==============================================================================
PININST (Mini-FBI) exits at: 20:57:13 Sunday, December 14, 2014
[Mini-FBI]
Result=PASSED
[C:\System.sav\Logs\BB\AFLASH.log]
Result=PASSED
[C:\System.sav\Logs\BB\ARBH40.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\Audio.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\BBarIE9.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\BCBT4.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\BIOS.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\BKG_XML.log]
Result=PASSED
[C:\System.sav\Logs\BB\BTBHOST.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\BTBUS.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\Cardreader.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\Ceement.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\CompName.log]
Result=PASSED
[C:\System.sav\Logs\BB\Costco.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\DTICON_BBV.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\DVD2D3D.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\Ebay.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\FU_CTO.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\FU_Tweaks.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HOTSTART_BBV.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPAA.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPCM41.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPCM41_REG.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPCOSE.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPDGF.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPDOC.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPLB.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPMKT.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPMroom.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPOSD.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPPlus.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\hppm.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPQL.log]
Result=PASSED
[C:\System.sav\Logs\BB\HPSecA.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPSF.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPSPIP12.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\HPSWFK.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\IE9.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\IEHome.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\LAN.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\LoJack.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\NorIS_DV.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\Norton180.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\OSEnhReg.log]
Result=PASSED
[C:\System.sav\Logs\BB\PureOSSR.log]
Result=PASSED
[C:\System.sav\Logs\BB\RM4Win.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\Snfish.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\STARTMENU_BBV.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\SymHPE.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\TDCWIDI.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\TouchPad.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\URLOffer.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\VGA_A.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\VUDU.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\WallpaperOk.log]
Log file...
Component: Wallpaper for Windows 7 - TDC
Timing: Pininst_BBV2Post
Error: Wallpaper installation failed, did not find ResultCode=0
RESULT=FAILED
Standard Error information...
Standard Out information...
Result=FAILED
[C:\System.sav\Logs\BB\WinLive.log]
Result=PASSED
[C:\System.sav\Logs\BB\WLAN_A.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\WLAN_B.LOG]
Result=PASSED
[C:\System.sav\Logs\BB\WMIWirelessOn.log]
Result=PASSED
[C:\System.sav\Logs\BB\Youcam.log]
Result=PASSED
[LogFiles]
NumOfLogs=59.
[DumpFile]
Result=PASSED
[WinSAT]
Result=PASSED
[21:03:31.50] Sysprep_succeeded.tag does not exist ...
[21:03:31.50] ------------------------------------------------------------------------------------------
[21:03:31.50] BBVLast.cmd : [20x] CTOError.flg is detected at the end of BBV process...
[21:03:31.50] Suggest to create PIN-log and send to TWN PDC NB-PreinPM for further analysis ...
[21:03:31.50] ------------------------------------------------------------------------------------------Good Morning @CCStefanini ,
Welcome to the HP Forums!
It is a terrific place to find answers and ideas!
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I grasp that you tried to do the recovery from the recovery disks HP sent but received this error " P2PP BurnBoot Check Failed" .
You have tried changing the date in the bios but there was no change.
Here is a link to Troubleshooting HP System Recovery Problems (Windows 7) that will guide you through some steps.
Here is a link to a search I did in the forum for your error that were resolved. You may wish to peruse these as they may have a suggestion that may help. P2PP BurnBoot Check Failed forum search
As HP did just send you the recovery kit, you may also contact them for assistance.
Please call our technical support at 800 474 6836. If you live outside the US/Canada Region, please click the link below to get a support number for your region.
World Wide Phone Support
Good Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping! -
My 13" black macbook keeps having hard drive failures -- I'm on my third hard drive
The first one lasted 2 years. It failed within the special warranty period that Apple offered because so many computers like mine were also having hard drive failures. I didn't know about the special warranty they were offering, even after contacting Apple and telling them about my problem and describing the exact symptoms of the problem they were fixing for free. Thank you for that. So I went to a local store and paid ~$130 to have it fixed. This time I was paranoid about not moving my computer, and if I did have to move it, make sure it was off. Then without warning, it happens again less than 2 years later. I would expect a computer hard drive, especially one that is taken care of as well as mine, to last more ~20 months (less than 2 years) TWICE. It seems that this is a problem not with the hard drive but with the computer. I'm pretty upset that hard drives are now basically disposable -- I'm afraid to use it now unless absolutely necessary, otherwise I'll feel like I'm making its clock tick closer and closer to the next time it fries the hard drive. For as much as I paid for this computer, I expect a bit more than that. Unless there is some magical fix to this, I can safely say my next computer will be a super cheap net book.
Does anyone have any more info on this, any ways to avoid frying more hard drives, or has any one had any luck resolving this issue with Apple? I greatly appreciate any help. Thank you!Mechanical hard drives have moveable parts and they are going to fail eventually. Every drive has an MTBF (Mean Time Between Failure) rating in the thousands of hours, but that is an average (half will fail sooner, half will fail later) not an absolute longevity guarantee.
I've used an original (Apple-OEM Fujitsu 120Gb 5400rpm), a Hitachi 320Gb 7200rpm, and currently a Seagate 500Gb 7200rpm drive in my mid-2007 MacBook. I replaced the 120Gb because I was running out of room. I still use it as an external backup for certain files. The 320Gb Hitachi failed after less than two years, but had a three-year-warranty, so it was replaced at no charge. I'm using the Hitachi replacement externally to clone my current drive in order to test OS X and software updates before installing them 'for keeps' on my working system.
A solid-state (SSD) drive might be less prone to mechanical failure, but that is still no absolute guarantee that it won't EVER fail, and SSD's are still about double or more the cost of mechanical drives.
The best thing is to simply be prepared for the eventual failure with a strategy for frequent and reliable backups. -
Clock problem and shutdown problem! Are they related?
Having a problem with my Dual 2 GHz Power Mac G5
A few days ago I noticed that my clock was not showing in the menu bar in the upper right corner of my desktop.
I went into System Preferences and went to Date & Time. Under the clock tab “Show Date and Time in Menu Bar” the box was not checked off. I checked it off and went to the “Date and Time” tab. The date and time was correct. I then checked the box “Click the lock to prevent further changes” to lock it. The date and time did not show up in the menu bar. I then went back to the tab “Show Date and Time in Menu Bar” and the box I checked was not checked off even thought the lock was still locked.
I then moved my cursor up to the menu bar in the upper right corner to see what would happen and the spinning beach ball started up but only for the original icons such as Bluetooth, Mobile Me (which I do not use), Time Machine, Spaces (doesn’t indicated the number when I switch Spaces, etc. The icons Norton Anti Virus and Tech Tool Pro in the menu bar are okay.
Also, when I attempt to shut down my computer the system clears the icons from my desktop except for a picture I have on my desktop and I get a gray wheel spinning and the system just hangs until I press and hold the on/off switch. I don’t know if the clock and shutdown problems are related.
The only new software I loaded recently was Skype with Logitech WebCam for the Mac and Quicken 2007 (Had a problem with Quicken 2006). They both are working okay.
And ideas on why I cannot get my clock to show up and my computer to shutdown?You may have to consider a new post in the Hardware forum area for the computer
model and build/year; if there is a possibility of some basis the matter could be in
the machine and not the software running within it.
Your last two/three posts are in the Leopard 10.5(.8) forum area and do indicate
some kind of problem where troubleshooting the computer to discover if the matter
at hand would be either hardware or software based, may be the way to go.
The link to the 10.6 Snow Leopard forum won't be of help if your computer is a
PPC-based G5 tower, or other older pre-Intel configuration. And I remember
your earlier questions about the iMac G4 and some other issues in the past.
You may ask the moderators to put your post in a new thread of its own, in the
Leopard 10.5 area; so as to not 'piggy-back' another topic; even though some
of the odd issues you've had seem similar to this OP's topic line and appear to
be in the same general series of hardware. {The question here seems valid.}
The routine suggestions to check, test, verify, and perhaps repair or replace
the system; save a bootable clone to suitable external standalone device if
testing a suspect computer's viability is recommended; and the basics if not
already tried to help isolate the issue(s) as you've posted elsewhere, may be
of some help to try and do; so in that matter, a new thread of your own is best
for your own directed feedback. Since this kind of advice applies to most any
situation, including troubleshooting what may be hardware or software, I'm
adding my two and three-tenths cents worth here.
Your original included Apple Hardware Test may be of some help, in the process
of elimination; but is not conclusive, so other methods would be also suggested.
Some ideas appear to cover the same ground. However, system corruption or
disc failure can also manifest itself in odd ways & affect things indirectly for a time.
• OS X Maintenance And Troubleshooting
http://www.macattorney.com/ts.html
• Mac OS X BASIC TROUBLESHOOTING & MAINTENANCE
http://www.gballard.net/macrant/osx_troubleshooting.html
• Troubleshooting Tips for computers:
http://www.stcdio.org/offices/cem/mediaandtechnology/cem-computer-classes/troubl eshooting.html
So, at the risk of inadvertently alienating the OP, I am posting this as
a general help to following readers at some later time; and it may not
be too simple for a refresh course.
Some software issues can be resolved by repairing disk permissions,
and re-applying the last OS X update Combo file over the same one
already in the system; or if not up-to-date already, check & repair all
the general items and then apply the last Combo update.
A too-full hard disk drive can compromise the system integrity, so that
is a matter of course to keep up on what resources exist and remain
for the OS X to function correctly and for apps to multi-task together.
However that works out...
Good luck & happy computing! -
After rebooting after the power failure when I go to new websites or even within some websites after clicking on a link the message box appears and I have to add a security exception to get past the message and see the link. I am using V4.0. I do not get that message on another computer using V 3.6.15.
What can I do to reset the browser?John,
That did it! I no longer get that message. The clock was set to the wrong day and time. So far it is keeping time correctly, but per your suggestion I will also check the battery.
Thanks for the prompt and accurate help.
H Weiss -
Hi Guys,
I have a head scratcher that I'm dealing with. I have 2x (2 month) 6880-x switches configured with vss with 2 vsl links on each of its sup cards and switch 1 is the active switch on the vss. Both 6880x chassis also have 2 additional 10g modules each. I am dealing with 2 issues in this setup.
The first issue is, i have a 3750x with a 10g module thats port channeled to the vss with one 10g link going to each of the chassis. Within the first 3 days it started dropping the link that's plugged to switch1, then comes back on right away. It does it randomly throughout the day. I have changed out the optics on both ends, changed the cable, and also changed the module on the 3750x and I still get the same issue. The strange part is that when switch2 on the vss becomes the active switch, the problem goes away. I did notice this before changing out the optics, cable, module on the 3750x.
The second issue is the one I'm been trying to figure out along with cisco TAC. This started about a month after bring the vss online. When switch1 was the active switch in the vss, every couple of days vsl links drop one at a time, eventually killing the vss and putting the standby unit into recovery mode because of the dual active detection. once I reboot the standby switch, the vss comes back up normally. it did this a couple of times until I decided to force switch2 to be the active switch on the vss. when switch2 became active, the vss was stable for about a month then the vsl links died again, and the system failed over to switch1. after looking at the logs with cisco tac, we see that the vsl links stop responding which causes the failover, but up until now we still can't determine what is causing the vsl links to fail. cisco tac said that maybe the vsl links were being overloaded but we have been monitoring the bandwidth utilization on the vsl links and they never go beyond 1% utilization. The last suggestion by cisco tac was to add another vsl link but through another module other than the sup. This was done a couple of days ago so now i'm waiting to see if the vsl links fail again and since switch1 is the active switch on the vss, i'm having to deal with the first issue above with the 3750x.
I've included some log entries from the dropped port-channel member and also logs for when the vsl links fail.
Logs for 3750x port-channel member drops.
*Jul 5 05:27:10 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 5 05:27:10 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 5 05:27:10 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
*Jul 5 05:28:10 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to up
*Jul 6 11:28:52 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 6 11:28:52 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 6 11:28:53 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
*Jul 6 11:29:53 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to up
*Jul 7 06:27:25 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 7 06:27:25 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 7 06:27:26 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
*Jul 7 06:27:33 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to up
*Jul 7 06:33:43 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 7 06:33:43 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 7 06:33:43 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
*Jul 7 06:34:43 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to up
*Jul 7 07:38:35 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 7 07:38:35 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
*Jul 7 07:38:36 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
log for VSL link failures
*Jun 27 23:59:25 PDT: %VSLP-SW2-3-VSLP_LMP_FAIL_REASON: Te2/5/15: Link down
*Jun 27 23:59:25 PDT: %VSL-SW2-5-VSL_CNTRL_LINK: New VSL Control Link 2/5/16
*Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/5/15, changed state to down
*Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/5/15, changed state to down
*Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet2/5/15, changed state to down
*Jun 27 23:59:25 PDT: %VSLP-SW2-3-VSLP_LMP_FAIL_REASON: Te2/5/16: Link down
*Jun 27 23:59:25 PDT: %VSLP-SW2-2-VSL_DOWN: Last VSL interface Te2/5/16 went down
*Jun 27 23:59:25 PDT: %VSLP-SW2-2-VSL_DOWN: All VSL links went down while switch is in ACTIVE role
*Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/5/16, changed state to down
*Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface Port-channel2, changed state to down
*Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface Port-channel2, changed state to down
*Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet2/5/16, changed state to down
*Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
*Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface Port-channel1, changed state to down
*Jun 27 23:59:25 PDT: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD removed
*Jun 27 23:59:25 PDT: %OSPF-SW2-5-ADJCHG: Process 1, Nbr 10.253.0.3 on TenGigabitEthernet1/1/1 from FULL to DOWN, Neighbor Down: Interface down or detached
*Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface Port-channel24, changed state to down
*Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface Port-channel24, changed state to down
*Jun 27 23:59:26 PDT: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD removed
*Jun 27 23:59:26 PDT: %LINK-SW2-3-UPDOWN: Interface Port-channel17, changed state to down
*Jun 27 23:59:26 PDT: %PFREDUN-SW2-6-ACTIVE: Standby processor removed or reloaded, changing to Simplex mode
*Jun 27 23:59:26 PDT: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD removed
*Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/5/14, changed state to down
*Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/5/15, changed state to down
*Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/5/16, changed state to down
*Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/5/14, changed state to down
*Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/5/16, changed state to down
*Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/1/1, changed state to down
*Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/1/2, changed state to down
*Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/1/3, changed state to down
*Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/1, changed state to down
*Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/2, changed state to down
*Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/3, changed state to down
Press RETURN to get started!
*Jun 28 07:03:33.421: %USBFLASH-SW2_STBY-5-CHANGE: bootdisk has been inserted!
*Jun 28 07:03:53.297: %OIR-SW2_STBY-6-INSPS: Power supply inserted in slot 1
*Jun 28 07:03:53.301: %C6KPWR-SW2_STBY-4-PSOK: power supply 1 turned on.
*Jun 28 07:04:26.093: %FABRIC-SW2_STBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
*Jun 28 07:04:48.497: %DIAG-SW2_STBY-6-RUN_MINIMUM: Switch 2 Module 5: Running Minimal Diagnostics...
*Jun 28 07:04:48.497: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 15 is skipped in TestLoopback due to: the port is used as a VSL link.
*Jun 28 07:04:48.497: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 16 is skipped in TestLoopback due to: the port is used as a VSL link.
*Jun 28 07:04:55.049: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 15 is skipped in TestFexModeLoopback due to: the port is used as a VSL link.
*Jun 28 07:04:55.049: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 16 is skipped in TestFexModeLoopback due to: the port is used as a VSL link.
*Jun 28 07:05:00.165: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 15 is skipped in TestL2CTSLoopback due to: the port is used as a VSL link.
*Jun 28 07:05:00.165: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 16 is skipped in TestL2CTSLoopback due to: the port is used as a VSL link.
*Jun 28 07:05:06.049: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 15 is skipped in TestL3CTSLoopback due to: the port is used as a VSL link.
*Jun 28 07:05:06.049: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 16 is skipped in TestL3CTSLoopback due to: the port is used as a VSL link.
*Jun 28 07:05:23.309: %DIAG-SW2_STBY-6-DIAG_OK: Switch 2 Module 5: Passed Online Diagnostics
*Jun 28 00:05:38 PDT: %SYS-SW2_STBY-6-CLOCKUPDATE: System clock has been updated from 00:05:38 PDT Sat Jun 28 2014 to 00:05:38 PDT Sat Jun 28 2014, configured from console by console.
*Jun 28 00:05:38 PDT: %SYS-SW2_STBY-6-CLOCKUPDATE: System clock has been updated from 00:05:38 PDT Sat Jun 28 2014 to 00:05:38 PDT Sat Jun 28 2014, configured from console by console.
*Jun 28 00:05:38 PDT: %SSH-SW2_STBY-5-DISABLED: SSH 2.0 has been disabled
*Jun 28 00:05:54 PDT: %SYS-SW2_STBY-5-RESTART: System restarted --
Cisco IOS Software, c6880x Software (c6880x-ADVENTERPRISEK9-M), Version 15.1(2)SY2, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Wed 26-Feb-14 15:30 by prod_rel_team
*Jun 28 00:05:54 PDT: %SSH-SW2_STBY-5-ENABLED: SSH 2.0 has been enabled
*Jun 28 00:05:54 PDT: %SYS-SW2_STBY-3-LOGGER_FLUSHED: System was paused for 00:03:01 to ensure console debugging output.
*Jun 28 00:05:56 PDT: %C6KENV-SW2_STBY-4-LOWER_SLOT_EMPTY: The lower adjacent slot of module 5 might be empty. Airdam must be installed in that slot to be NEBS compliant
*Jun 28 00:07:36 PDT: %DIAG-SW2_STBY-6-RUN_MINIMUM: Switch 2 Module 1: Running Minimal Diagnostics...
*Jun 28 00:07:37 PDT: %SYS-SW2_STBY-3-LOGGER_FLUSHED: System was paused for 00:01:29 to ensure console debugging output.
*Jun 28 00:07:41 PDT: %DIAG-SW2_STBY-6-RUN_MINIMUM: Switch 2 Module 2: Running Minimal Diagnostics...
*Jun 28 00:08:10 PDT: %DIAG-SW2_STBY-6-DIAG_OK: Switch 2 Module 1: Passed Online Diagnostics
*Jun 28 00:08:22 PDT: %EC-SW2_STBY-5-CANNOT_BUNDLE2: Te2/1/10 is not compatible with Te1/2/10 and will be suspended (Operational flow control send of Te2/1/10 is off, Te1/2/10 is on)
*Jun 28 00:08:31 PDT: %EC-SW2_STBY-5-COMPATIBLE: Te2/1/10 is compatible with port-channel members
*Jun 28 00:08:45 PDT: %DIAG-SW2_STBY-6-DIAG_OK: Switch 2 Module 2: Passed Online Diagnostics
*Jun 28 00:08:46 PDT: %C6KENV-SW2_STBY-4-HIGHER_SLOT_EMPTY: The higher adjacent slot of module 2 might be empty. Airdam must be installed in that slot to be NEBS compliant
ELDC1C1-AG01-1 line 0
************************ W A R N I N G ***************************
* THIS IS A PRIVATE COMPUTER SYSTEM, AND FOR AUTHORIZED USE ONLY.*
* THIS SYSTEM IS MONITORED, AND ANY UNAUTHORIZED USE MAY BE *
* SUBJECT TO CRIMINAL PROSECUTION. *
* IF YOU ARE NOT AUTHORIZED, LOG OUT IMMEDIATELY!!!!! *
so according to the logs, it seems like the switch was reloaded or something of the nature but even the cisco tac said that it wasnt the case but couldnt determine whats causing it either. Tac went through the config on the vss and has said that its configured correctly.
Maybe someone else has experienced this issue or if someone can point out something that I can look at... sorry for the very long post.
thanksI suppose, we have the same problem. Only when Switch 1 is the active switch of the 6880-X VSS system, the connection to the FEX-stack breaks suddenly after running fine for some days and the FEX-stack (3 x 6800-IA) get only ready again when I reset the whole VSS-system, both VSS-switches and the FEX-stack.
All access ports at the FEX can't connect to our infrastructure (DHCP,DNS...). The two connected TenG FEX-stack uplinks sometimes get down and sometimes only the uplink to the active parent switch get down. The SYST LED of FEX 1 lighting amber.
When parent switch 2 is the active unit the issue never occured.
6880-X running with 15.2(1)SY, 6800-IA running with 15.2(3)E.
Cisco TAC is investigating that issue, but till now without any result.
When the issue occurs, the recorded logging messages are:
Syslog 6880-X
Apr 7 07:42:43.182: %PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 3, class 21, max_msg 32, total throttled 1274 (FEX-101)
Apr 7 07:45:43.181: %PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 3, class 21, max_msg 32, total throttled 1276 (FEX-101)
Syslog 6800-IA:
Apr 7 07:57:43.182: %PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 3, class 21, max_msg 32, total throttled 1284
-Traceback= 5198C4z 21413F8z 1C3B35Cz 1C3C6FCz 1C3CA00z 2654CC0z 26509BCz
Apr 7 08:00:43.181: %PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 3, class 21, max_msg 32, total throttled 1286
-Traceback= 5198C4z 21413F8z 1C3B35Cz 1C3C6FCz 1C3CA00z 2654CC0z 26509BCz -
X121e randomly wake up from suspended status and real time clock error
Hi all
Previously I considered my x121e suffer from overheating issue and causes real time clock error (RTC). However, after more testing and investigation, I believe the problem is related to other hardware issues and I like to hear people opinion before sending the laptop back to Lenovo.
The machine goes into suspend status either pressing the power button or closing the lid from Windows7 (clean install) without problem. However, it would wake up itself randomly, "beep" twice and screen shows RTC and CMOS checksum error. This happen more often when I am holding the machine (i.e. some movement/vibration). I wonder:
- Is it the RTC battery problem, cause the RTC to wake up the machine?
- Other hardware failure?
The laptop has a clean OS installed/recovered. Latest 1.16 Bios installed. No USB or memory card attached. Ram replaced and not the cause.
Please advise
HowardHello,
I am unsure; you would have to contact Lenovo directly and find out how they handle this situation. They may want the ThinkPad X121e back so they can run thorough diagnostics on it, just in case the problem is something else. That way it gets fixed the first time.
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество -
Iphone not ringing, clock not holding correct time and no wi-fi
Man...I thought I had done something, but since the 2.1 update, my phone doesnt ring but for one or two random calls. The clock is also not holding time...it does if i restart the phone but within hours its back to hopping around, trying to get the right time. When it does stop doing that, the time is wrong.
On top of that, it cannot find any wi-fi connections.
Ive restored it to the previous back up and it doesnt do any of this.
Is anyone else having these problems since the update?Try the suggestions here to see if they resolve your problem:
http://support.apple.com/kb/ts1559
If those solutions don't work your iPhone 4s has probably developed a hardware problem. The permanent solution is to get it replaced.
You can search the internet for heating and freezing solutions that might work (at least for a while).
For example, see here: https://www.youtube.com/watch?v=nj10bz5bI6A
Root cause: On some iPhone 4s devices there may be a flow soldering problem with the WiFi chip. After long periods of WiFi activity such as installing an iOS update (for example, iOS 7 or iOS 8) there may be a connection failure. A work-around to this is the procedure in the youTube video.
A true hardware fix may be found here:
https://www.ifixit.com/Guide/How+to+Fix+iPhone+4S+Wi-Fi+Grayed+Out/22167
Maybe you are looking for
-
EN488AA docking station - not charging
Hi all, this is my first post on this forum (i dont work for HP) so be nice We have had a few docking stations (EN488AA) which have stopped charging the laptop's when they are docked. As an electronics engineer my interest was tweaked and I had to ta
-
Dynamic shell script scheduling
I want to automate a report to run on the 20th of every month through a shell script. However, I don't want to run if 20th happens to be a weekend. Any ideas on how to do this? Do I need a seperate script to check for the date? thanks
-
Disjoint Selections in Parallel Processing Profile
Hello All, I wanted to use the parallel processing profile for my DP background jobs. When I referred the 'Note 853142 - Consulting: Parallel processing profile for DP batch runs' it says use this parallel processing using disjoint selection
-
Igfxtray.exe has stopped working
Hi, The error message "igfxtray.exe has stopped working" appears every time I start my computer (a newly bought asus G551jm running Windows 8.1). I already tried to reinstall both the Intel and the Nvidia graphic drivers but the message keeps popping
-
Hi I am new member My phone reports error code 1009 What is it? Please help me Thank u