3.15-rc2: i915 regression: only top 20% of screen works in X

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

* 3.15-rc2: i915 regression: only top 20% of screen works in X
@ 2014-04-23 20:22 Pavel Machek
  2014-04-23 21:09 ` Daniel Vetter
  0 siblings, 1 reply; 20+ messages in thread
From: Pavel Machek @ 2014-04-23 20:22 UTC (permalink / raw)
  To: daniel.vetter, jani.nikula, intel-gfx, dri-devel,
	Rafael J. Wysocki, kernel list

Hi!

After update to 3.15-rc2, only top 20% of screen works on X.

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)

00:02.1 Display controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)
	   Subsystem: Intel Corporation Device d614
	   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
	   ParErr- Stepping- SERR- FastB2B- DisINTx-
	   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
	   >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	   Latency: 0
	   Region 0: Memory at d0400000 (64-bit, non-prefetchable)
	   [size=1M]
	   Capabilities: <access denied>

This worked before. I believe it worked in 3.14. It definitely works
in 3.11-rc2.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-23 20:22 3.15-rc2: i915 regression: only top 20% of screen works in X Pavel Machek
@ 2014-04-23 21:09 ` Daniel Vetter
  2014-04-23 22:03   ` Pavel Machek
  2014-04-23 22:09   ` Pavel Machek
  0 siblings, 2 replies; 20+ messages in thread
From: Daniel Vetter @ 2014-04-23 21:09 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Nikula, Jani, intel-gfx, dri-devel, Rafael J. Wysocki,
	kernel list

On Wed, Apr 23, 2014 at 10:22 PM, Pavel Machek <pavel@ucw.cz> wrote:
> After update to 3.15-rc2, only top 20% of screen works on X.
>
> 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> Integrated Graphics Controller (rev 03)
>
> 00:02.1 Display controller: Intel Corporation 4 Series Chipset
> Integrated Graphics Controller (rev 03)
>            Subsystem: Intel Corporation Device d614
>            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>            ParErr- Stepping- SERR- FastB2B- DisINTx-
>            Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>            >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>            Latency: 0
>            Region 0: Memory at d0400000 (64-bit, non-prefetchable)
>            [size=1M]
>            Capabilities: <access denied>
>
> This worked before. I believe it worked in 3.14. It definitely works
> in 3.11-rc2.

