Gig 1/1 interface on a standby Sup 2 card active?

Hi,
My 2 6513s each have 2 Sup 2 cards in them. The slot 1 Sup card in both 6513s is the active one and Gi1/1 on each connects the 2 6513s together.
Tonight I want to pull the active Sup 2 card from the secondary 6513. If I move the cable in the secondary 6513 from Gi1/1 to Gi2/1, will I still have connectivity between the 2 6513s?
In other words, are the interfaces on the standby Sup 2 card available for use when the card is in standby mode or does it only work when it becomes active?
The configuration of ports 1/1 and 2/1 of the 2nd 6513 are below.
Also, is there a document that delineates how these 2 Sup cards on these 2 6513s should be configured for highest availability (ie. Sup card failure on either 6513)? I looked high and low on Cisco's Web site but could not find one.
Thanks, Ian.
interface GigabitEthernet1/1
description Link to COBCore1
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 99
switchport trunk allowed vlan 80,99,100,110,111,113,120-123,130,131,133,140
switchport trunk allowed vlan add 141,153,155,165,181-186,189,200,210,212,231
switchport trunk allowed vlan add 500
switchport mode trunk
spanning-tree link-type point-to-point
interface GigabitEthernet1/2
no ip address
shutdown
interface GigabitEthernet2/1
description Link to COBCore1
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 99
switchport trunk allowed vlan 80,99,100,110,111,113,120-123,130,131,133,140
switchport trunk allowed vlan add 141,153,155,165,181-186,189,200,210,212,231
switchport trunk allowed vlan add 500
switchport mode trunk
spanning-tree link-type point-to-point

the GB interfaces on the standby 6500 supervisor are active, even if the sup is in standby mode.
configure your switch to use the 1/2 GB interface and make the link connection. verify the link is up and you can pass traffic.
then you can adjust your 1/1 interface without causing downtime.
(if you create an etherchannel of the two, this will allow you to remove 1/1 and not lose any connectivity)
for high availability, i use the practice of:
switch1-sup1 gb 1/1 >> switch2-sup2 gb 1/1
switch1-sup1 gb 1/2 >> switch2-sup1 gb 1/2
switch1-sup2 gb 1/1 >> switch2-sup1 gb 1/1
switch1-sup2 gb 1/2 >> switch2-sup2 gb 1/2
this allows for a fully meshed configuration for highest available redundancy.

Similar Messages

Standby Sup synchronization verification

My redundant supervisor crashed sometime back. The following error was observed
%SYS-3-SYS_LCPERR3:Module 2: Bus Asic #0 out of sync error:
Module requires attention - troubleshoot or contact TAC for assistance
This problem was resolved later.
My question is how do i verify that my standby sup will function properly when the active one fails? This is a production network, can't bring it down for testing.
I tried to verify if the bootflash in module 2 had synchronized with the image in the active sup using the command
show flash 2/bootflash:
But this command gives me the message File system in use (8). Try again later.
Is this normal? should i be concerned?
Is there any other way to check if the standby sup will function properly in the event of the primary failing

Hello,
From the output you're seeing from the dir 2/bootflash: it appears that the bootflash is being locked by another process. I've provided a sample of the same outputs for your review from another switch to compare.
SR3-Cat6509a (enable) dir bootflash:
-#- -length- -----date/time------ name
1 9720136 Jan 25 2006 22:27:08 cat6000-sup2k8.8-4-5.bin
2 8828948 Feb 19 2006 02:30:34 cat6000-sup2k8.8-3-5.bin
3 7671080 Feb 19 2006 02:57:13 RTSYNC_cat6000-sup2k8.7-6-9.bin
5761020 bytes available (26220548 bytes used)
SR3-Cat6509a (enable) dir 2/bootflash:
-#- -length- -----date/time------ name
1 7671080 Feb 03 2006 19:40:21 cat6000-sup2k8.7-6-9.bin
2 8828948 Feb 19 2006 03:16:16 cat6000-sup2k8.8-3-5.bin
15481284 bytes available (16500284 bytes used)
Hope this helps.
Regards,
James

Change parameter instance_name after standby database has been activated

Hello ,
our primary database is configured as follows:
SQL> show parameter db_name;
NAME                                 TYPE        VALUE
db_name                              string      prod01
SQL> show parameter instance_name
NAME                                 TYPE        VALUE
instance_name                        string      prod01
the corresponding standby database is configured as:
SQL> show parameter db_name;
NAME                                 TYPE        VALUE
db_name                              string      prod01
SQL> show parameter instance_name
NAME                                 TYPE        VALUE
instance_name                        string      stbyprod01
Now the standby database shall be activated. Afterwards I want to change the parameter INSTANCE_NAME from stbyprod01 to prod01.
The question now is: what needs to be done to change the parameter INSTANCE_NAME? As a matter of fact the standby database will
already be activated and be treated and handled as a standalone database. The former primary database will not be used anymore.
I would proceed as follows:
SQL> create pfile='initprod01.ora' from spfile;
SQL> shutdown immediate;
oracle #> edit the pfile and change the parameter INSTANCE_NAME from stbyprod01 to prod01
SQL> startup;
SQL> create spfile='spfileprod01.ora' from pfile;
SQL> shutdown immediate;
SQL> startup;
That should be all - from my point of view (I know that LISTENER.ORA and TNSNAMES.ORA should be modified, too).
If anybody has already experiences with changing the INSTANCE_NAME parameter but sees some further configurations: please just let me know!
Rgds
Jan

Hi ,
only "alter system set instance_name='TEST' scope=spfile" will work since the parameter INSTANCE_NAME is static. After restarting the database/instance the statement "show parameter instance_name" will show the new instance name.
But when selecting the view V$INSTANCE the value of the column INSTANCE_NAME has still the old value. Any idea why this value remains unchanged in the view V$INSTANCE?
Rgds
Jan

Monitor interface vlan with ASA 5505 in HA Active/Standby Deployment

Hi,
I doing HA Active/Standby Deployment with two ASA 5505. ASA documents mention that it will monitor all physical interfaces itself to decide a failover. But in my case I configure vlan interface instead of physical interface. My inside interfaces in each ASA connect to two diferent Switches. My question is if one inside physical interface (lead to one switch) down, does the failover occur? I suspect it does not, but I would like to make sure before doing HA.
Any replies will be appreciated.

Hi, I usually instead of doing a cross-connect on the inside leave it to something like A-to-A and B-to-B if the switches are not doing VSS or VPC. So I would just connect eth0/7 from ASA-A to SW-A and similar on ASA-B. This makes it cleaner.
You can then control if you want to failover if the PO goes down or any 1 of the 2 interfaces in the PO go down.
I am not saying that your above design is invalid, but I have usually done this in the past.

Actiontec MI424WR GigE Bonded LAN interfaces

Good Morning Everyone! I wanted to see if it was possible to bond the 4 LAN interfaces on the Actiontec MI424WR GigE routers to connect up to a etherchannel on a Cisco Switch? I have looked at the manual but I have been unable to find any information on this setup. Just curious to see if anyone has accomplished this. Thanks.

Why would you want to do that? The FiOS WAN link is at best 300/65Mbs. A single GigE port has more than enough bandwidth to handle this. Redundancy is not an issue, as there is only one WAN link so a redundant LAN doesn't buy anything.
To answer your question, I've never heard or seen anything about Ethernet bonding support in the MI424WR routers. Bonding is something used by high end networks, and not typically found on a small office/home office router such as the MI424WR
Have Fun!
If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.

X11 won't start (sets monitor to standby) with nVidia card

