Karl Williamson wrote:
> On 3/28/19 8:03 AM, Ingo Schwarze wrote:
> >It is unspecified whether the locale object pointed to by base
> >shall be modified, or freed and a new locale object created.
>
> I can see how you might be able to argue for your interpretation. I
> believe the
On 3/28/19 8:03 AM, Ingo Schwarze wrote:
Hi Ted and Karl,
Ted Unangst wrote on Wed, Mar 27, 2019 at 06:03:29PM -0400:
Karl Williamson wrote:
Ted Unangst wrote:
This should fix things.
There is no bug and nothing to fix.
Our existing implementation fully conforms to the POSIX
lists+m...@ggp2.com:
> >Synopsis: suspend not working starting within the past ~3 week snaps
I'm typing this on an almost identical machine which also follows
-current and has had no problems resuming in recent weeks.
> acpi0: tables DSDT FACP UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT BOOT BATB
I'll repeated what others have said.
These reports are *way too vague*. It is impossible to take any
action based upon them.
We need more people to get involved at finding *the specific moments
in time* when commits were made which affect resume, on their specific
machines.
If we don't get
Responding to myself but Raf Czlonka (@rjc) pointed out something
that seems to be important.
Before @jcs azalia driver fixes for Matebook X were in repo I was
building kernel from my local, patched sources. And recently, these
changes were accepted and I started using snapshot kernel. And I
I had similar issues, randomly:
- black screen after waking up
- unresponsive terminal (keyboard and touchpad were
responding but commands were not executed, CTRL+C didn't work, no
network).
- something that looked like crashed X Window server (went back to
the console)
- and mix of issues above
> Unsupported release. It is fixed in 6.2. Last release is 6.4. We're
> preparing for 6.5
>
> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libc/stdlib/malloc.c?rev=1.225
>
> Why keep running old stuff? The upgrade proces is really simple.
thank you to Stuart and you for the quick
On Thu, Mar 28, 2019 at 08:14:52PM +0100, Sebastian Benoit wrote:
> you can use the ones on http://ftp.hostserver.de/archive/
Perfect - I should be able to quickly track this down early next week.
Thanks, and that's a great resource to throw in my bag of tricks :)
lists+m...@ggp2.com(lists+m...@ggp2.com) on 2019.03.28 18:44:09 +:
> On Thu, Mar 28, 2019 at 11:35:06AM -0700, Mike Larkin wrote:
> > Please help us solve this by bisecting to find the offending diff. Or at
> > least
> > narrow it down to a smaller timeframe.
>
> I will be happy to do this,
On Thu, Mar 28, 2019 at 11:35:06AM -0700, Mike Larkin wrote:
> Please help us solve this by bisecting to find the offending diff. Or at least
> narrow it down to a smaller timeframe.
I will be happy to do this, but will be offline until Monday. What's
the best method to start troubleshooting?
> Date: Thu, 28 Mar 2019 15:46:13 +0100
> From: Frederic Cambus
>
> On Tue, Mar 26, 2019 at 09:58:09PM +0500, dmitry.sensei wrote:
> > Also I have kernel loop trap.. after running X and switching to 0 screen
> > (Ctrl-Alt-F1)
>
> Thanks for your report and for sharing your dmesg.
>
> I just
On Tue, Mar 26, 2019 at 09:58:09PM +0500, dmitry.sensei wrote:
> Also I have kernel loop trap.. after running X and switching to 0 screen
> (Ctrl-Alt-F1)
Thanks for your report and for sharing your dmesg.
I just reverted the other commit I previously did to efifb(4). Please
let me know if this
Hi Ted and Karl,
Ted Unangst wrote on Wed, Mar 27, 2019 at 06:03:29PM -0400:
> Karl Williamson wrote:
>> Ted Unangst wrote:
>>> This should fix things.
There is no bug and nothing to fix.
Our existing implementation fully conforms to the POSIX specification.
POSIX explicitly says:
It is
On Thu, Mar 28, 2019 at 01:50:33PM +0100, paul zimmermann wrote:
> > Unsupported release. It is fixed in 6.2. Last release is 6.4. We're
> > preparing for 6.5
> >
> > http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libc/stdlib/malloc.c?rev=1.225
> >
> > Why keep running old stuff? The
On Thu, Mar 28, 2019 at 11:52:46AM +0100, paul.zimmerm...@inria.fr wrote:
> >Synopsis:posix_memalign does not return aligned memory
> >Category:system
> >Environment:
> System : OpenBSD 6.1
> Details : OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT 2017
>
On 2019/03/28 11:52, paul.zimmerm...@inria.fr wrote:
> >Synopsis:posix_memalign does not return aligned memory
> >Category:system
> >Environment:
> System : OpenBSD 6.1
> Details : OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT 2017
>
>
>Synopsis: posix_memalign does not return aligned memory
>Category: system
>Environment:
System : OpenBSD 6.1
Details : OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT 2017
17 matches
Mail list logo
