Re: INO64 Effecting Firefox

2017-05-30 Thread Pete Wright
On 05/28/2017 08:54, Pete Wright wrote: Hi all, I can't imagine that this is related to INO64, but since upgrading my world and kernel on drm-next (which merged upstream CURRENT as of May 27 which should include the ino64 work) I am having segfaults running firefox. Previous to this

RE: INO64 Effecting Firefox

2017-05-29 Thread M - Krasznai András
...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Oleg V. Nauman Sent: Sunday, May 28, 2017 6:45 PM To: freebsd-current@freebsd.org Subject: Re: INO64 Effecting Firefox On Sunday 28 May 2017 18:09:19 O. Hartmann wrote: > Am Sun, 28 May 2017 08:54:35 -0700 > > Pete

Re: INO64 Effecting Firefox

2017-05-28 Thread Oleg V. Nauman
On Sunday 28 May 2017 18:09:19 O. Hartmann wrote: > Am Sun, 28 May 2017 08:54:35 -0700 > > Pete Wright schrieb: > > Hi all, > > > > I can't imagine that this is related to INO64, but since upgrading my > > world and kernel on drm-next (which merged upstream CURRENT as of

Re: INO64 Effecting Firefox

2017-05-28 Thread O. Hartmann
Am Sun, 28 May 2017 08:54:35 -0700 Pete Wright schrieb: > Hi all, > > I can't imagine that this is related to INO64, but since upgrading my > world and kernel on drm-next (which merged upstream CURRENT as of May 27 > which should include the ino64 work) I am having

INO64 Effecting Firefox

2017-05-28 Thread Pete Wright
Hi all, I can't imagine that this is related to INO64, but since upgrading my world and kernel on drm-next (which merged upstream CURRENT as of May 27 which should include the ino64 work) I am having segfaults running firefox. Previous to this firefox was very stable for work/personal daily