Hello everyone!
I'm having some trouble getting my computer to work properly. Yesterday it was working perfectly, but today it would't start again. After some troubleshooting I've determined that the problem lies with X11 and the graphics driver. The bootloader, grub, and arch itself, boots perfectly in runlevel 3, but the moment you run "startx" it would appear to be loading for a while and finally the screen goes to standby mode and there is no way out of that other than reseting the computer using the reset button. I've tried uninstalling the nvidia drivers and installing nouveau drivers, but it still won't start X, this time arround, it would just hang up with a white screen.
I've also tried removing xorg.conf and also using nvidia utility to generate a new one, but neither seems to work.
/var/log/Xorg.0.log doesn't report any errors, it just gives different info from the configuration and the graphics card and just ends there.
I've tried booting with a debian live USB but it would't boot either (the computer would just restart). I've also tried a Kubuntu live USB, this time arround, it would start to boot but the graphics appeared to be corrupted (strange colored noise all over the screen) and eventually it would just hang up. Using nomodeset Kubuntu finally booted (using vesa I guess?), but the same didn't work in Arch (I'm guessing because I have the nvidia drivers installed instead of nouveau).
In conclussion, something appears to be wrong with the graphics card, I dont't know if it's a software problem or a hardware problem, as it started from one day to the other, without any upgrades in between, and it just doesn't work in any of the 3 distributions I've tested.
Any suggestions in what to do to troubleshoot this?
Thanks in advance,
Santiago.-

Xorg.0.log
[ 35.560]
X.Org X Server 1.14.4
Release Date: 2013-10-31
[ 35.560] X Protocol Version 11, Revision 0
[ 35.560] Build Operating System: Linux 3.11.6-1-ARCH x86_64
[ 35.561] Current Operating System: Linux arch 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
[ 35.561] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=17d019be-e01f-4c1c-ac50-69e1f3dc0592 rw quiet 3
[ 35.562] Build Date: 01 November 2013 05:10:48PM
[ 35.562]
[ 35.562] Current version of pixman: 0.30.2
[ 35.562] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 35.562] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 35.564] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 4 21:35:07 2013
[ 35.576] (==) Using config file: "/etc/X11/xorg.conf"
[ 35.576] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 35.577] (==) ServerLayout "Layout0"
[ 35.577] (**) |-->Screen "Screen0" (0)
[ 35.577] (**) | |-->Monitor "Monitor0"
[ 35.577] (**) | |-->Device "Device0"
[ 35.577] (**) |-->Input Device "Keyboard0"
[ 35.577] (**) |-->Input Device "Mouse0"
[ 35.577] (==) Automatically adding devices
[ 35.577] (==) Automatically enabling devices
[ 35.577] (==) Automatically adding GPU devices
[ 35.603] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 35.603] Entry deleted from font path.
[ 35.603] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 35.603] Entry deleted from font path.
[ 35.603] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 35.603] Entry deleted from font path.
[ 35.603] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 35.604] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 35.604] Entry deleted from font path.
[ 35.604] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 35.604] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 35.604] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 35.604] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 35.604] (WW) Disabling Keyboard0
[ 35.604] (WW) Disabling Mouse0
[ 35.604] (II) Loader magic: 0x7fdc20
[ 35.604] (II) Module ABI versions:
[ 35.604] X.Org ANSI C Emulation: 0.4
[ 35.604] X.Org Video Driver: 14.1
[ 35.604] X.Org XInput driver : 19.1
[ 35.604] X.Org Server Extension : 7.0
[ 35.604] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 35.605] (--) PCI:*(0:1:0:0) 10de:0421:1682:2353 rev 161, Mem @ 0xfa000000/16777216, 0xd0000000/268435456, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[ 35.606] Initializing built-in extension Generic Event Extension
[ 35.606] Initializing built-in extension SHAPE
[ 35.606] Initializing built-in extension MIT-SHM
[ 35.606] Initializing built-in extension XInputExtension
[ 35.606] Initializing built-in extension XTEST
[ 35.607] Initializing built-in extension BIG-REQUESTS
[ 35.607] Initializing built-in extension SYNC
[ 35.607] Initializing built-in extension XKEYBOARD
[ 35.607] Initializing built-in extension XC-MISC
[ 35.608] Initializing built-in extension SECURITY
[ 35.608] Initializing built-in extension XINERAMA
[ 35.608] Initializing built-in extension XFIXES
[ 35.608] Initializing built-in extension RENDER
[ 35.608] Initializing built-in extension RANDR
[ 35.609] Initializing built-in extension COMPOSITE
[ 35.609] Initializing built-in extension DAMAGE
[ 35.609] Initializing built-in extension MIT-SCREEN-SAVER
[ 35.609] Initializing built-in extension DOUBLE-BUFFER
[ 35.619] Initializing built-in extension RECORD
[ 35.629] Initializing built-in extension DPMS
[ 35.638] Initializing built-in extension X-Resource
[ 35.647] Initializing built-in extension XVideo
[ 35.656] Initializing built-in extension XVideo-MotionCompensation
[ 35.665] Initializing built-in extension XFree86-VidModeExtension
[ 35.673] Initializing built-in extension XFree86-DGA
[ 35.682] Initializing built-in extension XFree86-DRI
[ 35.690] Initializing built-in extension DRI2
[ 35.690] (II) LoadModule: "glx"
[ 35.757] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 36.111] (II) Module glx: vendor="NVIDIA Corporation"
[ 36.111] compiled for 4.0.2, module version = 1.0.0
[ 36.111] Module class: X.Org Server Extension
[ 36.111] (II) NVIDIA GLX Module 325.15 Wed Jul 31 18:12:00 PDT 2013
[ 36.126] Loading extension GLX
[ 36.126] (II) LoadModule: "nvidia"
[ 36.136] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 36.195] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 36.195] compiled for 4.0.2, module version = 1.0.0
[ 36.195] Module class: X.Org Video Driver
[ 36.197] (II) NVIDIA dlloader X Driver 325.15 Wed Jul 31 17:50:57 PDT 2013
[ 36.197] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 36.197] (--) using VT number 2
[ 36.248] (II) Loading sub module "fb"
[ 36.248] (II) LoadModule: "fb"
[ 36.259] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 36.270] (II) Module fb: vendor="X.Org Foundation"
[ 36.270] compiled for 1.14.4, module version = 1.0.0
[ 36.270] ABI class: X.Org ANSI C Emulation, version 0.4
[ 36.270] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 36.270] (II) Loading sub module "wfb"
[ 36.270] (II) LoadModule: "wfb"
[ 36.270] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 36.271] (II) Module wfb: vendor="X.Org Foundation"
[ 36.271] compiled for 1.14.4, module version = 1.0.0
[ 36.271] ABI class: X.Org ANSI C Emulation, version 0.4
[ 36.271] (II) Loading sub module "shadow"
[ 36.271] (II) LoadModule: "shadow"
[ 36.271] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 36.272] (II) Module shadow: vendor="X.Org Foundation"
[ 36.272] compiled for 1.14.4, module version = 1.1.0
[ 36.272] ABI class: X.Org ANSI C Emulation, version 0.4
[ 36.272] (II) Loading sub module "ramdac"
[ 36.272] (II) LoadModule: "ramdac"
[ 36.272] (II) Module "ramdac" already built-in
[ 36.274] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 36.274] (==) NVIDIA(0): RGB weight 888
[ 36.274] (==) NVIDIA(0): Default visual is TrueColor
[ 36.274] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 36.274] (**) NVIDIA(0): Option "UseEdidDpi" "False"
[ 36.274] (**) NVIDIA(0): Option "DPI" "96 x 96"
[ 36.274] (**) NVIDIA(0): Enabling 2D acceleration
[ 50.151] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[ 50.256] (II) NVIDIA(GPU-0): Display (Samsung SMB2330H (CRT-0)) does not support NVIDIA 3D
[ 50.256] (II) NVIDIA(GPU-0): Vision stereo.
[ 50.256] (II) NVIDIA(0): NVIDIA GPU GeForce 8500 GT (G86) at PCI:1:0:0 (GPU-0)
[ 50.256] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 50.256] (--) NVIDIA(0): VideoBIOS: 60.86.41.00.85
[ 50.256] (II) NVIDIA(0): Detected PCI Express Link width: 16X
journalctl -xb
-- Logs begin at Sat 2013-08-17 21:55:41 ART, end at Mon 2013-11-04 22:01:35 ART. --
Nov 04 21:59:09 arch systemd-journal[120]: Runtime journal is using 364.0K (max 100.1M, leaving 150.2M of free 1001.3M, current limit 100.1M).
Nov 04 21:59:09 arch systemd-journal[120]: Runtime journal is using 368.0K (max 100.1M, leaving 150.2M of free 1001.3M, current limit 100.1M).
Nov 04 21:59:09 arch kernel: Initializing cgroup subsys cpuset
Nov 04 21:59:09 arch kernel: Initializing cgroup subsys cpu
Nov 04 21:59:09 arch kernel: Initializing cgroup subsys cpuacct
Nov 04 21:59:09 arch kernel: Linux version 3.11.6-1-ARCH (nobody@var-lib-archbuild-extra-x86_64-thomas) (gcc version 4.8.1 20130725 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013
Nov 04 21:59:09 arch kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=17d019be-e01f-4c1c-ac50-69e1f3dc0592 rw quiet 3
Nov 04 21:59:09 arch kernel: e820: BIOS-provided physical RAM map:
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007fbb4fff] usable
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fbb5000-0x000000007fbf7fff] ACPI NVS
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fbf8000-0x000000007fd4bfff] reserved
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd4c000-0x000000007fd51fff] ACPI data
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd52000-0x000000007fd52fff] ACPI NVS
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd53000-0x000000007fd54fff] ACPI data
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd55000-0x000000007fd56fff] ACPI NVS
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd57000-0x000000007fd57fff] reserved
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd58000-0x000000007fd5bfff] ACPI NVS
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd5c000-0x000000007fd6afff] reserved
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd6b000-0x000000007fefffff] usable
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffbfffff] reserved
Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
Nov 04 21:59:09 arch kernel: NX (Execute Disable) protection: active
Nov 04 21:59:09 arch kernel: SMBIOS 2.4 present.
Nov 04 21:59:09 arch kernel: DMI: /DG31PR, BIOS PRG3110H.86A.0071.2010.0318.1704 03/18/2010
Nov 04 21:59:09 arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 04 21:59:09 arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 04 21:59:09 arch kernel: No AGP bridge found
Nov 04 21:59:09 arch kernel: e820: last_pfn = 0x7ff00 max_arch_pfn = 0x400000000
Nov 04 21:59:09 arch kernel: MTRR default type: uncachable
Nov 04 21:59:09 arch kernel: MTRR fixed ranges enabled:
Nov 04 21:59:09 arch kernel: 00000-9FFFF write-back
Nov 04 21:59:09 arch kernel: A0000-E7FFF uncachable
Nov 04 21:59:09 arch kernel: E8000-FFFFF write-protect
Nov 04 21:59:09 arch kernel: MTRR variable ranges enabled:
Nov 04 21:59:09 arch kernel: 0 base 000000000 mask F80000000 write-back
Nov 04 21:59:09 arch kernel: 1 base 07FF00000 mask FFFF00000 uncachable
Nov 04 21:59:09 arch kernel: 2 disabled
Nov 04 21:59:09 arch kernel: 3 disabled
Nov 04 21:59:09 arch kernel: 4 disabled
Nov 04 21:59:09 arch kernel: 5 disabled
Nov 04 21:59:09 arch kernel: 6 disabled
Nov 04 21:59:09 arch kernel: 7 disabled
Nov 04 21:59:09 arch kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov 04 21:59:09 arch kernel: found SMP MP-table at [mem 0x000fc620-0x000fc62f] mapped at [ffff8800000fc620]
Nov 04 21:59:09 arch kernel: Scanning 1 areas for low memory corruption
Nov 04 21:59:09 arch kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov 04 21:59:09 arch kernel: [mem 0x00000000-0x000fffff] page 4k
Nov 04 21:59:09 arch kernel: BRK [0x01b2f000, 0x01b2ffff] PGTABLE
Nov 04 21:59:09 arch kernel: BRK [0x01b30000, 0x01b30fff] PGTABLE
Nov 04 21:59:09 arch kernel: BRK [0x01b31000, 0x01b31fff] PGTABLE
Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7f800000-0x7f9fffff]
Nov 04 21:59:09 arch kernel: [mem 0x7f800000-0x7f9fffff] page 2M
Nov 04 21:59:09 arch kernel: BRK [0x01b32000, 0x01b32fff] PGTABLE
Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7c000000-0x7f7fffff]
Nov 04 21:59:09 arch kernel: [mem 0x7c000000-0x7f7fffff] page 2M
Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x00100000-0x7bffffff]
Nov 04 21:59:09 arch kernel: [mem 0x00100000-0x001fffff] page 4k
Nov 04 21:59:09 arch kernel: [mem 0x00200000-0x7bffffff] page 2M
Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7fa00000-0x7fbb4fff]
Nov 04 21:59:09 arch kernel: [mem 0x7fa00000-0x7fbb4fff] page 4k
Nov 04 21:59:09 arch kernel: BRK [0x01b33000, 0x01b33fff] PGTABLE
Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7fd6b000-0x7fefffff]
Nov 04 21:59:09 arch kernel: [mem 0x7fd6b000-0x7fefffff] page 4k
Nov 04 21:59:09 arch kernel: BRK [0x01b34000, 0x01b34fff] PGTABLE
Nov 04 21:59:09 arch kernel: RAMDISK: [mem 0x37a14000-0x37d01fff]
Nov 04 21:59:09 arch kernel: ACPI: RSDP 00000000000f03f0 00024 (v02 INTEL)
Nov 04 21:59:09 arch kernel: ACPI: XSDT 000000007fd53f10 00044 (v01 INTEL DG31PR 06222004 MSFT 00010013)
Nov 04 21:59:09 arch kernel: ACPI: FACP 000000007fd51d90 000F4 (v04 INTEL DG31PR 06222004 MSFT 00010013)
Nov 04 21:59:09 arch kernel: ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20130517/tbfadt-395)
Nov 04 21:59:09 arch kernel: ACPI BIOS Warning (bug): 32/64X FACS address mismatch in FADT - 0x7FD56F40/0x000000007FD52F40, using 32 (20130517/tbfadt-522)
Nov 04 21:59:09 arch kernel: ACPI: DSDT 000000007fd4c010 04BE9 (v01 INTEL DG31PR 00000000 INTL 20051117)
Nov 04 21:59:09 arch kernel: ACPI: FACS 000000007fd56f40 00040
Nov 04 21:59:09 arch kernel: ACPI: APIC 000000007fd51f10 0006C (v02 INTEL DG31PR 06222004 MSFT 00010013)
Nov 04 21:59:09 arch kernel: ACPI: HPET 000000007fd5ad10 00038 (v01 INTEL ICH7HPET 06222004 AMI. 00000001)
Nov 04 21:59:09 arch kernel: ACPI: MCFG 000000007fd5ac10 0003C (v01 INTEL DG31PR 06222004 MSFT 00000097)
Nov 04 21:59:09 arch kernel: ACPI: Local APIC address 0xfee00000
Nov 04 21:59:09 arch kernel: No NUMA configuration found
Nov 04 21:59:09 arch kernel: Faking a node at [mem 0x0000000000000000-0x000000007fefffff]
Nov 04 21:59:09 arch kernel: Initmem setup node 0 [mem 0x00000000-0x7fefffff]
Nov 04 21:59:09 arch kernel: NODE_DATA [mem 0x7fefb000-0x7fefffff]
Nov 04 21:59:09 arch kernel: [ffffea0000000000-ffffea0001ffffff] PMD -> [ffff88007d200000-ffff88007f1fffff] on node 0
Nov 04 21:59:09 arch kernel: Zone ranges:
Nov 04 21:59:09 arch kernel: DMA [mem 0x00001000-0x00ffffff]
Nov 04 21:59:09 arch kernel: DMA32 [mem 0x01000000-0xffffffff]
Nov 04 21:59:09 arch kernel: Normal empty
Nov 04 21:59:09 arch kernel: Movable zone start for each node
Nov 04 21:59:09 arch kernel: Early memory node ranges
Nov 04 21:59:09 arch kernel: node 0: [mem 0x00001000-0x0009efff]
Nov 04 21:59:09 arch kernel: node 0: [mem 0x00100000-0x7fbb4fff]
Nov 04 21:59:09 arch kernel: node 0: [mem 0x7fd6b000-0x7fefffff]
Nov 04 21:59:09 arch kernel: On node 0 totalpages: 523496
Nov 04 21:59:09 arch kernel: DMA zone: 64 pages used for memmap
Nov 04 21:59:09 arch kernel: DMA zone: 21 pages reserved
Nov 04 21:59:09 arch kernel: DMA zone: 3998 pages, LIFO batch:0
Nov 04 21:59:09 arch kernel: DMA32 zone: 8124 pages used for memmap
Nov 04 21:59:09 arch kernel: DMA32 zone: 519498 pages, LIFO batch:31
Nov 04 21:59:09 arch kernel: ACPI: PM-Timer IO Port: 0x408
Nov 04 21:59:09 arch kernel: ACPI: Local APIC address 0xfee00000
Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
Nov 04 21:59:09 arch kernel: ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
Nov 04 21:59:09 arch kernel: IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
Nov 04 21:59:09 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov 04 21:59:09 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov 04 21:59:09 arch kernel: ACPI: IRQ0 used by override.
Nov 04 21:59:09 arch kernel: ACPI: IRQ2 used by override.
Nov 04 21:59:09 arch kernel: ACPI: IRQ9 used by override.
Nov 04 21:59:09 arch kernel: Using ACPI (MADT) for SMP configuration information
Nov 04 21:59:09 arch kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Nov 04 21:59:09 arch kernel: smpboot: Allowing 4 CPUs, 0 hotplug CPUs
Nov 04 21:59:09 arch kernel: nr_irqs_gsi: 40
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fbb5000-0x7fbf7fff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fbf8000-0x7fd4bfff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd4c000-0x7fd51fff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd52000-0x7fd52fff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd53000-0x7fd54fff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd55000-0x7fd56fff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd57000-0x7fd57fff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd58000-0x7fd5bfff]
Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd5c000-0x7fd6afff]
Nov 04 21:59:09 arch kernel: e820: [mem 0x7ff00000-0xfed1bfff] available for PCI devices
Nov 04 21:59:09 arch kernel: Booting paravirtualized kernel on bare hardware
Nov 04 21:59:09 arch kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
Nov 04 21:59:09 arch kernel: PERCPU: Embedded 29 pages/cpu @ffff88007f800000 s86528 r8192 d24064 u524288
Nov 04 21:59:09 arch kernel: pcpu-alloc: s86528 r8192 d24064 u524288 alloc=1*2097152
Nov 04 21:59:09 arch kernel: pcpu-alloc: [0] 0 1 2 3
Nov 04 21:59:09 arch kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 515287
Nov 04 21:59:09 arch kernel: Policy zone: DMA32
Nov 04 21:59:09 arch kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=17d019be-e01f-4c1c-ac50-69e1f3dc0592 rw quiet 3
Nov 04 21:59:09 arch kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov 04 21:59:09 arch kernel: Checking aperture...
Nov 04 21:59:09 arch kernel: No AGP bridge found
Nov 04 21:59:09 arch kernel: Calgary: detecting Calgary via BIOS EBDA area
Nov 04 21:59:09 arch kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov 04 21:59:09 arch kernel: Memory: 2045916K/2093984K available (5050K kernel code, 799K rwdata, 1696K rodata, 1140K init, 1288K bss, 48068K reserved)
Nov 04 21:59:09 arch kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Nov 04 21:59:09 arch kernel: Preemptible hierarchical RCU implementation.
Nov 04 21:59:09 arch kernel: RCU dyntick-idle grace-period acceleration is enabled.
Nov 04 21:59:09 arch kernel: Dump stacks of tasks blocking RCU-preempt GP.
Nov 04 21:59:09 arch kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
Nov 04 21:59:09 arch kernel: NR_IRQS:8448 nr_irqs:712 16
Nov 04 21:59:09 arch kernel: Console: colour dummy device 80x25
Nov 04 21:59:09 arch kernel: console [tty0] enabled
Nov 04 21:59:09 arch kernel: allocated 8388608 bytes of page_cgroup
Nov 04 21:59:09 arch kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov 04 21:59:09 arch kernel: hpet clockevent registered
Nov 04 21:59:09 arch kernel: tsc: Fast TSC calibration using PIT
Nov 04 21:59:09 arch kernel: tsc: Detected 2399.803 MHz processor
Nov 04 21:59:09 arch kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4801.58 BogoMIPS (lpj=7999343)
Nov 04 21:59:09 arch kernel: pid_max: default: 32768 minimum: 301
Nov 04 21:59:09 arch kernel: Security Framework initialized
Nov 04 21:59:09 arch kernel: AppArmor: AppArmor disabled by boot time parameter
Nov 04 21:59:09 arch kernel: Yama: becoming mindful.
Nov 04 21:59:09 arch kernel: Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Nov 04 21:59:09 arch kernel: Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Nov 04 21:59:09 arch kernel: Mount-cache hash table entries: 256
Nov 04 21:59:09 arch kernel: Initializing cgroup subsys memory
Nov 04 21:59:09 arch kernel: Initializing cgroup subsys devices
Nov 04 21:59:09 arch kernel: Initializing cgroup subsys freezer
Nov 04 21:59:09 arch kernel: Initializing cgroup subsys net_cls
Nov 04 21:59:09 arch kernel: Initializing cgroup subsys blkio
Nov 04 21:59:09 arch kernel: CPU: Physical Processor ID: 0
Nov 04 21:59:09 arch kernel: CPU: Processor Core ID: 0
Nov 04 21:59:09 arch kernel: mce: CPU supports 6 MCE banks
Nov 04 21:59:09 arch kernel: CPU0: Thermal monitoring enabled (TM2)
Nov 04 21:59:09 arch kernel: Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32
tlb_flushall_shift: -1
Nov 04 21:59:09 arch kernel: Freeing SMP alternatives memory: 20K (ffffffff819e6000 - ffffffff819eb000)
Nov 04 21:59:09 arch kernel: ACPI: Core revision 20130517
Nov 04 21:59:09 arch kernel: ACPI: All ACPI Tables successfully acquired
Nov 04 21:59:09 arch kernel: ftrace: allocating 20100 entries in 79 pages
Nov 04 21:59:09 arch kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov 04 21:59:09 arch kernel: smpboot: CPU0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (fam: 06, model: 0f, stepping: 0b)
Nov 04 21:59:09 arch kernel: Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
Nov 04 21:59:09 arch kernel: perf_event_intel: PEBS disabled due to CPU errata
Nov 04 21:59:09 arch kernel: ... version: 2
Nov 04 21:59:09 arch kernel: ... bit width: 40
Nov 04 21:59:09 arch kernel: ... generic registers: 2
Nov 04 21:59:09 arch kernel: ... value mask: 000000ffffffffff
Nov 04 21:59:09 arch kernel: ... max period: 000000007fffffff
Nov 04 21:59:09 arch kernel: ... fixed-purpose events: 3
Nov 04 21:59:09 arch kernel: ... event mask: 0000000700000003
Nov 04 21:59:09 arch kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov 04 21:59:09 arch kernel: smpboot: Booting Node 0, Processors #1 #2 #3 OK
Nov 04 21:59:09 arch kernel: Brought up 4 CPUs
Nov 04 21:59:09 arch kernel: smpboot: Total of 4 processors activated (19206.35 BogoMIPS)
Nov 04 21:59:09 arch kernel: devtmpfs: initialized
Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fbb5000-0x7fbf7fff] (274432 bytes)
Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fd52000-0x7fd52fff] (4096 bytes)
Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fd55000-0x7fd56fff] (8192 bytes)
Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fd58000-0x7fd5bfff] (16384 bytes)
Nov 04 21:59:09 arch kernel: RTC time: 0:59:05, date: 11/05/13
Nov 04 21:59:09 arch kernel: NET: Registered protocol family 16
Nov 04 21:59:09 arch kernel: ACPI: bus type PCI registered
Nov 04 21:59:09 arch kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov 04 21:59:09 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-40] at [mem 0xe0000000-0xe40fffff] (base 0xe0000000)
Nov 04 21:59:09 arch kernel: PCI: not using MMCONFIG
Nov 04 21:59:09 arch kernel: PCI: Using configuration type 1 for base access
Nov 04 21:59:09 arch kernel: mtrr: your CPUs had inconsistent fixed MTRR settings
Nov 04 21:59:09 arch kernel: mtrr: your CPUs had inconsistent variable MTRR settings
Nov 04 21:59:09 arch kernel: mtrr: probably your BIOS does not setup all CPUs.
Nov 04 21:59:09 arch kernel: mtrr: corrected configuration.
Nov 04 21:59:09 arch kernel: bio: create slab <bio-0> at 0
Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(Module Device)
Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(Processor Device)
Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(Processor Aggregator Device)
Nov 04 21:59:09 arch kernel: ACPI: EC: Look up EC in DSDT
Nov 04 21:59:09 arch kernel: ACPI: Executed 1 blocks of module-level executable AML code
Nov 04 21:59:09 arch kernel: ACPI: SSDT 000000007fd56c10 002CC (v01 AMI IST 00000001 MSFT 03000001)
Nov 04 21:59:09 arch kernel: ACPI: Dynamic OEM Table Load:
Nov 04 21:59:09 arch kernel: ACPI: SSDT (null) 002CC (v01 AMI IST 00000001 MSFT 03000001)
Nov 04 21:59:09 arch kernel: ACPI: Interpreter enabled
Nov 04 21:59:09 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
Nov 04 21:59:09 arch kernel: ACPI: (supports S0 S1 S3 S4 S5)
Nov 04 21:59:09 arch kernel: ACPI: Using IOAPIC for interrupt routing
Nov 04 21:59:09 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-40] at [mem 0xe0000000-0xe40fffff] (base 0xe0000000)
Nov 04 21:59:09 arch kernel: PCI: MMCONFIG at [mem 0xe0000000-0xe40fffff] reserved in ACPI motherboard resources
Nov 04 21:59:09 arch kernel: PCI: MMCONFIG for 0000 [bus00-1f] at [mem 0xe0000000-0xe1ffffff] (base 0xe0000000) (size reduced!)
Nov 04 21:59:09 arch kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov 04 21:59:09 arch kernel: ACPI: No dock devices found.
Nov 04 21:59:09 arch kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov 04 21:59:09 arch kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Nov 04 21:59:09 arch kernel: acpi PNP0A08:00: Requesting ACPI _OSC control (0x1d)
Nov 04 21:59:09 arch kernel: acpi PNP0A08:00: ACPI _OSC control (0x1d) granted
Nov 04 21:59:09 arch kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-1f] only partially covers this bridge
Nov 04 21:59:09 arch kernel: PCI host bridge to bus 0000:00
Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [mem 0x80000000-0xffffffff]
Nov 04 21:59:09 arch kernel: pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: [8086:29c1] type 01 class 0x060400
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Nov 04 21:59:09 arch kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
Nov 04 21:59:09 arch kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xfb200000-0xfb203fff 64bit]
Nov 04 21:59:09 arch kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: System wakeup disabled by ACPI
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.0: reg 0x20: [io 0xf080-0xf09f]
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.1: reg 0x20: [io 0xf060-0xf07f]
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.1: System wakeup disabled by ACPI
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.2: reg 0x20: [io 0xf040-0xf05f]
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.2: System wakeup disabled by ACPI
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.3: reg 0x20: [io 0xf020-0xf03f]
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.3: System wakeup disabled by ACPI
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: reg 0x10: [mem 0xfb204000-0xfb2043ff]
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: System wakeup disabled by ACPI
Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: System wakeup disabled by ACPI
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: [8086:27b8] type 00 class 0x060100
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: address space collision: [io 0x0400-0x047f] conflicts with ACPI CPU throttle [??? 0x00000410-0x00000415 flags 0x80000000]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: quirk: [io 0x0500-0x053f] claimed by ICH6 GPIO
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0290 (mask 00ff)
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: [8086:27df] type 00 class 0x01018a
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x10: [io 0xf130-0xf137]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x14: [io 0xf120-0xf123]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x18: [io 0xf110-0xf117]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x1c: [io 0xf100-0xf103]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x20: [io 0xf0f0-0xf0ff]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: [8086:27c0] type 00 class 0x01018f
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf0e0-0xf0e7]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf0d0-0xf0d3]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf0c0-0xf0c7]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf0b0-0xf0b3]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf0a0-0xf0af]
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: PME# supported from D3hot
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: [10de:0421] type 00 class 0x030000
Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x10: [mem 0xfa000000-0xfaffffff]
Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x14: [mem 0xd0000000-0xdfffffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xf8000000-0xf9ffffff 64bit]
Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfb000000-0xfb01ffff pref]
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfb0fffff]
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: reg 0x10: [io 0xd000-0xd0ff]
Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: reg 0x18: [mem 0xfb120000-0xfb120fff 64bit]
Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: reg 0x30: [mem 0xfb100000-0xfb11ffff pref]
Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: supports D1 D2
Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: PME# supported from D1 D2 D3hot D3cold
Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xfb100000-0xfb1fffff]
Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: PCI bridge to [bus 04] (subtractive decode)
Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [mem 0x80000000-0xffffffff] (subtractive decode)
Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 10 11 12 14 15)
Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Nov 04 21:59:09 arch kernel: ACPI: Enabled 3 GPEs in block 00 to 1F
Nov 04 21:59:09 arch kernel: ACPI: \_SB_.PCI0: notify handler is installed
Nov 04 21:59:09 arch kernel: Found 1 acpi root devices
Nov 04 21:59:09 arch kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov 04 21:59:09 arch kernel: vgaarb: loaded
Nov 04 21:59:09 arch kernel: vgaarb: bridge control possible 0000:01:00.0
Nov 04 21:59:09 arch kernel: PCI: Using ACPI for IRQ routing
Nov 04 21:59:09 arch kernel: PCI: pci_cache_line_size set to 64 bytes
Nov 04 21:59:09 arch kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
Nov 04 21:59:09 arch kernel: e820: reserve RAM buffer [mem 0x7fbb5000-0x7fffffff]
Nov 04 21:59:09 arch kernel: e820: reserve RAM buffer [mem 0x7ff00000-0x7fffffff]
Nov 04 21:59:09 arch kernel: NetLabel: Initializing
Nov 04 21:59:09 arch kernel: NetLabel: domain hash size = 128
Nov 04 21:59:09 arch kernel: NetLabel: protocols = UNLABELED CIPSOv4
Nov 04 21:59:09 arch kernel: NetLabel: unlabeled traffic allowed by default
Nov 04 21:59:09 arch kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Nov 04 21:59:09 arch kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
Nov 04 21:59:09 arch kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
Nov 04 21:59:09 arch kernel: Switched to clocksource hpet
Nov 04 21:59:09 arch kernel: pnp: PnP ACPI init
Nov 04 21:59:09 arch kernel: ACPI: bus type PNP registered
Nov 04 21:59:09 arch kernel: system 00:00: [mem 0xfed14000-0xfed19fff] has been reserved
Nov 04 21:59:09 arch kernel: system 00:00: [mem 0xe0000000-0xe3ffffff] has been reserved
Nov 04 21:59:09 arch kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Nov 04 21:59:09 arch kernel: system 00:01: [io 0x0400-0x047f] could not be reserved
Nov 04 21:59:09 arch kernel: system 00:01: [io 0x1180-0x119f] has been reserved
Nov 04 21:59:09 arch kernel: system 00:01: [io 0x0500-0x053f] has been reserved
Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfec00000-0xfecfffff] could not be reserved
Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfee00000-0xfee0ffff] has been reserved
Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xffb00000-0xffcfffff] could not be reserved
Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfc800000-0xfc800fff] has been reserved
Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfed20000-0xfed7ffff] has been reserved
Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xffe00000-0xffffffff] has been reserved
Nov 04 21:59:09 arch kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
Nov 04 21:59:09 arch kernel: system 00:02: [io 0x0290-0x029f] has been reserved
Nov 04 21:59:09 arch kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 04 21:59:09 arch kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
Nov 04 21:59:09 arch kernel: pnp 00:04: [dma 2]
Nov 04 21:59:09 arch kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0700 (active)
Nov 04 21:59:09 arch kernel: pnp 00:05: [dma 0 disabled]
Nov 04 21:59:09 arch kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 04 21:59:09 arch kernel: pnp 00:06: [dma 4]
Nov 04 21:59:09 arch kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0200 (active)
Nov 04 21:59:09 arch kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 04 21:59:09 arch kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0800 (active)
Nov 04 21:59:09 arch kernel: system 00:09: [io 0x04d0-0x04d1] has been reserved
Nov 04 21:59:09 arch kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 04 21:59:09 arch kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov 04 21:59:09 arch kernel: pnp 00:0b: Plug and Play ACPI device, IDs PNP0103 (active)
Nov 04 21:59:09 arch kernel: pnp: PnP ACPI: found 12 devices
Nov 04 21:59:09 arch kernel: ACPI: bus type PNP unregistered
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 02] add_size 200000
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: BAR 13: [io 0x0400-0x047f] has bogus alignment
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0x80000000-0x801fffff]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0x80200000-0x803fffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: BAR 15: assigned [mem 0x80400000-0x805fffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x2000-0x2fff]
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfb0fffff]
Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x80000000-0x801fffff]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x80200000-0x803fffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xfb100000-0xfb1fffff]
Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0x80400000-0x805fffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: PCI bridge to [bus 04]
Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: setting latency timer to 64
Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 7 [mem 0x80000000-0xffffffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:01: resource 1 [mem 0xf8000000-0xfb0fffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci_bus 0000:02: resource 0 [io 0x2000-0x2fff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:02: resource 1 [mem 0x80000000-0x801fffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:02: resource 2 [mem 0x80200000-0x803fffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:03: resource 1 [mem 0xfb100000-0xfb1fffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:03: resource 2 [mem 0x80400000-0x805fffff 64bit pref]
Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 7 [mem 0x80000000-0xffffffff]
Nov 04 21:59:09 arch kernel: NET: Registered protocol family 2
Nov 04 21:59:09 arch kernel: TCP established hash table entries: 16384 (order: 6, 262144 bytes)
Nov 04 21:59:09 arch kernel: TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
Nov 04 21:59:09 arch kernel: TCP: Hash tables configured (established 16384 bind 16384)
Nov 04 21:59:09 arch kernel: TCP: reno registered
Nov 04 21:59:09 arch kernel: UDP hash table entries: 1024 (order: 3, 32768 bytes)
Nov 04 21:59:09 arch kernel: UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
Nov 04 21:59:09 arch kernel: NET: Registered protocol family 1
Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: EHCI: BIOS handoff failed (BIOS bug?) 01010001
Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: Boot video device
Nov 04 21:59:09 arch kernel: PCI: CLS 64 bytes, default 64
Nov 04 21:59:09 arch kernel: Unpacking initramfs...
Nov 04 21:59:09 arch kernel: Freeing initrd memory: 3000K (ffff880037a14000 - ffff880037d02000)
Nov 04 21:59:09 arch kernel: Scanning for low memory corruption every 60 seconds
Nov 04 21:59:09 arch kernel: audit: initializing netlink socket (disabled)
Nov 04 21:59:09 arch kernel: type=2000 audit(1383613146.559:1): initialized
Nov 04 21:59:09 arch kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov 04 21:59:09 arch kernel: zbud: loaded
Nov 04 21:59:09 arch kernel: VFS: Disk quotas dquot_6.5.2
Nov 04 21:59:09 arch kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov 04 21:59:09 arch kernel: msgmni has been set to 4001
Nov 04 21:59:09 arch kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov 04 21:59:09 arch kernel: io scheduler noop registered
Nov 04 21:59:09 arch kernel: io scheduler deadline registered
Nov 04 21:59:09 arch kernel: io scheduler cfq registered (default)
Nov 04 21:59:09 arch kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
Nov 04 21:59:09 arch kernel: pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov 04 21:59:09 arch kernel: pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov 04 21:59:09 arch kernel: pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov 04 21:59:09 arch kernel: pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
Nov 04 21:59:09 arch kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.0:pcie04: HPC vendor_id 8086 device_id 27d0 ss_vid 8086 ss_did 27d0
Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.0:pcie04: service driver pciehp loaded
Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.1:pcie04: HPC vendor_id 8086 device_id 27d2 ss_vid 8086 ss_did 27d2
Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.1:pcie04: service driver pciehp loaded
Nov 04 21:59:09 arch kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov 04 21:59:09 arch kernel: vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov 04 21:59:09 arch kernel: vesafb: scrolling: redraw
Nov 04 21:59:09 arch kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov 04 21:59:09 arch kernel: vesafb: framebuffer at 0xf9000000, mapped to 0xffffc90002400000, using 1216k, total 1216k
Nov 04 21:59:09 arch kernel: Console: switching to colour frame buffer device 80x30
Nov 04 21:59:09 arch kernel: fb0: VESA VGA frame buffer device
Nov 04 21:59:09 arch kernel: intel_idle: does not run on family 6 model 15
Nov 04 21:59:09 arch kernel: GHES: HEST is not enabled!
Nov 04 21:59:09 arch kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Nov 04 21:59:09 arch kernel: 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Nov 04 21:59:09 arch kernel: Linux agpgart interface v0.103
Nov 04 21:59:09 arch kernel: i8042: PNP: PS/2 Controller [PNP0f03:PS2M] at 0x60,0x64 irq 12
Nov 04 21:59:09 arch kernel: i8042: PNP: PS/2 controller doesn't have KBD irq; using default 1
Nov 04 21:59:09 arch kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Nov 04 21:59:09 arch kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Nov 04 21:59:09 arch kernel: mousedev: PS/2 mouse device common for all mice
Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: RTC can wake from S4
Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
Nov 04 21:59:09 arch kernel: cpuidle: using governor ladder
Nov 04 21:59:09 arch kernel: cpuidle: using governor menu
Nov 04 21:59:09 arch kernel: drop_monitor: Initializing network drop monitor service
Nov 04 21:59:09 arch kernel: TCP: cubic registered
Nov 04 21:59:09 arch kernel: NET: Registered protocol family 10
Nov 04 21:59:09 arch kernel: NET: Registered protocol family 17
Nov 04 21:59:09 arch kernel: Key type dns_resolver registered
Nov 04 21:59:09 arch kernel: PM: Hibernation image not present or could not be loaded.
Nov 04 21:59:09 arch kernel: registered taskstats version 1
Nov 04 21:59:09 arch kernel: Magic number: 5:843:960
Nov 04 21:59:09 arch kernel: memory memory11: hash matches
Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: setting system clock to 2013-11-05 00:59:07 UTC (1383613147)
Nov 04 21:59:09 arch kernel: Freeing unused kernel memory: 1140K (ffffffff818c9000 - ffffffff819e6000)
Nov 04 21:59:09 arch kernel: Write protecting the kernel read-only data: 8192k
Nov 04 21:59:09 arch kernel: Freeing unused kernel memory: 1084K (ffff8800014f1000 - ffff880001600000)
Nov 04 21:59:09 arch kernel: Freeing unused kernel memory: 352K (ffff8800017a8000 - ffff880001800000)
Nov 04 21:59:09 arch systemd-udevd[58]: starting version 208
Nov 04 21:59:09 arch kernel: Floppy drive(s): fd0 is 1.44M
Nov 04 21:59:09 arch kernel: SCSI subsystem initialized
Nov 04 21:59:09 arch kernel: ACPI: bus type USB registered
Nov 04 21:59:09 arch kernel: usbcore: registered new interface driver usbfs
Nov 04 21:59:09 arch kernel: usbcore: registered new interface driver hub
Nov 04 21:59:09 arch kernel: usbcore: registered new device driver usb
Nov 04 21:59:09 arch kernel: ACPI: bus type ATA registered
Nov 04 21:59:09 arch kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov 04 21:59:09 arch kernel: uhci_hcd: USB Universal Host Controller Interface driver
Nov 04 21:59:09 arch kernel: libata version 3.00 loaded.
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000f080
Nov 04 21:59:09 arch kernel: ehci-pci: EHCI PCI platform driver
Nov 04 21:59:09 arch kernel: hub 1-0:1.0: USB hub found
Nov 04 21:59:09 arch kernel: hub 1-0:1.0: 2 ports detected
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000f060
Nov 04 21:59:09 arch kernel: hub 2-0:1.0: USB hub found
Nov 04 21:59:09 arch kernel: hub 2-0:1.0: 2 ports detected
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000f040
Nov 04 21:59:09 arch kernel: FDC 0 is a post-1991 82077
Nov 04 21:59:09 arch kernel: hub 3-0:1.0: USB hub found
Nov 04 21:59:09 arch kernel: hub 3-0:1.0: 2 ports detected
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000f020
Nov 04 21:59:09 arch kernel: hub 4-0:1.0: USB hub found
Nov 04 21:59:09 arch kernel: hub 4-0:1.0: 2 ports detected
Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.1: version 2.13
Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.1: setting latency timer to 64
Nov 04 21:59:09 arch kernel: scsi0 : ata_piix
Nov 04 21:59:09 arch kernel: scsi1 : ata_piix
Nov 04 21:59:09 arch kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf0f0 irq 14
Nov 04 21:59:09 arch kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf0f8 irq 15
Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.2: MAP [
Nov 04 21:59:09 arch kernel: P0 P2 P1 P3 ]
Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
Nov 04 21:59:09 arch kernel: ata2: port disabled--ignoring
Nov 04 21:59:09 arch kernel: scsi2 : ata_piix
Nov 04 21:59:09 arch kernel: scsi3 : ata_piix
Nov 04 21:59:09 arch kernel: ata3: SATA max UDMA/133 cmd 0xf0e0 ctl 0xf0d0 bmdma 0xf0a0 irq 19
Nov 04 21:59:09 arch kernel: ata4: SATA max UDMA/133 cmd 0xf0c0 ctl 0xf0b0 bmdma 0xf0a8 irq 19
Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64
Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 5
Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: debug port 1
Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: irq 23, io mem 0xfb204000
Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
Nov 04 21:59:09 arch kernel: hub 5-0:1.0: USB hub found
Nov 04 21:59:09 arch kernel: hub 5-0:1.0: 8 ports detected
Nov 04 21:59:09 arch kernel: hub 1-0:1.0: USB hub found
Nov 04 21:59:09 arch kernel: hub 1-0:1.0: 2 ports detected
Nov 04 21:59:09 arch kernel: hub 2-0:1.0: USB hub found
Nov 04 21:59:09 arch kernel: hub 2-0:1.0: 2 ports detected
Nov 04 21:59:09 arch kernel: hub 3-0:1.0: USB hub found
Nov 04 21:59:09 arch kernel: hub 3-0:1.0: 2 ports detected
Nov 04 21:59:09 arch kernel: hub 4-0:1.0: USB hub found
Nov 04 21:59:09 arch kernel: hub 4-0:1.0: 2 ports detected
Nov 04 21:59:09 arch kernel: ata4.00: ATA-8: WDC WD10EZEX-00RKKA0, 80.00A80, max UDMA/133
Nov 04 21:59:09 arch kernel: ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Nov 04 21:59:09 arch kernel: ata4.00: configured for UDMA/133
Nov 04 21:59:09 arch kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD10EZEX-00R 80.0 PQ: 0 ANSI: 5
Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] 4096-byte physical blocks
Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Write Protect is off
Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 04 21:59:09 arch kernel: sda: sda1 sda2 sda3 sda4 sda5
Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Attached SCSI disk
Nov 04 21:59:09 arch kernel: usb 3-2: new full-speed USB device number 2 using uhci_hcd
Nov 04 21:59:09 arch kernel: tsc: Refined TSC clocksource calibration: 2399.950 MHz
Nov 04 21:59:09 arch kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Nov 04 21:59:09 arch systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Nov 04 21:59:09 arch systemd[1]: Set hostname to <arch>.
Nov 04 21:59:09 arch kernel: Switched to clocksource tsc
Nov 04 21:59:09 arch systemd[1]: Failed to load default target: No such file or directory
Nov 04 21:59:09 arch systemd[1]: Trying to load rescue target...
Nov 04 21:59:09 arch systemd[1]: Starting Encrypted Volumes.
Nov 04 21:59:09 arch systemd[1]: Reached target Encrypted Volumes.
Nov 04 21:59:09 arch systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
Nov 04 21:59:09 arch systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Nov 04 21:59:09 arch systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
Nov 04 21:59:09 arch systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Nov 04 21:59:09 arch systemd[1]: Starting Journal Socket.
Nov 04 21:59:09 arch systemd[1]: Listening on Journal Socket.
Nov 04 21:59:09 arch systemd[1]: Starting Setup Virtual Console...
Nov 04 21:59:09 arch systemd[1]: Starting Apply Kernel Variables...
Nov 04 21:59:09 arch systemd[1]: Started Set Up Additional Binary Formats.
Nov 04 21:59:09 arch systemd[1]: Started Load Kernel Modules.
Nov 04 21:59:09 arch systemd[1]: Mounted FUSE Control File System.
Nov 04 21:59:09 arch systemd[1]: Mounting POSIX Message Queue File System...
Nov 04 21:59:09 arch systemd[1]: Mounting Huge Pages File System...
Nov 04 21:59:09 arch systemd[1]: Mounting Configuration File System...
Nov 04 21:59:09 arch systemd[1]: Starting Journal Service...
Nov 04 21:59:09 arch systemd[1]: Started Journal Service.
Nov 04 21:59:09 arch systemd-journal[120]: Journal started
-- Subject: The Journal has been started
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The system journal process has been starting up, opened the journal
-- files for writing and is now ready to process requests.
Nov 04 21:59:09 arch systemd[1]: Starting Create list of required static device nodes for the current kernel...
-- Subject: Unit kmod-static-nodes.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit kmod-static-nodes.service has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Starting udev Kernel Socket.
-- Subject: Unit systemd-udevd-kernel.socket has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udevd-kernel.socket has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Listening on udev Kernel Socket.
-- Subject: Unit systemd-udevd-kernel.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udevd-kernel.socket has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Starting udev Control Socket.
-- Subject: Unit systemd-udevd-control.socket has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udevd-control.socket has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Listening on udev Control Socket.
-- Subject: Unit systemd-udevd-control.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udevd-control.socket has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Starting udev Coldplug all Devices...
-- Subject: Unit systemd-udev-trigger.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udev-trigger.service has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Mounting Debug File System...
-- Subject: Unit sys-kernel-debug.mount has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-kernel-debug.mount has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Expecting device dev-sda4.device...
-- Subject: Unit dev-sda4.device has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-sda4.device has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Expecting device dev-disk-by\x2duuid-32d1daa9\x2daa59\x2d4ac1\x2da592\x2d23aa1ae655c5.device...
-- Subject: Unit dev-disk-by\x2duuid-32d1daa9\x2daa59\x2d4ac1\x2da592\x2d23aa1ae655c5.device has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-disk-by\x2duuid-32d1daa9\x2daa59\x2d4ac1\x2da592\x2d23aa1ae655c5.device has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Mounting Temporary Directory...
-- Subject: Unit tmp.mount has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit tmp.mount has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Started File System Check on Root Device.
-- Subject: Unit systemd-fsck-root.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-fsck-root.service has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Starting Remount Root and Kernel File Systems...
-- Subject: Unit systemd-remount-fs.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-remount-fs.service has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Starting Root Slice.
-- Subject: Unit -.slice has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit -.slice has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Created slice Root Slice.
-- Subject: Unit -.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit -.slice has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Starting System Slice.
-- Subject: Unit system.slice has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit system.slice has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Created slice System Slice.
-- Subject: Unit system.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit system.slice has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Expecting device dev-disk-by\x2duuid-bdf255b1\x2d60c6\x2d4714\x2d8dc8\x2d5bd057b49aaa.device...
-- Subject: Unit dev-disk-by\x2duuid-bdf255b1\x2d60c6\x2d4714\x2d8dc8\x2d5bd057b49aaa.device has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-disk-by\x2duuid-bdf255b1\x2d60c6\x2d4714\x2d8dc8\x2d5bd057b49aaa.device has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Started Apply Kernel Variables.
-- Subject: Unit systemd-sysctl.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-sysctl.service has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Mounted POSIX Message Queue File System.
-- Subject: Unit dev-mqueue.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-mqueue.mount has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Mounted Huge Pages File System.
-- Subject: Unit dev-hugepages.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-hugepages.mount has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Mounted Configuration File System.
-- Subject: Unit sys-kernel-config.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-kernel-config.mount has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Mounted Debug File System.
-- Subject: Unit sys-kernel-debug.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-kernel-debug.mount has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Mounted Temporary Directory.
-- Subject: Unit tmp.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit tmp.mount has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Started Create list of required static device nodes for the current kernel.
-- Subject: Unit kmod-static-nodes.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit kmod-static-nodes.service has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Started udev Coldplug all Devices.
-- Subject: Unit systemd-udev-trigger.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udev-trigger.service has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Starting Create static device nodes in /dev...
-- Subject: Unit systemd-tmpfiles-setup-dev.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-setup-dev.service has begun starting up.
Nov 04 21:59:09 arch systemd[1]: Started Remount Root and Kernel File Systems.
-- Subject: Unit systemd-remount-fs.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-remount-fs.service has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Starting Load/Save Random Seed...
-- Subject: Unit systemd-random-seed.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-random-seed.service has begun starting up.
Nov 04 21:59:09 arch kernel: EXT4-fs (sda1): re-mounted. Opts: data=ordered
Nov 04 21:59:09 arch systemd[1]: Started Load/Save Random Seed.
-- Subject: Unit systemd-random-seed.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-random-seed.service has finished starting up.
-- The start-up result is done.
Nov 04 21:59:09 arch systemd[1]: Started Create static device nodes in /dev.
-- Subject: Unit systemd-tmpfiles-setup-dev.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mail

Interface Manager Material Transaction can not be activated

Hi hussein,
One of the interface managers for INVENTORY module can not be activated.
I tried to activated it using:
Navigation: INVENTORY > Setup >Transactions > Interface Managers > Material Transactions
Goto Tools > Launch Manager > Submit Conc. program "Process Transaction Inferface"
Then after the job is completed, I checked the manager but it is still "inactive" status. :(
Its log says:
+---------------------------------------------------------------------------+
Inventory: Version : 11.5.0 - Development
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
INCTCM module: Process transaction interface
+---------------------------------------------------------------------------+
Current system time is 07-DEC-2009 14:57:19
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
Executing request completion options...
Output is not being printed because:
The print option has been disabled for this report.
+------------- 1) PRINT -------------+
+--------------------------------------+
Finished executing request completion options.
+---------------------------------------------------------------------------+
Concurrent request completed successfully
Current system time is 07-DEC-2009 14:57:21
+---------------------------------------------------------------------------+Please help.....
Thanks a lot
msk

Hi yxes;
Navigation: INVENTORY > Setup >Transactions > Interface Managers > Material Transactions
Goto Tools > Launch Manager > Submit Conc. program "Process Transaction Inferface" Related Cm is Up? If yes please follow below and see its helpful:
The print option has been disabled for this report.
Regard
Helios

Creation of Logical Standby Database Using RMAN ACTIVE DATABASE COMMAND

Hi All,
I am in confusion how to create logical standby database from primary database using rman active database command.
What i did:-
Create primary database on machine 1 on RHEL 5 with Oracle 11gR2
Create standby database on machine 2 on RHEL 5 With Oracle 11gR2 from primary using RMAN active database command
Trying to create logical standby database on machine 3 on RHEL 5 with Oracle 11gR2 using RMAN active database command from primary.
The point which confuse me is to start the logical standby in nomount mode on machine 3 with which pfile like i create the pfile for standby database do i need to create the pfile for logical standby db.
I done the creation of logical standby database by converting physical standby to logical standby database
I am following the below mentioned doc for the same:
Creating a physical and a logical standby database in a DR environment | Chen Guang&#039;s Blog
Kindly guide me how to work over the same or please provide me the steps of the same.
Thanks in advance.

Thanks for your reply
I already started the logical standby database with pfile in nomount mode. And successfully completed the duplication of database. by mentioning the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter.
But i am not able to receive the logs on the above mentioned blog i run the sql command to check the logs but getting "no rows selected"
My primary database pfile is:
pc01prmy.__db_cache_size=83886080
pc01prmy.__java_pool_size=12582912
pc01prmy.__large_pool_size=4194304
pc01prmy.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01prmy.__pga_aggregate_target=79691776
pc01prmy.__sga_target=239075328
pc01prmy.__shared_io_pool_size=0
pc01prmy.__shared_pool_size=134217728
pc01prmy.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01prmy/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01PRMY/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01PRMY/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.fal_client='PC01PRMY'
*.fal_server='PC01SBY'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='SERVICE=pc01sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pc01sby'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='DEFER'
*.log_archive_dest_state_3='DEFER'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
My logical standby pfile is:-
pc01ls.__db_cache_size=92274688
pc01ls.__java_pool_size=12582912
pc01ls.__large_pool_size=4194304
pc01ls.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01ls.__pga_aggregate_target=79691776
pc01ls.__sga_target=239075328
pc01ls.__shared_io_pool_size=0
pc01ls.__shared_pool_size=125829120
pc01ls.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01ls/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01LS/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01LS/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_unique_name='pc01ls'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='LOCATION=/u01/app/oracle/flash_recovery_area/PC01LS/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
Kindly advice over the same

Interface with no mapping could not be activated

Hello,
i want to transform an invoic01 Idoc into a xml-file. Ther is no format transformation, I only want to get the xml file.
With XI 2.0 I only had to define no message program. Now I wanted to do the same in XI 3.0 but I get an error message that says that there is no mapping-program. I don't want to have one.
What do I have to do?
TIA
Volker

Hi,
I found out, how to do it.
Don't define an interfacemapping in your repository.
In your directory define a interface determination without interfacemapping.
You can use a simple string as datatype in your repository, in my case, for the inbound messageinterface.
Thanks for your help
Volker

Can't switch standby logfiles to status=active

Hi DBA's
I'm trying to create logical standby on 10.2 on fedora 6 on manual http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
I can't create proper working standby redo logs.
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4
('/u01/app/oracle/oradata/ORCL/onlinelog/log4a.log',
'/u01/app/oracle/flash_recovery_area/ORCL/onlinelog/log4b.log') SIZE 50M;
then create the rest of standby redos and switch logfile:
ALTER SYSTEM SWITCH LOGFILE;
when:
SQL> SELECT GROUP#,THREAD#,SEQUENCE#,ARCHIVED,STATUS FROM V$STANDBY_LOG;
GROUP# THREAD# SEQUENCE# ARC STATUS
4 0 0 YES UNASSIGNED
5 0 0 YES UNASSIGNED
6 0 0 YES UNASSIGNED
What to do?
Edited by: val75 on Jun 21, 2009 11:08 PM

try switch log at primay
please try to run this Command and then open the primary database.
alter database set standby database to maximize performance;
alter database open;

Active/Standby failover automatic primary active

I have 2 ASAs 5510 with same physical configuration and running ok with active/standby failover mode. Like we have PREEMPT command in active/active failover to get back primary active after its been rebooted from failed mode. This command makes primary back to active and makes secondary firewall standby automatically.
Need help to know any such command for active/standby failover for automatic primary active. Currently we have to use command FAILOVER ACTIVE on primary to make it active manually.

Remember, failover in ASA works differently than HSRP. ASA does NOT use
HSRP. Furthermore, there is NO HSRP ip address in ASA either. You are
talking about two different technologies.
Think of it this way. HSRP technology works very similar to VRRP and
Juniper NSRP. All of these technologies use virtual IP address. If you
have two devices, you will have an Virtual IP address, in addition
to the physical ip addresses of the two devices. ASA does not use the
extra VIP.

GT70 question (Super Raid card)

Hello All!
Quick question, I'm interested in the new GT70 2PE-1069NL (1x 128GB msata SSD) or the GT70 2PE-1063NL (2x 128GB msata SSD).
Now, I'm wondering if the 1069 already features a Super RAID 2 expansion bay, so I can add my own msata SSD if I want to.
The difference between the two is €200,- and I'm wondering if it's worth the RAID 0 setup and the 4GB RAM extra. The 1063 also features a Blu ray player, but I won't use that.
Also, what msata SSD is in the 1069 and 1063?
Thanks in advance!

Quote from: Ragaroah on 02-April-14, 05:26:24
Hello All!
Quick question, I'm interested in the new GT70 2PE-1069NL (1x 128GB msata SSD) or the GT70 2PE-1063NL (2x 128GB msata SSD).
Now, I'm wondering if the 1069 already features a Super RAID 2 expansion bay, so I can add my own msata SSD if I want to.
The difference between the two is €200,- and I'm wondering if it's worth the RAID 0 setup and the 4GB RAM extra. The 1063 also features a Blu ray player, but I won't use that.
Also, what msata SSD is in the 1069 and 1063?
Thanks in advance!
Most likely they BOTH have the mSATA SuperRaid2 card.
For the €200, I would go for it. 4 GB more RAM, another 128 GB SSD, and a blue ray player to me makes it worth it.
No idea regarding what SSD or chipset it uses. It can vary from notebook to notebook since they will (most likely, I don't know this for sure...just guessing) probably buy whatever they can get for the cheapest.
Most likely it will be a SF2281 based card though. Atleast, that's my guess.

Does Standby mean nothing is active?

If you've got your web browser open to check for emails on hotmail or whatever ...and you put the PB into Standby ... does it continue to check ... and do other apps continue to work ... or does Standby sort of put everything into a sleep or hybernation until you "wake it."
Thanks

I often access my device from my desktop computer to copy files to it while it is in standby, and the WiFi is turned on.

SUP failed over manually, voice service failed after FAILOVER, started accessing old voice vlan which was removed from config

Hey guys,
I am pretty sure, my subject is kinda confusing. Sorry about that. Here is what happened.
1. 4510r with Supervisor V 1000BaseX, switched over to standby Sup, then reseated Active SUP, once reseat complete, switched again to get the reseated SUP up and running as Active SUP.
2. a simple maintenance which was supposed to cause no outage and it did not cause any outage as well.
3. however, what i did not notice was, even though the voice vlan was configured to access 2353, they were accessing vlan 453.
4. the change was made 2 weeks prior to this maintenance where voice vlans were previously accessing 453 and they were all changed to access 2353. configs were saved.
5. however, after the maintenance, the running config showed that they were acessing 2353 but when checking the mac address on the interface, it was seen accessing 453.
6. the fix was to remove the config and re add it , that fixed it.
Has anyone else experienced the issue ? What really happened there ?
software version: Version 15.0(2)SG5
#sh module
Chassis Type : WS-C4510R
Power consumed by backplane : 40 Watts
Mod Ports Card Type Model
---+-----+--------------------------------------+------------------+-----------
1 2 Supervisor V 1000BaseX (GBIC) WS-X4516
2 2 Supervisor V 1000BaseX (GBIC) WS-X4516
3 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
5 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
6 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
7 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
8 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
9 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V

configs were saved many times prior to the maintenance. i did a " write mem ".

Prevent LBFO Primary/Standby fallback

Hi All,
I have a client requirement to implement network redundancy on a Windows Server 2012 R2 platform. So enter two switches, firewalls, routers etc.
As part of this I have set up an LBFO team on NIC 1 & 2.
The client has since informed me that they have (in the past) had flakey inter-site links which resulted in the NIC team flapping between the Primary and Standby NIC as the primary network interface went up and down. Consequently, one of the tests that
I need to implement and pass is that if the active primary interface fails, the standby picks up the active role until such a time as the secondary interface fails rather than swapping back to the primary interface when the connection is restored
TIA
Jason

The best way to avoid this problem with Active/Standby is to not use it. Generally Active/Active mode is better than Active/Standby.
As you've noticed, Active/Standby mode forces an additional failover event:
An active NIC goes down, so there is a failover to the standby NIC.
The previously-active NIC is restored, so there is a failover from the standby NIC back to the newly-restored NIC.
This additional failover is by design. The design of Active/Standby is to designate a standby NIC, and the team tries to keep that NIC on standby as much as possible.
Because of this additional failover, Active/Active mode actually gives you better fault-tolerance than Active/Standby. And of course, Active/Active also makes better use of your available bandwidth, since you get to use the bandwidth of the redundant
NIC when there is no fault. Finally, note that Active/Standby does not have any advantage in failover latency or "effectiveness"; the failover performed by Active/Active is just the same as that performed in Active/Standby.
Therefore, I actually reccomend that Active/Active is your configuration of first resort. Active/Active is better or equal to Active/Standby in most respects. (Exception: If you have a configuration where one NIC
really is worse than the others, e.g., it has a lower link speed, then Active/Standby may be appropriate.)

Gig 1/1 interface on a standby Sup 2 card active?

Similar Messages

Maybe you are looking for