Signed-off-by: Diego Viola
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index 573cf17262da..1b4b4f508662 100644
On Thu, Feb 25, 2021 at 2:22 AM Diego Viola wrote:
>
> Hi Ben,
>
> I can confirm that your last two patches[0][1] fix the timeout issues
> (those from a normal boot and from suspend/resume).
>
> [0]
> https://github.com/skeggsb/linux/commit/90224a17437b1f39dbecbb385567c1f
/0ee6dc49601359042fd254bbd8ba6b4685b4d0d7
Tested-by: Diego Viola
on both patches.
Thanks, I appreciate it a lot.
Diego
On Wed, Feb 24, 2021 at 6:50 AM Ben Skeggs wrote:
>
> On Wed, 17 Feb 2021 at 13:30, Alexandre Courbot wrote:
> >
> > On Wed, Feb 17, 2021 at 1:20 AM Diego Viola wrote:
> > >
> &g
Hi Ben,
On Wed, Feb 24, 2021 at 6:50 AM Ben Skeggs wrote:
>
> On Wed, 17 Feb 2021 at 13:30, Alexandre Courbot wrote:
> >
> > On Wed, Feb 17, 2021 at 1:20 AM Diego Viola wrote:
> > >
> > > This code times out on GP108, probably because the BIOS puts it into
This code times out on GP108, probably because the BIOS puts it into a
bad state.
Since we reset the PMU on driver load anyway, we are at no risk from
missing a response from it since we are not waiting for one to begin
with.
Signed-off-by: Diego Viola
---
drivers/gpu/drm/nouveau/nvkm/subdev
This code times out on GP108, probably because the BIOS puts it into a
bad state.
Since we reset the PMU on driver load anyway, we are at no risk from
missing a response from it since we are not waiting for one to begin
with.
Signed-off-by: Diego Viola
---
drivers/gpu/drm/nouveau/nvkm/subdev
.
v2: use drm_atomic_crtc_needs_modeset() (Daniel).
Cc: 1882...@bugs.launchpad.net
Fixes: 3954ff10e06e ("drm/virtio: skip set_scanout if framebuffer didn't
change")
Signed-off-by: Gerd Hoffmann
Tested-by: Jiri Slaby
Tested-by: Diego Viola
---
drivers/gpu/drm/virtio/virtgpu_display.c | 11
Hi Joerg,
On Thu, Jan 24, 2019 at 6:42 AM Joerg Roedel wrote:
>
> Hi Diego,
>
> thanks for the report!
You're welcome, many thanks for your quick reply.
>
> On Thu, Jan 24, 2019 at 01:57:31AM -0200, Diego Viola wrote:
> > [10499.577192] WARNING: CPU: 2 PID: 3487 at
-- Forwarded message -
From: Diego Viola
Date: Thu, Jan 24, 2019 at 1:57 AM
Subject: Nested KVM is broken on a AMD Ryzen 5 2400G
To: , ,
,
Hello,
I am trying to do nested KVM on a Ryzen 5 2400G, my use case is the following:
- Arch Linux as the host OS.
- Ubuntu 18.04.1
On Fri, Nov 30, 2018 at 5:30 PM Jarkko Sakkinen
wrote:
>
> In order to comply with the CoC, replace with a hug.
>
> Signed-off-by: Jarkko Sakkinen
> ---
> arch/parisc/kernel/sys_parisc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On Fri, Nov 30, 2018 at 5:30 PM Jarkko Sakkinen
wrote:
>
> In order to comply with the CoC, replace with a hug.
>
> Signed-off-by: Jarkko Sakkinen
> ---
> arch/parisc/kernel/sys_parisc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On Mon, Nov 12, 2018 at 5:42 PM Greg KH wrote:
>
> On Mon, Nov 12, 2018 at 05:22:52PM -0200, Diego Viola wrote:
> > med_power_with_dipm still causes freezes after updating the firmware to
> > the latest version (DXT04L5Q).
> >
> > Set model_rev to NULL and blacklist
On Mon, Nov 12, 2018 at 5:42 PM Greg KH wrote:
>
> On Mon, Nov 12, 2018 at 05:22:52PM -0200, Diego Viola wrote:
> > med_power_with_dipm still causes freezes after updating the firmware to
> > the latest version (DXT04L5Q).
> >
> > Set model_rev to NULL and blacklist
On Mon, Nov 12, 2018 at 5:30 PM Jens Axboe wrote:
>
> On 11/12/18 12:22 PM, Diego Viola wrote:
> > med_power_with_dipm still causes freezes after updating the firmware to
> > the latest version (DXT04L5Q).
> >
> > Set model_rev to NULL and blacklist the device.
>
On Mon, Nov 12, 2018 at 5:30 PM Jens Axboe wrote:
>
> On 11/12/18 12:22 PM, Diego Viola wrote:
> > med_power_with_dipm still causes freezes after updating the firmware to
> > the latest version (DXT04L5Q).
> >
> > Set model_rev to NULL and blacklist the device.
>
med_power_with_dipm still causes freezes after updating the firmware to
the latest version (DXT04L5Q).
Set model_rev to NULL and blacklist the device.
Signed-off-by: Diego Viola
Reviewed-by: Hans de Goede
---
drivers/ata/libata-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
med_power_with_dipm still causes freezes after updating the firmware to
the latest version (DXT04L5Q).
Set model_rev to NULL and blacklist the device.
Signed-off-by: Diego Viola
Reviewed-by: Hans de Goede
---
drivers/ata/libata-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
On Sun, Oct 28, 2018 at 11:34 AM Diego Viola wrote:
>
> med_power_with_dipm still causes freezes after updating the firmware to
> the latest version (DXT04L5Q).
>
> Set model_rev to NULL and blacklist the device.
>
> Signed-off-by: Diego Viola
> ---
> drivers/ata/lib
On Sun, Oct 28, 2018 at 11:34 AM Diego Viola wrote:
>
> med_power_with_dipm still causes freezes after updating the firmware to
> the latest version (DXT04L5Q).
>
> Set model_rev to NULL and blacklist the device.
>
> Signed-off-by: Diego Viola
> ---
> drivers/ata/lib
med_power_with_dipm still causes freezes after updating the firmware to
the latest version (DXT04L5Q).
Set model_rev to NULL and blacklist the device.
Signed-off-by: Diego Viola
---
drivers/ata/libata-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ata/libata
med_power_with_dipm still causes freezes after updating the firmware to
the latest version (DXT04L5Q).
Set model_rev to NULL and blacklist the device.
Signed-off-by: Diego Viola
---
drivers/ata/libata-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ata/libata
Hi Hans,
On Sun, Oct 28, 2018 at 7:48 AM Hans de Goede wrote:
>
> Hi,
>
> On 28-10-18 05:13, Diego Viola wrote:
> > On Fri, Oct 26, 2018 at 5:36 PM Diego Viola wrote:
> >>
> >> On Fri, Oct 26, 2018 at 11:21 AM Jens Axboe wrote:
> >>&
Hi Hans,
On Sun, Oct 28, 2018 at 7:48 AM Hans de Goede wrote:
>
> Hi,
>
> On 28-10-18 05:13, Diego Viola wrote:
> > On Fri, Oct 26, 2018 at 5:36 PM Diego Viola wrote:
> >>
> >> On Fri, Oct 26, 2018 at 11:21 AM Jens Axboe wrote:
> >>&
On Fri, Oct 26, 2018 at 5:36 PM Diego Viola wrote:
>
> On Fri, Oct 26, 2018 at 11:21 AM Jens Axboe wrote:
> >
> > On 10/26/18 7:45 AM, Diego Viola wrote:
> > > med_power_with_dipm causes my T450 to freeze with a SAMSUNG
> > > MZ7TD256HAFV-000L9 SSD (firmw
On Fri, Oct 26, 2018 at 5:36 PM Diego Viola wrote:
>
> On Fri, Oct 26, 2018 at 11:21 AM Jens Axboe wrote:
> >
> > On 10/26/18 7:45 AM, Diego Viola wrote:
> > > med_power_with_dipm causes my T450 to freeze with a SAMSUNG
> > > MZ7TD256HAFV-000L9 SSD (firmw
On Fri, Oct 26, 2018 at 11:21 AM Jens Axboe wrote:
>
> On 10/26/18 7:45 AM, Diego Viola wrote:
> > med_power_with_dipm causes my T450 to freeze with a SAMSUNG
> > MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
> >
> > Switching the LPM to max_performance fixes t
On Fri, Oct 26, 2018 at 11:21 AM Jens Axboe wrote:
>
> On 10/26/18 7:45 AM, Diego Viola wrote:
> > med_power_with_dipm causes my T450 to freeze with a SAMSUNG
> > MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
> >
> > Switching the LPM to max_performance fixes t
On Fri, Oct 26, 2018 at 10:48 AM Diego Viola wrote:
>
> Hi Hans,
>
> On Fri, Oct 26, 2018 at 8:59 AM Hans de Goede wrote:
> >
> > Hi,
> >
> > On 26-10-18 03:58, Diego Viola wrote:
> > > med_power_with_dipm causes my T450 to freeze with a SAMSUNG
&g
On Fri, Oct 26, 2018 at 10:48 AM Diego Viola wrote:
>
> Hi Hans,
>
> On Fri, Oct 26, 2018 at 8:59 AM Hans de Goede wrote:
> >
> > Hi,
> >
> > On 26-10-18 03:58, Diego Viola wrote:
> > > med_power_with_dipm causes my T450 to freeze with a SAMSUNG
&g
Hi Hans,
On Fri, Oct 26, 2018 at 8:59 AM Hans de Goede wrote:
>
> Hi,
>
> On 26-10-18 03:58, Diego Viola wrote:
> > med_power_with_dipm causes my T450 to freeze with a SAMSUNG
> > MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
> >
> > Switching the LPM
Hi Hans,
On Fri, Oct 26, 2018 at 8:59 AM Hans de Goede wrote:
>
> Hi,
>
> On 26-10-18 03:58, Diego Viola wrote:
> > med_power_with_dipm causes my T450 to freeze with a SAMSUNG
> > MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
> >
> > Switching the LPM
med_power_with_dipm causes my T450 to freeze with a SAMSUNG
MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
Switching the LPM to max_performance fixes this issue.
Signed-off-by: Diego Viola
---
drivers/ata/libata-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ata/libata-core.c
med_power_with_dipm causes my T450 to freeze with a SAMSUNG
MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
Switching the LPM to max_performance fixes this issue.
Signed-off-by: Diego Viola
---
drivers/ata/libata-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ata/libata-core.c
med_power_with_dipm causes my T450 to freeze with a SAMSUNG
MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
Switching the LPM to max_performance fixes this issue.
Signed-off-by: Diego Viola
---
drivers/ata/libata-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ata/libata-core.c
med_power_with_dipm causes my T450 to freeze with a SAMSUNG
MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
Switching the LPM to max_performance fixes this issue.
Signed-off-by: Diego Viola
---
drivers/ata/libata-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ata/libata-core.c
med_power_with_dipm causes my T450 to freeze with a SAMSUNG
MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
Switching the LPM to max_performance fixes this issue.
Signed-off-by: Diego Viola
---
drivers/ata/libata-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ata/libata-core.c
med_power_with_dipm causes my T450 to freeze with a SAMSUNG
MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
Switching the LPM to max_performance fixes this issue.
Signed-off-by: Diego Viola
---
drivers/ata/libata-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ata/libata-core.c
Signed-off-by: Diego Viola
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 02a39617e..db46fa83c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -93,7 +93,7 @@ Descriptions of section entries:
Supported: Someone
Signed-off-by: Diego Viola
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 02a39617e..db46fa83c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -93,7 +93,7 @@ Descriptions of section entries:
Supported: Someone
Signed-off-by: Diego Viola
---
CREDITS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CREDITS b/CREDITS
index 5befd2d71..b82efb36d 100644
--- a/CREDITS
+++ b/CREDITS
@@ -1473,7 +1473,7 @@ W: http://www.linux-ide.org/
W: http://www.linuxdiskcert.org/
D: Random SMP kernel
Signed-off-by: Diego Viola
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 0c90c4354..3dd188d52 100644
--- a/Makefile
+++ b/Makefile
@@ -1099,7 +1099,7 @@ archprepare: archheaders archscripts prepare1
scripts_basic
prepare0
Signed-off-by: Diego Viola
---
CREDITS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CREDITS b/CREDITS
index 5befd2d71..b82efb36d 100644
--- a/CREDITS
+++ b/CREDITS
@@ -1473,7 +1473,7 @@ W: http://www.linux-ide.org/
W: http://www.linuxdiskcert.org/
D: Random SMP kernel
Signed-off-by: Diego Viola
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 0c90c4354..3dd188d52 100644
--- a/Makefile
+++ b/Makefile
@@ -1099,7 +1099,7 @@ archprepare: archheaders archscripts prepare1
scripts_basic
prepare0
On Sun, Sep 23, 2018 at 5:59 AM Richard Weinberger
wrote:
>
> On Sun, Sep 23, 2018 at 3:00 AM Miguel Ojeda
> wrote:
> >
> > Hi Diego,
> >
> > A few things, since it looks like this is your first patch.
>
> git log...
>
> > On Sat, Sep 22, 2018 at 5
On Sun, Sep 23, 2018 at 5:59 AM Richard Weinberger
wrote:
>
> On Sun, Sep 23, 2018 at 3:00 AM Miguel Ojeda
> wrote:
> >
> > Hi Diego,
> >
> > A few things, since it looks like this is your first patch.
>
> git log...
>
> > On Sat, Sep 22, 2018 at 5
Hi Miguel,
On Sat, Sep 22, 2018 at 9:59 PM Miguel Ojeda
wrote:
>
> Hi Diego,
>
> A few things, since it looks like this is your first patch.
>
> On Sat, Sep 22, 2018 at 5:56 PM, Diego Viola wrote:
> > On Wed, Sep 12, 2018 at 12:54 AM Diego Viola wrote:
> >>
Hi Miguel,
On Sat, Sep 22, 2018 at 9:59 PM Miguel Ojeda
wrote:
>
> Hi Diego,
>
> A few things, since it looks like this is your first patch.
>
> On Sat, Sep 22, 2018 at 5:56 PM, Diego Viola wrote:
> > On Wed, Sep 12, 2018 at 12:54 AM Diego Viola wrote:
> >>
On Wed, Sep 12, 2018 at 12:54 AM Diego Viola wrote:
>
> Signed-off-by: Diego Viola
> ---
> CREDITS | 2 +-
> MAINTAINERS | 2 +-
> Makefile| 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/CREDITS b/CREDITS
> index 5befd2d71..b8
On Wed, Sep 12, 2018 at 12:54 AM Diego Viola wrote:
>
> Signed-off-by: Diego Viola
> ---
> CREDITS | 2 +-
> MAINTAINERS | 2 +-
> Makefile| 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/CREDITS b/CREDITS
> index 5befd2d71..b8
Signed-off-by: Diego Viola
---
CREDITS | 2 +-
MAINTAINERS | 2 +-
Makefile| 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/CREDITS b/CREDITS
index 5befd2d71..b82efb36d 100644
--- a/CREDITS
+++ b/CREDITS
@@ -1473,7 +1473,7 @@ W: http://www.linux-ide.org/
W: http
Signed-off-by: Diego Viola
---
CREDITS | 2 +-
MAINTAINERS | 2 +-
Makefile| 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/CREDITS b/CREDITS
index 5befd2d71..b82efb36d 100644
--- a/CREDITS
+++ b/CREDITS
@@ -1473,7 +1473,7 @@ W: http://www.linux-ide.org/
W: http
Signed-off-by: Diego Viola
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d870cb57c..6567bf245 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -93,7 +93,7 @@ Descriptions of section entries:
Supported: Someone
Signed-off-by: Diego Viola
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d870cb57c..6567bf245 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -93,7 +93,7 @@ Descriptions of section entries:
Supported: Someone
On Mon, Jun 11, 2018 at 3:11 PM, Jeremy Cline wrote:
> On 06/11/2018 01:56 PM, Jeremy Cline wrote:
>> On 06/11/2018 11:30 AM, Peter Zijlstra wrote:
>>> On Mon, Jun 11, 2018 at 04:38:01PM +0200, Peter Zijlstra wrote:
On Mon, Jun 11, 2018 at 04:17:42PM +0200, Peter Zijlstra wrote:
> On
On Mon, Jun 11, 2018 at 3:11 PM, Jeremy Cline wrote:
> On 06/11/2018 01:56 PM, Jeremy Cline wrote:
>> On 06/11/2018 11:30 AM, Peter Zijlstra wrote:
>>> On Mon, Jun 11, 2018 at 04:38:01PM +0200, Peter Zijlstra wrote:
On Mon, Jun 11, 2018 at 04:17:42PM +0200, Peter Zijlstra wrote:
> On
On Mon, Jun 11, 2018 at 10:59 AM, Jeremy Cline wrote:
> Hi folks,
>
> A few Fedora users have reported[0] a regression starting in v4.16.8
> where the boot will hang ~1/3 of the time with the following RCU stall
> warning:
>
> INFO: rcu_sched detected stalls on CPUs/tasks:
> o1-...!: (0 ticks
On Mon, Jun 11, 2018 at 10:59 AM, Jeremy Cline wrote:
> Hi folks,
>
> A few Fedora users have reported[0] a regression starting in v4.16.8
> where the boot will hang ~1/3 of the time with the following RCU stall
> warning:
>
> INFO: rcu_sched detected stalls on CPUs/tasks:
> o1-...!: (0 ticks
On Mon, Apr 23, 2018 at 12:10 PM, Peter Zijlstra wrote:
> On Mon, Apr 23, 2018 at 04:00:52PM +0200, Peter Zijlstra wrote:
>> On Mon, Apr 23, 2018 at 02:38:47PM +0200, Peter Zijlstra wrote:
>> > @@ -834,8 +857,12 @@ static int clocksource_unbind(struct clocksource *cs)
>> >
On Mon, Apr 23, 2018 at 12:10 PM, Peter Zijlstra wrote:
> On Mon, Apr 23, 2018 at 04:00:52PM +0200, Peter Zijlstra wrote:
>> On Mon, Apr 23, 2018 at 02:38:47PM +0200, Peter Zijlstra wrote:
>> > @@ -834,8 +857,12 @@ static int clocksource_unbind(struct clocksource *cs)
>> > if
On Mon, Apr 23, 2018 at 11:00 AM, Peter Zijlstra wrote:
> On Mon, Apr 23, 2018 at 02:38:47PM +0200, Peter Zijlstra wrote:
>> @@ -834,8 +857,12 @@ static int clocksource_unbind(struct clocksource *cs)
>> if (curr_clocksource == cs)
>>
On Mon, Apr 23, 2018 at 11:00 AM, Peter Zijlstra wrote:
> On Mon, Apr 23, 2018 at 02:38:47PM +0200, Peter Zijlstra wrote:
>> @@ -834,8 +857,12 @@ static int clocksource_unbind(struct clocksource *cs)
>> if (curr_clocksource == cs)
>> return -EBUSY;
>> }
On Mon, Apr 23, 2018 at 9:49 AM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Mon, Apr 23, 2018 at 9:38 AM, Peter Zijlstra <pet...@infradead.org> wrote:
>> On Mon, Apr 23, 2018 at 08:49:25AM -0300, Diego Viola wrote:
>>> On Mon, Apr 23, 2018 at 8:48 AM, Peter
On Mon, Apr 23, 2018 at 9:49 AM, Diego Viola wrote:
> On Mon, Apr 23, 2018 at 9:38 AM, Peter Zijlstra wrote:
>> On Mon, Apr 23, 2018 at 08:49:25AM -0300, Diego Viola wrote:
>>> On Mon, Apr 23, 2018 at 8:48 AM, Peter Zijlstra
>>> wrote:
>>> > On Mon,
On Mon, Apr 23, 2018 at 9:38 AM, Peter Zijlstra <pet...@infradead.org> wrote:
> On Mon, Apr 23, 2018 at 08:49:25AM -0300, Diego Viola wrote:
>> On Mon, Apr 23, 2018 at 8:48 AM, Peter Zijlstra <pet...@infradead.org> wrote:
>> > On Mon, Apr 23, 2018 at 08:23
On Mon, Apr 23, 2018 at 9:38 AM, Peter Zijlstra wrote:
> On Mon, Apr 23, 2018 at 08:49:25AM -0300, Diego Viola wrote:
>> On Mon, Apr 23, 2018 at 8:48 AM, Peter Zijlstra wrote:
>> > On Mon, Apr 23, 2018 at 08:23:24AM -0300, Diego Viola wrote:
>> >> > That's a Core
On Mon, Apr 23, 2018 at 8:48 AM, Peter Zijlstra <pet...@infradead.org> wrote:
> On Mon, Apr 23, 2018 at 08:23:24AM -0300, Diego Viola wrote:
>> > That's a Core2 era chip; does it actually have stable TSC ?
>>
>> I'm not sure.
>
> dmesg | grep -i tsc
>
> sh
On Mon, Apr 23, 2018 at 8:48 AM, Peter Zijlstra wrote:
> On Mon, Apr 23, 2018 at 08:23:24AM -0300, Diego Viola wrote:
>> > That's a Core2 era chip; does it actually have stable TSC ?
>>
>> I'm not sure.
>
> dmesg | grep -i tsc
>
> should be able to tell you.
On Mon, Apr 23, 2018 at 6:16 AM, Peter Zijlstra <pet...@infradead.org> wrote:
> On Sat, Apr 21, 2018 at 11:19:55PM -0300, Diego Viola wrote:
>
>> The problem only happens *after* resuming from suspend, in normal S0
>> state it never happens.
>
> What kind of suspen
On Mon, Apr 23, 2018 at 6:16 AM, Peter Zijlstra wrote:
> On Sat, Apr 21, 2018 at 11:19:55PM -0300, Diego Viola wrote:
>
>> The problem only happens *after* resuming from suspend, in normal S0
>> state it never happens.
>
> What kind of suspend are you doing? s2disk,
On Sun, Apr 22, 2018 at 2:47 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Sat, Apr 21, 2018 at 11:19 PM, Diego Viola <diego.vi...@gmail.com> wrote:
>> Hi,
>>
>> I'm currently experiencing freezes after resuming from suspend when
>> using various applic
On Sun, Apr 22, 2018 at 2:47 PM, Diego Viola wrote:
> On Sat, Apr 21, 2018 at 11:19 PM, Diego Viola wrote:
>> Hi,
>>
>> I'm currently experiencing freezes after resuming from suspend when
>> using various applications on my desktop.
>>
>> For example, w
On Sat, Apr 21, 2018 at 11:19 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> Hi,
>
> I'm currently experiencing freezes after resuming from suspend when
> using various applications on my desktop.
>
> For example, when using Firefox and switching between tabs the screen
On Sat, Apr 21, 2018 at 11:19 PM, Diego Viola wrote:
> Hi,
>
> I'm currently experiencing freezes after resuming from suspend when
> using various applications on my desktop.
>
> For example, when using Firefox and switching between tabs the screen
> would freeze, all
Hi,
I'm currently experiencing freezes after resuming from suspend when
using various applications on my desktop.
For example, when using Firefox and switching between tabs the screen
would freeze, allowing me to only move the mouse pointer but focusing
the mouse pointer on a application won't
Hi,
I'm currently experiencing freezes after resuming from suspend when
using various applications on my desktop.
For example, when using Firefox and switching between tabs the screen
would freeze, allowing me to only move the mouse pointer but focusing
the mouse pointer on a application won't
On Fri, Apr 28, 2017 at 2:32 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Thu, Apr 27, 2017 at 8:09 PM, Diego Viola <diego.vi...@gmail.com> wrote:
>> On Thu, Apr 27, 2017 at 7:56 PM, Diego Viola <diego.vi...@gmail.com> wrote:
>>> Hello,
>>&g
On Fri, Apr 28, 2017 at 2:32 PM, Diego Viola wrote:
> On Thu, Apr 27, 2017 at 8:09 PM, Diego Viola wrote:
>> On Thu, Apr 27, 2017 at 7:56 PM, Diego Viola wrote:
>>> Hello,
>>>
>>> For some reason 4.11-rc8 makes my Dell Inspiron 5558 crash. The
>>>
On Thu, Apr 27, 2017 at 8:09 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Thu, Apr 27, 2017 at 7:56 PM, Diego Viola <diego.vi...@gmail.com> wrote:
>> Hello,
>>
>> For some reason 4.11-rc8 makes my Dell Inspiron 5558 crash. The
>> problem is very r
On Thu, Apr 27, 2017 at 8:09 PM, Diego Viola wrote:
> On Thu, Apr 27, 2017 at 7:56 PM, Diego Viola wrote:
>> Hello,
>>
>> For some reason 4.11-rc8 makes my Dell Inspiron 5558 crash. The
>> problem is very random and I don't know how to reproduce it.
>>
>>
On Thu, Apr 27, 2017 at 7:56 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> Hello,
>
> For some reason 4.11-rc8 makes my Dell Inspiron 5558 crash. The
> problem is very random and I don't know how to reproduce it.
>
> That said, this only started happening with 4.11-r
On Thu, Apr 27, 2017 at 7:56 PM, Diego Viola wrote:
> Hello,
>
> For some reason 4.11-rc8 makes my Dell Inspiron 5558 crash. The
> problem is very random and I don't know how to reproduce it.
>
> That said, this only started happening with 4.11-rc8 and I've been
>
Hello,
For some reason 4.11-rc8 makes my Dell Inspiron 5558 crash. The
problem is very random and I don't know how to reproduce it.
That said, this only started happening with 4.11-rc8 and I've been
using 4.11 since rc3 and it didn't happen at all with the previous
RCs.
Not sure how I could
Hello,
For some reason 4.11-rc8 makes my Dell Inspiron 5558 crash. The
problem is very random and I don't know how to reproduce it.
That said, this only started happening with 4.11-rc8 and I've been
using 4.11 since rc3 and it didn't happen at all with the previous
RCs.
Not sure how I could
On Thu, Mar 23, 2017 at 2:12 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Thu, Mar 23, 2017 at 2:02 PM, Mathias Nyman
> <mathias.ny...@linux.intel.com> wrote:
>> On 22.03.2017 19:51, Mathias Nyman wrote:
>>>
>>> On 22.03.2017 00:52, Diego Viola wrot
On Thu, Mar 23, 2017 at 2:12 PM, Diego Viola wrote:
> On Thu, Mar 23, 2017 at 2:02 PM, Mathias Nyman
> wrote:
>> On 22.03.2017 19:51, Mathias Nyman wrote:
>>>
>>> On 22.03.2017 00:52, Diego Viola wrote:
>>>>
>>>> On Tue, Mar 21, 2017 at 12:2
On Thu, Mar 23, 2017 at 2:02 PM, Mathias Nyman
<mathias.ny...@linux.intel.com> wrote:
> On 22.03.2017 19:51, Mathias Nyman wrote:
>>
>> On 22.03.2017 00:52, Diego Viola wrote:
>>>
>>> On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola <diego.vi...@gmail.com&
On Thu, Mar 23, 2017 at 2:02 PM, Mathias Nyman
wrote:
> On 22.03.2017 19:51, Mathias Nyman wrote:
>>
>> On 22.03.2017 00:52, Diego Viola wrote:
>>>
>>> On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola
>>> wrote:
>>>>
>>>> On Tue, Mar
On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola <diego.vi...@gmail.com> wrote:
>> On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola <diego.vi...@gmail.com> wrote:
>>> On Mon, Mar 20, 20
On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola wrote:
> On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola wrote:
>> On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola wrote:
>>> On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola wrote:
>>>> On Mon, Mar 20, 2017 at 1:32
On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola <diego.vi...@gmail.com> wrote:
>> On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola <diego.vi...@gmail.com> wrote:
>>> On Mon, Ma
On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola wrote:
> On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola wrote:
>> On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola wrote:
>>> On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
>>> wrote:
>>>> On 20.03.2017 17:39, Die
On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola <diego.vi...@gmail.com> wrote:
>> On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
>> <mathias.ny...@linux.intel.com> wrote:
>>&
On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola wrote:
> On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola wrote:
>> On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
>> wrote:
>>> On 20.03.2017 17:39, Diego Viola wrote:
>>>>
>>>> On Mon, Mar
On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
> <mathias.ny...@linux.intel.com> wrote:
>> On 20.03.2017 17:39, Diego Viola wrote:
>>>
>>> On Mon, Mar 20, 2017
On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola wrote:
> On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
> wrote:
>> On 20.03.2017 17:39, Diego Viola wrote:
>>>
>>> On Mon, Mar 20, 2017 at 11:21 AM, Mathias Nyman
>>> wrote:
>>&
On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
<mathias.ny...@linux.intel.com> wrote:
> On 20.03.2017 17:39, Diego Viola wrote:
>>
>> On Mon, Mar 20, 2017 at 11:21 AM, Mathias Nyman
>> <mathias.ny...@linux.intel.com> wrote:
>>>
>>> On 19.03.201
On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
wrote:
> On 20.03.2017 17:39, Diego Viola wrote:
>>
>> On Mon, Mar 20, 2017 at 11:21 AM, Mathias Nyman
>> wrote:
>>>
>>> On 19.03.2017 23:29, Diego Viola wrote:
>>>>
>>>>
>
>>&g
On Mon, Mar 20, 2017 at 11:21 AM, Mathias Nyman
<mathias.ny...@linux.intel.com> wrote:
> On 19.03.2017 23:29, Diego Viola wrote:
>>
>> On Fri, Mar 17, 2017 at 5:18 PM, Diego Viola <diego.vi...@gmail.com>
>> wrote:
>>>
>>> On Fri, Mar 17,
On Mon, Mar 20, 2017 at 11:21 AM, Mathias Nyman
wrote:
> On 19.03.2017 23:29, Diego Viola wrote:
>>
>> On Fri, Mar 17, 2017 at 5:18 PM, Diego Viola
>> wrote:
>>>
>>> On Fri, Mar 17, 2017 at 1:57 PM, Diego Viola
>>> wrote:
>>>>
On Fri, Mar 17, 2017 at 5:18 PM, Diego Viola <diego.vi...@gmail.com> wrote:
> On Fri, Mar 17, 2017 at 1:57 PM, Diego Viola <diego.vi...@gmail.com> wrote:
>> On Fri, Mar 17, 2017 at 1:24 PM, Alan Stern <st...@rowland.harvard.edu>
>> wrote:
>>> On Fri, 1
1 - 100 of 301 matches
Mail list logo