Updating src tree:
P src/distrib/sets/lists/man/mi
P src/external/gpl3/gcc/dist/libsanitizer/asan/asan_mapping.h
P src/lib/libnvmm/libnvmm.3
P src/share/man/man4/Makefile
P src/share/man/man4/isa.4
U src/share/man/man4/nct.4
P src/sys/arch/amd64/conf/GENERIC
P src/sys/arch/i386/conf/GENERIC
P
Can someone who has this issue explain it shortly?
- Which GPU?
- What part of updating (kernel, userland) did it?
- Does a clean build of everything fix it?
the i915 driver has broken userland compatibility. mrg/riastradh fixed it,
but I won't be surprised if there's more we haven't spotted
Riccardo Mottola wrote:
>On 24/10/2019 22:06, Robert Swindells wrote:
>> You maybe need some changes to the ata disk driver that went in on the
>> 23rd.
>
>bad luck. I upgraded kernel and modules, installed and it crashes during
>userland build, so no progress at all.
>
>Still a crash in
On Wed, 2019-10-16 at 12:10 +0100, Chavdar Ivanov wrote:
> On Wed, 16 Oct 2019 at 11:03, David H. Gutteridge > wrote:
>
> > FWIW, aside from Firefox (where I also see this issue), I've found
> > since the recent Mesa upgrade, Xfce4's window manager consistently
> > crashes during startup.
On Sat, 19 Oct 2019, John D. Baker wrote:
> So, it seems the plan of action is to reboot the installed system
> (8.1_STABLE) in single-user mode, turn off autoconfig on the RAID
> and reboot the test kernel in single-user mode. Then I can observe
> the ahcisata behavior with respect to the RAID
Hi,
On 24/10/2019 22:06, Robert Swindells wrote:
You maybe need some changes to the ata disk driver that went in on the
23rd.
bad luck. I upgraded kernel and modules, installed and it crashes during
userland build, so no progress at all.
Still a crash in compat_90_sys_fstatvfs1() at
I've rebuilt my -current system a few hours ago, followed by a build
of wip/qemu-nvmm, I see now at 4.1.
So far everything seems to be working as expected.
BTW I have been getting - on all my qemu-nvmm builds from wip - a PLIST error -
share/locale/bg/LC_MESSAGES/qemu.mo
> [W]hich of the following is more readable to the user:
> $ ls foo
> ls: foo: No such file or directory
> or
> $ ls foo
> ls: stat(foo): No such file or directory
It depends entirely on the user.
As I recently wrote on a non-NetBSD mailing list, there is no such
thing as a good or bad user
On Thu, Oct 24, 2019 at 10:17:17PM +0300, Valery Ushakov wrote:
> On Thu, Oct 24, 2019 at 05:26:41 +0200, Martin Husemann wrote:
>
> > Deal with this properly in sysinst would mean:
> >
> > 1) run a script like:
> > rm -f /tmp/list
> > for s in *.${suffix}
> > do
> >for dir in $( tar tvf
On Fri, Oct 25, 2019 at 3:04 PM Michael van Elst wrote:
>
> ozaki.ry...@gmail.com (Ryota Ozaki) writes:
>
> >> @@ -72,7 +74,7 @@ serverconnect(const char *addr, unsigned short port)
> >> + err(1, "setsockopt(SO_NOSIGPIPE)");
> >> +err(1, "open(%s)", path);
>
> >I prefer more
On Fri, Oct 25, 2019 at 2:38 PM Valery Ushakov wrote:
>
> On Fri, Oct 25, 2019 at 12:56:43 +0900, Ryota Ozaki wrote:
>
> > > @@ -72,7 +74,7 @@ serverconnect(const char *addr, unsigned short port)
> > > [...]
> > > + err(1, "setsockopt(SO_NOSIGPIPE)");
> > >
> > > I'd just trim it down
ozaki.ry...@gmail.com (Ryota Ozaki) writes:
>> @@ -72,7 +74,7 @@ serverconnect(const char *addr, unsigned short port)
>> + err(1, "setsockopt(SO_NOSIGPIPE)");
>> +err(1, "open(%s)", path);
>I prefer more informative messages. Why do you want to trim them?
Usually the error
12 matches
Mail list logo
