CX Module failed after reload

Hi there!
I do know if it is some kind of bug, but all the time after reload the CX module all things stop work, regardless of what form do I reset the module.
I already tried to acccess the module and reload, tried to stop services with "services stop" command and after that "reload", tried to shutdown using ASA commands and reload it from ASA... everytime I reload when the module come back all services start perfectly, like example below:
spcx02>show services status
============================================================
Process           | PID   | Up    | Up Time
============================================================
AD Interface      | 6284  | True  | 05:03:03
Message Nameserver| 6022  | True  | 05:03:59
HTTP Auth Daemon  | 6094  | True  | 05:03:58
PDTS              | 6073  | True  | 05:03:59
HTTP Inspector    | 6193  | True  | 05:03:37
HTTP Server       | 5972  | True  | 05:03:59
Data Plane        | 6270  | True  | 05:03:06
Management Plane  | 6115  | True  | 05:03:45
HPM Monitor       | 6289  | True  | 05:03:03
Updater           | 6399  | True  | 05:02:52
Card Manager      | 5930  | True  | 05:03:59
ARP Daemon        | 6089  | True  | 05:03:58
Event Server      | 6133  | True  | 05:03:41
TLS Proxy         | 6204  | True  | 05:03:37
============================================================
spcx02>show ver
Cisco ASA CX Platform 9.1.2 (42)
Cisco Prime Security Manager 9.1.2 (42) for spcx02 firewall
spcx02>
I even can access the GUI using my browser, but all athentication with CDA or AD that before boot was working correctly show up the error:
"Connection failed with error: Could not connect to virtual directory interface."
Everytime I reload I must reinstall the entire module and reconfigure everything. Anyone know if this is a bug that crashes the database or something like this?
Regards,
Rodrigo Alves

Ah, I forgot to write down that after reload the module and it come back it stop all traffic passing through the firewall and I must remove the policy-map configuration:
policy-map global_policy
class inspection_default
  inspect dns preset_dns_map
  inspect ftp
  inspect rsh
  inspect rtsp
  inspect sqlnet
  inspect sunrpc
  inspect xdmcp
  inspect sip 
  inspect netbios
  inspect tftp
  inspect ip-options
  inspect icmp
  inspect h323 h225
  inspect h323 ras
  inspect skinny 
class class-default
  cxsc fail-open auth-proxy

