On Sun, Aug 14, 2016 at 06:16:11PM +0200, Alessandro DE LAURENZIS wrote:
> Mike,
>
> On Fri, 12 Aug 2016 19:47:40 +0200
> Alessandro DE LAURENZIS wrote:
>
> > Hi Mike,
> >
> > On 2016-08-12 18:54, Mike Larkin wrote:
> > > Shrug. Works fine here on i386 and amd64.
> > >
> > > Do other processes
Mike,
On Fri, 12 Aug 2016 19:47:40 +0200
Alessandro DE LAURENZIS wrote:
> Hi Mike,
>
> On 2016-08-12 18:54, Mike Larkin wrote:
> > Shrug. Works fine here on i386 and amd64.
> >
> > Do other processes crash as well? What if you leave fluxbox
> > running? Does
> > it eventually fail on its own w
Hi Mike,
On 2016-08-12 18:54, Mike Larkin wrote:
Shrug. Works fine here on i386 and amd64.
Do other processes crash as well? What if you leave fluxbox running?
Does
it eventually fail on its own without needing fluxbox-remote to trigger
it?
As far as I can say, no other crash, neither fluxb
On Fri, Aug 12, 2016 at 11:23:45AM +0200, Alessandro De Laurenzis wrote:
> Hi Mike,
>
> (sorry, I'm having issues with my e-mail service...)
>
> >I installed fluxbox and tried to repro this. It works fine here.
> >
> >Does this fail just after many ZZZs? because it looks from your dmesg that
> >y
Hi Mike,
(sorry, I'm having issues with my e-mail service...)
>I installed fluxbox and tried to repro this. It works fine here.
>
>Does this fail just after many ZZZs? because it looks from your dmesg that
>you did a bunch of them. Does it fail after the first one?
>
>-ml
the crash is triggered
On Thu, Aug 11, 2016 at 09:39:33PM +0200, Alessandro DE LAURENZIS wrote:
> dmesg and pkg_info -t as requested:
>
I installed fluxbox and tried to repro this. It works fine here.
Does this fail just after many ZZZs? because it looks from your dmesg that
you did a bunch of them. Does it fail after
dmesg and pkg_info -t as requested:
OpenBSD 6.0-current (GENERIC.MP) #2345: Tue Aug 9 23:00:50 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3177906176 (3030MB)
avail mem = 3077181440 (2934MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0
On Thu, Aug 11, 2016 at 03:10:25PM +0200, Alessandro DE LAURENZIS wrote:
> Hello,
>
> I'm reporting this without any details because actually I do not know how to
> start a debugging...
>
> After resuming from an hibernation, restarting Fluxbox (Restart from menu or
> issuing "fluxbox-remote -Res
On 2016-08-11 15:23, Alessandro DE LAURENZIS wrote:
Hello David,
Does restarting Fluxbox work otherwise or the crash only happens after
resuming?
restarting it before suspend to disk works flawlessly.
Cheers
It's worth mentioning that suspending to RAM does *not* trigger the
crash.
--
A
Hello David,
Does restarting Fluxbox work otherwise or the crash only happens after
resuming?
restarting it before suspend to disk works flawlessly.
Cheers
--
Alessandro DE LAURENZIS
[mailto:jus...@atlantide.t28.net]
LinkedIn: http://it.linkedin.com/in/delaurenzis
On Thu, Aug 11, 2016 at 3:10 PM, Alessandro DE LAURENZIS
wrote:
> Hello,
>
> I'm reporting this without any details because actually I do not know how to
> start a debugging...
>
> After resuming from an hibernation, restarting Fluxbox (Restart from menu or
> issuing "fluxbox-remote -Restart") sys
Hello,
I'm reporting this without any details because actually I do not know
how to start a debugging...
After resuming from an hibernation, restarting Fluxbox (Restart from
menu or issuing "fluxbox-remote -Restart") systematically crashes it,
causing the XDM login window to appear. No core
12 matches
Mail list logo
