On Fri, Apr 03, 2020 at 09:29:41PM +0200, Thomas Klausner wrote:
> On Sat, Apr 04, 2020 at 05:55:01AM +1100, Matthew Green wrote:
> > Thomas Klausner writes:
> > > Here's a version with less warnings:
> > >
> > > int a;
> > > struct b {
> > > char c;
> > > void *d;
> > > };
> > > struct b e()
Dear Andrew,
On 2020-04-07, Yorick Hardy wrote:
> Dear Andrew,
>
> On 2020-04-07, Andrew Doran wrote:
> > Hi Yorick.
> >
> > On Mon, Apr 06, 2020 at 11:16:37PM +0200, Yorick Hardy wrote:
> >
> > >Crash version 9.99.54, image version 9.99.54.
> > >crash: _kvm_kvatop(0)
> > >Kernel co
Updating src tree:
P src/common/lib/libc/string/strcat.c
P src/common/lib/libc/string/strchr.c
P src/common/lib/libc/string/strrchr.c
P src/distrib/ews4800mips/floppies/ramdisk/list
P src/share/man/man9/spl.9
P src/sys/arch/aarch64/aarch64/pmap.c
P src/sys/arch/aarch64/include/pmap.h
P src/sys/ar
Basically all SoCs has the same pattern: "0x3[0]504d44" where 0
changes from 1 to 8 as of now. Previously code had a switch statement
just comparing values directly, but current optimization with the
"array" utilized the fact that ids were up to number "7". Because of
this, just adding EX2 to array
Dear Andrew,
On 2020-04-07, Andrew Doran wrote:
> Hi Yorick.
>
> On Mon, Apr 06, 2020 at 11:16:37PM +0200, Yorick Hardy wrote:
>
> >Crash version 9.99.54, image version 9.99.54.
> >crash: _kvm_kvatop(0)
> >Kernel compiled without options LOCKDEBUG.
> >System panicked: vrelel: bad
Hi Yorick.
On Mon, Apr 06, 2020 at 11:16:37PM +0200, Yorick Hardy wrote:
>Crash version 9.99.54, image version 9.99.54.
>crash: _kvm_kvatop(0)
>Kernel compiled without options LOCKDEBUG.
>System panicked: vrelel: bad ref count
>Backtrace from time of crash is available.
>c
Hi Greg,
Greg Troxel wrote:
> To deal with this, you can do one of:
>
> fix gobject-introspection :-)
>
> figure out what requires it and add -X for that too, building up a
> list
>
> in your sources, cvs update the gobject-introspection directory back
> in time to the version you have inst
Riccardo Mottola writes:
> since build of gobject-introspection fails for me, I thought to continue
> updating "the rest" if possible.
>
> I tried:
> pkg_rolling-replace -uv -x gobject-introspection
>
> and even:
> pkg_rolling-replace -uv -X gobject-introspection
You want "-X".
> but I still ge
Hi!
since build of gobject-introspection fails for me, I thought to continue
updating "the rest" if possible.
I tried:
pkg_rolling-replace -uv -x gobject-introspection
and even:
pkg_rolling-replace -uv -X gobject-introspection
but I still get stuck there as the first package in update!
Why th
Hi!
after upgrading all to 9.9.52... and finding it again acceptably stable
(only wifi issues.. but that about later) I am doing a full pkgsrc
rolling update
gobject-introspection fails:
[104/163] Generating gir-glib with a custom command
FAILED: gir/GLib-2.0.gir
/usr/pkg/bin/python3.7 tools/g-i
In article ,
Andrius V wrote:
>There's a mistake in rdcpicb.c patch. Last ID duplicated, should be {
>PCI_VENDOR_RDC, PCI_PRODUCT_RDC_R6036_PCIB}.
>
Thanks, I committed the first two, but not the one below because I am not
sure if the change in the mask is correct. Where are the bit values
docum
Hi,
The above panic is repeatable - just build the latest version of
nodejs and run 'make test':
Command: out/Release/node
/usr/pkgsrc/lang/nodejs/work/node-v13.12.0/test/parallel/test-process-execpath.js
[01:07|% 57|+ 1694|- 4]: release test-process-uncaught-exception-monitor
.
This
Hi,
On NetBSD 9.99.54 (GENERIC) #0: Sun Apr 5 11:58:20 BST 2020 I just got:
...
panic: kernel diagnostic assertion "semcnt >= 0" failed: file
"/home/sysbuild/src/sys/kern/kern_uidinfo.c", line 241
cpu4: Begin traceback...
vpanic() at netbsd:vpanic+0x178
kern_assert() at netbsd:kern_assert+0x48
c
NetBSD Test Fixture wrote:
> This is an automatically generated notice of new failures of the
> NetBSD test suite.
>
> The newly failing test cases are:
>
> fs/puffs/t_basic:root_chrdev
> fs/puffs/t_basic:root_fifo
> fs/puffs/t_basic:root_lnk
(etc)
These are already reported in kern/
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
fs/puffs/t_basic:root_chrdev
fs/puffs/t_basic:root_fifo
fs/puffs/t_basic:root_lnk
fs/puffs/t_basic:root_reg
fs/puffs/t_fuzz:mountfuzz8
fs/vfs/t_full:udf_fi
15 matches
Mail list logo
