Got it. I suppose that explains why it was so unreliably
reproducible..
In any case, the patch is holding strong still with plenty of activity
since, so it's looking good.
Thak you for all of this; very instructive.
On Sat, Jan 06, 2018 at 08:55:00PM +, Chris Wilson wrote:
> Quoting
Got it. I suppose that explains why it was so unreliably
reproducible..
In any case, the patch is holding strong still with plenty of activity
since, so it's looking good.
Thak you for all of this; very instructive.
On Sat, Jan 06, 2018 at 08:55:00PM +, Chris Wilson wrote:
> Quoting
Thanks!
It's also a mystery to me why I never had any crashes on any of the
other systems running on this machine running the same (unpatched)
kernels.
I'm assuming the window manager might have something to do with it:
all of the others are on i3 and the buggy one's openbox, so perhaps
tiling
Thanks!
It's also a mystery to me why I never had any crashes on any of the
other systems running on this machine running the same (unpatched)
kernels.
I'm assuming the window manager might have something to do with it:
all of the others are on i3 and the buggy one's openbox, so perhaps
tiling
On Sat, Jan 06, 2018 at 08:24:43AM -0500, Alexandru Chirvasitu wrote:
> Thank you!
>
> I'll apply that more elaborate patch you sent in the longer message to
> my clone of the repo and see if it still freezes.
>
I'm on it now with no freezes yet, despite trying my best :).
I have a question
On Sat, Jan 06, 2018 at 08:24:43AM -0500, Alexandru Chirvasitu wrote:
> Thank you!
>
> I'll apply that more elaborate patch you sent in the longer message to
> my clone of the repo and see if it still freezes.
>
I'm on it now with no freezes yet, despite trying my best :).
I have a question
Thank you!
I'll apply that more elaborate patch you sent in the longer message to
my clone of the repo and see if it still freezes.
On Sat, Jan 06, 2018 at 10:43:20AM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-05 22:05:18)
> > Here we go.
> >
> > I have
> >
> >
Thank you!
I'll apply that more elaborate patch you sent in the longer message to
my clone of the repo and see if it still freezes.
On Sat, Jan 06, 2018 at 10:43:20AM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-05 22:05:18)
> > Here we go.
> >
> > I have
> >
> >
Will do.
On Fri, Jan 05, 2018 at 08:02:48PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-05 19:58:42)
> > OK, I then plan to try with the previous config, plus these
> > modifications:
> >
> > CONFIG_PAGE_POISONING not set
> > CONFIG_SLUB_STATS=y
> >
> > I'm a little
Will do.
On Fri, Jan 05, 2018 at 08:02:48PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-05 19:58:42)
> > OK, I then plan to try with the previous config, plus these
> > modifications:
> >
> > CONFIG_PAGE_POISONING not set
> > CONFIG_SLUB_STATS=y
> >
> > I'm a little
OK, I then plan to try with the previous config, plus these
modifications:
CONFIG_PAGE_POISONING not set
CONFIG_SLUB_STATS=y
I'm a little puzzled about this:
On Fri, Jan 05, 2018 at 07:51:01PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-05 19:37:24)
> > I'll try. I need a
OK, I then plan to try with the previous config, plus these
modifications:
CONFIG_PAGE_POISONING not set
CONFIG_SLUB_STATS=y
I'm a little puzzled about this:
On Fri, Jan 05, 2018 at 07:51:01PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-05 19:37:24)
> > I'll try. I need a
I'll try. I need a bit of clarification:
On Fri, Jan 05, 2018 at 05:52:25PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-03 21:53:15)
> > All right, here's the dmesg from the kernel compiled from drm-tip (in
> > sync with upstream at the time of the compilation earlier
I'll try. I need a bit of clarification:
On Fri, Jan 05, 2018 at 05:52:25PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-03 21:53:15)
> > All right, here's the dmesg from the kernel compiled from drm-tip (in
> > sync with upstream at the time of the compilation earlier
All right, here's the dmesg from the kernel compiled from drm-tip (in
sync with upstream at the time of the compilation earlier today), with
CONFIG_DRM_I915_DEBUG_GEM=y
I crashed it by opening 20+ xterm windows. Doesn't always do it though
(tried this before).
On Wed, Jan 03, 2018 at 11:31:31AM
All right, here's the dmesg from the kernel compiled from drm-tip (in
sync with upstream at the time of the compilation earlier today), with
CONFIG_DRM_I915_DEBUG_GEM=y
I crashed it by opening 20+ xterm windows. Doesn't always do it though
(tried this before).
On Wed, Jan 03, 2018 at 11:31:31AM
Thank you for that!
I'd been getting used to seeing warnings to that effect, so got
complacent and stopped checking for errors..
In any case, it's now compiled and installed, and I will report back
with any new logs if / when another hang occurs.
On Wed, Jan 03, 2018 at 02:53:45PM +, Chris
Thank you for that!
I'd been getting used to seeing warnings to that effect, so got
complacent and stopped checking for errors..
In any case, it's now compiled and installed, and I will report back
with any new logs if / when another hang occurs.
On Wed, Jan 03, 2018 at 02:53:45PM +, Chris
On Wed, Jan 03, 2018 at 01:47:56PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-03 13:46:42)
> > I've cloned your
> >
> > https://anongit.freedesktop.org/git/drm-tip.git
> >
> > and am now trying to build it (just the master; I haven't tried
> > previous commits). The
On Wed, Jan 03, 2018 at 01:47:56PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-03 13:46:42)
> > I've cloned your
> >
> > https://anongit.freedesktop.org/git/drm-tip.git
> >
> > and am now trying to build it (just the master; I haven't tried
> > previous commits). The
I've cloned your
https://anongit.freedesktop.org/git/drm-tip.git
and am now trying to build it (just the master; I haven't tried
previous commits). The build fails at the modules stage with
Makefile:1015: recipe for target 'drivers' failed
make: *** [drivers] Error 2
What is the earliest
I've cloned your
https://anongit.freedesktop.org/git/drm-tip.git
and am now trying to build it (just the master; I haven't tried
previous commits). The build fails at the modules stage with
Makefile:1015: recipe for target 'drivers' failed
make: *** [drivers] Error 2
What is the earliest
For comparison, here's another one produced by the same kernel, on the
same laptop, but a different hard drive.
The OS was installed on a USB stick that I'd boot the laptop off
of. Recently I started getting lags when copying to / from the stick,
so I moved the OS to an external SSD.
Everything
For comparison, here's another one produced by the same kernel, on the
same laptop, but a different hard drive.
The OS was installed on a USB stick that I'd boot the laptop off
of. Recently I started getting lags when copying to / from the stick,
so I moved the OS to an external SSD.
Everything
Attached. Crashed quite a bit faster than before this time.
It always seems to have something to do with opening and alt-tabbing
between windows. This time what produced the crash was an attempt to
open a new terminal.
The hanging happened right after issuing the keyboard shortcut, before
the
Attached. Crashed quite a bit faster than before this time.
It always seems to have something to do with opening and alt-tabbing
between windows. This time what produced the crash was an attempt to
open a new terminal.
The hanging happened right after issuing the keyboard shortcut, before
the
All right, we're in business with the new dmesg: It hung again, with a
4.15-rc6 kernel with kasan support.
The new dmesg is attached; the trace is longer now, as you expected.
And thanks!
On Sun, Dec 31, 2017 at 04:54:14PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2017-12-31
All right, we're in business with the new dmesg: It hung again, with a
4.15-rc6 kernel with kasan support.
The new dmesg is attached; the trace is longer now, as you expected.
And thanks!
On Sun, Dec 31, 2017 at 04:54:14PM +, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2017-12-31
Compiled a couple of kernels with kasan enabled. I don't yet have a
crash, but on the system that has been crashing I have the following
kasan distress signals on bootup (dmesg attached):
[0.027746]
==
[0.027759] BUG: KASAN:
Compiled a couple of kernels with kasan enabled. I don't yet have a
crash, but on the system that has been crashing I have the following
kasan distress signals on bootup (dmesg attached):
[0.027746]
==
[0.027759] BUG: KASAN:
Quoting Alexandru Chirvasitu (2017-12-30 17:31:32)
> Short description: I get freezes of my desktop completely eliminating
> mouse / keyboard functionality.
>
> I’m on an UltraLap 5330, Processor: i7-7500U, Memory: 32 GB DDR4-2133
> Video Card: Intel HD (included). It's running Void linux 64 bit.
Quoting Alexandru Chirvasitu (2017-12-30 17:31:32)
> Short description: I get freezes of my desktop completely eliminating
> mouse / keyboard functionality.
>
> I’m on an UltraLap 5330, Processor: i7-7500U, Memory: 32 GB DDR4-2133
> Video Card: Intel HD (included). It's running Void linux 64 bit.
32 matches
Mail list logo