Screenshot or more detailed description of what "only top 20% of
screen works in X" means?
Anything in dmesg?
bisect result presuming that it reproduces reliably?

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-23 21:09 ` Daniel Vetter
@ 2014-04-23 22:03   ` Pavel Machek
  2014-04-23 22:09   ` Pavel Machek
  1 sibling, 0 replies; 20+ messages in thread
From: Pavel Machek @ 2014-04-23 22:03 UTC (permalink / raw)
  To: Daniel Vetter
  Cc: Nikula, Jani, intel-gfx, dri-devel, Rafael J. Wysocki,
	kernel list

On Wed 2014-04-23 23:09:45, Daniel Vetter wrote:
> On Wed, Apr 23, 2014 at 10:22 PM, Pavel Machek <pavel@ucw.cz> wrote:
> > After update to 3.15-rc2, only top 20% of screen works on X.
> >
> > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller (rev 03)
> >
> > 00:02.1 Display controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller (rev 03)
> >            Subsystem: Intel Corporation Device d614
> >            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> >            ParErr- Stepping- SERR- FastB2B- DisINTx-
> >            Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
> >            >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> >            Latency: 0
> >            Region 0: Memory at d0400000 (64-bit, non-prefetchable)
> >            [size=1M]
> >            Capabilities: <access denied>
> >
> > This worked before. I believe it worked in 3.14. It definitely works
> > in 3.11-rc2.
> 
> Screenshot or more detailed description of what "only top 20% of
> screen works in X" means?

Well, top cca 20% is ok, then I got repeated pattern of some part of screen.

> Anything in dmesg?

That will take a look.

> bisect result presuming that it reproduces reliably?

If there's no other chance, I guess I could do bisect. But
first.... Do you have similar hardware? Does it work for you? Are
there any experimental changes that went in recently and I should
try reverting first?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-23 21:09 ` Daniel Vetter
  2014-04-23 22:03   ` Pavel Machek
@ 2014-04-23 22:09   ` Pavel Machek
  2014-04-24  5:50     ` Chris Wilson
  1 sibling, 1 reply; 20+ messages in thread
From: Pavel Machek @ 2014-04-23 22:09 UTC (permalink / raw)
  To: Daniel Vetter
  Cc: Nikula, Jani, intel-gfx, dri-devel, Rafael J. Wysocki,
	kernel list

Hi!

> > After update to 3.15-rc2, only top 20% of screen works on X.
> >
> > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller (rev 03)
> >
> > 00:02.1 Display controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller (rev 03)
> >            Subsystem: Intel Corporation Device d614
> >            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> >            ParErr- Stepping- SERR- FastB2B- DisINTx-
> >            Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
> >            >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> >            Latency: 0
> >            Region 0: Memory at d0400000 (64-bit, non-prefetchable)
> >            [size=1M]
> >            Capabilities: <access denied>
> >
> > This worked before. I believe it worked in 3.14. It definitely works
> > in 3.11-rc2.
> 
> Screenshot or more detailed description of what "only top 20% of
> screen works in X" means?
> Anything in dmesg?

Actually yes, dmesg suggests it is quite
sick. drivers/gpu/drm/drm_mm.c:767 warning triggered
repeatedly. Also.. initial framebuffer does not work ; I don't seem to
see anything before X start up. (This is Debian 6.0.9)

Best regards,
								Pavel

Initializing cgroup subsys cpu
Linux version 3.15.0-rc1+ (pavel@amd) (gcc version 4.4.5 (Debian 4.4.5-8) ) #335 SMP Sat Apr 19 17:58:01 CEST 2014
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x00000000bd87dfff] usable
BIOS-e820: [mem 0x00000000bd87e000-0x00000000bd900fff] ACPI NVS
BIOS-e820: [mem 0x00000000bd901000-0x00000000bda42fff] reserved
BIOS-e820: [mem 0x00000000bda43000-0x00000000bda56fff] ACPI NVS
BIOS-e820: [mem 0x00000000bda57000-0x00000000bdb54fff] reserved
BIOS-e820: [mem 0x00000000bdb55000-0x00000000bdb5dfff] ACPI data
BIOS-e820: [mem 0x00000000bdb5e000-0x00000000bdb67fff] ACPI NVS
BIOS-e820: [mem 0x00000000bdb68000-0x00000000bdb88fff] reserved
BIOS-e820: [mem 0x00000000bdb89000-0x00000000bdb8efff] ACPI NVS
BIOS-e820: [mem 0x00000000bdb8f000-0x00000000bdcfffff] usable
BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed8ffff] reserved
BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000013fffffff] usable
Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
SMBIOS 2.4 present.
DMI:                  /DG41MJ, BIOS MJG4110H.86A.0006.2009.1223.1155 12/23/2009
e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
e820: last_pfn = 0xbdd00 max_arch_pfn = 0x100000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-E7FFF uncachable
  E8000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 000000000 mask F00000000 write-back
  1 base 100000000 mask FC0000000 write-back
  2 base 0BDD00000 mask FFFF00000 write-through
  3 base 0BDE00000 mask FFFE00000 uncachable
  4 base 0BE000000 mask FFE000000 uncachable
  5 base 0C0000000 mask FC0000000 uncachable
  6 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
initial memory mapped: [mem 0x00000000-0x053fffff]
Base memory trampoline at [c009a000] 9a000 size 16384
init_memory_mapping: [mem 0x00000000-0x000fffff]
 [mem 0x00000000-0x000fffff] page 4k
init_memory_mapping: [mem 0x37000000-0x373fffff]
 [mem 0x37000000-0x373fffff] page 4k
BRK [0x05109000, 0x05109fff] PGTABLE
init_memory_mapping: [mem 0x30000000-0x36ffffff]
 [mem 0x30000000-0x36ffffff] page 4k
BRK [0x0510a000, 0x0510afff] PGTABLE
BRK [0x0510b000, 0x0510bfff] PGTABLE
BRK [0x0510c000, 0x0510cfff] PGTABLE
BRK [0x0510d000, 0x0510dfff] PGTABLE
BRK [0x0510e000, 0x0510efff] PGTABLE
init_memory_mapping: [mem 0x00100000-0x2fffffff]
 [mem 0x00100000-0x2fffffff] page 4k
init_memory_mapping: [mem 0x37400000-0x377fdfff]
 [mem 0x37400000-0x377fdfff] page 4k
ACPI: RSDP 0x000F03C0 000024 (v02 INTEL )
ACPI: XSDT 0xBDB5CE18 000044 (v01 INTEL  DG41MJ   00000006 MSFT 00010013)
ACPI: FACP 0xBDB5BD98 0000F4 (v04 INTEL  DG41RQ   00000006 MSFT 00010013)
ACPI BIOS Warning (bug): 32/64X FACS address mismatch in FADT: 0xBDB5FF40/0x00000000BDB64F40, using 64-bit address (20140214/tbfadt-271)
ACPI: DSDT 0xBDB55018 005983 (v01 INTEL  DG41MJ   00000006 INTL 20051117)
ACPI: FACS 0xBDB64F40 000040
ACPI: APIC 0xBDB5BF18 00006C (v02 INTEL  DG41MJ   00000006 MSFT 00010013)
ACPI: MCFG 0xBDB66E18 00003C (v01 INTEL  DG41MJ   00000006 MSFT 00000097)
ACPI: HPET 0xBDB66D98 000038 (v01 INTEL  DG41MJ   00000006 AMI. 00000003)
ACPI: Local APIC address 0xfee00000
2149MB HIGHMEM available.
887MB LOWMEM available.
  mapped low ram: 0 - 377fe000
  low ram: 0 - 377fe000
Zone ranges:
  DMA      [mem 0x00001000-0x00ffffff]
  Normal   [mem 0x01000000-0x377fdfff]
  HighMem  [mem 0x377fe000-0xbdcfffff]
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x00001000-0x0009dfff]
  node   0: [mem 0x00100000-0xbd87dfff]
  node   0: [mem 0xbdb8f000-0xbdcfffff]
On node 0 totalpages: 776588
free_area_init_node: node 0, pgdat c4b566c0, node_mem_map f5885024
  DMA zone: 36 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 3997 pages, LIFO batch:0
  Normal zone: 1962 pages used for memmap
  Normal zone: 223230 pages, LIFO batch:31
  HighMem zone: 4836 pages used for memmap
  HighMem zone: 549361 pages, LIFO batch:31
Using APIC driver default
Reserving Intel graphics stolen memory at 0xbe000000-0xbfffffff
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled)
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
smpboot: Allowing 4 CPUs, 2 hotplug CPUs
nr_irqs_gsi: 40
PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
e820: [mem 0xc0000000-0xfebfffff] available for PCI devices
setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 13 pages/cpu @f7794000 s29312 r0 d23936 u53248
pcpu-alloc: s29312 r0 d23936 u53248 alloc=13*4096
pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 774590
Kernel command line: BOOT_IMAGE=(hd0,2)/l/linux-good/arch/x86/boot/bzImage root=/dev/sda3 resume=/dev/sda1
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Initializing CPU#0
xsave: enabled xstate_bv 0x3, cntxt size 0x240
Initializing HighMem for node 0 (000377fe:000bdd00)
Initializing Movable for node 0 (00000000:00000000)
Memory: 3059460K/3106352K available (8171K kernel code, 529K rwdata, 3012K rodata, 488K init, 5108K bss, 46892K reserved, 2197444K highmem)
virtual kernel memory layout:
    fixmap  : 0xffe6f000 - 0xfffff000   (1600 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000   ( 120 MB)
    lowmem  : 0xc0000000 - 0xf77fe000   ( 887 MB)
      .init : 0xc4b74000 - 0xc4bee000   ( 488 kB)
      .data : 0xc47fb245 - 0xc4b72400   (3548 kB)
      .text : 0xc4000000 - 0xc47fb245   (8172 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
Hierarchical RCU implementation.
	RCU dyntick-idle grace-period acceleration is enabled.
	RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
NR_IRQS:2304 nr_irqs:712 16
CPU 0 irqstacks, hard=f541a000 soft=f541c000
spurious 8259A interrupt: IRQ7.
Console: colour VGA+ 80x25
console [tty0] enabled
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES:  8
... MAX_LOCK_DEPTH:          48
... MAX_LOCKDEP_KEYS:        8191
... CLASSHASH_SIZE:          4096
... MAX_LOCKDEP_ENTRIES:     16384
... MAX_LOCKDEP_CHAINS:      32768
... CHAINHASH_SIZE:          16384
 memory used by lock dependency info: 3551 kB
 per task-struct memory footprint: 1152 bytes
ODEBUG: 11 of 11 active objects replaced
hpet clockevent registered
tsc: Fast TSC calibration using PIT
tsc: Detected 2799.691 MHz processor
Calibrating delay loop (skipped), value calculated using timer frequency.. 5599.38 BogoMIPS (lpj=11198764)
pid_max: default: 32768 minimum: 301
ACPI: Core revision 20140214
ACPI: All ACPI Tables successfully acquired
Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32, 1GB 0
tlb_flushall_shift: -1
debug: unmapping init [mem 0xc4bee000-0xc4bf5fff]
Enabling APIC mode:  Flat.  Using 1 I/O APICs
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
smpboot: CPU0: Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz (fam: 06, model: 17, stepping: 0a)
Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
... version:                2
... bit width:              40
... generic registers:      2
... value mask:             000000ffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             0000000700000003
CPU 1 irqstacks, hard=f55b8000 soft=f55ba000
x86: Booting SMP configuration:
.... node  #0, CPUs:      #1
Initializing CPU#1
x86: Booted up 1 node, 2 CPUs
smpboot: Total of 2 processors activated (11198.76 BogoMIPS)
NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
devtmpfs: initialized
PM: Registering ACPI NVS region [mem 0xbd87e000-0xbd900fff] (536576 bytes)
PM: Registering ACPI NVS region [mem 0xbda43000-0xbda56fff] (81920 bytes)
PM: Registering ACPI NVS region [mem 0xbdb5e000-0xbdb67fff] (40960 bytes)
PM: Registering ACPI NVS region [mem 0xbdb89000-0xbdb8efff] (24576 bytes)
NET: Registered protocol family 16
cpuidle: using governor ladder
cpuidle: using governor menu
ACPI: bus type PCI registered
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: not using MMCONFIG
PCI: Using configuration type 1 for base access
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: SSDT 0xBDB5FC18 0002CC (v01 AMI    IST      00000001 MSFT 03000001)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0x00000000 0002CC (v01 AMI    IST      00000001 MSFT 03000001)
ACPI: Interpreter enabled
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140214/hwxface-580)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140214/hwxface-580)
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
PCI: Using MMCONFIG for extended config space
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
ACPI: \_PR_.CPU3: failed to get CPU APIC ID.
ACPI: \_PR_.CPU4: failed to get CPU APIC ID.
ACPI: \_PR_.CPU5: failed to get CPU APIC ID.
ACPI: \_PR_.CPU6: failed to get CPU APIC ID.
ACPI: \_PR_.CPU7: failed to get CPU APIC ID.
ACPI: \_PR_.CPU8: failed to get CPU APIC ID.
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments]
acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI]
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
pci_bus 0000:00: root bus resource [io  0x0d00-0xffff]
pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: root bus resource [mem 0xc0000000-0xffffffff]
pci 0000:00:00.0: [8086:2e30] type 00 class 0x060000
pci 0000:00:01.0: [8086:2e31] type 01 class 0x060400
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: System wakeup disabled by ACPI
pci 0000:00:02.0: [8086:2e32] type 00 class 0x030000
pci 0000:00:02.0: reg 0x10: [mem 0xd0000000-0xd03fffff 64bit]
pci 0000:00:02.0: reg 0x18: [mem 0xc0000000-0xcfffffff 64bit pref]
pci 0000:00:02.0: reg 0x20: [io  0xf140-0xf147]
pci 0000:00:02.1: [8086:2e33] type 00 class 0x038000
pci 0000:00:02.1: reg 0x10: [mem 0xd0400000-0xd04fffff 64bit]
pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
pci 0000:00:1b.0: reg 0x10: [mem 0xd0600000-0xd0603fff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: System wakeup disabled by ACPI
pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: System wakeup disabled by ACPI
pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
pci 0000:00:1d.0: reg 0x20: [io  0xf080-0xf09f]
pci 0000:00:1d.0: System wakeup disabled by ACPI
pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
pci 0000:00:1d.1: reg 0x20: [io  0xf060-0xf07f]
pci 0000:00:1d.1: System wakeup disabled by ACPI
pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
pci 0000:00:1d.2: reg 0x20: [io  0xf040-0xf05f]
pci 0000:00:1d.2: System wakeup disabled by ACPI
pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
pci 0000:00:1d.3: reg 0x20: [io  0xf020-0xf03f]
pci 0000:00:1d.3: System wakeup disabled by ACPI
pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
pci 0000:00:1d.7: reg 0x10: [mem 0xd0604000-0xd06043ff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: System wakeup disabled by ACPI
pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
pci 0000:00:1e.0: System wakeup disabled by ACPI
pci 0000:00:1f.0: [8086:27b8] type 00 class 0x060100
pci 0000:00:1f.0: can't claim BAR 7 [io  0x0800-0x087f]: address conflict with ACPI CPU throttle [io  0x0810-0x0815]
pci 0000:00:1f.0: quirk: [io  0x0480-0x04bf] claimed by ICH6 GPIO
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0a00 (mask 00ff)
pci 0000:00:1f.1: [8086:27df] type 00 class 0x01018a
pci 0000:00:1f.1: reg 0x10: [io  0x0000-0x0007]
pci 0000:00:1f.1: reg 0x14: [io  0x0000-0x0003]
pci 0000:00:1f.1: reg 0x18: [io  0x08f0-0x08f7]
pci 0000:00:1f.1: reg 0x1c: [io  0x08f8-0x08fb]
pci 0000:00:1f.1: reg 0x20: [io  0xf0f0-0xf0ff]
pci 0000:00:1f.1: legacy IDE quirk: reg 0x10: [io  0x01f0-0x01f7]
pci 0000:00:1f.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
pci 0000:00:1f.1: legacy IDE quirk: reg 0x18: [io  0x0170-0x0177]
pci 0000:00:1f.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
pci 0000:00:1f.2: [8086:27c0] type 00 class 0x01018f
pci 0000:00:1f.2: reg 0x10: [io  0xf0e0-0xf0e7]
pci 0000:00:1f.2: reg 0x14: [io  0xf0d0-0xf0d3]
pci 0000:00:1f.2: reg 0x18: [io  0xf0c0-0xf0c7]
pci 0000:00:1f.2: reg 0x1c: [io  0xf0b0-0xf0b3]
pci 0000:00:1f.2: reg 0x20: [io  0xf0a0-0xf0af]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
pci 0000:00:1f.3: reg 0x20: [io  0x0400-0x041f]
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:1c.0: PCI bridge to [bus 02]
pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
pci 0000:03:00.0: reg 0x10: [io  0xe000-0xe0ff]
pci 0000:03:00.0: reg 0x18: [mem 0xd0514000-0xd0514fff 64bit pref]
pci 0000:03:00.0: reg 0x20: [mem 0xd0510000-0xd0513fff 64bit pref]
pci 0000:03:00.0: reg 0x30: [mem 0xd0500000-0xd050ffff pref]
pci 0000:03:00.0: supports D1 D2
pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:1c.1: PCI bridge to [bus 03]
pci 0000:00:1c.1:   bridge window [io  0xe000-0xefff]
pci 0000:00:1c.1:   bridge window [mem 0xd0500000-0xd05fffff]
pci 0000:00:1e.0: PCI bridge to [bus 04] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0000-0x0cf7] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0d00-0xffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xc0000000-0xffffffff] (subtractive decode)
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 10 11 12 14 15)
ACPI: Enabled 2 GPEs in block 00 to 1F
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:00:02.0
SCSI subsystem initialized
libata version 3.00 loaded.
ACPI: bus type USB registered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
e820: reserve RAM buffer [mem 0xbd87e000-0xbfffffff]
e820: reserve RAM buffer [mem 0xbdd00000-0xbfffffff]
Bluetooth: Core ver 2.19
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1 at net/wireless/reg.c:479 regulatory_init+0x88/0xf5()
db.txt is empty, you should update it...
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.15.0-rc1+ #335
Hardware name:                  /DG41MJ, BIOS MJG4110H.86A.0006.2009.1223.1155 12/23/2009
 000001df f5517e44 c47f4b0f c4a9e750 f5517e74 c403872a c4aa85f8 f5517ea0
 00000001 c4a9e750 000001df c4baa8df c4baa8df 00000000 c4baa780 f5517ec8
 f5517e8c c40387ce 00000009 f5517e84 c4aa85f8 f5517ea0 f5517ecc c4baa8df
Call Trace:
 [<c47f4b0f>] dump_stack+0x41/0x52
 [<c403872a>] warn_slowpath_common+0x7a/0xa0
 [<c4baa8df>] ? regulatory_init+0x88/0xf5
 [<c4baa8df>] ? regulatory_init+0x88/0xf5
 [<c4baa780>] ? cache_initialize+0x86/0x86
 [<c40387ce>] warn_slowpath_fmt+0x2e/0x30
 [<c4baa8df>] regulatory_init+0x88/0xf5
 [<c4baa7df>] cfg80211_init+0x5f/0xd7
 [<c4ba9e21>] ? bt_init+0x6e/0x98
 [<c40003fa>] do_one_initcall+0xca/0x180
 [<c406e40b>] ? __wake_up+0x1b/0x50
 [<c4b74663>] ? repair_env_string+0x15/0x5b
 [<c4051e11>] ? parse_args+0x1f1/0x440
 [<c4b745a9>] kernel_init_freeable+0xec/0x191
 [<c4b7464e>] ? kernel_init_freeable+0x191/0x191
 [<c47f12fb>] kernel_init+0xb/0xe0
 [<c47f9d41>] ret_from_kernel_thread+0x21/0x30
 [<c47f12f0>] ? rest_init+0xb0/0xb0
---[ end trace 5ca1be6641aaee8c ]---
cfg80211: Calling CRDA to update world regulatory domain
Switched to clocksource hpet
pnp: PnP ACPI init
ACPI: bus type PNP registered
system 00:00: [mem 0xfed14000-0xfed19fff] has been reserved
system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
system 00:01: [io  0x0800-0x087f] could not be reserved
system 00:01: [io  0x0480-0x04bf] has been reserved
system 00:01: [mem 0xfec00000-0xfec00fff] could not be reserved
system 00:01: [mem 0xfee00000-0xfee00fff] has been reserved
system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
system 00:01: [mem 0xfed20000-0xfed8ffff] has been reserved
system 00:01: [mem 0xff000000-0xffffffff] could not be reserved
system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:03: [dma 0 disabled]
pnp 00:03: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:04: [dma 3]
pnp 00:04: Plug and Play ACPI device, IDs PNP0401 (active)
pnp 00:05: [dma 4]
pnp 00:05: Plug and Play ACPI device, IDs PNP0200 (active)
pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:07: Plug and Play ACPI device, IDs PNP0800 (active)
system 00:08: [io  0x04d0-0x04d1] has been reserved
system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:09: Plug and Play ACPI device, IDs PNP0c04 (active)
pnp 00:0a: Plug and Play ACPI device, IDs PNP0103 (active)
pnp: PnP ACPI: found 11 devices
ACPI: bus type PNP unregistered
pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 02] add_size 1000
pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 02] add_size 200000
pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
pci 0000:00:1f.0: BAR 7: [io  0x0800-0x087f] has bogus alignment
pci 0000:00:1c.0: res[8]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
pci 0000:00:1c.0: res[9]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
pci 0000:00:1c.1: res[9]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
pci 0000:00:1c.0: res[7]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
pci 0000:00:1c.0: BAR 8: assigned [mem 0xd0700000-0xd08fffff]
pci 0000:00:1c.0: BAR 9: assigned [mem 0xd0900000-0xd0afffff 64bit pref]
pci 0000:00:1c.1: BAR 9: assigned [mem 0xd0b00000-0xd0cfffff 64bit pref]
pci 0000:00:1c.0: BAR 7: assigned [io  0x1000-0x1fff]
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:1c.0: PCI bridge to [bus 02]
pci 0000:00:1c.0:   bridge window [io  0x1000-0x1fff]
pci 0000:00:1c.0:   bridge window [mem 0xd0700000-0xd08fffff]
pci 0000:00:1c.0:   bridge window [mem 0xd0900000-0xd0afffff 64bit pref]
pci 0000:00:1c.1: PCI bridge to [bus 03]
pci 0000:00:1c.1:   bridge window [io  0xe000-0xefff]
pci 0000:00:1c.1:   bridge window [mem 0xd0500000-0xd05fffff]
pci 0000:00:1c.1:   bridge window [mem 0xd0b00000-0xd0cfffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 04]
pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7]
pci_bus 0000:00: resource 5 [io  0x0d00-0xffff]
pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: resource 7 [mem 0xc0000000-0xffffffff]
pci_bus 0000:02: resource 0 [io  0x1000-0x1fff]
pci_bus 0000:02: resource 1 [mem 0xd0700000-0xd08fffff]
pci_bus 0000:02: resource 2 [mem 0xd0900000-0xd0afffff 64bit pref]
pci_bus 0000:03: resource 0 [io  0xe000-0xefff]
pci_bus 0000:03: resource 1 [mem 0xd0500000-0xd05fffff]
pci_bus 0000:03: resource 2 [mem 0xd0b00000-0xd0cfffff 64bit pref]
pci_bus 0000:04: resource 4 [io  0x0000-0x0cf7]
pci_bus 0000:04: resource 5 [io  0x0d00-0xffff]
pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:04: resource 7 [mem 0xc0000000-0xffffffff]
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 6, 294912 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 512 (order: 3, 40960 bytes)
UDP-Lite hash table entries: 512 (order: 3, 40960 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
pci 0000:00:02.0: Boot video device
PCI: CLS 64 bytes, default 64
futex hash table entries: 1024 (order: 4, 65536 bytes)
bounce pool size: 64 pages
ntfs: driver 2.1.30 [Flags: R/W].
fuse init (API version 7.23)
msgmni has been set to 1683
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
usbcore: registered new interface driver udlfb
intel_idle: does not run on family 6 model 23
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
ACPI: Power Button [PWRF]
GHES: HEST is not enabled!
Error: Driver 'battery' is already registered, aborting...
ERST DBG: ERST support is disabled.
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
lp: driver loaded but no devices found
Non-volatile memory driver v1.3
intel_rng: Firmware space is locked read-only. If you can't or
intel_rng: don't want to disable this in firmware setup, and if
intel_rng: you are certain that your system has a functional
intel_rng: RNG, try using the 'no_fwh_detect' option.
Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel G41 Chipset
agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
agpgart-intel 0000:00:00.0: detected 32768K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000
[drm] Initialized drm 1.1.0 20060810
[drm] Memory usable by graphics device = 2048M
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 head 00002034 tail 00000000 start 0012f000
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/drm_mm.c:767 drm_mm_takedown+0x2c/0x30()
Memory manager not clean during takedown.
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W     3.15.0-rc1+ #335
Hardware name:                  /DG41MJ, BIOS MJG4110H.86A.0006.2009.1223.1155 12/23/2009
 000002ff f5517c00 c47f4b0f c4a27b17 f5517c30 c403872a c4a51954 f5517c5c
 00000001 c4a27b17 000002ff c435126c c435126c f40a8000 f4fd3800 fffffffb
 f5517c48 c40387ce 00000009 f5517c40 c4a51954 f5517c5c f5517c5c c435126c
Call Trace:
 [<c47f4b0f>] dump_stack+0x41/0x52
 [<c403872a>] warn_slowpath_common+0x7a/0xa0
 [<c435126c>] ? drm_mm_takedown+0x2c/0x30
 [<c435126c>] ? drm_mm_takedown+0x2c/0x30
 [<c40387ce>] warn_slowpath_fmt+0x2e/0x30
 [<c435126c>] drm_mm_takedown+0x2c/0x30
 [<c437f471>] i915_gem_init+0x71/0x190
 [<c43d2ff9>] i915_driver_load+0xa59/0xe00
 [<c43d3490>] ? i915_switcheroo_set_state+0xa0/0xa0
 [<c4075e1e>] ? __lock_acquire+0x3ae/0xc80
 [<c47f924d>] ? _raw_spin_unlock+0x1d/0x20
 [<c434dd02>] ? drm_minor_register+0x152/0x1c0
 [<c434de16>] drm_dev_register+0xa6/0xf0
 [<c434fb41>] drm_get_pci_dev+0x71/0x1d0
 [<c4360045>] i915_pci_probe+0x35/0x50
 [<c429b313>] local_pci_probe+0x33/0x80
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c429b5e0>] pci_device_probe+0x60/0x80
 [<c43e488f>] driver_probe_device+0x7f/0x360
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c43e4bf1>] __driver_attach+0x81/0x90
 [<c43e2f68>] bus_for_each_dev+0x68/0x90
 [<c43e4599>] driver_attach+0x19/0x20
 [<c43e4b70>] ? driver_probe_device+0x360/0x360
 [<c43e3817>] bus_add_driver+0x167/0x200
 [<c43e50b4>] driver_register+0x54/0xe0
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c429b6a5>] __pci_register_driver+0x45/0x50
 [<c434fd82>] drm_pci_init+0xe2/0x110
 [<c4b988e8>] ? drm_core_init+0xdb/0x107
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c4b98976>] i915_init+0x62/0x64
 [<c40003fa>] do_one_initcall+0xca/0x180
 [<c406e40b>] ? __wake_up+0x1b/0x50
 [<c4b74663>] ? repair_env_string+0x15/0x5b
 [<c4051e11>] ? parse_args+0x1f1/0x440
 [<c4b745a9>] kernel_init_freeable+0xec/0x191
 [<c4b7464e>] ? kernel_init_freeable+0x191/0x191
 [<c47f12fb>] kernel_init+0xb/0xe0
 [<c47f9d41>] ret_from_kernel_thread+0x21/0x30
 [<c47f12f0>] ? rest_init+0xb0/0xb0
---[ end trace 5ca1be6641aaee8d ]---
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/i915/intel_pm.c:5637 intel_display_power_put+0xfe/0x130()
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W     3.15.0-rc1+ #335
Hardware name:                  /DG41MJ, BIOS MJG4110H.86A.0006.2009.1223.1155 12/23/2009
 00001605 f5517c10 c47f4b0f c4a52694 f5517c40 c403872a c49eeaf8 00000001
 00000001 c4a52694 00001605 c4368b6e c4368b6e 00000999 00000015 f40a8000
 f5517c50 c403876d 00000009 00000000 f5517c7c c4368b6e c4a51954 f5517c7c
Call Trace:
 [<c47f4b0f>] dump_stack+0x41/0x52
 [<c403872a>] warn_slowpath_common+0x7a/0xa0
 [<c4368b6e>] ? intel_display_power_put+0xfe/0x130
 [<c4368b6e>] ? intel_display_power_put+0xfe/0x130
 [<c403876d>] warn_slowpath_null+0x1d/0x20
 [<c4368b6e>] intel_display_power_put+0xfe/0x130
 [<c437f471>] ? i915_gem_init+0x71/0x190
 [<c43d30c5>] i915_driver_load+0xb25/0xe00
 [<c43d3490>] ? i915_switcheroo_set_state+0xa0/0xa0
 [<c4075e1e>] ? __lock_acquire+0x3ae/0xc80
 [<c47f924d>] ? _raw_spin_unlock+0x1d/0x20
 [<c434dd02>] ? drm_minor_register+0x152/0x1c0
 [<c434de16>] drm_dev_register+0xa6/0xf0
 [<c434fb41>] drm_get_pci_dev+0x71/0x1d0
 [<c4360045>] i915_pci_probe+0x35/0x50
 [<c429b313>] local_pci_probe+0x33/0x80
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c429b5e0>] pci_device_probe+0x60/0x80
 [<c43e488f>] driver_probe_device+0x7f/0x360
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c43e4bf1>] __driver_attach+0x81/0x90
 [<c43e2f68>] bus_for_each_dev+0x68/0x90
 [<c43e4599>] driver_attach+0x19/0x20
 [<c43e4b70>] ? driver_probe_device+0x360/0x360
 [<c43e3817>] bus_add_driver+0x167/0x200
 [<c43e50b4>] driver_register+0x54/0xe0
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c429b6a5>] __pci_register_driver+0x45/0x50
 [<c434fd82>] drm_pci_init+0xe2/0x110
 [<c4b988e8>] ? drm_core_init+0xdb/0x107
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c4b98976>] i915_init+0x62/0x64
 [<c40003fa>] do_one_initcall+0xca/0x180
 [<c406e40b>] ? __wake_up+0x1b/0x50
 [<c4b74663>] ? repair_env_string+0x15/0x5b
 [<c4051e11>] ? parse_args+0x1f1/0x440
 [<c4b745a9>] kernel_init_freeable+0xec/0x191
 [<c4b7464e>] ? kernel_init_freeable+0x191/0x191
 [<c47f12fb>] kernel_init+0xb/0xe0
 [<c47f9d41>] ret_from_kernel_thread+0x21/0x30
 [<c47f12f0>] ? rest_init+0xb0/0xb0
---[ end trace 5ca1be6641aaee8e ]---
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/drm_mm.c:767 drm_mm_takedown+0x2c/0x30()
Memory manager not clean during takedown.
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W     3.15.0-rc1+ #335
Hardware name:                  /DG41MJ, BIOS MJG4110H.86A.0006.2009.1223.1155 12/23/2009
 000002ff f5517c14 c47f4b0f c4a27b17 f5517c44 c403872a c4a51954 f5517c70
 00000001 c4a27b17 000002ff c435126c c435126c f40a8000 fffffffb f40a8000
 f5517c5c c40387ce 00000009 f5517c54 c4a51954 f5517c70 f5517c70 c435126c
Call Trace:
 [<c47f4b0f>] dump_stack+0x41/0x52
 [<c403872a>] warn_slowpath_common+0x7a/0xa0
 [<c435126c>] ? drm_mm_takedown+0x2c/0x30
 [<c435126c>] ? drm_mm_takedown+0x2c/0x30
 [<c40387ce>] warn_slowpath_fmt+0x2e/0x30
 [<c435126c>] drm_mm_takedown+0x2c/0x30
 [<c43831f1>] i915_gem_cleanup_stolen+0x21/0x30
 [<c43d30d3>] i915_driver_load+0xb33/0xe00
 [<c43d3490>] ? i915_switcheroo_set_state+0xa0/0xa0
 [<c4075e1e>] ? __lock_acquire+0x3ae/0xc80
 [<c47f924d>] ? _raw_spin_unlock+0x1d/0x20
 [<c434dd02>] ? drm_minor_register+0x152/0x1c0
 [<c434de16>] drm_dev_register+0xa6/0xf0
 [<c434fb41>] drm_get_pci_dev+0x71/0x1d0
 [<c4360045>] i915_pci_probe+0x35/0x50
 [<c429b313>] local_pci_probe+0x33/0x80
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c429b5e0>] pci_device_probe+0x60/0x80
 [<c43e488f>] driver_probe_device+0x7f/0x360
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c43e4bf1>] __driver_attach+0x81/0x90
 [<c43e2f68>] bus_for_each_dev+0x68/0x90
 [<c43e4599>] driver_attach+0x19/0x20
 [<c43e4b70>] ? driver_probe_device+0x360/0x360
 [<c43e3817>] bus_add_driver+0x167/0x200
 [<c43e50b4>] driver_register+0x54/0xe0
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c429b6a5>] __pci_register_driver+0x45/0x50
 [<c434fd82>] drm_pci_init+0xe2/0x110
 [<c4b988e8>] ? drm_core_init+0xdb/0x107
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c4b98976>] i915_init+0x62/0x64
 [<c40003fa>] do_one_initcall+0xca/0x180
 [<c406e40b>] ? __wake_up+0x1b/0x50
 [<c4b74663>] ? repair_env_string+0x15/0x5b
 [<c4051e11>] ? parse_args+0x1f1/0x440
 [<c4b745a9>] kernel_init_freeable+0xec/0x191
 [<c4b7464e>] ? kernel_init_freeable+0x191/0x191
 [<c47f12fb>] kernel_init+0xb/0xe0
 [<c47f9d41>] ret_from_kernel_thread+0x21/0x30
 [<c47f12f0>] ? rest_init+0xb0/0xb0
---[ end trace 5ca1be6641aaee8f ]---
[drm:i915_driver_load] *ERROR* failed to init modeset
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/drm_mm.c:767 drm_mm_takedown+0x2c/0x30()
Memory manager not clean during takedown.
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W     3.15.0-rc1+ #335
Hardware name:                  /DG41MJ, BIOS MJG4110H.86A.0006.2009.1223.1155 12/23/2009
 000002ff f5517c20 c47f4b0f c4a27b17 f5517c50 c403872a c4a51954 f5517c7c
 00000001 c4a27b17 000002ff c435126c c435126c f4fd3800 fffffffb f40aa018
 f5517c68 c40387ce 00000009 f5517c60 c4a51954 f5517c7c f5517c7c c435126c
Call Trace:
 [<c47f4b0f>] dump_stack+0x41/0x52
 [<c403872a>] warn_slowpath_common+0x7a/0xa0
 [<c435126c>] ? drm_mm_takedown+0x2c/0x30
 [<c435126c>] ? drm_mm_takedown+0x2c/0x30
 [<c40387ce>] warn_slowpath_fmt+0x2e/0x30
 [<c435126c>] drm_mm_takedown+0x2c/0x30
 [<c43d29cd>] i915_driver_load+0x42d/0xe00
 [<c4075e1e>] ? __lock_acquire+0x3ae/0xc80
 [<c47f924d>] ? _raw_spin_unlock+0x1d/0x20
 [<c434dd02>] ? drm_minor_register+0x152/0x1c0
 [<c434de16>] drm_dev_register+0xa6/0xf0
 [<c434fb41>] drm_get_pci_dev+0x71/0x1d0
 [<c4360045>] i915_pci_probe+0x35/0x50
 [<c429b313>] local_pci_probe+0x33/0x80
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c429b5e0>] pci_device_probe+0x60/0x80
 [<c43e488f>] driver_probe_device+0x7f/0x360
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c43e4bf1>] __driver_attach+0x81/0x90
 [<c43e2f68>] bus_for_each_dev+0x68/0x90
 [<c43e4599>] driver_attach+0x19/0x20
 [<c43e4b70>] ? driver_probe_device+0x360/0x360
 [<c43e3817>] bus_add_driver+0x167/0x200
 [<c43e50b4>] driver_register+0x54/0xe0
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c429b6a5>] __pci_register_driver+0x45/0x50
 [<c434fd82>] drm_pci_init+0xe2/0x110
 [<c4b988e8>] ? drm_core_init+0xdb/0x107
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c4b98976>] i915_init+0x62/0x64
 [<c40003fa>] do_one_initcall+0xca/0x180
 [<c406e40b>] ? __wake_up+0x1b/0x50
 [<c4b74663>] ? repair_env_string+0x15/0x5b
 [<c4051e11>] ? parse_args+0x1f1/0x440
 [<c4b745a9>] kernel_init_freeable+0xec/0x191
 [<c4b7464e>] ? kernel_init_freeable+0x191/0x191
 [<c47f12fb>] kernel_init+0xb/0xe0
 [<c47f9d41>] ret_from_kernel_thread+0x21/0x30
 [<c47f12f0>] ? rest_init+0xb0/0xb0
---[ end trace 5ca1be6641aaee90 ]---
kmem_cache_destroy i915_gem_object: Slab cache still has objects
CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W     3.15.0-rc1+ #335
Hardware name:                  /DG41MJ, BIOS MJG4110H.86A.0006.2009.1223.1155 12/23/2009
 f57b2a40 f5517c64 c47f4b0f f57b2a00 f5517c7c c40d03ec c49f6910 f479b3e0
 f4fd3800 fffffffb f5517d6c c43d2a0d c4855752 c4a2dc53 00000001 c50d8de0
 c4a2dc2a 0000015c f817c15b 00000002 f82b615c 00005f02 00000003 00000000
Call Trace:
 [<c47f4b0f>] dump_stack+0x41/0x52
 [<c40d03ec>] kmem_cache_destroy+0x9c/0xc0
 [<c43d2a0d>] i915_driver_load+0x46d/0xe00
 [<c4075e1e>] ? __lock_acquire+0x3ae/0xc80
 [<c47f924d>] ? _raw_spin_unlock+0x1d/0x20
 [<c434dd02>] ? drm_minor_register+0x152/0x1c0
 [<c434de16>] drm_dev_register+0xa6/0xf0
 [<c434fb41>] drm_get_pci_dev+0x71/0x1d0
 [<c4360045>] i915_pci_probe+0x35/0x50
 [<c429b313>] local_pci_probe+0x33/0x80
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c429b5e0>] pci_device_probe+0x60/0x80
 [<c43e488f>] driver_probe_device+0x7f/0x360
 [<c429a3c2>] ? pci_match_device+0xb2/0xc0
 [<c43e4bf1>] __driver_attach+0x81/0x90
 [<c43e2f68>] bus_for_each_dev+0x68/0x90
 [<c43e4599>] driver_attach+0x19/0x20
 [<c43e4b70>] ? driver_probe_device+0x360/0x360
 [<c43e3817>] bus_add_driver+0x167/0x200
 [<c43e50b4>] driver_register+0x54/0xe0
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c429b6a5>] __pci_register_driver+0x45/0x50
 [<c434fd82>] drm_pci_init+0xe2/0x110
 [<c4b988e8>] ? drm_core_init+0xdb/0x107
 [<c4b98914>] ? drm_core_init+0x107/0x107
 [<c4b98976>] i915_init+0x62/0x64
 [<c40003fa>] do_one_initcall+0xca/0x180
 [<c406e40b>] ? __wake_up+0x1b/0x50
 [<c4b74663>] ? repair_env_string+0x15/0x5b
 [<c4051e11>] ? parse_args+0x1f1/0x440
 [<c4b745a9>] kernel_init_freeable+0xec/0x191
 [<c4b7464e>] ? kernel_init_freeable+0x191/0x191
 [<c47f12fb>] kernel_init+0xb/0xe0
 [<c47f9d41>] ret_from_kernel_thread+0x21/0x30
 [<c47f12f0>] ? rest_init+0xb0/0xb0
i915: probe of 0000:00:02.0 failed with error -5
parport_pc 00:04: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 5 [PCSPP(,...)]
lp0: using parport0 (interrupt-driven).
loop: module loaded
nbd: registered device at major 43
ata_piix 0000:00:1f.1: version 2.13
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf0f0 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf0f8 irq 15
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ata2: port disabled--ignoring
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0xf0e0 ctl 0xf0d0 bmdma 0xf0a0 irq 19
ata4: SATA max UDMA/133 cmd 0xf0c0 ctl 0xf0b0 bmdma 0xf0a8 irq 19
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:03:00.0 eth0: RTL8168d/8111d at 0xf8024000, 00:27:0e:2a:43:71, XID 081000c0 IRQ 17
r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
CSLIP: code copyright 1989 Regents of the University of California.
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:ds
iwl3945: Copyright(c) 2003-2011 Intel Corporation
usbcore: registered new interface driver ax88179_178a
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver cdc_ncm
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-pci 0000:00:1d.7: EHCI Host Controller
ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci-pci 0000:00:1d.7: debug port 1
ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
ehci-pci 0000:00:1d.7: irq 23, io mem 0xd0604000
ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 3.15.0-rc1+ ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: detected 2 ports
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000f080
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 3.15.0-rc1+ uhci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: detected 2 ports
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000f060
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 3.15.0-rc1+ uhci_hcd
usb usb3: SerialNumber: 0000:00:1d.1
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: detected 2 ports
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000f040
usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 3.15.0-rc1+ uhci_hcd
usb usb4: SerialNumber: 0000:00:1d.2
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: detected 2 ports
uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000f020
usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: UHCI Host Controller
usb usb5: Manufacturer: Linux 3.15.0-rc1+ uhci_hcd
usb usb5: SerialNumber: 0000:00:1d.3
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver usblp
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver ftdi_sio
usbserial: USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver option
usbserial: USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver pl2303
usbserial: USB Serial support registered for pl2303
usbcore: registered new interface driver ti_usb_3410_5052
usbserial: USB Serial support registered for TI USB 3410 1 port adapter
usbserial: USB Serial support registered for TI USB 5052 2 port adapter
driver ftdi-elan
usbcore: registered new interface driver ftdi-elan
i8042: PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mousedev: PS/2 mouse device common for all mice
input: PC Speaker as /devices/platform/pcspkr/input/input3
rtc_cmos 00:06: RTC can wake from S4
rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
rtc_cmos 00:06: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
usbcore: registered new interface driver btusb
lguest: mapped switcher at ffe65000
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: cubic registered
NET: Registered protocol family 17
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: HIDP socket layer initialized
Using IPI No-Shortcut mode
rtc_cmos 00:06: setting system clock to 2014-04-23 22:03:58 UTC (1398290638)
PM: Checking hibernation image partition /dev/sda1
sound hdaudioC0D2: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
sound hdaudioC0D2:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
sound hdaudioC0D2:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
sound hdaudioC0D2:    mono: mono_out=0x0
sound hdaudioC0D2:    inputs:
sound hdaudioC0D2:      Front Mic=0x19
sound hdaudioC0D2:      Rear Mic=0x18
sound hdaudioC0D2:      Line=0x1a
input: HDA Intel Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
ata3.01: NODEV after polling detection
ata3.00: ATAPI: HL-DT-ST DVDRAM GT20N, CQ02, max UDMA/133
ata3.00: configured for UDMA/133
scsi 2:0:0:0: CD-ROM            HL-DT-ST DVDRAM GT20N     CQ02 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 2:0:0:0: Attached scsi CD-ROM sr0
sr 2:0:0:0: Attached scsi generic sg0 type 5
ata4.00: ATA-9: ST1000LM014-1EJ164, SM11, max UDMA/133
ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/133
scsi 3:0:0:0: Direct-Access     ATA      ST1000LM014-1EJ1 SM11 PQ: 0 ANSI: 5
sd 3:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 3:0:0:0: [sda] 4096-byte physical blocks
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 3:0:0:0: Attached scsi generic sg1 type 0
sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4
sd 3:0:0:0: [sda] Attached SCSI disk
PM: Hibernation image partition 8:1 present
PM: Looking for hibernation image.
PM: Image not found (code -22)
PM: Hibernation image not present or could not be loaded.
ALSA device list:
  #0: HDA Intel at 0xd0600000 irq 16
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda3): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) readonly on device 8:3.
devtmpfs: mounted
debug: unmapping init [mem 0xc4b74000-0xc4bedfff]
Write protecting the kernel text: 8176k
Write protecting the kernel read-only data: 3016k
usb 1-4: new high-speed USB device number 3 using ehci-pci
usb 1-4: New USB device found, idVendor=058f, idProduct=6362
usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4: Product: Mass Storage Device
usb 1-4: Manufacturer: Generic
usb 1-4: SerialNumber: 058F312D81B
usb-storage 1-4:1.0: USB Mass Storage device detected
scsi4 : usb-storage 1-4:1.0
tsc: Refined TSC clocksource calibration: 2799.955 MHz
udev[1664]: starting version 164
usb 2-1: new low-speed USB device number 2 using uhci_hcd
usb 2-1: New USB device found, idVendor=0458, idProduct=002e
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1: Product: NetScroll+ Traveler
usb 2-1: Manufacturer: KYE
input: KYE NetScroll+ Traveler as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/0003:0458:002E.0001/input/input9
hid-generic 0003:0458:002E.0001: input,hidraw0: USB HID v1.10 Mouse [KYE NetScroll+ Traveler] on usb-0000:00:1d.0-1/input0
usb 4-2: new low-speed USB device number 2 using uhci_hcd
scsi 4:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
sd 4:0:0:0: Attached scsi generic sg2 type 0
scsi 4:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
sd 4:0:0:1: Attached scsi generic sg3 type 0
sd 4:0:0:0: [sdb] Attached SCSI removable disk
scsi 4:0:0:2: Direct-Access     Generic  USB SM Reader    1.02 PQ: 0 ANSI: 0
sd 4:0:0:2: Attached scsi generic sg4 type 0
sd 4:0:0:1: [sdc] Attached SCSI removable disk
scsi 4:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
sd 4:0:0:3: Attached scsi generic sg5 type 0
sd 4:0:0:3: [sde] Attached SCSI removable disk
sd 4:0:0:2: [sdd] Attached SCSI removable disk
usb 4-2: New USB device found, idVendor=04f2, idProduct=0111
usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 4-2: Product: USB Keyboard
usb 4-2: Manufacturer: Chicony
input: Chicony USB Keyboard as /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/0003:04F2:0111.0002/input/input10
hid-generic 0003:04F2:0111.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony USB Keyboard] on usb-0000:00:1d.2-2/input0
Switched to clocksource tsc
input: Chicony USB Keyboard as /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.1/0003:04F2:0111.0003/input/input11
hid-generic 0003:04F2:0111.0003: input,hiddev0,hidraw2: USB HID v1.10 Device [Chicony USB Keyboard] on usb-0000:00:1d.2-2/input1
random: nonblocking pool is initialized
Adding 2097148k swap on /dev/sda1.  Priority:-1 extents:1 across:2097148k 
EXT3-fs (sda3): using internal journal
EXT4-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: errors=remount-ro
EXT3-fs (sda4): error: can't find ext3 filesystem on dev sda4.
input: ACPI Virtual Keyboard Device as /devices/virtual/input/input12
r8169 0000:03:00.0: Direct firmware load failed with error -2
r8169 0000:03:00.0: Falling back to user helper
r8169 0000:03:00.0 eth1: unable to load firmware patch rtl_nic/rtl8168d-1.fw (-12)
r8169 0000:03:00.0 eth1: link down
r8169 0000:03:00.0 eth1: link down
r8169 0000:03:00.0 eth1: link up
sshd (3421): /proc/3421/oom_adj is deprecated, please use /proc/3421/oom_score_adj instead.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-23 22:09   ` Pavel Machek
@ 2014-04-24  5:50     ` Chris Wilson
  2014-04-24  6:03       ` Daniel Vetter
  2014-04-24 10:42       ` 3.15-rc2: " Pavel Machek
  0 siblings, 2 replies; 20+ messages in thread
From: Chris Wilson @ 2014-04-24  5:50 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Daniel Vetter, intel-gfx, Rafael J. Wysocki, dri-devel,
	kernel list, Jiri Kosina

On Thu, Apr 24, 2014 at 12:09:52AM +0200, Pavel Machek wrote:
> Hi!
> 
> > > After update to 3.15-rc2, only top 20% of screen works on X.
> > >
> > > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > > Integrated Graphics Controller (rev 03)
> > >
> > > 00:02.1 Display controller: Intel Corporation 4 Series Chipset
> > > Integrated Graphics Controller (rev 03)
> > >            Subsystem: Intel Corporation Device d614
> > >            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > >            ParErr- Stepping- SERR- FastB2B- DisINTx-
> > >            Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
> > >            >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> > >            Latency: 0
> > >            Region 0: Memory at d0400000 (64-bit, non-prefetchable)
> > >            [size=1M]
> > >            Capabilities: <access denied>
> > >
> > > This worked before. I believe it worked in 3.14. It definitely works
> > > in 3.11-rc2.
> > 
> > Screenshot or more detailed description of what "only top 20% of
> > screen works in X" means?
> > Anything in dmesg?
> 
> Actually yes, dmesg suggests it is quite
> sick. drivers/gpu/drm/drm_mm.c:767 warning triggered
> repeatedly. Also.. initial framebuffer does not work ; I don't seem to
> see anything before X start up. (This is Debian 6.0.9)

That says that i915.ko failed to initialise the GPU (or rather the GPU
wasn't responding) and bailed during module load. The key line here is

[drm:init_ring_common] *ERROR* render ring initialization failed ctl
0001f001 head 00002034 tail 00000000 start 0012f000

Jiri has been seeing a similar issue creep in during resume, but it is
not reliable enough to bisect. Is your boot failure reliable enough to
bisect? Also drm-intel-nightly should mitigate this failure and allow
i915.ko to continue to load and run X, which would be worth testing to
make sure that works as intended.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24  5:50     ` Chris Wilson
@ 2014-04-24  6:03       ` Daniel Vetter
  2014-04-24 13:36         ` Pavel Machek
                           ` (4 more replies)
  2014-04-24 10:42       ` 3.15-rc2: " Pavel Machek
  1 sibling, 5 replies; 20+ messages in thread
