* Kernel almost hangs when CONFIG_DRM_RADEON=y
@ 2011-08-27 4:20 Pavel Ivanov
2011-08-27 9:00 ` Michel Dänzer
0 siblings, 1 reply; 37+ messages in thread
From: Pavel Ivanov @ 2011-08-27 4:20 UTC (permalink / raw)
To: David Airlie, dri-devel; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Hi,
I observe very strange behavior dependent on value of
CONFIG_DRM_RADEON parameter. When it's set to m everything works very
good, no problem. When I set it to y I see kernel hang during boot. Or
I should better say it "almost hangs" because during last boot attempt
I accidentally waited a little bit longer and saw that after more than
a minute waiting system continued to boot. Dmesg after "hang" shows
these messages:
[ 8.542639] [drm] Loading CEDAR Microcode
[ 69.161605] r600_cp: Failed to load firmware "radeon/CEDAR_pfp.bin"
[ 69.161670] [drm:evergreen_startup] *ERROR* Failed to load firmware!
While during normal boot
[ 9.898870] [drm] Loading CEDAR Microcode
[ 9.908425] radeon 0000:05:00.0: WB enabled
Is this a bug?
I'm seeing this on 3.1-rc3. Full dmesgs for both boots are attached.
Pavel
[-- Attachment #2: dmesg.module --]
[-- Type: application/octet-stream, Size: 81378 bytes --]
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.1.0-rc3-mods (pivanof@PavelComp) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4) ) #9 SMP PREEMPT Fri Aug 26 22:55:07 EDT 2011
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-rc3-mods root=UUID=a6d88530-6469-4ea2-91b9-410e088b4eff ro vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e5000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000bf780000 (usable)
[ 0.000000] BIOS-e820: 00000000bf78e000 - 00000000bf790000 (reserved)
[ 0.000000] BIOS-e820: 00000000bf790000 - 00000000bf79e000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
[ 0.000000] BIOS-e820: 00000000bf7ed000 - 00000000c0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000240000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI present.
[ 0.000000] DMI: System manufacturer System Product Name/Z8NA-D6(C), BIOS 1002 06/28/2010
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] last_pfn = 0x240000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-E3FFF write-protect
[ 0.000000] E4000-E7FFF write-through
[ 0.000000] E8000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask FE00000000 write-back
[ 0.000000] 1 base 0200000000 mask FFC0000000 write-back
[ 0.000000] 2 base 00C0000000 mask FFC0000000 uncachable
[ 0.000000] 3 base 00BF800000 mask FFFF800000 uncachable
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820 update range: 00000000bf800000 - 0000000100000000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0xbf780 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [ffff8800000ff780] ff780
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
[ 0.000000] init_memory_mapping: 0000000000000000-00000000bf780000
[ 0.000000] 0000000000 - 00bf600000 page 2M
[ 0.000000] 00bf600000 - 00bf780000 page 4k
[ 0.000000] kernel direct mapping tables up to bf780000 @ bf77b000-bf780000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000240000000
[ 0.000000] 0100000000 - 0240000000 page 2M
[ 0.000000] kernel direct mapping tables up to 240000000 @ 23fff6000-240000000
[ 0.000000] RAMDISK: 338be000 - 35c57000
[ 0.000000] ACPI: RSDP 00000000000fb620 00024 (v02 ACPIAM)
[ 0.000000] ACPI: XSDT 00000000bf790100 00084 (v01 062810 XSDT1507 20100628 MSFT 00000097)
[ 0.000000] ACPI: FACP 00000000bf790290 000F4 (v03 062810 FACP1507 20100628 MSFT 00000097)
[ 0.000000] ACPI: DSDT 00000000bf790540 05B3D (v01 S0081 S0081002 00000002 INTL 20060113)
[ 0.000000] ACPI: FACS 00000000bf79e000 00040
[ 0.000000] ACPI: APIC 00000000bf790390 0011E (v01 062810 APIC1507 20100628 MSFT 00000097)
[ 0.000000] ACPI: MCFG 00000000bf7904b0 0003C (v01 062810 OEMMCFG 20100628 MSFT 00000097)
[ 0.000000] ACPI: SPMI 00000000bf7904f0 00041 (v05 062810 OEMSPMI 20100628 MSFT 00000097)
[ 0.000000] ACPI: OEMB 00000000bf79e040 00072 (v01 062810 OEMB1507 20100628 MSFT 00000097)
[ 0.000000] ACPI: SRAT 00000000bf798540 00128 (v01 062810 OEMSRAT 00000001 INTL 00000001)
[ 0.000000] ACPI: HPET 00000000bf798670 00038 (v01 062810 OEMHPET 20100628 MSFT 00000097)
[ 0.000000] ACPI: SSDT 00000000bf79fcb0 0154F (v01 DpgPmm CpuPm 00000012 INTL 20060113)
[ 0.000000] ACPI: EINJ 00000000bf7986b0 00130 (v01 AMIER AMI_EINJ 20100628 MSFT 00000097)
[ 0.000000] ACPI: BERT 00000000bf798840 00030 (v01 AMIER AMI_BERT 20100628 MSFT 00000097)
[ 0.000000] ACPI: ERST 00000000bf798870 001B0 (v01 AMIER AMI_ERST 20100628 MSFT 00000097)
[ 0.000000] ACPI: HEST 00000000bf798a20 000A8 (v01 AMIER ABC_HEST 20100628 MSFT 00000097)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
[ 0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
[ 0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 0x04 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 0x06 -> Node 0
[ 0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x14 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x16 -> Node 1
[ 0.000000] SRAT: Node 0 PXM 0 0-c0000000
[ 0.000000] SRAT: Node 0 PXM 0 100000000-140000000
[ 0.000000] SRAT: Node 1 PXM 1 140000000-240000000
[ 0.000000] NUMA: Node 0 [0,c0000000) + [100000000,140000000) -> [0,140000000)
[ 0.000000] Initmem setup node 0 0000000000000000-0000000140000000
[ 0.000000] NODE_DATA [000000013fffe000 - 000000013fffffff]
[ 0.000000] Initmem setup node 1 0000000140000000-0000000240000000
[ 0.000000] NODE_DATA [000000023fffe000 - 000000023fffffff]
[ 0.000000] [ffffea0000000000-ffffea0004ffffff] PMD -> [ffff88013be00000-ffff88013fdfffff] on node 0
[ 0.000000] [ffffea0005000000-ffffea0008ffffff] PMD -> [ffff88023b600000-ffff88023f5fffff] on node 1
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00240000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[4] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x000bf780
[ 0.000000] 0: 0x00100000 -> 0x00140000
[ 0.000000] 1: 0x00140000 -> 0x00240000
[ 0.000000] On node 0 totalpages: 1046287
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 5 pages reserved
[ 0.000000] DMA zone: 3914 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 16320 pages used for memmap
[ 0.000000] DMA32 zone: 763840 pages, LIFO batch:31
[ 0.000000] Normal zone: 4096 pages used for memmap
[ 0.000000] Normal zone: 258048 pages, LIFO batch:31
[ 0.000000] On node 1 totalpages: 1048576
[ 0.000000] Normal zone: 16384 pages used for memmap
[ 0.000000] Normal zone: 1032192 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x10] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x12] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x14] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x16] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x8c] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x8d] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x8e] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x8f] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x90] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x91] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x92] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x93] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x94] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x95] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x96] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x97] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: IOAPIC (id[0x03] address[0xfec8a000] gsi_base[24])
[ 0.000000] IOAPIC[1]: apic_id 3, version 32, address 0xfec8a000, GSI 24-47
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000
[ 0.000000] 24 Processors exceeds NR_CPUS limit of 16
[ 0.000000] SMP: Allowing 16 CPUs, 8 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 64
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e5000
[ 0.000000] PM: Registered nosave memory: 00000000000e5000 - 0000000000100000
[ 0.000000] PM: Registered nosave memory: 00000000bf780000 - 00000000bf78e000
[ 0.000000] PM: Registered nosave memory: 00000000bf78e000 - 00000000bf790000
[ 0.000000] PM: Registered nosave memory: 00000000bf790000 - 00000000bf79e000
[ 0.000000] PM: Registered nosave memory: 00000000bf79e000 - 00000000bf7d0000
[ 0.000000] PM: Registered nosave memory: 00000000bf7d0000 - 00000000bf7e0000
[ 0.000000] PM: Registered nosave memory: 00000000bf7e0000 - 00000000bf7ed000
[ 0.000000] PM: Registered nosave memory: 00000000bf7ed000 - 00000000c0000000
[ 0.000000] PM: Registered nosave memory: 00000000c0000000 - 00000000e0000000
[ 0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000
[ 0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fee00000
[ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000
[ 0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ffe00000
[ 0.000000] PM: Registered nosave memory: 00000000ffe00000 - 0000000100000000
[ 0.000000] Allocating PCI resources starting at c0000000 (gap: c0000000:20000000)
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:16 nr_node_ids:2
[ 0.000000] PERCPU: Embedded 27 pages/cpu @ffff88013bc00000 s81664 r8192 d20736 u262144
[ 0.000000] pcpu-alloc: s81664 r8192 d20736 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 00 01 02 03 08 10 12 14 [1] 04 05 06 07 09 11 13 15
[ 0.000000] Built 2 zonelists in Node order, mobility grouping on. Total pages: 2057994
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-rc3-mods root=UUID=a6d88530-6469-4ea2-91b9-410e088b4eff ro vt.handoff=7
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 8128652k/9437184k available (6332k kernel code, 1057732k absent, 250800k reserved, 6738k data, 824k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:4352 nr_irqs:1216 16
[ 0.000000] Extended CMOS year: 2000
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 67108864 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] hpet clockevent registered
[ 0.000000] Fast TSC calibration using PIT
[ 0.010000] Detected 2133.736 MHz processor.
[ 0.000007] Calibrating delay loop (skipped), value calculated using timer frequency.. 4267.47 BogoMIPS (lpj=21337360)
[ 0.000121] pid_max: default: 32768 minimum: 301
[ 0.000225] Security Framework initialized
[ 0.000292] AppArmor: AppArmor initialized
[ 0.001184] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.003717] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.004738] Mount-cache hash table entries: 256
[ 0.004994] Initializing cgroup subsys cpuacct
[ 0.005052] Initializing cgroup subsys memory
[ 0.005132] Initializing cgroup subsys devices
[ 0.005186] Initializing cgroup subsys freezer
[ 0.005240] Initializing cgroup subsys net_cls
[ 0.005294] Initializing cgroup subsys blkio
[ 0.005390] CPU: Physical Processor ID: 0
[ 0.005444] CPU: Processor Core ID: 0
[ 0.005500] mce: CPU supports 9 MCE banks
[ 0.005565] CPU0: Thermal monitoring enabled (TM1)
[ 0.005627] using mwait in idle threads.
[ 0.006824] ACPI: Core revision 20110623
[ 0.033891] ftrace: allocating 23820 entries in 94 pages
[ 0.043543] Switched APIC routing to physical flat.
[ 0.044062] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.143938] CPU0: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz stepping 05
[ 0.268149] APIC calibration not consistent with PM-Timer: 109ms instead of 100ms
[ 0.268224] APIC delta adjusted to PM-Timer: 833361 (916692)
[ 0.268284] Performance Events: PEBS fmt1+, erratum AAJ80 worked around, Nehalem events, Intel PMU driver.
[ 0.268481] ... version: 3
[ 0.268533] ... bit width: 48
[ 0.268585] ... generic registers: 4
[ 0.268638] ... value mask: 0000ffffffffffff
[ 0.268693] ... max period: 000000007fffffff
[ 0.269384] ... fixed-purpose events: 3
[ 0.269436] ... event mask: 000000070000000f
[ 0.328895] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.408011] Booting Node 0, Processors #1
[ 0.408079] smpboot cpu 1: start_ip = 9a000
[ 0.587739] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.647533] #2
[ 0.647567] smpboot cpu 2: start_ip = 9a000
[ 0.827286] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.887031] #3
[ 0.887065] smpboot cpu 3: start_ip = 9a000
[ 1.066736] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.126557] Ok.
[ 1.126608] Booting Node 1, Processors #4
[ 1.126679] smpboot cpu 4: start_ip = 9a000
[ 1.306278] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.366059] #5
[ 1.366095] smpboot cpu 5: start_ip = 9a000
[ 1.545829] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.605569] #6
[ 1.605604] smpboot cpu 6: start_ip = 9a000
[ 1.786387] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.845072] #7
[ 1.845107] smpboot cpu 7: start_ip = 9a000
[ 2.024846] NMI watchdog enabled, takes one hw-pmu counter.
[ 2.044645] Brought up 8 CPUs
[ 2.044699] Total of 8 processors activated (34228.01 BogoMIPS).
[ 2.048785] devtmpfs: initialized
[ 2.049019] PM: Registering ACPI NVS region at bf79e000 (204800 bytes)
[ 2.049966] print_constraints: dummy:
[ 2.050048] RTC time: 3:57:34, date: 08/27/11
[ 2.050146] NET: Registered protocol family 16
[ 2.050298] ACPI: bus type pci registered
[ 2.050409] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 2.050489] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
[ 2.091000] PCI: Using configuration type 1 for base access
[ 2.092003] bio: create slab <bio-0> at 0
[ 2.092155] ACPI: Added _OSI(Module Device)
[ 2.092208] ACPI: Added _OSI(Processor Device)
[ 2.092262] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 2.092316] ACPI: Added _OSI(Processor Aggregator Device)
[ 2.094011] ACPI: EC: Look up EC in DSDT
[ 2.094290] \_SB_:_OSC evaluation returned wrong type
[ 2.094292] _OSC request data:1 16
[ 2.095804] ACPI: Executed 1 blocks of module-level executable AML code
[ 2.098919] ACPI: SSDT 00000000bf79e0c0 011A4 (v01 DpgPmm P001Ist 00000011 INTL 20060113)
[ 2.099560] ACPI: Dynamic OEM Table Load:
[ 2.099670] ACPI: SSDT (null) 011A4 (v01 DpgPmm P001Ist 00000011 INTL 20060113)
[ 2.099901] ACPI: SSDT 00000000bf79f270 00678 (v01 PmRef P001Cst 00003001 INTL 20060113)
[ 2.100474] ACPI: Dynamic OEM Table Load:
[ 2.100583] ACPI: SSDT (null) 00678 (v01 PmRef P001Cst 00003001 INTL 20060113)
[ 2.100792] ACPI: SSDT 00000000bf79f8f0 003BA (v01 PmRef Cpu0Tst 00003000 INTL 20060113)
[ 2.101392] ACPI: Dynamic OEM Table Load:
[ 2.101502] ACPI: SSDT (null) 003BA (v01 PmRef Cpu0Tst 00003000 INTL 20060113)
[ 2.102186] ACPI: Interpreter enabled
[ 2.102240] ACPI: (supports S0 S1 S4 S5)
[ 2.102419] ACPI: Using IOAPIC for interrupt routing
[ 2.109762] ACPI: No dock devices found.
[ 2.109841] HEST: Table parsing has been initialized.
[ 2.109897] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 2.110059] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 2.110276] pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
[ 2.110335] pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
[ 2.110394] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
[ 2.110469] pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000dffff]
[ 2.110544] pci_root PNP0A08:00: host bridge window [mem 0xc0000000-0xdfffffff]
[ 2.110618] pci_root PNP0A08:00: host bridge window [mem 0xf0000000-0xfed8ffff]
[ 2.110708] pci 0000:00:00.0: [8086:3403] type 0 class 0x000600
[ 2.110759] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 2.110763] pci 0000:00:00.0: PME# disabled
[ 2.110790] pci 0000:00:01.0: [8086:3408] type 1 class 0x000604
[ 2.110840] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 2.110844] pci 0000:00:01.0: PME# disabled
[ 2.110868] pci 0000:00:02.0: [8086:3409] type 1 class 0x000604
[ 2.110917] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
[ 2.110920] pci 0000:00:02.0: PME# disabled
[ 2.110943] pci 0000:00:03.0: [8086:340a] type 1 class 0x000604
[ 2.110992] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 2.110996] pci 0000:00:03.0: PME# disabled
[ 2.111021] pci 0000:00:07.0: [8086:340e] type 1 class 0x000604
[ 2.111070] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[ 2.111073] pci 0000:00:07.0: PME# disabled
[ 2.111097] pci 0000:00:08.0: [8086:340f] type 1 class 0x000604
[ 2.111146] pci 0000:00:08.0: PME# supported from D0 D3hot D3cold
[ 2.111149] pci 0000:00:08.0: PME# disabled
[ 2.111172] pci 0000:00:09.0: [8086:3410] type 1 class 0x000604
[ 2.111221] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
[ 2.111225] pci 0000:00:09.0: PME# disabled
[ 2.111248] pci 0000:00:0a.0: [8086:3411] type 1 class 0x000604
[ 2.111296] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
[ 2.111300] pci 0000:00:0a.0: PME# disabled
[ 2.111323] pci 0000:00:10.0: [8086:3425] type 0 class 0x000800
[ 2.111391] pci 0000:00:10.1: [8086:3426] type 0 class 0x000800
[ 2.111454] pci 0000:00:11.0: [8086:3427] type 0 class 0x000800
[ 2.111520] pci 0000:00:11.1: [8086:3428] type 0 class 0x000800
[ 2.111585] pci 0000:00:14.0: [8086:342e] type 0 class 0x000800
[ 2.111653] pci 0000:00:14.1: [8086:3422] type 0 class 0x000800
[ 2.111720] pci 0000:00:14.2: [8086:3423] type 0 class 0x000800
[ 2.111783] pci 0000:00:14.3: [8086:3438] type 0 class 0x000800
[ 2.111847] pci 0000:00:16.0: [8086:3430] type 0 class 0x000880
[ 2.111861] pci 0000:00:16.0: reg 10: [mem 0xfbcd8000-0xfbcdbfff 64bit]
[ 2.111930] pci 0000:00:16.1: [8086:3431] type 0 class 0x000880
[ 2.111943] pci 0000:00:16.1: reg 10: [mem 0xfbcdc000-0xfbcdffff 64bit]
[ 2.112010] pci 0000:00:16.2: [8086:3432] type 0 class 0x000880
[ 2.112024] pci 0000:00:16.2: reg 10: [mem 0xfbce0000-0xfbce3fff 64bit]
[ 2.112091] pci 0000:00:16.3: [8086:3433] type 0 class 0x000880
[ 2.112104] pci 0000:00:16.3: reg 10: [mem 0xfbce4000-0xfbce7fff 64bit]
[ 2.112171] pci 0000:00:16.4: [8086:3429] type 0 class 0x000880
[ 2.112185] pci 0000:00:16.4: reg 10: [mem 0xfbce8000-0xfbcebfff 64bit]
[ 2.112251] pci 0000:00:16.5: [8086:342a] type 0 class 0x000880
[ 2.112265] pci 0000:00:16.5: reg 10: [mem 0xfbcec000-0xfbceffff 64bit]
[ 2.112332] pci 0000:00:16.6: [8086:342b] type 0 class 0x000880
[ 2.112346] pci 0000:00:16.6: reg 10: [mem 0xfbcf0000-0xfbcf3fff 64bit]
[ 2.112413] pci 0000:00:16.7: [8086:342c] type 0 class 0x000880
[ 2.112426] pci 0000:00:16.7: reg 10: [mem 0xfbcf4000-0xfbcf7fff 64bit]
[ 2.112496] pci 0000:00:1a.0: [8086:3a37] type 0 class 0x000c03
[ 2.112541] pci 0000:00:1a.0: reg 20: [io 0xa400-0xa41f]
[ 2.112588] pci 0000:00:1a.1: [8086:3a38] type 0 class 0x000c03
[ 2.112633] pci 0000:00:1a.1: reg 20: [io 0xa480-0xa49f]
[ 2.112689] pci 0000:00:1a.7: [8086:3a3c] type 0 class 0x000c03
[ 2.112711] pci 0000:00:1a.7: reg 10: [mem 0xfbcfd000-0xfbcfd3ff]
[ 2.112788] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[ 2.112792] pci 0000:00:1a.7: PME# disabled
[ 2.112817] pci 0000:00:1b.0: [8086:3a3e] type 0 class 0x000403
[ 2.112833] pci 0000:00:1b.0: reg 10: [mem 0xfbcf8000-0xfbcfbfff 64bit]
[ 2.112890] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 2.112894] pci 0000:00:1b.0: PME# disabled
[ 2.112915] pci 0000:00:1d.0: [8086:3a34] type 0 class 0x000c03
[ 2.112960] pci 0000:00:1d.0: reg 20: [io 0xa800-0xa81f]
[ 2.113006] pci 0000:00:1d.1: [8086:3a35] type 0 class 0x000c03
[ 2.113052] pci 0000:00:1d.1: reg 20: [io 0xa880-0xa89f]
[ 2.113097] pci 0000:00:1d.2: [8086:3a36] type 0 class 0x000c03
[ 2.113142] pci 0000:00:1d.2: reg 20: [io 0xac00-0xac1f]
[ 2.113187] pci 0000:00:1d.3: [8086:3a39] type 0 class 0x000c03
[ 2.113234] pci 0000:00:1d.3: reg 20: [io 0xb000-0xb01f]
[ 2.113288] pci 0000:00:1d.7: [8086:3a3a] type 0 class 0x000c03
[ 2.113310] pci 0000:00:1d.7: reg 10: [mem 0xfbcfe000-0xfbcfe3ff]
[ 2.113386] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 2.113391] pci 0000:00:1d.7: PME# disabled
[ 2.113413] pci 0000:00:1e.0: [8086:244e] type 1 class 0x000604
[ 2.113472] pci 0000:00:1f.0: [8086:3a16] type 0 class 0x000601
[ 2.113557] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0ca0 (mask 0003)
[ 2.113635] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0294 (mask 0003)
[ 2.113744] pci 0000:00:1f.2: [8086:3a20] type 0 class 0x000101
[ 2.113760] pci 0000:00:1f.2: reg 10: [io 0xbc00-0xbc07]
[ 2.113769] pci 0000:00:1f.2: reg 14: [io 0xb880-0xb883]
[ 2.113778] pci 0000:00:1f.2: reg 18: [io 0xb800-0xb807]
[ 2.113786] pci 0000:00:1f.2: reg 1c: [io 0xb480-0xb483]
[ 2.113794] pci 0000:00:1f.2: reg 20: [io 0xb400-0xb40f]
[ 2.113803] pci 0000:00:1f.2: reg 24: [io 0xb080-0xb08f]
[ 2.113841] pci 0000:00:1f.3: [8086:3a30] type 0 class 0x000c05
[ 2.113857] pci 0000:00:1f.3: reg 10: [mem 0xfbcff000-0xfbcff0ff 64bit]
[ 2.113880] pci 0000:00:1f.3: reg 20: [io 0x0400-0x041f]
[ 2.113913] pci 0000:00:1f.5: [8086:3a26] type 0 class 0x000101
[ 2.113930] pci 0000:00:1f.5: reg 10: [io 0xcc00-0xcc07]
[ 2.113938] pci 0000:00:1f.5: reg 14: [io 0xc880-0xc883]
[ 2.113946] pci 0000:00:1f.5: reg 18: [io 0xc800-0xc807]
[ 2.113955] pci 0000:00:1f.5: reg 1c: [io 0xc480-0xc483]
[ 2.113963] pci 0000:00:1f.5: reg 20: [io 0xc400-0xc40f]
[ 2.113972] pci 0000:00:1f.5: reg 24: [io 0xc080-0xc08f]
[ 2.114060] pci 0000:08:00.0: [168c:002b] type 0 class 0x000280
[ 2.114078] pci 0000:08:00.0: reg 10: [mem 0xfbef0000-0xfbefffff 64bit]
[ 2.114146] pci 0000:08:00.0: supports D1
[ 2.114148] pci 0000:08:00.0: PME# supported from D0 D1 D3hot
[ 2.114152] pci 0000:08:00.0: PME# disabled
[ 2.124507] pci 0000:00:01.0: PCI bridge to [bus 08-08]
[ 2.124569] pci 0000:00:01.0: bridge window [mem 0xfbe00000-0xfbefffff]
[ 2.124618] pci 0000:00:02.0: PCI bridge to [bus 07-07]
[ 2.124717] pci 0000:00:03.0: PCI bridge to [bus 06-06]
[ 2.124826] pci 0000:05:00.0: [1002:68f9] type 0 class 0x000300
[ 2.124840] pci 0000:05:00.0: reg 10: [mem 0xd0000000-0xdfffffff 64bit pref]
[ 2.124852] pci 0000:05:00.0: reg 18: [mem 0xfbdc0000-0xfbddffff 64bit]
[ 2.124860] pci 0000:05:00.0: reg 20: [io 0xe000-0xe0ff]
[ 2.124874] pci 0000:05:00.0: reg 30: [mem 0xfbda0000-0xfbdbffff pref]
[ 2.124894] pci 0000:05:00.0: supports D1 D2
[ 2.124917] pci 0000:05:00.1: [1002:aa68] type 0 class 0x000403
[ 2.124931] pci 0000:05:00.1: reg 10: [mem 0xfbdfc000-0xfbdfffff 64bit]
[ 2.124980] pci 0000:05:00.1: supports D1 D2
[ 2.144467] pci 0000:00:07.0: PCI bridge to [bus 05-05]
[ 2.144527] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 2.144532] pci 0000:00:07.0: bridge window [mem 0xfbd00000-0xfbdfffff]
[ 2.144539] pci 0000:00:07.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 2.144584] pci 0000:00:08.0: PCI bridge to [bus 04-04]
[ 2.144687] pci 0000:00:09.0: PCI bridge to [bus 03-03]
[ 2.144785] pci 0000:00:0a.0: PCI bridge to [bus 02-02]
[ 2.144884] pci 0000:01:04.0: [1102:0007] type 0 class 0x000401
[ 2.144902] pci 0000:01:04.0: reg 10: [io 0xdc00-0xdc1f]
[ 2.144971] pci 0000:01:04.0: supports D1 D2
[ 2.145012] pci 0000:00:1e.0: PCI bridge to [bus 01-01] (subtractive decode)
[ 2.145073] pci 0000:00:1e.0: bridge window [io 0xd000-0xdfff]
[ 2.145081] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
[ 2.145083] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 2.145086] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 2.145089] pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
[ 2.145091] pci 0000:00:1e.0: bridge window [mem 0xc0000000-0xdfffffff] (subtractive decode)
[ 2.145094] pci 0000:00:1e.0: bridge window [mem 0xf0000000-0xfed8ffff] (subtractive decode)
[ 2.145126] pci 0000:00:01.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.145189] pci 0000:00:01.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.145247] pci 0000:08:00.0: Dev MPS 128 MPSS 128 MRRS 512
[ 2.145303] pci 0000:08:00.0: MPS configured higher than maximum supported by the device. If a bus issue occurs, try running with pci=pcie_bus_safe.
[ 2.145404] pci 0000:08:00.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.145462] pci 0000:00:02.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.145524] pci 0000:00:02.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.145581] pci 0000:00:03.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.145644] pci 0000:00:03.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.145701] pci 0000:00:07.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.145763] pci 0000:00:07.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.145820] pci 0000:05:00.0: Dev MPS 256 MPSS 256 MRRS 512
[ 2.145885] pci 0000:05:00.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.145942] pci 0000:05:00.1: Dev MPS 256 MPSS 256 MRRS 512
[ 2.146007] pci 0000:05:00.1: Dev MPS 256 MPSS 256 MRRS 128
[ 2.146064] pci 0000:00:08.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.146126] pci 0000:00:08.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.146184] pci 0000:00:09.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.146246] pci 0000:00:09.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.146303] pci 0000:00:0a.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.146365] pci 0000:00:0a.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.146423] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 2.146624] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 2.146711] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE1._PRT]
[ 2.146739] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE2._PRT]
[ 2.146766] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE3._PRT]
[ 2.146806] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE7._PRT]
[ 2.146832] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE8._PRT]
[ 2.146857] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE9._PRT]
[ 2.146882] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPEA._PRT]
[ 2.146906] pci0000:00: Requesting ACPI _OSC control (0x1d)
[ 2.146964] pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
[ 2.147040] ACPI _OSC control for PCIe not granted, disabling ASPM
[ 2.164684] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12 14 15)
[ 2.165091] ACPI: PCI Interrupt Link [LNKB] (IRQs *5)
[ 2.165267] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 *7 10 11 12 14 15)
[ 2.165672] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 *10 11 12 14 15)
[ 2.166076] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
[ 2.166554] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12 14 *15)
[ 2.166958] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 6 7 10 11 12 *14 15)
[ 2.167363] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 10 *11 12 14 15)
[ 2.167856] vgaarb: device added: PCI:0000:05:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 2.167934] vgaarb: loaded
[ 2.167983] vgaarb: bridge control possible 0000:05:00.0
[ 2.168206] SCSI subsystem initialized
[ 2.168302] libata version 3.00 loaded.
[ 2.168346] usbcore: registered new interface driver usbfs
[ 2.168410] usbcore: registered new interface driver hub
[ 2.168492] usbcore: registered new device driver usb
[ 2.168663] wmi: Mapper loaded
[ 2.168714] PCI: Using ACPI for IRQ routing
[ 2.175190] PCI: Discovered peer bus fe
[ 2.175266] pci 0000:fe:00.0: [8086:2c40] type 0 class 0x000600
[ 2.175292] pci 0000:fe:00.1: [8086:2c01] type 0 class 0x000600
[ 2.175319] pci 0000:fe:02.0: [8086:2c10] type 0 class 0x000600
[ 2.175343] pci 0000:fe:02.1: [8086:2c11] type 0 class 0x000600
[ 2.175367] pci 0000:fe:02.4: [8086:2c14] type 0 class 0x000600
[ 2.175393] pci 0000:fe:02.5: [8086:2c15] type 0 class 0x000600
[ 2.175418] pci 0000:fe:03.0: [8086:2c18] type 0 class 0x000600
[ 2.175441] pci 0000:fe:03.1: [8086:2c19] type 0 class 0x000600
[ 2.175464] pci 0000:fe:03.2: [8086:2c1a] type 0 class 0x000600
[ 2.175488] pci 0000:fe:03.4: [8086:2c1c] type 0 class 0x000600
[ 2.175513] pci 0000:fe:04.0: [8086:2c20] type 0 class 0x000600
[ 2.175536] pci 0000:fe:04.1: [8086:2c21] type 0 class 0x000600
[ 2.175559] pci 0000:fe:04.2: [8086:2c22] type 0 class 0x000600
[ 2.175585] pci 0000:fe:04.3: [8086:2c23] type 0 class 0x000600
[ 2.175611] pci 0000:fe:05.0: [8086:2c28] type 0 class 0x000600
[ 2.175634] pci 0000:fe:05.1: [8086:2c29] type 0 class 0x000600
[ 2.175658] pci 0000:fe:05.2: [8086:2c2a] type 0 class 0x000600
[ 2.175681] pci 0000:fe:05.3: [8086:2c2b] type 0 class 0x000600
[ 2.175707] pci 0000:fe:06.0: [8086:2c30] type 0 class 0x000600
[ 2.175730] pci 0000:fe:06.1: [8086:2c31] type 0 class 0x000600
[ 2.175753] pci 0000:fe:06.2: [8086:2c32] type 0 class 0x000600
[ 2.175779] pci 0000:fe:06.3: [8086:2c33] type 0 class 0x000600
[ 2.176249] PCI: Discovered peer bus ff
[ 2.176325] pci 0000:ff:00.0: [8086:2c40] type 0 class 0x000600
[ 2.176347] pci 0000:ff:00.1: [8086:2c01] type 0 class 0x000600
[ 2.176370] pci 0000:ff:02.0: [8086:2c10] type 0 class 0x000600
[ 2.176391] pci 0000:ff:02.1: [8086:2c11] type 0 class 0x000600
[ 2.176413] pci 0000:ff:02.4: [8086:2c14] type 0 class 0x000600
[ 2.176433] pci 0000:ff:02.5: [8086:2c15] type 0 class 0x000600
[ 2.176455] pci 0000:ff:03.0: [8086:2c18] type 0 class 0x000600
[ 2.176478] pci 0000:ff:03.1: [8086:2c19] type 0 class 0x000600
[ 2.176498] pci 0000:ff:03.2: [8086:2c1a] type 0 class 0x000600
[ 2.176519] pci 0000:ff:03.4: [8086:2c1c] type 0 class 0x000600
[ 2.176541] pci 0000:ff:04.0: [8086:2c20] type 0 class 0x000600
[ 2.176562] pci 0000:ff:04.1: [8086:2c21] type 0 class 0x000600
[ 2.176582] pci 0000:ff:04.2: [8086:2c22] type 0 class 0x000600
[ 2.176603] pci 0000:ff:04.3: [8086:2c23] type 0 class 0x000600
[ 2.176625] pci 0000:ff:05.0: [8086:2c28] type 0 class 0x000600
[ 2.176648] pci 0000:ff:05.1: [8086:2c29] type 0 class 0x000600
[ 2.176669] pci 0000:ff:05.2: [8086:2c2a] type 0 class 0x000600
[ 2.176689] pci 0000:ff:05.3: [8086:2c2b] type 0 class 0x000600
[ 2.176712] pci 0000:ff:06.0: [8086:2c30] type 0 class 0x000600
[ 2.176733] pci 0000:ff:06.1: [8086:2c31] type 0 class 0x000600
[ 2.176753] pci 0000:ff:06.2: [8086:2c32] type 0 class 0x000600
[ 2.176774] pci 0000:ff:06.3: [8086:2c33] type 0 class 0x000600
[ 2.177256] PCI: pci_cache_line_size set to 64 bytes
[ 2.177469] reserve RAM buffer: 000000000009fc00 - 000000000009ffff
[ 2.177471] reserve RAM buffer: 00000000bf780000 - 00000000bfffffff
[ 2.177562] NetLabel: Initializing
[ 2.177614] NetLabel: domain hash size = 128
[ 2.177667] NetLabel: protocols = UNLABELED CIPSOv4
[ 2.177734] NetLabel: unlabeled traffic allowed by default
[ 2.177839] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
[ 2.177901] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 2.178097] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 2.254453] Switching to clocksource hpet
[ 2.255453] Switched to NOHz mode on CPU #6
[ 2.263684] AppArmor: AppArmor Filesystem Enabled
[ 2.263768] pnp: PnP ACPI init
[ 2.263834] ACPI: bus type pnp registered
[ 2.264010] pnp 00:00: [bus 00-ff]
[ 2.264013] pnp 00:00: [io 0x0cf8-0x0cff]
[ 2.264015] pnp 00:00: [io 0x0000-0x0cf7 window]
[ 2.264017] pnp 00:00: [io 0x0d00-0xffff window]
[ 2.264020] pnp 00:00: [mem 0x000a0000-0x000bffff window]
[ 2.264025] pnp 00:00: [mem 0x000d0000-0x000dffff window]
[ 2.264027] pnp 00:00: [mem 0xc0000000-0xdfffffff window]
[ 2.264029] pnp 00:00: [mem 0xf0000000-0xfed8ffff window]
[ 2.264116] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
[ 2.264127] pnp 00:01: [mem 0xfbf00000-0xfbffffff]
[ 2.264129] pnp 00:01: [mem 0xfc000000-0xfcffffff]
[ 2.264131] pnp 00:01: [mem 0xfd000000-0xfdffffff]
[ 2.264133] pnp 00:01: [mem 0xfe000000-0xfebfffff]
[ 2.264135] pnp 00:01: [mem 0xfec8a000-0xfec8afff]
[ 2.264137] pnp 00:01: [mem 0xfed10000-0xfed10fff]
[ 2.264232] Switched to NOHz mode on CPU #0
[ 2.264312] Switched to NOHz mode on CPU #3
[ 2.264319] Switched to NOHz mode on CPU #1
[ 2.264326] Switched to NOHz mode on CPU #4
[ 2.264330] system 00:01: [mem 0xfbf00000-0xfbffffff] has been reserved
[ 2.264333] system 00:01: [mem 0xfc000000-0xfcffffff] has been reserved
[ 2.264335] system 00:01: [mem 0xfd000000-0xfdffffff] has been reserved
[ 2.264337] system 00:01: [mem 0xfe000000-0xfebfffff] has been reserved
[ 2.264340] system 00:01: [mem 0xfec8a000-0xfec8afff] could not be reserved
[ 2.264342] system 00:01: [mem 0xfed10000-0xfed10fff] has been reserved
[ 2.264345] system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 2.264362] Switched to NOHz mode on CPU #2
[ 2.264376] Switched to NOHz mode on CPU #5
[ 2.264381] pnp 00:02: [dma 4]
[ 2.264384] Switched to NOHz mode on CPU #7
[ 2.264388] pnp 00:02: [io 0x0000-0x000f]
[ 2.264390] pnp 00:02: [io 0x0081-0x0083]
[ 2.264391] pnp 00:02: [io 0x0087]
[ 2.264393] pnp 00:02: [io 0x0089-0x008b]
[ 2.264394] pnp 00:02: [io 0x008f]
[ 2.264396] pnp 00:02: [io 0x00c0-0x00df]
[ 2.264428] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
[ 2.264439] pnp 00:03: [io 0x0070-0x0071]
[ 2.264450] pnp 00:03: [irq 8]
[ 2.264478] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 2.264486] pnp 00:04: [io 0x0061]
[ 2.264527] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
[ 2.264537] pnp 00:05: [io 0x00f0-0x00ff]
[ 2.264542] pnp 00:05: [irq 13]
[ 2.264570] pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 2.264730] pnp 00:06: [io 0x0000-0xffffffffffffffff disabled]
[ 2.264732] pnp 00:06: [io 0x0000-0xffffffffffffffff disabled]
[ 2.264734] pnp 00:06: [io 0x0290-0x029f]
[ 2.264819] system 00:06: [io 0x0290-0x029f] has been reserved
[ 2.264823] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.264936] pnp 00:07: [io 0x0010-0x001f]
[ 2.264938] pnp 00:07: [io 0x0022-0x003f]
[ 2.264940] pnp 00:07: [io 0x0044-0x005f]
[ 2.264941] pnp 00:07: [io 0x0062-0x0063]
[ 2.264943] pnp 00:07: [io 0x0065-0x006f]
[ 2.264944] pnp 00:07: [io 0x0072-0x007f]
[ 2.264946] pnp 00:07: [io 0x0080]
[ 2.264947] pnp 00:07: [io 0x0084-0x0086]
[ 2.264949] pnp 00:07: [io 0x0088]
[ 2.264950] pnp 00:07: [io 0x008c-0x008e]
[ 2.264952] pnp 00:07: [io 0x0090-0x009f]
[ 2.264953] pnp 00:07: [io 0x00a2-0x00bf]
[ 2.264955] pnp 00:07: [io 0x00e0-0x00ef]
[ 2.264956] pnp 00:07: [io 0x04d0-0x04d1]
[ 2.264958] pnp 00:07: [io 0x0ca0-0x0caf]
[ 2.264959] pnp 00:07: [io 0x0800-0x087f]
[ 2.264961] pnp 00:07: [io 0x0000-0xffffffffffffffff disabled]
[ 2.264963] pnp 00:07: [io 0x0500-0x057f]
[ 2.264969] pnp 00:07: [mem 0xfed1c000-0xfed1ffff]
[ 2.264971] pnp 00:07: [mem 0xfed20000-0xfed3ffff]
[ 2.264972] pnp 00:07: [mem 0xfed40000-0xfed8ffff]
[ 2.265078] system 00:07: [io 0x04d0-0x04d1] has been reserved
[ 2.265136] system 00:07: [io 0x0ca0-0x0caf] has been reserved
[ 2.265194] system 00:07: [io 0x0800-0x087f] has been reserved
[ 2.265251] system 00:07: [io 0x0500-0x057f] has been reserved
[ 2.265308] system 00:07: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 2.265367] system 00:07: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 2.265426] system 00:07: [mem 0xfed40000-0xfed8ffff] has been reserved
[ 2.265485] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.265538] pnp 00:08: [mem 0xfed00000-0xfed003ff]
[ 2.265571] pnp 00:08: Plug and Play ACPI device, IDs PNP0103 (active)
[ 2.265780] pnp 00:09: [io 0x03f8-0x03ff]
[ 2.265787] pnp 00:09: [irq 4]
[ 2.265789] pnp 00:09: [dma 0 disabled]
[ 2.265863] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
[ 2.266083] pnp 00:0a: [io 0x02f8-0x02ff]
[ 2.266089] pnp 00:0a: [irq 3]
[ 2.266091] pnp 00:0a: [dma 0 disabled]
[ 2.266192] pnp 00:0a: Plug and Play ACPI device, IDs PNP0501 (active)
[ 2.266263] pnp 00:0b: [mem 0xfec00000-0xfec00fff]
[ 2.266265] pnp 00:0b: [mem 0xfee00000-0xfee00fff]
[ 2.266351] system 00:0b: [mem 0xfec00000-0xfec00fff] could not be reserved
[ 2.266412] system 00:0b: [mem 0xfee00000-0xfee00fff] has been reserved
[ 2.266472] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.266528] pnp 00:0c: [io 0x0060]
[ 2.266530] pnp 00:0c: [io 0x0064]
[ 2.266536] pnp 00:0c: [irq 12]
[ 2.266585] pnp 00:0c: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
[ 2.266622] pnp 00:0d: [mem 0xe0000000-0xefffffff]
[ 2.266708] system 00:0d: [mem 0xe0000000-0xefffffff] has been reserved
[ 2.266768] system 00:0d: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.266932] pnp 00:0e: [mem 0x00000000-0x0009ffff]
[ 2.266934] pnp 00:0e: [mem 0x000c0000-0x000cffff]
[ 2.266936] pnp 00:0e: [mem 0x000e0000-0x000fffff]
[ 2.266938] pnp 00:0e: [mem 0x00100000-0xbfffffff]
[ 2.266940] pnp 00:0e: [mem 0xfed90000-0xffffffff]
[ 2.267041] system 00:0e: [mem 0x00000000-0x0009ffff] could not be reserved
[ 2.267102] system 00:0e: [mem 0x000c0000-0x000cffff] could not be reserved
[ 2.267161] system 00:0e: [mem 0x000e0000-0x000fffff] could not be reserved
[ 2.267221] system 00:0e: [mem 0x00100000-0xbfffffff] could not be reserved
[ 2.267280] system 00:0e: [mem 0xfed90000-0xffffffff] could not be reserved
[ 2.267341] system 00:0e: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 2.267463] pnp: PnP ACPI: found 15 devices
[ 2.267517] ACPI: ACPI bus type pnp unregistered
[ 2.274994] PCI: max bus depth: 1 pci_try_num: 2
[ 2.275055] pci 0000:00:01.0: PCI bridge to [bus 08-08]
[ 2.275114] pci 0000:00:01.0: bridge window [mem 0xfbe00000-0xfbefffff]
[ 2.275178] pci 0000:00:02.0: PCI bridge to [bus 07-07]
[ 2.275240] pci 0000:00:03.0: PCI bridge to [bus 06-06]
[ 2.275303] pci 0000:00:07.0: PCI bridge to [bus 05-05]
[ 2.275359] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 2.275418] pci 0000:00:07.0: bridge window [mem 0xfbd00000-0xfbdfffff]
[ 2.275478] pci 0000:00:07.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 2.277343] pci 0000:00:08.0: PCI bridge to [bus 04-04]
[ 2.277405] pci 0000:00:09.0: PCI bridge to [bus 03-03]
[ 2.277467] pci 0000:00:0a.0: PCI bridge to [bus 02-02]
[ 2.277530] pci 0000:00:1e.0: PCI bridge to [bus 01-01]
[ 2.277586] pci 0000:00:1e.0: bridge window [io 0xd000-0xdfff]
[ 2.277660] pci 0000:00:01.0: setting latency timer to 64
[ 2.277667] pci 0000:00:02.0: setting latency timer to 64
[ 2.277673] pci 0000:00:03.0: setting latency timer to 64
[ 2.277680] pci 0000:00:07.0: setting latency timer to 64
[ 2.277687] pci 0000:00:08.0: setting latency timer to 64
[ 2.277693] pci 0000:00:09.0: setting latency timer to 64
[ 2.277700] pci 0000:00:0a.0: setting latency timer to 64
[ 2.277707] pci 0000:00:1e.0: setting latency timer to 64
[ 2.277712] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 2.277714] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 2.277717] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 2.277719] pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
[ 2.277721] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xdfffffff]
[ 2.277723] pci_bus 0000:00: resource 9 [mem 0xf0000000-0xfed8ffff]
[ 2.277726] pci_bus 0000:08: resource 1 [mem 0xfbe00000-0xfbefffff]
[ 2.277728] pci_bus 0000:05: resource 0 [io 0xe000-0xefff]
[ 2.277730] pci_bus 0000:05: resource 1 [mem 0xfbd00000-0xfbdfffff]
[ 2.277733] pci_bus 0000:05: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
[ 2.277736] pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
[ 2.277738] pci_bus 0000:01: resource 4 [io 0x0000-0x0cf7]
[ 2.277740] pci_bus 0000:01: resource 5 [io 0x0d00-0xffff]
[ 2.277743] pci_bus 0000:01: resource 6 [mem 0x000a0000-0x000bffff]
[ 2.277745] pci_bus 0000:01: resource 7 [mem 0x000d0000-0x000dffff]
[ 2.277747] pci_bus 0000:01: resource 8 [mem 0xc0000000-0xdfffffff]
[ 2.277749] pci_bus 0000:01: resource 9 [mem 0xf0000000-0xfed8ffff]
[ 2.277752] pci_bus 0000:fe: resource 0 [io 0x0000-0xffff]
[ 2.277754] pci_bus 0000:fe: resource 1 [mem 0x00000000-0xffffffffff]
[ 2.277757] pci_bus 0000:ff: resource 0 [io 0x0000-0xffff]
[ 2.277759] pci_bus 0000:ff: resource 1 [mem 0x00000000-0xffffffffff]
[ 2.277805] NET: Registered protocol family 2
[ 2.278122] IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 2.279475] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
[ 2.281596] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 2.281940] TCP: Hash tables configured (established 524288 bind 65536)
[ 2.281998] TCP reno registered
[ 2.282065] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[ 2.282170] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[ 2.282403] NET: Registered protocol family 1
[ 2.282673] pci 0000:05:00.0: Boot video device
[ 2.282759] PCI: CLS 256 bytes, default 64
[ 2.282817] Trying to unpack rootfs image as initramfs...
[ 3.065411] Freeing initrd memory: 36452k freed
[ 3.074627] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 3.074692] Placing 64MB software IO TLB between ffff8800bb77b000 - ffff8800bf77b000
[ 3.074768] software IO TLB at phys 0xbb77b000 - 0xbf77b000
[ 3.076438] audit: initializing netlink socket (disabled)
[ 3.076511] type=2000 audit(1314417454.880:1): initialized
[ 3.116839] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 3.163866] VFS: Disk quotas dquot_6.5.2
[ 3.164001] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 3.164771] fuse init (API version 7.17)
[ 3.164933] msgmni has been set to 15947
[ 3.165302] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 3.165411] io scheduler noop registered
[ 3.165463] io scheduler deadline registered
[ 3.165557] io scheduler cfq registered (default)
[ 3.166127] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 3.166207] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 3.166366] intel_idle: MWAIT substates: 0x1120
[ 3.166381] intel_idle: v0.4 model 0x1A
[ 3.166383] intel_idle: lapic_timer_reliable_states 0x2
[ 3.166522] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
[ 3.166602] ACPI: Power Button [PWRB]
[ 3.166690] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 3.166765] ACPI: Power Button [PWRF]
[ 3.167029] ACPI: acpi_idle yielding to intel_idle
[ 3.170184] ERST: Failed to get Error Log Address Range.
[ 3.322393] [Firmware Warn]: GHES: Poll interval is 0 for generic hardware error source: 1, disabled.
[ 3.322536] \_SB_:_OSC evaluation returned wrong type
[ 3.322538] _OSC request data:1 0 0
[ 3.322542] GHES: Failed to enable APEI firmware first mode.
[ 3.322676] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 3.343234] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 3.592304] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 4.070817] Refined TSC clocksource calibration: 2133.408 MHz.
[ 4.070880] Switching to clocksource tsc
[ 8.532332] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 8.691884] 00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 8.831330] Linux agpgart interface v0.103
[ 8.832723] brd: module loaded
[ 8.833445] loop: module loaded
[ 8.833706] ata_piix 0000:00:1f.2: version 2.13
[ 8.833735] ata_piix 0000:00:1f.2: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 8.833802] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 8.834046] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 8.834274] scsi0 : ata_piix
[ 8.834421] scsi1 : ata_piix
[ 8.835412] ata1: SATA max UDMA/133 cmd 0xbc00 ctl 0xb880 bmdma 0xb400 irq 23
[ 8.835476] ata2: SATA max UDMA/133 cmd 0xb800 ctl 0xb480 bmdma 0xb408 irq 23
[ 8.835560] ata_piix 0000:00:1f.5: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[ 8.835623] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[ 8.835854] ata_piix 0000:00:1f.5: setting latency timer to 64
[ 8.836022] scsi2 : ata_piix
[ 8.836143] scsi3 : ata_piix
[ 8.836950] ata3: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 21
[ 8.837012] ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 21
[ 8.837407] Fixed MDIO Bus: probed
[ 8.837489] PPP generic driver version 2.4.2
[ 8.837584] tun: Universal TUN/TAP device driver, 1.6
[ 8.837639] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 8.837779] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 8.837863] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 8.837942] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[ 8.837946] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[ 8.838046] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
[ 8.838152] ehci_hcd 0000:00:1a.7: debug port 1
[ 8.842072] ehci_hcd 0000:00:1a.7: cache line size of 256 is not supported
[ 8.842094] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfbcfd000
[ 8.860974] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 8.861152] hub 1-0:1.0: USB hub found
[ 8.861208] hub 1-0:1.0: 4 ports detected
[ 8.861366] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 8.861438] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 8.861441] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 8.861540] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[ 8.861638] ehci_hcd 0000:00:1d.7: debug port 1
[ 8.865553] ehci_hcd 0000:00:1d.7: cache line size of 256 is not supported
[ 8.865559] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfbcfe000
[ 8.880933] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 8.881094] hub 2-0:1.0: USB hub found
[ 8.881148] hub 2-0:1.0: 8 ports detected
[ 8.881300] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 8.881377] uhci_hcd: USB Universal Host Controller Interface driver
[ 8.881469] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 8.881533] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[ 8.881536] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 8.881636] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[ 8.881744] uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000a400
[ 8.881909] hub 3-0:1.0: USB hub found
[ 8.881964] hub 3-0:1.0: 2 ports detected
[ 8.882100] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[ 8.882164] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[ 8.882167] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 8.882271] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[ 8.882368] uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000a480
[ 8.882535] hub 4-0:1.0: USB hub found
[ 8.882589] hub 4-0:1.0: 2 ports detected
[ 8.882733] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 8.882796] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 8.882800] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 8.882896] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
[ 8.882998] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000a800
[ 8.883162] hub 5-0:1.0: USB hub found
[ 8.883216] hub 5-0:1.0: 2 ports detected
[ 8.883359] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 8.883422] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 8.883425] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 8.883521] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
[ 8.883627] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000a880
[ 8.883791] hub 6-0:1.0: USB hub found
[ 8.883845] hub 6-0:1.0: 2 ports detected
[ 8.883981] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 8.884045] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 8.884048] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 8.884138] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
[ 8.884236] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000ac00
[ 8.884396] hub 7-0:1.0: USB hub found
[ 8.884451] hub 7-0:1.0: 2 ports detected
[ 8.884585] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
[ 8.884649] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[ 8.884652] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 8.884747] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 8
[ 8.884844] uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000b000
[ 8.885012] hub 8-0:1.0: USB hub found
[ 8.885066] hub 8-0:1.0: 2 ports detected
[ 8.885254] i8042: PNP: PS/2 Controller [PNP0f03:PS2M] at 0x60,0x64 irq 12
[ 8.885313] i8042: PNP: PS/2 controller doesn't have KBD irq; using default 1
[ 8.888032] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 8.888115] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 8.888286] mousedev: PS/2 mouse device common for all mice
[ 8.888491] rtc_cmos 00:03: RTC can wake from S4
[ 8.888652] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 8.888733] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 8.888901] device-mapper: uevent: version 1.0.3
[ 8.889039] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: dm-devel@redhat.com
[ 8.889187] device-mapper: multipath: version 1.3.0 loaded
[ 8.889243] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 8.889571] cpuidle: using governor ladder
[ 8.889902] cpuidle: using governor menu
[ 8.889955] EFI Variables Facility v0.08 2004-May-17
[ 8.890278] TCP cubic registered
[ 8.890469] NET: Registered protocol family 10
[ 8.891188] NET: Registered protocol family 17
[ 8.891259] Registering the dns_resolver key type
[ 8.891757] PM: Hibernation image not present or could not be loaded.
[ 8.891777] registered taskstats version 1
[ 8.915951] Magic number: 7:798:968
[ 8.916410] rtc_cmos 00:03: setting system clock to 2011-08-27 03:57:41 UTC (1314417461)
[ 8.920140] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 8.920198] EDD information not available.
[ 9.191450] ata4: SATA link down (SStatus 0 SControl 300)
[ 9.202392] ata3: SATA link down (SStatus 0 SControl 300)
[ 9.260263] usb 2-2: new high speed USB device number 3 using ehci_hcd
[ 9.689505] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 9.689579] ata1.01: SATA link down (SStatus 0 SControl 300)
[ 9.689819] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9.689888] ata2.01: SATA link down (SStatus 0 SControl 300)
[ 9.689953] ata2.01: link offline, clearing class 3 to NONE
[ 9.699551] usb 5-1: new low speed USB device number 2 using uhci_hcd
[ 9.709637] ata2.00: ATAPI: Optiarc DVD RW AD-7260S, 1.03, max UDMA/100
[ 9.710207] ata1.00: ATA-8: ST31000524AS, JC45, max UDMA/133
[ 9.710270] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 9.749637] ata2.00: configured for UDMA/100
[ 9.749840] ata1.00: configured for UDMA/133
[ 9.750281] scsi 0:0:0:0: Direct-Access ATA ST31000524AS JC45 PQ: 0 ANSI: 5
[ 9.750746] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 9.750843] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 9.750968] sd 0:0:0:0: [sda] Write Protect is off
[ 9.751672] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 9.751696] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9.752651] scsi 1:0:0:0: CD-ROM Optiarc DVD RW AD-7260S 1.03 PQ: 0 ANSI: 5
[ 9.755309] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[ 9.755391] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 9.755642] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 9.755900] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 9.788275] sda: sda1 sda2 < sda5 >
[ 9.789425] sd 0:0:0:0: [sda] Attached SCSI disk
[ 9.792053] Freeing unused kernel memory: 824k freed
[ 9.792287] Write protecting the kernel read-only data: 12288k
[ 9.801259] Freeing unused kernel memory: 1836k freed
[ 9.807982] Freeing unused kernel memory: 1380k freed
[ 9.832417] udev[105]: starting version 167
[ 9.870058] [drm] Initialized drm 1.1.0 20060810
[ 9.895900] [drm] radeon defaulting to kernel modesetting.
[ 9.895960] [drm] radeon kernel modesetting enabled.
[ 9.896123] radeon 0000:05:00.0: PCI INT A -> GSI 30 (level, low) -> IRQ 30
[ 9.896185] radeon 0000:05:00.0: setting latency timer to 64
[ 9.896504] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68F9 0x1462:0x2340).
[ 9.896622] [drm] register mmio base: 0xFBDC0000
[ 9.896676] [drm] register mmio size: 131072
[ 9.896904] ATOM BIOS: 113
[ 9.897028] radeon 0000:05:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[ 9.897106] radeon 0000:05:00.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF
[ 9.897185] mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining
[ 9.897261] [drm] Detected VRAM RAM=1024M, BAR=256M
[ 9.897316] [drm] RAM width 64bits DDR
[ 9.897469] [TTM] Zone kernel: Available graphics memory: 4084572 kiB.
[ 9.897532] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
[ 9.897590] [TTM] Initializing pool allocator.
[ 9.897667] [drm] radeon: 1024M of VRAM memory ready
[ 9.897722] [drm] radeon: 512M of GTT memory ready.
[ 9.897786] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 9.897843] [drm] Driver supports precise vblank timestamp query.
[ 9.897937] radeon 0000:05:00.0: irq 64 for MSI/MSI-X
[ 9.897943] radeon 0000:05:00.0: radeon: using MSI.
[ 9.898030] [drm] radeon: irq initialized.
[ 9.898085] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 9.898870] [drm] Loading CEDAR Microcode
[ 9.908425] radeon 0000:05:00.0: WB enabled
[ 9.924241] input: KB Multimedia keyboard as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input2
[ 9.924845] generic-usb 0003:05D5:0624.0001: input,hidraw0: USB HID v1.10 Keyboard [KB Multimedia keyboard ] on usb-0000:00:1d.0-1/input0
[ 9.925384] [drm] ring test succeeded in 1 usecs
[ 9.925570] [drm] radeon: ib pool ready.
[ 9.925735] [drm] ib test succeeded in 0 usecs
[ 9.925793] failed to evaluate ATIF got AE_BAD_PARAMETER
[ 9.926035] [drm] Radeon Display Connectors
[ 9.926088] [drm] Connector 0:
[ 9.926138] [drm] HDMI-A
[ 9.926187] [drm] HPD1
[ 9.926236] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
[ 9.926310] [drm] Encoders:
[ 9.926360] [drm] DFP1: INTERNAL_UNIPHY1
[ 9.926412] [drm] Connector 1:
[ 9.926462] [drm] DVI-I
[ 9.926511] [drm] HPD4
[ 9.926560] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c
[ 9.926634] [drm] Encoders:
[ 9.926683] [drm] DFP2: INTERNAL_UNIPHY
[ 9.926736] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 9.926789] [drm] Connector 2:
[ 9.926838] [drm] VGA
[ 9.926887] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
[ 9.926961] [drm] Encoders:
[ 9.927011] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[ 9.936902] [drm] Radeon display connector HDMI-A-1: No monitor connected or invalid EDID
[ 9.940114] input: KB Multimedia keyboard as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.1/input/input3
[ 9.940709] generic-usb 0003:05D5:0624.0002: input,hidraw1: USB HID v1.10 Device [KB Multimedia keyboard ] on usb-0000:00:1d.0-1/input1
[ 9.940872] usbcore: registered new interface driver usbhid
[ 9.940928] usbhid: USB HID core driver
[ 9.990363] [drm] Radeon display connector DVI-I-1: Found valid EDID
[ 10.000249] [drm] Radeon display connector VGA-1: No monitor connected or invalid EDID
[ 10.000376] [drm] Internal thermal controller with fan control
[ 10.000513] [drm] radeon: power management initialized
[ 10.093884] [drm] fb mappable at 0xD0141000
[ 10.093939] [drm] vram apper at 0xD0000000
[ 10.093991] [drm] size 7299072
[ 10.094041] [drm] fb depth is 24
[ 10.094091] [drm] pitch is 6912
[ 10.094342] fbcon: radeondrmfb (fb0) is primary device
[ 10.568890] Console: switching to colour frame buffer device 210x65
[ 10.573256] fb0: radeondrmfb frame buffer device
[ 10.573281] drm: registered panic notifier
[ 10.573307] [drm] Initialized radeon 2.11.0 20080528 for 0000:05:00.0 on minor 0
[ 10.938590] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 12.614853] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 13.053415] udev[422]: starting version 167
[ 14.586081] cfg80211: Calling CRDA to update world regulatory domain
[ 14.598995] lp: driver loaded but no devices found
[ 14.618925] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 14.636003] ipmi message handler version 39.2
[ 14.686229] dca service started, version 1.12.1
[ 14.839090] ipmi device interface
[ 14.856677] IPMI System Interface driver.
[ 14.856743] ipmi_si: probing via SMBIOS
[ 14.856746] ipmi_si: SMBIOS: mem 0xca2 regsize 1 spacing 1 irq 0
[ 14.856748] ipmi_si: Adding SMBIOS-specified kcs state machine
[ 14.856751] ipmi_si: probing via SPMI
[ 14.856753] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
[ 14.856755] ipmi_si: Adding SPMI-specified kcs state machine
[ 14.856758] ipmi_si: Trying SMBIOS-specified kcs state machine at mem address 0xca2, slave address 0x0, irq 0
[ 14.856761] ipmi_si: Could not set up I/O space
[ 14.888623] ipmi_si: Trying SPMI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
[ 14.888632] ipmi_si: Interface detection failed
[ 14.942679] Linux video capture interface: v2.00
[ 14.972275] uvcvideo: Found UVC 1.00 device Vimicro USB Camera (Altair) (0ac8:3450)
[ 14.974523] input: Vimicro USB Camera (Altair) as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2:1.0/input/input4
[ 14.974721] usbcore: registered new interface driver uvcvideo
[ 14.974723] USB Video Class driver (1.1.1)
[ 14.997006] coretemp coretemp.0: TjMax is 97 C.
[ 14.997049] coretemp coretemp.0: TjMax is 97 C.
[ 14.997061] coretemp coretemp.0: TjMax is 97 C.
[ 14.997157] coretemp coretemp.0: TjMax is 97 C.
[ 14.997208] coretemp coretemp.4: TjMax is 97 C.
[ 14.997224] coretemp coretemp.4: TjMax is 97 C.
[ 14.997242] coretemp coretemp.4: TjMax is 97 C.
[ 14.997314] coretemp coretemp.4: TjMax is 97 C.
[ 15.197990] w83627ehf: Found W83667HG chip at 0x290
[ 15.290630] EDAC MC: Ver: 2.1.0
[ 15.306854] EDAC MC1: Giving out device to 'i7core_edac.c' 'i7 core #1': DEV 0000:fe:03.0
[ 15.306874] EDAC PCI0: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:fe:03.0' (POLLED)
[ 15.306911] EDAC MC0: Giving out device to 'i7core_edac.c' 'i7 core #0': DEV 0000:ff:03.0
[ 15.306919] EDAC PCI1: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:ff:03.0' (POLLED)
[ 15.306922] EDAC i7core: Driver loaded.
[ 15.457832] i2c i2c-8: Found w83795adg rev. B at 0x2f
[ 15.697275] w83795 8-002f: PECI agent 1 Tbase temperature: 85
[ 15.717287] w83795 8-002f: PECI agent 2 Tbase temperature: 85
[ 15.722664] cfg80211: World regulatory domain updated:
[ 15.722667] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 15.722671] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 15.722673] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 15.722676] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 15.722678] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 15.722681] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 15.840136] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5
[ 15.908177] type=1400 audit(1314417468.503:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=740 comm="apparmor_parser"
[ 15.908242] type=1400 audit(1314417468.503:3): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=740 comm="apparmor_parser"
[ 15.908298] type=1400 audit(1314417468.503:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=740 comm="apparmor_parser"
[ 16.015566] ioatdma: Intel(R) QuickData Technology Driver 4.00
[ 16.015641] ioatdma 0000:00:16.0: enabling device (0000 -> 0002)
[ 16.015662] ioatdma 0000:00:16.0: PCI INT A -> GSI 43 (level, low) -> IRQ 43
[ 16.015693] ioatdma 0000:00:16.0: setting latency timer to 64
[ 16.015733] ioatdma 0000:00:16.0: irq 65 for MSI/MSI-X
[ 16.016041] ioatdma 0000:00:16.1: enabling device (0000 -> 0002)
[ 16.016055] ioatdma 0000:00:16.1: PCI INT B -> GSI 44 (level, low) -> IRQ 44
[ 16.016079] ioatdma 0000:00:16.1: setting latency timer to 64
[ 16.016116] ioatdma 0000:00:16.1: irq 66 for MSI/MSI-X
[ 16.016368] ioatdma 0000:00:16.2: enabling device (0000 -> 0002)
[ 16.016381] ioatdma 0000:00:16.2: PCI INT C -> GSI 45 (level, low) -> IRQ 45
[ 16.016405] ioatdma 0000:00:16.2: setting latency timer to 64
[ 16.016443] ioatdma 0000:00:16.2: irq 67 for MSI/MSI-X
[ 16.016666] ioatdma 0000:00:16.3: enabling device (0000 -> 0002)
[ 16.016677] ioatdma 0000:00:16.3: PCI INT D -> GSI 46 (level, low) -> IRQ 46
[ 16.016698] ioatdma 0000:00:16.3: setting latency timer to 64
[ 16.016733] ioatdma 0000:00:16.3: irq 68 for MSI/MSI-X
[ 16.017035] ioatdma 0000:00:16.4: enabling device (0000 -> 0002)
[ 16.017041] ioatdma 0000:00:16.4: PCI INT A -> GSI 43 (level, low) -> IRQ 43
[ 16.017064] ioatdma 0000:00:16.4: setting latency timer to 64
[ 16.017101] ioatdma 0000:00:16.4: irq 69 for MSI/MSI-X
[ 16.017331] ioatdma 0000:00:16.5: enabling device (0000 -> 0002)
[ 16.017337] ioatdma 0000:00:16.5: PCI INT B -> GSI 44 (level, low) -> IRQ 44
[ 16.017360] ioatdma 0000:00:16.5: setting latency timer to 64
[ 16.017396] ioatdma 0000:00:16.5: irq 70 for MSI/MSI-X
[ 16.017615] ioatdma 0000:00:16.6: enabling device (0000 -> 0002)
[ 16.017620] ioatdma 0000:00:16.6: PCI INT C -> GSI 45 (level, low) -> IRQ 45
[ 16.017640] ioatdma 0000:00:16.6: setting latency timer to 64
[ 16.017676] ioatdma 0000:00:16.6: irq 71 for MSI/MSI-X
[ 16.017893] ioatdma 0000:00:16.7: enabling device (0000 -> 0002)
[ 16.017898] ioatdma 0000:00:16.7: PCI INT D -> GSI 46 (level, low) -> IRQ 46
[ 16.017918] ioatdma 0000:00:16.7: setting latency timer to 64
[ 16.017953] ioatdma 0000:00:16.7: irq 72 for MSI/MSI-X
[ 16.607092] snd_ca0106 0000:01:04.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 16.607111] snd-ca0106: Model 100a Rev 00000000 Serial 100a1102
[ 16.797439] ath9k 0000:08:00.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
[ 16.797450] ath9k 0000:08:00.0: setting latency timer to 64
[ 16.846395] ath: EEPROM regdomain: 0x809c
[ 16.846398] ath: EEPROM indicates we should expect a country code
[ 16.846400] ath: doing EEPROM country->regdmn map search
[ 16.846402] ath: country maps to regdmn code: 0x52
[ 16.846404] ath: Country alpha2 being used: CN
[ 16.846405] ath: Regpair used: 0x52
[ 16.846408] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846411] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846413] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846416] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846418] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846421] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846423] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846426] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846428] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846430] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846432] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846435] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846437] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846440] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846442] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846444] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846446] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846449] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846451] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846454] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846456] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 16.846458] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.846460] cfg80211: Disabling freq 2467 MHz as custom regd has no rule that fits a 20 MHz wide channel
[ 16.846463] cfg80211: Disabling freq 2472 MHz as custom regd has no rule that fits a 20 MHz wide channel
[ 16.846465] cfg80211: Disabling freq 2484 MHz as custom regd has no rule that fits a 20 MHz wide channel
[ 16.847993] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 16.847996] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.847998] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848001] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848003] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848005] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848007] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848010] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848012] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848015] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848017] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848020] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848022] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848024] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848026] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848029] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848031] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848034] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848036] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848039] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848041] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848044] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848046] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848049] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848051] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848053] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.848056] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
[ 16.848058] cfg80211: 2474000 KHz - 2494000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 16.895054] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[ 16.895747] cfg80211: Calling CRDA for country: CN
[ 16.895852] Registered led device: ath9k-phy0
[ 16.895857] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc90011920000, irq=28
[ 16.899180] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899185] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899187] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899190] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899192] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899195] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899197] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899200] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899202] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899204] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899206] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899209] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899211] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899214] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899216] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899219] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899221] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899223] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899225] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899228] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899230] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899233] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899235] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899237] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899239] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
[ 16.899242] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 16.899244] cfg80211: Disabling freq 2484 MHz
[ 16.899248] cfg80211: Regulatory domain changed to country: CN
[ 16.899250] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 16.899252] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 16.899255] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (N/A, 3000 mBm)
[ 17.097466] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 17.097529] snd_hda_intel 0000:00:1b.0: irq 73 for MSI/MSI-X
[ 17.097557] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
[ 17.174412] hda-intel: no codecs found!
[ 17.174502] snd_hda_intel 0000:00:1b.0: PCI INT A disabled
[ 17.174552] snd_hda_intel 0000:05:00.1: PCI INT B -> GSI 37 (level, low) -> IRQ 37
[ 17.175057] snd_hda_intel 0000:05:00.1: irq 73 for MSI/MSI-X
[ 17.175082] snd_hda_intel 0000:05:00.1: setting latency timer to 64
[ 17.266455] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0
[ 17.266879] input: HD-Audio Generic HDMI/DP as /devices/pci0000:00/0000:00:07.0/0000:05:00.1/sound/card1/input6
[ 17.609020] type=1400 audit(1314417470.203:5): apparmor="STATUS" operation="profile_load" name="/usr/share/gdm/guest-session/Xsession" pid=1034 comm="apparmor_parser"
[ 17.649067] type=1400 audit(1314417470.243:6): apparmor="STATUS" operation="profile_load" name="/usr/sbin/libvirtd" pid=1040 comm="apparmor_parser"
[ 17.657508] type=1400 audit(1314417470.253:7): apparmor="STATUS" operation="profile_load" name="/usr/sbin/tcpdump" pid=1041 comm="apparmor_parser"
[ 17.735883] type=1400 audit(1314417470.333:8): apparmor="STATUS" operation="profile_load" name="/usr/lib/libvirt/virt-aa-helper" pid=1038 comm="apparmor_parser"
[ 17.746941] type=1400 audit(1314417470.343:9): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=1035 comm="apparmor_parser"
[ 17.747012] type=1400 audit(1314417470.343:10): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1035 comm="apparmor_parser"
[ 17.747070] type=1400 audit(1314417470.343:11): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=1035 comm="apparmor_parser"
[ 18.521345] ppdev: user-space parallel port driver
[ 19.479583] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 20.479260] Adding 19529724k swap on /dev/mapper/cryptswap1. Priority:-1 extents:1 across:19529724k
[ 22.021061] wlan0: authenticate with 00:26:b8:18:ff:90 (try 1)
[ 22.023034] wlan0: authenticated
[ 22.023076] wlan0: associate with 00:26:b8:18:ff:90 (try 1)
[ 22.026161] wlan0: RX AssocResp from 00:26:b8:18:ff:90 (capab=0x431 status=0 aid=2)
[ 22.026167] wlan0: associated
[ 22.027068] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 22.193809] cfg80211: Calling CRDA for country: US
[ 22.197945] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197949] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197952] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197955] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197957] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197960] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197962] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197964] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197967] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197969] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197971] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197974] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197977] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197979] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197981] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197984] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197986] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197989] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197991] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197993] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.197996] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 22.197998] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 22.198000] cfg80211: Disabling freq 2467 MHz
[ 22.198002] cfg80211: Disabling freq 2472 MHz
[ 22.198003] cfg80211: Disabling freq 2484 MHz
[ 22.198008] cfg80211: Regulatory domain changed to country: US
[ 22.198009] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 22.198012] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 22.198014] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 22.198017] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 22.198019] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 22.198022] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 22.198024] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 23.392785] audit_printk_skb: 12 callbacks suppressed
[ 23.392788] type=1400 audit(1314417476.003:16): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince" pid=1036 comm="apparmor_parser"
[ 23.393979] type=1400 audit(1314417476.003:17): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince-previewer" pid=1036 comm="apparmor_parser"
[ 23.394356] type=1400 audit(1314417476.003:18): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince-thumbnailer" pid=1036 comm="apparmor_parser"
[ 25.894904] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
[ 27.103194] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
[-- Attachment #3: dmesg.built-in --]
[-- Type: application/octet-stream, Size: 81503 bytes --]
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.1.0-rc3-radeon (pivanof@PavelComp) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4) ) #10 SMP PREEMPT Fri Aug 26 23:43:38 EDT 2011
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-rc3-radeon root=UUID=a6d88530-6469-4ea2-91b9-410e088b4eff ro vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e5000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000bf780000 (usable)
[ 0.000000] BIOS-e820: 00000000bf78e000 - 00000000bf790000 (reserved)
[ 0.000000] BIOS-e820: 00000000bf790000 - 00000000bf79e000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
[ 0.000000] BIOS-e820: 00000000bf7ed000 - 00000000c0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000240000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI present.
[ 0.000000] DMI: System manufacturer System Product Name/Z8NA-D6(C), BIOS 1002 06/28/2010
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] last_pfn = 0x240000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-E3FFF write-protect
[ 0.000000] E4000-E7FFF write-through
[ 0.000000] E8000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask FE00000000 write-back
[ 0.000000] 1 base 0200000000 mask FFC0000000 write-back
[ 0.000000] 2 base 00C0000000 mask FFC0000000 uncachable
[ 0.000000] 3 base 00BF800000 mask FFFF800000 uncachable
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820 update range: 00000000bf800000 - 0000000100000000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0xbf780 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [ffff8800000ff780] ff780
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
[ 0.000000] init_memory_mapping: 0000000000000000-00000000bf780000
[ 0.000000] 0000000000 - 00bf600000 page 2M
[ 0.000000] 00bf600000 - 00bf780000 page 4k
[ 0.000000] kernel direct mapping tables up to bf780000 @ bf77b000-bf780000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000240000000
[ 0.000000] 0100000000 - 0240000000 page 2M
[ 0.000000] kernel direct mapping tables up to 240000000 @ 23fff6000-240000000
[ 0.000000] RAMDISK: 3497e000 - 364b7000
[ 0.000000] ACPI: RSDP 00000000000fb620 00024 (v02 ACPIAM)
[ 0.000000] ACPI: XSDT 00000000bf790100 00084 (v01 062810 XSDT1507 20100628 MSFT 00000097)
[ 0.000000] ACPI: FACP 00000000bf790290 000F4 (v03 062810 FACP1507 20100628 MSFT 00000097)
[ 0.000000] ACPI: DSDT 00000000bf790540 05B3D (v01 S0081 S0081002 00000002 INTL 20060113)
[ 0.000000] ACPI: FACS 00000000bf79e000 00040
[ 0.000000] ACPI: APIC 00000000bf790390 0011E (v01 062810 APIC1507 20100628 MSFT 00000097)
[ 0.000000] ACPI: MCFG 00000000bf7904b0 0003C (v01 062810 OEMMCFG 20100628 MSFT 00000097)
[ 0.000000] ACPI: SPMI 00000000bf7904f0 00041 (v05 062810 OEMSPMI 20100628 MSFT 00000097)
[ 0.000000] ACPI: OEMB 00000000bf79e040 00072 (v01 062810 OEMB1507 20100628 MSFT 00000097)
[ 0.000000] ACPI: SRAT 00000000bf798540 00128 (v01 062810 OEMSRAT 00000001 INTL 00000001)
[ 0.000000] ACPI: HPET 00000000bf798670 00038 (v01 062810 OEMHPET 20100628 MSFT 00000097)
[ 0.000000] ACPI: SSDT 00000000bf79fcb0 0154F (v01 DpgPmm CpuPm 00000012 INTL 20060113)
[ 0.000000] ACPI: EINJ 00000000bf7986b0 00130 (v01 AMIER AMI_EINJ 20100628 MSFT 00000097)
[ 0.000000] ACPI: BERT 00000000bf798840 00030 (v01 AMIER AMI_BERT 20100628 MSFT 00000097)
[ 0.000000] ACPI: ERST 00000000bf798870 001B0 (v01 AMIER AMI_ERST 20100628 MSFT 00000097)
[ 0.000000] ACPI: HEST 00000000bf798a20 000A8 (v01 AMIER ABC_HEST 20100628 MSFT 00000097)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
[ 0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
[ 0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 0x04 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 0x06 -> Node 0
[ 0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x14 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x16 -> Node 1
[ 0.000000] SRAT: Node 0 PXM 0 0-c0000000
[ 0.000000] SRAT: Node 0 PXM 0 100000000-140000000
[ 0.000000] SRAT: Node 1 PXM 1 140000000-240000000
[ 0.000000] NUMA: Node 0 [0,c0000000) + [100000000,140000000) -> [0,140000000)
[ 0.000000] Initmem setup node 0 0000000000000000-0000000140000000
[ 0.000000] NODE_DATA [000000013fffe000 - 000000013fffffff]
[ 0.000000] Initmem setup node 1 0000000140000000-0000000240000000
[ 0.000000] NODE_DATA [000000023fffe000 - 000000023fffffff]
[ 0.000000] [ffffea0000000000-ffffea0004ffffff] PMD -> [ffff88013be00000-ffff88013fdfffff] on node 0
[ 0.000000] [ffffea0005000000-ffffea0008ffffff] PMD -> [ffff88023b600000-ffff88023f5fffff] on node 1
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00240000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[4] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x000bf780
[ 0.000000] 0: 0x00100000 -> 0x00140000
[ 0.000000] 1: 0x00140000 -> 0x00240000
[ 0.000000] On node 0 totalpages: 1046287
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 5 pages reserved
[ 0.000000] DMA zone: 3914 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 16320 pages used for memmap
[ 0.000000] DMA32 zone: 763840 pages, LIFO batch:31
[ 0.000000] Normal zone: 4096 pages used for memmap
[ 0.000000] Normal zone: 258048 pages, LIFO batch:31
[ 0.000000] On node 1 totalpages: 1048576
[ 0.000000] Normal zone: 16384 pages used for memmap
[ 0.000000] Normal zone: 1032192 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x10] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x12] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x14] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x16] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x8c] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x8d] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x8e] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x8f] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x90] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x91] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x92] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x93] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x94] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x95] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x96] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x97] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: IOAPIC (id[0x03] address[0xfec8a000] gsi_base[24])
[ 0.000000] IOAPIC[1]: apic_id 3, version 32, address 0xfec8a000, GSI 24-47
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000
[ 0.000000] 24 Processors exceeds NR_CPUS limit of 16
[ 0.000000] SMP: Allowing 16 CPUs, 8 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 64
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e5000
[ 0.000000] PM: Registered nosave memory: 00000000000e5000 - 0000000000100000
[ 0.000000] PM: Registered nosave memory: 00000000bf780000 - 00000000bf78e000
[ 0.000000] PM: Registered nosave memory: 00000000bf78e000 - 00000000bf790000
[ 0.000000] PM: Registered nosave memory: 00000000bf790000 - 00000000bf79e000
[ 0.000000] PM: Registered nosave memory: 00000000bf79e000 - 00000000bf7d0000
[ 0.000000] PM: Registered nosave memory: 00000000bf7d0000 - 00000000bf7e0000
[ 0.000000] PM: Registered nosave memory: 00000000bf7e0000 - 00000000bf7ed000
[ 0.000000] PM: Registered nosave memory: 00000000bf7ed000 - 00000000c0000000
[ 0.000000] PM: Registered nosave memory: 00000000c0000000 - 00000000e0000000
[ 0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000
[ 0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fee00000
[ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000
[ 0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ffe00000
[ 0.000000] PM: Registered nosave memory: 00000000ffe00000 - 0000000100000000
[ 0.000000] Allocating PCI resources starting at c0000000 (gap: c0000000:20000000)
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:16 nr_node_ids:2
[ 0.000000] PERCPU: Embedded 27 pages/cpu @ffff88013bc00000 s81664 r8192 d20736 u262144
[ 0.000000] pcpu-alloc: s81664 r8192 d20736 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 00 01 02 03 08 10 12 14 [1] 04 05 06 07 09 11 13 15
[ 0.000000] Built 2 zonelists in Node order, mobility grouping on. Total pages: 2057994
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-rc3-radeon root=UUID=a6d88530-6469-4ea2-91b9-410e088b4eff ro vt.handoff=7
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 8137152k/9437184k available (7212k kernel code, 1057732k absent, 242300k reserved, 5897k data, 840k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:4352 nr_irqs:1216 16
[ 0.000000] Extended CMOS year: 2000
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 67108864 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] hpet clockevent registered
[ 0.000000] Fast TSC calibration using PIT
[ 0.010000] Detected 2132.987 MHz processor.
[ 0.000006] Calibrating delay loop (skipped), value calculated using timer frequency.. 4265.97 BogoMIPS (lpj=21329870)
[ 0.000121] pid_max: default: 32768 minimum: 301
[ 0.000227] Security Framework initialized
[ 0.000293] AppArmor: AppArmor initialized
[ 0.001188] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.003723] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.004744] Mount-cache hash table entries: 256
[ 0.005001] Initializing cgroup subsys cpuacct
[ 0.005060] Initializing cgroup subsys memory
[ 0.005138] Initializing cgroup subsys devices
[ 0.005193] Initializing cgroup subsys freezer
[ 0.005247] Initializing cgroup subsys net_cls
[ 0.005301] Initializing cgroup subsys blkio
[ 0.005398] CPU: Physical Processor ID: 0
[ 0.005451] CPU: Processor Core ID: 0
[ 0.005507] mce: CPU supports 9 MCE banks
[ 0.005571] CPU0: Thermal monitoring enabled (TM1)
[ 0.005633] using mwait in idle threads.
[ 0.006837] ACPI: Core revision 20110623
[ 0.033927] ftrace: allocating 25628 entries in 101 pages
[ 0.044364] Switched APIC routing to physical flat.
[ 0.044881] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.144932] CPU0: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz stepping 05
[ 0.268712] APIC calibration not consistent with PM-Timer: 109ms instead of 100ms
[ 0.268787] APIC delta adjusted to PM-Timer: 833361 (916692)
[ 0.268846] Performance Events: PEBS fmt1+, erratum AAJ80 worked around, Nehalem events, Intel PMU driver.
[ 0.269042] ... version: 3
[ 0.269094] ... bit width: 48
[ 0.269146] ... generic registers: 4
[ 0.269198] ... value mask: 0000ffffffffffff
[ 0.269891] ... max period: 000000007fffffff
[ 0.269946] ... fixed-purpose events: 3
[ 0.269998] ... event mask: 000000070000000f
[ 0.329596] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.408865] Booting Node 0, Processors #1
[ 0.408933] smpboot cpu 1: start_ip = 9a000
[ 0.589024] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.648888] #2
[ 0.648921] smpboot cpu 2: start_ip = 9a000
[ 0.828968] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.888886] #3
[ 0.888919] smpboot cpu 3: start_ip = 9a000
[ 1.069018] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.128908] Ok.
[ 1.128959] Booting Node 1, Processors #4
[ 1.129031] smpboot cpu 4: start_ip = 9a000
[ 1.308958] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.368908] #5
[ 1.368943] smpboot cpu 5: start_ip = 9a000
[ 1.549010] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.608912] #6
[ 1.608947] smpboot cpu 6: start_ip = 9a000
[ 1.788968] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.848918] #7
[ 1.848953] smpboot cpu 7: start_ip = 9a000
[ 2.029015] NMI watchdog enabled, takes one hw-pmu counter.
[ 2.048908] Brought up 8 CPUs
[ 2.048962] Total of 8 processors activated (34064.55 BogoMIPS).
[ 2.052998] devtmpfs: initialized
[ 2.053242] PM: Registering ACPI NVS region at bf79e000 (204800 bytes)
[ 2.054189] print_constraints: dummy:
[ 2.054271] RTC time: 3:54:32, date: 08/27/11
[ 2.054367] NET: Registered protocol family 16
[ 2.054520] ACPI: bus type pci registered
[ 2.054630] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 2.054710] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
[ 2.095305] PCI: Using configuration type 1 for base access
[ 2.096419] bio: create slab <bio-0> at 0
[ 2.096572] ACPI: Added _OSI(Module Device)
[ 2.096626] ACPI: Added _OSI(Processor Device)
[ 2.096679] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 2.096733] ACPI: Added _OSI(Processor Aggregator Device)
[ 2.098446] ACPI: EC: Look up EC in DSDT
[ 2.098726] \_SB_:_OSC evaluation returned wrong type
[ 2.098728] _OSC request data:1 16
[ 2.100252] ACPI: Executed 1 blocks of module-level executable AML code
[ 2.103384] ACPI: SSDT 00000000bf79e0c0 011A4 (v01 DpgPmm P001Ist 00000011 INTL 20060113)
[ 2.104023] ACPI: Dynamic OEM Table Load:
[ 2.104132] ACPI: SSDT (null) 011A4 (v01 DpgPmm P001Ist 00000011 INTL 20060113)
[ 2.104362] ACPI: SSDT 00000000bf79f270 00678 (v01 PmRef P001Cst 00003001 INTL 20060113)
[ 2.104939] ACPI: Dynamic OEM Table Load:
[ 2.105047] ACPI: SSDT (null) 00678 (v01 PmRef P001Cst 00003001 INTL 20060113)
[ 2.105255] ACPI: SSDT 00000000bf79f8f0 003BA (v01 PmRef Cpu0Tst 00003000 INTL 20060113)
[ 2.105850] ACPI: Dynamic OEM Table Load:
[ 2.105959] ACPI: SSDT (null) 003BA (v01 PmRef Cpu0Tst 00003000 INTL 20060113)
[ 2.106644] ACPI: Interpreter enabled
[ 2.106698] ACPI: (supports S0 S1 S4 S5)
[ 2.106876] ACPI: Using IOAPIC for interrupt routing
[ 2.114157] ACPI: No dock devices found.
[ 2.114235] HEST: Table parsing has been initialized.
[ 2.114291] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 2.114453] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 2.114666] pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
[ 2.114725] pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
[ 2.114783] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
[ 2.114858] pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000dffff]
[ 2.114933] pci_root PNP0A08:00: host bridge window [mem 0xc0000000-0xdfffffff]
[ 2.115007] pci_root PNP0A08:00: host bridge window [mem 0xf0000000-0xfed8ffff]
[ 2.115097] pci 0000:00:00.0: [8086:3403] type 0 class 0x000600
[ 2.115147] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 2.115151] pci 0000:00:00.0: PME# disabled
[ 2.115179] pci 0000:00:01.0: [8086:3408] type 1 class 0x000604
[ 2.115229] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 2.115233] pci 0000:00:01.0: PME# disabled
[ 2.115256] pci 0000:00:02.0: [8086:3409] type 1 class 0x000604
[ 2.115305] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
[ 2.115309] pci 0000:00:02.0: PME# disabled
[ 2.115332] pci 0000:00:03.0: [8086:340a] type 1 class 0x000604
[ 2.115381] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 2.115385] pci 0000:00:03.0: PME# disabled
[ 2.115410] pci 0000:00:07.0: [8086:340e] type 1 class 0x000604
[ 2.115459] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[ 2.115462] pci 0000:00:07.0: PME# disabled
[ 2.115486] pci 0000:00:08.0: [8086:340f] type 1 class 0x000604
[ 2.115535] pci 0000:00:08.0: PME# supported from D0 D3hot D3cold
[ 2.115539] pci 0000:00:08.0: PME# disabled
[ 2.115561] pci 0000:00:09.0: [8086:3410] type 1 class 0x000604
[ 2.115611] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
[ 2.115614] pci 0000:00:09.0: PME# disabled
[ 2.115637] pci 0000:00:0a.0: [8086:3411] type 1 class 0x000604
[ 2.115686] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
[ 2.115690] pci 0000:00:0a.0: PME# disabled
[ 2.115712] pci 0000:00:10.0: [8086:3425] type 0 class 0x000800
[ 2.115781] pci 0000:00:10.1: [8086:3426] type 0 class 0x000800
[ 2.115844] pci 0000:00:11.0: [8086:3427] type 0 class 0x000800
[ 2.115910] pci 0000:00:11.1: [8086:3428] type 0 class 0x000800
[ 2.115975] pci 0000:00:14.0: [8086:342e] type 0 class 0x000800
[ 2.116043] pci 0000:00:14.1: [8086:3422] type 0 class 0x000800
[ 2.116110] pci 0000:00:14.2: [8086:3423] type 0 class 0x000800
[ 2.116174] pci 0000:00:14.3: [8086:3438] type 0 class 0x000800
[ 2.116237] pci 0000:00:16.0: [8086:3430] type 0 class 0x000880
[ 2.116251] pci 0000:00:16.0: reg 10: [mem 0xfbcd8000-0xfbcdbfff 64bit]
[ 2.116320] pci 0000:00:16.1: [8086:3431] type 0 class 0x000880
[ 2.116334] pci 0000:00:16.1: reg 10: [mem 0xfbcdc000-0xfbcdffff 64bit]
[ 2.116402] pci 0000:00:16.2: [8086:3432] type 0 class 0x000880
[ 2.116415] pci 0000:00:16.2: reg 10: [mem 0xfbce0000-0xfbce3fff 64bit]
[ 2.116482] pci 0000:00:16.3: [8086:3433] type 0 class 0x000880
[ 2.116496] pci 0000:00:16.3: reg 10: [mem 0xfbce4000-0xfbce7fff 64bit]
[ 2.116563] pci 0000:00:16.4: [8086:3429] type 0 class 0x000880
[ 2.116576] pci 0000:00:16.4: reg 10: [mem 0xfbce8000-0xfbcebfff 64bit]
[ 2.116643] pci 0000:00:16.5: [8086:342a] type 0 class 0x000880
[ 2.116657] pci 0000:00:16.5: reg 10: [mem 0xfbcec000-0xfbceffff 64bit]
[ 2.116724] pci 0000:00:16.6: [8086:342b] type 0 class 0x000880
[ 2.116737] pci 0000:00:16.6: reg 10: [mem 0xfbcf0000-0xfbcf3fff 64bit]
[ 2.116804] pci 0000:00:16.7: [8086:342c] type 0 class 0x000880
[ 2.116818] pci 0000:00:16.7: reg 10: [mem 0xfbcf4000-0xfbcf7fff 64bit]
[ 2.116887] pci 0000:00:1a.0: [8086:3a37] type 0 class 0x000c03
[ 2.116933] pci 0000:00:1a.0: reg 20: [io 0xa400-0xa41f]
[ 2.116980] pci 0000:00:1a.1: [8086:3a38] type 0 class 0x000c03
[ 2.117024] pci 0000:00:1a.1: reg 20: [io 0xa480-0xa49f]
[ 2.117081] pci 0000:00:1a.7: [8086:3a3c] type 0 class 0x000c03
[ 2.117103] pci 0000:00:1a.7: reg 10: [mem 0xfbcfd000-0xfbcfd3ff]
[ 2.117179] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[ 2.117183] pci 0000:00:1a.7: PME# disabled
[ 2.117208] pci 0000:00:1b.0: [8086:3a3e] type 0 class 0x000403
[ 2.117224] pci 0000:00:1b.0: reg 10: [mem 0xfbcf8000-0xfbcfbfff 64bit]
[ 2.117280] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 2.117284] pci 0000:00:1b.0: PME# disabled
[ 2.117306] pci 0000:00:1d.0: [8086:3a34] type 0 class 0x000c03
[ 2.117351] pci 0000:00:1d.0: reg 20: [io 0xa800-0xa81f]
[ 2.117396] pci 0000:00:1d.1: [8086:3a35] type 0 class 0x000c03
[ 2.117440] pci 0000:00:1d.1: reg 20: [io 0xa880-0xa89f]
[ 2.117486] pci 0000:00:1d.2: [8086:3a36] type 0 class 0x000c03
[ 2.117530] pci 0000:00:1d.2: reg 20: [io 0xac00-0xac1f]
[ 2.117576] pci 0000:00:1d.3: [8086:3a39] type 0 class 0x000c03
[ 2.117620] pci 0000:00:1d.3: reg 20: [io 0xb000-0xb01f]
[ 2.117674] pci 0000:00:1d.7: [8086:3a3a] type 0 class 0x000c03
[ 2.117696] pci 0000:00:1d.7: reg 10: [mem 0xfbcfe000-0xfbcfe3ff]
[ 2.117772] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 2.117776] pci 0000:00:1d.7: PME# disabled
[ 2.117798] pci 0000:00:1e.0: [8086:244e] type 1 class 0x000604
[ 2.117857] pci 0000:00:1f.0: [8086:3a16] type 0 class 0x000601
[ 2.117942] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0ca0 (mask 0003)
[ 2.118020] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0294 (mask 0003)
[ 2.118129] pci 0000:00:1f.2: [8086:3a20] type 0 class 0x000101
[ 2.118146] pci 0000:00:1f.2: reg 10: [io 0xbc00-0xbc07]
[ 2.118154] pci 0000:00:1f.2: reg 14: [io 0xb880-0xb883]
[ 2.118163] pci 0000:00:1f.2: reg 18: [io 0xb800-0xb807]
[ 2.118171] pci 0000:00:1f.2: reg 1c: [io 0xb480-0xb483]
[ 2.118179] pci 0000:00:1f.2: reg 20: [io 0xb400-0xb40f]
[ 2.118188] pci 0000:00:1f.2: reg 24: [io 0xb080-0xb08f]
[ 2.118226] pci 0000:00:1f.3: [8086:3a30] type 0 class 0x000c05
[ 2.118242] pci 0000:00:1f.3: reg 10: [mem 0xfbcff000-0xfbcff0ff 64bit]
[ 2.118265] pci 0000:00:1f.3: reg 20: [io 0x0400-0x041f]
[ 2.118298] pci 0000:00:1f.5: [8086:3a26] type 0 class 0x000101
[ 2.118314] pci 0000:00:1f.5: reg 10: [io 0xcc00-0xcc07]
[ 2.118323] pci 0000:00:1f.5: reg 14: [io 0xc880-0xc883]
[ 2.118331] pci 0000:00:1f.5: reg 18: [io 0xc800-0xc807]
[ 2.118340] pci 0000:00:1f.5: reg 1c: [io 0xc480-0xc483]
[ 2.118348] pci 0000:00:1f.5: reg 20: [io 0xc400-0xc40f]
[ 2.118357] pci 0000:00:1f.5: reg 24: [io 0xc080-0xc08f]
[ 2.118444] pci 0000:08:00.0: [168c:002b] type 0 class 0x000280
[ 2.118462] pci 0000:08:00.0: reg 10: [mem 0xfbef0000-0xfbefffff 64bit]
[ 2.118530] pci 0000:08:00.0: supports D1
[ 2.118532] pci 0000:08:00.0: PME# supported from D0 D1 D3hot
[ 2.118536] pci 0000:08:00.0: PME# disabled
[ 2.128928] pci 0000:00:01.0: PCI bridge to [bus 08-08]
[ 2.128991] pci 0000:00:01.0: bridge window [mem 0xfbe00000-0xfbefffff]
[ 2.129040] pci 0000:00:02.0: PCI bridge to [bus 07-07]
[ 2.129138] pci 0000:00:03.0: PCI bridge to [bus 06-06]
[ 2.129247] pci 0000:05:00.0: [1002:68f9] type 0 class 0x000300
[ 2.129261] pci 0000:05:00.0: reg 10: [mem 0xd0000000-0xdfffffff 64bit pref]
[ 2.129273] pci 0000:05:00.0: reg 18: [mem 0xfbdc0000-0xfbddffff 64bit]
[ 2.129281] pci 0000:05:00.0: reg 20: [io 0xe000-0xe0ff]
[ 2.129296] pci 0000:05:00.0: reg 30: [mem 0xfbda0000-0xfbdbffff pref]
[ 2.129315] pci 0000:05:00.0: supports D1 D2
[ 2.129338] pci 0000:05:00.1: [1002:aa68] type 0 class 0x000403
[ 2.129352] pci 0000:05:00.1: reg 10: [mem 0xfbdfc000-0xfbdfffff 64bit]
[ 2.129401] pci 0000:05:00.1: supports D1 D2
[ 2.148929] pci 0000:00:07.0: PCI bridge to [bus 05-05]
[ 2.148989] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 2.148994] pci 0000:00:07.0: bridge window [mem 0xfbd00000-0xfbdfffff]
[ 2.149001] pci 0000:00:07.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 2.149050] pci 0000:00:08.0: PCI bridge to [bus 04-04]
[ 2.149149] pci 0000:00:09.0: PCI bridge to [bus 03-03]
[ 2.149247] pci 0000:00:0a.0: PCI bridge to [bus 02-02]
[ 2.149346] pci 0000:01:04.0: [1102:0007] type 0 class 0x000401
[ 2.149364] pci 0000:01:04.0: reg 10: [io 0xdc00-0xdc1f]
[ 2.149432] pci 0000:01:04.0: supports D1 D2
[ 2.149473] pci 0000:00:1e.0: PCI bridge to [bus 01-01] (subtractive decode)
[ 2.149534] pci 0000:00:1e.0: bridge window [io 0xd000-0xdfff]
[ 2.149542] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
[ 2.149544] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 2.149547] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 2.149549] pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
[ 2.149552] pci 0000:00:1e.0: bridge window [mem 0xc0000000-0xdfffffff] (subtractive decode)
[ 2.149554] pci 0000:00:1e.0: bridge window [mem 0xf0000000-0xfed8ffff] (subtractive decode)
[ 2.149587] pci 0000:00:01.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.149650] pci 0000:00:01.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.149708] pci 0000:08:00.0: Dev MPS 128 MPSS 128 MRRS 512
[ 2.149764] pci 0000:08:00.0: MPS configured higher than maximum supported by the device. If a bus issue occurs, try running with pci=pcie_bus_safe.
[ 2.149865] pci 0000:08:00.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.149922] pci 0000:00:02.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.149984] pci 0000:00:02.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.150042] pci 0000:00:03.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.150104] pci 0000:00:03.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.150161] pci 0000:00:07.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.150222] pci 0000:00:07.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.150280] pci 0000:05:00.0: Dev MPS 256 MPSS 256 MRRS 512
[ 2.150344] pci 0000:05:00.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.150402] pci 0000:05:00.1: Dev MPS 256 MPSS 256 MRRS 512
[ 2.150466] pci 0000:05:00.1: Dev MPS 256 MPSS 256 MRRS 128
[ 2.150523] pci 0000:00:08.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.150585] pci 0000:00:08.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.150643] pci 0000:00:09.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.150705] pci 0000:00:09.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.150762] pci 0000:00:0a.0: Dev MPS 128 MPSS 256 MRRS 128
[ 2.150824] pci 0000:00:0a.0: Dev MPS 256 MPSS 256 MRRS 128
[ 2.150882] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 2.151086] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 2.151177] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE1._PRT]
[ 2.151203] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE2._PRT]
[ 2.151229] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE3._PRT]
[ 2.151261] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE7._PRT]
[ 2.151290] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE8._PRT]
[ 2.151316] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE9._PRT]
[ 2.151341] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPEA._PRT]
[ 2.151365] pci0000:00: Requesting ACPI _OSC control (0x1d)
[ 2.151423] pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
[ 2.151499] ACPI _OSC control for PCIe not granted, disabling ASPM
[ 2.169055] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12 14 15)
[ 2.169460] ACPI: PCI Interrupt Link [LNKB] (IRQs *5)
[ 2.169636] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 *7 10 11 12 14 15)
[ 2.170038] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 *10 11 12 14 15)
[ 2.170440] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
[ 2.170915] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12 14 *15)
[ 2.171317] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 6 7 10 11 12 *14 15)
[ 2.171718] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 10 *11 12 14 15)
[ 2.172210] vgaarb: device added: PCI:0000:05:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 2.172288] vgaarb: loaded
[ 2.172338] vgaarb: bridge control possible 0000:05:00.0
[ 2.172549] SCSI subsystem initialized
[ 2.172644] libata version 3.00 loaded.
[ 2.172687] usbcore: registered new interface driver usbfs
[ 2.172751] usbcore: registered new interface driver hub
[ 2.172833] usbcore: registered new device driver usb
[ 2.173001] wmi: Mapper loaded
[ 2.173052] PCI: Using ACPI for IRQ routing
[ 2.179512] PCI: Discovered peer bus fe
[ 2.179588] pci 0000:fe:00.0: [8086:2c40] type 0 class 0x000600
[ 2.179613] pci 0000:fe:00.1: [8086:2c01] type 0 class 0x000600
[ 2.179641] pci 0000:fe:02.0: [8086:2c10] type 0 class 0x000600
[ 2.179664] pci 0000:fe:02.1: [8086:2c11] type 0 class 0x000600
[ 2.179688] pci 0000:fe:02.4: [8086:2c14] type 0 class 0x000600
[ 2.179714] pci 0000:fe:02.5: [8086:2c15] type 0 class 0x000600
[ 2.179739] pci 0000:fe:03.0: [8086:2c18] type 0 class 0x000600
[ 2.179762] pci 0000:fe:03.1: [8086:2c19] type 0 class 0x000600
[ 2.179785] pci 0000:fe:03.2: [8086:2c1a] type 0 class 0x000600
[ 2.179809] pci 0000:fe:03.4: [8086:2c1c] type 0 class 0x000600
[ 2.179834] pci 0000:fe:04.0: [8086:2c20] type 0 class 0x000600
[ 2.179857] pci 0000:fe:04.1: [8086:2c21] type 0 class 0x000600
[ 2.179880] pci 0000:fe:04.2: [8086:2c22] type 0 class 0x000600
[ 2.179906] pci 0000:fe:04.3: [8086:2c23] type 0 class 0x000600
[ 2.179931] pci 0000:fe:05.0: [8086:2c28] type 0 class 0x000600
[ 2.179955] pci 0000:fe:05.1: [8086:2c29] type 0 class 0x000600
[ 2.179978] pci 0000:fe:05.2: [8086:2c2a] type 0 class 0x000600
[ 2.180001] pci 0000:fe:05.3: [8086:2c2b] type 0 class 0x000600
[ 2.180027] pci 0000:fe:06.0: [8086:2c30] type 0 class 0x000600
[ 2.180050] pci 0000:fe:06.1: [8086:2c31] type 0 class 0x000600
[ 2.180073] pci 0000:fe:06.2: [8086:2c32] type 0 class 0x000600
[ 2.180098] pci 0000:fe:06.3: [8086:2c33] type 0 class 0x000600
[ 2.180560] PCI: Discovered peer bus ff
[ 2.180636] pci 0000:ff:00.0: [8086:2c40] type 0 class 0x000600
[ 2.180657] pci 0000:ff:00.1: [8086:2c01] type 0 class 0x000600
[ 2.180681] pci 0000:ff:02.0: [8086:2c10] type 0 class 0x000600
[ 2.180701] pci 0000:ff:02.1: [8086:2c11] type 0 class 0x000600
[ 2.180723] pci 0000:ff:02.4: [8086:2c14] type 0 class 0x000600
[ 2.180743] pci 0000:ff:02.5: [8086:2c15] type 0 class 0x000600
[ 2.180765] pci 0000:ff:03.0: [8086:2c18] type 0 class 0x000600
[ 2.180787] pci 0000:ff:03.1: [8086:2c19] type 0 class 0x000600
[ 2.180807] pci 0000:ff:03.2: [8086:2c1a] type 0 class 0x000600
[ 2.180828] pci 0000:ff:03.4: [8086:2c1c] type 0 class 0x000600
[ 2.180850] pci 0000:ff:04.0: [8086:2c20] type 0 class 0x000600
[ 2.180871] pci 0000:ff:04.1: [8086:2c21] type 0 class 0x000600
[ 2.180891] pci 0000:ff:04.2: [8086:2c22] type 0 class 0x000600
[ 2.180911] pci 0000:ff:04.3: [8086:2c23] type 0 class 0x000600
[ 2.180934] pci 0000:ff:05.0: [8086:2c28] type 0 class 0x000600
[ 2.180956] pci 0000:ff:05.1: [8086:2c29] type 0 class 0x000600
[ 2.180977] pci 0000:ff:05.2: [8086:2c2a] type 0 class 0x000600
[ 2.180997] pci 0000:ff:05.3: [8086:2c2b] type 0 class 0x000600
[ 2.181020] pci 0000:ff:06.0: [8086:2c30] type 0 class 0x000600
[ 2.181040] pci 0000:ff:06.1: [8086:2c31] type 0 class 0x000600
[ 2.181060] pci 0000:ff:06.2: [8086:2c32] type 0 class 0x000600
[ 2.181081] pci 0000:ff:06.3: [8086:2c33] type 0 class 0x000600
[ 2.181558] PCI: pci_cache_line_size set to 64 bytes
[ 2.181771] reserve RAM buffer: 000000000009fc00 - 000000000009ffff
[ 2.181774] reserve RAM buffer: 00000000bf780000 - 00000000bfffffff
[ 2.181864] NetLabel: Initializing
[ 2.181916] NetLabel: domain hash size = 128
[ 2.181969] NetLabel: protocols = UNLABELED CIPSOv4
[ 2.182034] NetLabel: unlabeled traffic allowed by default
[ 2.182136] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
[ 2.182198] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 2.182393] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 2.269111] Switching to clocksource hpet
[ 2.278221] AppArmor: AppArmor Filesystem Enabled
[ 2.278304] pnp: PnP ACPI init
[ 2.278366] ACPI: bus type pnp registered
[ 2.278543] pnp 00:00: [bus 00-ff]
[ 2.278551] pnp 00:00: [io 0x0cf8-0x0cff]
[ 2.278554] pnp 00:00: [io 0x0000-0x0cf7 window]
[ 2.278556] pnp 00:00: [io 0x0d00-0xffff window]
[ 2.278558] pnp 00:00: [mem 0x000a0000-0x000bffff window]
[ 2.278560] pnp 00:00: [mem 0x000d0000-0x000dffff window]
[ 2.278562] pnp 00:00: [mem 0xc0000000-0xdfffffff window]
[ 2.278564] pnp 00:00: [mem 0xf0000000-0xfed8ffff window]
[ 2.278645] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
[ 2.278655] pnp 00:01: [mem 0xfbf00000-0xfbffffff]
[ 2.278657] pnp 00:01: [mem 0xfc000000-0xfcffffff]
[ 2.278659] pnp 00:01: [mem 0xfd000000-0xfdffffff]
[ 2.278661] pnp 00:01: [mem 0xfe000000-0xfebfffff]
[ 2.278663] pnp 00:01: [mem 0xfec8a000-0xfec8afff]
[ 2.278665] pnp 00:01: [mem 0xfed10000-0xfed10fff]
[ 2.278775] system 00:01: [mem 0xfbf00000-0xfbffffff] has been reserved
[ 2.278834] system 00:01: [mem 0xfc000000-0xfcffffff] has been reserved
[ 2.278893] system 00:01: [mem 0xfd000000-0xfdffffff] has been reserved
[ 2.278971] Switched to NOHz mode on CPU #0
[ 2.279025] Switched to NOHz mode on CPU #4
[ 2.279029] Switched to NOHz mode on CPU #6
[ 2.279034] system 00:01: [mem 0xfe000000-0xfebfffff] has been reserved
[ 2.279037] system 00:01: [mem 0xfec8a000-0xfec8afff] could not be reserved
[ 2.279039] system 00:01: [mem 0xfed10000-0xfed10fff] has been reserved
[ 2.279042] Switched to NOHz mode on CPU #2
[ 2.279045] system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 2.279071] Switched to NOHz mode on CPU #7
[ 2.279074] Switched to NOHz mode on CPU #5
[ 2.279081] pnp 00:02: [dma 4]
[ 2.279083] pnp 00:02: [io 0x0000-0x000f]
[ 2.279085] pnp 00:02: [io 0x0081-0x0083]
[ 2.279087] Switched to NOHz mode on CPU #3
[ 2.279090] pnp 00:02: [io 0x0087]
[ 2.279092] Switched to NOHz mode on CPU #1
[ 2.279095] pnp 00:02: [io 0x0089-0x008b]
[ 2.279096] pnp 00:02: [io 0x008f]
[ 2.279098] pnp 00:02: [io 0x00c0-0x00df]
[ 2.279127] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
[ 2.279138] pnp 00:03: [io 0x0070-0x0071]
[ 2.279147] pnp 00:03: [irq 8]
[ 2.279181] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 2.279201] pnp 00:04: [io 0x0061]
[ 2.279229] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
[ 2.279237] pnp 00:05: [io 0x00f0-0x00ff]
[ 2.279243] pnp 00:05: [irq 13]
[ 2.279270] pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 2.279436] pnp 00:06: [io 0x0000-0xffffffffffffffff disabled]
[ 2.279439] pnp 00:06: [io 0x0000-0xffffffffffffffff disabled]
[ 2.279441] pnp 00:06: [io 0x0290-0x029f]
[ 2.279524] system 00:06: [io 0x0290-0x029f] has been reserved
[ 2.279528] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.279631] pnp 00:07: [io 0x0010-0x001f]
[ 2.279634] pnp 00:07: [io 0x0022-0x003f]
[ 2.279636] pnp 00:07: [io 0x0044-0x005f]
[ 2.279638] pnp 00:07: [io 0x0062-0x0063]
[ 2.279640] pnp 00:07: [io 0x0065-0x006f]
[ 2.279641] pnp 00:07: [io 0x0072-0x007f]
[ 2.279643] pnp 00:07: [io 0x0080]
[ 2.279645] pnp 00:07: [io 0x0084-0x0086]
[ 2.279647] pnp 00:07: [io 0x0088]
[ 2.279648] pnp 00:07: [io 0x008c-0x008e]
[ 2.279650] pnp 00:07: [io 0x0090-0x009f]
[ 2.279652] pnp 00:07: [io 0x00a2-0x00bf]
[ 2.279654] pnp 00:07: [io 0x00e0-0x00ef]
[ 2.279656] pnp 00:07: [io 0x04d0-0x04d1]
[ 2.279663] pnp 00:07: [io 0x0ca0-0x0caf]
[ 2.279664] pnp 00:07: [io 0x0800-0x087f]
[ 2.279666] pnp 00:07: [io 0x0000-0xffffffffffffffff disabled]
[ 2.279669] pnp 00:07: [io 0x0500-0x057f]
[ 2.279671] pnp 00:07: [mem 0xfed1c000-0xfed1ffff]
[ 2.279673] pnp 00:07: [mem 0xfed20000-0xfed3ffff]
[ 2.279674] pnp 00:07: [mem 0xfed40000-0xfed8ffff]
[ 2.279780] system 00:07: [io 0x04d0-0x04d1] has been reserved
[ 2.279838] system 00:07: [io 0x0ca0-0x0caf] has been reserved
[ 2.279895] system 00:07: [io 0x0800-0x087f] has been reserved
[ 2.279952] system 00:07: [io 0x0500-0x057f] has been reserved
[ 2.280010] system 00:07: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 2.280068] system 00:07: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 2.280127] system 00:07: [mem 0xfed40000-0xfed8ffff] has been reserved
[ 2.280186] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.280240] pnp 00:08: [mem 0xfed00000-0xfed003ff]
[ 2.280272] pnp 00:08: Plug and Play ACPI device, IDs PNP0103 (active)
[ 2.280479] pnp 00:09: [io 0x03f8-0x03ff]
[ 2.280486] pnp 00:09: [irq 4]
[ 2.280488] pnp 00:09: [dma 0 disabled]
[ 2.280561] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
[ 2.280779] pnp 00:0a: [io 0x02f8-0x02ff]
[ 2.280786] pnp 00:0a: [irq 3]
[ 2.280788] pnp 00:0a: [dma 0 disabled]
[ 2.280889] pnp 00:0a: Plug and Play ACPI device, IDs PNP0501 (active)
[ 2.280961] pnp 00:0b: [mem 0xfec00000-0xfec00fff]
[ 2.280963] pnp 00:0b: [mem 0xfee00000-0xfee00fff]
[ 2.281049] system 00:0b: [mem 0xfec00000-0xfec00fff] could not be reserved
[ 2.281109] system 00:0b: [mem 0xfee00000-0xfee00fff] has been reserved
[ 2.281169] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.281230] pnp 00:0c: [io 0x0060]
[ 2.281232] pnp 00:0c: [io 0x0064]
[ 2.281238] pnp 00:0c: [irq 12]
[ 2.281284] pnp 00:0c: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
[ 2.281316] pnp 00:0d: [mem 0xe0000000-0xefffffff]
[ 2.281400] system 00:0d: [mem 0xe0000000-0xefffffff] has been reserved
[ 2.281461] system 00:0d: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.281622] pnp 00:0e: [mem 0x00000000-0x0009ffff]
[ 2.281624] pnp 00:0e: [mem 0x000c0000-0x000cffff]
[ 2.281626] pnp 00:0e: [mem 0x000e0000-0x000fffff]
[ 2.281628] pnp 00:0e: [mem 0x00100000-0xbfffffff]
[ 2.281630] pnp 00:0e: [mem 0xfed90000-0xffffffff]
[ 2.281736] system 00:0e: [mem 0x00000000-0x0009ffff] could not be reserved
[ 2.281796] system 00:0e: [mem 0x000c0000-0x000cffff] could not be reserved
[ 2.281856] system 00:0e: [mem 0x000e0000-0x000fffff] could not be reserved
[ 2.281915] system 00:0e: [mem 0x00100000-0xbfffffff] could not be reserved
[ 2.281974] system 00:0e: [mem 0xfed90000-0xffffffff] could not be reserved
[ 2.282035] system 00:0e: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 2.282157] pnp: PnP ACPI: found 15 devices
[ 2.282210] ACPI: ACPI bus type pnp unregistered
[ 2.289654] PCI: max bus depth: 1 pci_try_num: 2
[ 2.289715] pci 0000:00:01.0: PCI bridge to [bus 08-08]
[ 2.289774] pci 0000:00:01.0: bridge window [mem 0xfbe00000-0xfbefffff]
[ 2.289837] pci 0000:00:02.0: PCI bridge to [bus 07-07]
[ 2.289900] pci 0000:00:03.0: PCI bridge to [bus 06-06]
[ 2.289962] pci 0000:00:07.0: PCI bridge to [bus 05-05]
[ 2.290018] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 2.290078] pci 0000:00:07.0: bridge window [mem 0xfbd00000-0xfbdfffff]
[ 2.290138] pci 0000:00:07.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 2.290852] pci 0000:00:08.0: PCI bridge to [bus 04-04]
[ 2.290915] pci 0000:00:09.0: PCI bridge to [bus 03-03]
[ 2.290977] pci 0000:00:0a.0: PCI bridge to [bus 02-02]
[ 2.291039] pci 0000:00:1e.0: PCI bridge to [bus 01-01]
[ 2.291095] pci 0000:00:1e.0: bridge window [io 0xd000-0xdfff]
[ 2.291169] pci 0000:00:01.0: setting latency timer to 64
[ 2.291176] pci 0000:00:02.0: setting latency timer to 64
[ 2.291183] pci 0000:00:03.0: setting latency timer to 64
[ 2.291190] pci 0000:00:07.0: setting latency timer to 64
[ 2.291196] pci 0000:00:08.0: setting latency timer to 64
[ 2.291203] pci 0000:00:09.0: setting latency timer to 64
[ 2.291209] pci 0000:00:0a.0: setting latency timer to 64
[ 2.291216] pci 0000:00:1e.0: setting latency timer to 64
[ 2.291221] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 2.291224] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 2.291226] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 2.291228] pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
[ 2.291230] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xdfffffff]
[ 2.291233] pci_bus 0000:00: resource 9 [mem 0xf0000000-0xfed8ffff]
[ 2.291235] pci_bus 0000:08: resource 1 [mem 0xfbe00000-0xfbefffff]
[ 2.291238] pci_bus 0000:05: resource 0 [io 0xe000-0xefff]
[ 2.291240] pci_bus 0000:05: resource 1 [mem 0xfbd00000-0xfbdfffff]
[ 2.291242] pci_bus 0000:05: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
[ 2.291245] pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
[ 2.291248] pci_bus 0000:01: resource 4 [io 0x0000-0x0cf7]
[ 2.291250] pci_bus 0000:01: resource 5 [io 0x0d00-0xffff]
[ 2.291252] pci_bus 0000:01: resource 6 [mem 0x000a0000-0x000bffff]
[ 2.291254] pci_bus 0000:01: resource 7 [mem 0x000d0000-0x000dffff]
[ 2.291257] pci_bus 0000:01: resource 8 [mem 0xc0000000-0xdfffffff]
[ 2.291259] pci_bus 0000:01: resource 9 [mem 0xf0000000-0xfed8ffff]
[ 2.291261] pci_bus 0000:fe: resource 0 [io 0x0000-0xffff]
[ 2.291264] pci_bus 0000:fe: resource 1 [mem 0x00000000-0xffffffffff]
[ 2.291266] pci_bus 0000:ff: resource 0 [io 0x0000-0xffff]
[ 2.291269] pci_bus 0000:ff: resource 1 [mem 0x00000000-0xffffffffff]
[ 2.291318] NET: Registered protocol family 2
[ 2.291634] IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 2.292958] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
[ 2.295037] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 2.295338] TCP: Hash tables configured (established 524288 bind 65536)
[ 2.295396] TCP reno registered
[ 2.295462] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[ 2.295563] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[ 2.295791] NET: Registered protocol family 1
[ 2.296063] pci 0000:05:00.0: Boot video device
[ 2.296141] PCI: CLS 256 bytes, default 64
[ 2.296194] Trying to unpack rootfs image as initramfs...
[ 2.890699] Freeing initrd memory: 27876k freed
[ 2.897753] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 2.897818] Placing 64MB software IO TLB between ffff8800bb77b000 - ffff8800bf77b000
[ 2.897893] software IO TLB at phys 0xbb77b000 - 0xbf77b000
[ 2.899593] audit: initializing netlink socket (disabled)
[ 2.899665] type=2000 audit(1314417272.700:1): initialized
[ 2.941340] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 2.988436] VFS: Disk quotas dquot_6.5.2
[ 2.988567] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 2.989348] fuse init (API version 7.17)
[ 2.989512] msgmni has been set to 15947
[ 2.989865] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 2.989972] io scheduler noop registered
[ 2.990024] io scheduler deadline registered
[ 2.990121] io scheduler cfq registered (default)
[ 2.990689] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 2.990767] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 2.990935] intel_idle: MWAIT substates: 0x1120
[ 2.990950] intel_idle: v0.4 model 0x1A
[ 2.990952] intel_idle: lapic_timer_reliable_states 0x2
[ 2.991083] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
[ 2.991164] ACPI: Power Button [PWRB]
[ 2.991255] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 2.991331] ACPI: Power Button [PWRF]
[ 2.991593] ACPI: acpi_idle yielding to intel_idle
[ 2.994788] APEI: Can not request iomem region <00000000bf7b522a-00000000bf7b522c> for GARs.
[ 2.994912] [Firmware Warn]: GHES: Poll interval is 0 for generic hardware error source: 1, disabled.
[ 2.995048] \_SB_:_OSC evaluation returned wrong type
[ 2.995050] _OSC request data:1 0 0
[ 2.995054] GHES: Failed to enable APEI firmware first mode.
[ 2.995190] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 3.015795] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 3.199739] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 3.889262] Refined TSC clocksource calibration: 2133.408 MHz.
[ 3.889325] Switching to clocksource tsc
[ 8.240088] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 8.399972] 00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 8.539708] Linux agpgart interface v0.103
[ 8.539848] [drm] Initialized drm 1.1.0 20060810
[ 8.539914] [drm] radeon defaulting to kernel modesetting.
[ 8.539970] [drm] radeon kernel modesetting enabled.
[ 8.540106] radeon 0000:05:00.0: PCI INT A -> GSI 30 (level, low) -> IRQ 30
[ 8.540168] radeon 0000:05:00.0: setting latency timer to 64
[ 8.540319] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68F9 0x1462:0x2340).
[ 8.540432] [drm] register mmio base: 0xFBDC0000
[ 8.540486] [drm] register mmio size: 131072
[ 8.540690] ATOM BIOS: 113
[ 8.540816] radeon 0000:05:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[ 8.540895] radeon 0000:05:00.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF
[ 8.540974] mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining
[ 8.541051] [drm] Detected VRAM RAM=1024M, BAR=256M
[ 8.541105] [drm] RAM width 64bits DDR
[ 8.541200] [TTM] Zone kernel: Available graphics memory: 4082514 kiB.
[ 8.541262] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
[ 8.541320] [TTM] Initializing pool allocator.
[ 8.541400] [drm] radeon: 1024M of VRAM memory ready
[ 8.541455] [drm] radeon: 512M of GTT memory ready.
[ 8.541519] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 8.541576] [drm] Driver supports precise vblank timestamp query.
[ 8.541677] radeon 0000:05:00.0: irq 64 for MSI/MSI-X
[ 8.541683] radeon 0000:05:00.0: radeon: using MSI.
[ 8.541771] [drm] radeon: irq initialized.
[ 8.541826] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 8.542639] [drm] Loading CEDAR Microcode
[ 69.161605] r600_cp: Failed to load firmware "radeon/CEDAR_pfp.bin"
[ 69.161670] [drm:evergreen_startup] *ERROR* Failed to load firmware!
[ 69.161728] radeon 0000:05:00.0: disabling GPU acceleration
[ 69.162829] radeon 0000:05:00.0: ffff880235bc2c00 unpin not necessary
[ 69.162888] radeon 0000:05:00.0: ffff880235bc2c00 unpin not necessary
[ 69.162970] failed to evaluate ATIF got AE_BAD_PARAMETER
[ 69.163195] [drm] Radeon Display Connectors
[ 69.163248] [drm] Connector 0:
[ 69.163297] [drm] HDMI-A
[ 69.163346] [drm] HPD1
[ 69.163396] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
[ 69.163470] [drm] Encoders:
[ 69.163519] [drm] DFP1: INTERNAL_UNIPHY1
[ 69.163572] [drm] Connector 1:
[ 69.163621] [drm] DVI-I
[ 69.163670] [drm] HPD4
[ 69.163719] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c
[ 69.163793] [drm] Encoders:
[ 69.163843] [drm] DFP2: INTERNAL_UNIPHY
[ 69.163895] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 69.163948] [drm] Connector 2:
[ 69.163997] [drm] VGA
[ 69.164046] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
[ 69.164121] [drm] Encoders:
[ 69.164170] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[ 69.174083] [drm] Radeon display connector HDMI-A-1: No monitor connected or invalid EDID
[ 69.227644] [drm] Radeon display connector DVI-I-1: Found valid EDID
[ 69.237588] [drm] Radeon display connector VGA-1: No monitor connected or invalid EDID
[ 69.237712] [drm] Internal thermal controller with fan control
[ 69.237850] [drm] radeon: power management initialized
[ 69.315978] [drm] fb mappable at 0xD0040000
[ 69.316032] [drm] vram apper at 0xD0000000
[ 69.316084] [drm] size 7299072
[ 69.316134] [drm] fb depth is 24
[ 69.316184] [drm] pitch is 6912
[ 69.316290] fbcon: radeondrmfb (fb0) is primary device
[ 69.577073] Console: switching to colour frame buffer device 210x65
[ 69.581449] fb0: radeondrmfb frame buffer device
[ 69.581473] drm: registered panic notifier
[ 69.581499] [drm] Initialized radeon 2.11.0 20080528 for 0000:05:00.0 on minor 0
[ 69.582866] brd: module loaded
[ 69.583541] loop: module loaded
[ 69.583785] ata_piix 0000:00:1f.2: version 2.13
[ 69.583810] ata_piix 0000:00:1f.2: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 69.583848] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 69.583958] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 69.584188] scsi0 : ata_piix
[ 69.584296] scsi1 : ata_piix
[ 69.585289] ata1: SATA max UDMA/133 cmd 0xbc00 ctl 0xb880 bmdma 0xb400 irq 23
[ 69.585328] ata2: SATA max UDMA/133 cmd 0xb800 ctl 0xb480 bmdma 0xb408 irq 23
[ 69.585389] ata_piix 0000:00:1f.5: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[ 69.585427] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[ 69.585526] ata_piix 0000:00:1f.5: setting latency timer to 64
[ 69.585688] scsi2 : ata_piix
[ 69.585774] scsi3 : ata_piix
[ 69.586549] ata3: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 21
[ 69.586586] ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 21
[ 69.586953] Fixed MDIO Bus: probed
[ 69.587005] PPP generic driver version 2.4.2
[ 69.587072] tun: Universal TUN/TAP device driver, 1.6
[ 69.587098] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 69.587218] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 69.587277] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 69.587324] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[ 69.587328] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[ 69.587417] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
[ 69.587482] ehci_hcd 0000:00:1a.7: debug port 1
[ 69.591399] ehci_hcd 0000:00:1a.7: cache line size of 256 is not supported
[ 69.591414] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfbcfd000
[ 69.611552] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 69.611725] hub 1-0:1.0: USB hub found
[ 69.611750] hub 1-0:1.0: 4 ports detected
[ 69.611880] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 69.611927] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 69.611930] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 69.612003] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[ 69.612062] ehci_hcd 0000:00:1d.7: debug port 1
[ 69.615967] ehci_hcd 0000:00:1d.7: cache line size of 256 is not supported
[ 69.615972] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfbcfe000
[ 69.631554] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 69.631702] hub 2-0:1.0: USB hub found
[ 69.631726] hub 2-0:1.0: 8 ports detected
[ 69.631847] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 69.631902] uhci_hcd: USB Universal Host Controller Interface driver
[ 69.633682] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 69.635415] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[ 69.635419] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 69.637190] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[ 69.638997] uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000a400
[ 69.640884] hub 3-0:1.0: USB hub found
[ 69.642676] hub 3-0:1.0: 2 ports detected
[ 69.644540] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[ 69.646339] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[ 69.646342] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 69.648155] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[ 69.649976] uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000a480
[ 69.651904] hub 4-0:1.0: USB hub found
[ 69.653703] hub 4-0:1.0: 2 ports detected
[ 69.655561] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 69.657359] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 69.657363] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 69.659199] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
[ 69.661018] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000a800
[ 69.662921] hub 5-0:1.0: USB hub found
[ 69.664707] hub 5-0:1.0: 2 ports detected
[ 69.666577] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 69.668388] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 69.668392] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 69.670233] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
[ 69.672101] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000a880
[ 69.674056] hub 6-0:1.0: USB hub found
[ 69.675890] hub 6-0:1.0: 2 ports detected
[ 69.677798] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 69.679657] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 69.679661] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 69.681558] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
[ 69.683423] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000ac00
[ 69.685375] hub 7-0:1.0: USB hub found
[ 69.687217] hub 7-0:1.0: 2 ports detected
[ 69.689107] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
[ 69.690948] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[ 69.690951] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 69.692820] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 8
[ 69.694694] uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000b000
[ 69.696635] hub 8-0:1.0: USB hub found
[ 69.698481] hub 8-0:1.0: 2 ports detected
[ 69.700455] i8042: PNP: PS/2 Controller [PNP0f03:PS2M] at 0x60,0x64 irq 12
[ 69.702308] i8042: PNP: PS/2 controller doesn't have KBD irq; using default 1
[ 69.706805] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 69.708707] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 69.710664] mousedev: PS/2 mouse device common for all mice
[ 69.712662] rtc_cmos 00:03: RTC can wake from S4
[ 69.714586] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 69.716425] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 69.718351] device-mapper: uevent: version 1.0.3
[ 69.720271] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: dm-devel@redhat.com
[ 69.722194] device-mapper: multipath: version 1.3.0 loaded
[ 69.724046] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 69.726164] cpuidle: using governor ladder
[ 69.728276] cpuidle: using governor menu
[ 69.730094] EFI Variables Facility v0.08 2004-May-17
[ 69.732197] TCP cubic registered
[ 69.734162] NET: Registered protocol family 10
[ 69.737059] NET: Registered protocol family 17
[ 69.738907] Registering the dns_resolver key type
[ 69.741305] PM: Hibernation image not present or could not be loaded.
[ 69.741322] registered taskstats version 1
[ 69.766310] Magic number: 7:248:918
[ 69.768526] rtc_cmos 00:03: setting system clock to 2011-08-27 03:55:40 UTC (1314417340)
[ 69.773751] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 69.775588] EDD information not available.
[ 69.942688] ata4: SATA link down (SStatus 0 SControl 300)
[ 69.955377] ata3: SATA link down (SStatus 0 SControl 300)
[ 70.011734] usb 2-2: new high speed USB device number 3 using ehci_hcd
[ 70.441815] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 70.443696] ata2.01: SATA link down (SStatus 0 SControl 300)
[ 70.445566] ata2.01: link offline, clearing class 3 to NONE
[ 70.445811] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 70.447711] ata1.01: SATA link down (SStatus 0 SControl 300)
[ 70.451810] usb 5-1: new low speed USB device number 2 using uhci_hcd
[ 70.462025] ata2.00: ATAPI: Optiarc DVD RW AD-7260S, 1.03, max UDMA/100
[ 70.464397] ata1.00: ATA-8: ST31000524AS, JC45, max UDMA/133
[ 70.466281] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 70.482326] ata1.00: configured for UDMA/133
[ 70.484559] scsi 0:0:0:0: Direct-Access ATA ST31000524AS JC45 PQ: 0 ANSI: 5
[ 70.486777] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 70.488781] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 70.490694] sd 0:0:0:0: [sda] Write Protect is off
[ 70.492905] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 70.492929] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 70.501988] ata2.00: configured for UDMA/100
[ 70.506238] scsi 1:0:0:0: CD-ROM Optiarc DVD RW AD-7260S 1.03 PQ: 0 ANSI: 5
[ 70.510752] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[ 70.513057] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 70.515296] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 70.515455] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 70.532421] sda: sda1 sda2 < sda5 >
[ 70.535444] sd 0:0:0:0: [sda] Attached SCSI disk
[ 70.539983] Freeing unused kernel memory: 840k freed
[ 70.542094] Write protecting the kernel read-only data: 12288k
[ 70.549760] Freeing unused kernel memory: 956k freed
[ 70.556525] Freeing unused kernel memory: 924k freed
[ 70.585206] udev[106]: starting version 167
[ 70.684145] input: KB Multimedia keyboard as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input2
[ 70.686488] generic-usb 0003:05D5:0624.0001: input,hidraw0: USB HID v1.10 Keyboard [KB Multimedia keyboard ] on usb-0000:00:1d.0-1/input0
[ 70.701088] input: KB Multimedia keyboard as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.1/input/input3
[ 70.703671] generic-usb 0003:05D5:0624.0002: input,hidraw1: USB HID v1.10 Device [KB Multimedia keyboard ] on usb-0000:00:1d.0-1/input1
[ 70.705757] usbcore: registered new interface driver usbhid
[ 70.707777] usbhid: USB HID core driver
[ 70.934817] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 72.542461] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 73.112103] udev[431]: starting version 167
[ 74.746885] EDAC MC: Ver: 2.1.0
[ 74.747855] dca service started, version 1.12.1
[ 74.754147] type=1400 audit(1314417345.474:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=714 comm="apparmor_parser"
[ 74.754212] type=1400 audit(1314417345.474:3): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=714 comm="apparmor_parser"
[ 74.754269] type=1400 audit(1314417345.474:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=714 comm="apparmor_parser"
[ 74.790536] lp: driver loaded but no devices found
[ 74.798619] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 74.819373] ipmi message handler version 39.2
[ 74.839884] ipmi device interface
[ 74.851559] EDAC MC1: Giving out device to 'i7core_edac.c' 'i7 core #1': DEV 0000:fe:03.0
[ 74.851580] EDAC PCI0: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:fe:03.0' (POLLED)
[ 74.851616] EDAC MC0: Giving out device to 'i7core_edac.c' 'i7 core #0': DEV 0000:ff:03.0
[ 74.851626] EDAC PCI1: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:ff:03.0' (POLLED)
[ 74.851628] EDAC i7core: Driver loaded.
[ 74.867847] Linux video capture interface: v2.00
[ 75.084160] cfg80211: Calling CRDA to update world regulatory domain
[ 75.183610] IPMI System Interface driver.
[ 75.183674] ipmi_si: probing via SMBIOS
[ 75.183677] ipmi_si: SMBIOS: mem 0xca2 regsize 1 spacing 1 irq 0
[ 75.183679] ipmi_si: Adding SMBIOS-specified kcs state machine
[ 75.183683] ipmi_si: probing via SPMI
[ 75.183685] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
[ 75.183687] ipmi_si: Adding SPMI-specified kcs state machine
[ 75.183690] ipmi_si: Trying SMBIOS-specified kcs state machine at mem address 0xca2, slave address 0x0, irq 0
[ 75.183693] ipmi_si: Could not set up I/O space
[ 75.282130] ipmi_si: Trying SPMI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
[ 75.282139] ipmi_si: Interface detection failed
[ 75.428908] coretemp coretemp.0: TjMax is 97 C.
[ 75.428927] coretemp coretemp.0: TjMax is 97 C.
[ 75.428942] coretemp coretemp.0: TjMax is 97 C.
[ 75.429003] coretemp coretemp.0: TjMax is 97 C.
[ 75.429058] coretemp coretemp.4: TjMax is 97 C.
[ 75.429129] coretemp coretemp.4: TjMax is 97 C.
[ 75.429191] coretemp coretemp.4: TjMax is 97 C.
[ 75.429385] coretemp coretemp.4: TjMax is 97 C.
[ 75.440106] ioatdma: Intel(R) QuickData Technology Driver 4.00
[ 75.440192] ioatdma 0000:00:16.0: enabling device (0000 -> 0002)
[ 75.440217] ioatdma 0000:00:16.0: PCI INT A -> GSI 43 (level, low) -> IRQ 43
[ 75.440248] ioatdma 0000:00:16.0: setting latency timer to 64
[ 75.440292] ioatdma 0000:00:16.0: irq 64 for MSI/MSI-X
[ 75.440623] ioatdma 0000:00:16.1: enabling device (0000 -> 0002)
[ 75.440641] ioatdma 0000:00:16.1: PCI INT B -> GSI 44 (level, low) -> IRQ 44
[ 75.440676] ioatdma 0000:00:16.1: setting latency timer to 64
[ 75.440718] ioatdma 0000:00:16.1: irq 65 for MSI/MSI-X
[ 75.440954] ioatdma 0000:00:16.2: enabling device (0000 -> 0002)
[ 75.440965] ioatdma 0000:00:16.2: PCI INT C -> GSI 45 (level, low) -> IRQ 45
[ 75.440985] ioatdma 0000:00:16.2: setting latency timer to 64
[ 75.441019] ioatdma 0000:00:16.2: irq 66 for MSI/MSI-X
[ 75.441286] ioatdma 0000:00:16.3: enabling device (0000 -> 0002)
[ 75.441297] ioatdma 0000:00:16.3: PCI INT D -> GSI 46 (level, low) -> IRQ 46
[ 75.441316] ioatdma 0000:00:16.3: setting latency timer to 64
[ 75.441349] ioatdma 0000:00:16.3: irq 67 for MSI/MSI-X
[ 75.441571] ioatdma 0000:00:16.4: enabling device (0000 -> 0002)
[ 75.441577] ioatdma 0000:00:16.4: PCI INT A -> GSI 43 (level, low) -> IRQ 43
[ 75.441595] ioatdma 0000:00:16.4: setting latency timer to 64
[ 75.441630] ioatdma 0000:00:16.4: irq 68 for MSI/MSI-X
[ 75.442028] ioatdma 0000:00:16.5: enabling device (0000 -> 0002)
[ 75.442037] ioatdma 0000:00:16.5: PCI INT B -> GSI 44 (level, low) -> IRQ 44
[ 75.442061] ioatdma 0000:00:16.5: setting latency timer to 64
[ 75.442101] ioatdma 0000:00:16.5: irq 69 for MSI/MSI-X
[ 75.442336] ioatdma 0000:00:16.6: enabling device (0000 -> 0002)
[ 75.442341] ioatdma 0000:00:16.6: PCI INT C -> GSI 45 (level, low) -> IRQ 45
[ 75.442360] ioatdma 0000:00:16.6: setting latency timer to 64
[ 75.442398] ioatdma 0000:00:16.6: irq 70 for MSI/MSI-X
[ 75.442623] ioatdma 0000:00:16.7: enabling device (0000 -> 0002)
[ 75.442629] ioatdma 0000:00:16.7: PCI INT D -> GSI 46 (level, low) -> IRQ 46
[ 75.442648] ioatdma 0000:00:16.7: setting latency timer to 64
[ 75.442683] ioatdma 0000:00:16.7: irq 71 for MSI/MSI-X
[ 75.451626] uvcvideo: Found UVC 1.00 device Vimicro USB Camera (Altair) (0ac8:3450)
[ 75.454136] input: Vimicro USB Camera (Altair) as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2:1.0/input/input4
[ 75.454520] usbcore: registered new interface driver uvcvideo
[ 75.454522] USB Video Class driver (1.1.1)
[ 75.489217] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5
[ 75.663366] cfg80211: World regulatory domain updated:
[ 75.663370] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 75.663373] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 75.663375] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 75.663378] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 75.663381] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 75.663383] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 75.915766] w83627ehf: Found W83667HG chip at 0x290
[ 76.232217] i2c i2c-8: Found w83795adg rev. B at 0x2f
[ 76.449146] ath9k 0000:08:00.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
[ 76.449156] ath9k 0000:08:00.0: setting latency timer to 64
[ 76.482020] w83795 8-002f: PECI agent 1 Tbase temperature: 85
[ 76.497925] ath: EEPROM regdomain: 0x809c
[ 76.497927] ath: EEPROM indicates we should expect a country code
[ 76.497929] ath: doing EEPROM country->regdmn map search
[ 76.497931] ath: country maps to regdmn code: 0x52
[ 76.497933] ath: Country alpha2 being used: CN
[ 76.497934] ath: Regpair used: 0x52
[ 76.497937] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497940] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497942] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497945] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497947] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497950] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497952] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497954] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497957] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497959] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497961] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497964] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497966] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497968] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497971] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497973] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497975] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497978] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497980] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497982] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497984] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 76.497987] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.497989] cfg80211: Disabling freq 2467 MHz as custom regd has no rule that fits a 20 MHz wide channel
[ 76.497992] cfg80211: Disabling freq 2472 MHz as custom regd has no rule that fits a 20 MHz wide channel
[ 76.497994] cfg80211: Disabling freq 2484 MHz as custom regd has no rule that fits a 20 MHz wide channel
[ 76.499580] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499583] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499586] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499588] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499590] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499593] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499595] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499598] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499600] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499602] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499605] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499607] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499609] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499612] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499614] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499617] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499619] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499622] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499624] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499626] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499629] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499631] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499633] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499636] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499638] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499641] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.499643] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
[ 76.499645] cfg80211: 2474000 KHz - 2494000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 76.512208] w83795 8-002f: PECI agent 2 Tbase temperature: 85
[ 76.543487] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[ 76.544140] cfg80211: Calling CRDA for country: CN
[ 76.544290] Registered led device: ath9k-phy0
[ 76.544295] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc90011800000, irq=28
[ 76.548064] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548068] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548071] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548073] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548076] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548078] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548080] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548083] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548085] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548088] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548090] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548092] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548094] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548097] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548099] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548102] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548104] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548106] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548109] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548111] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548113] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548116] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548118] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548121] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548123] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
[ 76.548125] cfg80211: 2402000 KHz - 2482000 KHz @ KHz), (N/A mBi, 2000 mBm)
[ 76.548128] cfg80211: Disabling freq 2484 MHz
[ 76.548131] cfg80211: Regulatory domain changed to country: CN
[ 76.548133] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 76.548135] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 76.548138] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (N/A, 3000 mBm)
[ 76.840877] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 76.840939] snd_hda_intel 0000:00:1b.0: irq 72 for MSI/MSI-X
[ 76.840967] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
[ 76.867656] snd_ca0106 0000:01:04.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 76.867672] snd-ca0106: Model 100a Rev 00000000 Serial 100a1102
[ 76.932244] hda-intel: no codecs found!
[ 76.932332] snd_hda_intel 0000:00:1b.0: PCI INT A disabled
[ 76.932388] snd_hda_intel 0000:05:00.1: PCI INT B -> GSI 37 (level, low) -> IRQ 37
[ 76.932833] snd_hda_intel 0000:05:00.1: irq 72 for MSI/MSI-X
[ 76.932858] snd_hda_intel 0000:05:00.1: setting latency timer to 64
[ 77.047767] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0
[ 77.048094] input: HD-Audio Generic HDMI/DP as /devices/pci0000:00/0000:00:07.0/0000:05:00.1/sound/card0/input6
[ 77.230503] type=1400 audit(1314417347.944:5): apparmor="STATUS" operation="profile_load" name="/usr/share/gdm/guest-session/Xsession" pid=1053 comm="apparmor_parser"
[ 77.234188] type=1400 audit(1314417347.954:6): apparmor="STATUS" operation="profile_load" name="/usr/sbin/libvirtd" pid=1059 comm="apparmor_parser"
[ 77.265979] type=1400 audit(1314417347.984:7): apparmor="STATUS" operation="profile_load" name="/usr/sbin/tcpdump" pid=1060 comm="apparmor_parser"
[ 77.330562] type=1400 audit(1314417348.044:8): apparmor="STATUS" operation="profile_load" name="/usr/lib/libvirt/virt-aa-helper" pid=1057 comm="apparmor_parser"
[ 77.395107] type=1400 audit(1314417348.114:9): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
[ 77.395178] type=1400 audit(1314417348.114:10): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1054 comm="apparmor_parser"
[ 77.395237] type=1400 audit(1314417348.114:11): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=1054 comm="apparmor_parser"
[ 78.193303] ppdev: user-space parallel port driver
[ 78.872807] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 80.405067] Adding 19529724k swap on /dev/mapper/cryptswap1. Priority:-1 extents:1 across:19529724k
[ 81.182974] wlan0: authenticate with 00:26:b8:18:ff:90 (try 1)
[ 81.184888] wlan0: authenticated
[ 81.184915] wlan0: associate with 00:26:b8:18:ff:90 (try 1)
[ 81.187966] wlan0: RX AssocResp from 00:26:b8:18:ff:90 (capab=0x431 status=0 aid=2)
[ 81.187970] wlan0: associated
[ 81.188867] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 81.382400] cfg80211: Calling CRDA for country: US
[ 81.385907] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385911] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385914] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385917] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385919] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385922] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385924] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385926] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385929] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385931] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385933] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385936] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385938] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385941] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385943] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385946] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385948] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385950] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385952] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385955] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385957] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 81.385960] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[ 81.385962] cfg80211: Disabling freq 2467 MHz
[ 81.385963] cfg80211: Disabling freq 2472 MHz
[ 81.385965] cfg80211: Disabling freq 2484 MHz
[ 81.385968] cfg80211: Regulatory domain changed to country: US
[ 81.385970] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 81.385972] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 81.385975] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 81.385977] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 81.385980] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 81.385982] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 81.385985] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 83.132334] audit_printk_skb: 12 callbacks suppressed
[ 83.132337] type=1400 audit(1314417353.854:16): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince" pid=1055 comm="apparmor_parser"
[ 83.133435] type=1400 audit(1314417353.854:17): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince-previewer" pid=1055 comm="apparmor_parser"
[ 83.133806] type=1400 audit(1314417353.854:18): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince-thumbnailer" pid=1055 comm="apparmor_parser"
[ 85.843441] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-27 4:20 Kernel almost hangs when CONFIG_DRM_RADEON=y Pavel Ivanov
@ 2011-08-27 9:00 ` Michel Dänzer
2011-08-27 22:50 ` Pavel Ivanov
2011-08-27 23:03 ` Kyle Moffett
0 siblings, 2 replies; 37+ messages in thread
From: Michel Dänzer @ 2011-08-27 9:00 UTC (permalink / raw)
To: Pavel Ivanov; +Cc: dri-devel, linux-kernel
On Sam, 2011-08-27 at 00:20 -0400, Pavel Ivanov wrote:
>
> I observe very strange behavior dependent on value of
> CONFIG_DRM_RADEON parameter. When it's set to m everything works very
> good, no problem. When I set it to y I see kernel hang during boot. Or
> I should better say it "almost hangs" because during last boot attempt
> I accidentally waited a little bit longer and saw that after more than
> a minute waiting system continued to boot. Dmesg after "hang" shows
> these messages:
>
> [ 8.542639] [drm] Loading CEDAR Microcode
> [ 69.161605] r600_cp: Failed to load firmware "radeon/CEDAR_pfp.bin"
> [ 69.161670] [drm:evergreen_startup] *ERROR* Failed to load firmware!
>
> While during normal boot
>
> [ 9.898870] [drm] Loading CEDAR Microcode
> [ 9.908425] radeon 0000:05:00.0: WB enabled
With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
loaded from userspace, so it needs to be built into the kernel as well.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-27 9:00 ` Michel Dänzer
@ 2011-08-27 22:50 ` Pavel Ivanov
2011-08-28 5:36 ` Borislav Petkov
2011-08-27 23:03 ` Kyle Moffett
1 sibling, 1 reply; 37+ messages in thread
From: Pavel Ivanov @ 2011-08-27 22:50 UTC (permalink / raw)
To: Michel Dänzer; +Cc: dri-devel, linux-kernel
2011/8/27 Michel Dänzer <michel@daenzer.net>:
>> I observe very strange behavior dependent on value of
>> CONFIG_DRM_RADEON parameter. When it's set to m everything works very
>> good, no problem. When I set it to y I see kernel hang during boot. Or
>> I should better say it "almost hangs" because during last boot attempt
>> I accidentally waited a little bit longer and saw that after more than
>> a minute waiting system continued to boot. Dmesg after "hang" shows
>> these messages:
>>
>> [ 8.542639] [drm] Loading CEDAR Microcode
>> [ 69.161605] r600_cp: Failed to load firmware "radeon/CEDAR_pfp.bin"
>> [ 69.161670] [drm:evergreen_startup] *ERROR* Failed to load firmware!
>>
>> While during normal boot
>>
>> [ 9.898870] [drm] Loading CEDAR Microcode
>> [ 9.908425] radeon 0000:05:00.0: WB enabled
>
> With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
> loaded from userspace, so it needs to be built into the kernel as well.
How should I do that? I've tried to set all "m"s to "y" in .config and
still saw this issue. Should I set some special parameter?
Pavel
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-27 22:50 ` Pavel Ivanov
@ 2011-08-28 5:36 ` Borislav Petkov
2011-08-28 21:47 ` Pavel Ivanov
2011-08-29 13:20 ` Peter Zijlstra
0 siblings, 2 replies; 37+ messages in thread
From: Borislav Petkov @ 2011-08-28 5:36 UTC (permalink / raw)
To: Pavel Ivanov; +Cc: Michel Dänzer, dri-devel, linux-kernel
On Sat, Aug 27, 2011 at 06:50:37PM -0400, Pavel Ivanov wrote:
> 2011/8/27 Michel Dänzer <michel@daenzer.net>:
> >> I observe very strange behavior dependent on value of
> >> CONFIG_DRM_RADEON parameter. When it's set to m everything works very
> >> good, no problem. When I set it to y I see kernel hang during boot. Or
> >> I should better say it "almost hangs" because during last boot attempt
> >> I accidentally waited a little bit longer and saw that after more than
> >> a minute waiting system continued to boot. Dmesg after "hang" shows
> >> these messages:
> >>
> >> [ 8.542639] [drm] Loading CEDAR Microcode
> >> [ 69.161605] r600_cp: Failed to load firmware "radeon/CEDAR_pfp.bin"
> >> [ 69.161670] [drm:evergreen_startup] *ERROR* Failed to load firmware!
> >>
> >> While during normal boot
> >>
> >> [ 9.898870] [drm] Loading CEDAR Microcode
> >> [ 9.908425] radeon 0000:05:00.0: WB enabled
> >
> > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
> > loaded from userspace, so it needs to be built into the kernel as well.
>
> How should I do that? I've tried to set all "m"s to "y" in .config and
> still saw this issue. Should I set some special parameter?
You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
most probably be located in /lib/firmware or to whatever you have set
CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
a warning at the end of the kernel build). This way, it works for both
radeon being =m and =y.
HTH.
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-28 5:36 ` Borislav Petkov
@ 2011-08-28 21:47 ` Pavel Ivanov
2011-08-29 13:20 ` Peter Zijlstra
1 sibling, 0 replies; 37+ messages in thread
From: Pavel Ivanov @ 2011-08-28 21:47 UTC (permalink / raw)
To: Borislav Petkov, Pavel Ivanov, Michel Dänzer, dri-devel,
linux-kernel
On Sun, Aug 28, 2011 at 1:36 AM, Borislav Petkov <bp@alien8.de> wrote:
>> > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
>> > loaded from userspace, so it needs to be built into the kernel as well.
>>
>> How should I do that? I've tried to set all "m"s to "y" in .config and
>> still saw this issue. Should I set some special parameter?
>
> You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
> configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
>
> The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
> most probably be located in /lib/firmware or to whatever you have set
> CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
> a warning at the end of the kernel build). This way, it works for both
> radeon being =m and =y.
Everything else in /lib/firmware/radeon is needed after user space
become available?
Pavel
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
@ 2011-08-28 21:47 ` Pavel Ivanov
0 siblings, 0 replies; 37+ messages in thread
From: Pavel Ivanov @ 2011-08-28 21:47 UTC (permalink / raw)
To: Borislav Petkov, Pavel Ivanov, Michel Dänzer, dri-devel,
linux-kernel
On Sun, Aug 28, 2011 at 1:36 AM, Borislav Petkov <bp@alien8.de> wrote:
>> > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
>> > loaded from userspace, so it needs to be built into the kernel as well.
>>
>> How should I do that? I've tried to set all "m"s to "y" in .config and
>> still saw this issue. Should I set some special parameter?
>
> You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
> configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
>
> The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
> most probably be located in /lib/firmware or to whatever you have set
> CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
> a warning at the end of the kernel build). This way, it works for both
> radeon being =m and =y.
Everything else in /lib/firmware/radeon is needed after user space
become available?
Pavel
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-28 21:47 ` Pavel Ivanov
(?)
@ 2011-08-29 5:49 ` Borislav Petkov
2011-08-29 6:04 ` Michel Dänzer
-1 siblings, 1 reply; 37+ messages in thread
From: Borislav Petkov @ 2011-08-29 5:49 UTC (permalink / raw)
To: Pavel Ivanov; +Cc: Michel Dänzer, dri-devel, linux-kernel
On Sun, Aug 28, 2011 at 05:47:59PM -0400, Pavel Ivanov wrote:
> On Sun, Aug 28, 2011 at 1:36 AM, Borislav Petkov <bp@alien8.de> wrote:
> >> > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
> >> > loaded from userspace, so it needs to be built into the kernel as well.
> >>
> >> How should I do that? I've tried to set all "m"s to "y" in .config and
> >> still saw this issue. Should I set some special parameter?
> >
> > You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
> > configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
> >
> > The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
> > most probably be located in /lib/firmware or to whatever you have set
> > CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
> > a warning at the end of the kernel build). This way, it works for both
> > radeon being =m and =y.
>
> Everything else in /lib/firmware/radeon is needed after user space
> become available?
You mean the other *.bin files? If so, not for your case, AFAICT - your
driver is requesting CEDAR_pfp.bin only, correct? But I mean, it won't
hurt if you leave them all there, they're under 1M.
You should recheck and add any other .bin files to the
CONFIG_EXTRA_FIRMWARE string so that radeon.ko is satisfied :).
HTH.
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 5:49 ` Borislav Petkov
@ 2011-08-29 6:04 ` Michel Dänzer
0 siblings, 0 replies; 37+ messages in thread
From: Michel Dänzer @ 2011-08-29 6:04 UTC (permalink / raw)
To: Borislav Petkov; +Cc: Pavel Ivanov, linux-kernel, dri-devel
On Mon, 2011-08-29 at 07:49 +0200, Borislav Petkov wrote:
> On Sun, Aug 28, 2011 at 05:47:59PM -0400, Pavel Ivanov wrote:
> > On Sun, Aug 28, 2011 at 1:36 AM, Borislav Petkov <bp@alien8.de> wrote:
> > >> > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
> > >> > loaded from userspace, so it needs to be built into the kernel as well.
> > >>
> > >> How should I do that? I've tried to set all "m"s to "y" in .config and
> > >> still saw this issue. Should I set some special parameter?
> > >
> > > You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
> > > configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
> > >
> > > The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
> > > most probably be located in /lib/firmware or to whatever you have set
> > > CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
> > > a warning at the end of the kernel build). This way, it works for both
> > > radeon being =m and =y.
> >
> > Everything else in /lib/firmware/radeon is needed after user space
> > become available?
>
> You mean the other *.bin files? If so, not for your case, AFAICT - your
> driver is requesting CEDAR_pfp.bin only, correct?
It'll need all the CEDAR_*.bin files.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
@ 2011-08-29 6:04 ` Michel Dänzer
0 siblings, 0 replies; 37+ messages in thread
From: Michel Dänzer @ 2011-08-29 6:04 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, dri-devel, Pavel Ivanov
On Mon, 2011-08-29 at 07:49 +0200, Borislav Petkov wrote:
> On Sun, Aug 28, 2011 at 05:47:59PM -0400, Pavel Ivanov wrote:
> > On Sun, Aug 28, 2011 at 1:36 AM, Borislav Petkov <bp@alien8.de> wrote:
> > >> > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
> > >> > loaded from userspace, so it needs to be built into the kernel as well.
> > >>
> > >> How should I do that? I've tried to set all "m"s to "y" in .config and
> > >> still saw this issue. Should I set some special parameter?
> > >
> > > You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
> > > configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
> > >
> > > The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
> > > most probably be located in /lib/firmware or to whatever you have set
> > > CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
> > > a warning at the end of the kernel build). This way, it works for both
> > > radeon being =m and =y.
> >
> > Everything else in /lib/firmware/radeon is needed after user space
> > become available?
>
> You mean the other *.bin files? If so, not for your case, AFAICT - your
> driver is requesting CEDAR_pfp.bin only, correct?
It'll need all the CEDAR_*.bin files.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-28 5:36 ` Borislav Petkov
2011-08-28 21:47 ` Pavel Ivanov
@ 2011-08-29 13:20 ` Peter Zijlstra
2011-08-29 13:38 ` Borislav Petkov
1 sibling, 1 reply; 37+ messages in thread
From: Peter Zijlstra @ 2011-08-29 13:20 UTC (permalink / raw)
To: Borislav Petkov; +Cc: Pavel Ivanov, Michel Dänzer, dri-devel, linux-kernel
On Sun, 2011-08-28 at 07:36 +0200, Borislav Petkov wrote:
> > > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
> > > loaded from userspace, so it needs to be built into the kernel as well.
> >
> > How should I do that? I've tried to set all "m"s to "y" in .config and
> > still saw this issue. Should I set some special parameter?
>
> You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
> configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
>
> The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
> most probably be located in /lib/firmware or to whatever you have set
> CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
> a warning at the end of the kernel build). This way, it works for both
> radeon being =m and =y.
Should we make Kconfig pop up a dialog and ask for the whereabouts of
these firmware thingies when you mark the driver =y?
This all sounds like magic to me, having to know you need to add to
EXTRA_FIRMWARE, having to know what file it needs etc.. For all intents
and purposes =y just doesn't work and that's broken.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 13:20 ` Peter Zijlstra
@ 2011-08-29 13:38 ` Borislav Petkov
2011-08-29 13:43 ` Dave Airlie
2011-08-29 13:48 ` Alex Deucher
0 siblings, 2 replies; 37+ messages in thread
From: Borislav Petkov @ 2011-08-29 13:38 UTC (permalink / raw)
To: Peter Zijlstra, Alex Deucher
Cc: Pavel Ivanov, Michel Dänzer, dri-devel, linux-kernel
On Mon, Aug 29, 2011 at 03:20:21PM +0200, Peter Zijlstra wrote:
> On Sun, 2011-08-28 at 07:36 +0200, Borislav Petkov wrote:
> > > > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
> > > > loaded from userspace, so it needs to be built into the kernel as well.
> > >
> > > How should I do that? I've tried to set all "m"s to "y" in .config and
> > > still saw this issue. Should I set some special parameter?
> >
> > You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
> > configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
> >
> > The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
> > most probably be located in /lib/firmware or to whatever you have set
> > CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
> > a warning at the end of the kernel build). This way, it works for both
> > radeon being =m and =y.
>
> Should we make Kconfig pop up a dialog and ask for the whereabouts of
> these firmware thingies when you mark the driver =y?
>
> This all sounds like magic to me, having to know you need to add to
> EXTRA_FIRMWARE, having to know what file it needs etc.. For all intents
> and purposes =y just doesn't work and that's broken.
Yep, you make a lot of sense. I had to fumble the build/reboot cycle a
couple of times and do some code staring even to figure this out. In
the end, I copied the whole radeon/ folder from David's firmware git
repo into /lib/firmware and made radeon.ko =m again so that I don't have
to add *.bin entries to CONFIG_EXTRA_FIRMWARE each time I'm building a
kernel on a different machine.
Besides, there was this other issue on lkml today where
CONFIG_EXTRA_FIRMWARE can cause nconf to segfault when you overflow
its length of 256 by trying to include a bunch of firmware *bin files:
http://lkml.org/lkml/2011/8/29/86
Alex?
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 13:38 ` Borislav Petkov
@ 2011-08-29 13:43 ` Dave Airlie
2011-08-29 13:48 ` Alex Deucher
1 sibling, 0 replies; 37+ messages in thread
From: Dave Airlie @ 2011-08-29 13:43 UTC (permalink / raw)
To: Borislav Petkov
Cc: Peter Zijlstra, Alex Deucher, Pavel Ivanov, Michel Dänzer,
dri-devel, linux-kernel
2011/8/29 Borislav Petkov <bp@alien8.de>:
> On Mon, Aug 29, 2011 at 03:20:21PM +0200, Peter Zijlstra wrote:
>> On Sun, 2011-08-28 at 07:36 +0200, Borislav Petkov wrote:
>> > > > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
>> > > > loaded from userspace, so it needs to be built into the kernel as well.
>> > >
>> > > How should I do that? I've tried to set all "m"s to "y" in .config and
>> > > still saw this issue. Should I set some special parameter?
>> >
>> > You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
>> > configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
>> >
>> > The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
>> > most probably be located in /lib/firmware or to whatever you have set
>> > CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
>> > a warning at the end of the kernel build). This way, it works for both
>> > radeon being =m and =y.
>>
>> Should we make Kconfig pop up a dialog and ask for the whereabouts of
>> these firmware thingies when you mark the driver =y?
>>
>> This all sounds like magic to me, having to know you need to add to
>> EXTRA_FIRMWARE, having to know what file it needs etc.. For all intents
>> and purposes =y just doesn't work and that's broken.
>
> Yep, you make a lot of sense. I had to fumble the build/reboot cycle a
> couple of times and do some code staring even to figure this out. In
> the end, I copied the whole radeon/ folder from David's firmware git
> repo into /lib/firmware and made radeon.ko =m again so that I don't have
> to add *.bin entries to CONFIG_EXTRA_FIRMWARE each time I'm building a
> kernel on a different machine.
That asks the question is your distro isn't shipping those firmware for you.
The main thing is you build in the driver which firmware to include?
granted all the radeon firmware is only about 580k so its probably not
a problem to somehow magically add them all to CONFIG_EXTRA_FIRMWARE
if RADEON=y, if someone thinks to make kbuild do it, but you really
only 3 or 4 of them on any one card.
Dave.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 13:38 ` Borislav Petkov
2011-08-29 13:43 ` Dave Airlie
@ 2011-08-29 13:48 ` Alex Deucher
2011-08-29 14:16 ` Borislav Petkov
2011-08-29 16:28 ` Kyle Moffett
1 sibling, 2 replies; 37+ messages in thread
From: Alex Deucher @ 2011-08-29 13:48 UTC (permalink / raw)
To: Borislav Petkov
Cc: Peter Zijlstra, Pavel Ivanov, Michel Dänzer, dri-devel,
linux-kernel
2011/8/29 Borislav Petkov <bp@alien8.de>:
> On Mon, Aug 29, 2011 at 03:20:21PM +0200, Peter Zijlstra wrote:
>> On Sun, 2011-08-28 at 07:36 +0200, Borislav Petkov wrote:
>> > > > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
>> > > > loaded from userspace, so it needs to be built into the kernel as well.
>> > >
>> > > How should I do that? I've tried to set all "m"s to "y" in .config and
>> > > still saw this issue. Should I set some special parameter?
>> >
>> > You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
>> > configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
>> >
>> > The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
>> > most probably be located in /lib/firmware or to whatever you have set
>> > CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
>> > a warning at the end of the kernel build). This way, it works for both
>> > radeon being =m and =y.
>>
>> Should we make Kconfig pop up a dialog and ask for the whereabouts of
>> these firmware thingies when you mark the driver =y?
>>
>> This all sounds like magic to me, having to know you need to add to
>> EXTRA_FIRMWARE, having to know what file it needs etc.. For all intents
>> and purposes =y just doesn't work and that's broken.
>
> Yep, you make a lot of sense. I had to fumble the build/reboot cycle a
> couple of times and do some code staring even to figure this out. In
> the end, I copied the whole radeon/ folder from David's firmware git
> repo into /lib/firmware and made radeon.ko =m again so that I don't have
> to add *.bin entries to CONFIG_EXTRA_FIRMWARE each time I'm building a
> kernel on a different machine.
>
> Besides, there was this other issue on lkml today where
> CONFIG_EXTRA_FIRMWARE can cause nconf to segfault when you overflow
> its length of 256 by trying to include a bunch of firmware *bin files:
> http://lkml.org/lkml/2011/8/29/86
If you are going to build the ucode into your kernel you'll need to
pick the ones you want to include or increase the limit regardless of
whether it's radeon ucode or ucode for some other chip. For a
particular card you only need the ones for that card (e.g.,
CEDAR_*.bin or REDWOOD_*.bin, etc.)
Alex
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 13:48 ` Alex Deucher
@ 2011-08-29 14:16 ` Borislav Petkov
2011-08-29 15:47 ` David Airlie
2011-08-29 16:28 ` Kyle Moffett
1 sibling, 1 reply; 37+ messages in thread
From: Borislav Petkov @ 2011-08-29 14:16 UTC (permalink / raw)
To: Alex Deucher, Dave Airlie
Cc: Peter Zijlstra, Pavel Ivanov, Michel Dänzer, dri-devel,
linux-kernel
On Mon, Aug 29, 2011 at 09:48:22AM -0400, Alex Deucher wrote:
> >> Should we make Kconfig pop up a dialog and ask for the whereabouts of
> >> these firmware thingies when you mark the driver =y?
> >>
> >> This all sounds like magic to me, having to know you need to add to
> >> EXTRA_FIRMWARE, having to know what file it needs etc.. For all intents
> >> and purposes =y just doesn't work and that's broken.
> >
> > Yep, you make a lot of sense. I had to fumble the build/reboot cycle a
> > couple of times and do some code staring even to figure this out. In
> > the end, I copied the whole radeon/ folder from David's firmware git
> > repo into /lib/firmware and made radeon.ko =m again so that I don't have
> > to add *.bin entries to CONFIG_EXTRA_FIRMWARE each time I'm building a
> > kernel on a different machine.
> >
> > Besides, there was this other issue on lkml today where
> > CONFIG_EXTRA_FIRMWARE can cause nconf to segfault when you overflow
> > its length of 256 by trying to include a bunch of firmware *bin files:
> > http://lkml.org/lkml/2011/8/29/86
>
> If you are going to build the ucode into your kernel you'll need to
> pick the ones you want to include or increase the limit regardless of
> whether it's radeon ucode or ucode for some other chip. For a
> particular card you only need the ones for that card (e.g.,
> CEDAR_*.bin or REDWOOD_*.bin, etc.)
Alex, Dave, yeah, that's all fine.
The question Peter asked is, how to make this much more understandable
to the user so that she/he doesn't have to figure it out on their own.
IOW, if one sets RADEON to =y in Kconfig, it should automatically
generate a selection menu with all the firmware required so that
the user can select from it either the CEDAR* or the REDWOOD* (or
the DOUGHNUT* :-)) ones for her/his card and when the user selects
one entry, the required strings are added to CONFIG_EXTRA_FIRMWARE
_automatically_.
Maybe even Kbuild should try to find them on the system, and, if unable
to, remind the user to install the needed firmware package.
Anyway, something to that effect, the above is just to illustrate the
intention, I don't know whether it would work. In any case, we're
lacking user help there and we don't want to put every user through
the process of finding which firmware files she/he needs when setting
RADEON=y.
Does that make more sense?
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 14:16 ` Borislav Petkov
@ 2011-08-29 15:47 ` David Airlie
2011-08-29 15:55 ` Borislav Petkov
0 siblings, 1 reply; 37+ messages in thread
From: David Airlie @ 2011-08-29 15:47 UTC (permalink / raw)
To: Borislav Petkov
Cc: Peter Zijlstra, Michel Dänzer, linux-kernel, dri-devel,
Pavel Ivanov, Alex Deucher, Dave Airlie
----- Original Message -----
> From: "Borislav Petkov" <bp@alien8.de>
> To: "Alex Deucher" <alexdeucher@gmail.com>, "Dave Airlie" <airlied@gmail.com>
> Cc: "Peter Zijlstra" <peterz@infradead.org>, "Michel Dänzer" <michel@daenzer.net>, "linux-kernel"
> <linux-kernel@vger.kernel.org>, dri-devel@lists.freedesktop.org, "Pavel Ivanov" <paivanof@gmail.com>
> Sent: Monday, 29 August, 2011 3:16:12 PM
> Subject: Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
> On Mon, Aug 29, 2011 at 09:48:22AM -0400, Alex Deucher wrote:
> > >> Should we make Kconfig pop up a dialog and ask for the
> > >> whereabouts of
> > >> these firmware thingies when you mark the driver =y?
> > >>
> > >> This all sounds like magic to me, having to know you need to add
> > >> to
> > >> EXTRA_FIRMWARE, having to know what file it needs etc.. For all
> > >> intents
> > >> and purposes =y just doesn't work and that's broken.
> > >
> > > Yep, you make a lot of sense. I had to fumble the build/reboot
> > > cycle a
> > > couple of times and do some code staring even to figure this out.
> > > In
> > > the end, I copied the whole radeon/ folder from David's firmware
> > > git
> > > repo into /lib/firmware and made radeon.ko =m again so that I
> > > don't have
> > > to add *.bin entries to CONFIG_EXTRA_FIRMWARE each time I'm
> > > building a
> > > kernel on a different machine.
> > >
> > > Besides, there was this other issue on lkml today where
> > > CONFIG_EXTRA_FIRMWARE can cause nconf to segfault when you
> > > overflow
> > > its length of 256 by trying to include a bunch of firmware *bin
> > > files:
> > > http://lkml.org/lkml/2011/8/29/86
> >
> > If you are going to build the ucode into your kernel you'll need to
> > pick the ones you want to include or increase the limit regardless
> > of
> > whether it's radeon ucode or ucode for some other chip. For a
> > particular card you only need the ones for that card (e.g.,
> > CEDAR_*.bin or REDWOOD_*.bin, etc.)
>
> Alex, Dave, yeah, that's all fine.
>
> The question Peter asked is, how to make this much more understandable
> to the user so that she/he doesn't have to figure it out on their own.
> IOW, if one sets RADEON to =y in Kconfig, it should automatically
> generate a selection menu with all the firmware required so that
> the user can select from it either the CEDAR* or the REDWOOD* (or
> the DOUGHNUT* :-)) ones for her/his card and when the user selects
> one entry, the required strings are added to CONFIG_EXTRA_FIRMWARE
> _automatically_.
>
> Maybe even Kbuild should try to find them on the system, and, if
> unable
> to, remind the user to install the needed firmware package.
>
> Anyway, something to that effect, the above is just to illustrate the
> intention, I don't know whether it would work. In any case, we're
> lacking user help there and we don't want to put every user through
> the process of finding which firmware files she/he needs when setting
> RADEON=y.
>
> Does that make more sense?
Oh it makes sense, just neither of us are Kbuild hackers and I'm not sure that'll change at any point :)
It also sounds like something that could apply to any driver with external firmware.
Dave.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 15:47 ` David Airlie
@ 2011-08-29 15:55 ` Borislav Petkov
2011-08-29 16:10 ` Arnaud Lacombe
0 siblings, 1 reply; 37+ messages in thread
From: Borislav Petkov @ 2011-08-29 15:55 UTC (permalink / raw)
To: David Airlie
Cc: Peter Zijlstra, Michel Dänzer, linux-kernel, dri-devel,
Pavel Ivanov, Alex Deucher, Dave Airlie, linux-kbuild
On Mon, Aug 29, 2011 at 11:47:24AM -0400, David Airlie wrote:
> > On Mon, Aug 29, 2011 at 09:48:22AM -0400, Alex Deucher wrote:
> > > >> Should we make Kconfig pop up a dialog and ask for the
> > > >> whereabouts of
> > > >> these firmware thingies when you mark the driver =y?
> > > >>
> > > >> This all sounds like magic to me, having to know you need to add
> > > >> to
> > > >> EXTRA_FIRMWARE, having to know what file it needs etc.. For all
> > > >> intents
> > > >> and purposes =y just doesn't work and that's broken.
> > > >
> > > > Yep, you make a lot of sense. I had to fumble the build/reboot
> > > > cycle a
> > > > couple of times and do some code staring even to figure this out.
> > > > In
> > > > the end, I copied the whole radeon/ folder from David's firmware
> > > > git
> > > > repo into /lib/firmware and made radeon.ko =m again so that I
> > > > don't have
> > > > to add *.bin entries to CONFIG_EXTRA_FIRMWARE each time I'm
> > > > building a
> > > > kernel on a different machine.
> > > >
> > > > Besides, there was this other issue on lkml today where
> > > > CONFIG_EXTRA_FIRMWARE can cause nconf to segfault when you
> > > > overflow
> > > > its length of 256 by trying to include a bunch of firmware *bin
> > > > files:
> > > > http://lkml.org/lkml/2011/8/29/86
> > >
> > > If you are going to build the ucode into your kernel you'll need to
> > > pick the ones you want to include or increase the limit regardless
> > > of
> > > whether it's radeon ucode or ucode for some other chip. For a
> > > particular card you only need the ones for that card (e.g.,
> > > CEDAR_*.bin or REDWOOD_*.bin, etc.)
> >
> > Alex, Dave, yeah, that's all fine.
> >
> > The question Peter asked is, how to make this much more understandable
> > to the user so that she/he doesn't have to figure it out on their own.
> > IOW, if one sets RADEON to =y in Kconfig, it should automatically
> > generate a selection menu with all the firmware required so that
> > the user can select from it either the CEDAR* or the REDWOOD* (or
> > the DOUGHNUT* :-)) ones for her/his card and when the user selects
> > one entry, the required strings are added to CONFIG_EXTRA_FIRMWARE
> > _automatically_.
> >
> > Maybe even Kbuild should try to find them on the system, and, if
> > unable
> > to, remind the user to install the needed firmware package.
> >
> > Anyway, something to that effect, the above is just to illustrate the
> > intention, I don't know whether it would work. In any case, we're
> > lacking user help there and we don't want to put every user through
> > the process of finding which firmware files she/he needs when setting
> > RADEON=y.
> >
> > Does that make more sense?
>
> Oh it makes sense, just neither of us are Kbuild hackers and I'm not sure that'll change at any point :)
>
> It also sounds like something that could apply to any driver with external firmware.
So it seems like all the request_firmware() drivers could use a Kbuild
functionality of some sort which presents the user with an option to
select the firmware blobs for his hw when those drivers are =y. Hairy.
Adding kbuild ML.
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 15:55 ` Borislav Petkov
@ 2011-08-29 16:10 ` Arnaud Lacombe
0 siblings, 0 replies; 37+ messages in thread
From: Arnaud Lacombe @ 2011-08-29 16:10 UTC (permalink / raw)
To: Borislav Petkov
Cc: David Airlie, Peter Zijlstra, Michel Dänzer, linux-kernel,
dri-devel, Pavel Ivanov, Alex Deucher, Dave Airlie, linux-kbuild
Hi,
On Mon, Aug 29, 2011 at 11:55 AM, Borislav Petkov <bp@alien8.de> wrote:
> On Mon, Aug 29, 2011 at 11:47:24AM -0400, David Airlie wrote:
>> > On Mon, Aug 29, 2011 at 09:48:22AM -0400, Alex Deucher wrote:
>> > > >> Should we make Kconfig pop up a dialog and ask for the
>> > > >> whereabouts of
>> > > >> these firmware thingies when you mark the driver =y?
>> > > >>
>> > > >> This all sounds like magic to me, having to know you need to add
>> > > >> to
>> > > >> EXTRA_FIRMWARE, having to know what file it needs etc.. For all
>> > > >> intents
>> > > >> and purposes =y just doesn't work and that's broken.
>> > > >
>> > > > Yep, you make a lot of sense. I had to fumble the build/reboot
>> > > > cycle a
>> > > > couple of times and do some code staring even to figure this out.
>> > > > In
>> > > > the end, I copied the whole radeon/ folder from David's firmware
>> > > > git
>> > > > repo into /lib/firmware and made radeon.ko =m again so that I
>> > > > don't have
>> > > > to add *.bin entries to CONFIG_EXTRA_FIRMWARE each time I'm
>> > > > building a
>> > > > kernel on a different machine.
>> > > >
>> > > > Besides, there was this other issue on lkml today where
>> > > > CONFIG_EXTRA_FIRMWARE can cause nconf to segfault when you
>> > > > overflow
>> > > > its length of 256 by trying to include a bunch of firmware *bin
>> > > > files:
>> > > > http://lkml.org/lkml/2011/8/29/86
>> > >
>> > > If you are going to build the ucode into your kernel you'll need to
>> > > pick the ones you want to include or increase the limit regardless
>> > > of
>> > > whether it's radeon ucode or ucode for some other chip. For a
>> > > particular card you only need the ones for that card (e.g.,
>> > > CEDAR_*.bin or REDWOOD_*.bin, etc.)
>> >
>> > Alex, Dave, yeah, that's all fine.
>> >
>> > The question Peter asked is, how to make this much more understandable
>> > to the user so that she/he doesn't have to figure it out on their own.
>> > IOW, if one sets RADEON to =y in Kconfig, it should automatically
>> > generate a selection menu with all the firmware required so that
>> > the user can select from it either the CEDAR* or the REDWOOD* (or
>> > the DOUGHNUT* :-)) ones for her/his card and when the user selects
>> > one entry, the required strings are added to CONFIG_EXTRA_FIRMWARE
>> > _automatically_.
>> >
>> > Maybe even Kbuild should try to find them on the system, and, if
>> > unable
>> > to, remind the user to install the needed firmware package.
>> >
>> > Anyway, something to that effect, the above is just to illustrate the
>> > intention, I don't know whether it would work. In any case, we're
>> > lacking user help there and we don't want to put every user through
>> > the process of finding which firmware files she/he needs when setting
>> > RADEON=y.
>> >
>> > Does that make more sense?
>>
>> Oh it makes sense, just neither of us are Kbuild hackers and I'm not sure that'll change at any point :)
>>
>> It also sounds like something that could apply to any driver with external firmware.
>
> So it seems like all the request_firmware() drivers could use a Kbuild
> functionality of some sort which presents the user with an option to
> select the firmware blobs for his hw when those drivers are =y. Hairy.
>
> Adding kbuild ML.
>
do you want something ala:
config EXTRA_FIRMWARE
string
default ""
append "FOO" if BAR
append "FOZ" if BAZ
or maybe a new type "list" which would behave as a comma/space separated value.
config EXTRA_FIRMWARE
list "bla"
append "FOO" if BAR
append "FOZ" if BAZ
?
Thanks,
- Arnaud
> --
> Regards/Gruss,
> Boris.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
@ 2011-08-29 16:10 ` Arnaud Lacombe
0 siblings, 0 replies; 37+ messages in thread
From: Arnaud Lacombe @ 2011-08-29 16:10 UTC (permalink / raw)
To: Borislav Petkov
Cc: David Airlie, Peter Zijlstra, Michel Dänzer, linux-kernel,
dri-devel, Pavel Ivanov, Alex Deucher, Dave Airlie, linux-kbuild
Hi,
On Mon, Aug 29, 2011 at 11:55 AM, Borislav Petkov <bp@alien8.de> wrote:
> On Mon, Aug 29, 2011 at 11:47:24AM -0400, David Airlie wrote:
>> > On Mon, Aug 29, 2011 at 09:48:22AM -0400, Alex Deucher wrote:
>> > > >> Should we make Kconfig pop up a dialog and ask for the
>> > > >> whereabouts of
>> > > >> these firmware thingies when you mark the driver =y?
>> > > >>
>> > > >> This all sounds like magic to me, having to know you need to add
>> > > >> to
>> > > >> EXTRA_FIRMWARE, having to know what file it needs etc.. For all
>> > > >> intents
>> > > >> and purposes =y just doesn't work and that's broken.
>> > > >
>> > > > Yep, you make a lot of sense. I had to fumble the build/reboot
>> > > > cycle a
>> > > > couple of times and do some code staring even to figure this out.
>> > > > In
>> > > > the end, I copied the whole radeon/ folder from David's firmware
>> > > > git
>> > > > repo into /lib/firmware and made radeon.ko =m again so that I
>> > > > don't have
>> > > > to add *.bin entries to CONFIG_EXTRA_FIRMWARE each time I'm
>> > > > building a
>> > > > kernel on a different machine.
>> > > >
>> > > > Besides, there was this other issue on lkml today where
>> > > > CONFIG_EXTRA_FIRMWARE can cause nconf to segfault when you
>> > > > overflow
>> > > > its length of 256 by trying to include a bunch of firmware *bin
>> > > > files:
>> > > > http://lkml.org/lkml/2011/8/29/86
>> > >
>> > > If you are going to build the ucode into your kernel you'll need to
>> > > pick the ones you want to include or increase the limit regardless
>> > > of
>> > > whether it's radeon ucode or ucode for some other chip. For a
>> > > particular card you only need the ones for that card (e.g.,
>> > > CEDAR_*.bin or REDWOOD_*.bin, etc.)
>> >
>> > Alex, Dave, yeah, that's all fine.
>> >
>> > The question Peter asked is, how to make this much more understandable
>> > to the user so that she/he doesn't have to figure it out on their own.
>> > IOW, if one sets RADEON to =y in Kconfig, it should automatically
>> > generate a selection menu with all the firmware required so that
>> > the user can select from it either the CEDAR* or the REDWOOD* (or
>> > the DOUGHNUT* :-)) ones for her/his card and when the user selects
>> > one entry, the required strings are added to CONFIG_EXTRA_FIRMWARE
>> > _automatically_.
>> >
>> > Maybe even Kbuild should try to find them on the system, and, if
>> > unable
>> > to, remind the user to install the needed firmware package.
>> >
>> > Anyway, something to that effect, the above is just to illustrate the
>> > intention, I don't know whether it would work. In any case, we're
>> > lacking user help there and we don't want to put every user through
>> > the process of finding which firmware files she/he needs when setting
>> > RADEON=y.
>> >
>> > Does that make more sense?
>>
>> Oh it makes sense, just neither of us are Kbuild hackers and I'm not sure that'll change at any point :)
>>
>> It also sounds like something that could apply to any driver with external firmware.
>
> So it seems like all the request_firmware() drivers could use a Kbuild
> functionality of some sort which presents the user with an option to
> select the firmware blobs for his hw when those drivers are =y. Hairy.
>
> Adding kbuild ML.
>
do you want something ala:
config EXTRA_FIRMWARE
string
default ""
append "FOO" if BAR
append "FOZ" if BAZ
or maybe a new type "list" which would behave as a comma/space separated value.
config EXTRA_FIRMWARE
list "bla"
append "FOO" if BAR
append "FOZ" if BAZ
?
Thanks,
- Arnaud
> --
> Regards/Gruss,
> Boris.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 16:10 ` Arnaud Lacombe
(?)
@ 2011-08-29 17:17 ` Borislav Petkov
2011-08-29 17:38 ` Michel Dänzer
` (3 more replies)
-1 siblings, 4 replies; 37+ messages in thread
From: Borislav Petkov @ 2011-08-29 17:17 UTC (permalink / raw)
To: Arnaud Lacombe
Cc: David Airlie, Peter Zijlstra, Michel Dänzer, linux-kernel,
dri-devel, Pavel Ivanov, Alex Deucher, Dave Airlie, linux-kbuild
On Mon, Aug 29, 2011 at 12:10:45PM -0400, Arnaud Lacombe wrote:
> do you want something ala:
>
> config EXTRA_FIRMWARE
> string
> default ""
> append "FOO" if BAR
> append "FOZ" if BAZ
>
> or maybe a new type "list" which would behave as a comma/space separated value.
>
> config EXTRA_FIRMWARE
> list "bla"
> append "FOO" if BAR
> append "FOZ" if BAZ
Yeah, actually Kyle's note (http://lkml.org/lkml/2011/8/29/289) makes
much more sense for linux and the whole firmware in the kernel deal.
So it looks like the drivers should be taught to wait for userspace to
appear instead of Kconfig helping them build-in firmware. And then we
should go ahead and remove CONFIG_EXTRA_FIRMWARE completely...
Thanks.
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 17:17 ` Borislav Petkov
@ 2011-08-29 17:38 ` Michel Dänzer
2011-08-29 17:50 ` Peter Zijlstra
` (2 subsequent siblings)
3 siblings, 0 replies; 37+ messages in thread
From: Michel Dänzer @ 2011-08-29 17:38 UTC (permalink / raw)
To: Borislav Petkov
Cc: Arnaud Lacombe, David Airlie, Peter Zijlstra, linux-kernel,
dri-devel, Pavel Ivanov, Alex Deucher, Dave Airlie, linux-kbuild
On Mon, 2011-08-29 at 19:17 +0200, Borislav Petkov wrote:
> On Mon, Aug 29, 2011 at 12:10:45PM -0400, Arnaud Lacombe wrote:
> > do you want something ala:
> >
> > config EXTRA_FIRMWARE
> > string
> > default ""
> > append "FOO" if BAR
> > append "FOZ" if BAZ
> >
> > or maybe a new type "list" which would behave as a comma/space separated value.
> >
> > config EXTRA_FIRMWARE
> > list "bla"
> > append "FOO" if BAR
> > append "FOZ" if BAZ
>
> Yeah, actually Kyle's note (http://lkml.org/lkml/2011/8/29/289) makes
> much more sense for linux and the whole firmware in the kernel deal.
> So it looks like the drivers should be taught to wait for userspace to
> appear [...]
What would be the point of building radeon into the kernel then? It's
not gonna be active before the module could be loaded...
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
@ 2011-08-29 17:38 ` Michel Dänzer
0 siblings, 0 replies; 37+ messages in thread
From: Michel Dänzer @ 2011-08-29 17:38 UTC (permalink / raw)
To: Borislav Petkov
Cc: linux-kbuild, Peter Zijlstra, linux-kernel, dri-devel, Ivanov,
Dave, Arnaud Lacombe, Pavel, David Airlie
On Mon, 2011-08-29 at 19:17 +0200, Borislav Petkov wrote:
> On Mon, Aug 29, 2011 at 12:10:45PM -0400, Arnaud Lacombe wrote:
> > do you want something ala:
> >
> > config EXTRA_FIRMWARE
> > string
> > default ""
> > append "FOO" if BAR
> > append "FOZ" if BAZ
> >
> > or maybe a new type "list" which would behave as a comma/space separated value.
> >
> > config EXTRA_FIRMWARE
> > list "bla"
> > append "FOO" if BAR
> > append "FOZ" if BAZ
>
> Yeah, actually Kyle's note (http://lkml.org/lkml/2011/8/29/289) makes
> much more sense for linux and the whole firmware in the kernel deal.
> So it looks like the drivers should be taught to wait for userspace to
> appear [...]
What would be the point of building radeon into the kernel then? It's
not gonna be active before the module could be loaded...
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 17:17 ` Borislav Petkov
2011-08-29 17:38 ` Michel Dänzer
@ 2011-08-29 17:50 ` Peter Zijlstra
2011-08-29 18:09 ` Peter Zijlstra
2011-08-29 18:16 ` Peter Zijlstra
3 siblings, 0 replies; 37+ messages in thread
From: Peter Zijlstra @ 2011-08-29 17:50 UTC (permalink / raw)
To: Borislav Petkov
Cc: Arnaud Lacombe, David Airlie, Michel Dänzer, linux-kernel,
dri-devel, Pavel Ivanov, Alex Deucher, Dave Airlie, linux-kbuild
On Mon, 2011-08-29 at 19:17 +0200, Borislav Petkov wrote:
> On Mon, Aug 29, 2011 at 12:10:45PM -0400, Arnaud Lacombe wrote:
> > do you want something ala:
> >
> > config EXTRA_FIRMWARE
> > string
> > default ""
> > append "FOO" if BAR
> > append "FOZ" if BAZ
> >
> > or maybe a new type "list" which would behave as a comma/space separated value.
> >
> > config EXTRA_FIRMWARE
> > list "bla"
> > append "FOO" if BAR
> > append "FOZ" if BAZ
>
> Yeah, actually Kyle's note (http://lkml.org/lkml/2011/8/29/289) makes
> much more sense for linux and the whole firmware in the kernel deal.
> So it looks like the drivers should be taught to wait for userspace to
> appear instead of Kconfig helping them build-in firmware. And then we
> should go ahead and remove CONFIG_EXTRA_FIRMWARE completely...
That would suck, suppose this radeon thing is the only console you've
got (ppc64/sparc64 don't have text mode iirc) and userspace doesn't come
up?
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 17:17 ` Borislav Petkov
2011-08-29 17:38 ` Michel Dänzer
2011-08-29 17:50 ` Peter Zijlstra
@ 2011-08-29 18:09 ` Peter Zijlstra
2011-08-29 18:16 ` Peter Zijlstra
3 siblings, 0 replies; 37+ messages in thread
From: Peter Zijlstra @ 2011-08-29 18:09 UTC (permalink / raw)
To: Borislav Petkov
Cc: Arnaud Lacombe, David Airlie, Michel Dänzer, linux-kernel,
dri-devel, Pavel Ivanov, Alex Deucher, Dave Airlie, linux-kbuild
On Mon, 2011-08-29 at 19:50 +0200, Peter Zijlstra wrote:
> On Mon, 2011-08-29 at 19:17 +0200, Borislav Petkov wrote:
> > On Mon, Aug 29, 2011 at 12:10:45PM -0400, Arnaud Lacombe wrote:
> > > do you want something ala:
> > >
> > > config EXTRA_FIRMWARE
> > > string
> > > default ""
> > > append "FOO" if BAR
> > > append "FOZ" if BAZ
> > >
> > > or maybe a new type "list" which would behave as a comma/space separated value.
> > >
> > > config EXTRA_FIRMWARE
> > > list "bla"
> > > append "FOO" if BAR
> > > append "FOZ" if BAZ
> >
> > Yeah, actually Kyle's note (http://lkml.org/lkml/2011/8/29/289) makes
> > much more sense for linux and the whole firmware in the kernel deal.
> > So it looks like the drivers should be taught to wait for userspace to
> > appear instead of Kconfig helping them build-in firmware. And then we
> > should go ahead and remove CONFIG_EXTRA_FIRMWARE completely...
>
> That would suck, suppose this radeon thing is the only console you've
> got (ppc64/sparc64 don't have text mode iirc) and userspace doesn't come
> up?
Same is true for NICs and netconsole of course. Not being able to stick
blobs into the kernel image would so suck.
Silently building a kernel without one and then getting stuck on boot,
only to figure out after much pain that you need EXTRA_FIRMWARE and the
more pain to figure out what blob to stick in is beyond crazy.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 17:17 ` Borislav Petkov
` (2 preceding siblings ...)
2011-08-29 18:09 ` Peter Zijlstra
@ 2011-08-29 18:16 ` Peter Zijlstra
2011-08-29 21:14 ` Borislav Petkov
3 siblings, 1 reply; 37+ messages in thread
From: Peter Zijlstra @ 2011-08-29 18:16 UTC (permalink / raw)
To: Borislav Petkov
Cc: Arnaud Lacombe, David Airlie, Michel Dänzer, linux-kernel,
dri-devel, Pavel Ivanov, Alex Deucher, Dave Airlie, linux-kbuild
On Mon, 2011-08-29 at 20:09 +0200, Peter Zijlstra wrote:
> > That would suck, suppose this radeon thing is the only console you've
> > got (ppc64/sparc64 don't have text mode iirc) and userspace doesn't come
> > up?
>
> Same is true for NICs and netconsole of course. Not being able to stick
> blobs into the kernel image would so suck.
NICs and nfsroot, I suppose can you use an initrd over tftp as well, but
really, what's the point of an in-kernel nfsroot if you need initrd
crap.
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 18:16 ` Peter Zijlstra
@ 2011-08-29 21:14 ` Borislav Petkov
2011-08-30 2:08 ` Henrique de Moraes Holschuh
2011-08-30 2:08 ` Henrique de Moraes Holschuh
0 siblings, 2 replies; 37+ messages in thread
From: Borislav Petkov @ 2011-08-29 21:14 UTC (permalink / raw)
To: Peter Zijlstra
Cc: Arnaud Lacombe, David Airlie, Michel Dänzer, linux-kernel,
dri-devel, Pavel Ivanov, Alex Deucher, Dave Airlie, linux-kbuild
On Mon, Aug 29, 2011 at 08:16:53PM +0200, Peter Zijlstra wrote:
> On Mon, 2011-08-29 at 20:09 +0200, Peter Zijlstra wrote:
> > > That would suck, suppose this radeon thing is the only console you've
> > > got (ppc64/sparc64 don't have text mode iirc) and userspace doesn't come
> > > up?
> >
> > Same is true for NICs and netconsole of course. Not being able to stick
> > blobs into the kernel image would so suck.
>
> NICs and nfsroot, I suppose can you use an initrd over tftp as well, but
> really, what's the point of an in-kernel nfsroot if you need initrd
> crap.
Damn,
just when I thought that the lofty goal of Linux distancing itself from
firmware crap is within reach, you came up with all those real-life,
nagging examples.
So here's the whole deal IMHO:
* driver =m and request_firmware() works fine - you only need the blobs
in the right place.
* driver =y and request_firmware() should be fixed in all cases where
driver can wait.
Your use cases could probably be addressed by supplying firmware blobs
from the bootloader. We had this talk already concerning CPU microcode
updates and how the current method is to load CPU ucode when the module
gets loaded, which might be too late for some obscure (and not so
obscure) cases.
So, hypothetically speaking, hpa suggested then that we could pass
firmware blobs over the linked list setup_data thing in the real-mode
kernel header and parse_setup_data() can look at them and map them
somewhere later for the driver to find. This should be doable because
you're only gonna need a handful of blobs for CPU ucode, network and GPU
if the last is compiled in.
I wanted to take a serious look at that for the ucode loading, maybe I
should try to shuffle some time for it...
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 21:14 ` Borislav Petkov
@ 2011-08-30 2:08 ` Henrique de Moraes Holschuh
2011-08-30 2:08 ` Henrique de Moraes Holschuh
1 sibling, 0 replies; 37+ messages in thread
From: Henrique de Moraes Holschuh @ 2011-08-30 2:08 UTC (permalink / raw)
To: Borislav Petkov, Peter Zijlstra, Arnaud Lacombe, David Airlie
On Mon, 29 Aug 2011, Borislav Petkov wrote:
> So, hypothetically speaking, hpa suggested then that we could pass
> firmware blobs over the linked list setup_data thing in the real-mode
> kernel header and parse_setup_data() can look at them and map them
> somewhere later for the driver to find. This should be doable because
> you're only gonna need a handful of blobs for CPU ucode, network and GPU
> if the last is compiled in.
>
> I wanted to take a serious look at that for the ucode loading, maybe I
> should try to shuffle some time for it...
It would be very useful, yes.
Alternatively, you could extend the initrd format to have a firmware
directory appended after the filesystem image. ACPI is going to abuse
the initrd in just that way to override ACPI tables very soon (patches
have been already submitted to linux-acpi), so if a more structured and
extensible way to piggy-back early-init data in the initrd is needed, it
would be good to bring that to the table NOW.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 21:14 ` Borislav Petkov
2011-08-30 2:08 ` Henrique de Moraes Holschuh
@ 2011-08-30 2:08 ` Henrique de Moraes Holschuh
2011-08-30 7:17 ` Borislav Petkov
2011-08-30 8:37 ` Peter Zijlstra
1 sibling, 2 replies; 37+ messages in thread
From: Henrique de Moraes Holschuh @ 2011-08-30 2:08 UTC (permalink / raw)
To: Borislav Petkov, Peter Zijlstra, Arnaud Lacombe, David Airlie,
Michel Dänzer, linux-kernel, dri-devel, Pavel Ivanov,
Alex Deucher, Dave Airlie, linux-kbuild
On Mon, 29 Aug 2011, Borislav Petkov wrote:
> So, hypothetically speaking, hpa suggested then that we could pass
> firmware blobs over the linked list setup_data thing in the real-mode
> kernel header and parse_setup_data() can look at them and map them
> somewhere later for the driver to find. This should be doable because
> you're only gonna need a handful of blobs for CPU ucode, network and GPU
> if the last is compiled in.
>
> I wanted to take a serious look at that for the ucode loading, maybe I
> should try to shuffle some time for it...
It would be very useful, yes.
Alternatively, you could extend the initrd format to have a firmware
directory appended after the filesystem image. ACPI is going to abuse
the initrd in just that way to override ACPI tables very soon (patches
have been already submitted to linux-acpi), so if a more structured and
extensible way to piggy-back early-init data in the initrd is needed, it
would be good to bring that to the table NOW.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-30 2:08 ` Henrique de Moraes Holschuh
@ 2011-08-30 7:17 ` Borislav Petkov
2011-08-30 8:37 ` Peter Zijlstra
1 sibling, 0 replies; 37+ messages in thread
From: Borislav Petkov @ 2011-08-30 7:17 UTC (permalink / raw)
To: Henrique de Moraes Holschuh
Cc: Peter Zijlstra, Arnaud Lacombe, David Airlie, Michel Dänzer,
linux-kernel, dri-devel, Pavel Ivanov, Alex Deucher, Dave Airlie,
linux-kbuild
On Mon, Aug 29, 2011 at 11:08:28PM -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 29 Aug 2011, Borislav Petkov wrote:
> > So, hypothetically speaking, hpa suggested then that we could pass
> > firmware blobs over the linked list setup_data thing in the real-mode
> > kernel header and parse_setup_data() can look at them and map them
> > somewhere later for the driver to find. This should be doable because
> > you're only gonna need a handful of blobs for CPU ucode, network and GPU
> > if the last is compiled in.
> >
> > I wanted to take a serious look at that for the ucode loading, maybe I
> > should try to shuffle some time for it...
>
> It would be very useful, yes.
>
> Alternatively, you could extend the initrd format to have a firmware
> directory appended after the filesystem image. ACPI is going to abuse
> the initrd in just that way to override ACPI tables very soon (patches
> have been already submitted to linux-acpi),
.. lemme guess: they didn't put the correct tables in the BIOS in the
first place and now it is too late for a BIOS fix and want to shuffle in
all those "fixes" through initrd ontop of ACPI. Oh boy, do I love all
the ACPI crap stories :).
> so if a more structured and extensible way to piggy-back early-init
> data in the initrd is needed, it would be good to bring that to the
> table NOW.
Yeah, that's not more than an idea right now, I haven't even started
playing with it. If it turns out to be more superior, it could be reused
for other things too but right now it's too early to tell.
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
@ 2011-08-30 7:17 ` Borislav Petkov
0 siblings, 0 replies; 37+ messages in thread
From: Borislav Petkov @ 2011-08-30 7:17 UTC (permalink / raw)
To: Henrique de Moraes Holschuh
Cc: linux-kbuild, Peter Zijlstra, Michel Dänzer, linux-kernel,
dri-devel, Pavel Ivanov, Arnaud Lacombe, David Airlie
On Mon, Aug 29, 2011 at 11:08:28PM -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 29 Aug 2011, Borislav Petkov wrote:
> > So, hypothetically speaking, hpa suggested then that we could pass
> > firmware blobs over the linked list setup_data thing in the real-mode
> > kernel header and parse_setup_data() can look at them and map them
> > somewhere later for the driver to find. This should be doable because
> > you're only gonna need a handful of blobs for CPU ucode, network and GPU
> > if the last is compiled in.
> >
> > I wanted to take a serious look at that for the ucode loading, maybe I
> > should try to shuffle some time for it...
>
> It would be very useful, yes.
>
> Alternatively, you could extend the initrd format to have a firmware
> directory appended after the filesystem image. ACPI is going to abuse
> the initrd in just that way to override ACPI tables very soon (patches
> have been already submitted to linux-acpi),
.. lemme guess: they didn't put the correct tables in the BIOS in the
first place and now it is too late for a BIOS fix and want to shuffle in
all those "fixes" through initrd ontop of ACPI. Oh boy, do I love all
the ACPI crap stories :).
> so if a more structured and extensible way to piggy-back early-init
> data in the initrd is needed, it would be good to bring that to the
> table NOW.
Yeah, that's not more than an idea right now, I haven't even started
playing with it. If it turns out to be more superior, it could be reused
for other things too but right now it's too early to tell.
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-30 7:17 ` Borislav Petkov
(?)
@ 2011-08-30 14:44 ` Henrique de Moraes Holschuh
-1 siblings, 0 replies; 37+ messages in thread
From: Henrique de Moraes Holschuh @ 2011-08-30 14:44 UTC (permalink / raw)
To: Borislav Petkov, Peter Zijlstra, Arnaud Lacombe, David Airlie
On Tue, 30 Aug 2011, Borislav Petkov wrote:
> On Mon, Aug 29, 2011 at 11:08:28PM -0300, Henrique de Moraes Holschuh wrote:
> > On Mon, 29 Aug 2011, Borislav Petkov wrote:
> > > So, hypothetically speaking, hpa suggested then that we could pass
> > > firmware blobs over the linked list setup_data thing in the real-mode
> > > kernel header and parse_setup_data() can look at them and map them
> > > somewhere later for the driver to find. This should be doable because
> > > you're only gonna need a handful of blobs for CPU ucode, network and GPU
> > > if the last is compiled in.
> > >
> > > I wanted to take a serious look at that for the ucode loading, maybe I
> > > should try to shuffle some time for it...
> >
> > It would be very useful, yes.
> >
> > Alternatively, you could extend the initrd format to have a firmware
> > directory appended after the filesystem image. ACPI is going to abuse
> > the initrd in just that way to override ACPI tables very soon (patches
> > have been already submitted to linux-acpi),
>
> .. lemme guess: they didn't put the correct tables in the BIOS in the
> first place and now it is too late for a BIOS fix and want to shuffle in
> all those "fixes" through initrd ontop of ACPI. Oh boy, do I love all
> the ACPI crap stories :).
Heh.
Actually, the patches were created by a distro for debug purposes. No
vendor pushed for them. But it is a safe bet that users will end up using
them to work around ACPI vendor crap that will never get fixed properly
through a BIOS update, etc.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-30 7:17 ` Borislav Petkov
(?)
(?)
@ 2011-08-30 14:44 ` Henrique de Moraes Holschuh
-1 siblings, 0 replies; 37+ messages in thread
From: Henrique de Moraes Holschuh @ 2011-08-30 14:44 UTC (permalink / raw)
To: Borislav Petkov, Peter Zijlstra, Arnaud Lacombe, David Airlie,
Michel Dänzer, linux-kernel, dri-devel, Pavel Ivanov,
Alex Deucher, Dave Airlie, linux-kbuild
On Tue, 30 Aug 2011, Borislav Petkov wrote:
> On Mon, Aug 29, 2011 at 11:08:28PM -0300, Henrique de Moraes Holschuh wrote:
> > On Mon, 29 Aug 2011, Borislav Petkov wrote:
> > > So, hypothetically speaking, hpa suggested then that we could pass
> > > firmware blobs over the linked list setup_data thing in the real-mode
> > > kernel header and parse_setup_data() can look at them and map them
> > > somewhere later for the driver to find. This should be doable because
> > > you're only gonna need a handful of blobs for CPU ucode, network and GPU
> > > if the last is compiled in.
> > >
> > > I wanted to take a serious look at that for the ucode loading, maybe I
> > > should try to shuffle some time for it...
> >
> > It would be very useful, yes.
> >
> > Alternatively, you could extend the initrd format to have a firmware
> > directory appended after the filesystem image. ACPI is going to abuse
> > the initrd in just that way to override ACPI tables very soon (patches
> > have been already submitted to linux-acpi),
>
> .. lemme guess: they didn't put the correct tables in the BIOS in the
> first place and now it is too late for a BIOS fix and want to shuffle in
> all those "fixes" through initrd ontop of ACPI. Oh boy, do I love all
> the ACPI crap stories :).
Heh.
Actually, the patches were created by a distro for debug purposes. No
vendor pushed for them. But it is a safe bet that users will end up using
them to work around ACPI vendor crap that will never get fixed properly
through a BIOS update, etc.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-30 2:08 ` Henrique de Moraes Holschuh
2011-08-30 7:17 ` Borislav Petkov
@ 2011-08-30 8:37 ` Peter Zijlstra
2011-08-30 14:55 ` Henrique de Moraes Holschuh
1 sibling, 1 reply; 37+ messages in thread
From: Peter Zijlstra @ 2011-08-30 8:37 UTC (permalink / raw)
To: Henrique de Moraes Holschuh
Cc: Borislav Petkov, Arnaud Lacombe, David Airlie,
Michel Dänzer, linux-kernel, dri-devel, Pavel Ivanov,
Alex Deucher, Dave Airlie, linux-kbuild
On Mon, 2011-08-29 at 23:08 -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 29 Aug 2011, Borislav Petkov wrote:
> > So, hypothetically speaking, hpa suggested then that we could pass
> > firmware blobs over the linked list setup_data thing in the real-mode
> > kernel header and parse_setup_data() can look at them and map them
> > somewhere later for the driver to find. This should be doable because
> > you're only gonna need a handful of blobs for CPU ucode, network and GPU
> > if the last is compiled in.
> >
> > I wanted to take a serious look at that for the ucode loading, maybe I
> > should try to shuffle some time for it...
>
> It would be very useful, yes.
>
> Alternatively, you could extend the initrd format to have a firmware
> directory appended after the filesystem image. ACPI is going to abuse
> the initrd in just that way to override ACPI tables very soon (patches
> have been already submitted to linux-acpi), so if a more structured and
> extensible way to piggy-back early-init data in the initrd is needed, it
> would be good to bring that to the table NOW.
Uhm,.. does that mean that soon we can't boot kernels without initrd?
That too is a massive regression in my eyes.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-30 8:37 ` Peter Zijlstra
@ 2011-08-30 14:55 ` Henrique de Moraes Holschuh
0 siblings, 0 replies; 37+ messages in thread
From: Henrique de Moraes Holschuh @ 2011-08-30 14:55 UTC (permalink / raw)
To: Peter Zijlstra
Cc: Borislav Petkov, Arnaud Lacombe, David Airlie,
Michel Dänzer, linux-kernel, dri-devel, Pavel Ivanov,
Alex Deucher, Dave Airlie, linux-kbuild
On Tue, 30 Aug 2011, Peter Zijlstra wrote:
> On Mon, 2011-08-29 at 23:08 -0300, Henrique de Moraes Holschuh wrote:
> > On Mon, 29 Aug 2011, Borislav Petkov wrote:
> > > So, hypothetically speaking, hpa suggested then that we could pass
> > > firmware blobs over the linked list setup_data thing in the real-mode
> > > kernel header and parse_setup_data() can look at them and map them
> > > somewhere later for the driver to find. This should be doable because
> > > you're only gonna need a handful of blobs for CPU ucode, network and GPU
> > > if the last is compiled in.
> > >
> > > I wanted to take a serious look at that for the ucode loading, maybe I
> > > should try to shuffle some time for it...
> >
> > It would be very useful, yes.
> >
> > Alternatively, you could extend the initrd format to have a firmware
> > directory appended after the filesystem image. ACPI is going to abuse
> > the initrd in just that way to override ACPI tables very soon (patches
> > have been already submitted to linux-acpi), so if a more structured and
> > extensible way to piggy-back early-init data in the initrd is needed, it
> > would be good to bring that to the table NOW.
>
> Uhm,.. does that mean that soon we can't boot kernels without initrd?
> That too is a massive regression in my eyes.
Well, if work starts soon enough on a bootloader extension to avoid messing
with the initrd, we could refuse to set that initrd-based ACPI table
override as ABI on the grounds that it is a debug thing, and later move it
to the properly designed firmware bootloader extension.
Maybe the grub multiboot protocol[1] is worth looking at, assuming that
thing is salvagable and would actually work for both 32bit and 64bit BIOS
and UEFI bootstrapping?
[1]http://www.gnu.org/software/grub/manual/multiboot/multiboot.html
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 13:48 ` Alex Deucher
2011-08-29 14:16 ` Borislav Petkov
@ 2011-08-29 16:28 ` Kyle Moffett
2011-08-29 17:21 ` Borislav Petkov
1 sibling, 1 reply; 37+ messages in thread
From: Kyle Moffett @ 2011-08-29 16:28 UTC (permalink / raw)
To: Alex Deucher
Cc: Borislav Petkov, Peter Zijlstra, Pavel Ivanov,
Michel Dänzer, dri-devel, linux-kernel
On Mon, Aug 29, 2011 at 09:48, Alex Deucher <alexdeucher@gmail.com> wrote:
> 2011/8/29 Borislav Petkov <bp@alien8.de>:
>> On Mon, Aug 29, 2011 at 03:20:21PM +0200, Peter Zijlstra wrote:
>>> On Sun, 2011-08-28 at 07:36 +0200, Borislav Petkov wrote:
>>> > > > With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
>>> > > > loaded from userspace, so it needs to be built into the kernel as well.
>>> > >
>>> > > How should I do that? I've tried to set all "m"s to "y" in .config and
>>> > > still saw this issue. Should I set some special parameter?
>>> >
>>> > You need to add "radeon/CEDAR_pfp.bin" to CONFIG_EXTRA_FIRMWARE when you
>>> > configure your kernel and enable CONFIG_FIRMWARE_IN_KERNEL.
>>> >
>>> > The radeon/CEDAR_pfp.bin file (+ leading directory, mind you) should
>>> > most probably be located in /lib/firmware or to whatever you have set
>>> > CONFIG_EXTRA_FIRMWARE_DIR so that Kbuild can find it (if not, you'll get
>>> > a warning at the end of the kernel build). This way, it works for both
>>> > radeon being =m and =y.
>>>
>>> Should we make Kconfig pop up a dialog and ask for the whereabouts of
>>> these firmware thingies when you mark the driver =y?
>>>
>>> This all sounds like magic to me, having to know you need to add to
>>> EXTRA_FIRMWARE, having to know what file it needs etc.. For all intents
>>> and purposes =y just doesn't work and that's broken.
>>
>> Yep, you make a lot of sense. I had to fumble the build/reboot cycle a
>> couple of times and do some code staring even to figure this out. In
>> the end, I copied the whole radeon/ folder from David's firmware git
>> repo into /lib/firmware and made radeon.ko =m again so that I don't have
>> to add *.bin entries to CONFIG_EXTRA_FIRMWARE each time I'm building a
>> kernel on a different machine.
>>
>> Besides, there was this other issue on lkml today where
>> CONFIG_EXTRA_FIRMWARE can cause nconf to segfault when you overflow
>> its length of 256 by trying to include a bunch of firmware *bin files:
>> http://lkml.org/lkml/2011/8/29/86
>
> If you are going to build the ucode into your kernel you'll need to
> pick the ones you want to include or increase the limit regardless of
> whether it's radeon ucode or ucode for some other chip. For a
> particular card you only need the ones for that card (e.g.,
> CEDAR_*.bin or REDWOOD_*.bin, etc.)
No, Linus pushed back really hard last time this issue came up with
something; a network driver if I recall correctly.
The issue is that this happens *EVEN FOR MODULAR DRIVERS* during
suspend/resume. The firmware simply may not be available yet.
If the driver fundamentally cannot work without the firmware then it should
bind to the device and wait until the first userspace action before requesting
firmware.
Furthermore, the trend is generally to push the firmware OUT of the kernel
binary to avoid any chance of license issues. Even if the code is built-in
it should not need built-in firmware.
The quickest fix is probably something like this:
config DRM_RADEON_FIRMWARE
tristate
default m if STANDALONE
default y
config DRM_RADEON
depends DRM_RADEON_FIRMWARE
That should prevent somebody from building the radeon driver into the
kernel unless they manually indicate that they have the extra firmware.
Long-term, the driver should support modular firmware even when it's
built-in to the kernel.
Cheers,
Kyle Moffett
^ permalink raw reply [flat|nested] 37+ messages in thread* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 16:28 ` Kyle Moffett
@ 2011-08-29 17:21 ` Borislav Petkov
2011-08-29 17:51 ` Peter Zijlstra
0 siblings, 1 reply; 37+ messages in thread
From: Borislav Petkov @ 2011-08-29 17:21 UTC (permalink / raw)
To: Kyle Moffett
Cc: Alex Deucher, Borislav Petkov, Peter Zijlstra, Pavel Ivanov,
Michel Dänzer, dri-devel, linux-kernel
On Mon, Aug 29, 2011 at 12:28:31PM -0400, Kyle Moffett wrote:
> No, Linus pushed back really hard last time this issue came up with
> something; a network driver if I recall correctly.
r8169 probably.
> The issue is that this happens *EVEN FOR MODULAR DRIVERS* during
> suspend/resume. The firmware simply may not be available yet.
>
> If the driver fundamentally cannot work without the firmware then it should
> bind to the device and wait until the first userspace action before requesting
> firmware.
>
> Furthermore, the trend is generally to push the firmware OUT of the kernel
> binary to avoid any chance of license issues. Even if the code is built-in
> it should not need built-in firmware.
>
> The quickest fix is probably something like this:
>
> config DRM_RADEON_FIRMWARE
> tristate
> default m if STANDALONE
> default y
>
> config DRM_RADEON
> depends DRM_RADEON_FIRMWARE
>
> That should prevent somebody from building the radeon driver into the
> kernel unless they manually indicate that they have the extra firmware.
>
> Long-term, the driver should support modular firmware even when it's
> built-in to the kernel.
Yep, and drivers should be able to select the firmware they need without
users even needing to do anything about it except installing some
firmware-nonfree package or whatever.
Yeah, sounds much better than Kconfig actually aiding and abetting
firmware blobs in the kernel and users needing to do stuff.
Thanks.
--
Regards/Gruss,
Boris.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-29 17:21 ` Borislav Petkov
@ 2011-08-29 17:51 ` Peter Zijlstra
0 siblings, 0 replies; 37+ messages in thread
From: Peter Zijlstra @ 2011-08-29 17:51 UTC (permalink / raw)
To: Borislav Petkov
Cc: Kyle Moffett, Alex Deucher, Pavel Ivanov, Michel Dänzer,
dri-devel, linux-kernel
On Mon, 2011-08-29 at 19:21 +0200, Borislav Petkov wrote:
>
> Yeah, sounds much better than Kconfig actually aiding and abetting
> firmware blobs in the kernel and users needing to do stuff.
>
I would very much like to retain that option.. and having to manually
figure out what blob goes with what driver just isn't fun.
^ permalink raw reply [flat|nested] 37+ messages in thread
* Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
2011-08-27 9:00 ` Michel Dänzer
2011-08-27 22:50 ` Pavel Ivanov
@ 2011-08-27 23:03 ` Kyle Moffett
1 sibling, 0 replies; 37+ messages in thread
From: Kyle Moffett @ 2011-08-27 23:03 UTC (permalink / raw)
To: Michel Dänzer; +Cc: Pavel Ivanov, dri-devel, linux-kernel
2011/8/27 Michel Dänzer <michel@daenzer.net>:
> On Sam, 2011-08-27 at 00:20 -0400, Pavel Ivanov wrote:
>> I observe very strange behavior dependent on value of
>> CONFIG_DRM_RADEON parameter. When it's set to m everything works very
>> good, no problem. When I set it to y I see kernel hang during boot. Or
>> I should better say it "almost hangs" because during last boot attempt
>> I accidentally waited a little bit longer and saw that after more than
>> a minute waiting system continued to boot. Dmesg after "hang" shows
>> these messages:
>>
>> [ 8.542639] [drm] Loading CEDAR Microcode
>> [ 69.161605] r600_cp: Failed to load firmware "radeon/CEDAR_pfp.bin"
>> [ 69.161670] [drm:evergreen_startup] *ERROR* Failed to load firmware!
>>
>> While during normal boot
>>
>> [ 9.898870] [drm] Loading CEDAR Microcode
>> [ 9.908425] radeon 0000:05:00.0: WB enabled
>
> With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
> loaded from userspace, so it needs to be built into the kernel as well.
Linus has gotten pissed previously about drivers that do this.
I actually recall a patch previously that made request_firmware() fail instantly
before userspace is loaded, which would get rid of the hang, but presumably
not actually make the driver work when built-in.
The solution is to allow the driver to "attach" to the device but if
the firmware is
not available at that time then retrying the request_firmware() later, ideally
triggered from some userspace action.
Cheers,
Kyle Moffett
^ permalink raw reply [flat|nested] 37+ messages in thread
end of thread, other threads:[~2011-08-30 14:55 UTC | newest]
Thread overview: 37+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-08-27 4:20 Kernel almost hangs when CONFIG_DRM_RADEON=y Pavel Ivanov
2011-08-27 9:00 ` Michel Dänzer
2011-08-27 22:50 ` Pavel Ivanov
2011-08-28 5:36 ` Borislav Petkov
2011-08-28 21:47 ` Pavel Ivanov
2011-08-28 21:47 ` Pavel Ivanov
2011-08-29 5:49 ` Borislav Petkov
2011-08-29 6:04 ` Michel Dänzer
2011-08-29 6:04 ` Michel Dänzer
2011-08-29 13:20 ` Peter Zijlstra
2011-08-29 13:38 ` Borislav Petkov
2011-08-29 13:43 ` Dave Airlie
2011-08-29 13:48 ` Alex Deucher
2011-08-29 14:16 ` Borislav Petkov
2011-08-29 15:47 ` David Airlie
2011-08-29 15:55 ` Borislav Petkov
2011-08-29 16:10 ` Arnaud Lacombe
2011-08-29 16:10 ` Arnaud Lacombe
2011-08-29 17:17 ` Borislav Petkov
2011-08-29 17:38 ` Michel Dänzer
2011-08-29 17:38 ` Michel Dänzer
2011-08-29 17:50 ` Peter Zijlstra
2011-08-29 18:09 ` Peter Zijlstra
2011-08-29 18:16 ` Peter Zijlstra
2011-08-29 21:14 ` Borislav Petkov
2011-08-30 2:08 ` Henrique de Moraes Holschuh
2011-08-30 2:08 ` Henrique de Moraes Holschuh
2011-08-30 7:17 ` Borislav Petkov
2011-08-30 7:17 ` Borislav Petkov
2011-08-30 14:44 ` Henrique de Moraes Holschuh
2011-08-30 14:44 ` Henrique de Moraes Holschuh
2011-08-30 8:37 ` Peter Zijlstra
2011-08-30 14:55 ` Henrique de Moraes Holschuh
2011-08-29 16:28 ` Kyle Moffett
2011-08-29 17:21 ` Borislav Petkov
2011-08-29 17:51 ` Peter Zijlstra
2011-08-27 23:03 ` Kyle Moffett
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.