Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-04-12 Thread Oliver Pinter 
On 4/12/16, Edward Tomasz Napierała  wrote:
> I have the exact same problem on T420.  Switching consoles back and forth
> works as a workaround.


I have the same issue on my HP Probook 430G1 (Haswell GPU).


>
> On 0411T1633, Adrian Chadd wrote:
>> hiya,
>>
>> My x230 backlight doesn't come back on after I suspend/resume :( Any
>> ideas? does it work fine for you?
>>
>>
>>
>> -adrian
>>
>>
>> On 9 March 2016 at 17:31, Conrad Meyer  wrote:
>> > On Wed, Mar 9, 2016 at 12:48 PM, Adrian Chadd 
>> > wrote:
>> >> Woo!
>> >>
>> >> Just so its' not lost - people in irc have found power consumption has
>> >> jumped dramatically since this commit. :(
>> >
>> > For the record, on X230 (Ivybridge) I actually see lower power
>> > consumption with the new 3.8 kms:
>> >
>> > (All at brightness 100)
>> > Old kernel, no KMS:  11W
>> > Old kernel, KMS:  13W
>> > New kernel, no KMS:  11W
>> > New kernel, KMS:  11W
>> >
>> > With brightness down to minimum (5%):
>> > New kernel, KMS:  8.9W
>> >
>> > Best,
>> > Conrad
>>
> ___
> svn-src-h...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/svn-src-head
> To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
>
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-04-12 Thread John Baldwin 
On Tuesday, April 12, 2016 08:17:35 AM Adrian Chadd wrote:
> So, if I suspend in /xorg/, it works. but if I suspend now in vt, it
> doesn't work.
> 
> (Yes, vt + i915kms..)

I can confirm the same on my x220 (and this is a regression).  Switching
over to another ttyv and back "fixes" it as trasz@ noted.  I think the issue
isn't that the backlight isn't on; I think it's that the frame buffer contents
aren't restored properly and are left as all black when resuming on the
console.

-- 
John Baldwin
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-04-12 Thread Adrian Chadd 
So, if I suspend in /xorg/, it works. but if I suspend now in vt, it
doesn't work.

(Yes, vt + i915kms..)


-a
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-04-12 Thread Edward Tomasz Napierała 
I have the exact same problem on T420.  Switching consoles back and forth
works as a workaround.

On 0411T1633, Adrian Chadd wrote:
> hiya,
> 
> My x230 backlight doesn't come back on after I suspend/resume :( Any
> ideas? does it work fine for you?
> 
> 
> 
> -adrian
> 
> 
> On 9 March 2016 at 17:31, Conrad Meyer  wrote:
> > On Wed, Mar 9, 2016 at 12:48 PM, Adrian Chadd  
> > wrote:
> >> Woo!
> >>
> >> Just so its' not lost - people in irc have found power consumption has
> >> jumped dramatically since this commit. :(
> >
> > For the record, on X230 (Ivybridge) I actually see lower power
> > consumption with the new 3.8 kms:
> >
> > (All at brightness 100)
> > Old kernel, no KMS:  11W
> > Old kernel, KMS:  13W
> > New kernel, no KMS:  11W
> > New kernel, KMS:  11W
> >
> > With brightness down to minimum (5%):
> > New kernel, KMS:  8.9W
> >
> > Best,
> > Conrad
> 
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-04-12 Thread Jean-Sébastien Pédron 
On 12/04/2016 01:33, Adrian Chadd wrote:
> hiya,

Hi!

> My x230 backlight doesn't come back on after I suspend/resume :( Any
> ideas? does it work fine for you?

I don't know, I never had a single laptop where suspend/resume worked :(

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-04-11 Thread Conrad Meyer 
I haven't tried suspend/resume on the X230, sorry.

Conrad

On Mon, Apr 11, 2016 at 4:33 PM, Adrian Chadd  wrote:
> hiya,
>
> My x230 backlight doesn't come back on after I suspend/resume :( Any
> ideas? does it work fine for you?
>
>
>
> -adrian
>
>
> On 9 March 2016 at 17:31, Conrad Meyer  wrote:
>> On Wed, Mar 9, 2016 at 12:48 PM, Adrian Chadd  wrote:
>>> Woo!
>>>
>>> Just so its' not lost - people in irc have found power consumption has
>>> jumped dramatically since this commit. :(
>>
>> For the record, on X230 (Ivybridge) I actually see lower power
>> consumption with the new 3.8 kms:
>>
>> (All at brightness 100)
>> Old kernel, no KMS:  11W
>> Old kernel, KMS:  13W
>> New kernel, no KMS:  11W
>> New kernel, KMS:  11W
>>
>> With brightness down to minimum (5%):
>> New kernel, KMS:  8.9W
>>
>> Best,
>> Conrad
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-04-11 Thread Adrian Chadd 
hiya,

My x230 backlight doesn't come back on after I suspend/resume :( Any
ideas? does it work fine for you?



-adrian


On 9 March 2016 at 17:31, Conrad Meyer  wrote:
> On Wed, Mar 9, 2016 at 12:48 PM, Adrian Chadd  wrote:
>> Woo!
>>
>> Just so its' not lost - people in irc have found power consumption has
>> jumped dramatically since this commit. :(
>
> For the record, on X230 (Ivybridge) I actually see lower power
> consumption with the new 3.8 kms:
>
> (All at brightness 100)
> Old kernel, no KMS:  11W
> Old kernel, KMS:  13W
> New kernel, no KMS:  11W
> New kernel, KMS:  11W
>
> With brightness down to minimum (5%):
> New kernel, KMS:  8.9W
>
> Best,
> Conrad
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Conrad Meyer 
On Wed, Mar 9, 2016 at 12:48 PM, Adrian Chadd  wrote:
> Woo!
>
> Just so its' not lost - people in irc have found power consumption has
> jumped dramatically since this commit. :(

For the record, on X230 (Ivybridge) I actually see lower power
consumption with the new 3.8 kms:

(All at brightness 100)
Old kernel, no KMS:  11W
Old kernel, KMS:  13W
New kernel, no KMS:  11W
New kernel, KMS:  11W

With brightness down to minimum (5%):
New kernel, KMS:  8.9W

Best,
Conrad
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Renato Botelho 
> On Mar 9, 2016, at 20:10, Renato Botelho  wrote:
> 
>> On Mar 9, 2016, at 19:47, Jean-Sébastien Pédron  wrote:
>> 
>> On 09/03/2016 16:58, Renato Botelho wrote:
>>> After revert it to r296547 and manually apply ZFS fix I can
>>> successfully load i915kms during boot.
>> 
>> Yeah, I never test to load DRM drivers from /boot/loader.conf. I confirm
>> it doesn't work with Haswell at least. I have no idea how to debug this.
>> 
>> Is it sufficient for you to load the driver from /etc/rc.conf instead?
>> You can try the following line:
>>   kld_list="i915kms"
>> 
>> It achieves the same result, but it's faster to boot and works.
> 
> Didn’t know about it, I’ll start using it and will let you know. Thanks!

It works, thanks!

--
Renato Botelho



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Renato Botelho 
> On Mar 9, 2016, at 19:47, Jean-Sébastien Pédron  wrote:
> 
> On 09/03/2016 16:58, Renato Botelho wrote:
>> After revert it to r296547 and manually apply ZFS fix I can
>> successfully load i915kms during boot.
> 
> Yeah, I never test to load DRM drivers from /boot/loader.conf. I confirm
> it doesn't work with Haswell at least. I have no idea how to debug this.
> 
> Is it sufficient for you to load the driver from /etc/rc.conf instead?
> You can try the following line:
>kld_list="i915kms"
> 
> It achieves the same result, but it's faster to boot and works.

Didn’t know about it, I’ll start using it and will let you know. Thanks!

--
Renato Botelho



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Jean-Sébastien Pédron 
On 09/03/2016 21:48, Adrian Chadd wrote:
> Woo!
> 
> Just so its' not lost - people in irc have found power consumption has
> jumped dramatically since this commit. :(

Ed Maste posted a message to freebsd-x11@ with measurements for those
interested.

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Jean-Sébastien Pédron 
On 09/03/2016 16:58, Renato Botelho wrote:
> After revert it to r296547 and manually apply ZFS fix I can
> successfully load i915kms during boot.

Yeah, I never test to load DRM drivers from /boot/loader.conf. I confirm
it doesn't work with Haswell at least. I have no idea how to debug this.

Is it sufficient for you to load the driver from /etc/rc.conf instead?
You can try the following line:
kld_list="i915kms"

It achieves the same result, but it's faster to boot and works.

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Adrian Chadd 
Woo!

Just so its' not lost - people in irc have found power consumption has
jumped dramatically since this commit. :(


-adrian
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Renato Botelho 
> On Mar 9, 2016, at 12:58, Renato Botelho  wrote:
> 
>> On Mar 9, 2016, at 12:33, Renato Botelho  wrote:
>> 
>>> On Mar 9, 2016, at 08:07, Jean-Sébastien Pédron  
>>> wrote:
>>> 
>>> On 09/03/2016 10:48, Renato Botelho wrote:
 
 I cannot boot anymore after moving to this revision. My laptop is a 
 ThinkPad T430 (IvyBridge).
>>> 
>>> Hi!
>>> 
>>> Could you please test the following things?
>>> 
>>> 1. Try to boot without loading i915kms from /boot/loader.conf, then
>>> kldload it manually and see what happens.
>> 
>> It works fine if I load it after boot.
>> 
>>> 2. Try to boot a kernel built with the parent commit
>> 
>> I’ll revert tree to parent commit, apply ZFS fix manually and rebuild then I 
>> will let you know
> 
> After revert it to r296547 and manually apply ZFS fix I can successfully load 
> i915kms during boot.
> 
> Just let me know what I can do to help from now to collect all the data you 
> need. I’ll move it to recent -current and load i915kms after boot.

Here is dmesg output on r296567, loading i915kms after boot and running startx:

Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.0-CURRENT #6 r296567: Wed Mar  9 15:08:44 BRT 2016
root@:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 
3.8.0)
WARNING: WITNESS option enabled, expect reduced performance.
VT(efifb): resolution 640x480
CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (2494.39-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306a9  Family=0x6  Model=0x3a  Stepping=9
  
Features=0xbfebfbff
  
Features2=0x7fbae3bf
  AMD Features=0x28100800
  AMD Features2=0x1
  Structured Extended Features=0x281
  XSAVE Features=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 12884901888 (12288 MB)
avail memory = 12233527296 (11666 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
random: unblocking device.
ioapic0  irqs 0-23 on motherboard
random: entropy device external interface
kbd1 at kbdmux0
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0x80efff90, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi_ec0:  port 0x62,0x66 on acpi0
acpi0: Power Button (fixed)
cpu0:  on acpi0
cpu1:  on acpi0
cpu2:  on acpi0
cpu3:  on acpi0
attimer0:  port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Event timer "HPET4" frequency 14318180 Hz quality 440
atrtc0:  port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_lid0:  on acpi0
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
vgapci0:  port 0x6000-0x603f mem 
0xf000-0xf03f,0xe000-0xefff at device 2.0 on pci0
agp0:  on vgapci0
agp0: aperture size is 256M, detected 65532k stolen memory
vgapci0: Boot video device
xhci0:  mem 0xf252-0xf252 at 
device 20.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
xhci0: Port routing mask set to 0x
usbus0 on xhci0
pci0:  at device 22.0 (no driver attached)
em0:  port 0x6080-0x609f mem 
0xf250-0xf251,0xf253b000-0xf253bfff at device 25.0 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: 00:21:cc:ca:81:68
em0: netmap queues/slots: TX 1/1024, RX 1/1024
ehci0:  mem 0xf253a000-0xf253a3ff at 
device 26.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
hdac0:  mem 0xf253-0xf2533fff at device 
27.0 on pci0
pcib1:  at device 28.0 on pci0
pci1:  on pcib1
sdhci_pci0:  mem 0xf1d0-0xf1d000ff at device 0.0 on pci1
sdhci_pci0: 1 slot(s) allocated
pcib2:  at device 28.1 on pci0

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Adrian Chadd 
Hm, I thought some of the drm code required interrupts to be up for
i2c transactions to complete?

Maybe it's gotten worse in the later linux kernel versions?



-adrian
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Renato Botelho 
> On Mar 9, 2016, at 12:33, Renato Botelho  wrote:
> 
>> On Mar 9, 2016, at 08:07, Jean-Sébastien Pédron  wrote:
>> 
>> On 09/03/2016 10:48, Renato Botelho wrote:
 Author: dumbbell
 Date: Tue Mar  8 20:33:02 2016
 New Revision: 296548
 URL: https://svnweb.freebsd.org/changeset/base/296548
 
 Log:
 drm/i915: Update to match Linux 3.8.13
>>> 
>>> I cannot boot anymore after moving to this revision. My laptop is a 
>>> ThinkPad T430 (IvyBridge).
>> 
>> Hi!
>> 
>> Could you please test the following things?
>> 
>> 1. Try to boot without loading i915kms from /boot/loader.conf, then
>>  kldload it manually and see what happens.
> 
> It works fine if I load it after boot.
> 
>> 2. Try to boot a kernel built with the parent commit
> 
> I’ll revert tree to parent commit, apply ZFS fix manually and rebuild then I 
> will let you know

After revert it to r296547 and manually apply ZFS fix I can successfully load 
i915kms during boot.

Just let me know what I can do to help from now to collect all the data you 
need. I’ll move it to recent -current and load i915kms after boot.
--
Renato Botelho



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Emmanuel Vadot 
On Wed, 9 Mar 2016 06:48:31 -0300
Renato Botelho  wrote:

> > On Mar 8, 2016, at 17:33, Jean-Sébastien Pédron  
> > wrote:
> > 
> > Author: dumbbell
> > Date: Tue Mar  8 20:33:02 2016
> > New Revision: 296548
> > URL: https://svnweb.freebsd.org/changeset/base/296548
> > 
> > Log:
> >  drm/i915: Update to match Linux 3.8.13
> > 
> >  This update brings initial support for Haswell GPUs.
> > 
> >  Tested by: Many users of FreeBSD, PC-BSD and HardenedBSD
> >  Relnotes:  yes
> >  Sponsored by:  The FreeBSD Foundation
> >  Differential Revision: https://reviews.freebsd.org/D5554
> 
> I cannot boot anymore after moving to this revision. My laptop is a ThinkPad 
> T430 (IvyBridge).
> 
> I got some warnings like
> 
> info: [drm] MTRR allocation failed.  Graphics performance may suffer.
> 
> and in the end it just stops with these last 3 messages:
> 
> info: [drm] MSI enabled 1 message(s)
> info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> info: [drm] Driver supports precise vblank timestamp query.
> 
> And never pass this point.
> 
> By default I?m using GENERIC-NODEBUG, I?ll boot with old kernel and rebuild 
> it using GENERIC to make sure I can collect more data.
> --
> Renato Botelho

 I think that I have the same problem (but with haswell)

 When I load manually i915kms I don't have any problem but there is still some 
error message printed :
info: [drm] Initialized drm 1.1.0 20060810
drmn0:  on vgapci0
info: [drm] Memory usable by graphics device = 2048M
info: [drm] MTRR allocation failed.  Graphics performance may suffer.
iicbus0: error: [drm:pid697:i915_write32] *ERROR* Unknown 
unclaimed register before writing to c5100
 on iicbb0 addr 0xff
iic0:  on iicbus0
iic1:  on iicbus1
iicbus2:  on iicbb1 addr 0x0
iic2:  on iicbus2
iic3:  on iicbus3
iicbus4:  on iicbb2 addr 0x0
iic4:  on iicbus4
iic5:  on iicbus5
iicbus6:  on iicbb3 addr 0x0
iic6:  on iicbus6
iic7:  on iicbus7
iicbus8:  on iicbb4 addr 0x0
iic8:  on iicbus8
iic9:  on iicbus9
iicbus10:  on iicbb5 addr 0x0
iic10:  on iicbus10
iic11:  on iicbus11
info: [drm] MSI enabled 1 message(s)
info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
info: [drm] Driver supports precise vblank timestamp query.
error: [drm:pid697:lpt_init_pch_refclk] *ERROR* FDI mPHY reset assert timeout
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error: [drm:pid697:intel_sbi_write] *ERROR* timeout waiting for SBI to complete 
write transaction
error: [drm:pid697:intel_sbi_read] *ERROR* timeout waiting for SBI to complete 
read transaction
error:

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Renato Botelho 
> On Mar 9, 2016, at 08:07, Jean-Sébastien Pédron  wrote:
> 
> On 09/03/2016 10:48, Renato Botelho wrote:
>>> Author: dumbbell
>>> Date: Tue Mar  8 20:33:02 2016
>>> New Revision: 296548
>>> URL: https://svnweb.freebsd.org/changeset/base/296548
>>> 
>>> Log:
>>> drm/i915: Update to match Linux 3.8.13
>> 
>> I cannot boot anymore after moving to this revision. My laptop is a ThinkPad 
>> T430 (IvyBridge).
> 
> Hi!
> 
> Could you please test the following things?
> 
> 1. Try to boot without loading i915kms from /boot/loader.conf, then
>   kldload it manually and see what happens.

It works fine if I load it after boot.

> 2. Try to boot a kernel built with the parent commit

I’ll revert tree to parent commit, apply ZFS fix manually and rebuild then I 
will let you know

--
Renato Botelho



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Jean-Sébastien Pédron 
On 09/03/2016 12:29, Renato Botelho wrote:
> Looks like something broke the system completely, I’m getting core 
> dumps on ZFS and cannot mount all my partitions. Maybe this could be
> > the cause of the problems with i915 too.

The ZFS issue is fixed in r296563.

See:
https://lists.freebsd.org/pipermail/freebsd-current/2016-March/060037.html

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Renato Botelho 
> On Mar 9, 2016, at 08:07, Jean-Sébastien Pédron  wrote:
> 
> On 09/03/2016 10:48, Renato Botelho wrote:
>>> Author: dumbbell
>>> Date: Tue Mar  8 20:33:02 2016
>>> New Revision: 296548
>>> URL: https://svnweb.freebsd.org/changeset/base/296548
>>> 
>>> Log:
>>> drm/i915: Update to match Linux 3.8.13
>> 
>> I cannot boot anymore after moving to this revision. My laptop is a ThinkPad 
>> T430 (IvyBridge).
> 
> Hi!
> 
> Could you please test the following things?
> 
> 1. Try to boot without loading i915kms from /boot/loader.conf, then
>   kldload it manually and see what happens.
> 2. Try to boot a kernel built with the parent commit

Looks like something broke the system completely, I’m getting core dumps on ZFS 
and cannot mount all my partitions. Maybe this could be the cause of the 
problems with i915 too.

I’ll work on recovering my system to a good state and then I will do a bisect 
to detect if this particular revision really broke it and will let you know.

Thanks
--
Renato Botelho



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Jean-Sébastien Pédron 
On 09/03/2016 10:48, Renato Botelho wrote:
>> Author: dumbbell
>> Date: Tue Mar  8 20:33:02 2016
>> New Revision: 296548
>> URL: https://svnweb.freebsd.org/changeset/base/296548
>>
>> Log:
>>  drm/i915: Update to match Linux 3.8.13
> 
> I cannot boot anymore after moving to this revision. My laptop is a ThinkPad 
> T430 (IvyBridge).

Hi!

Could you please test the following things?

1. Try to boot without loading i915kms from /boot/loader.conf, then
   kldload it manually and see what happens.
2. Try to boot a kernel built with the parent commit

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature

Re: svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-09 Thread Renato Botelho 
> On Mar 8, 2016, at 17:33, Jean-Sébastien Pédron  wrote:
> 
> Author: dumbbell
> Date: Tue Mar  8 20:33:02 2016
> New Revision: 296548
> URL: https://svnweb.freebsd.org/changeset/base/296548
> 
> Log:
>  drm/i915: Update to match Linux 3.8.13
> 
>  This update brings initial support for Haswell GPUs.
> 
>  Tested by:   Many users of FreeBSD, PC-BSD and HardenedBSD
>  Relnotes:yes
>  Sponsored by:The FreeBSD Foundation
>  Differential Revision:   https://reviews.freebsd.org/D5554

I cannot boot anymore after moving to this revision. My laptop is a ThinkPad 
T430 (IvyBridge).

I got some warnings like

info: [drm] MTRR allocation failed.  Graphics performance may suffer.

and in the end it just stops with these last 3 messages:

info: [drm] MSI enabled 1 message(s)
info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
info: [drm] Driver supports precise vblank timestamp query.

And never pass this point.

By default I’m using GENERIC-NODEBUG, I’ll boot with old kernel and rebuild it 
using GENERIC to make sure I can collect more data.
--
Renato Botelho

___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

svn commit: r296548 - in head/sys: dev/agp dev/drm2 dev/drm2/i915 modules/drm2/i915kms

2016-03-08 Thread Jean-Sébastien Pédron 
Author: dumbbell
Date: Tue Mar  8 20:33:02 2016
New Revision: 296548
URL: https://svnweb.freebsd.org/changeset/base/296548

Log:
  drm/i915: Update to match Linux 3.8.13
  
  This update brings initial support for Haswell GPUs.
  
  Tested by:Many users of FreeBSD, PC-BSD and HardenedBSD
  Relnotes: yes
  Sponsored by: The FreeBSD Foundation
  Differential Revision:https://reviews.freebsd.org/D5554

Added:
  head/sys/dev/drm2/drm_mem_util.h   (contents, props changed)
  head/sys/dev/drm2/i915/dvo.h   (contents, props changed)
  head/sys/dev/drm2/i915/dvo_ch7017.c   (contents, props changed)
  head/sys/dev/drm2/i915/dvo_ch7xxx.c   (contents, props changed)
  head/sys/dev/drm2/i915/dvo_ivch.c   (contents, props changed)
  head/sys/dev/drm2/i915/dvo_ns2501.c   (contents, props changed)
  head/sys/dev/drm2/i915/dvo_sil164.c   (contents, props changed)
  head/sys/dev/drm2/i915/dvo_tfp410.c   (contents, props changed)
  head/sys/dev/drm2/i915/intel_acpi.c   (contents, props changed)
  head/sys/dev/drm2/i915/intel_dvo.c   (contents, props changed)
Modified:
  head/sys/dev/agp/agp_i810.c
  head/sys/dev/agp/agp_i810.h
  head/sys/dev/drm2/drmP.h
  head/sys/dev/drm2/drm_atomic.h
  head/sys/dev/drm2/drm_dp_iic_helper.c
  head/sys/dev/drm2/drm_drv.c
  head/sys/dev/drm2/drm_linux_list.h
  head/sys/dev/drm2/drm_os_freebsd.c
  head/sys/dev/drm2/drm_os_freebsd.h
  head/sys/dev/drm2/drm_pciids.h
  head/sys/dev/drm2/i915/i915_debug.c
  head/sys/dev/drm2/i915/i915_dma.c
  head/sys/dev/drm2/i915/i915_drm.h
  head/sys/dev/drm2/i915/i915_drv.c
  head/sys/dev/drm2/i915/i915_drv.h
  head/sys/dev/drm2/i915/i915_gem.c
  head/sys/dev/drm2/i915/i915_gem_context.c
  head/sys/dev/drm2/i915/i915_gem_evict.c
  head/sys/dev/drm2/i915/i915_gem_execbuffer.c
  head/sys/dev/drm2/i915/i915_gem_gtt.c
  head/sys/dev/drm2/i915/i915_gem_stolen.c
  head/sys/dev/drm2/i915/i915_gem_tiling.c
  head/sys/dev/drm2/i915/i915_irq.c
  head/sys/dev/drm2/i915/i915_reg.h
  head/sys/dev/drm2/i915/i915_suspend.c
  head/sys/dev/drm2/i915/intel_bios.c
  head/sys/dev/drm2/i915/intel_bios.h
  head/sys/dev/drm2/i915/intel_crt.c
  head/sys/dev/drm2/i915/intel_ddi.c
  head/sys/dev/drm2/i915/intel_display.c
  head/sys/dev/drm2/i915/intel_dp.c
  head/sys/dev/drm2/i915/intel_drv.h
  head/sys/dev/drm2/i915/intel_fb.c
  head/sys/dev/drm2/i915/intel_hdmi.c
  head/sys/dev/drm2/i915/intel_iic.c
  head/sys/dev/drm2/i915/intel_lvds.c
  head/sys/dev/drm2/i915/intel_modes.c
  head/sys/dev/drm2/i915/intel_opregion.c
  head/sys/dev/drm2/i915/intel_overlay.c
  head/sys/dev/drm2/i915/intel_panel.c
  head/sys/dev/drm2/i915/intel_pm.c
  head/sys/dev/drm2/i915/intel_ringbuffer.c
  head/sys/dev/drm2/i915/intel_ringbuffer.h
  head/sys/dev/drm2/i915/intel_sdvo.c
  head/sys/dev/drm2/i915/intel_sprite.c
  head/sys/dev/drm2/i915/intel_tv.c
  head/sys/modules/drm2/i915kms/Makefile

Modified: head/sys/dev/agp/agp_i810.c
==
--- head/sys/dev/agp/agp_i810.c Tue Mar  8 20:24:12 2016(r296547)
+++ head/sys/dev/agp/agp_i810.c Tue Mar  8 20:33:02 2016(r296548)
@@ -250,6 +250,10 @@ struct agp_i810_driver {
void (*chipset_flush)(device_t);
 };
 
+static struct {
+   struct intel_gtt base;
+} intel_private;
+
 static const struct agp_i810_driver agp_i810_i810_driver = {
.chiptype = CHIP_I810,
.gen = 1,
@@ -526,6 +530,29 @@ static const struct agp_i810_driver agp_
.chipset_flush = agp_i810_chipset_flush,
 };
 
+static const struct agp_i810_driver agp_i810_valleyview_driver = {
+   .chiptype = CHIP_SB,
+   .gen = 7,
+   .busdma_addr_mask_sz = 40,
+   .res_spec = agp_g4x_res_spec,
+   .check_active = agp_sb_check_active,
+   .set_desc = agp_i810_set_desc,
+   .dump_regs = agp_sb_dump_regs,
+   .get_stolen_size = agp_sb_get_stolen_size,
+   .get_gtt_mappable_entries = agp_i915_get_gtt_mappable_entries,
+   .get_gtt_total_entries = agp_sb_get_gtt_total_entries,
+   .install_gatt = agp_g4x_install_gatt,
+   .deinstall_gatt = agp_i830_deinstall_gatt,
+   .write_gtt = agp_sb_write_gtt,
+   .install_gtt_pte = agp_sb_install_gtt_pte,
+   .read_gtt_pte = agp_g4x_read_gtt_pte,
+   .read_gtt_pte_paddr = agp_sb_read_gtt_pte_paddr,
+   .set_aperture = agp_i915_set_aperture,
+   .chipset_flush_setup = agp_i810_chipset_flush_setup,
+   .chipset_flush_teardown = agp_i810_chipset_flush_teardown,
+   .chipset_flush = agp_i810_chipset_flush,
+};
+
 /* For adding new devices, devid is the id of the graphics controller
  * (pci:0:2:0, for example).  The placeholder (usually at pci:0:2:1) for the
  * second head should never be added.  The bridge_offset is the offset to
@@ -763,40 +790,200 @@ static const struct agp_i810_match {
},
{
.devid = 0x04028086,
-   .name = "Haswell desktop GT1",
+   .name = "Haswell GT1 desktop",
+   .driver =