Re: radeon(4) drm crashing on current/amd64

2016-05-26 Thread Sebastien Marie
On Thu, May 26, 2016 at 08:15:44PM -0600, Theo de Raadt wrote: > > > > Without seeing a ktrace output, I don't think I can make any progress > > here. > > Well there's the answer! > > Start running it in ktrace on a large filesystem --- all the time, and > hope the edge condition gets hit. > J

Re: radeon(4) drm crashing on current/amd64

2016-05-26 Thread Theo de Raadt
> i3's restore_xcb_check_cb() (src/restore_layout.c), if it sees that the > connection to X has been lost, it calls restore_connect() which calls > libxcb's xcb_connect(). > > In libxcb that calls xcb_connect_to_display_with_auth_info() which calls > _xcb_open(), which calls _xcb_open_unix() and u

Re: radeon(4) drm crashing on current/amd64

2016-05-26 Thread Carlin Bingham
On Fri, May 27, 2016 at 01:07:09AM +0200, Theo Buehler wrote: > On Thu, May 26, 2016 at 05:54:30PM -0400, Andre Smagin wrote: > > On Sat, 14 May 2016 21:01:29 +0200 (CEST) > > danj+o...@chown.me wrote: > > > > > >Synopsis:radeon(4) drm crashing on current/amd64 > > [...] > > > drm:pid77501

Re: radeon(4) drm crashing on current/amd64

2016-05-26 Thread Theo de Raadt
> > > >Synopsis:radeon(4) drm crashing on current/amd64 > > [...] > > > drm:pid77501:radeon_fence_wait_empty_locked *ERROR* error waiting for > > > ring[3] to become idle (-1601868) > > > > > > I am seeing the same issue, very infrequently (may be once every week or > > two): > > > > d

Re: radeon(4) drm crashing on current/amd64

2016-05-26 Thread Theo Buehler
On Thu, May 26, 2016 at 05:54:30PM -0400, Andre Smagin wrote: > On Sat, 14 May 2016 21:01:29 +0200 (CEST) > danj+o...@chown.me wrote: > > > >Synopsis: radeon(4) drm crashing on current/amd64 > [...] > > drm:pid77501:radeon_fence_wait_empty_locked *ERROR* error waiting for > > ring[3] to become i

Re: radeon(4) drm crashing on current/amd64

2016-05-26 Thread Andre Smagin
On Sat, 14 May 2016 21:01:29 +0200 (CEST) danj+o...@chown.me wrote: > >Synopsis:radeon(4) drm crashing on current/amd64 [...] > drm:pid77501:radeon_fence_wait_empty_locked *ERROR* error waiting for ring[3] > to become idle (-1601868) I am seeing the same issue, very infrequently (may be onc

Re: variable name typo in strcat.3

2016-05-26 Thread Tim Kuijsten
Op 26-05-16 om 23:24 schreef Tim Kuijsten: rename s to dst, just like in strncat, strcpy and strncpy. Index: strcat.3 === RCS file: /cvs/src/lib/libc/string/strcat.3,v retrieving revision 1.17 diff -u -p -r1.17 strcat.3 --- strcat.

Re: variable name typo in strcat.3

2016-05-26 Thread Todd C. Miller
On Thu, 26 May 2016 23:24:16 +0200, Tim Kuijsten wrote: > rename s to dst, just like in strncat, strcpy and strncpy. Committed, thanks. - todd

variable name typo in strcat.3

2016-05-26 Thread Tim Kuijsten
rename s to dst, just like in strncat, strcpy and strncpy. Index: strcat.3 === RCS file: /cvs/src/lib/libc/string/strcat.3,v retrieving revision 1.17 diff -u -p -r1.17 strcat.3 --- strcat.319 Apr 2014 11:30:40 - 1.17 ++

Re: Default OpenBSD 5.9 GCC 4.2.1 compiler segfaults when compiling a sample file

2016-05-26 Thread David Coppa
On Wed, May 25, 2016 at 1:18 PM, David Coppa wrote: > On Tue, 24 May 2016, Stefan Kempf wrote: > >> Hmm, looking closer at your bugzilla link, this somewhat larger diff >> should also fix the same problem, but it was committed against GPLv2 sources. >> Still need to try it though. >> >> https://gc