On 17/05/2018 21:14, Pete Wright wrote:
>
>
> On 05/12/2018 19:25, Pete Wright wrote:
>> hi there - i have an amd64 laptop that's been running CURRENT for a while
>> using both drm-next and drm-stable for graphics. during the past week or so
>> i've run into issues with suspend resume...well tech
On 05/12/2018 19:25, Pete Wright wrote:
hi there - i have an amd64 laptop that's been running CURRENT for a
while using both drm-next and drm-stable for graphics. during the past
week or so i've run into issues with suspend resume...well technically
resume has stopped working. i've tested a
On 05/15/18 16:48, Pete Wright wrote:
On 05/14/2018 20:35, Theron wrote:
On 05/13/18 15:44, Pete Wright wrote:
so i've done a bit more debugging on my end. i've even installed
the 11.2-BETA branch last night since 11-STABLE worked without
issues about a month or so ago.
i've set "debug.ac
On 05/14/2018 20:35, Theron wrote:
On 05/13/18 15:44, Pete Wright wrote:
so i've done a bit more debugging on my end. i've even installed
the 11.2-BETA branch last night since 11-STABLE worked without
issues about a month or so ago.
i've set "debug.acpi.resume_beep=1" and when resuming aft
On 0514T1158, Andriy Gapon wrote:
> On 14/05/2018 11:44, Mikaël Urankar wrote:
> > Could it be the same problem described here?
> > https://lists.freebsd.org/pipermail/freebsd-hackers/2018-May/052778.html
>
> That problem is _not_ a regression.
FWIW, this machine (the one affected by the sluggish
On 05/13/18 15:44, Pete Wright wrote:
so i've done a bit more debugging on my end. i've even installed the
11.2-BETA branch last night since 11-STABLE worked without issues
about a month or so ago.
i've set "debug.acpi.resume_beep=1" and when resuming after entering
an S3 sleep state the bel
On 05/14/2018 01:18, Niclas Zeising wrote:
On 05/13/18 21:44, Pete Wright wrote:
On 05/13/2018 10:27, Pete Wright wrote:
On 05/13/2018 08:58, Theron wrote:
Hi!
I'm also seeing issues, not as severe as Pete, but after I resume
(which works, with drm-next and DMC firmware), the system bec
On 14/05/2018 11:44, Mikaël Urankar wrote:
> Could it be the same problem described here?
> https://lists.freebsd.org/pipermail/freebsd-hackers/2018-May/052778.html
That problem is _not_ a regression.
--
Andriy Gapon
___
freebsd-current@freebsd.org mai
2018-05-14 10:27 GMT+02:00 Niclas Zeising :
> On 05/14/18 10:06, Edward Tomasz Napierała wrote:
>
>> On 0513T1244, Pete Wright wrote:
>>
>>>
>>>
>>> On 05/13/2018 10:27, Pete Wright wrote:
>>>
On 05/13/2018 08:58, Theron wrote:
> Hi!
>> I'm also seeing issues, not as se
On 05/14/18 10:06, Edward Tomasz Napierała wrote:
On 0513T1244, Pete Wright wrote:
On 05/13/2018 10:27, Pete Wright wrote:
On 05/13/2018 08:58, Theron wrote:
Hi!
I'm also seeing issues, not as severe as Pete, but after I resume
(which works, with drm-next and DMC firmware), the system beco
On 05/13/18 17:58, Theron wrote:
Hi!
I'm also seeing issues, not as severe as Pete, but after I resume
(which works, with drm-next and DMC firmware), the system becomes
sluggish. It feels like I/O takes more time, and graphics are
sluggish (very sientific, I know, but for instance git operati
On 05/13/18 18:16, Michael Gmelin wrote:
On 13. May 2018, at 11:54, Niclas Zeising wrote:
On 05/13/18 09:48, Andriy Gapon wrote:
On 13/05/2018 05:25, Pete Wright wrote:
hi there - i have an amd64 laptop that's been running CURRENT for a while using
both drm-next and drm-stable for graphics
On 05/13/18 21:44, Pete Wright wrote:
On 05/13/2018 10:27, Pete Wright wrote:
On 05/13/2018 08:58, Theron wrote:
Hi!
I'm also seeing issues, not as severe as Pete, but after I resume
(which works, with drm-next and DMC firmware), the system becomes
sluggish. It feels like I/O takes more
On 0513T1244, Pete Wright wrote:
>
>
> On 05/13/2018 10:27, Pete Wright wrote:
> >
> >
> > On 05/13/2018 08:58, Theron wrote:
> >>> Hi!
> >>> I'm also seeing issues, not as severe as Pete, but after I resume
> >>> (which works, with drm-next and DMC firmware), the system becomes
> >>> sluggish.
On 05/13/2018 10:27, Pete Wright wrote:
On 05/13/2018 08:58, Theron wrote:
Hi!
I'm also seeing issues, not as severe as Pete, but after I resume
(which works, with drm-next and DMC firmware), the system becomes
sluggish. It feels like I/O takes more time, and graphics are
sluggish (very
> On 13. May 2018, at 11:54, Niclas Zeising wrote:
>
>> On 05/13/18 09:48, Andriy Gapon wrote:
>>> On 13/05/2018 05:25, Pete Wright wrote:
>>> hi there - i have an amd64 laptop that's been running CURRENT for a while
>>> using
>>> both drm-next and drm-stable for graphics. during the past week
On 05/13/2018 08:58, Theron wrote:
Hi!
I'm also seeing issues, not as severe as Pete, but after I resume
(which works, with drm-next and DMC firmware), the system becomes
sluggish. It feels like I/O takes more time, and graphics are
sluggish (very sientific, I know, but for instance git ope
Hi!
I'm also seeing issues, not as severe as Pete, but after I resume
(which works, with drm-next and DMC firmware), the system becomes
sluggish. It feels like I/O takes more time, and graphics are
sluggish (very sientific, I know, but for instance git operations are
much slower after a resum
On 05/13/18 09:48, Andriy Gapon wrote:
On 13/05/2018 05:25, Pete Wright wrote:
hi there - i have an amd64 laptop that's been running CURRENT for a while using
both drm-next and drm-stable for graphics. during the past week or so i've run
into issues with suspend resume...well technically resume
On 13/05/2018 05:25, Pete Wright wrote:
> hi there - i have an amd64 laptop that's been running CURRENT for a while
> using
> both drm-next and drm-stable for graphics. during the past week or so i've run
> into issues with suspend resume...well technically resume has stopped
> working.
> i've t
hi there - i have an amd64 laptop that's been running CURRENT for a
while using both drm-next and drm-stable for graphics. during the past
week or so i've run into issues with suspend resume...well technically
resume has stopped working. i've tested a couple configurations and
none have allowe
21 matches
Mail list logo