From: Daniel Vetter @ 2014-04-24  6:03 UTC (permalink / raw)
  To: Chris Wilson, Pavel Machek, Daniel Vetter, intel-gfx,
	Rafael J. Wysocki, dri-devel, kernel list, Jiri Kosina

On Thu, Apr 24, 2014 at 7:50 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> That says that i915.ko failed to initialise the GPU (or rather the GPU
> wasn't responding) and bailed during module load. The key line here is
>
> [drm:init_ring_common] *ERROR* render ring initialization failed ctl
> 0001f001 head 00002034 tail 00000000 start 0012f000
>
> Jiri has been seeing a similar issue creep in during resume, but it is
> not reliable enough to bisect. Is your boot failure reliable enough to
> bisect? Also drm-intel-nightly should mitigate this failure and allow
> i915.ko to continue to load and run X, which would be worth testing to
> make sure that works as intended.

Oh right, g4x going beserk :( Apparently something changed in 3.15
somewhere which made this much more likely, but like Chris said in
Jiri's case it's too unreliable to reproduce for a bisect. We've had
this come&go pretty much ever since kms support was merged and never
tracked it down.

The bug is https://bugs.freedesktop.org/show_bug.cgi?id=76554

Like Chris said please test latest drm-intel-nighlty from
http://cgit.freedesktop.org/drm-intel to make sure that the recently
merged mitigation measures work properly. But those won't get your gpu
back, only the display and it's only for 3.16. We're still hunting a
proper fix for 3.15.

And if you can indeed reliably reproduce this a bisect could be really useful.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24  6:03       ` Daniel Vetter
@ 2014-04-24 13:36         ` Pavel Machek
  2014-04-24 13:56           ` Jiri Kosina
  2014-04-24 13:43         ` Pavel Machek
                           ` (3 subsequent siblings)
  4 siblings, 1 reply; 20+ messages in thread
From: Pavel Machek @ 2014-04-24 13:36 UTC (permalink / raw)
  To: Daniel Vetter
  Cc: Chris Wilson, intel-gfx, Rafael J. Wysocki, dri-devel,
	kernel list, Jiri Kosina

On Thu 2014-04-24 08:03:04, Daniel Vetter wrote:
> On Thu, Apr 24, 2014 at 7:50 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > That says that i915.ko failed to initialise the GPU (or rather the GPU
> > wasn't responding) and bailed during module load. The key line here is
> >
> > [drm:init_ring_common] *ERROR* render ring initialization failed ctl
> > 0001f001 head 00002034 tail 00000000 start 0012f000
> >
> > Jiri has been seeing a similar issue creep in during resume, but it is
> > not reliable enough to bisect. Is your boot failure reliable enough to
> > bisect? Also drm-intel-nightly should mitigate this failure and allow
> > i915.ko to continue to load and run X, which would be worth testing to
> > make sure that works as intended.
> 
> Oh right, g4x going beserk :( Apparently something changed in 3.15
> somewhere which made this much more likely, but like Chris said in
> Jiri's case it's too unreliable to reproduce for a bisect. We've had
> this come&go pretty much ever since kms support was merged and never
> tracked it down.

So far I went back to 3.14, and yes, graphics works there.

Back to 3.15, put it to smaller monitor. This time, top 30% of screen
works, and last working scanline is copied to the rest 60% of
screen. [With the exception of mouse cursor, that somehow affects that
magically.]

> The bug is https://bugs.freedesktop.org/show_bug.cgi?id=76554
> 
> Like Chris said please test latest drm-intel-nighlty from
> http://cgit.freedesktop.org/drm-intel to make sure that the recently
> merged mitigation measures work properly. But those won't get your gpu
> back, only the display and it's only for 3.16. We're still hunting a
> proper fix for 3.15.

So you know where the bug is or not?

> And if you can indeed reliably reproduce this a bisect could be really useful.

I'm confused. And yes, it seems reliable. But I'm not sure if I see
same bug you are talking about.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24 13:36         ` Pavel Machek
@ 2014-04-24 13:56           ` Jiri Kosina
  0 siblings, 0 replies; 20+ messages in thread
From: Jiri Kosina @ 2014-04-24 13:56 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Daniel Vetter, Chris Wilson, intel-gfx, Rafael J. Wysocki,
	dri-devel, kernel list

On Thu, 24 Apr 2014, Pavel Machek wrote:

> > > [drm:init_ring_common] *ERROR* render ring initialization failed ctl
> > > 0001f001 head 00002034 tail 00000000 start 0012f000
> > >
> > > Jiri has been seeing a similar issue creep in during resume, but it is
> > > not reliable enough to bisect. Is your boot failure reliable enough to
> > > bisect? Also drm-intel-nightly should mitigate this failure and allow
> > > i915.ko to continue to load and run X, which would be worth testing to
> > > make sure that works as intended.
> > 
> > Oh right, g4x going beserk :( Apparently something changed in 3.15
> > somewhere which made this much more likely, but like Chris said in
> > Jiri's case it's too unreliable to reproduce for a bisect. We've had
> > this come&go pretty much ever since kms support was merged and never
> > tracked it down.
> 
> So far I went back to 3.14, and yes, graphics works there.
> 
> Back to 3.15, put it to smaller monitor. This time, top 30% of screen
> works, and last working scanline is copied to the rest 60% of
> screen. [With the exception of mouse cursor, that somehow affects that
> magically.]
> 
> > The bug is https://bugs.freedesktop.org/show_bug.cgi?id=76554
> > 
> > Like Chris said please test latest drm-intel-nighlty from
> > http://cgit.freedesktop.org/drm-intel to make sure that the recently
> > merged mitigation measures work properly. But those won't get your gpu
> > back, only the display and it's only for 3.16. We're still hunting a
> > proper fix for 3.15.
> 
> So you know where the bug is or not?

No, but there is a workaround for cases kernel finds out that it cannot 
execute GPU commands (because the rings failed to initialize), and instead 
it falls back to CPU rendering directly into the framebuffer.

So it's highly sub-optimal, but works around the complete wreckage.

-- 
Jiri Kosina
SUSE Labs


^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24  6:03       ` Daniel Vetter
  2014-04-24 13:36         ` Pavel Machek
@ 2014-04-24 13:43         ` Pavel Machek
  2014-04-24 15:03           ` Chris Wilson
  2014-04-24 19:28         ` [partial bisect] " Pavel Machek
                           ` (2 subsequent siblings)
  4 siblings, 1 reply; 20+ messages in thread
From: Pavel Machek @ 2014-04-24 13:43 UTC (permalink / raw)
  To: Daniel Vetter
  Cc: Chris Wilson, intel-gfx, Rafael J. Wysocki, dri-devel,
	kernel list, Jiri Kosina

Hi!

> Like Chris said please test latest drm-intel-nighlty from
> http://cgit.freedesktop.org/drm-intel to make sure that the recently
> merged mitigation measures work properly. But those won't get your gpu
> back, only the display and it's only for 3.16. We're still hunting a

What does it means "won't get my gpu back, just my display"? Gpu is
the thing driving the display... no?

I checked out drm-intel-nightly. Now I can see some kernel messages
scrolling around on vga console (improvement?), but then end up with
completely blank screen, and dead machine, AFAICT. Can't seem to ping
it.

BTW you might want to fix these...

drivers/gpu/drm/i915/i915_cmd_parser.c: In function ‘i915_parse_cmds’:
drivers/gpu/drm/i915/i915_cmd_parser.c:919: warning: format ‘%td’
expects type ‘ptrdiff_t’, but argument 5 has type ‘long unsigned int’
  CC      drivers/gpu/drm/i915/i915_gem_context.o
  LD [M]  drivers/gpu/drm/udl/udl.o
  CC      drivers/gpu/drm/i915/i915_gem_debug.o
  CC      drivers/gpu/drm/i915/i915_gem_dmabuf.o
  CC      drivers/gpu/drm/i915/i915_gem_evict.o
  CC      drivers/gpu/drm/i915/i915_gem_execbuffer.o
  CC      drivers/gpu/drm/i915/i915_gem_gtt.o
drivers/gpu/drm/i915/i915_gem_gtt.c: In function
‘gen8_ggtt_insert_entries’:
drivers/gpu/drm/i915/i915_gem_gtt.c:1389: warning: ‘addr’ may be used
uninitialized in this function
drivers/gpu/drm/i915/i915_gem_gtt.c: In function
‘gen6_ggtt_insert_entries’:
drivers/gpu/drm/i915/i915_gem_gtt.c:1435: warning: ‘addr’ may be used
uninitialized in this function

Thanks,
									Pavel


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24 13:43         ` Pavel Machek
@ 2014-04-24 15:03           ` Chris Wilson
  0 siblings, 0 replies; 20+ messages in thread
From: Chris Wilson @ 2014-04-24 15:03 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Daniel Vetter, intel-gfx, Rafael J. Wysocki, dri-devel,
	kernel list, Jiri Kosina

On Thu, Apr 24, 2014 at 03:43:45PM +0200, Pavel Machek wrote:
> Hi!
> 
> > Like Chris said please test latest drm-intel-nighlty from
> > http://cgit.freedesktop.org/drm-intel to make sure that the recently
> > merged mitigation measures work properly. But those won't get your gpu
> > back, only the display and it's only for 3.16. We're still hunting a
> 
> What does it means "won't get my gpu back, just my display"? Gpu is
> the thing driving the display... no?

We think of it as discrete functional units, i.e. the display engine is
separate from the GPU. What happens here is that the render engine
doesn't respond to our commands to set it up, but that should not
prevent us from setting the register values in the display engine to drive
the actual outputs.
 
> I checked out drm-intel-nightly. Now I can see some kernel messages
> scrolling around on vga console (improvement?), but then end up with
> completely blank screen, and dead machine, AFAICT. Can't seem to ping
> it.

Eeek. Do you have netconsole handy?
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

^ permalink raw reply	[flat|nested] 20+ messages in thread

* [partial bisect] Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24  6:03       ` Daniel Vetter
  2014-04-24 13:36         ` Pavel Machek
  2014-04-24 13:43         ` Pavel Machek
@ 2014-04-24 19:28         ` Pavel Machek
  2014-04-24 19:40         ` [bisect result] " Pavel Machek
  2014-04-24 20:13         ` [PATCH] fix " Pavel Machek
  4 siblings, 0 replies; 20+ messages in thread
From: Pavel Machek @ 2014-04-24 19:28 UTC (permalink / raw)
  To: Daniel Vetter
  Cc: Chris Wilson, intel-gfx, Rafael J. Wysocki, dri-devel,
	kernel list, Jiri Kosina

Hi!

> And if you can indeed reliably reproduce this a bisect could be
>  really useful

It seems reliable, yes. So far I got:
								Pavel

git bisect start
# good: [455c6fdbd219161bd09b1165f11699d6d73de11c] Linux 3.14
git bisect good 455c6fdbd219161bd09b1165f11699d6d73de11c
# bad: [c39b06951f1dc2e384650288676c5b7dcc0ec92c] DRM: armada: fix corruption while loading cursors
git bisect bad c39b06951f1dc2e384650288676c5b7dcc0ec92c
# good: [5fb6b953bb7aa86a9c8ea760934982cedc45c52b] include/linux/syscalls.h: add sys_renameat2() prototype
git bisect good 5fb6b953bb7aa86a9c8ea760934982cedc45c52b
# good: [8ad2bc9796994ecba9f4ba2fc9abca27ee9d193d] Merge branch 'drm-intel-next' of git://git.freedesktop.org/git/drm-intel into drm-next
git bisect good 8ad2bc9796994ecba9f4ba2fc9abca27ee9d193d
# good: [1287aa903f1b9248f34fb215e3b875d2ae243425] drm: Remove the prefix argument of drm_ut_debug_printk()
git bisect good 1287aa903f1b9248f34fb215e3b875d2ae243425
# bad: [c8431fda9f9f3c3b7490cb44bd5720b494a2421e] drm/i915: don't get/put runtime PM at the debugfs forcewake file
git bisect bad c8431fda9f9f3c3b7490cb44bd5720b494a2421e
# bad: [db8384f2e07bfa8cc607914dfa0b3cee81f59839] drm/i915: don't get/put PC8 reference on freeze/thaw
git bisect bad db8384f2e07bfa8cc607914dfa0b3cee81f59839
# bad: [b2040f6fed736ccd2319768bc59833abe74148b8] drm/i915: Remove erronous WARN in the vlv pipe crc code
git bisect bad b2040f6fed736ccd2319768bc59833abe74148b8
# good: [301ea74a57851c19e1438ceeaffab663f402f79f] drm/i915: Allow HDMI+VGA cloning
git bisect good 301ea74a57851c19e1438ceeaffab663f402f79f
# bad: [02f6a1e750df8201561171c47472435557a65864] drm/i915: warn if ring is active before sync flush
git bisect bad 02f6a1e750df8201561171c47472435557a65864
# good: [8407bb9129da95fc4099b84cdbbc23e6d4f66aee] drm/i915/bdw: Use scratch page table for GEN8 PPGTT
git bisect good 8407bb9129da95fc4099b84cdbbc23e6d4f66aee





-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* [bisect result] Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24  6:03       ` Daniel Vetter
                           ` (2 preceding siblings ...)
  2014-04-24 19:28         ` [partial bisect] " Pavel Machek
@ 2014-04-24 19:40         ` Pavel Machek
  2014-04-24 20:15           ` Chris Wilson
  2014-04-24 20:13         ` [PATCH] fix " Pavel Machek
  4 siblings, 1 reply; 20+ messages in thread
From: Pavel Machek @ 2014-04-24 19:40 UTC (permalink / raw)
  To: Daniel Vetter
  Cc: Chris Wilson, intel-gfx, Rafael J. Wysocki, dri-devel,
	kernel list, Jiri Kosina

Hi!

> And if you can indeed reliably reproduce this a bisect could be really useful.

And we have a winner here :-)

Ok, it was not as painfull as I feared.

It does not revert cleanly, but doing it by hand was not that bad.

Best regards,
   	    	   	    	      	    	     	 Pavel

a51435a3137ad8ae75c288c39bd2d8b2696bae8f is the first bad commit
commit a51435a3137ad8ae75c288c39bd2d8b2696bae8f
Author: Naresh Kumar Kachhi <naresh.kumar.kachhi@intel.com>
Date:   Wed Mar 12 16:39:40 2014 +0530

    drm/i915: disable rings before HW status page setup
    
    Rings should be idle before issuing sync_flush
    (in intel_ring_setup_status_page). This patch moves the ring
    disabling before doing the HW status page setup.
    
    Signed-off-by: Naresh Kumar Kachhi <naresh.kumar.kachhi@intel.com>
    Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

:040000 040000 23f2763fe684882008ca395f38d0da1cf197a85e
f1052c959b35a99ceae9886603086c09edee5df8 M	drivers
pavel@amd:/data/l/linux-good$ 


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: [bisect result] Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24 19:40         ` [bisect result] " Pavel Machek
@ 2014-04-24 20:15           ` Chris Wilson
  2014-04-24 22:00             ` Pavel Machek
  2014-04-24 22:06             ` Pavel Machek
  0 siblings, 2 replies; 20+ messages in thread
From: Chris Wilson @ 2014-04-24 20:15 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Daniel Vetter, intel-gfx, Rafael J. Wysocki, dri-devel,
	kernel list, Jiri Kosina

On Thu, Apr 24, 2014 at 09:40:38PM +0200, Pavel Machek wrote:
> Hi!
> 
> > And if you can indeed reliably reproduce this a bisect could be really useful.
> 
> And we have a winner here :-)
> 
> Ok, it was not as painfull as I feared.
> 
> It does not revert cleanly, but doing it by hand was not that bad.

Oh my. That is bizarre, can you check whether you have

commit 9991ae787a0c87fe7c783b4b6f4754c3cdbb6213
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Apr 2 16:36:07 2014 +0100

    drm/i915: Move all ring resets before setting the HWS page

in your latest kernel? That just makes

> commit a51435a3137ad8ae75c288c39bd2d8b2696bae8f
> Author: Naresh Kumar Kachhi <naresh.kumar.kachhi@intel.com>
> Date:   Wed Mar 12 16:39:40 2014 +0530
> 
>     drm/i915: disable rings before HW status page setup

more consistent wrt g4x.

To confirm, on drm-intel-nightly you used a patch like:

diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
index 36a62af..ce6186a 100644
--- a/drivers/gpu/drm/i915/intel_ringbuffer.c
+++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
@@ -494,6 +494,11 @@ static int init_ring_common(struct intel_ring_buffer *ring)
               I915_READ_TAIL(ring),
               I915_READ_START(ring));
 
+       if (I915_NEED_GFX_HWS(dev))
+               intel_ring_setup_status_page(ring);
+       else
+               ring_setup_phys_status_page(ring);
+
        if (!stop_ring(ring)) {
                /* G45 ring initialization often fails to reset head to zero */
                DRM_DEBUG_KMS("%s head not reset to zero "
@@ -517,11 +522,6 @@ static int init_ring_common(struct intel_ring_buffer *ring)
                }
        }
 
-       if (I915_NEED_GFX_HWS(dev))
-               intel_ring_setup_status_page(ring);
-       else
-               ring_setup_phys_status_page(ring);
-
 reset:
        /* Initialize the ring. This must happen _after_ we've cleared the ring
         * registers with the above sequence (the readback of the HEAD registers


-- 
Chris Wilson, Intel Open Source Technology Centre

^ permalink raw reply related	[flat|nested] 20+ messages in thread

* Re: [bisect result] Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24 20:15           ` Chris Wilson
@ 2014-04-24 22:00             ` Pavel Machek
  2014-04-24 22:06             ` Pavel Machek
  1 sibling, 0 replies; 20+ messages in thread
From: Pavel Machek @ 2014-04-24 22:00 UTC (permalink / raw)
  To: Chris Wilson, Daniel Vetter, intel-gfx, Rafael J. Wysocki,
	dri-devel, kernel list, Jiri Kosina

Hi!

> > > And if you can indeed reliably reproduce this a bisect could be really useful.
> > 
> > And we have a winner here :-)
> > 
> > Ok, it was not as painfull as I feared.
> > 
> > It does not revert cleanly, but doing it by hand was not that bad.
> 
> Oh my. That is bizarre, can you check whether you have

> commit 9991ae787a0c87fe7c783b4b6f4754c3cdbb6213
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Wed Apr 2 16:36:07 2014 +0100
> 
>     drm/i915: Move all ring resets before setting the HWS page
> 
> in your latest kernel? That just makes

No, I don't have that one.

> To confirm, on drm-intel-nightly you used a patch like:

I did not use drm-intel-nightly, but 3.15-rc2, because
drm-intel-nightly did not work at all. (Netconsole is not that easy to
set up, and I'd prefer not debugging 2 problems at the same time.)

Let me check with my patch reverted and 9991ae applied.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: [bisect result] Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24 20:15           ` Chris Wilson
  2014-04-24 22:00             ` Pavel Machek
@ 2014-04-24 22:06             ` Pavel Machek
  2014-04-24 22:15               ` Jiri Kosina
  2014-04-25 11:33               ` Jani Nikula
  1 sibling, 2 replies; 20+ messages in thread
From: Pavel Machek @ 2014-04-24 22:06 UTC (permalink / raw)
  To: Chris Wilson, Daniel Vetter, intel-gfx, Rafael J. Wysocki,
	dri-devel, kernel list, Jiri Kosina

> On Thu, Apr 24, 2014 at 09:40:38PM +0200, Pavel Machek wrote:
> > Hi!
> > 
> > > And if you can indeed reliably reproduce this a bisect could be really useful.
> > 
> > And we have a winner here :-)
> > 
> > Ok, it was not as painfull as I feared.
> > 
> > It does not revert cleanly, but doing it by hand was not that bad.
> 
> Oh my. That is bizarre, can you check whether you have
> 
> commit 9991ae787a0c87fe7c783b4b6f4754c3cdbb6213

Yes, with that commit, graphics is back to working state. Please push
it to mainline soon -- it fixes a regression. Feel free  to add

Tested-by: Pavel Machek <pavel@ucw.cz>

Thanks,
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: [bisect result] Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24 22:06             ` Pavel Machek
@ 2014-04-24 22:15               ` Jiri Kosina
  2014-04-25 11:33               ` Jani Nikula
  1 sibling, 0 replies; 20+ messages in thread
From: Jiri Kosina @ 2014-04-24 22:15 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Chris Wilson, Daniel Vetter, intel-gfx, Rafael J. Wysocki,
	dri-devel, kernel list

On Fri, 25 Apr 2014, Pavel Machek wrote:

> > > And we have a winner here :-)
> > > 
> > > Ok, it was not as painfull as I feared.
> > > 
> > > It does not revert cleanly, but doing it by hand was not that bad.
> > 
> > Oh my. That is bizarre, can you check whether you have
> > 
> > commit 9991ae787a0c87fe7c783b4b6f4754c3cdbb6213
> 
> Yes, with that commit, graphics is back to working state. Please push
> it to mainline soon -- it fixes a regression. Feel free  to add

Alright, most of my testing has been done with that commit present 
(obviously, as I've been using Chris' branch that has this incorporated), 
so I have a different ring initialization problem than Pavel had.

-- 
Jiri Kosina
SUSE Labs


^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: [bisect result] Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24 22:06             ` Pavel Machek
  2014-04-24 22:15               ` Jiri Kosina
@ 2014-04-25 11:33               ` Jani Nikula
  1 sibling, 0 replies; 20+ messages in thread
From: Jani Nikula @ 2014-04-25 11:33 UTC (permalink / raw)
  To: Pavel Machek, Chris Wilson, Daniel Vetter, intel-gfx,
	Rafael J. Wysocki, dri-devel, kernel list, Jiri Kosina

On Fri, 25 Apr 2014, Pavel Machek <pavel@ucw.cz> wrote:
>> On Thu, Apr 24, 2014 at 09:40:38PM +0200, Pavel Machek wrote:
>> > Hi!
>> > 
>> > > And if you can indeed reliably reproduce this a bisect could be really useful.
>> > 
>> > And we have a winner here :-)
>> > 
>> > Ok, it was not as painfull as I feared.
>> > 
>> > It does not revert cleanly, but doing it by hand was not that bad.
>> 
>> Oh my. That is bizarre, can you check whether you have
>> 
>> commit 9991ae787a0c87fe7c783b4b6f4754c3cdbb6213
>
> Yes, with that commit, graphics is back to working state. Please push
> it to mainline soon -- it fixes a regression. Feel free  to add
>
> Tested-by: Pavel Machek <pavel@ucw.cz>

I cherry-picked and pushed

commit 9991ae787a0c87fe7c783b4b6f4754c3cdbb6213
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Apr 2 16:36:07 2014 +0100

    drm/i915: Move all ring resets before setting the HWS page

to -fixes. Thanks for testing.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

^ permalink raw reply	[flat|nested] 20+ messages in thread

* [PATCH] fix i915 regression: only top 20% of screen works in X
  2014-04-24  6:03       ` Daniel Vetter
                           ` (3 preceding siblings ...)
  2014-04-24 19:40         ` [bisect result] " Pavel Machek
@ 2014-04-24 20:13         ` Pavel Machek
  4 siblings, 0 replies; 20+ messages in thread
From: Pavel Machek @ 2014-04-24 20:13 UTC (permalink / raw)
  To: Daniel Vetter
  Cc: Chris Wilson, intel-gfx, Rafael J. Wysocki, dri-devel,
	kernel list, Jiri Kosina


Fix regression where only 20% of screen works in X. This is manual
revert of a51435a3137ad8ae75c288c39bd2d8b2696bae8f.

Signed-off-by: Pavel Machek <pavel@ucw.cz>


diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
index 6bc68bd..cf63c67 100644
--- a/drivers/gpu/drm/i915/intel_ringbuffer.c
+++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
@@ -447,6 +447,11 @@ static int init_ring_common(struct intel_ring_buffer *ring)
 
 	gen6_gt_force_wake_get(dev_priv, FORCEWAKE_ALL);
 
+	if (I915_NEED_GFX_HWS(dev))
+		intel_ring_setup_status_page(ring);
+	else
+		ring_setup_phys_status_page(ring);
+
 	/* Stop the ring if it's running. */
 	I915_WRITE_CTL(ring, 0);
 	I915_WRITE_HEAD(ring, 0);
@@ -454,11 +459,6 @@ static int init_ring_common(struct intel_ring_buffer *ring)
 	if (wait_for_atomic((I915_READ_MODE(ring) & MODE_IDLE) != 0, 1000))
 		DRM_ERROR("%s :timed out trying to stop ring\n", ring->name);
 
-	if (I915_NEED_GFX_HWS(dev))
-		intel_ring_setup_status_page(ring);
-	else
-		ring_setup_phys_status_page(ring);
-
 	head = I915_READ_HEAD(ring) & HEAD_ADDR;
 
 	/* G45 ring initialization fails to reset head to zero */


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply related	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24  5:50     ` Chris Wilson
  2014-04-24  6:03       ` Daniel Vetter
@ 2014-04-24 10:42       ` Pavel Machek
  2014-04-24 11:39         ` Jiri Kosina
  1 sibling, 1 reply; 20+ messages in thread
From: Pavel Machek @ 2014-04-24 10:42 UTC (permalink / raw)
  To: Chris Wilson, Daniel Vetter, intel-gfx, Rafael J. Wysocki,
	dri-devel, kernel list, Jiri Kosina

Hi!

> > > > After update to 3.15-rc2, only top 20% of screen works on X.
> > > >
> > > > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > > > Integrated Graphics Controller (rev 03)
> > > >
> > > > 00:02.1 Display controller: Intel Corporation 4 Series Chipset
> > > > Integrated Graphics Controller (rev 03)
> > > >            Subsystem: Intel Corporation Device d614
> > > >            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > > >            ParErr- Stepping- SERR- FastB2B- DisINTx-
> > > >            Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
> > > >            >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> > > >            Latency: 0
> > > >            Region 0: Memory at d0400000 (64-bit, non-prefetchable)
> > > >            [size=1M]
> > > >            Capabilities: <access denied>
> > > >
> > > > This worked before. I believe it worked in 3.14. It definitely works
> > > > in 3.11-rc2.
> > > 
> > > Screenshot or more detailed description of what "only top 20% of
> > > screen works in X" means?
> > > Anything in dmesg?
> > 
> > Actually yes, dmesg suggests it is quite
> > sick. drivers/gpu/drm/drm_mm.c:767 warning triggered
> > repeatedly. Also.. initial framebuffer does not work ; I don't seem to
> > see anything before X start up. (This is Debian 6.0.9)
> 
> That says that i915.ko failed to initialise the GPU (or rather the GPU
> wasn't responding) and bailed during module load. The key line here is

> [drm:init_ring_common] *ERROR* render ring initialization failed ctl
> 0001f001 head 00002034 tail 00000000 start 0012f000

Actually, I'm not using modules -- everything is build-in. Can you try
that config? Perhaps you can then reproduce the failure.

> Jiri has been seeing a similar issue creep in during resume, but it is
> not reliable enough to bisect. Is your boot failure reliable enough to
> bisect? Also drm-intel-nightly should mitigate this failure and allow
> i915.ko to continue to load and run X, which would be worth testing to
> make sure that works as intended.

So far it failed 100% of time, but this is my main machine, so
bringing it down for extended periods is no-no.

Greetings to Prague :-). Jiri, do you have  i915 a module or build-in?

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
  2014-04-24 10:42       ` 3.15-rc2: " Pavel Machek
@ 2014-04-24 11:39         ` Jiri Kosina
  0 siblings, 0 replies; 20+ messages in thread
From: Jiri Kosina @ 2014-04-24 11:39 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Chris Wilson, Daniel Vetter, intel-gfx, Rafael J. Wysocki,
	dri-devel, kernel list

On Thu, 24 Apr 2014, Pavel Machek wrote:

> > That says that i915.ko failed to initialise the GPU (or rather the GPU 
> > wasn't responding) and bailed during module load. The key line here is
> 
> > [drm:init_ring_common] *ERROR* render ring initialization failed ctl
> > 0001f001 head 00002034 tail 00000000 start 0012f000
> 
> Actually, I'm not using modules -- everything is build-in. Can you try
> that config? Perhaps you can then reproduce the failure.

> > Jiri has been seeing a similar issue creep in during resume, but it is 
> > not reliable enough to bisect. Is your boot failure reliable enough to 
> > bisect? Also drm-intel-nightly should mitigate this failure and allow 
> > i915.ko to continue to load and run X, which would be worth testing to 
> > make sure that works as intended.
> 
> So far it failed 100% of time, but this is my main machine, so
> bringing it down for extended periods is no-no.
> 
> Greetings to Prague :-). Jiri, do you have  i915 a module or build-in?

Hi there Pavel, long time no see :)

I have i915 built as a module.

The thing is, that I can't really bisect this; the problem is, that I've 
started seeing this quite a long time ago, but only very sporadically 
(something like once in 40 resumes). But it was getting gradually worse 
and worse with newer kernels, and with current tree (both Linus' tree and 
drm-intel-testing), I am getting it 100% reproducibly on every resume.

This makes bisection completely impossible though.

-- 
Jiri Kosina

^ permalink raw reply	[flat|nested] 20+ messages in thread

end of thread, other threads:[~2014-04-25 11:33 UTC | newest]

Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-23 20:22 3.15-rc2: i915 regression: only top 20% of screen works in X Pavel Machek
2014-04-23 21:09 ` Daniel Vetter
2014-04-23 22:03   ` Pavel Machek
2014-04-23 22:09   ` Pavel Machek
2014-04-24  5:50     ` Chris Wilson
2014-04-24  6:03       ` Daniel Vetter
2014-04-24 13:36         ` Pavel Machek
2014-04-24 13:56           ` Jiri Kosina
2014-04-24 13:43         ` Pavel Machek
2014-04-24 15:03           ` Chris Wilson
2014-04-24 19:28         ` [partial bisect] " Pavel Machek
2014-04-24 19:40         ` [bisect result] " Pavel Machek
2014-04-24 20:15           ` Chris Wilson
2014-04-24 22:00             ` Pavel Machek
2014-04-24 22:06             ` Pavel Machek
2014-04-24 22:15               ` Jiri Kosina
2014-04-25 11:33               ` Jani Nikula
2014-04-24 20:13         ` [PATCH] fix " Pavel Machek
2014-04-24 10:42       ` 3.15-rc2: " Pavel Machek
2014-04-24 11:39         ` Jiri Kosina

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox