Inits
Hi,
What is diff between init without data transfer and init with data transfer?
What are the benefits?
Can anybody exlain in detail?
Thanks
Hi Sasi,
Please try to search in the forums. This has been discussed many times...
Similar Messages
-
Can we determine path of my INIT.ORA file from data dictionary views.
Hello Guru’s
I am new to oracle, My question is for the sake of my knowledge: I work on oracle 10G.
Is there any data dictionary view from where I can get the path of my INIT.ORA file.
Regards,NewDay wrote:
Hello Guru’s
I am new to oracle, My question is for the sake of my knowledge: I work on oracle 10G.
Is there any data dictionary view from where I can get the path of my INIT.ORA file.
AFAIK , its no. You can check the path from the show parameter command like following,
SQL> show parameter spfile
NAME TYPE
VALUE
spfile string
/u01/app/oracle/product/10.2.0
/db_1/dbs/spfileorcl.ora
SQL>HTH
Aman.... -
OutOfMemory error in java.awt.image.DataBufferInt. init
We have an applet application that performs Print Preview of the images in the canvas. The images are like a network of entities (it has pictures of the entities involve (let's say Person) and how it links to other entities). We are using IE to launch the applet.
We set min heap space to 128MB, JVM max heap space to 256MB, java plugin max heap space to 256MB using the Control Panel > Java.
When the canvas width is about 54860 and height is 1644 and perform Print Preview, it thows an OutOfMemoryError in java.awt.image.DataBufferInt.<int>, hence, the Print Preview page is not shown. The complete stack trace (and logs) is as follows:
Width: 54860 H: 1644
Max heap: 254 # using Runtime.getRuntime().maxMemory()
javaplugin.maxHeapSize: 256M # using System.getProperties("javaplugin.maxHeapSize")
n page x n page : 1x1
Exception in thread "AWT-EventQueue-2" java.lang.OutOfMemoryError: Java heap space
at java.awt.image.DataBufferInt.<init>(Unknown Source)
at java.awt.image.Raster.createPackedRaster(Unknown Source)
at java.awt.image.DirectColorModel.createCompatibleWritableRaster(Unknown Source)
at java.awt.image.BufferedImage.<init>(Unknown Source)
at com.azeus.gdi.chart.GDIChart.preparePreview(GDIChart.java:731)
at com.azeus.gdi.chart.GDIChart.getPreview(GDIChart.java:893)
at com.azeus.gdi.ui.GDIUserInterface.printPreviewOp(GDIUserInterface.java:1526)
at com.azeus.gdi.ui.GDIUserInterface$21.actionPerformed(GDIUserInterface.java:1438)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Drilling down the cause of the problem. The OutOfMemory occurred in the constructor of DataBufferInt when it tried to create an int array:
public DataBufferInt(int size) {
super(STABLE, TYPE_INT, size);
data = new int[size]; # this part produce out of memory error when size = width X height
bankdata = new int[1][];
bankdata[0] = data;
The OutOfMemory error occurred when size is width * height (54860 X 1644) which is 90,189,840 bytes (~86MB).
I can replicate the OutOfMemory error when initiating an int array using a test class when it uses the default max heap space but if I increase the heap space to 256MB, it cannot be replicated in the test class.
Using a smaller width and height with product not exceeding 64MB, the applet can perform Print Preview successfully.
Given this, I think the java applet is not using the value assigned in javaplugin.maxHeapSize to set the max heap space, hence, it still uses the default max heap size and throws OutOfMemory in int array when size exceeds the default max heap space which is 64MB.
For additional information, below is some of the java properties (when press S in java applet console):
browser = sun.plugin
browser.vendor = Sun Microsystems, Inc.
browser.version = 1.1
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.awt.printerjob = sun.awt.windows.WPrinterJob
java.class.path = C:\PROGRA~1\Java\jre6\classes
java.class.version = 50.0
java.class.version.applet = true
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = 1.6.0_17-b04
java.specification.version = 1.6
java.vendor.applet = true
java.version = 1.6.0_17
java.version.applet = true
javaplugin.maxHeapSpace = 256M
javaplugin.nodotversion = 160_17
javaplugin.version = 1.6.0_17
javaplugin.vm.options = -Xms128M -Djavaplugin.maxHeapSpace=256M -Xmx256m -Xms128M
javawebstart.version = javaws-1.6.0_17
Kindly advise if this is a bug in JRE or wrong setting. If wrong setting, please advise on the proper way to set the heap space to prevent OutOfMemory in initializing int array.
Thanks a lot.
Edited by: rei_xanther on Jun 28, 2010 12:01 AM
Edited by: rei_xanther on Jun 28, 2010 12:37 AMrei_xanther wrote:
..But the maximum value of the int data type is 2,147,483,647. That is the maximum positive integer value that can be stored in (the 4 bytes of) a signed int, but..
..The value that I passed in the int array size is only 90,189,840...its only connection with RAM is that each int requires 4 bytes of memory to hold it.
new int[size] -- size is 90,189,840Sure. So the number of bytes required to hold those 90,189,840 ints is 360,759,360.
I assumed that one element in the int array is 1 byte. ..Your assumption is wrong. How could it be possible to store 32 bits (4 bytes) in 8 bits (1 byte)? (a)
a) Short of some clever compression algorithm applied to the data. -
Classloader difference in init() and destroy()?
I was getting a ClassNotFoundException (see below) inside a log4j call from my servlet destroy() method. To test, I attempted the same log4j call from my servlet init() method and it works just fine. In fact, in this test, since the class is already loaded at init time it finds it successfully at destroy time (ie. the log4j call is successful). But, if I take the call out of init and the class in not loaded anywhere prior to destroy(), it fails with the ClassNotFoundException in destroy(). Anybody have any insight on this one? Thanks.
The exception stack dump:
java.lang.NoClassDefFoundError: org/apache/log4j/spi/ThrowableInformation
at org.apache.log4j.spi.LoggingEvent.<init>(LoggingEvent.java:145)
at org.apache.log4j.Category.forcedLog(Category.java:372)
at org.apache.log4j.Category.info(Category.java:691)
I'm using log4j version 1.2.7.
I'm importing org.apache.log4j.Logger;
I instantiate in my class: private Logger theLog = Logger.getLogger(this.getClass());
I'm calling: theLog.info(String s, Throwable e);Where do you have the log4j.jar? It sounds like the ClassFinder for that jar has already been closed (as part of the undeployment) by the time your destroy is called.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/ -
"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 -
Hello folks
First of all, I want to say sorry for my English.
Well, I have one jsp file and I want to pass one value from web.xml file to it but I don't know how
I also did the same thing with servlet and it's OK, I used function getInitParameter in ServletConfig and modified file web.xml in Tomcat 3.2.
Please help me
Thanks in advance.Hi,
For example, if your web.xml has something like:
<context-param>
<param-name>testParam</param-name>
<param-value>[email protected]</param-value>
</context-param>
You can access the "testParam" init param from within your JSP scriptlet as:
String value = getServletContext().getInitParameter("testParam");
where "testParam" matches the <param-name> element of one of these initialization parameters.
Hope that helps.
Regards,
Senthil Babu
Developer Technical Support
SUN Microsystems
http://www.sun.com/developers/support/ -
Urgent....How can i redirect to my jsp page from servlet in init() method..
How can i redirect to my jsp page from servlet in init() method..Becoz that servlet is calling while server startsup..so im writing some piece of code in init() method..after that i want to redirect to some jsp page ...is it possible?
using RequestDispatcher..its not possible..becoz
RequestDispatcher rd = sc.getRequestDispatcher("goto.jsp");
rd.foward(req,res);
Here the request and response are null objects..
So mi question can frame as how can i get request/response in servlet's init method()..Hi guys
did any one get a solution for this issue. calling a jsp in the startup of the servlet, i mean in the startup servlet. I do have a same req like i need to call a JSP which does some data reterival and calculations and i am putting the results in the cache. so in the jsp there in no output of HTML. when i use the URLConnection i am getting a error as below.
java.net.SocketException: Unexpected end of file from server
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:707)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:612)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:705)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:612)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:519)
at com.toysrus.fns.alphablox.Startup.callJSP(Unknown Source)
at com.toysrus.fns.alphablox.Startup.init(Unknown Source)
at org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317)
so plz do let me know how to call a jsp in the start up of a servlet.
Thanks
Vidya -
Accessing parameters from request header in init()
Hello
How can I access parameters passed on the client request header like
http://localhost:8080/servlet/DBServlet?database=mydatabase
from the servlet initialization method ini()
The getInitParameter() only returns parameters defined in the web.xml file (if is this correct).
I would like to use the getParameter() from the request class, how can I do this within init()
ThanksGreetings,
Hello
How can I access parameters passed on the client
request header like
http://localhost:8080/servlet/DBServlet?database=mydat
base
from the servlet initialization method ini()You can not. As you pointed out, the init() method is for servlet initialization - it is called by the container to allow the servlet to prepare to receive requests, which are then passed to the service() method.
The getInitParameter() only returns parameters defined
in the web.xml file (if is this correct). That is correct - parameters can be defined in the deployment descriptor in either the <servlet> level (passed to the servlet in ServletConfig), or the <webapp> level (passed to the entire webapp in ServletContext).
I would like to use the getParameter() from the
request class, how can I do this within init()Again, you can not - there simply is not any client communication during initialization.
ThanksRegards,
Tony "Vee Schade" Cook -
Netbeans: adding to jPanel via code after init (jFreeChart)
This will be my second post. Many thanks to those who replied to my first questions.
I am using netbeans 5.5
I am attempting to run the following jFreeChart demo but in netbeans.
Original demo located here: http://www.java2s.com/Code/Java/Chart/JFreeChartPieChartDemo7.htm
Instead of programically creating the jPanel like the demo does, i would like to do it using the netbeans GUI and then add the code to create the jFreeChart.
In netbeans i create a new project, create a new jFrame and place a new jPanel on the form (keeping the variable name jPanel1) as illustrated below:
* MainForm.java
* Created on June 28, 2007, 1:48 PM
package mypkg;
import org.jfree.chart.ChartFactory;
import org.jfree.chart.ChartPanel;
import org.jfree.chart.JFreeChart;
import org.jfree.chart.plot.PiePlot;
import org.jfree.chart.plot.PiePlot3D;
import org.jfree.data.general.DefaultPieDataset;
import org.jfree.ui.ApplicationFrame;
import org.jfree.ui.RefineryUtilities;
* @author me
public class MainForm extends javax.swing.JFrame {
/** Creates new form MainForm */
public MainForm() {
initComponents();
/** Netbeans Auto-Generated Code goes here which I have omitted */
* @param args the command line arguments
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new MainForm().setVisible(true);
private void CreateChart() {
DefaultPieDataset dataset = new DefaultPieDataset();
dataset.setValue("Section 1", 23.3);
dataset.setValue("Section 2", 56.5);
dataset.setValue("Section 3", 43.3);
dataset.setValue("Section 4", 11.1);
JFreeChart chart3 = ChartFactory.createPieChart3D("Chart 3", dataset, false, false, false);
PiePlot3D plot3 = (PiePlot3D) chart3.getPlot();
plot3.setForegroundAlpha(0.6f);
plot3.setCircular(true);
jPanel1.add(new ChartPanel(chart3));
jPanel1.validate();
// Variables declaration - do not modify
private javax.swing.JPanel jPanel1;
// End of variables declaration
}I then attempted to call the CreateChart() function in several places (in the MainForm() function, in the pre and post creation code properties of the jPanel's properties dialog in netbeans (as well as pre and post init in the same screen)) and nothing seems to work. the program compiles and the jFrame comes up but the chart does not show.
If i run the example at the above noted link it runs fine in netbeans if i copy and paste the code directly, it just doesnt work when i try to get it to work through the netbeans GUI builder and the jPanel i create through it.
Can any more advanced netbeans/java users lend me a hand or point me in the right direction?
NOTE: in the code pasted above, i am only trying to run one of the four chart demo's listed in the original source in the link.
NOTE2: in the code pasted above it doesnt show me calling CreateChart() from anywhere, im hoping to get some advice on how to proceed from here.
Message was edited by:
amadmanHere is the netbeans generated code that i had omitted in the post above:
private void initComponents() {
jPanel1 = new javax.swing.JPanel();
setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE);
CreateChart(); //this is one of the many places i tried sticking the function
javax.swing.GroupLayout jPanel1Layout = new javax.swing.GroupLayout(jPanel1);
jPanel1.setLayout(jPanel1Layout);
jPanel1Layout.setHorizontalGroup(
jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGap(0, 546, Short.MAX_VALUE)
jPanel1Layout.setVerticalGroup(
jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGap(0, 398, Short.MAX_VALUE)
layout.setHorizontalGroup(
layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(layout.createSequentialGroup()
.addContainerGap()
.addComponent(jPanel1, javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)
.addContainerGap())
layout.setVerticalGroup(
layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(layout.createSequentialGroup()
.addContainerGap()
.addComponent(jPanel1, javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)
.addContainerGap())
pack();
}// </editor-fold> I believe this is what you mentioned looking for, or close to it:
javax.swing.GroupLayout layout = new javax.swing.GroupLayout(getContentPane());
getContentPane().setLayout(layout);any thoughts? -
Init w/o data transfer shows Added/Transfrd - 1/1
Hi ,
Init w/o data transfer load was successful after having applied <i>Note 689964 - ODS object: Switching from a full to delta upload !</i>
I have two weird ( nt sure ) issues below :
<b>Issue 1</b>
On Manage screen I see Added - 1 & Transferred - 1, however I dont see this record in the DSO ( Display data ).
Why is that so ?
<b>
Issue 2</b>
All seems green excepting when I go check the Details Tab - I see some reds
DataStore Activation (Change Log) : Errors occurred
No data targets selected for update. Action terminated.
InfoPackage ZPAK_*** could not be started by Bapi_ipak_start
Errors in InfoPackage check for DataStore 0CCA_O09 ; no update possible
Please comment SDNer'sDear Jr.Roberto,
Issue 1
On Manage screen I see Added - 1 & Transferred - 1, however I dont see this record in the DSO ( Display data ).
Why is that so ?
<b>
--> When you do a init with out data transfer, system transfers one record that is not corresponding to the data, but is a control record corresponding to the init selections.</b>
Issue 2
All seems green excepting when I go check the Details Tab - I see some reds
DataStore Activation (Change Log) : Errors occurred
No data targets selected for update. Action terminated.
InfoPackage ZPAK_*** could not be started by Bapi_ipak_start
Errors in InfoPackage check for DataStore 0CCA_O09 ; no update possible
<b>---> It is because you dont have a active update rules maintained for the infosource to the data target, or you have not selected any data target in the infopackage , it can also be the case that the infopackage which generates a program to start the load is having some errors, if possbile create another infopackage and start the load with active Update rules to data target.</b>
Cheers!!!!
Charan
Message was edited by:
Sri Krishna Charan Viswanatha -
i am trying to install oracle 11g xe on ubuntu aws instance when i execute sudo /etc/init.d/oracle-xe configure command iam getting this error: sudo: /etc/init.d/oracle-xe : command not found.
"command not found" means ... there is no such thing.
Has the .rpm been installed?
http://docs.oracle.com/cd/E17781_01/install.112/e18802/toc.htm#XEINL122 -
Hi,
I am getting different record count for Full and Init GL - Data loads.
Count for Init is about 300 records less than the count for Full load.
What could be the reason ?
Thanks,while posting question be clear what cube/datasource ,which GL OLD or NEW you are working whats the background...else its just speculating and beating around bush guessing..
http://help.sap.com/saphelp_erp2005vp/helpdata/en/45/757140723d990ae10000000a155106/content.htm
New Gl data flow-
Re: New GL cubes 0FIGL_V10, 0FIGL_V11
Hope it Helps
Chetan
@CP.. -
Hi,
I have some questions on init.ora file. While checking the init file in my system i found that it defines a spfile in a non default location.
The parameter names are like
1) db1.__db_cache_size
2) *._kgl_large_heap_warning_threshold
3) *.sga_target
what do they indicate? I mean what does 'db1.__' , '*._' and '*.' indicate? There are multiple database in the Windows 2003 server and the db version is 10g R1
Regards,
SID
Edited by: SID3 on Jun 29, 2010 5:55 AM
Edited by: SID3 on Jun 29, 2010 5:56 AMSID3 wrote:
From the discussion i guess the following points
1) db1._ means they are specific to databases.
2) *._ and * means they are used accross databases and chaging it in any of the initfile might affect all? I seriously doubt this.You are mistaken when speaking about database. Bear in mind, a database is not an instance.
* here means this parameter will apply to any instance of that database (if it is in RAC), or to the only one instance of that database (if it is in non-RAC).
Find out more :
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_2013.htm#i2146449
Nicolas. -
Root device mounted successfully, but /sbin/init does not exist ???
I'm having the issue where when I boot after doing a fresh install, it gives me:
ERROR: Root device mounted successfully, but /sbin/init does not exist
Bailing out, you are on your own. Good luck
sh: can't access tty; job control turned off
[rootfs /]#
My fstab:
# /etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda1 LABEL=homerroot
UUID=877deab9-624d-4e1d-90a1-ccc1d6ebc0c6 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=homerboot
UUID=77835da5-8a38-44c1-bf27-bb657df4484b /boot ext4 rw,relatime,data=ordered 0 2
# /dev/sda3 LABEL=homeretc
UUID=8a1b5bd8-b147-41e0-87df-70a4a9e12df2 /etc ext4 rw,relatime,data=ordered 0 2
# /dev/sda4 LABEL=homervar
UUID=8eb2e7b1-cdf1-46ce-9dc1-439d002bfae4 /var ext4 rw,relatime,data=ordered 0 2
# /dev/sda5 LABEL=homerusr
UUID=bce162b4-d27f-450c-a0e6-4d3ebc6242dc /usr ext4 rw,relatime,data=ordered 0 2
# /dev/sda6 LABEL=home
UUID=62de76ab-b6d4-4e3d-a423-c287b81813a9 /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda7 LABEL=public
UUID=d98a9c8e-2301-4e66-8c7f-26167633a4b0 /public ext4 rw,relatime,data=ordered 0 2
This looks fine to me, but when /dev/sda1 is mounted at /new_root, none of the other devices are mounted....
I don't know if this is what's causing the problem since /etc, and /usr are on separate partitions from root, but
this would be the first time I get a problem dividing things this way (on ubuntu, mint, fedora, et cetera).
So I tried:
https://bbs.archlinux.org/viewtopic.php … 3#p1283343
I get "* is owned by filesystem 2013.05-2" for all three dirs from step three.
None of the other steps have any effect....
I also tried:
https://bbs.archlinux.org/viewtopic.php?id=172943
My /dev/sda1 mounts to new_root, so I don't think I'm having his problem.
And:
https://bbs.archlinux.org/viewtopic.php?id=166423
I reinstalled systemd-sysvcompat, and I'm sure that's not my problem.
Interestingly enough, /usr/lib/systemd/systemd is an elf file on my target hard disk.
Is this an outdated issue or something? Or should /usr/lib/systemd/systemd be a text file?
Thanks in advance for your help guys!WorMzy wrote:Oh, and /usr/lib/systemd/systemd is supposed to be an ELF binary. Not sure why you think it should be a text file.
I saw another thread saying that adding an entry there would help. I think it was "init=<something>".
WonderWoofy wrote:A separate /etc is not supported whatsoever. There needs to be initial access to a few things there. I'm sure it could be made to work with some initramfs hackery. But it is neither supported or wise to do so IMO.
I'll not do the separate partitions then. Thanks. I'll check back if it works/doesn't-works. -
[Solved]Unable to boot /sbin/init does not exist.
When I boot, I get this message: ERROR: Root device mounted successfully, but /shin/init does not exist. This is an installation that was working fine for me before. I went into Windows to free up disk space, and when I booted Arch later, this is what came up. I have already tried using the live disk as a rescue, but I am unable to chroot into it. I have checked my partitions with a live disk and my files are still there. Is there any way that I can fix this without reinstalling Arch? I have a lot of things that I cannot reinstall right now as I don't have access to the internet currently, and I am using my phone to access the forum.
Last edited by LGG42 (2013-11-27 02:43:47)My bootloader is Syslinux. Yes, I am able to mount the file systems. The partitions are in ext4 format. I boot from legacy BIOS, as I have had EFI problems in the past. arch-chroot gives me this: ==> ERROR: failed to setup API filesystems in chroot /mnt. I should have been clear about what I did in Windows. I was running out of space in Windows, and I had some unallocated disk space, and so I extended my Windows partition.
The output of frisk -l is:
Disk /dev/sda: 500.1 GB, 500107862016 sectors
Units = sectors of 1* 512
I/O size (minimum/optimal): 4096 Bytes/4096 bytes
disk label type: got
#1 start: 2048 End 821247 size 400M type windows recovery 2 start 821248 End 1353727 Size 260M type ms basic 3 start 874614784 End 916559871 Size 128M ms reserved 4 start 1615872 End 874614783 Size 416G ms basic. 5 start 874614784 End 91655781 Size 20G ms basic. 6 start 916561920 End 916756479 Size 95M type EFI system. 7 start 916758528 End 928495615 8 start 928495616 end 928499711 Size 2M type ms basic. 9 start 928499712 End 976773119 size 23G type ms basic. Sorry about the mess that is in. As a note, my / partition is #5, and my home is #9. Thank you for helping. -
[SOLVED] /sbin/init does not exist error on boot
Hi all,
Let me first say that Arch Linux is a great distribution and I couldn't be more happier with it! Thanks to everyone who is involved in building it.
However, as the subject line suggests, I have run into a problem. I have tried every trick in my book and every suggestion on Google but the problem still persists.
The setup
* UEFI boot loader on /dev/sda1
* BTRFS file system on /dev/sda2 in __active subvolume
* The system was installed in Jan using the latest install CD (I presume systemd changes were already applied)
The problem
Booting halts on rEFInd screen
What I have tried
Since the last pacman command upgraded git and kernel to 3.7.6-1 (this is not the first kernel upgrade on this system)my first idea was to rollback to 3.7.5-1 which results in /sbin/init not found error.
Re-installing 3.7.6-1 halts the system on rEFInd boot screen. I tried booting from rEFI shell and it results in the same /sbin/init not found error (on 3.7.6-1 kernel) so I presume that's the main issue here.
From there on (as suggested by various posts online) I have verified that rEFInd points to the correct root partition. Also, I've tried passing /bin/systemd explicitly but the error still persists.
I can boot into Live install environment and chroot into the setup on my drive. I have checked that /sbin/init exists (as well as /bin/systemd).
I am out of options here. Any help will be much appreciated.
Please let me know if you require any other information from me.
Last edited by clalbus (2013-02-10 20:59:42)OK, now that I have marked the __active subvolume as default I can boot (using EFI shell) without using the rootflags=subvol=__active kernel parameter.
However, rEFInd boot loader is still not working (with or without rootflags=subvol=__active). Unfortunately I don't see any error messages as the system hangs at rEFInd boot screen.
Here's my archlinux.nsh (that I use to boot through EFI shell):
echo -on
\EFI\arch\vmlinuz-arch.efi root=PARTUUID=626f545b-44f5-4a72-b1f3-d942fbcd0b46 ro rootfstype=btrfs add_efi_memmap systemd.unit=graphical.target initrd=\EFI\arch\initramfs-linux.img rootflags=subvol=__active
Here's my refind_linux.conf from (/boot/efi/EFI/arch)
"Boot with defaults" "root=PARTUUID=626f545b-44f5-4a72-b1f3-d942fbcd0b46 ro rootfstype=btrfs add_efi_memmap systemd.unit=graphical.target rootflags=subvol=__active"
"Boot to terminal" "root=PARTUUID=626f545b-44f5-4a72-b1f3-d942fbcd0b46 ro rootfstype=btrfs add_efi_memmap systemd.unit=multi-user.target rootflags=subvol=__active"
Any idea why booting through EFI shell would work but not through rEFInd?
Is it worthwhile rebuilding /boot?
Maybe you are looking for
-
Correlation Rule where no accountId on resource
Hi experts ;-), I have a resource with no accountId, but Employee Number as primary unique identifier. I have written a correlation rule to match this employeenumber to an extended user attrib also called employeenumber (previously populated from a f
-
Problem in JDBC Adapter Mapping
Hi all, I am working on a scenario wherein i am trying to connect an ORACLE DB to SAP 4.7 system using XI 3.0 . I configured the JDBC Adapter and the JDBC adpter is picking up the message but i have a problem in JDBC adpter Mapping. The error message
-
Using WAIT step in Sync/Async Bridge
I am using a sync/async bridge and placed a 1 minute wait step in between my async send and async reply. When I test my process, the async reply comes in but then my 1 minute wait eventually times out and gives me an error. Can someone guide me in
-
My Ipod touch (4th gen) will not sync, My Ipod touch (4th gen) will not sync
I was trying to add more music to my ipod. That's when it would not sync to itunes on my computer. I have tried uninstalling Itunes and refreshing my ipod, none of that worked. Can anyone help me?
-
ZEBRA PROGRAMMING FOR SHIPPING LABEL
Hi gurus, i have one assignment for creating shipping label using zebra programming into SAPSCRIPT. page size is 5 inch X 7 inch. I also want to draw a circle and in that circle i want to write P\B . i.e. no lead symbol. can anybody give me the samp