Re: xfwm4 crashes on NetBSD 9.99.17 (was "Re: firefox dumping core after NetBSD upgrade")
On Tue, 2019-10-29 at 19:52 -0400, David H. Gutteridge wrote: > On Tue, 2019-10-29 at 10:38 +, Chavdar Ivanov wrote: > > I've tested xfce4 - a few days old build from -current pkgsrc - now > > on > > real hardware with functional dri2. I get the same as with the > > VirtualBox client - I have to disable compositing to get xfwm4 > > working. At the same time glmark2 returns the usual or close to > > results. > > What do you find if you disable compositing to get Xfce to start, and > then enable it once xfwm4 is running successfully? I find that seems > to > work. So it fails some sort of initial probing, but then is able to > activate the feature later, anyway. (As if there are two different > code > paths for this, or something is getting corrupted in memory during > start up, but that isn't happening later on. I haven't had a chance to > look at it in gdb again, yet.) Sorry, that's the wrong example, the right example is: - Move or delete the xfwm4.xml file from the .config path - Start Xfce - Go to Window Manager Tweaks->Compositor - Note that the compositor is enabled, and related setting changes (e.g. opacity of window decorations) successfully apply. Yet, on the next startup cycle, xfwm4 crashes. (And it crashes with my previous example of starting with the compositor turned off, and then turning it on.) Regards, Dave
daily CVS update output
Updating src tree: P src/distrib/sets/lists/man/mi P src/doc/CHANGES P src/etc/MAKEDEV.tmpl P src/share/man/man4/Makefile U src/share/man/man4/smscphy.4 P src/share/mk/bsd.README P src/share/mk/bsd.own.mk P src/sys/arch/amd64/conf/ALL P src/sys/arch/amd64/conf/GENERIC U src/sys/arch/arm/dts/omap3-n900.dts P src/sys/arch/arm/ti/files.ti U src/sys/arch/arm/ti/omap3_dss.c U src/sys/arch/arm/ti/omap3_dssreg.h P src/sys/arch/arm/ti/ti_iic.c P src/sys/arch/arm/ti/ti_iicreg.h P src/sys/arch/evbarm/conf/GENERIC P src/sys/arch/i386/conf/ALL P src/sys/arch/i386/conf/GENERIC P src/sys/dev/DEVNAMES P src/sys/dev/mii/files.mii U src/sys/dev/mii/smscphy.c P src/sys/dev/usb/if_urndis.c P src/usr.sbin/sysinst/Makefile.inc Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 43022091 Nov 1 03:04 ls-lRA.gz
Re: Is KUBSAN broken?
On 31.10.2019 01:16, Kamil Rytarowski wrote: > On 30.10.2019 14:49, SAITOH Masanobu wrote: >> Hi. >> >> Today, I updated three amd64 machines to the latest -current and >> all of them didn't boot. All of them use "options KUBSAN". Two of >> them stuck at after "loading /var/db/entropy-file" and another >> machine reset after loading the kernel. Without KUBSAN, all of the >> machines boot. >> >> OK: 2019/10/28 06:31:39 >> NG: 2019/10/30 02:44:29 >> > > I will try to reproduce it and bisect. > > It looks like syzbot is down too. > > https://syzkaller.appspot.com/bug?id=b439b7b09227095aec40d333565190be9272c7b6 > OK. The culprit reason for kUBSan breakage is GCC8 switch. If it worked after that date, it was rather and accident and tools were not rebuilt. I'm trying to make sense of what is going on and I will fix it. signature.asc Description: OpenPGP digital signature
Panic on NetBSD-9 using zfs receive and xen
hello. I'm experimenting with a NetBSD-9 Xen server running zfs volumes as domU disks. While runing a zfs receive of a snapshot of a domU disk from another server, I experienced the following crash. While this could be zfs related, I've been running zfs receives numerous times on the system without a problem. This is on Dom0 with 8GB of RAm and 1 CPU. This is from NetBSD-9_BETA from about September 25, 2019. I wasn't able to get a crash dump, but, maybe, this log will help figure out what's going wrong. It seems like a race condition in the pool code, but I'm not familiar with that part of the kernel enough to provide a lot of detail at the moment. has anyone else seen this issue? Is it a known problem or should I file a bug? -thanks -Brian [ 12156.8100589] panic: kernel diagnostic assertion "(pp->pr_nout > 0)" failed: file "/usr/local/netbsd/src-90/sys/kern/subr_pool.c", line 1146 pool_do_put: [xbbrp] putting with none out [ 12156.8100589] cpu0: Begin traceback... [ 12156.8100589] vpanic() at netbsd:vpanic+0x143 [ 12156.8100589] kern_assert() at netbsd:kern_assert+0x48 [ 12156.8100589] pool_put() at netbsd:pool_put+0x5b6 [ 12156.8100589] pool_cache_invalidate_groups() at netbsd:pool_cache_invalidate_groups+0x59 [ 12156.8100589] pool_reclaim() at netbsd:pool_reclaim+0x72 [ 12156.8100589] pool_drain() at netbsd:pool_drain+0x85 [ 12156.8200580] uvmpd_pool_drain_thread() at netbsd:uvmpd_pool_drain_thread+0x74 [ 12156.8200580] cpu0: End traceback... [ 12156.8200580] dumping to dev 168,11 (offset=2097007, size=0): not possible [ 12156.8200580] rebooting...
Re: scp protocol error on multiple file copy?
On Thu, 31 Oct 2019, John D. Baker wrote: > I added the "-T" switch (disable strict filename checking) and that made > it work. > > I'll need to check, but as I use 'ksh' as login shell it would be nice > if ksh/bash filename-generation [ !(), @(), etc. ] could be used. Maybe > it's only available in interactive shells? I added the "-v" verbose switch to one of the failing command forms. I used (ksh filename generation): $ scp -v -T -p buildhost:"/path/to/@(sets/@([bem*|text.tgz)|kernel/netbsd-CUSTOM.gz)" . On the remote, it invokes 'scp' with an undocumented "-f" (lowercase "f") switch: debug1: Sending command: scp -v -p -f /path/to/@(sets/@([bem*|text.tgz)|kernel/netbsd-CUSTOM.gz) passing it the path/fileglob given on the local host. That is what then reports "No such file or directory." which is passed back to the local side. Sink: \001scp: /path/to/@(sets/@([bem*|text.tgz)|kernel/netbsd-CUSTOM.gz): No such file or directory scp: /path/to/@(sets/@([bem*|text.tgz)|kernel/netbsd-CUSTOM.gz): No such file or directory Adding "-v" to my original multiple-path source file form shows that it checks timestamps on the first matching file of the [bem]* glob and extracts the matching name, but then complains when that isn't a literal match for what was given on the command line. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: scp protocol error on multiple file copy?
On Wed, 30 Oct 2019, John D. Baker wrote: > used a command line like: > > $ scp -p buildhost:"/path/to/sets/[bem]* /path/to/sets/text.tgz > /path/to/kernel/netbsd-CUSTOM.gz" . > > to copy relevant sets and kernel to the machine's local disk. > > Today when I tried my usual procedure to update this host, I instead got: > > protocol error: filename does not match request I added the "-T" switch (disable strict filename checking) and that made it work. I'll need to check, but as I use 'ksh' as login shell it would be nice if ksh/bash filename-generation [ !(), @(), etc. ] could be used. Maybe it's only available in interactive shells? -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
re: scp protocol error on multiple file copy?
On Thu, 31 Oct 2019 16:46:47 - (UTC), mlel...@serpens.de (Michael
van Elst) wrote:
> jdbaker%consolidated.net@localhost ("John D. Baker") writes:
>
> > $ scp -p buildhost:'/path/to/{sets/text.tgz,kernel/netbsd-CUSTOM.gz}' .
>
> >It prompted for the password and then I got:
>
> > scp: /path/to/{sets/text.tgz,kernel/netbsd-CUSTOM.gz}: No such file or
> > directory
>
>
> % scp fud:'raid{0,1}.label' .
> raid0.label 100% 894 250.4KB/s 0.9KB/s
>
> raid1.label 100% 890 307.0KB/s 0.9KB/s
>
>
> % scp fud:'notthere/raid{0,1}.label' .
> scp: notthere/raid0.label: No such file or directory
> scp: notthere/raid1.label: No such file or directory
>
> Seems to work.
>
> However:
>
> % scp fud:'raid{0,1}.label' .
> foo
>
> scp is just using ssh to run an scp command on the remote machine and
> parsing the data sent to stdout. In this case I added a 'echo foo'
> to the remote .cshrc file (with tcsh as login shell).
>
> Also
>
> % scp fud:'raid{0,1}.label' .
> scp: raid{0,1}.label: No such file or directory
>
> happens when I change the login shell to /bin/sh (or /bin/ksh) on the
> remote machine because sh and ksh don't understand this syntax.
I see. I use ksh everywhere as login shell, so that explains the
C-shell-style filename globbing failures. Odd that it doesn't seem to
be able to cope with ksh filename generation: !(), @(), etc., but simple
sh-style globbing works.
It would be neat if it could be told to run an arbitrary shell, but
that's probably a gaping security hole...
In any event, I wonder what changed to cause the original error I
saw. The multiple-source-file syntax I illustrated used to work.
--
|/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD
| X No HTML/proprietary data in email. BSD just sits there and works!
|/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: scp protocol error on multiple file copy?
jdba...@consolidated.net ("John D. Baker") writes:
> $ scp -p buildhost:'/path/to/{sets/text.tgz,kernel/netbsd-CUSTOM.gz}' .
>It prompted for the password and then I got:
> scp: /path/to/{sets/text.tgz,kernel/netbsd-CUSTOM.gz}: No such file or
> directory
% scp fud:'raid{0,1}.label' .
raid0.label 100% 894 250.4KB/s 0.9KB/s
raid1.label 100% 890 307.0KB/s 0.9KB/s
% scp fud:'notthere/raid{0,1}.label' .
scp: notthere/raid0.label: No such file or directory
scp: notthere/raid1.label: No such file or directory
Seems to work.
However:
% scp fud:'raid{0,1}.label' .
foo
scp is just using ssh to run an scp command on the remote machine and
parsing the data sent to stdout. In this case I added a 'echo foo'
to the remote .cshrc file (with tcsh as login shell).
Also
% scp fud:'raid{0,1}.label' .
scp: raid{0,1}.label: No such file or directory
happens when I change the login shell to /bin/sh (or /bin/ksh) on the
remote machine because sh and ksh don't understand this syntax.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
re: undefined reference in system library on netbsd-9/sparc
(For some reason, your recent messages have not reached me--not even quarantined by my ISP's web-mail system.) On Wed, 30 Oct 2019 13:34:12 +1100, matthew green wrote: > "John D. Baker" writes: > > > > Whatever was available in 8.99.26 was sufficient for the purpose. I have > > never had a problem building "sysutils/apcupsd" on sparc until now. Been > > building it since netbsd-6 days at least. > > yeah - it's likely GCC 8 fallout. GCC 8? Perhaps there were forward-looking changes intended for the eventual import of GCC 8 that are already in netbsd-9 which is using GCC 7? I'm presently updating packages on -current/sparc (9.99.17) which is still using GCC 7 at this point. I'll see how it behaves when it gets to 'apcupsd'. If -current/sparc gets switched to GCC 8 soon, I'll start over and see how that goes. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
re: scp protocol error on multiple file copy?
(For some reason, your recent messages have not reached me at all, not
even quarantined on my ISP's web-mail system.)
On Thu, 31 Oct 2019 17:14:46 +1100, matthew green
wrote:
> this is odd. probably some recent change is trying to protect you..
>
> can you try eg:
>
>scp buildhost:'{file1,file2}' .
>
> to copy multiple files? ie, use shell globbing with a single word
> vs multiple words..
I don't think 'scp' understands C-shell-style globbing (w/braces,etc.).
I used something like:
$ scp -p buildhost:'/path/to/{sets/text.tgz,kernel/netbsd-CUSTOM.gz}' .
It prompted for the password and then I got:
scp: /path/to/{sets/text.tgz,kernel/netbsd-CUSTOM.gz}: No such file or
directory
(It would be nice if it did so I wouldn't have to repeat common parts
of a long path.)
--
|/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD
| X No HTML/proprietary data in email. BSD just sits there and works!
|/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: Size differences between yacc and bison
On Thu, Oct 31, 2019 at 09:00:53AM +0100, Anders Magnusson wrote: > Here are the results, using gcc as the compiler: > > bison: > nbi386:/home/ragge/pcc/cc/ccom >size cgram.o > text data bss dec hex filename > 25637 0 0 25637 6425 cgram.o > > yacc: > nbi386:/home/ragge/pcc/cc/ccom >size cgram.o > text data bss dec hex filename > 57914 0 24 57938 e252 cgram.o The generated automatons seem to be nearly identical, but the table encoding differs: bison uses uint8 and uint16 types in a lot of static tables, while yacc seems to generically use YYINT (which is typedef'd to int). Not sure if that explains it all though, but maybe a good first thing to check. Martin
Size differences between yacc and bison
Hi, while compiling pcc I saw that the resulting binary for the grammar differs very much in size (!). Anyone have any ideas about this before I start trying to find out what's "wrong" with yacc? Here are the results, using gcc as the compiler: bison: nbi386:/home/ragge/pcc/cc/ccom >size cgram.o text data bss dec hex filename 25637 0 0 25637 6425 cgram.o yacc: nbi386:/home/ragge/pcc/cc/ccom >size cgram.o text data bss dec hex filename 57914 0 24 57938 e252 cgram.o -- Ragge
Size differences between yacc and bison
Hi, while compiling pcc I saw that the resulting binary for the grammar differs very much in size (!). Anyone have any ideas about this before I start trying to find out what's "wrong" with yacc? Here are the results, using gcc as the compiler: bison: nbi386:/home/ragge/pcc/cc/ccom >size cgram.o text data bss dec hex filename 25637 0 0 25637 6425 cgram.o yacc: nbi386:/home/ragge/pcc/cc/ccom >size cgram.o text data bss dec hex filename 57914 0 24 57938 e252 cgram.o -- Ragge
Re: time(1) reporting corrupted system time
Mateusz Guzik wrote: > Hi, I failed to find a follow up to this. > > I see someone gave the you the fix for corrupted time accounting. > Did you get around to finding the offending commit? For the corrupted system time, I believe the offending commit was kern_resource.c 1.180, and the fix was 1.182. As for the increased system time taken by release builds, it has happened in multiple steps. I have bisected the largest increases, but analyzing and writing up the results for current-users is still on my "to do" list. -- Andreas Gustafsson, g...@gson.org
re: scp protocol error on multiple file copy?
this is odd. probably some recent change is trying to protect you..
can you try eg:
scp buildhost:'{file1,file2}' .
to copy multiple files? ie, use shell globbing with a single word
vs multiple words..
.mrg.
