Kill a variable?
I need to remove a variable after I used it, is it possible?
got a method that get some info from a db and puts it in a jtable.
after this I need to kill the variable so, if I need to, I can do that database method-thingy again.
got it?
*****SOLVED WITH A BAD AS SOLUTION******
Similar Messages
-
[svn] 3190: - First legacy-compatibility package; runs TC acceptance tests
Revision: 3190
Author: [email protected]
Date: 2008-09-11 20:02:41 -0700 (Thu, 11 Sep 2008)
Log Message:
- First legacy-compatibility package; runs TC acceptance tests
-- Live variable analysis for local vars
- Some comments and verboseStatus tracing
- OP_kill marked as having side effect (kills the variable)
- GO side of asc/GO integration
Modified Paths:
flex/sdk/trunk/modules/asc/src/java/adobe/abc/GlobalOptimizer.java -
Easy Question, online store Qty purchase
I need a bit of help, and I'm not quite proficient in CF
really.
I have built a registration system in CF, which has three
steps (pages). On the last step, you can choose to return to Step 1
and register another person, OR you can choose to Pay Now.
I wanted to use session variable or cookies (I'm not really
certain of the difference) to have the system count silently the
number of times a visitor has gone through, and then when they do
hit "Pay Now", to multiply the variable count X the cost per
ticket.
This is what I have been doing:
on
Step 1, I define the variable session.Quantity with:
<cfif (NOT isDefined("session.Quantity ")) >
<cfset session.Quantity = "0" />
</cfif>
On
Step 2, we gather final registration info, and right after
the Insert statement, I increase the value of the session.Quantity
with:
<cfset session.Quantity =#session.Quantity #+1>
On
Step 3, I give them the option to Pay Now (which takes the
session.Quantity and successfully produces the cost) using:
<cfoutput> <cfset TotalCost = #session.quantity# *
75></cfoutput> (and then send them to payment and kill
session variable)
OR, I give them the chance to return to step 1 and go
through again.
NOW, this has been working just fine during my testing,
UNLESS you close down the browser mid stream (and happen to have
another one open in the background), which means that you didn't
pay and the session variable didn't get deleted.
THEN, when you return to the Step 1 again (20min) later,
because you want to do the registration over again, after your
first registration pass, you are already on session.Quantity = 4
(example).
OK, so I am a bit green, and I don't know much about the
application.cfm process (mine is below) or CFLOCK usage, but I
think this is part of my issue. I've read so much, and am now so
confused. Can someone give some clear advice and example that I
could work through, pertinent to this problem.
My cfapplication.cfm file:
<cfapplication name="Application1"
sessionmanagement="Yes"
sessiontimeout="#CreateTimeSpan(0,0,30,0)#"
applicationtimeout="#CreateTimeSpan(0,0,30,0)#"
>
<cfif StructKeyExists(session, "cfid") AND (NOT
StructKeyExists(cookie, "cfid") OR NOT StructKeyExists(cookie,
"cftoken"))>
<cfcookie name="cfid" value="#session.cfid#" />
<cfcookie name="cftoken" value="#session.cftoken#" />
</cfif>
Thanks to the SMART people out there,
Stephen
Tallahassee, FLmaybe you should start by reading the answers to your
previous post...
Azadi Saryev
Sabai-dee.com
Vientiane, Laos
http://www.sabai-dee.com -
"Kernel panic - not syncing: Attempted to kill init!" on shutdown
For several years now, I've been happily using Arch. I'm quite a seasoned user. I've solved countless errors and problems with my systems on 3 different machines, but I don't know how to fix this one. I've searched the forum and asked google -- got no answer.
Since systemd upgrade on my Asus laptop, shutdown and reboot broke down. The other machine with Arch works fine (systemd installed), but that's a stationary computer.
I don't know what may be wrong... The system is upgraded to the full. The error displayed by kernel is as follows:
Kernel panic - not syncing: Attempted to kill init!
And photo of it happening: http://i.imgur.com/kewfbYv.jpg
This happens every time I try to shut down or reboot the laptop. (I'm using the poweroff and reboot commands). I have to press the power button for a while to force poweroff. It's really annoying.
Everything works just fine except this kernel panic. I'm using catalyst drivers. Other than that - nothing "unusual".
Boot journal:
-- Logs begin at Mon 2012-12-31 05:00:25 CET, end at Sat 2013-01-26 12:27:00 CET. --
Jan 26 12:20:45 further systemd-journal[145]: Allowing runtime journal files to grow to 171.5M.
Jan 26 12:20:45 further kernel: Initializing cgroup subsys cpuset
Jan 26 12:20:45 further kernel: Initializing cgroup subsys cpu
Jan 26 12:20:45 further kernel: Linux version 3.7.4-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 2013
Jan 26 12:20:45 further kernel: Command line: root=/dev/sda6 ro nomodeset init=/sbin/init rootfstype=ext4
Jan 26 12:20:45 further kernel: e820: BIOS-provided physical RAM map:
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x0000000000100000-0x000000008f6bffff] usable
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f6c0000-0x000000008f702fff] ACPI NVS
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f703000-0x000000008f711fff] ACPI data
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f712000-0x000000008f828fff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f829000-0x000000008f838fff] ACPI NVS
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f839000-0x000000008f867fff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f868000-0x000000008f868fff] usable
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f869000-0x000000008f871fff] ACPI NVS
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f872000-0x000000008f883fff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f884000-0x000000008f891fff] ACPI NVS
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f892000-0x000000008f893fff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f894000-0x000000008f89afff] ACPI NVS
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f89b000-0x000000008f89dfff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f89e000-0x000000008f8a6fff] ACPI NVS
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f8a7000-0x000000008f8cdfff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f8ce000-0x000000008fad0fff] ACPI NVS
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008fad1000-0x000000008fd45fff] usable
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008fd46000-0x000000008fef6fff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008fef7000-0x000000008fefffff] usable
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fed61000-0x00000000fed70fff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x0000000100001000-0x000000014effffff] usable
Jan 26 12:20:45 further kernel: NX (Execute Disable) protection: active
Jan 26 12:20:45 further kernel: DMI 2.7 present.
Jan 26 12:20:45 further kernel: DMI: ASUSTeK Computer Inc. K43TA/K43TA, BIOS 214 04/06/2012
Jan 26 12:20:45 further kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
Jan 26 12:20:45 further kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jan 26 12:20:45 further kernel: No AGP bridge found
Jan 26 12:20:45 further kernel: e820: last_pfn = 0x14f000 max_arch_pfn = 0x400000000
Jan 26 12:20:45 further kernel: MTRR default type: uncachable
Jan 26 12:20:45 further kernel: MTRR fixed ranges enabled:
Jan 26 12:20:45 further kernel: 00000-9FFFF write-back
Jan 26 12:20:45 further kernel: A0000-BFFFF write-through
Jan 26 12:20:45 further kernel: C0000-CEFFF write-protect
Jan 26 12:20:45 further kernel: CF000-E7FFF uncachable
Jan 26 12:20:45 further kernel: E8000-FFFFF write-protect
Jan 26 12:20:45 further kernel: MTRR variable ranges enabled:
Jan 26 12:20:45 further kernel: 0 base 0000000000 mask FF80000000 write-back
Jan 26 12:20:45 further kernel: 1 base 0080000000 mask FFF0000000 write-back
Jan 26 12:20:45 further kernel: 2 base 008FF00000 mask FFFFF00000 uncachable
Jan 26 12:20:45 further kernel: 3 disabled
Jan 26 12:20:45 further kernel: 4 disabled
Jan 26 12:20:45 further kernel: 5 disabled
Jan 26 12:20:45 further kernel: 6 disabled
Jan 26 12:20:45 further kernel: 7 disabled
Jan 26 12:20:45 further kernel: TOM2: 000000014f000000 aka 5360M
Jan 26 12:20:45 further kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jan 26 12:20:45 further kernel: e820: update [mem 0x8ff00000-0xffffffff] usable ==> reserved
Jan 26 12:20:45 further kernel: e820: last_pfn = 0x8ff00 max_arch_pfn = 0x400000000
Jan 26 12:20:45 further kernel: found SMP MP-table at [mem 0x000fce90-0x000fce9f] mapped at [ffff8800000fce90]
Jan 26 12:20:45 further kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
Jan 26 12:20:45 further kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Jan 26 12:20:45 further kernel: Using GB pages for direct mapping
Jan 26 12:20:45 further kernel: init_memory_mapping: [mem 0x00000000-0x8fefffff]
Jan 26 12:20:45 further kernel: [mem 0x00000000-0x7fffffff] page 1G
Jan 26 12:20:45 further kernel: [mem 0x80000000-0x8fdfffff] page 2M
Jan 26 12:20:45 further kernel: [mem 0x8fe00000-0x8fefffff] page 4k
Jan 26 12:20:45 further kernel: kernel direct mapping tables up to 0x8fefffff @ [mem 0x1fffd000-0x1fffffff]
Jan 26 12:20:45 further kernel: init_memory_mapping: [mem 0x100001000-0x14effffff]
Jan 26 12:20:45 further kernel: [mem 0x100001000-0x1001fffff] page 4k
Jan 26 12:20:45 further kernel: [mem 0x100200000-0x14effffff] page 2M
Jan 26 12:20:45 further kernel: kernel direct mapping tables up to 0x14effffff @ [mem 0x8fefc000-0x8fefffff]
Jan 26 12:20:45 further kernel: RAMDISK: [mem 0x37d07000-0x37feffff]
Jan 26 12:20:45 further kernel: ACPI: RSDP 00000000000f0450 00024 (v02 _ASUS_)
Jan 26 12:20:45 further kernel: ACPI: XSDT 000000008f703068 00054 (v01 _ASUS_ Notebook 01072009 AMI 00010013)
Jan 26 12:20:45 further kernel: ACPI: FACP 000000008f70f1a0 000F4 (v04 _ASUS_ Notebook 01072009 AMI 00010013)
Jan 26 12:20:45 further kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20120913/tbfadt-598)
Jan 26 12:20:45 further kernel: ACPI: DSDT 000000008f703150 0C050 (v02 _ASUS_ Notebook 00000000 INTL 20091112)
Jan 26 12:20:45 further kernel: ACPI: FACS 000000008f89af80 00040
Jan 26 12:20:45 further kernel: ACPI: APIC 000000008f70f298 00072 (v03 _ASUS_ Notebook 01072009 AMI 00010013)
Jan 26 12:20:45 further kernel: ACPI: MCFG 000000008f70f310 0003C (v01 _ASUS_ GMCH945. 01072009 MSFT 00000097)
Jan 26 12:20:45 further kernel: ACPI: HPET 000000008f70f350 00038 (v01 _ASUS_ Notebook 01072009 AMI 00000004)
Jan 26 12:20:45 further kernel: ACPI: SSDT 000000008f70f388 00726 (v01 _ASUS_ POWERNOW 00000001 AMD 00000001)
Jan 26 12:20:45 further kernel: ACPI: SSDT 000000008f70fab0 0190A (v02 _ASUS_ ALIB 00000001 MSFT 04000000)
Jan 26 12:20:45 further kernel: ACPI: Local APIC address 0xfee00000
Jan 26 12:20:45 further kernel: No NUMA configuration found
Jan 26 12:20:45 further kernel: Faking a node at [mem 0x0000000000000000-0x000000014effffff]
Jan 26 12:20:45 further kernel: Initmem setup node 0 [mem 0x00000000-0x14effffff]
Jan 26 12:20:45 further kernel: NODE_DATA [mem 0x14effc000-0x14effffff]
Jan 26 12:20:45 further kernel: [ffffea0000000000-ffffea00053fffff] PMD -> [ffff88014ae00000-ffff88014e5fffff] on node 0
Jan 26 12:20:45 further kernel: Zone ranges:
Jan 26 12:20:45 further kernel: DMA [mem 0x00010000-0x00ffffff]
Jan 26 12:20:45 further kernel: DMA32 [mem 0x01000000-0xffffffff]
Jan 26 12:20:45 further kernel: Normal [mem 0x100000000-0x14effffff]
Jan 26 12:20:45 further kernel: Movable zone start for each node
Jan 26 12:20:45 further kernel: Early memory node ranges
Jan 26 12:20:45 further kernel: node 0: [mem 0x00010000-0x0009cfff]
Jan 26 12:20:45 further kernel: node 0: [mem 0x00100000-0x8f6bffff]
Jan 26 12:20:45 further kernel: node 0: [mem 0x8f868000-0x8f868fff]
Jan 26 12:20:45 further kernel: node 0: [mem 0x8fad1000-0x8fd45fff]
Jan 26 12:20:45 further kernel: node 0: [mem 0x8fef7000-0x8fefffff]
Jan 26 12:20:45 further kernel: node 0: [mem 0x100001000-0x14effffff]
Jan 26 12:20:45 further kernel: On node 0 totalpages: 911563
Jan 26 12:20:45 further kernel: DMA zone: 64 pages used for memmap
Jan 26 12:20:45 further kernel: DMA zone: 6 pages reserved
Jan 26 12:20:45 further kernel: DMA zone: 3911 pages, LIFO batch:0
Jan 26 12:20:45 further kernel: DMA32 zone: 16320 pages used for memmap
Jan 26 12:20:45 further kernel: DMA32 zone: 567679 pages, LIFO batch:31
Jan 26 12:20:45 further kernel: Normal zone: 5056 pages used for memmap
Jan 26 12:20:45 further kernel: Normal zone: 318527 pages, LIFO batch:31
Jan 26 12:20:45 further kernel: ACPI: PM-Timer IO Port: 0x808
Jan 26 12:20:45 further kernel: ACPI: Local APIC address 0xfee00000
Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
Jan 26 12:20:45 further kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Jan 26 12:20:45 further kernel: ACPI: IOAPIC (id[0x03] address[0xfec00000] gsi_base[0])
Jan 26 12:20:45 further kernel: IOAPIC[0]: apic_id 3, version 33, address 0xfec00000, GSI 0-23
Jan 26 12:20:45 further kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jan 26 12:20:45 further kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
Jan 26 12:20:45 further kernel: ACPI: IRQ0 used by override.
Jan 26 12:20:45 further kernel: ACPI: IRQ2 used by override.
Jan 26 12:20:45 further kernel: ACPI: IRQ9 used by override.
Jan 26 12:20:45 further kernel: Using ACPI (MADT) for SMP configuration information
Jan 26 12:20:45 further kernel: ACPI: HPET id: 0xffffffff base: 0xfed00000
Jan 26 12:20:45 further kernel: smpboot: Allowing 4 CPUs, 2 hotplug CPUs
Jan 26 12:20:45 further kernel: nr_irqs_gsi: 40
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000000009d000 - 000000000009e000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000000009e000 - 00000000000a0000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f6c0000 - 000000008f703000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f703000 - 000000008f712000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f712000 - 000000008f829000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f829000 - 000000008f839000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f839000 - 000000008f868000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f869000 - 000000008f872000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f872000 - 000000008f884000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f884000 - 000000008f892000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f892000 - 000000008f894000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f894000 - 000000008f89b000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f89b000 - 000000008f89e000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f89e000 - 000000008f8a7000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f8a7000 - 000000008f8ce000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f8ce000 - 000000008fad1000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008fd46000 - 000000008fef7000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008ff00000 - 00000000e0000000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000f0000000 - 00000000fec00000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec01000 - 00000000fec10000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec10000 - 00000000fec11000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec11000 - 00000000fed00000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed00000 - 00000000fed01000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed01000 - 00000000fed61000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed61000 - 00000000fed71000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed71000 - 00000000fed80000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed80000 - 00000000fed90000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed90000 - 00000000ff000000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000ff000000 - 0000000100000000
Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 0000000100000000 - 0000000100001000
Jan 26 12:20:45 further kernel: e820: [mem 0x8ff00000-0xdfffffff] available for PCI devices
Jan 26 12:20:45 further kernel: Booting paravirtualized kernel on bare hardware
Jan 26 12:20:45 further kernel: setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1
Jan 26 12:20:45 further kernel: PERCPU: Embedded 28 pages/cpu @ffff88014ec00000 s84544 r8192 d21952 u524288
Jan 26 12:20:45 further kernel: pcpu-alloc: s84544 r8192 d21952 u524288 alloc=1*2097152
Jan 26 12:20:45 further kernel: pcpu-alloc: [0] 0 1 2 3
Jan 26 12:20:45 further kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 890117
Jan 26 12:20:45 further kernel: Policy zone: Normal
Jan 26 12:20:45 further kernel: Kernel command line: root=/dev/sda6 ro nomodeset init=/sbin/init rootfstype=ext4
Jan 26 12:20:45 further kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Jan 26 12:20:45 further kernel: __ex_table already sorted, skipping sort
Jan 26 12:20:45 further kernel: Checking aperture...
Jan 26 12:20:45 further kernel: No AGP bridge found
Jan 26 12:20:45 further kernel: Calgary: detecting Calgary via BIOS EBDA area
Jan 26 12:20:45 further kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jan 26 12:20:45 further kernel: Memory: 3508092k/5488640k available (4832k kernel code, 1842388k absent, 138160k reserved, 4077k data, 808k init)
Jan 26 12:20:45 further kernel: SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Jan 26 12:20:45 further kernel: Preemptible hierarchical RCU implementation.
Jan 26 12:20:45 further kernel: RCU dyntick-idle grace-period acceleration is enabled.
Jan 26 12:20:45 further kernel: Dump stacks of tasks blocking RCU-preempt GP.
Jan 26 12:20:45 further kernel: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
Jan 26 12:20:45 further kernel: NR_IRQS:4352 nr_irqs:712 16
Jan 26 12:20:45 further kernel: Extended CMOS year: 2000
Jan 26 12:20:45 further kernel: Console: colour VGA+ 80x25
Jan 26 12:20:45 further kernel: console [tty0] enabled
Jan 26 12:20:45 further kernel: allocated 14680064 bytes of page_cgroup
Jan 26 12:20:45 further kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jan 26 12:20:45 further kernel: hpet clockevent registered
Jan 26 12:20:45 further kernel: tsc: Fast TSC calibration using PIT
Jan 26 12:20:45 further kernel: tsc: Detected 1896.600 MHz processor
Jan 26 12:20:45 further kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3794.25 BogoMIPS (lpj=6322000)
Jan 26 12:20:45 further kernel: pid_max: default: 32768 minimum: 301
Jan 26 12:20:45 further kernel: Security Framework initialized
Jan 26 12:20:45 further kernel: AppArmor: AppArmor disabled by boot time parameter
Jan 26 12:20:45 further kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Jan 26 12:20:45 further kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Jan 26 12:20:45 further kernel: Mount-cache hash table entries: 256
Jan 26 12:20:45 further kernel: Initializing cgroup subsys cpuacct
Jan 26 12:20:45 further kernel: Initializing cgroup subsys memory
Jan 26 12:20:45 further kernel: Initializing cgroup subsys devices
Jan 26 12:20:45 further kernel: Initializing cgroup subsys freezer
Jan 26 12:20:45 further kernel: Initializing cgroup subsys net_cls
Jan 26 12:20:45 further kernel: Initializing cgroup subsys blkio
Jan 26 12:20:45 further kernel: tseg: 008ff00000
Jan 26 12:20:45 further kernel: CPU: Physical Processor ID: 0
Jan 26 12:20:45 further kernel: CPU: Processor Core ID: 0
Jan 26 12:20:45 further kernel: mce: CPU supports 6 MCE banks
Jan 26 12:20:45 further kernel: [120B blob data]
Jan 26 12:20:45 further kernel: Freeing SMP alternatives: 16k freed
Jan 26 12:20:45 further kernel: ACPI: Core revision 20120913
Jan 26 12:20:45 further kernel: ftrace: allocating 18585 entries in 73 pages
Jan 26 12:20:45 further kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jan 26 12:20:45 further kernel: smpboot: CPU0: AMD A4-3300M APU with Radeon(tm) HD Graphics (fam: 12, model: 01, stepping: 00)
Jan 26 12:20:45 further kernel: Performance Events: AMD PMU driver.
Jan 26 12:20:45 further kernel: ... version: 0
Jan 26 12:20:45 further kernel: ... bit width: 48
Jan 26 12:20:45 further kernel: ... generic registers: 4
Jan 26 12:20:45 further kernel: ... value mask: 0000ffffffffffff
Jan 26 12:20:45 further kernel: ... max period: 00007fffffffffff
Jan 26 12:20:45 further kernel: ... fixed-purpose events: 0
Jan 26 12:20:45 further kernel: ... event mask: 000000000000000f
Jan 26 12:20:45 further kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jan 26 12:20:45 further kernel: smpboot: Booting Node 0, Processors #1
Jan 26 12:20:45 further kernel: Brought up 2 CPUs
Jan 26 12:20:45 further kernel: smpboot: Total of 2 processors activated (7589.50 BogoMIPS)
Jan 26 12:20:45 further kernel: devtmpfs: initialized
Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f6c0000-0x8f702fff] (274432 bytes)
Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f829000-0x8f838fff] (65536 bytes)
Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f869000-0x8f871fff] (36864 bytes)
Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f884000-0x8f891fff] (57344 bytes)
Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f894000-0x8f89afff] (28672 bytes)
Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f89e000-0x8f8a6fff] (36864 bytes)
Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f8ce000-0x8fad0fff] (2109440 bytes)
Jan 26 12:20:45 further kernel: NET: Registered protocol family 16
Jan 26 12:20:45 further kernel: ACPI: bus type pci registered
Jan 26 12:20:45 further kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Jan 26 12:20:45 further kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
Jan 26 12:20:45 further kernel: PCI: Using configuration type 1 for base access
Jan 26 12:20:45 further kernel: bio: create slab <bio-0> at 0
Jan 26 12:20:45 further kernel: ACPI: Added _OSI(Module Device)
Jan 26 12:20:45 further kernel: ACPI: Added _OSI(Processor Device)
Jan 26 12:20:45 further kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Jan 26 12:20:45 further kernel: ACPI: Added _OSI(Processor Aggregator Device)
Jan 26 12:20:45 further kernel: ACPI: EC: Look up EC in DSDT
Jan 26 12:20:45 further kernel: ACPI: Executed 1 blocks of module-level executable AML code
Jan 26 12:20:45 further kernel: ACPI: Interpreter enabled
Jan 26 12:20:45 further kernel: ACPI: (supports S0 S3 S4 S5)
Jan 26 12:20:45 further kernel: ACPI: Using IOAPIC for interrupt routing
Jan 26 12:20:45 further kernel: [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
Jan 26 12:20:45 further kernel: [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
Jan 26 12:20:45 further kernel: ACPI: EC: GPE = 0x3, I/O: command/status = 0x66, data = 0x62
Jan 26 12:20:45 further kernel: ACPI: No dock devices found.
Jan 26 12:20:45 further kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jan 26 12:20:45 further kernel: \_SB_.PCI0:_OSC request failed
Jan 26 12:20:45 further kernel: _OSC request data:1 8 1f
Jan 26 12:20:45 further kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Jan 26 12:20:45 further kernel: PCI host bridge to bus 0000:00
Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x03af]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x03b0-0x03df]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x1778-0xffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [mem 0xb0000000-0xffffffff]
Jan 26 12:20:45 further kernel: pci 0000:00:00.0: [1022:1705] type 00 class 0x060000
Jan 26 12:20:45 further kernel: pci 0000:00:01.0: [1002:9648] type 00 class 0x030000
Jan 26 12:20:45 further kernel: pci 0000:00:01.0: reg 10: [mem 0xb0000000-0xbfffffff pref]
Jan 26 12:20:45 further kernel: pci 0000:00:01.0: reg 14: [io 0xf000-0xf0ff]
Jan 26 12:20:45 further kernel: pci 0000:00:01.0: reg 18: [mem 0xfeb00000-0xfeb3ffff]
Jan 26 12:20:45 further kernel: pci 0000:00:01.0: supports D1 D2
Jan 26 12:20:45 further kernel: pci 0000:00:01.1: [1002:1714] type 00 class 0x040300
Jan 26 12:20:45 further kernel: pci 0000:00:01.1: reg 10: [mem 0xfeb44000-0xfeb47fff]
Jan 26 12:20:45 further kernel: pci 0000:00:01.1: supports D1 D2
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: [1022:1707] type 01 class 0x060400
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jan 26 12:20:45 further kernel: pci 0000:00:04.0: [1022:1709] type 01 class 0x060400
Jan 26 12:20:45 further kernel: pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
Jan 26 12:20:45 further kernel: pci 0000:00:05.0: [1022:170a] type 01 class 0x060400
Jan 26 12:20:45 further kernel: pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
Jan 26 12:20:45 further kernel: pci 0000:00:10.0: [1022:7812] type 00 class 0x0c0330
Jan 26 12:20:45 further kernel: pci 0000:00:10.0: reg 10: [mem 0xfeb48000-0xfeb49fff 64bit]
Jan 26 12:20:45 further kernel: pci 0000:00:10.0: PME# supported from D0 D3hot D3cold
Jan 26 12:20:45 further kernel: pci 0000:00:11.0: [1022:7801] type 00 class 0x010601
Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 10: [io 0xf140-0xf147]
Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 14: [io 0xf130-0xf133]
Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 18: [io 0xf120-0xf127]
Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 1c: [io 0xf110-0xf113]
Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 20: [io 0xf100-0xf10f]
Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 24: [mem 0xfeb4d000-0xfeb4d7ff]
Jan 26 12:20:45 further kernel: pci 0000:00:12.0: [1022:7807] type 00 class 0x0c0310
Jan 26 12:20:45 further kernel: pci 0000:00:12.0: reg 10: [mem 0xfeb4c000-0xfeb4cfff]
Jan 26 12:20:45 further kernel: pci 0000:00:12.2: [1022:7808] type 00 class 0x0c0320
Jan 26 12:20:45 further kernel: pci 0000:00:12.2: reg 10: [mem 0xfeb4b000-0xfeb4b0ff]
Jan 26 12:20:45 further kernel: pci 0000:00:12.2: supports D1 D2
Jan 26 12:20:45 further kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
Jan 26 12:20:45 further kernel: pci 0000:00:14.0: [1022:780b] type 00 class 0x0c0500
Jan 26 12:20:45 further kernel: pci 0000:00:14.2: [1022:780d] type 00 class 0x040300
Jan 26 12:20:45 further kernel: pci 0000:00:14.2: reg 10: [mem 0xfeb40000-0xfeb43fff 64bit]
Jan 26 12:20:45 further kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
Jan 26 12:20:45 further kernel: pci 0000:00:14.3: [1022:780e] type 00 class 0x060100
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: [1022:780f] type 01 class 0x060401
Jan 26 12:20:45 further kernel: pci 0000:00:14.7: [1022:7806] type 00 class 0x080501
Jan 26 12:20:45 further kernel: pci 0000:00:14.7: reg 10: [mem 0xfeb4a000-0xfeb4a0ff 64bit]
Jan 26 12:20:45 further kernel: pci 0000:00:18.0: [1022:1700] type 00 class 0x060000
Jan 26 12:20:45 further kernel: pci 0000:00:18.1: [1022:1701] type 00 class 0x060000
Jan 26 12:20:45 further kernel: pci 0000:00:18.2: [1022:1702] type 00 class 0x060000
Jan 26 12:20:45 further kernel: pci 0000:00:18.3: [1022:1703] type 00 class 0x060000
Jan 26 12:20:45 further kernel: pci 0000:00:18.4: [1022:1704] type 00 class 0x060000
Jan 26 12:20:45 further kernel: pci 0000:00:18.5: [1022:1718] type 00 class 0x060000
Jan 26 12:20:45 further kernel: pci 0000:00:18.6: [1022:1716] type 00 class 0x060000
Jan 26 12:20:45 further kernel: pci 0000:00:18.7: [1022:1719] type 00 class 0x060000
Jan 26 12:20:45 further kernel: pci 0000:01:00.0: [1002:6741] type 00 class 0x030000
Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 10: [mem 0xc0000000-0xcfffffff 64bit pref]
Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 18: [mem 0xfea20000-0xfea3ffff 64bit]
Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 20: [io 0xe000-0xe0ff]
Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 30: [mem 0xfea00000-0xfea1ffff pref]
Jan 26 12:20:45 further kernel: pci 0000:01:00.0: supports D1 D2
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xfea00000-0xfeafffff]
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
Jan 26 12:20:45 further kernel: pci 0000:02:00.0: [10ec:8168] type 00 class 0x020000
Jan 26 12:20:45 further kernel: pci 0000:02:00.0: reg 10: [io 0xd000-0xd0ff]
Jan 26 12:20:45 further kernel: pci 0000:02:00.0: reg 18: [mem 0xd0004000-0xd0004fff 64bit pref]
Jan 26 12:20:45 further kernel: pci 0000:02:00.0: reg 20: [mem 0xd0000000-0xd0003fff 64bit pref]
Jan 26 12:20:45 further kernel: pci 0000:02:00.0: supports D1 D2
Jan 26 12:20:45 further kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Jan 26 12:20:45 further kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
Jan 26 12:20:45 further kernel: pci 0000:03:00.0: [168c:002b] type 00 class 0x028000
Jan 26 12:20:45 further kernel: pci 0000:03:00.0: reg 10: [mem 0xfe900000-0xfe90ffff 64bit]
Jan 26 12:20:45 further kernel: pci 0000:03:00.0: supports D1
Jan 26 12:20:45 further kernel: pci 0000:03:00.0: PME# supported from D0 D1 D3hot D3cold
Jan 26 12:20:45 further kernel: pci 0000:00:05.0: PCI bridge to [bus 03]
Jan 26 12:20:45 further kernel: pci 0000:00:05.0: bridge window [mem 0xfe900000-0xfe9fffff]
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: PCI bridge to [bus 04] (subtractive decode)
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x0000-0x03af] (subtractive decode)
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x03e0-0x0cf7] (subtractive decode)
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x03b0-0x03df] (subtractive decode)
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x1778-0xffff] (subtractive decode)
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [mem 0xb0000000-0xffffffff] (subtractive decode)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR14._PRT]
Jan 26 12:20:45 further kernel: \_SB_.PCI0:_OSC request failed
Jan 26 12:20:45 further kernel: _OSC request data:1 1f 1f
Jan 26 12:20:45 further kernel: pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM
Jan 26 12:20:45 further kernel: pci0000:00: Unable to request _OSC control (_OSC support mask: 0x08)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN24] (IRQs *24)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN25] (IRQs *25)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN26] (IRQs *26)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN27] (IRQs *27)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN28] (IRQs *28)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN29] (IRQs *29)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN30] (IRQs *30)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN31] (IRQs *31)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN32] (IRQs *32)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN33] (IRQs *33)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN34] (IRQs *34)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN35] (IRQs *35)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN36] (IRQs *36)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN37] (IRQs *37)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN38] (IRQs *38)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN39] (IRQs *39)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN40] (IRQs *40)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN41] (IRQs *41)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN42] (IRQs *42)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN43] (IRQs *43)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN44] (IRQs *44)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN45] (IRQs *45)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN46] (IRQs *46)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN47] (IRQs *47)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN48] (IRQs *48)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN49] (IRQs *49)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN50] (IRQs *50)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN51] (IRQs *51)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN52] (IRQs *52)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN53] (IRQs *53)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN54] (IRQs *54)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN55] (IRQs *55)
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 4 5 7 10 11 14 15) *0
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 4 5 7 10 11 14 15) *0
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 11 14 15) *0
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 4 5 7 10 11 14 15) *0
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 11 14 15) *0
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11 14 15) *0
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11 14 15) *0
Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11 14 15) *0
Jan 26 12:20:45 further kernel: vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none
Jan 26 12:20:45 further kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
Jan 26 12:20:45 further kernel: vgaarb: loaded
Jan 26 12:20:45 further kernel: vgaarb: bridge control possible 0000:01:00.0
Jan 26 12:20:45 further kernel: vgaarb: no bridge control possible 0000:00:01.0
Jan 26 12:20:45 further kernel: PCI: Using ACPI for IRQ routing
Jan 26 12:20:45 further kernel: PCI: pci_cache_line_size set to 64 bytes
Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8f6c0000-0x8fffffff]
Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8f869000-0x8fffffff]
Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8fd46000-0x8fffffff]
Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8ff00000-0x8fffffff]
Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x14f000000-0x14fffffff]
Jan 26 12:20:45 further kernel: NetLabel: Initializing
Jan 26 12:20:45 further kernel: NetLabel: domain hash size = 128
Jan 26 12:20:45 further kernel: NetLabel: protocols = UNLABELED CIPSOv4
Jan 26 12:20:45 further kernel: NetLabel: unlabeled traffic allowed by default
Jan 26 12:20:45 further kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
Jan 26 12:20:45 further kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter
Jan 26 12:20:45 further kernel: Switching to clocksource hpet
Jan 26 12:20:45 further kernel: pnp: PnP ACPI init
Jan 26 12:20:45 further kernel: ACPI: bus type pnp registered
Jan 26 12:20:45 further kernel: pnp 00:00: [bus 00-ff]
Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x0cf8-0x0cff]
Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x0000-0x03af window]
Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x03e0-0x0cf7 window]
Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x03b0-0x03df window]
Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x1778-0xffff window]
Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0x000a0000-0x000bffff window]
Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0x000c0000-0x000dffff window]
Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0xb0000000-0xffffffff window]
Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0x00000000 window]
Jan 26 12:20:45 further kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
Jan 26 12:20:45 further kernel: pnp 00:01: [mem 0xe0000000-0xefffffff]
Jan 26 12:20:45 further kernel: system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
Jan 26 12:20:45 further kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0010-0x001f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0022-0x003f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0063]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0065]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0067-0x006f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0072-0x007f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0080]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0084-0x0086]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0088]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x008c-0x008e]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0090-0x009f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x00a2-0x00bf]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x00b1]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x00e0-0x00ef]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x04d0-0x04d1]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x040b]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x04d6]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c00-0x0c01]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c14]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c50-0x0c51]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c52]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c6c]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c6f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd0-0x0cd1]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd2-0x0cd3]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd4-0x0cd5]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd6-0x0cd7]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd8-0x0cdf]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0800-0x089f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0000-0xffffffffffffffff disabled]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0000-0x000f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0b20-0x0b3f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0900-0x090f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0910-0x091f]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0xfe00-0xfefe]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0060-0x005f disabled]
Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0064-0x0063 disabled]
Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfec00000-0xfec00fff]
Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfee00000-0xfee00fff]
Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfed80000-0xfed8ffff]
Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfed61000-0xfed70fff]
Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfec10000-0xfec10fff]
Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfed00000-0xfed00fff]
Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xff000000-0xffffffff]
Jan 26 12:20:45 further kernel: system 00:02: [io 0x04d0-0x04d1] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x040b] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x04d6] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c00-0x0c01] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c14] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c50-0x0c51] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c52] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c6c] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c6f] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd0-0x0cd1] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd2-0x0cd3] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd4-0x0cd5] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd6-0x0cd7] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd8-0x0cdf] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0800-0x089f] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0b20-0x0b3f] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0900-0x090f] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0x0910-0x091f] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [io 0xfe00-0xfefe] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfec00000-0xfec00fff] could not be reserved
Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfee00000-0xfee00fff] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfed80000-0xfed8ffff] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfed61000-0xfed70fff] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfec10000-0xfec10fff] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfed00000-0xfed00fff] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: [mem 0xff000000-0xffffffff] has been reserved
Jan 26 12:20:45 further kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
Jan 26 12:20:45 further kernel: pnp 00:03: [dma 4]
Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0000-0x000f]
Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0081-0x0083]
Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0087]
Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0089-0x008b]
Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x008f]
Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x00c0-0x00df]
Jan 26 12:20:45 further kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0200 (active)
Jan 26 12:20:45 further kernel: pnp 00:04: [io 0x0070-0x0071]
Jan 26 12:20:45 further kernel: pnp 00:04: [irq 8]
Jan 26 12:20:45 further kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
Jan 26 12:20:45 further kernel: pnp 00:05: [io 0x0061]
Jan 26 12:20:45 further kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0010-0x001f]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0022-0x003f]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0044-0x005f]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0072-0x007f]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0080]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0084-0x0086]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0088]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x008c-0x008e]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0090-0x009f]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x00a2-0x00bf]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x00e0-0x00ef]
Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x04d0-0x04d1]
Jan 26 12:20:45 further kernel: system 00:06: [io 0x04d0-0x04d1] has been reserved
Jan 26 12:20:45 further kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jan 26 12:20:45 further kernel: pnp 00:07: [io 0x00f0-0x00ff]
Jan 26 12:20:45 further kernel: pnp 00:07: [irq 13]
Jan 26 12:20:45 further kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0c04 (active)
Jan 26 12:20:45 further kernel: pnp 00:08: [io 0x1770-0x1777]
Jan 26 12:20:45 further kernel: system 00:08: [io 0x1770-0x1777] has been reserved
Jan 26 12:20:45 further kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
Jan 26 12:20:45 further kernel: pnp 00:09: [irq 12]
Jan 26 12:20:45 further kernel: pnp 00:09: Plug and Play ACPI device, IDs ETD0102 PNP0f13 (active)
Jan 26 12:20:45 further kernel: pnp 00:0a: [io 0x0060]
Jan 26 12:20:45 further kernel: pnp 00:0a: [io 0x0064]
Jan 26 12:20:45 further kernel: pnp 00:0a: [irq 1]
Jan 26 12:20:45 further kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
Jan 26 12:20:45 further kernel: pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled]
Jan 26 12:20:45 further kernel: pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled]
Jan 26 12:20:45 further kernel: system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
Jan 26 12:20:45 further kernel: pnp 00:0c: [mem 0xfed00000-0xfed003ff]
Jan 26 12:20:45 further kernel: pnp 00:0c: Plug and Play ACPI device, IDs PNP0103 (active)
Jan 26 12:20:45 further kernel: pnp: PnP ACPI: found 13 devices
Jan 26 12:20:45 further kernel: ACPI: ACPI bus type pnp unregistered
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xfea00000-0xfeafffff]
Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
Jan 26 12:20:45 further kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
Jan 26 12:20:45 further kernel: pci 0000:00:05.0: PCI bridge to [bus 03]
Jan 26 12:20:45 further kernel: pci 0000:00:05.0: bridge window [mem 0xfe900000-0xfe9fffff]
Jan 26 12:20:45 further kernel: pci 0000:00:14.4: PCI bridge to [bus 04]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x03af]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 6 [io 0x03b0-0x03df]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 7 [io 0x1778-0xffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 10 [mem 0xb0000000-0xffffffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
Jan 26 12:20:45 further kernel: pci_bus 0000:01: resource 1 [mem 0xfea00000-0xfeafffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:01: resource 2 [mem 0xc0000000-0xcfffffff 64bit pref]
Jan 26 12:20:45 further kernel: pci_bus 0000:02: resource 0 [io 0xd000-0xdfff]
Jan 26 12:20:45 further kernel: pci_bus 0000:02: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
Jan 26 12:20:45 further kernel: pci_bus 0000:03: resource 1 [mem 0xfe900000-0xfe9fffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 4 [io 0x0000-0x03af]
Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 5 [io 0x03e0-0x0cf7]
Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 6 [io 0x03b0-0x03df]
Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 7 [io 0x1778-0xffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 8 [mem 0x000a0000-0x000bffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 9 [mem 0x000c0000-0x000dffff]
Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 10 [mem 0xb0000000-0xffffffff]
Jan 26 12:20:45 further kernel: NET: Registered protocol family 2
Jan 26 12:20:45 further kernel: TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
Jan 26 12:20:45 further kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jan 26 12:20:45 further kernel: TCP: Hash tables configured (established 524288 bind 65536)
Jan 26 12:20:45 further kernel: TCP: reno registered
Jan 26 12:20:45 further kernel: UDP hash table entries: 2048 (order: 4, 65536 bytes)
Jan 26 12:20:45 further kernel: UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
Jan 26 12:20:45 further kernel: NET: Registered protocol family 1
Jan 26 12:20:45 further kernel: pci 0000:00:01.0: Boot video device
Jan 26 12:20:45 further kernel: PCI: CLS 64 bytes, default 64
Jan 26 12:20:45 further kernel: Unpacking initramfs...
Jan 26 12:20:45 further kernel: Freeing initrd memory: 2980k freed
Jan 26 12:20:45 further kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jan 26 12:20:45 further kernel: software IO TLB [mem 0x8b6c0000-0x8f6bffff] (64MB) mapped at [ffff88008b6c0000-ffff88008f6bffff]
Jan 26 12:20:45 further kernel: LVT offset 0 assigned for vector 0x400
Jan 26 12:20:45 further kernel: perf: AMD IBS detected (0x000000ff)
Jan 26 12:20:45 further kernel: audit: initializing netlink socket (disabled)
Jan 26 12:20:45 further kernel: type=2000 audit(1359202838.726:1): initialized
Jan 26 12:20:45 further kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jan 26 12:20:45 further kernel: VFS: Disk quotas dquot_6.5.2
Jan 26 12:20:45 further kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jan 26 12:20:45 further kernel: msgmni has been set to 6857
Jan 26 12:20:45 further kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jan 26 12:20:45 further kernel: io scheduler noop registered
Jan 26 12:20:45 further kernel: io scheduler deadline registered
Jan 26 12:20:45 further kernel: io scheduler cfq registered (default)
Jan 26 12:20:45 further kernel: GHES: HEST is not enabled!
Jan 26 12:20:45 further kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Jan 26 12:20:45 further kernel: Linux agpgart interface v0.103
Jan 26 12:20:45 further kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
Jan 26 12:20:45 further kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jan 26 12:20:45 further kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Jan 26 12:20:45 further kernel: mousedev: PS/2 mouse device common for all mice
Jan 26 12:20:45 further kernel: rtc_cmos 00:04: RTC can wake from S4
Jan 26 12:20:45 further kernel: rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
Jan 26 12:20:45 further kernel: rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jan 26 12:20:45 further kernel: cpuidle: using governor ladder
Jan 26 12:20:45 further kernel: cpuidle: using governor menu
Jan 26 12:20:45 further kernel: drop_monitor: Initializing network drop monitor service
Jan 26 12:20:45 further kernel: TCP: cubic registered
Jan 26 12:20:45 further kernel: NET: Registered protocol family 10
Jan 26 12:20:45 further kernel: NET: Registered protocol family 17
Jan 26 12:20:45 further kernel: Key type dns_resolver registered
Jan 26 12:20:45 further kernel: PM: Hibernation image not present or could not be loaded.
Jan 26 12:20:45 further kernel: registered taskstats version 1
Jan 26 12:20:45 further kernel: rtc_cmos 00:04: setting system clock to 2013-01-26 12:20:39 UTC (1359202839)
Jan 26 12:20:45 further kernel: Freeing unused kernel memory: 808k freed
Jan 26 12:20:45 further kernel: Write protecting the kernel read-only data: 8192k
Jan 26 12:20:45 further kernel: Freeing unused kernel memory: 1300k freed
Jan 26 12:20:45 further kernel: Freeing unused kernel memory: 492k freed
Jan 26 12:20:45 further kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
Jan 26 12:20:45 further systemd-udevd[46]: starting version 197
Jan 26 12:20:45 further kernel: ACPI: bus type usb registered
Jan 26 12:20:45 further kernel: usbcore: registered new interface driver usbfs
Jan 26 12:20:45 further kernel: usbcore: registered new interface driver hub
Jan 26 12:20:45 further kernel: SCSI subsystem initialized
Jan 26 12:20:45 further kernel: usbcore: registered new device driver usb
Jan 26 12:20:45 further kernel: sdhci: Secure Digital Host Controller Interface driver
Jan 26 12:20:45 further kernel: sdhci: Copyright(c) Pierre Ossman
Jan 26 12:20:45 further kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: EHCI Host Controller
Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: new USB bus registered, assigned bus number 1
Jan 26 12:20:45 further kernel: QUIRK: Enable AMD PLL fix
Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: debug port 1
Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: irq 17, io mem 0xfeb4b000
Jan 26 12:20:45 further kernel: ACPI: bus type scsi registered
Jan 26 12:20:45 further kernel: libata version 3.00 loaded.
Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00
Jan 26 12:20:45 further kernel: hub 1-0:1.0: USB hub found
Jan 26 12:20:45 further kernel: hub 1-0:1.0: 5 ports detected
Jan 26 12:20:45 further kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan 26 12:20:45 further kernel: ohci_hcd 0000:00:12.0: OHCI Host Controller
Jan 26 12:20:45 further kernel: ohci_hcd 0000:00:12.0: new USB bus registered, assigned bus number 2
Jan 26 12:20:45 further kernel: ohci_hcd 0000:00:12.0: irq 18, io mem 0xfeb4c000
Jan 26 12:20:45 further kernel: hub 2-0:1.0: USB hub found
Jan 26 12:20:45 further kernel: hub 2-0:1.0: 5 ports detected
Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: xHCI Host Controller
Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 3
Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 18, io mem 0xfeb48000
Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 40 for MSI/MSI-X
Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 41 for MSI/MSI-X
Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 42 for MSI/MSI-X
Jan 26 12:20:45 further kernel: xHCI xhci_add_endpoint called for root hub
Jan 26 12:20:45 further kernel: xHCI xhci_check_bandwidth called for root hub
Jan 26 12:20:45 further kernel: hub 3-0:1.0: USB hub found
Jan 26 12:20:45 further kernel: hub 3-0:1.0: 2 ports detected
Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: xHCI Host Controller
Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 4
Jan 26 12:20:45 further kernel: xHCI xhci_add_endpoint called for root hub
Jan 26 12:20:45 further kernel: xHCI xhci_check_bandwidth called for root hub
Jan 26 12:20:45 further kernel: hub 4-0:1.0: USB hub found
Jan 26 12:20:45 further kernel: hub 4-0:1.0: 2 ports detected
Jan 26 12:20:45 further kernel: sdhci-pci 0000:00:14.7: SDHCI controller found [1022:7806] (rev 0)
Jan 26 12:20:45 further kernel: Registered led device: mmc0::
Jan 26 12:20:45 further kernel: mmc0: SDHCI controller on PCI [0000:00:14.7] using ADMA
Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: version 3.0
Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: irq 43 for MSI/MSI-X
Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: AHCI 0001.0300 32 slots 3 ports 3 Gbps 0x7 impl SATA mode
Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part sxs
Jan 26 12:20:45 further kernel: scsi0 : ahci
Jan 26 12:20:45 further kernel: scsi1 : ahci
Jan 26 12:20:45 further kernel: scsi2 : ahci
Jan 26 12:20:45 further kernel: ata1: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d100 irq 43
Jan 26 12:20:45 further kernel: ata2: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d180 irq 43
Jan 26 12:20:45 further kernel: ata3: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d200 irq 43
Jan 26 12:20:45 further kernel: usb 1-3: new high-speed USB device number 2 using ehci_hcd
Jan 26 12:20:45 further kernel: ata3: SATA link down (SStatus 0 SControl 300)
Jan 26 12:20:45 further kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 26 12:20:45 further kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jan 26 12:20:45 further kernel: ata2.00: ATAPI: MATSHITADVD-RAM UJ8B0, 1.00, max UDMA/100
Jan 26 12:20:45 further kernel: ata1.00: ATA-8: WDC WD5000BPVT-80HXZT3, 01.01A01, max UDMA/133
Jan 26 12:20:45 further kernel: ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Jan 26 12:20:45 further kernel: ata1.00: failed to get Identify Device Data, Emask 0x1
Jan 26 12:20:45 further kernel: ata2.00: configured for UDMA/100
Jan 26 12:20:45 further kernel: ata1.00: failed to get Identify Device Data, Emask 0x1
Jan 26 12:20:45 further kernel: ata1.00: configured for UDMA/133
Jan 26 12:20:45 further kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD5000BPVT-8 01.0 PQ: 0 ANSI: 5
Jan 26 12:20:45 further kernel: scsi 1:0:0:0: CD-ROM MATSHITA DVD-RAM UJ8B0 1.00 PQ: 0 ANSI: 5
Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Write Protect is off
Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 26 12:20:45 further kernel: sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 >
Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jan 26 12:20:45 further kernel: sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Jan 26 12:20:45 further kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Jan 26 12:20:45 further kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
Jan 26 12:20:45 further kernel: usb 1-5: new high-speed USB device number 4 using ehci_hcd
Jan 26 12:20:45 further kernel: tsc: Refined TSC clocksource calibration: 1896.550 MHz
Jan 26 12:20:45 further kernel: Switching to clocksource tsc
Jan 26 12:20:45 further kernel: Initializing USB Mass Storage driver...
Jan 26 12:20:45 further kernel: usbcore: registered new interface driver usb-storage
Jan 26 12:20:45 further kernel: USB Mass Storage support registered.
Jan 26 12:20:45 further kernel: usb 2-4: new full-speed USB device number 2 using ohci_hcd
Jan 26 12:20:45 further kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Jan 26 12:20:45 further systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Jan 26 12:20:45 further systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Jan 26 12:20:45 further systemd[1]: Set hostname to <further>.
Jan 26 12:20:45 further systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
Jan 26 12:20:45 further systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
Jan 26 12:20:45 further systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Jan 26 12:20:45 further systemd[1]: Starting Remote File Systems.
Jan 26 12:20:45 further systemd[1]: Reached target Remote File Systems.
Jan 26 12:20:45 further systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
Jan 26 12:20:45 further systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
Jan 26 12:20:45 further systemd[1]: Starting Delayed Shutdown Socket.
Jan 26 12:20:45 further systemd[1]: Listening on Delayed Shutdown Socket.
Jan 26 12:20:45 further systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
Jan 26 12:20:45 further systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Jan 26 12:20:45 further systemd[1]: Starting udev Kernel Socket.
Jan 26 12:20:45 further systemd[1]: Listening on udev Kernel Socket.
Jan 26 12:20:45 further systemd[1]: Starting udev Control Socket.
Jan 26 12:20:45 further systemd[1]: Listening on udev Control Socket.
Jan 26 12:20:45 further systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
Jan 26 12:20:45 further systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Jan 26 12:20:45 further systemd[1]: Starting Encrypted Volumes.
Jan 26 12:20:45 further systemd[1]: Reached target Encrypted Volumes.
Jan 26 12:20:45 further systemd[1]: Expecting device dev-disk-by\x2duuid-f71c0eee\x2da4ec\x2d43a0\x2d89c7\x2d51f13a79169a.device...
Jan 26 12:20:45 further systemd[1]: Expecting device dev-disk-by\x2duuid-26f87130\x2d99b7\x2d4a00\x2d997c\x2de177c335f448.device...
Jan 26 12:20:45 further systemd[1]: Expecting device dev-disk-by\x2duuid-6c6af8e9\x2dbd25\x2d463b\x2dae87\x2dc894d7b092b5.device...
Jan 26 12:20:45 further systemd[1]: Starting Journal Socket.
Jan 26 12:20:45 further systemd[1]: Listening on Journal Socket.
Jan 26 12:20:45 further systemd[1]: Started File System Check on Root Device.
Jan 26 12:20:45 further systemd[1]: Starting Remount Root and Kernel File Systems...
Jan 26 12:20:45 further systemd[1]: Starting Load Kernel Modules...
Jan 26 12:20:45 further systemd[1]: Mounting Huge Pages File System...
Jan 26 12:20:45 further systemd[1]: Starting udev Coldplug all Devices...
Jan 26 12:20:45 further systemd[1]: Started Set Up Additional Binary Formats.
Jan 26 12:20:45 further systemd[1]: Starting Setup Virtual Console...
Jan 26 12:20:45 further systemd[1]: Mounting POSIX Message Queue File System...
Jan 26 12:20:45 further systemd[1]: Starting udev Kernel Device Manager...
Jan 26 12:20:45 further systemd[1]: Starting Apply Kernel Variables...
Jan 26 12:20:45 further systemd[1]: Mounting Debug File System...
Jan 26 12:20:45 further systemd[1]: Starting Journal Service...
Jan 26 12:20:45 further systemd[1]: Started Journal Service.
Jan 26 12:20:45 further systemd-udevd[142]: starting version 197
Jan 26 12:20:45 further systemd-journal[145]: Journal started
Jan 26 12:20:45 further systemd[1]: Started Apply Kernel Variables.
Jan 26 12:20:45 further systemd[1]: Mounted Debug File System.
Jan 26 12:20:45 further systemd[1]: Mounted Huge Pages File System.
Jan 26 12:20:45 further systemd[1]: Started udev Coldplug all Devices.
Jan 26 12:20:45 further systemd[1]: Mounted POSIX Message Queue File System.
Jan 26 12:20:45 further systemd[1]: Started udev Kernel Device Manager.
Jan 26 12:20:45 further kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
Jan 26 12:20:45 further kernel: ACPI: Power Button [PWRB]
Jan 26 12:20:45 further kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
Jan 26 12:20:45 further kernel: ACPI: Sleep Button [SLPB]
Jan 26 12:20:45 further kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
Jan 26 12:20:45 further kernel: ACPI: Lid Switch [LID]
Jan 26 12:20:45 further kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Jan 26 12:20:45 further kernel: ACPI: Power Button [PWRF]
Jan 26 12:20:45 further kernel: AMD IOMMUv2 driver by Joerg Roedel <[email protected]>
Jan 26 12:20:45 further kernel: AMD IOMMUv2 functionality not available on this system
Jan 26 12:20:45 further kernel: EXT4-fs (sda6): re-mounted. Opts: barrier=0
Jan 26 12:20:45 further systemd[1]: Started Remount Root and Kernel File Systems.
Jan 26 12:20:45 further systemd[1]: Starting Local File Systems (Pre).
Jan 26 12:20:45 further systemd[1]: Reached target Local File Systems (Pre).
Jan 26 12:20:45 further systemd[1]: Mounting /tmp...
Jan 26 12:20:45 further systemd[1]: Starting Load Random Seed...
Jan 26 12:20:45 further systemd[1]: Mounted /tmp.
Jan 26 12:20:45 further kernel: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
Jan 26 12:20:45 further kernel: Disabling lock debugging due to kernel taint
Jan 26 12:20:45 further systemd-modules-load[136]: Inserted module 'fglrx'
Jan 26 12:20:45 further kernel: <6>[fglrx] Maximum main memory to use for locked dma buffers: 3278 MBytes.
Jan 26 12:20:45 further kernel: <6>[fglrx] vendor: 1002 device: 9648 count: 1
Jan 26 12:20:45 further kernel: <6>[fglrx] vendor: 1002 device: 6741 count: 2
Jan 26 12:20:45 further kernel: <6>[fglrx] ioport: bar 1, base 0xf000, size: 0x100
Jan 26 12:20:45 further kernel: <6>[fglrx] ioport: bar 4, base 0xe000, size: 0x100
Jan 26 12:20:45 further kernel: pci 0000:01:00.0: enabling device (0000 -> 0003)
Jan 26 12:20:45 further kernel: <6>[fglrx] Kernel PAT support is enabled
Jan 26 12:20:45 further kernel: <6>[fglrx] module loaded - fglrx 9.1.11 [Dec 19 2012] with 2 minors
Jan 26 12:20:45 further systemd[1]: Started Load Kernel Modules.
Jan 26 12:20:45 further systemd[1]: Mounted FUSE Control File System.
Jan 26 12:20:45 further systemd[1]: Mounted Configuration File System.
Jan 26 12:20:45 further systemd[1]: Started Load Random Seed.
Jan 26 12:20:45 furtherDuring boot there is a problem with your fglrx driver. It tries to use MSI interrupts instead of old pin-based method, but it is allready enabled and it warns you http://lxr.linux.no/linux+v3.7.4/drivers/pci/msi.c#L811 in line 828
And during shutdown there is a problem with pci_msi_shutdown. Maybe this problems related with each other?
try to disable globaly msi by adding nomsi to kernel options. If this help try to disable msi just for catalyst after boot by echo 0 in /sys/bus/pci/devices/[faulty device]/msi_bus
try to raise debug level to see message dev_dbg(dev, "shutdown\n"); here http://lxr.linux.no/linux+v3.7.4/drivers/base/core.c#L , open an entry in bugzilla
try do upgrade or downgrade catalyst if possible
switch to open source driver -
PL/SQL procedure to kill inactive session
Hi all ,
Please i am trying to write a procedure to kill inactive sessions of the shema 'TESTSCHEMA' .This is my first procedure , am not use to pl/sql but i went through many turtorial but have some errors at compliation .when i try to compile the procedure the errors are as below :
15:50:28 Start Find Objects [TESTSCHEMA@TESTDB_UNIX(2)] ...
15:50:28 End Find Objects [TESTSCHEMA@ TESTDB_UNIX(2)]
15:50:32 Start Compiling 1 object(s) ...
15:50:32 Executing ALTER PROCEDURE fib_dead_cnx_cleanup COMPILE ...
15:50:32 [13:2] PL/SQL: ORA-00933: SQL command not properly ended
15:50:32 [9:3] PL/SQL: SQL Statement ignored
15:50:32 [18:12] PLS-00103: Encountered the symbol "(" when expecting one of the following:
15:50:32 constant exception <an identifier>
15:50:32 <a double-quoted delimited-identifier> table LONG_ double ref
15:50:32 char time timestamp interval date binary national character
15:50:32 nchar
15:50:32 The symbol "<an identifier>" was substituted for "(" to continue.
15:50:32 [18:21] PLS-00103: Encountered the symbol "LOOP" when expecting one of the following:
15:50:32 := ; not null default character
15:50:32 The symbol "; was inserted before "LOOP" to continue.
15:50:32 [27:8] PLS-00103: Encountered the symbol "ALTER" when expecting one of the following:
15:50:32 begin case declare exit for goto if loop mod null pragma
15:50:32 raise return select update while with <an identifier>
15:50:32 <a double-quoted delimited-identifier> <a bind variable> <<
15:50:32 close current delete fetch lock insert open rollback
15:50:32 savepoint set sql execute commit forall merge pipe
15:50:32 Compilation complete - 5 error(s) found
15:50:32 End Compiling 1 object(s)
below is the procedure code :
CREATE OR REPLACE
PROCEDURE fib_dead_cnx_cleanup
AS
l_serial CHAR(100);
l_sid CHAR (100);
l_sid_serial CHAR(100);
l_count NUMBER(10,0);
CURSOR session_cur IS
SELECT sid,serial#,sid||','||serial# as sid_serial
FROM v$session
WHERE username='EBBFCAT' and schemaname='TESTSCHEMA'
and status='INACTIVE'
BEGIN
BEGIN
l_count := 0;
OPEN session_cur;
WHILE ( 1 = 1) LOOP
BEGIN
FETCH session_cur INTO l_sid ,l_serial,l_sid_serial ;
EXIT WHEN session_cur%NOTFOUND ;
BEGIN
alter system kill session 'l_sid_serial' ;
END;
END;
END;
CLOSE session_cur;
END;
END FIB_DEAD_CNX_CLEANUP;
ThanksHi,
Never write, let alone post, unformatted code.
When posting any formatted text on this site, type these 6 characters:
{code}
(small letters only, inside curly brackets) before and after sections of formatted text, to preserve spacing.
Among the benefits of formatting: you can indent to show the extent of blocks, such as BEGIN-END.
Different types of blocks need modifiers after the end, such as "END *IF* " and " END *LOOP* ". If each opening statement (BEGIN, IF, LOOP) is directly above its corresponding END, then it's easy to check if you got the right modifier.
Here's what you code looks like with some formatting, and a couple of corrections added. Look for -- comments.
CREATE OR REPLACE
PROCEDURE fib_dead_cnx_cleanup
AS
l_serial CHAR(100);
l_sid CHAR (100);
l_sid_serial CHAR(100);
l_count NUMBER(10,0);
CURSOR session_cur IS
SELECT sid
, serial#
, sid || ','
|| serial# as sid_serial
FROM v$session
WHERE username = 'EBBFCAT'
and schemaname = 'TESTSCHEMA'
and status = 'INACTIVE'; -- need semicolon here
BEGIN
BEGIN -- Why?
l_count := 0;
OPEN session_cur;
WHILE ( 1 = 1)
LOOP
BEGIN -- Why?
FETCH session_cur
INTO l_sid
, l_serial
, l_sid_serial ;
EXIT WHEN session_cur%NOTFOUND ;
BEGIN -- Why?
alter system kill session 'l_sid_serial' ; -- Not a PL/SQL command
END;
END;
END LOOP; -- LOOP ends with END LOOP
CLOSE session_cur;
END;
END FIB_DEAD_CNX_CLEANUP;Take baby steps.
I've been wrtiing PL/SQL for 20 years, and I would never write that much code at once. If you're a beginner, all the more reason to start small. Write as little as possible, test, debug and test again (if necessary). When you have someting working, add 2 or 3 more lines and test again.
It looks like you have three BEGIN statements that don't serve any purpose. You should get rid of them (and their corresponding END statements, of course).
One error I did not fix: ALTER SYSTEM is not a PL/SQL statement. It's a SQL statement. You can run a SQL statement inside PL/SQL by using dynamic SQL, where you construct a string containing the SQL statement, and then use dbms_sql or EXECUTE IMMEDIATE to run it.
Edited by: Frank Kulash on Aug 18, 2009 12:37 PM -
How can I kill all Threads of the same class from within the run() method?
Ok
I have a class called Consumer that extends Thread
I have several Consumer threans running... but, when a certain condition is true (within the run() method) in ANY of the threads, I want to kill ALL the threads of that object.
is this possible?I know this is gonna be too demanding, but can someone please tell me why my Consumer's run() method never reaches the System.out.println( "ALL CONSUMING DONE") line
Create a multi-threaded prime number calculator that is based on the producer-consumer model
using semaphores. Your program should be able to check for prime numbers in a range specified
by the user and with a variable number of threads. Example:
$ java PrimeFind 3 5000 10000
should use 1 producer and 2 consumers (3 threads in total, obviously the minimum is 2) to find all
the prime numbers in the range [5000,10000].
The producer should: use a buffer to store candidate numbers that have to be checked for
primality.
Consumers should: read from the buffer, check if a number is prime and update the status of the
program accordingly (e.g. show the number on the screen, or save it to a file)
import java.util.concurrent.Semaphore;
import java.io.*;
public class Assign1 {
static int fromThisNumber;
static int toThisNumber;
static int numberOfThreads;
static int buffer[];
static Semaphore ready; /*This semaphore is used by the Producer to signal
an "OK" to the consumers*/
static Semaphore critical; /*This is a Mutex semaphore. It allows only 1 consumer
to enter his critical section.
static Semaphore counter; /*This semaphore acts as a counter.
Instead of having a global variable
incremented each time, we just release()
this semephore when we find a prime number
Because remember that release() increments permits
static Producer prod;
static Consumer cons[];
static int in=0;
static int out=0;
static PrintWriter outFile;
public static void main (String args[]){
try{
outFile=new PrintWriter(new FileWriter("primes.txt"));
}catch(Exception e){}
numberOfThreads=Integer.parseInt(args[0]);
fromThisNumber=Integer.parseInt(args[1]);
toThisNumber=Integer.parseInt(args[2]);
buffer=new int[Integer.parseInt(args[2])-Integer.parseInt(args[1])+1];
ready=new Semaphore(0,false); /*We initialise it to 0 because we wait
for the Producer to produce atleast a
item. Suppose ready was 1 and if
Consumer ran first he would be in an
empty buffer */
critical=new Semaphore (1,false);/*We initialise it to 1 because when
the first Consumer thread tries
to enter its critical section, it
should be allowed to;
Subsequent threads will have to
wait since only 1 thread can
access its critical section at a time*/
counter=new Semaphore(0,false); // duh!
cons=new Consumer[numberOfThreads-1]; /*numberOfThreads-1 because 1 thread
is taken by the Producer*/
//Creating Producer object
prod=new Producer();
//Creating the Consumer object and start the thread.
for(int i=0;i<cons.length;i++)
cons=new Consumer();
cons[i].start();
prod.start();
//Printing to screen and file
/* for(int i=0;i<buffer.length;i++)
if(buffer[i]!=0)
System.out.println(buffer[i]);
outFile.println(buffer[i]);
System.out.println("Total primes found between "+args[1]+" and "+toThisNumber+": "+counter.availablePermits()+"\n primes.txt written");
outFile.println("Total primes found between "+args[1]+" and "+toThisNumber+": "+counter.availablePermits());
outFile.close();*/
static class Producer extends Thread {
public void run(){try{
while(in<buffer.length) /*'in' should always be more than 'out'.Oherwise the consumer will try to access an empty index*/
{ System.out.println("producing");
buffer[in]=fromThisNumber;
in++;
fromThisNumber++;
ready.release();
catch (Exception e){e.printStackTrace();}
System.out.println("ALL PRODUCING DONE");
static class Consumer extends Thread {
int tempout=0;
public void run(){try{
System.out.println("before while"+this.getId());
while(tempout<=in)
System.out.println("before ready"+this.getId()+" "+ready.availablePermits()+" "+in);
ready.acquire();
System.out.println("before critical.acquire"+this.getId());
critical.acquire();
tempout=out;
out++;
critical.release();
if(!isPrime(buffer[tempout]))
{System.out.println(buffer[tempout]+" by "+this.getId());buffer[tempout]=0;}
else {counter.release();System.out.println("prime added: "+buffer[tempout]+" by "+this.getId());}
critical.acquire();
tempout=out;
System.out.println("tempout:"+tempout+" of "+this.getId());
critical.release();
System.out.println("ALL CONSUMING DONE"+this.getId());
catch(Exception e){e.printStackTrace();}
//Prime number-checking method
public boolean isPrime(int n){
for(int i=2;i<=(n/2);i++)
if(n%i==0)
return false;
return true;
======================
import java.util.concurrent.Semaphore;
import java.io.*;
/* 3 questions to ask Barlas
* Why error if I start the Consumer threads before Producer
* Why does the counter semaphore always give a +1 result at the end
* Is there a way I can verify that all the work is not being done by only 1 consumer thread? In other words, the workload is being shared properly
* if I put ready.acquire() outside or inside the while loop, its not making any difference, why?
* Strangely, its not making any difference if I playing with the release() and aquire() of the semaphores, WHY?!?!
public class Assign1 {
static int fromThisNumber;
static int toThisNumber;
static int numberOfThreads;
static int buffer[];
static Semaphore ready; /*This semaphore is used by the Producer to signal
an "OK" to the consumers*/
static Semaphore critical; /*This is a Mutex semaphore. It allows only 1 consumer
to enter his critical section.
static Semaphore counter; /*This semaphore acts as a counter.
Instead of having a global variable
incremented each time, we just release()
this semephore when we find a prime number
Because remember that release() increments permits
static Producer prod;
static Consumer cons[];
static int in=0;
static int out=0;
static PrintWriter outFile;
public static void main (String args[]){
try{
outFile=new PrintWriter(new FileWriter("primes.txt"));
}catch(Exception e){}
numberOfThreads=Integer.parseInt(args[0]);
fromThisNumber=Integer.parseInt(args[1]);
toThisNumber=Integer.parseInt(args[2]);
buffer=new int[Integer.parseInt(args[2])-Integer.parseInt(args[1])+1];
ready=new Semaphore(0,false); /*We initialise it to 0 because we wait
for the Producer to produce atleast a
item. Suppose ready was 1 and if
Consumer ran first he would be in an
empty buffer */
critical=new Semaphore (1,false);/*We initialise it to 1 because when
the first Consumer thread tries
to enter its critical section, it
should be allowed to;
Subsequent threads will have to
wait since only 1 thread can
access its critical section at a time*/
counter=new Semaphore(0,false); // duh!
cons=new Consumer[numberOfThreads-1]; /*numberOfThreads-1 because 1 thread
is taken by the Producer*/
//Creating Producer object
prod=new Producer();
//Creating the Consumer object and start the thread.
for(int i=0;i<cons.length;i++)
cons[i]=new Consumer();
cons[i].start();
prod.start();
//Printing to screen and file
/* for(int i=0;i<buffer.length;i++)
if(buffer[i]!=0)
System.out.println(buffer[i]);
outFile.println(buffer[i]);
System.out.println("Total primes found between "+args[1]+" and "+toThisNumber+": "+counter.availablePermits()+"\n primes.txt written");
outFile.println("Total primes found between "+args[1]+" and "+toThisNumber+": "+counter.availablePermits());
outFile.close();*/
static class Producer extends Thread {
public void run(){try{
while(in<buffer.length) /*'in' should always be more than 'out'.Oherwise the consumer will try to access an empty index*/
{ System.out.println("producing");
buffer[in]=fromThisNumber;
in++;
fromThisNumber++;
ready.release();
catch (Exception e){e.printStackTrace();}
System.out.println("ALL PRODUCING DONE");
static class Consumer extends Thread {
int tempout=0;
public void run(){try{
System.out.println("before while"+this.getId());
while(tempout<=in)
System.out.println("before ready"+this.getId()+" "+ready.availablePermits()+" "+in);
ready.acquire();
System.out.println("before critical.acquire"+this.getId());
critical.acquire();
tempout=out;
out++;
critical.release();
if(!isPrime(buffer[tempout]))
{System.out.println(buffer[tempout]+" by "+this.getId());buffer[tempout]=0;}
else {counter.release();System.out.println("prime added: "+buffer[tempout]+" by "+this.getId());}
critical.acquire();
tempout=out;
System.out.println("tempout:"+tempout+" of "+this.getId());
critical.release();
System.out.println("ALL CONSUMING DONE"+this.getId());
catch(Exception e){e.printStackTrace();}
//Prime number-checking method
public boolean isPrime(int n){
for(int i=2;i<=(n/2);i++)
if(n%i==0)
return false;
return true;
===========================
BTW, when I tried to change extends Thread to implements Runnable I got some kinda of error.
Actually, my program is pretty complete... its just that something if messed up in my Consumer's run() method's while loop... I think
I know guys its crazy to ask ya'll to look at so much code, but.... I'd really appreciate it. This assignment is killing me, been at it since 10 hours now.... -
Hi there!
Please, first, promise not to laugh!
In the script, I wrote:
text_field.text = "yes";
var a:String = text_field.text;
At the beginning of a conditional logic statement I want to
use the value of this variable.
How should I write the condition?
I tried:
if (a == yes) {....
if (a = yes) {....
if (a == "yes") {....
if (a.length = 3) {....
Nothing works...
Maybe I'm too tired and... confused!
Please, put me back on the track.
I thank you in advance.
Best regards from Old GerryGerryIsHere,
> In the script, I wrote:
> text_field.text = "yes";
> var a:String = text_field.text;
I'm with you so far.
> At the beginning of a conditional logic statement I want
> to use the value of this variable.
> How should I write the condition?
The a variable is typed as a string, so its value must be a
string.
> I tried:
> if (a == yes) {....
Because "yes" does not appear in quotes, Flash will
interpret it as a
variable. Since you haven't declared a yes variable anywhere,
it's value
will be undefined or null, so your first condition compares a
with, say,
undefined, which evaluates to false.
> if (a = yes) {....
This isn't a comparison at all, actually. The single equals
sign is an
active operator that *sets* the value of one thing to
another. Here, you're
setting the value of a to, again, undefined (or perhaps
null).
> if (a == "yes") {....
This should do it. When you say nothing works, how are you
determining
that?
> if (a.length = 3) {....
Again, the single equals sign is killing it. You're trying
to set the
String.length property to a number, but the length property
is read-only.
Is it possible that text_field isn't a correct reference to
one of your
text fields? One of your text fields would have to have the
instance name
"text_field" (minus quotes) in order to be referenceable by
ActionScript.
David Stiller
Co-author, Foundation Flash CS3 for Designers
http://tinyurl.com/2k29mj
"Luck is the residue of good design." -
Urgent please help(program to kill running process)
I am trying to execute "alter system kill session '9,32'" from my java program.But the query doesn't seem to get executed.
please help me.
Here is my code.....
package package6;
import java.sql.*;
public class killProcess{
public static void createTable() {
Connection con=null;
Statement st;
try{
String alterSql = "alter system kill session '9,32'";
st = con.createStatement();
st.executeQuery(alterSql);
}catch(SQLException sql){
System.out.println("SQLException se"+sql);
public static Connection getConnection() throws SQLException{
try{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
}catch(ClassNotFoundException e){
System.out.println("Class Not Found Exception");
Connection con =DriverManager.getConnection("jdbc:odbc:abc","system","manager");
return con;
public static void main(String args[]){
dbconn2.createTable();There is a lot of principial mistakes in youp example (I hope it just an example)
1. Never use a sun.jdbc.odbc.JdbcOdbcDriver in serious application - it is a lot of problems in this bridge. It can be used in tutorials only. You should use JDBC-diver from a manufacturer of your DB (http://industry.java.sun.com/products/jdbc/drivers)
2. NEVER create a staic variables for obtaining a connection - connection is a complicated object with limited lifetime. Connection should be obtained from a spesial pool or DataSource. See http://developer.java.sun.com/developer/technicalArticles/J2EE/pooling/ if you use enterprise-java or http://developer.java.sun.com/developer/onlineTraining/Programming/JDCBook/conpool.html for single application (but this is a tutorial only - the code is not work - contact me for obtaining a corrected code)
3. This code is ungrammatical
try{
String sql="alter system kill session '?,?'";
PreparedStatement ps = con.prepareStatement(sql);
}catch(SQLException sql){
System.out.println("SQLException se"+sql);
you should write at least:
String sql="alter system kill session '?,?'";
Connection con = null;
PreparedStatement ps = null;
try{
con = getConnection();
ps = con.prepareStatement(sql);
}catch(SQLException e){
System.out.println("SQLException se"+e);
e.printStackTrace();
}finally{
try{
if(ps!=null)
ps.close();
}catch(Throwable ee){
ee.printStackTrace()
try{
con.close();
}catch(Throwable ee){
ee.printStackTrace()
And whot are you mean in command "alter system kill session '?,?'"
Whot is it '?,?' - may be '?','?'?
You should check syntax of your SQL-instruction.
but your problem is not in Java -
May be syntax of the SQL-command
May be you should use CallableStatement extends of PreparedStatement
It can depend on DataDase.
And don't forget to commin your connection. -
New MacBook Pro, FileVault Locked in Perpetual Encryption, Kills Battery
I have a brand new (well, it's about 2 weeks old now) MacBook Pro (2.8 i7, 1 TB, 16 GB, Iris Pro 1536 MB). Love it.
When I initially set up this device after removing it from its box, I opted to enable FileVault encryption.
Since then, however, FileVault has been unable to complete the operation. It seems to be locked in a routine of perpetual encryption, despite the fact it reports it's doing nothing at all.
Here's what I see in the FileVault panel of System Preferences, for example:
Note the progress bar. It reads "Connect power adapter to resume encryption." This message remains regardless of whether or not the power adapter is connected.
If I click the "Turn Off FileVault…" button, I get:
So I'm in a bit of a catch 22: I can't turn it off until it's done, but it'll never be done because it's waiting for the power adapter to be plugged in, but it never recognizes when the power adapter is plugged in.
This wouldn't be so bad except for one problem: it's doing something in the background that's absolutely killing my battery. Whenever I unplug my power adapter, "Converting to FileVault" is always displayed under the "Apps Using Significant Energy" section of the battery menu.
Presumably as a result of this, I never get more than about 4 hours of battery life with this device, even with the screen fully dimmed and when just doing basic web browsing. Interestingly, under the "Energy" pane of Activity Monitor, there is no line item for any FileVault related activity.
One final note. I've read that Apple puts SSDs in MacBooks from different manufacturers. The drive in my device is identified as, "APPLE SSD SM1024F Media." The "SM" from what I understand denotes that I have a Samsung SSD in my MacBook. I'm not sure if there are issues related to Samsung drives, but it would be a variable in this situation.
I've contacted AppleCare about this and they are stumped, though they acknowledge it's a recognized problem that is being investigated. I'm on a list of people to be notified of a fix, but I have the feeling sorting this out is a low priority at Apple.
So I figured I'd reach our here in the community with a few questions:
Anyone else had this problem and have a fix?
Is this hardware related, or just software?
Do you think a basic nuke and pave of the device will make this problem go away?
Anyone have any other ideas?
Thanks for reading. I look forward to hearing back on any thoughts anyone might have.I finally got sick of the battery being chewed up in less than 3 hours, even with the lid closed, and no user-facing apps running. Yesterday I backed up all my files, erased the hard drive and reinstalled Yosemite.
During set up I opted to try FileVault again. Fortunately, it was successful this time, though it did take about an hour to complete the encryption process. I left the machine alone during that time and just let it perform that one function.
So if you have the problem I describe here, Apple doesn't seem interested in resolving the matter and you're only option is probably a full nuke and pave of your hard drive. It's a lot of work, but it'll probably save your battery in the long run. -
Clearing custom session variable in 5.0
I have set a custom session variable in a method called in the OnAfterLogin PEI.
Do I need to ckear this session variable on logout? If so, how do I do that?
Or does the session variable clear on its own if teh session is abandoned or killed on logout?
I just want to make sure I am not leaking any memory and do proper housekeeping.
Thanks!
Vanita
StaplesSam,
It appears that you are one of the few installations that actually used a display/formatting page under 4.x. Under 5.0 you have the option of going directly to the source of the card or gatewaying the card. Those are your only two options to my knowledge. I suppose that the answer might rest on using docfetch but this would require a custom CWS.
Good Luck
Phil Orion -
Putting a massive amount of data into a single variable
I'm running a command to find the amount of space .xar files (it's a Citrix temp file of sort) are using on my organization's main file server. The server itself presents quite a few terabytes of data and all our user's profile folders are there, so we're
talking about many thousands of folders with a whole mess of files. The command I was using is the following:
(gci w: -r -force -include *.xar | measure -sum -property Length).Sum
It took a long time to run, at least 5 hours, but it was finished when I got back to my desk this morning. Turns out we have 63 gigabytes of those .xar files.
I have a few questions:
1) Is this the best way to get that info?
2) If I need to put that command into a variable {$size = (gci w: -r -force ... Length).Sum} to get other info, am I going to kill my poor server's memory?
Thank you
[email protected]I may need to correlate size across department as sorted by user, or get total number of instances.
[email protected]
Is that department / user information all contained in the path to the file, or do you need to do something like query the Owner from NTFS security on the file?
Here's a quick C# function to search for files and output the full path and size of each to a CSV file. If this still isn't fast enough, maybe speed can be improved more by using the Win32 API's FindFirstFile / FileNextFile / FindClose functions,
but I'm not certain how much of a benefit that would give.
Note: This code requires at least .NET Framework 4.0, which means PowerShell 3.0.
Add-Type -TypeDefinition @'
using System;
using System.IO;
using System.Text;
using System.Collections.Generic;
public static class FileSearcher
public static void DumpFileInfoToCsv(string directory, string filter, bool recurse, string csvFile)
SearchOption searchOption = recurse ? SearchOption.AllDirectories : SearchOption.TopDirectoryOnly;
if (directory == null)
throw new ArgumentNullException("directory");
if (csvFile == null)
throw new ArgumentNullException("csvFile");
DirectoryInfo dirInfo = new DirectoryInfo(directory);
if (!dirInfo.Exists)
throw new DirectoryNotFoundException(directory);
using (StreamWriter csv = new StreamWriter(csvFile, false, Encoding.UTF8))
csv.WriteLine("\"Path\",\"Size\"");
if (string.IsNullOrEmpty(filter))
filter = "*";
foreach (FileInfo fileInfo in dirInfo.EnumerateFiles(filter, searchOption))
csv.WriteLine("\"{0}\",\"{1}\"", fileInfo.FullName, fileInfo.Length);
[FileSearcher]::DumpFileInfoToCsv('W:\', '*.xar', $true, "$home\XarFiles.csv")
You could then examine the CSV file at leisure to group and total up sizes however you like. (Remember to convert the CSV's "Size" column from a string to a numeric type first.) -
Possible to use process substitution a variable number of times?
Hello Archers,
I have a script like so:
#! /bin/bash
( readlink /proc/$$/fd/0 | grep -q "^pipe:" ) || ( file $(readlink /proc/$$/fd/0) | grep -q "character special" )
cat | tee >(awk 'NR % 2 == 0') >(awk '(NR+1) % 2 == 0')
Well, it's pretty trivial at the moment, but the underlying goal is to split the input, so it can be processed in parallel on multiple cores. If I understand correctly, the above code will split the input across exactly two cores. Does there exist some way to put the process substitution (i.e. ">(awk ' ... ')") in a loop?
Before trying to increase the number of cores, I first tried to see whether I could loop just two times with,
cat | tee $(for i in 1 2; do >(awk -vn="$i" '(NR + $n) % 2 == 0'); done)
but that didn't work.
It also occurred to me that maybe I'm presenting an X-Y problem. I did also consider using the split command, but as far as I can tell, it will only dump its output to files; it's no good for piping or process substitution. Any other ideas that would avoid needing to tee across a variable number of process substitutions?
Naturally, I tried a little Googlemancy, but only came up with answers to newbie questions, or tutorials aimed at newbies.
Thank you for your consideration.
Last edited by /dev/zero (2012-03-26 07:16:25)Or if you want to avoid named pipes, since during development they tend to create lots of files, and the script has to clean them up afterwards, take a look at the 'coproc' feature bash has since version 4
Though, remember that 'man bash' under BUGS says, there may only be one active coproc at a time.
According to this it's not really such a big deal though.
And it won't kill the started coprocesses or anything if you start another process...
Here's a sample session: (the spaces are important btw. )
wry:~/ $ bash [19:02:43]
wry@blubmb:~$ coproc c1 ( cat )
[1] 4129
wry@blubmb:~$ coproc c2 ( cat )
bash: warning: execute_coproc: coproc [4129:c1] still exists
[2] 4130
wry@blubmb:~$ echo $c1_PID $c2_PID -- ${c1[@]} ${c2[@]}
4129 4130 -- 63 60 62 58
wry@blubmb:~$ echo aaac1 >&${c1[1]}
wry@blubmb:~$ echo bbbc2 >&${c2[1]}
wry@blubmb:~$ read -u ${c1[0]} line1
wry@blubmb:~$ read -u ${c2[0]} line2
wry@blubmb:~$ echo $line1 and $line2
aaac1 and bbbc2
wry@blubmb:~$ kill $c1_PID $c2_PID
wry@blubmb:~$
[1]- Terminated coproc c1 ( cat )
[2]+ Terminated coproc c2 ( cat )
wry@blubmb:~$ exit
exit
Just keep in mind that the filedescriptors you get for a coproc won't be available in subshells you execute with &
Eg. you cannot do
coproc X
( use X ) &
Links: http://wiki.bash-hackers.org/syntax/keywords/coproc -
Vb6 - How do I Pass a single variable - CR XI
I have a vb6 application that retrieves data from an ACCESS DB. I would like to pass a single variable programatically to an .rpt file loaded into form containing a crviewer object. The ultimate goal is to generate a report based on a single record identified by the variable.
This has been killing me for days. Any help is appreciated.Not sure I understand the query, but you can pass any value to an already existing formula, empty or not. Would that work?
Ludek -
Hello fellow PI/BPM experts!
At a customer its required to build a ccBPM that ends the previous BPM who is processing a message with the same correlation ID.
The idea was to send a "Kill"-message at the start of the BPM to the same BPM class, and later in the BPM have a fork that waits a Kill-message (with the correct correlation) and ends the BPM.
However it seems that the BPM is always picking up his own Kill-message. Also when I put a wait step after sending the first Kill-message. So messages seem to be queued and are waiting for a BPM to pick it up.
Note that only = is possible in correlations, so a != on a timestamp or something similare doesnt seem possible.
We are on PI7.0 SP15.
Any ideas to solve this?
Thanks, Hannes
Edited by: Hannes Defloo on Aug 28, 2008 11:51 AM
Discovered the deliverey modes setting for BPM, see Delivery Modes in BPM.
But then when there is no other BPM listening the Kill-message is not recieved and the queue is stuck.Hello Iddo,
Thanks for the help, however I also found a way doing it with a single instance of a bpm.
- recieve step 1: async, invoicedocument, set correlation
- block: to put a deadline branch
- set variable to 1
- loop (until variable =0)
- fork, with neccessairy branches = 1
- branch1: recieves invoicedocument with the correlation set, if such a document is recieved, the loop is restarted
- branch2: normal logic (still to be implemented, will sent the invoicedocument to other systems), afterwards send a positive acknowledgement and set variable to 0 to stop the loop.
When sending several messages (with same content) only one bpm instance is created. So it seems that a recieve step with correlation has priority over creating a new bpm instance.
Krgs, Hannes -
What causes the Shared Variable Engine to Crash?
All,
Some background info:
I am using the SVE and DSC so that I can log my data to Citadel using Data Sets. I converted a previous DSC 7.1 project that used the tag engine over. That app ran for over 18 months. Need to upgrade app and add features at my customer requests so we migrated to LV 8.0.1.
I have an app that crashes the Shared Variable Engine (SVE). I created a test app with a single SV and then created a control and bound it to the SV and it works every time until I launch the larger app. The main app only has 33 SV that are set when I receive TCP data from PXI RT system (not using SV on RT since the logged data is only a fraction of the total data streamed and I don't want to take apart the RT data and send the SV separately). I have bound front panels controls to the SV's. When I run, I get server connection has been closed. I verified that the SVE was running with the test app before launching the main app.
I deploy the shared variables in the application and have verified they are deployed by the Monitor Variables utility ... but it always shows "No Value" for the data fields. I have set logging to enabled for data only, set Value Deaband (%) to 0 and Value resolution to 0, Update Deadband is Disabled as is Alarming, Scaling, Initial Value and Description. Security is set to default. All of the variables are set to Double, Network-Published, Single Writer with Buffering and Bind to Source disabled.
I have verified that the SV deploy without error by clicking Deploy from the project. Autodeploy All is off but I get the same results with it On (checked).
I undeploy and kill the process when I close the application.
I have tried only using 1 or 2 of the SV in the main app but get the same results. Every once in a blue moon it will work after rebooting the PC (but not everytime). Once it dies I have tried running NI examples as well as the test app and they fail until I reboot.
The error code indicates that the SVE engine has crashed. I have changed the service settings on Windows to relaunch on 1st, 2nd and all times after but nothing restarts the SVE. After it crashes it is impossible to exit LabVIEW without it hanging or reboot the PC without pressing the hard On/Off switch.
Once it dies there is nothing that I can do to get it back alive without rebooting the PC (a real problem for a control and monitoring system).
Any ideas would be greatly appreciated
Thanks.
RandyRandy
Sorry for the delay, I've been researching your issue and juggling a few other issues. :-) One thing we can check is the Windows Event Log which will give us some more details as to WHY the Shared Variable engine seems to be blowing up on us (Conttrol Panel -> Administrative Tools -> Event Viewer). Any details in there along the lines of Variable Engine or Tagger crashing will help us narrow down what's going on.
There's always a possibility of files not getting upgraded correctly; however there aren't many shared components between LV 7.1 and LV 8.0. The Shared Variable engine is entirely new and the installations of LabVIEW themselves don't share many files outside of the example finder and a few other small common components (things located in the appropriately named Shared folder) I keep both on my machine (in addition to 5.1, 6.1, 7.0, and 8.2) without any hiccups.
The SVE crashing I have seen in the past (and from internal bug reports) has been from buggered installs, so uninstalling and reinstalling DSC may be a good course of action. One good test to do in the middle is to see if the engine still crashes with DSC uninstalled.
Hope this helps.
--Paul Mandeltort
Automotive and Industrial Communications Product Marketing
Maybe you are looking for
-
STO and delivery is getting created in the foreground instead of background
Hi experts, In return document (with reference to Work Order), When user is selecting recommended action u2018YAu2019 and clicking the u2018returnu2019 button, an STO and delivery is getting created in the foreground instead of generating them in bac
-
I need help with a solution. I need to use older Adobe Software (LiveMotion) Unfortunately, it does not work with OS X beyond 10.3. I want to use the new OS X on my G5. I want to use one of my older Macs, I have a G4 and a G3, (would prefer to use G3
-
Correlation set problem with different messages
Hi. I have process with two receive activity correlated by correlation set. But second receive wait for different message as initiation receive. I created correlation set <correlationSets> <correlationSet name="OrderCorrelationSet" properties="ns1:or
-
I'm a bit confused here. If I do a "df -h" it shows /dev/disk0s2 as being 233GB capacity. It also shows a /dev/disk2s2 as being 465GB. I only have one HDD in this macbook obviously. Is disk2 a compression-enabled version perhaps? Both show the same a
-
Transaction FBL1N not displaying offset account after implementing BADI
hi everyone I have followd the SAP note 112312 to implement a BADI FI_ITEMS_CH_DATA in a BTE to make the fields Offset account to display When I went into debug mode, the table in the BADI is well populated with the offset account - gkont and gkart