Re: regression suspend/resume on Lenovo T420

2017-05-15 Thread Edward Tomasz Napierała
On 0515T2140, Konstantin Belousov wrote: > On Mon, May 15, 2017 at 06:37:58PM +0100, Edward Tomasz Napiera??a wrote: > > Thanks! The patch fixes resume for me, for both vt(4) and X11. > > Thanks everybody for testing, patch below should be committable, modulo > bugs. I did not tested it and ask

Re: regression suspend/resume on Lenovo T420

2017-05-15 Thread Manuel Stühn
On Mon, 15 May 2017 12:56:47 +0300, Konstantin Belousov wrote On Sun, May 14, 2017 at 08:02:52PM +, Poul-Henning Kamp wrote: In message <20170514193006.GA1298@brick>, Edward Tomasz =?utf-8?Q?Napiera=C5=82 a?= writes: I've tried to verify that, and sadly it wasn't it for me. The

Re: regression suspend/resume on Lenovo T420

2017-05-15 Thread Konstantin Belousov
On Mon, May 15, 2017 at 06:37:58PM +0100, Edward Tomasz Napiera??a wrote: > Thanks! The patch fixes resume for me, for both vt(4) and X11. Thanks everybody for testing, patch below should be committable, modulo bugs. I did not tested it and ask for the same test as the previous debugging patch.

Re: regression suspend/resume on Lenovo T420

2017-05-15 Thread Jonathan Anderson
On 15 May 2017, at 14:57, Konstantin Belousov wrote: On Mon, May 15, 2017 at 02:37:16PM -0230, Jonathan Anderson wrote: Running drm-next (which has -CURRENT last merged somewhere around r317651), this patch fixes one of the two problems I've been experiencing with suspend/resume. Definite

Re: regression suspend/resume on Lenovo T420

2017-05-15 Thread Edward Tomasz Napiera??a
On 0515T1256, Konstantin Belousov wrote: > On Sun, May 14, 2017 at 08:02:52PM +, Poul-Henning Kamp wrote: > > > > In message <20170514193006.GA1298@brick>, Edward Tomasz > > =?utf-8?Q?Napiera=C5=82 > > a?= writes: > > > > >I've tried to verify that, and sadly it wasn't it for me.

Re: regression suspend/resume on Lenovo T420

2017-05-15 Thread Pete Wright
On 05/15/2017 10:27, Konstantin Belousov wrote: On Mon, May 15, 2017 at 02:37:16PM -0230, Jonathan Anderson wrote: On 15 May 2017, at 7:26, Konstantin Belousov wrote: Try this. If it works, I will write a proper patch. diff --git a/sys/amd64/amd64/cpu_switch.S

Re: regression suspend/resume on Lenovo T420

2017-05-15 Thread Konstantin Belousov
On Mon, May 15, 2017 at 02:37:16PM -0230, Jonathan Anderson wrote: > On 15 May 2017, at 7:26, Konstantin Belousov wrote: > > > > Try this. If it works, I will write a proper patch. > > > > diff --git a/sys/amd64/amd64/cpu_switch.S > > b/sys/amd64/amd64/cpu_switch.S > > index

Re: regression suspend/resume on Lenovo T420

2017-05-15 Thread Jonathan Anderson
On 15 May 2017, at 7:26, Konstantin Belousov wrote: Try this. If it works, I will write a proper patch. diff --git a/sys/amd64/amd64/cpu_switch.S b/sys/amd64/amd64/cpu_switch.S index 33437ad16e6..9c0cd05ebea 100644 --- a/sys/amd64/amd64/cpu_switch.S +++ b/sys/amd64/amd64/cpu_switch.S @@

Re: regression suspend/resume on Lenovo T420

2017-05-15 Thread Konstantin Belousov
On Sun, May 14, 2017 at 08:02:52PM +, Poul-Henning Kamp wrote: > > In message <20170514193006.GA1298@brick>, Edward Tomasz > =?utf-8?Q?Napiera=C5=82 > a?= writes: > > >I've tried to verify that, and sadly it wasn't it for me. The commit > >that does break resume for me is r316767.

Re: regression suspend/resume on Lenovo T420

2017-05-14 Thread Poul-Henning Kamp
In message <20170514193006.GA1298@brick>, Edward Tomasz =?utf-8?Q?Napiera=C5=82 a?= writes: >I've tried to verify that, and sadly it wasn't it for me. The commit >that does break resume for me is r316767. The current -CURRENT with >this one commit reverted ("svn merge -c -r316767 .")

Re: regression suspend/resume on Lenovo T420

2017-05-14 Thread Edward Tomasz Napierała
ühn , > >>> Kopie: freebsd-current , > >>> Betreff: Re: regression suspend/resume on Lenovo T420 > >>> > >>> There were lots of commits that could break things. :-) > >>> > >>> > >>> Can you compile up some inter

Re: regression suspend/resume on Lenovo T420

2017-05-06 Thread Manuel Stühn
On Sat, May 06, 2017 at 10:52:56AM +0200, Manuel Stühn wrote: On Wed, 03 May 2017 22:28:41 +0200, Freebsdnewbie wrote Von: Adrian Chadd Gesendet: Mo. 01.05.2017 23:31 An: Manuel Stühn , Kopie: freebsd-current , Betreff: Re: regression suspend/resume on Lenovo T420 There were lots of commits

Re: regression suspend/resume on Lenovo T420

2017-05-06 Thread Manuel Stühn
On Wed, 03 May 2017 22:28:41 +0200, Freebsdnewbie wrote Von: Adrian Chadd Gesendet: Mo. 01.05.2017 23:31 An: Manuel Stühn , Kopie: freebsd-current , Betreff: Re: regression suspend/resume on Lenovo T420 There were lots of commits that could break things. :-) Can you compile up some

RE: Re: regression suspend/resume on Lenovo T420

2017-05-03 Thread freebsdnewbie
> Von: Adrian Chadd > Gesendet: Mo. 01.05.2017 23:31 > An: Manuel Stühn , > Kopie: freebsd-current , > Betreff: Re: regression suspend/resume on Lenovo T420 > > There were lots of commits that could break things. :-) > > > Can you compile up some interm

Re: regression suspend/resume on Lenovo T420

2017-05-03 Thread Pete Wright
On 05/01/2017 14:31, Adrian Chadd wrote: There were lots of commits that could break things. :-) Can you compile up some intermediary versions between 315141 and r317559 to find which commit range broke things? That'll make chasing it down much quicker! Thanks! Hey Adrian - I was looking

Re: regression suspend/resume on Lenovo T420

2017-05-02 Thread Pete Wright
On 05/01/2017 14:31, Adrian Chadd wrote: There were lots of commits that could break things. :-) Can you compile up some intermediary versions between 315141 and r317559 to find which commit range broke things? That'll make chasing it down much quicker! Thanks! FWIW I'm seeing this on the

Re: regression suspend/resume on Lenovo T420

2017-05-01 Thread Adrian Chadd
There were lots of commits that could break things. :-) Can you compile up some intermediary versions between 315141 and r317559 to find which commit range broke things? That'll make chasing it down much quicker! Thanks! -a On 29 April 2017 at 04:50, Manuel Stühn