Similar Messages

  • Loading Modules [FAIL] after updating to kernel 2.6.39

    During startup, I see that the Loading Modules part fails. It was doing just fine prior to the update. I fear that some modules are not loaded. So I want to know:
    (1) How to fix this
    (2) How to determine which module failed
    Thanks.

    I get the same problem at boot time (see a FAIL while loading modules) however,
    modprobe -av "list of modules"
    reports no problems. The list of modules I used is the same as in rc.conf in the MODULES directive, as shown below
    MODULES=(ac battery button processor thermal video cdrom intel-agp intel-gtt tpm_bios tpm tpm_tis tpm_tis dcdbas i2c-i801 i2c-core evdev joydev pcspkr psmouse serio_raw sparse-keymap memstick r592 mmc_core sdhci sdhci-pci pci_hotplug shpchp dell-laptop dell-wmi wmi nvidia iTCO_vendor_support iTCO_wdt crc-itu-t snd-hwdep snd snd-page-alloc snd-pcm snd-timer snd-hda-codec snd-hda-intel soundcore scsi_mod ata_piix libphy tg3 mac80211 rfkill iwl3945 iwl-legacy cfg80211 usbcore ehci-hcd uhci-hcd option usbserial usb_wwan firewire-core firewire-ohci sd_mod sr_mod st sg)
    Loading modules automatically was disabled in rc.conf; thus, these modules should be the only ones being loaded at boot time.
    Looked at syslog.log but found no issues. Here is a copy of kernel.log for reference:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Initializing cgroup subsys cpuset
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Initializing cgroup subsys cpu
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Linux version 2.6.39-ARCH (tobias@T-POWA-LX) (gcc version 4.6.0 20110603 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Jun 6 22:37:55 CEST 2011
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/82c10fe2-3a79-4aec-ad18-0a94e2adba10 ro
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-provided physical RAM map:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000bfe84c00 (usable)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000bfe84c00 - 00000000c0000000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000fed18000 - 00000000fed1c000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000feda0000 - 00000000feda6000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] NX (Execute Disable) protection: active
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMI 2.4 present.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMI: Dell Inc. Precision M6300 / , BIOS A08 02/28/2008
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] No AGP bridge found
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] last_pfn = 0x140000 max_arch_pfn = 0x400000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] MTRR default type: uncachable
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] MTRR fixed ranges enabled:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 00000-9FFFF write-back
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] A0000-BFFFF uncachable
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] C0000-CFFFF write-protect
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] D0000-EFFFF uncachable
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] F0000-FFFFF write-protect
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] MTRR variable ranges enabled:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0 base 000000000 mask F80000000 write-back
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 1 base 080000000 mask FC0000000 write-back
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 2 base 100000000 mask FC0000000 write-back
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 3 base 0BFF00000 mask FFFF00000 uncachable
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 4 disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 5 disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 6 disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 7 disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] e820 update range: 00000000bff00000 - 0000000100000000 (usable) ==> (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] last_pfn = 0xbfe84 max_arch_pfn = 0x400000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] initial memory mapped : 0 - 20000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] init_memory_mapping: 0000000000000000-00000000bfe84000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0000000000 - 00bfe00000 page 2M
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 00bfe00000 - 00bfe84000 page 4k
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] kernel direct mapping tables up to bfe84000 @ bfe7f000-bfe84000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] init_memory_mapping: 0000000100000000-0000000140000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0100000000 - 0140000000 page 2M
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] kernel direct mapping tables up to 140000000 @ 13fffa000-140000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] RAMDISK: 37e4a000 - 37ff0000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: RSDP 00000000000fbb60 00024 (v02 DELL )
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: XSDT 00000000bfe86600 00064 (v01 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: FACP 00000000bfe8649c 000F4 (v04 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: DSDT 00000000bfe86c00 05718 (v02 INT430 SYSFexxx 00001001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: FACS 00000000bfe95400 00040
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: HPET 00000000bfe86700 00038 (v01 DELL M08 00000001 ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: APIC 00000000bfe86800 00068 (v01 DELL M08 27D8021C ASL 00000047)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: ASF! 00000000bfe86400 0007E (v32 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: MCFG 00000000bfe867c0 0003E (v16 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: TCPA 00000000bfe86b00 00032 (v01 00000000 ASL 00000000)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: SLIC 00000000bfe8689c 00176 (v01 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: SSDT 00000000bfe84d7e 004CC (v01 PmRef CpuPm 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] No NUMA configuration found
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Faking a node at 0000000000000000-0000000140000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] NUMA: Using 63 for the hash shift.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Initmem setup node 0 0000000000000000-0000000140000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] NODE_DATA [000000013fffb000 - 000000013fffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] [ffffea0000000000-ffffea00045fffff] PMD -> [ffff88013b600000-ffff88013edfffff] on node 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Zone PFN ranges:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA 0x00000010 -> 0x00001000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA32 0x00001000 -> 0x00100000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Normal 0x00100000 -> 0x00140000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Movable zone start PFN for each node
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] early_node_map[3] active PFN ranges
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0: 0x00000010 -> 0x0000009f
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0: 0x00000100 -> 0x000bfe84
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0: 0x00100000 -> 0x00140000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] On node 0 totalpages: 1048083
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA zone: 56 pages used for memmap
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA zone: 5 pages reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA zone: 3922 pages, LIFO batch:0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA32 zone: 14280 pages used for memmap
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA32 zone: 767676 pages, LIFO batch:31
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Normal zone: 3584 pages used for memmap
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Normal zone: 258560 pages, LIFO batch:31
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: PM-Timer IO Port: 0x1008
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: IRQ0 used by override.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: IRQ2 used by override.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: IRQ9 used by override.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Using ACPI (MADT) for SMP configuration information
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] nr_irqs_gsi: 40
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000bfe84000 - 00000000bfe85000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000bfe85000 - 00000000c0000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000c0000000 - 00000000f8000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000f8000000 - 00000000fc000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fc000000 - 00000000fec00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 00000000fec10000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fec10000 - 00000000fed18000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fed18000 - 00000000fed1c000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fed20000 - 00000000fed90000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fed90000 - 00000000feda0000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000feda0000 - 00000000feda6000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000feda6000 - 00000000fee00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee10000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fee10000 - 00000000ffe00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000ffe00000 - 0000000100000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Allocating PCI resources starting at c0000000 (gap: c0000000:38000000)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Booting paravirtualized kernel on bare hardware
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:2 nr_node_ids:1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88013fc00000 s83136 r8192 d23360 u1048576
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] pcpu-alloc: s83136 r8192 d23360 u1048576 alloc=1*2097152
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] pcpu-alloc: [0] 0 1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1030158
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Policy zone: Normal
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Kernel command line: root=/dev/disk/by-uuid/82c10fe2-3a79-4aec-ad18-0a94e2adba10 ro
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Checking aperture...
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] No AGP bridge found
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Memory: 4057320k/5242880k available (4022k kernel code, 1050548k absent, 135012k reserved, 3332k data, 724k init)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Preemptable hierarchical RCU implementation.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] RCU-based detection of stalled CPUs is disabled.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Verbose stalled-CPUs detection is disabled.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] NR_IRQS:2304
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Extended CMOS year: 2000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Console: colour VGA+ 80x25
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] console [tty0] enabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] allocated 33554432 bytes of page_cgroup
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] hpet clockevent registered
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Fast TSC calibration using PIT
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Detected 2793.013 MHz processor.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.003337] Calibrating delay loop (skipped), value calculated using timer frequency.. 5588.77 BogoMIPS (lpj=9310043)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.003503] pid_max: default: 32768 minimum: 301
    Jun 13 04:03:43 cry-workstation kernel: [ 0.003677] Security Framework initialized
    Jun 13 04:03:43 cry-workstation kernel: [ 0.003763] AppArmor: AppArmor disabled by boot time parameter
    Jun 13 04:03:43 cry-workstation kernel: [ 0.006821] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.009196] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.010435] Mount-cache hash table entries: 256
    Jun 13 04:03:43 cry-workstation kernel: [ 0.010889] Initializing cgroup subsys ns
    Jun 13 04:03:43 cry-workstation kernel: [ 0.010975] ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011075] Initializing cgroup subsys cpuacct
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011182] Initializing cgroup subsys memory
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011279] Initializing cgroup subsys devices
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011362] Initializing cgroup subsys freezer
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011444] Initializing cgroup subsys net_cls
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011527] Initializing cgroup subsys blkio
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011659] CPU: Physical Processor ID: 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011741] CPU: Processor Core ID: 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011823] mce: CPU supports 6 MCE banks
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011912] CPU0: Thermal monitoring enabled (TM2)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011997] using mwait in idle threads.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.013001] ACPI: Core revision 20110316
    Jun 13 04:03:43 cry-workstation kernel: [ 0.016678] ftrace: allocating 15966 entries in 63 pages
    Jun 13 04:03:43 cry-workstation kernel: [ 0.020045] Setting APIC routing to flat
    Jun 13 04:03:43 cry-workstation kernel: [ 0.020498] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.055697] CPU0: Intel(R) Core(TM)2 Extreme CPU X7900 @ 2.80GHz stepping 0b
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] Performance Events: PEBS fmt0+, Core2 events, Intel PMU driver.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] PEBS disabled due to CPU errata.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... version: 2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... bit width: 40
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... generic registers: 2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... value mask: 000000ffffffffff
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... max period: 000000007fffffff
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... fixed-purpose events: 3
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... event mask: 0000000700000003
    Jun 13 04:03:43 cry-workstation kernel: [ 0.073433] NMI watchdog enabled, takes one hw-pmu counter.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.100004] Booting Node 0, Processors #1 Ok.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.100152] smpboot cpu 1: start_ip = 9a000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.196685] NMI watchdog enabled, takes one hw-pmu counter.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.203324] Brought up 2 CPUs
    Jun 13 04:03:43 cry-workstation kernel: [ 0.203406] Total of 2 processors activated (11176.50 BogoMIPS).
    Jun 13 04:03:43 cry-workstation kernel: [ 0.204478] devtmpfs: initialized
    Jun 13 04:03:43 cry-workstation kernel: [ 0.204478] print_constraints: dummy:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.204478] NET: Registered protocol family 16
    Jun 13 04:03:43 cry-workstation kernel: [ 0.204478] ACPI: bus type pci registered
    Jun 13 04:03:43 cry-workstation kernel: [ 0.206759] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.206859] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    Jun 13 04:03:43 cry-workstation kernel: [ 0.213476] PCI: Using configuration type 1 for base access
    Jun 13 04:03:43 cry-workstation kernel: [ 0.213565] dmi type 0xB1 record - unknown flag
    Jun 13 04:03:43 cry-workstation kernel: [ 0.213985] bio: create slab <bio-0> at 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.214148] ACPI: EC: Look up EC in DSDT
    Jun 13 04:03:43 cry-workstation kernel: [ 0.218377] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Jun 13 04:03:43 cry-workstation kernel: [ 0.222494] ACPI: SSDT 00000000bfe95480 00043 (v01 LMPWR DELLLOM 00001001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.222889] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.223102] ACPI: SSDT (null) 00043 (v01 LMPWR DELLLOM 00001001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.223492] ACPI: SSDT 00000000bfe858b4 002C8 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.223903] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.224115] ACPI: SSDT (null) 002C8 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.224424] ACPI: SSDT 00000000bfe8524a 005E5 (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.224825] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.226655] ACPI: SSDT (null) 005E5 (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.227020] ACPI: SSDT 00000000bfe85b7c 000C4 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.227430] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.227643] ACPI: SSDT (null) 000C4 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.227929] ACPI: SSDT 00000000bfe8582f 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.228333] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.228546] ACPI: SSDT (null) 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.228898] ACPI: Interpreter enabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.228980] ACPI: (supports S0 S3 S4 S5)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.229333] ACPI: Using IOAPIC for interrupt routing
    Jun 13 04:03:43 cry-workstation kernel: [ 0.297804] ACPI: ACPI Dock Station Driver: 1 docks/bays found
    Jun 13 04:03:43 cry-workstation kernel: [ 0.297889] HEST: Table not found.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.297971] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Jun 13 04:03:43 cry-workstation kernel: [ 0.304959] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318603] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318689] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318774] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318872] pci_root PNP0A03:00: host bridge window [mem 0x000d0000-0x000dffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318969] pci_root PNP0A03:00: host bridge window [mem 0xc0000000-0xf7ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319065] pci_root PNP0A03:00: host bridge window [mem 0xfc000000-0xfebfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319162] pci_root PNP0A03:00: host bridge window [mem 0xfec10000-0xfecfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319259] pci_root PNP0A03:00: host bridge window [mem 0xfed1c000-0xfed1ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319356] pci_root PNP0A03:00: host bridge window [mem 0xfed90000-0xfed9ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319453] pci_root PNP0A03:00: host bridge window [mem 0xfed40000-0xfed44fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319549] pci_root PNP0A03:00: host bridge window [mem 0xfeda7000-0xfedfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319646] pci_root PNP0A03:00: host bridge window [mem 0xfee10000-0xff9fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319743] pci_root PNP0A03:00: host bridge window [mem 0xffc00000-0xffdfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319840] pci_root PNP0A03:00: host bridge window [mem 0x140000000-0x337ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319948] pci 0000:00:00.0: [8086:2a00] type 0 class 0x000600
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319995] pci 0000:00:01.0: [8086:2a01] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320025] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320028] pci 0000:00:01.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320078] pci 0000:00:1a.0: [8086:2834] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320134] pci 0000:00:1a.0: reg 20: [io 0x6f20-0x6f3f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320172] pci 0000:00:1a.1: [8086:2835] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320227] pci 0000:00:1a.1: reg 20: [io 0x6f00-0x6f1f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320280] pci 0000:00:1a.7: [8086:283a] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320303] pci 0000:00:1a.7: reg 10: [mem 0xfed1c400-0xfed1c7ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320390] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320395] pci 0000:00:1a.7: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320424] pci 0000:00:1b.0: [8086:284b] type 0 class 0x000403
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320446] pci 0000:00:1b.0: reg 10: [mem 0xf6ffc000-0xf6ffffff 64bit]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320527] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320531] pci 0000:00:1b.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320558] pci 0000:00:1c.0: [8086:283f] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320642] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320646] pci 0000:00:1c.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320676] pci 0000:00:1c.1: [8086:2841] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320760] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320764] pci 0000:00:1c.1: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320796] pci 0000:00:1c.3: [8086:2845] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320879] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320883] pci 0000:00:1c.3: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320915] pci 0000:00:1c.5: [8086:2849] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320999] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321003] pci 0000:00:1c.5: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321031] pci 0000:00:1d.0: [8086:2830] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321087] pci 0000:00:1d.0: reg 20: [io 0x6f80-0x6f9f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321125] pci 0000:00:1d.1: [8086:2831] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321180] pci 0000:00:1d.1: reg 20: [io 0x6f60-0x6f7f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321218] pci 0000:00:1d.2: [8086:2832] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321273] pci 0000:00:1d.2: reg 20: [io 0x6f40-0x6f5f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321326] pci 0000:00:1d.7: [8086:2836] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321349] pci 0000:00:1d.7: reg 10: [mem 0xfed1c000-0xfed1c3ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321436] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321441] pci 0000:00:1d.7: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321463] pci 0000:00:1e.0: [8086:2448] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321547] pci 0000:00:1f.0: [8086:2811] type 0 class 0x000601
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321658] pci 0000:00:1f.0: quirk: [io 0x1000-0x107f] claimed by ICH6 ACPI/GPIO/TCO
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321758] pci 0000:00:1f.0: quirk: [io 0x1080-0x10bf] claimed by ICH6 GPIO
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321846] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0900 (mask 007f)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321947] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 0c80 (mask 003f)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322084] pci 0000:00:1f.1: [8086:2850] type 0 class 0x000101
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322100] pci 0000:00:1f.1: reg 10: [io 0x01f0-0x01f7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322111] pci 0000:00:1f.1: reg 14: [io 0x03f4-0x03f7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322123] pci 0000:00:1f.1: reg 18: [io 0x0170-0x0177]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322134] pci 0000:00:1f.1: reg 1c: [io 0x0374-0x0377]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322145] pci 0000:00:1f.1: reg 20: [io 0x6fa0-0x6faf]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322189] pci 0000:00:1f.2: [8086:2828] type 0 class 0x000101
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322210] pci 0000:00:1f.2: reg 10: [io 0x6eb0-0x6eb7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322221] pci 0000:00:1f.2: reg 14: [io 0x6eb8-0x6ebb]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322232] pci 0000:00:1f.2: reg 18: [io 0x6ec0-0x6ec7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322244] pci 0000:00:1f.2: reg 1c: [io 0x6ec8-0x6ecb]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322255] pci 0000:00:1f.2: reg 20: [io 0x6ee0-0x6eef]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322266] pci 0000:00:1f.2: reg 24: [io 0xeff0-0xefff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322300] pci 0000:00:1f.2: PME# supported from D3hot
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322304] pci 0000:00:1f.2: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322319] pci 0000:00:1f.3: [8086:283e] type 0 class 0x000c05
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322335] pci 0000:00:1f.3: reg 10: [mem 0xf6ffbf00-0xf6ffbfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322376] pci 0000:00:1f.3: reg 20: [io 0x10c0-0x10df]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322456] pci 0000:01:00.0: [10de:040d] type 0 class 0x000300
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322475] pci 0000:01:00.0: reg 10: [mem 0xf5000000-0xf5ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322495] pci 0000:01:00.0: reg 14: [mem 0xe0000000-0xefffffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322515] pci 0000:01:00.0: reg 1c: [mem 0xf2000000-0xf3ffffff 64bit]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322528] pci 0000:01:00.0: reg 24: [io 0xdf00-0xdf7f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322541] pci 0000:01:00.0: reg 30: [mem 0xf6e00000-0xf6e1ffff pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322620] pci 0000:00:01.0: PCI bridge to [bus 01-01]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322704] pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322707] pci 0000:00:01.0: bridge window [mem 0xf2000000-0xf6efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322711] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322769] pci 0000:00:1c.0: PCI bridge to [bus 0b-0b]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322856] pci 0000:00:1c.0: bridge window [io 0xf000-0x0000] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322861] pci 0000:00:1c.0: bridge window [mem 0xfff00000-0x000fffff] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322868] pci 0000:00:1c.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323026] pci 0000:0c:00.0: [8086:4222] type 0 class 0x000280
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323081] pci 0000:0c:00.0: reg 10: [mem 0xf1fff000-0xf1ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323422] pci 0000:0c:00.0: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323435] pci 0000:0c:00.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323504] pci 0000:0c:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323679] pci 0000:00:1c.1: PCI bridge to [bus 0c-0c]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323766] pci 0000:00:1c.1: bridge window [io 0xf000-0x0000] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323770] pci 0000:00:1c.1: bridge window [mem 0xf1f00000-0xf1ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323778] pci 0000:00:1c.1: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323837] pci 0000:00:1c.3: PCI bridge to [bus 0d-0e]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323923] pci 0000:00:1c.3: bridge window [io 0xc000-0xcfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323928] pci 0000:00:1c.3: bridge window [mem 0xf1c00000-0xf1efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323935] pci 0000:00:1c.3: bridge window [mem 0xf0000000-0xf01fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.324065] pci 0000:09:00.0: [14e4:1674] type 0 class 0x000200
    Jun 13 04:03:43 cry-workstation kernel: [ 0.324095] pci 0000:09:00.0: reg 10: [mem 0xf1bf0000-0xf1bfffff 64bit]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.324231] pci 0000:09:00.0: PME# supported from D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.324237] pci 0000:09:00.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330035] pci 0000:00:1c.5: PCI bridge to [bus 09-09]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330121] pci 0000:00:1c.5: bridge window [io 0xf000-0x0000] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330126] pci 0000:00:1c.5: bridge window [mem 0xf1b00000-0xf1bfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330134] pci 0000:00:1c.5: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330179] pci 0000:03:01.0: [1180:0832] type 0 class 0x000c00
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330195] pci 0000:03:01.0: proprietary Ricoh MMC controller disabled (via firewire function)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330294] pci 0000:03:01.0: MMC cards are now supported by standard SDHCI controller
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330405] pci 0000:03:01.0: reg 10: [mem 0xf1aff800-0xf1afffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330489] pci 0000:03:01.0: supports D1 D2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330491] pci 0000:03:01.0: PME# supported from D0 D1 D2 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330496] pci 0000:03:01.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330517] pci 0000:03:01.1: [1180:0822] type 0 class 0x000805
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330538] pci 0000:03:01.1: reg 10: [mem 0xf1aff400-0xf1aff4ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330622] pci 0000:03:01.1: supports D1 D2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330623] pci 0000:03:01.1: PME# supported from D0 D1 D2 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330628] pci 0000:03:01.1: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330648] pci 0000:03:01.2: [1180:0592] type 0 class 0x000880
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330670] pci 0000:03:01.2: reg 10: [mem 0xf1aff600-0xf1aff6ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330754] pci 0000:03:01.2: supports D1 D2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330756] pci 0000:03:01.2: PME# supported from D0 D1 D2 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330761] pci 0000:03:01.2: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330782] pci 0000:03:01.3: [1180:0852] type 0 class 0x000880
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330803] pci 0000:03:01.3: reg 10: [mem 0xf1aff700-0xf1aff7ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330888] pci 0000:03:01.3: supports D1 D2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330889] pci 0000:03:01.3: PME# supported from D0 D1 D2 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330894] pci 0000:03:01.3: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330963] pci 0000:00:1e.0: PCI bridge to [bus 03-03] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331051] pci 0000:00:1e.0: bridge window [io 0xf000-0x0000] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331056] pci 0000:00:1e.0: bridge window [mem 0xf1a00000-0xf1afffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331063] pci 0000:00:1e.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331065] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331067] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331069] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331071] pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331073] pci 0000:00:1e.0: bridge window [mem 0xc0000000-0xf7ffffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331075] pci 0000:00:1e.0: bridge window [mem 0xfc000000-0xfebfffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331077] pci 0000:00:1e.0: bridge window [mem 0xfec10000-0xfecfffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331079] pci 0000:00:1e.0: bridge window [mem 0xfed1c000-0xfed1ffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331081] pci 0000:00:1e.0: bridge window [mem 0xfed90000-0xfed9ffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331083] pci 0000:00:1e.0: bridge window [mem 0xfed40000-0xfed44fff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331085] pci 0000:00:1e.0: bridge window [mem 0xfeda7000-0xfedfffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331087] pci 0000:00:1e.0: bridge window [mem 0xfee10000-0xff9fffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331089] pci 0000:00:1e.0: bridge window [mem 0xffc00000-0xffdfffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331091] pci 0000:00:1e.0: bridge window [mem 0x140000000-0x337ffffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331127] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331268] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331339] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331363] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331393] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331425] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331455] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331483] pci0000:00: Requesting ACPI _OSC control (0x1d)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331566] Unable to assume _OSC PCIe control. Disabling ASPM
    Jun 13 04:03:43 cry-workstation kernel: [ 0.346067] ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 11) *5
    Jun 13 04:03:43 cry-workstation kernel: [ 0.346589] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *10
    Jun 13 04:03:43 cry-workstation kernel: [ 0.347028] ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 11) *3
    Jun 13 04:03:43 cry-workstation kernel: [ 0.347548] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 11) *3
    Jun 13 04:03:43 cry-workstation kernel: [ 0.348197] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.349186] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.350176] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.351158] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352318] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352418] vgaarb: loaded
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352570] PCI: Using ACPI for IRQ routing
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352652] PCI: pci_cache_line_size set to 64 bytes
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352839] reserve RAM buffer: 000000000009f000 - 000000000009ffff
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352841] reserve RAM buffer: 00000000bfe84c00 - 00000000bfffffff
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352941] NetLabel: Initializing
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353023] NetLabel: domain hash size = 128
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353104] NetLabel: protocols = UNLABELED CIPSOv4
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353197] NetLabel: unlabeled traffic allowed by default
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353323] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353412] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353754] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    Jun 13 04:03:43 cry-workstation kernel: [ 0.363324] Switching to clocksource hpet
    Jun 13 04:03:43 cry-workstation kernel: [ 0.366464] Switched to NOHz mode on CPU #0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.366550] Switched to NOHz mode on CPU #1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.369169] pnp: PnP ACPI init
    Jun 13 04:03:43 cry-workstation kernel: [ 0.369268] ACPI: bus type pnp registered
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376191] pnp 00:00: [bus 00-ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376193] pnp 00:00: [io 0x0000-0x0cf7 window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376195] pnp 00:00: [io 0x0cf8-0x0cff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376197] pnp 00:00: [io 0x0d00-0xffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376198] pnp 00:00: [mem 0x000a0000-0x000bffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376200] pnp 00:00: [mem 0x000d0000-0x000dffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376202] pnp 00:00: [mem 0xc0000000-0xf7ffffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376203] pnp 00:00: [mem 0xfc000000-0xfebfffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376205] pnp 00:00: [mem 0xfec10000-0xfecfffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376207] pnp 00:00: [mem 0xfed1c000-0xfed1ffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376208] pnp 00:00: [mem 0xfed90000-0xfed9ffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376210] pnp 00:00: [mem 0xfed40000-0xfed44fff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376212] pnp 00:00: [mem 0xfeda7000-0xfedfffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376213] pnp 00:00: [mem 0xfee10000-0xff9fffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376215] pnp 00:00: [mem 0xffc00000-0xffdfffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376216] pnp 00:00: [mem 0x140000000-0x337ffffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376281] pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376304] pnp 00:01: [irq 12]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376323] pnp 00:01: Plug and Play ACPI device, IDs PNP0f13 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376334] pnp 00:02: [io 0x0060]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376336] pnp 00:02: [io 0x0064]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376337] pnp 00:02: [io 0x0062]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376339] pnp 00:02: [io 0x0066]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376343] pnp 00:02: [irq 1]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376364] pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376376] pnp 00:03: [io 0x0070-0x0071]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376381] pnp 00:03: [irq 8]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376382] pnp 00:03: [io 0x0072-0x0077]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376400] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376412] pnp 00:04: [io 0x0061]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376417] pnp 00:04: [io 0x0063]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376418] pnp 00:04: [io 0x0065]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376419] pnp 00:04: [io 0x0067]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376439] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376453] pnp 00:05: [io 0x002e-0x002f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376454] pnp 00:05: [io 0x0c80-0x0caf]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376456] pnp 00:05: [io 0x0cc0-0x0cff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376457] pnp 00:05: [io 0x004e-0x004f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376509] system 00:05: [io 0x0c80-0x0caf] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376594] system 00:05: [io 0x0cc0-0x0cff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376694] system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376707] pnp 00:06: [dma 4]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376709] pnp 00:06: [io 0x0000-0x000f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376710] pnp 00:06: [io 0x0080-0x0085]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376712] pnp 00:06: [io 0x0087-0x008f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376713] pnp 00:06: [io 0x00c0-0x00df]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376714] pnp 00:06: [io 0x0010-0x001f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376716] pnp 00:06: [io 0x0090-0x0091]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376717] pnp 00:06: [io 0x0093-0x009f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376737] pnp 00:06: Plug and Play ACPI device, IDs PNP0200 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376747] pnp 00:07: [io 0x00f0-0x00ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376752] pnp 00:07: [irq 13]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376775] pnp 00:07: Plug and Play ACPI device, IDs PNP0c04 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376802] pnp 00:08: [mem 0xfed00000-0xfed003ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376838] system 00:08: [mem 0xfed00000-0xfed003ff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376925] system 00:08: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390722] pnp 00:09: [mem 0xfed40000-0xfed44fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390724] pnp 00:09: [io 0x0cb0-0x0cbb]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390761] system 00:09: [io 0x0cb0-0x0cbb] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390846] system 00:09: [mem 0xfed40000-0xfed44fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390932] system 00:09: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391564] pnp 00:0a: [io 0x0900-0x097f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391566] pnp 00:0a: [io 0x0092]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391567] pnp 00:0a: [io 0x00b2-0x00b3]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391569] pnp 00:0a: [io 0x0020-0x0021]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391570] pnp 00:0a: [io 0x00a0-0x00a1]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391572] pnp 00:0a: [irq 0 disabled]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391573] pnp 00:0a: [io 0x04d0-0x04d1]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391574] pnp 00:0a: [io 0x1000-0x1005]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391576] pnp 00:0a: [io 0x1008-0x100f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391588] pnp 00:0a: disabling [io 0x1000-0x1005] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391689] pnp 00:0a: disabling [io 0x1008-0x100f] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391833] system 00:0a: [io 0x0900-0x097f] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391918] system 00:0a: [io 0x04d0-0x04d1] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392006] system 00:0a: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392018] pnp 00:0b: [io 0xf400-0xf4fe]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392020] pnp 00:0b: [io 0x0086]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392021] pnp 00:0b: [io 0x1006-0x1007]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392022] pnp 00:0b: [io 0x100a-0x1059]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392024] pnp 00:0b: [io 0x1080-0x10bf]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392025] pnp 00:0b: [io 0x10c0-0x10df]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392026] pnp 00:0b: [io 0x1010-0x102f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392028] pnp 00:0b: [io 0x0809]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392039] pnp 00:0b: disabling [io 0x1006-0x1007] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392139] pnp 00:0b: disabling [io 0x100a-0x1059] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392240] pnp 00:0b: disabling [io 0x1010-0x102f] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392379] system 00:0b: [io 0xf400-0xf4fe] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392463] system 00:0b: [io 0x1080-0x10bf] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392548] system 00:0b: [io 0x10c0-0x10df] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392632] system 00:0b: [io 0x0809] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392717] system 00:0b: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400883] pnp 00:0c: [mem 0x00000000-0x0009efff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400885] pnp 00:0c: [mem 0x0009f000-0x0009ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400887] pnp 00:0c: [mem 0x000c0000-0x000cffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400889] pnp 00:0c: [mem 0x000e0000-0x000fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400890] pnp 00:0c: [mem 0x00100000-0xbfe84bff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400892] pnp 00:0c: [mem 0xbfe84c00-0xbfefffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400896] pnp 00:0c: [mem 0xbff00000-0xbfffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400898] pnp 00:0c: [mem 0xffe00000-0xffffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400899] pnp 00:0c: [mem 0xffa00000-0xffbfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400901] pnp 00:0c: [mem 0xfec00000-0xfec0ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400902] pnp 00:0c: [mem 0xfee00000-0xfee0ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400904] pnp 00:0c: [mem 0xfed20000-0xfed3ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400905] pnp 00:0c: [mem 0xfed45000-0xfed8ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400907] pnp 00:0c: [mem 0xfeda0000-0xfeda3fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400908] pnp 00:0c: [mem 0xfeda4000-0xfeda4fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400909] pnp 00:0c: [mem 0xfeda5000-0xfeda5fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400911] pnp 00:0c: [mem 0xfeda6000-0xfeda6fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400912] pnp 00:0c: [mem 0xfed18000-0xfed1bfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400914] pnp 00:0c: [mem 0xf8000000-0xfbffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400980] system 00:0c: [mem 0x00000000-0x0009efff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401066] system 00:0c: [mem 0x0009f000-0x0009ffff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401152] system 00:0c: [mem 0x000c0000-0x000cffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401238] system 00:0c: [mem 0x000e0000-0x000fffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401323] system 00:0c: [mem 0x00100000-0xbfe84bff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401409] system 00:0c: [mem 0xbfe84c00-0xbfefffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401494] system 00:0c: [mem 0xbff00000-0xbfffffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401580] system 00:0c: [mem 0xffe00000-0xffffffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401665] system 00:0c: [mem 0xffa00000-0xffbfffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401751] system 00:0c: [mem 0xfec00000-0xfec0ffff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401836] system 00:0c: [mem 0xfee00000-0xfee0ffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401921] system 00:0c: [mem 0xfed20000-0xfed3ffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402006] system 00:0c: [mem 0xfed45000-0xfed8ffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402092] system 00:0c: [mem 0xfeda0000-0xfeda3fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402177] system 00:0c: [mem 0xfeda4000-0xfeda4fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402262] system 00:0c: [mem 0xfeda5000-0xfeda5fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402348] system 00:0c: [mem 0xfeda6000-0xfeda6fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402433] system 00:0c: [mem 0xfed18000-0xfed1bfff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402518] system 00:0c: [mem 0xf8000000-0xfbffffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402604] system 00:0c: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402630] pnp: PnP ACPI: found 13 devices
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402712] ACPI: ACPI bus type pnp unregistered
    Jun 13 04:03:43 cry-workstation kernel: [ 0.408756] pci 0000:00:1c.5: BAR 15: assigned [mem 0xc0000000-0xc01fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.408855] pci 0000:00:1c.5: BAR 13: assigned [io 0x2000-0x2fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.408940] pci 0000:00:1c.1: BAR 15: assigned [mem 0xc0200000-0xc03fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409038] pci 0000:00:1c.1: BAR 13: assigned [io 0x3000-0x3fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409123] pci 0000:00:1c.0: BAR 14: assigned [mem 0xc0400000-0xc05fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409210] pci 0000:00:1c.0: BAR 15: assigned [mem 0xc0600000-0xc07fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409308] pci 0000:00:1c.0: BAR 13: assigned [io 0x4000-0x4fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409393] pci 0000:00:01.0: PCI bridge to [bus 01-01]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409477] pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409563] pci 0000:00:01.0: bridge window [mem 0xf2000000-0xf6efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409649] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409748] pci 0000:00:1c.0: PCI bridge to [bus 0b-0b]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409833] pci 0000:00:1c.0: bridge window [io 0x4000-0x4fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409921] pci 0000:00:1c.0: bridge window [mem 0xc0400000-0xc05fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410023] pci 0000:00:1c.0: bridge window [mem 0xc0600000-0xc07fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410126] pci 0000:00:1c.1: PCI bridge to [bus 0c-0c]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410211] pci 0000:00:1c.1: bridge window [io 0x3000-0x3fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410299] pci 0000:00:1c.1: bridge window [mem 0xf1f00000-0xf1ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410387] pci 0000:00:1c.1: bridge window [mem 0xc0200000-0xc03fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410490] pci 0000:00:1c.3: PCI bridge to [bus 0d-0e]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410575] pci 0000:00:1c.3: bridge window [io 0xc000-0xcfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410664] pci 0000:00:1c.3: bridge window [mem 0xf1c00000-0xf1efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410752] pci 0000:00:1c.3: bridge window [mem 0xf0000000-0xf01fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410854] pci 0000:00:1c.5: PCI bridge to [bus 09-09]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410939] pci 0000:00:1c.5: bridge window [io 0x2000-0x2fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411027] pci 0000:00:1c.5: bridge window [mem 0xf1b00000-0xf1bfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411116] pci 0000:00:1c.5: bridge window [mem 0xc0000000-0xc01fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411219] pci 0000:00:1e.0: PCI bridge to [bus 03-03]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411302] pci 0000:00:1e.0: bridge window [io disabled]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411389] pci 0000:00:1e.0: bridge window [mem 0xf1a00000-0xf1afffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411477] pci 0000:00:1e.0: bridge window [mem pref disabled]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411575] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411662] pci 0000:00:01.0: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411668] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411756] pci 0000:00:1c.0: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411764] pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411852] pci 0000:00:1c.1: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411860] pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
    Jun 13 04:03:43 cry-workstation kernel: [ 0.412988] pci 0000:00:1c.3: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.412994] pci 0000:00:1c.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413082] pci 0000:00:1c.5: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413090] pci 0000:00:1e.0: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413094] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413095] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413097] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413099] pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413101] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xf7ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413103] pci_bus 0000:00: resource 9 [mem 0xfc000000-0xfebfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413104] pci_bus 0000:00: resource 10 [mem 0xfec10000-0xfecfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413106] pci_bus 0000:00: resource 11 [mem 0xfed1c000-0xfed1ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413108] pci_bus 0000:00: resource 12 [mem 0xfed90000-0xfed9ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413110] pci_bus 0000:00: resource 13 [mem 0xfed40000-0xfed44fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413111] pci_bus 0000:00: resource 14 [mem 0xfeda7000-0xfedfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413113] pci_bus 0000:00: resource 15 [mem 0xfee10000-0xff9fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413115] pci_bus 0000:00: resource 16 [mem 0xffc00000-0xffdfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413117] pci_bus 0000:00: resource 17 [mem 0x140000000-0x337ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413119] pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413120] pci_bus 0000:01: resource 1 [mem 0xf2000000-0xf6efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413122] pci_bus 0000:01: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413124] pci_bus 0000:0b: resource 0 [io 0x4000-0x4fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413126] pci_bus 0000:0b: resource 1 [mem 0xc0400000-0xc05fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413128] pci_bus 0000:0b: resource 2 [mem 0xc0600000-0xc07fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413130] pci_bus 0000:0c: resource 0 [io 0x3000-0x3fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413132] pci_bus 0000:0c: resource 1 [mem 0xf1f00000-0xf1ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413133] pci_bus 0000:0c: resource 2 [mem 0xc0200000-0xc03fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413135] pci_bus 0000:0

  • 10G SFP Module absent after reload in Nexus 5548UP

    Hi there,
    i have a problem concerning two new 5548UP.
    After a reload, the 2x2 10G SFP Modules SFP-10G-SR are displayed as "sfpabsent" on a random basis.
    When i plug it out and afterwards in again, they work fine an the VPC-Peer link across the two switches comes up.
    My 1G SFP modules  are all working correctly.
    I tested firware version 6.0 and 5.2.
    Any suggestions?
    Thank you very much!

    Hi,
    We had the same problem with a Nexus 5596 in 5.1(3)N2(1a) last night:
    %NOHMS-2-NOHMS_ENV_ERR_FAN_SPEED: System minor alarm in fan tray 1: fan speed is out of range on fan 2. 5812 to 12500 rpm expected. 4072 rpm read
    %NOHMS-2-NOHMS_ENV_ERR_FAN_DOWN: System minor alarm on fans: One fan missing or failed
    %NOHMS-2-NOHMS_ENV_ERR_FAN_RECOVERED: Recovered: System minor alarm in fan tray 1
    %NOHMS-2-NOHMS_ENV_ERR_ALL_FAN_UP: Recovered: System minor alarm on fans: One fan missing or failed
    %PFMA-0-SYS_SHUTDOWN_FAN_DIR_MISMATCH: System shutdown in 60 seconds due to fan dir mismatch
    %NOHMS-2-NOHMS_ENV_ERR_FAN_DIR: System major alarm: fan direction mismatch with other fan(s)
    %PFMA-0-SYS_SHUTDOWN_FAN_DIR_MISMATCH: System shutdown in 55 seconds due to fan dir mismatch
    %PFMA-0-SYS_SHUTDOWN_FAN_DIR_MISMATCH: System shutdown in 50 seconds due to fan dir mismatch
    After reseating the FANs the switch came up. We'll open a TAC case.
    Javier

  • Login to Glassfish (AS 9.1) Admin Module fails after AM 7.1 install

    Hello Everyone,
    I am trying to deploy Sun Java System Access Manager 7.1 on Sun Java System Application Server 9.1 running on RH Linux. After deploying the war file and performing the initial configuration using /amserver/configurator.jsp and then restarting the server instance, I am no longer able to login to the administrative module of the application server. Following error comes up in the Server.log file:
    [#|2007-11-21T21:26:21.422-0800|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=15;_ThreadName=httpWorkerThread-4848-0;admin;|SEC5046: Audit: Authentication refused for [admin].|#]
    [#|2007-11-21T21:26:21.422-0800|WARNING|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=15;_ThreadName=httpWorkerThread-4848-0;_RequestID=43616e0d-d1d5-4aaa-88aa-7e7913125a67;|Web login failed: Login failed: javax.security.auth.login.LoginException: No LoginModules configured for fileRealm|#]
    In addition to running the configurator, I've also added the following permissions to the server.policy file:
    grant codeBase "file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/amserver/-" {
    permission java.net.SocketPermission "*", "connect,accept,resolve";
    permission java.util.PropertyPermission "*", "read, write";
    permission java.lang.RuntimePermission "modifyThreadGroup";
    permission java.lang.RuntimePermission "setFactory";
    permission java.lang.RuntimePermission "accessClassInPackage.*";
    permission java.util.logging.LoggingPermission "control";
    permission java.lang.RuntimePermission "shutdownHooks";
    permission javax.security.auth.AuthPermission "insertProvider.Mozilla-JSS";
    permission java.security.SecurityPermission "putProviderProperty.Mozilla-JSS";
    permission javax.security.auth.AuthPermission "getLoginConfiguration";
    permission javax.security.auth.AuthPermission "setLoginConfiguration";
    permission javax.security.auth.AuthPermission "modifyPrincipals";
    permission javax.security.auth.AuthPermission "createLoginContext.*";
    permission java.security.SecurityPermission "insertProvider.Mozilla-JSS";
    permission javax.security.auth.AuthPermission "putProviderProperty.Mozilla-JSS";
    permission java.io.FilePermission "<<ALL FILES>>", "execute,delete";
    permission java.util.PropertyPermission "java.util.logging.config.class", "write";
    permission java.security.SecurityPermission "removeProvider.SUN";
    permission java.security.SecurityPermission "insertProvider.SUN";
    permission java.security.SecurityPermission "removeProvider.Mozilla-JSS";
    permission javax.security.auth.AuthPermission "doAs";
    permission java.util.PropertyPermission "java.security.krb5.realm", "write";
    permission java.util.PropertyPermission "java.security.krb5.kdc", "write";
    permission java.util.PropertyPermission "java.security.auth.login.config", "write";
    permission java.util.PropertyPermission "user.language", "write";
    permission javax.security.auth.kerberos.ServicePermission "*", "accept";
    permission javax.net.ssl.SSLPermission "setHostnameVerifier";
    permission java.security.SecurityPermission "putProviderProperty.IAIK";
    permission java.security.SecurityPermission "removeProvider.IAIK";
    permission java.security.SecurityPermission "insertProvider.IAIK";
    Have I missed any steps? Are there any patches or workarounds for this issue?

    Hi,
    You can download the GUI files from this link according to the version you have:
    http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=7.1&mdfid=277641082&sftType=Unified+Communications+Manager+Express+Complete+Support+File+Set&optPlat=&nodecount=3&edesignator=null&modelName=Cisco+Unified+Communications+Manager+Express&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=null&imst=null&lr=Y
    1. Download appropriate tar file to tftp server. cme-basic-x.x.x.tar ? contains basic CME
    system files including GUI, MoH and phoneloads
    cme-gui-x.x.x.tar ? contains basic CME GUI files only
    2. Logon to privileged EXEC mode of router CLI
    3. Enter archive command to extract contents of tar file to router Flash memory:
    Router# archive tar /xtract tftp://ip-address/filename flash:
    Example 1:
    To extract contents of cme-basic-3.0.3.tar from tftp server 192.168.1.1 to flash:
    archive tar /xtract tftp://192.168.1.1/cme-basic-3.0.3.tar flash:
    Example 2:
    To extract contents of cme-gui-3.0.3.tar from tftp server 192.168.1.1 to flash:
    archive tar /xtract tftp://192.168.1.1/cme-gui-3.0.3.tar flash:
    This will update all the gui files in the location which the gui checks on the flash.
    Regards,
    Tere

  • 2960X Stack Fails After reload Command

    Did not find anything in Bug Tool or these forums for this so posting as a new question.
    Environment is multiple stacks of  2960X -48FPD-L switches in different IDF's running IOS 15.0(2)EX5.   They were installed new and configured by another party about one month ago.  Current configuration is attached to this post.
    Switch stack fails to rebuild/sync after CLI reload command via telnet session.  IP stack appears to not initialize so no  network connectivity comes up even though per the onsite staff the master switch system LED's are green and one of the uplinks is connected to that switch..
    The system LED's of the other switches are amber.
    Remedy for the time being is for someone onsite to power cycle all the switches in 20 second master reelection window.
    Have not yet had opportunity to go onsite to console into one of the master switches to reload and monitor the process from that perspetive.
    One telltale that makes me wonder about EX5 is the reload command as documented in the 15.0(2)EX Switch Manager command reference here:
    http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960x/software/15-0_2_EX/stack_manager/command_reference/b_stck_152ex_2960-x_cr/b_stck_152ex_2960-x_cr_chapter_01.html#wp3486313748
    should prompt with,
    "Proceed to reload the whole Stack? [confirm]"
    but actually only prompts with,
    "Proceed with reload? [confirm]"
    as if the command was 'reload slot 1' instead of just 'reload'.
    I have not found anything in the config missing/wrong as far as configuration of the stack is concerned other than priorities and ID's were all assigned automatically/default..
    If EX5 is the issue I'm not keen on downgrading to EX3 because the uplinks are SFP-10G-LRM which had more issues with EX3 than with EX5.
    Thanks in advance for your time.
    Jon

    Have you tried cold booting the switch.  I know it is a horrible work around, but I ran circles around this problem on a switch I had upgraded (well- downgraded) from 15.2(3)E that was hitting this bug. Warm boots seemed to do nothing to clear the %ILET-1-AUTHENTICATION_FAIL: This switch may note have been manufactured by Cisco (so on so forth).  Once I pulled the power cable from the switch and waited several seconds prior to reapplying power, the switch came up cleanly.  Currently, Cisco has safe harbored 15.0(2a)EX5.  Did you happen to catch which bootloader combos with 15.0(2a)EX5 seemed to have the most consistent problems with this bug?  The campus I work at is currently in the process of rolling out about 120 of these switches and originally decided to stick with 15.0(2)EX5 until we hit an OIR with SFPs that TAC almost immediately acknowledged as a new development for that specific image. We as a group decided to try out 15.2(3)E and quickly found out that the bug still existed.  By that point, TAC was aware of the problem and over the weekend (2 days time after opening the ticket on a Friday if I remember right), 15.0(2a)EX5 was released.  
    Here is a small sampling of the switches that we have rolled out and what their bootloader + running IOS is.  Note: There are a few "stable" cases running 15.2(3)E, but they will be rolled back during maintenance windows in the next few weeks.  Everything that has been deployed since 15.0(2a)EX5 has been available has been running without issue on that IOS.   I don't know how useful this data is, but I can continue to build a list, though it looks like every switch that I have that is running 15.0(2)EX5 from the factory that is getting upgraded to 15.0(2a)EX5 has the 15.2(2r)E1 bootloader, with a few cases with the 15.0(2r)EX3 bootloader. 
    Does anyone have information on when an IOS upgrade will trigger a bootloader upgrade?  One thing I can't put a finger on right now is that during the last few rack/stack/configs of new stacks I have noticed that some of the switches running 15.0(2)EX5 from the factory that are being upgraded to 15.0(2a)EX5 are receiving a bootloader upgrade while the vast majority are not.

  • After Effects Error: rendering error while writing to file...Output Module failed - 1610153646

    Hi – I’m currently working with someone who is running After Effects 5.5v10.5.0.253 on a PC which is running Windows 7 Ultimate. The computer has just recently been built and the software is newly installed. (ie. a couple of weeks old, max). Up until now, we have been using After Effects with no real issues. But tonight, we started to see the following error message, when trying to render something out:
    “After Effects Error: rendering error while writing to file xxxxx. Output Module failed, the file may be damaged or corrupted -1610153646” – displayed during render, which meant the render failed.”
    We started to review forums to see if we could come up with a fix and tried a few of the more common suggested solutions, including:
    Make sure there are no third-party plug-ins or Windows incompatible elements installed - as it’s a pretty new install, we haven’t added anything except out-of-the box elements.
    Clear the render queue – did this, no change.
    Reinstall Quicktime – did this, no change.
    Reinstall Creative Suite – also no change.
    Check the default program to open .mov files is Quicktime – Quicktime was already the default.
    A bit more detail about the machine...
    Ram is 32gb
    GPU is GeForce GTX 660ti
    250gb soild states
    2tb raid drive
    Any help would be much appreciated. This is now happening on all AE files, even files that worked fine earlier in the week. Other than the AE and QT reinstalls mentioned above, nothing new has been added to the machine this week. On a deadline – so a quick response would be amazing, right about now. Thanks.

    Hi Mylenium- thx for the quick response. We have have tried a bunch of different settings. AVIs work and we can do image sequences too. The only major problem seems to be with Quicktime files. While I appreciate your suggetion to convert with AME - this is only a workaround. Was really hoping for a solution that will fix the problem in After Effects? Heard rumor from a few friends in the biz, that this is a major bug... if possible, some feedback from Adobe product devs or someone with a technical background would be great! Thx.

  • LMS 4.0.1 software distribution 3 out of 7 fail to pass traffic after reload

    I've distributed (7) IOS C3560-ipbasek9-mz.150-1.SE2.bin upgrades on identical 3560G PS-S platform using LMS 4.0.1. All jobs come back successfully completed with the /MD5 hash matching exactly what Cisco has on their website. All devices have sufficient 32MB worth of Flash and verified enough was available prior to distribution.
    Issue: After reload 2 of these 3560G devices would not pass traffic. Also, neighboring devices could see these devices through "show cdp neighbors detail" but the management IP was not being displayed. After consoling into these devices via (console port) the management IP address was there but was unable to ping this address locally and neighboring devices were unable to be pinged as well. Performed the "sh run" command and verified the config was correct.
    ***Cisco's engineers suggestion was to load a lower IOS.***
    ***I've perused the caveats with this release and have not found any solutions.***
    I've already replaced the offending switches with new devices but don't want to keep upgrading with this many failures after reloading.

    Your devices with the NX-OS versions you indicate should be OK per the LMS 4.0.1 Supported Devices Table.
    Have you updated your LMS with the latest device packages? See the procedure here.

  • An output module failed. The file may be damaged or corrupted.

    Whenever I try to render something in After Effects CC 13.1.1, an error message pops up, saying "After Effects error: Rendering error while writing to file '[not going to disclose]' An output module failed. The file may be damaged or corrupted (-1610153464)."
    Screenshot of the error message:
    I tried reinstalling QuickTime (7), repaired it, updated After Effects to the latest version(as I am writing this), checked firewall software, and used other formats such as AVI.
    Adobe Media Encoder (CC 2014-latest version) won't work with me, either.
    I sent the composition to Adobe Media Encoder, and this is what I got, no progress here.
    Screenshot:
    It took a while to connect to the dynamic link server, and failed.
    This is a log of what has happened in Adobe Media Encoder.
    - Source File: C:\Users\Default.BronyGue\Documents\not done\pinkcoverart_AME\tmpAEtoAMEProject-Pink Intro1.aep
    - Output File: C:\Users\Default.BronyGue\Documents\not done\pinkcoverart_AME\Pink Intro.mp4
    - Preset Used: YouTube HD 720p 29.97
    - Video: 1280x720 (1.0), 29.97 fps, Progressive
    - Audio: AAC, 320 kbps, 48 kHz, Stereo
    - Bitrate: VBR, 2 pass, Target 5.00 Mbps, Max 5.00 Mbps
    - Encoding Time: 00:00:12
    06/29/2014 02:29:14 PM : Encoding Failed
    The Operation was interrupted by user
    (no need to worry about the above part)
    - Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage1.aep
    - Output File: C:\Users\Default.BronyGue\Videos\chilledup.wmv
    - Preset Used: Custom
    - Video: 1280x720 (1.0), 29.97 fps, Progressive
    - Audio: Windows Media Audio 10 Professional, 96000 Hz, Stereo, 24 bit
    - Bitrate: CBR, 2 pass, Max 10000.00 kbps
    - Encoding Time: 00:01:42
    11/22/2014 12:24:39 AM : Encoding Failed
    The Operation was interrupted by user
    - Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage1.aep
    - Output File: C:\Users\Default.BronyGue\Videos\chilledup.mpg
    - Preset Used: Custom
    - Video: 1280x720, 29.97 fps, Progressive, Quality 75
    - Audio: MPEG Audio, 384 kbps, 48 kHz, Stereo, 16 bit
    - Bitrate: VBR, 1 Pass, Min 4.00, Target 15.00, Max 18.50 Mbps
    - Encoding Time: 00:00:11
    11/22/2014 12:52:11 AM : Encoding Failed
    The Operation was interrupted by user
    - Encoding Time: 00:00:51
    11/22/2014 12:53:51 AM : Encoding Failed
    Export Error
    Error compiling movie.
    Unknown error.
    - Encoding Time: 00:00:46
    11/22/2014 08:39:46 AM : Encoding Failed
    Export Error
    Error compiling movie.
    Unknown error.
    - Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage4.aep
    - Output File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\montage.mpg
    - Preset Used: Match Source - High bitrate
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 00:00:00
    11/22/2014 10:06:45 AM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    I need some help! Any solutions?.
    Computer Specs:
    AMD FX-6300
    8GB 1600MHz DDR3 RAM
    NVIDIA GeForce GTX 650 Ti BOOST
    1TB 7200RPM Hard Drive
    Windows 8.1 Update 1(with latest updates)
    EDIT(11/23/2014 8:31PM PST): For some reason, other projects work for me just fine. I am not sure why it is not working on one project.
    Screenshot of a new project other than this I am rendering at the time of writing this edit:

    Can other projects can output to the same output location? Yes
    Can other projects render with the same render settings (codec, format, etc.)? Yes.
    If you create a new composition and just add a solid layer to it with no effects in the same project does it render? No. I still get the error.
    Can you render that brand new comp with the same render settings, output settings, output location etc.? Yes.
    If so, what effects are present in the offending comp? Twixtor Pro in all the cinematics/clips, Motion Tile and Transform for pan/crop & wiggle, Magic Bullet Looks and Bad TV Warping preset with just Wave Warp & Venetian Blinds for color correction, Gradient Ramp for text, Bad TV Warping preset with everything for effect, Transform for fade in/out, and ReelSmart Motion Blur v4.1.2 for motion blur.
    Also, what scripts are you using? Just the Move Anchor Point script I found from one of Mt. Mograph's videos, Summit 16 - 2.5D Minecraft Steve - After Effects - YouTube.
    Have you ever installed any third-party codec packs? (I've heard of some codec packs causing weird issues like this.) Yes, (not everything I have, just everything I can think of and find) I have K-Lite codec pack, Fraps, x264vfw, and Xvid MPEG-4 codec.

  • Adobe Print form error: Initialization of the font server module failed.

    Hi all,
    When trying to open a PDF preview the error below is displayed:
    "Initialization of the font server module failed."
    The problem occurs with SAP GUI 7.10 patch 15 and Adobe Reader 9
    With SAP GUI 7.10 patch 12 and 13 with Adobe Reader 9 the problem do not happen.
    Has anybody faced this kind of problem? Is it a SAP GUI patch release issue?
    Any help is welcome.
    Kind regards,
    Thiago Viaro

    Hi Thiago,
    We had exactly the same problem, but also with sp 12 and 13 for sapgui 710.
    After applying ECL 6.0 Patch 4, the problem was solved.
    Please have a look at sap note 1308147 and 1356854
    Cheers,
    Peter Albrecht

  • "...an Output Module failed" error screen...

    Greetings AE Peeps!!
    Long time - no see - been stupid busy. My Studio has just ponied up and upgraded our 5 Edit Stations to AE CS5. I personally am a huge advocate of not upgrading software while in the middle of a project, but this was out of my control. I am having a lot of crashing (app just quits for no reason while scrubbing) and other weirdness...like today. I am rendering a 3 minute piece in ProRes 4:2:2 (1280x720p) to my RAID (no special plug-ins or anything) and I get the following error at the very end of every render:
    After Effects Error: Rendering error while writing to file (insert my RAID path here). An output module failed. The file may be damaged or corrupted (-1610153464)
    I have never in 11 years got a "failed Output Module error". Can anyone speak to this and tell me how to get rid of it short of reinstalling AE?
    Grazie! Ciao!
    Joey

    First, make sure that you've installed the After Effects CS5 (10.0.1) update.
    Regarding the output module failure: It may be that this is because you have an output module created in a previous version of After Effects that refers to a codec or set of settings that isn't working in After Effects CS5. The best thing to do is to remove the output modules from the render items and then rebuild them in After Effects CS5. That may sound tedious, but you only need to do it once, and then you can save output module templates that you know work with After Effects CS5.
    As Mylenium suggested, there are some challenges associated with the fact that there is no 64-bit QuickTime, so we had to create our own 32-bit-to-64-bit QuickTime conversion layer (QT32 Server). QuickTime does work with After Effects CS5, but there are some hiccups in some cases on first use.
    If this doesn't help, answer back and we'll help you through.
    Oh, this might be useful, too:
    http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

  • Output module failed

    I know there are more posted about this problem bust still havent found a solution.
    I can only render out one movie from AE (CC 12.2.1.5). If I want to render a second movie I get ""[file path and name].mov”. An output module failed. The file may be damaged or corrupted. (-1610153464)"
    I've deleted DVCPROHDVideoOutput.component as read on a help file (http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in -after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html) but dit didn't fix it.
    A restart of OSX (10.9.2) fix it for one render and then I got the same problem again. I render to DXV codec (rgb+alpha) (http://resolume.com/software/codec)
    What do I do to fix this? Because rebooting is taking to much time
    thx Joost

    Have you installed any third-party codec packs (such as K-lite)? I've seen them cause this sort of issue in the past.
    Have you tried it in AE 13.1 or 13.0?

  • AE CC Render error output module failed

    Hi, I tried my best to find this answer on the forums but couldn't find anything current.
    I have isolated two issues in AE CC where I can duplicate a failed render with this message:
    After Effects error: Rendering error while writing file "xxx". An output module failed. The file may be damaged or corrupted. (-1610153464)
    This happens when opening an AE CS6 project and trying to render a simple comp with only one text layer and a moving mask. It also just happened after my first round trip test with Cinema 4D. I could RAM preview the c4d layer but the output to Quicktime h.264 failed.
    I have even tried a full reinstall of AE CC. I have the basic FxFactory Pro plugins and MagicBullet Looks installed, but neither are being used since this is a single 1280x720 comp with a single C4D layer. Plus like I said it failed with the same error in past CS6 files.
    I don't know how to force disable a plugin to test that, but I can't see how an unused plugin could cause a render to fail like this.
    I'm on a new (late 2012) 27" iMac
    3.4 GHz Intel Core i7
    8GB RAM
    NVIDIA GeForce GTX 680MX with 2GB VRAM
    OS X 10.8.4
    AE CC 12.0.0.404
    CUDA driver 5.0.59
    Thanks for any suggestions!
    Matt

    Olaf, did you read my reply where I explained my solution? First you should try the steps outlined in the article Todd references:
    http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime- errors-with-after-effects.html
    There seems to be a good way to isolate if it's the same issue I had, though. Let me go into a bit of depth for you.
    The trick was to launch the OS X app called Console, located in Applications > Utilities. It is a program that compiles and displays the system logs in real time. It's great to see the little things happening in the system that don't make it into the user interface. When I had my Console up and generated that same error you're having, I noticed this error in the log:
    The key here is the Adobe QT32 Server, which is mentioned in the TCP part of the article I linked to above from Todd. In my case at least, what was happening was that a third party app called AirServer was talking to the system's QuickTime over the same TCP ports the QT32 Server engine was trying, and it resulted in Adobe QT32 Server crashing, and that alert being thrown up in AfterEffects.
    If you're in the same boat, it means you have some sort of app or system extension that is also talking to QuickTime over TCP. That may not make any sense, but the easy thing to do is quit ALL third party apps, then quit AE, then restart AE.
    In my situation if AE gave me the error and then I quit AirServer, the error still happened because Adobe QT32 had already crashed. You have to relaunch AE after closing the offending third party app.
    To be sure you've quit all third party apps, open Activity Monitor (Applications > Utilities), chose "My Processes" from the dropdown menu, and scan through the list to make sure. You don't have to recognize all the processes there, but you should be able to recognize any third party ones you put there.
    Hope that helps!
    Matt

  • Windows  - error : output module .mov after effects

    When exporting a Quicktime movie from After Effects on windows 7, I get the following error ...
    After Effects error: Rendering error while writing to file "(my main internal drive / my file name).mov". An output module failed. The file may be damaged or corrupted. (-161-153464).
    I see a lot of suggestions for limiting the number of processors by using "msconfig" to change the "boot" file. This seems like a poor solution because it affects how all other programs use the processors.
    Does anyone have any other help on how to resolve this without reducing processors ?
    Thanks, for any help.

    RESOLVED
    I uninstalled Quicktime Pro. Re-started computer. Re-installed Quicktime Pro. Restarted After Effects.
    .mov output works fine now.

  • Output module failed 1610153464

    I am running CS5 on a Mac 10.6.6. I have both QTX and QT 7.6.6 installed
    Every time I render, it gives the following error message:
    An output module failed. The file may be damaged or corrupted. (-1610153464)
    I've tested the files on a different machine and they open and render out fine.
    I'm having these issues and I don't have any plugins installed.
    Re-Installed everything multiple times, trashed preferences, removed plugins from the Application support and still no luck.
    The only thing that works for me is outputting to a PNG or JPEG sequence.
    If I try to render using the Animation preset, It gives the error message.
    I also have been getting a weird "MooV" error message when I try to import certain types of quicktime files. Not all just a few random ones.
    All of this leads me to believe it is a Quicktime issue.
    Please can you help. Other than doing a complete clean operating install, which i am doubting will work.
    Robin Souter

    hey todd,
    good thinking, I was just trying the very same thing. alas when I try to open my AE project in Media Encoder I get the message
    "Could not connect to Adobe After Effects. Please verify that Adobe After Effects and Adobe Dynamic Link components are installed."
    I'm scratching my head, this also worked yesterday.
    Could it be anything to do with de-activation? I have cs5 installed on my workstation in my studio.
    I also have it installed on my laptop at home. do I need to contact Adobe each time I want to use 1 machine or the other?
    Also ever since installing cs5 on my laptop I get the following message each time I launch After Effects (dont know if its connected as I normally just click ok and use AE as normal)
    "Runtime Error! This application has requested the runtime to terminate it in an unusual way.
    Please contact the application's support team for more information"
    or maybe I didn't run the adobe uninstaller cleaner utility to get rid of traces of old versions, before installing cs5 to my laptop
    thanks
    ste

  • Upload to Blurb fails after exactly 30 minutes (There was an error uploading your book's pages...)

    After exactly 30 minutes after the upload has started, I get this error:
    There was an error uploading your book's pages.  Would you like to try again?  The choices given are "Retry Upload" and :"Cancel"
    When I retry, the same thing happens - fails after exacly 30 minutes.  I am using a window 7 pc (with Service Pack 1) and using Lightroom 5.4.  I have turned off my firewall and antivirus programs, rebooted, and connected directly to my router (not wireless) and ensuring my pc does not go to sleep, but did nothing I try wil help. 
    Anyone else get this?  Any ideas?  Thanks!

    Hello,
    I had this problem as well - the upload to Blurb would not work. Creation of a PDF and export as JPEG in the book module worked.
    For me, the solution was to turn off the Windows Firewall while uploading. Now it works!
    Two-in-Love (Photographe de Mariage en Suisse Romande)
    http://www.two-in-love.ch

Maybe you are looking for

  • Hard drive restore- issue

    I had to restore my hard drive (mac) and reloaded from a Backup (yeah!) but Adobe requires that I Uninstall(done), run a Cleanup (done) and reinstall from a new downloaded DMG file.  (why can't this be easier?) Upon trying to start the install I get

  • Can't access WMA files using flip4mac plug-in

    I'm a new mac user who just bought a macbook this past weekend. I realize that the below is perhaps a microsoft software issue, and not an apple issue (the apple care service people said as much and dismissed me), but the microsoft forums provide no

  • How to set main host for Adapter Engine in the HA enviroment

    Hi, all. Our XI env. is like the following. XI 3.0 SP11 on Windows 2003 + SQL Server. Central Instance(ABAP + J2EE Addon) is running on Host A, Dialog Instances(ABAP + J2EE Addon) are running on Host B and Host C. Our design was to have J2EE Adapter

  • Authorization Error using CozyRoc SSIS+

    Using Sharepoint Connection (CozyRoc SSIS+ 1.6 ), getting the following error:  "The request failed with HTTP status 401: Unauthorized.". The 'Test Connection' runs succesfully, but the package execution fails.  Also, using the SPCRED connection mana

  • How to call VB code to JAVA

    hello, can we create DLL files in VB. please write step by step code. please help me.