Re: Xorg applications take ages to load, unless started from xterm
On 23.11.2014 23:30, Ottavio Caruso wrote: Hello, this is a fresh installation of 6.1.5_PATCH on amd64. When I "startx", it takes ages to load the graphical environment, when I am in fluxbox and I launch applications from the menu, again it takes ages. However if I then launch applications from xterm they load quite fast. I've activated xdm, the login process is quite fast, once in fluxbox I have the same problems. I post warnings and errors from xorg.log: $ egrep "WW|EE" /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [34.180] (II) Loading extension MIT-SCREEN-SAVER [34.667] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [34.782] (WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB [35.010] (WW) intel(0): remove MTRR a - b [35.811] (WW) intel(0): remove MTRR a - b [35.866] (WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc008 to 0xd009 [35.866] (WW) intel(0): PP_STATUS before: on, ready, sequencing idle [35.866] (WW) intel(0): PP_STATUS after: on, ready, sequencing on [35.891] (WW) intel(0): DRI2 requires UXA [36.038] (WW) intel(0): remove MTRR a - b [36.131] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [37.561] (EE) AIGLX error: i965 does not export required DRI extension [37.568] (EE) AIGLX: reverting to software rendering [45.466] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 108.848] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 151.070] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 164.372] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 207.694] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 211.871] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 289.225] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 303.177] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 303.676] (WW) intel(0): ESR is 0x0001 [ 303.676] (WW) intel(0): Existing errors found in hardware state. [ 316.012] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 327.302] (WW) intel(0): drmDropMaster failed: Unknown error: 4294967295 [ 327.800] (WW) intel(0): ESR is 0x0001 [ 327.800] (WW) intel(0): Existing errors found in hardware state. Any ideas? Not sure what type of Intel VGA card you have, but support for those like HD3000 and such is in current NetBSD, not in 6.1.5. As well seems like you have 2 VGA cards in your computer and system can't decide properly which one to use. Can you disable one in BIOS?
Re: poor write performances with RAID 5 Raidframe
On 30.11.2014 00:18, Emile `iMil' Heitor wrote: Hi, I'm witnessing poor performances while writing to a RAID 5 Raidframe I setup to be my home NAS a couple of months ago. Following some documentations, tutorials, and mailing-list posts, I think I had everything aligned right as the following configuration suggests: raid1.conf: START array # numRow numCol numSpare 1 3 0 START disks /dev/wd2a /dev/wd3a /dev/wd4a START layout # sectPerSU SUsPerParityUnit SUsPerReconUnit RAID_level_5 64 1 1 5 START queue fifo 100 # gpt show raid1 startsize index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 94 128 7814057951 1 GPT part - NetBSD FFSv1/FFSv2 7814058079 32 Sec GPT table 7814058111 1 Sec GPT header # dkctl raid1 listwedges /dev/rraid1d: 1 wedge: dk0: 5bdb599c-744a-11e3-9160-002354666e0f, 7814057951 blocks at 128, type: ffs newfs(8) was done like this: # newfs -O2 -b64k -I dk0 The disks involved are Seagate Barracuda which are known to have as such high write transfer rate as ~100MB/s, and I merely get a 25MB/s with those: $ dd if=/dev/zero of=/export/imil/tmp/test bs=1m count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 42.619 secs (24603486 bytes/sec) On the other hand, read speed is really good: $ dd if=/export/imil/media/foobar_adventures.mp4 of=/dev/null bs=1m 1395+1 records in 1395+1 records out 1463376863 bytes transferred in 7.899 secs (185261028 bytes/sec) Any advice on this matter? Does this configuration looks good? This may help you a lot http://constantin.glez.de/blog/2010/01/home-server-raid-greed-and-why-mirroring-still-best Thanks, Emile `iMil' Heitor * _ | http://imil.net| ASCII ribbon campaign ( ) | http://www.NetBSD.org | - against HTML email X | http://gcu.info| & vCards / \
Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
Hi all, original questions is now nearly one year old https://mail-index.netbsd.org/pkgsrc-users/2019/12/10/msg029983.html There was no response and I can confirm that problem still exists on 9.1 stable amd64 and evbarm. Are developers at least aware that there is such problem and freerdp2 is not working with newer Windows hosts over RDP? evbarm: $ uname -a NetBSD armv7 9.1_STABLE NetBSD 9.1_STABLE (GENERIC) #0: Tue Nov 10 11:45:35 UTC 2020 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/evbarm/compile/GENERIC evbarm $ [19:45:51:767] [2861:67ec4000] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state [19:45:51:773] [2861:67ec4000] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [19:45:51:777] [2861:67ec4000] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [19:45:51:782] [2861:67ec4000] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [19:45:51:808] [2861:67ec4000] [INFO][com.freerdp.client.x11] - Property 256 does not exist [19:45:51:219] [2861:67ec4000] [INFO][com.freerdp.primitives] - primitives autodetect, using generic [19:45:51:354] [2861:67ec4000] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state [19:45:51:355] [2861:67ec4000] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state [19:45:53:759] [2861:67ec4000] [WARN][com.freerdp.crypto] - Certificate verification failure 'self signed certificate in certificate chain ( Do you trust the above certificate? (Y/T/N) Y [19:45:55:231] [2861:67ec4000] [ERROR][com.winpr.timezone] - StandardName conversion failed - using default [19:45:55:337] [2861:67ec4000] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 0: Undefined error: 0 [19:45:55:337] [2861:67ec4000] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] [19:45:55:358] [2861:67ec4000] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state [19:45:55:359] [2861:67ec4000] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state [19:45:57:497] [2861:67ec4000] [ERROR][com.winpr.timezone] - StandardName conversion failed - using default [19:45:58:607] [2861:67ec4000] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 0: Undefined error: 0 [19:45:58:607] [2861:67ec4000] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] [19:45:58:608] [2861:67ec4000] [ERROR][com.freerdp.core] - freerdp_post_connect failed $ pkg_info -c freerdp2 Information for freerdp2-2.1.1: Comment: Free implementation of the Remote Desktop Protocol (major version 2) $ $ date Mon Nov 16 19:53:06 CET 2020 $ $ ntpq -p remote refid st t when poll reach delay offset jitter == 2.netbsd.pool.n .POOL. 16 p- 6400.0000.000 0.002 +mail.spamassass 147.231.2.6 2 u 438 512 377 11.270 -0.135 0.657 *ntp.suas.cz .PHC0. 1 u 475 512 377 11.507 -0.982 0.577 +lhx.cz 147.231.100.52 u 944 512 3768.682 -0.913 1.253 -mail.spamassass 147.231.2.6 2 u 977 512 376 11.642 -0.208 0.651 -time.cloudflare 10.31.8.43 u 723 1024 3778.322 -1.429 0.775 $ DNS, VPN, browser all runs fine regarding time and related things. Not subscribed to lists so please cc
Re: Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
On 17.11.2020 09:00, Martin Husemann wrote: On Mon, Nov 16, 2020 at 07:54:38PM +0100, Bodie wrote: [19:45:55:337] [2861:67ec4000] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] [19:45:55:358] [2861:67ec4000] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state Why do you think this is related to the timer_* issue that they fixed? Because I am still getting this: $ uname -a NetBSD hostname 9.1_STABLE NetBSD 9.1_STABLE (GENERIC) #0: Sat Nov 14 15:38:43 UTC 2020 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 $ [09:28:48:378] [2337:82f08000] [ERROR][com.winpr.synch.timer] - InitializeWaitableTimer: os specific implementation is missing In my build log I see: -- Looking for timer_create - found -- Looking for timer_delete - found -- Looking for timer_settime - found -- Looking for timer_gettime - found so this looks good. Should I see these syscalls in ktruss output? Because I can't see them The client command line and help is so obfuscated thought that I did not manage to actually use it: [08:55:19:195] [17803:40b2bc00] [ERROR][com.freerdp.core] - nla_recv_pdu:freerdp_set_last_error_ex ERRCONNECT_LOGON_FAILURE [0x00020014] ... which probably means I got some \ wrong or used bogus authentication options. In FreeBSD they did this https://github.com/FreeRDP/FreeRDP/pull/4608/files as patch file to that winpr/libwinpr/CMakeLists.txt , but in pkgsrc I can't see it in patches (and to be honest not sure if it is needed if NetBSD has timer_create and others) Martin
Re: Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
On 17.11.2020 09:00, Martin Husemann wrote: On Mon, Nov 16, 2020 at 07:54:38PM +0100, Bodie wrote: [19:45:55:337] [2861:67ec4000] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] [19:45:55:358] [2861:67ec4000] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state Why do you think this is related to the timer_* issue that they fixed? and here is the output from ktruss between last regular message (which shows on FreeBSD too) and timer error: "[09:36:09:413] [1671:d46fb000] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd\n" 1671 8 xfreerdp2 mmap(0, 0x20, 0x3, 0x1002, 0x, 0, 0) = 0x78d8beaef000 1671 8 xfreerdp2 munmap(0x78d8beaef000, 0x20) = 0 1671 8 xfreerdp2 mmap(0, 0x3ff000, 0x3, 0x15001002, 0x, 0, 0) = 0x78d8be80 1671 8 xfreerdp2 munmap(0x78d8bea0, 0x1ff000) = 0 1671 8 xfreerdp2 __clock_gettime50(0x3, 0x78d8bf0feb60) = 0 1671 8 xfreerdp2 __clock_gettime50(0x3, 0x78d8bf0feb60) = 0 1671 8 xfreerdp2 __clock_gettime50(0x3, 0x78d8bf0feb80) = 0 1671 8 xfreerdp2 mmap(0, 0x1000, 0x3, 0x1002, 0x, 0, 0) = 0x78d8d4328000 1671 8 xfreerdp2 mmap(0, 0x5000, 0x3, 0x1002, 0x, 0, 0) = 0x78d8d4323000 1671 2 xfreerdp2 _ksem_init = 0 1671 2 xfreerdp2 pipe() = 75, 76 1671 2 xfreerdp2 pipe() = 77, 78 1671 8 xfreerdp2 mmap = 0x78d8d4322000 1671 2 xfreerdp2 fcntl(0x4d, 0x3, 0x4e) = 0 1671 8 xfreerdp2 _ksem_init(0, 0x78d8bf0fee38) = 0 1671 8 xfreerdp2 mmap(0, 0x3000, 0x3, 0x1002, 0x, 0, 0) = 0x78d8d431f000 1671 2 xfreerdp2 fcntl(0x4d, 0x4, 0x4) = 0 1671 2 xfreerdp2 read(0x4d, 0x78d8c33fdafc, 0x1) Err#35 EAGAIN 1671 2 xfreerdp2 mmap(0, 0x41, 0x3, 0x1002, 0x, 0, 0) = 0x78d8be3f 1671 2 xfreerdp2 mprotect(0x78d8be3f, 0x1, 0) = 0 1671 2 xfreerdp2 _lwp_self()= 2 1671 2 xfreerdp2 __sigprocmask14(0x1, 0x78d8c33fda00, 0x78d8c33fda40) = 0 1671 2 xfreerdp2 __sigprocmask14(0x3, 0x78d8c33fda40, 0) = 0 1671 2 xfreerdp2 getcontext(0x78d8c33fd740) = 0 1671 2 xfreerdp2 _lwp_create(0x78d8c33fd740, 0x40, 0x78d8d4645310) = 0 1671 2 xfreerdp2 poll(0x78d8c33fdc40, 0x1, 0) = 0 1671 2 xfreerdp2 write(0x8, 0x78d8d0c9982b, 0x1) = 1 "-" 1671 2 xfreerdp2 __gettimeofday50(0x78d8c33fb550, 0) = 0 1671 2 xfreerdp2 __gettimeofday50(0x78d8c33fb550, 0) = 0 1671 2 xfreerdp2 getpid() = 1671, 740 1671 2 xfreerdp2 write(0x2, 0x78d8c33fb330, 0x7f) = 127 "[09:36:09:414] [1671:d46fb000] [ERROR][com.winpr.synch.timer] - InitializeWaitableTimer: os specific implementation is missing\n" in FreeBSD it looks like this: "[09:46:06:406] [1114:01e7ea00] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd " 1114 xfreerdp CALL munmap(0x8050b9000,0x147000) 1114 xfreerdp RET write 116/0x74 1114 xfreerdp RET munmap 0 1114 xfreerdp CALL munmap(0x80540,0xb8000) 1114 xfreerdp RET munmap 0 1114 xfreerdp CALL mmap(0,0x1000,0x3,0x1002,0x,0) 1114 xfreerdp RET mmap 3382208/0x8050b9000 1114 xfreerdp CALL mmap(0,0x5000,0x3,0x1002,0x,0) 1114 xfreerdp RET mmap 3386304/0x8050ba000 1114 xfreerdp CALL mmap(0,0x1000,0x3,0x1002,0x,0) 1114 xfreerdp RET mmap 3406784/0x8050bf000 1114 xfreerdp CALL poll(0x7fffdf3f7ea0,0x1,0x) 1114 xfreerdp CALL pipe2(0x802d24570,0) 1114 xfreerdp RET pipe2 0 1114 xfreerdp CALL pipe2(0x802d5ac54,0) 1114 xfreerdp RET pipe2 0 1114 xfreerdp CALL fcntl(0x30,F_GETFL) 1114 xfreerdp RET fcntl 2 1114 xfreerdp CALL fcntl(0x30,F_SETFL,0x6) 1114 xfreerdp RET fcntl 0 1114 xfreerdp CALL mmap(0,0x1000,0x3,0x1002,0x,0) 1114 xfreerdp RET mmap 3410880/0x8050c 1114 xfreerdp CALL read(0x30,0x7fffdfffdb14,0x1) 1114 xfreerdp RET read -1 errno 35 Resource temporarily unavailable 1114 xfreerdp CALL mmap(0x7fffdeff6000,0x201000,0x3,0x400,0x,0) 1114 xfreerdp RET mmap 140736934666240/0x7fffdeff6000 1114 xfreerdp CALL mprotect(0x7fffdeff6000,0x1000,0) 1114 xfreerdp RET mprotect 0 1114 xfreerdp CALL thr_new(0x7fffdfffda10,0x68) 1114 xfreerdp RET thr_new 0 1114 xfreerdp CALL poll(0x7fffdfffdc00,0x1,0) 1114 xfreerdp RET poll 0 1114 xfreerdp CALL write(0x4,0x8006bbdd9,0x1) 1114 xfreerdp GIO fd 4 wrote 1 byte "-" 1114 xfreerdp RET write 1 1114 xfreerdp CALL kqueue 1114 xfreerdp RET kqueue 50/0x32 1114 xfreerdp CALL kevent(0x32,0x7fffdfffd9e0,0x1,0,0,0)
Re: Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
On 17.11.2020 10:48, Martin Husemann wrote: On Tue, Nov 17, 2020 at 09:32:39AM +0100, Bodie wrote: [09:28:48:378] [2337:82f08000] [ERROR][com.winpr.synch.timer] - InitializeWaitableTimer: os specific implementation is missing I don't get that, so the failure does not happen for all architectures/ versions of NetBSD. Maybe something is broken with the cmake test for that? Remote end is Windows 2016 server (and rdesktop can't connect to those, but xfreerdp2 can (if it does not fail on POSIX timers of course) Using eg. this: xfreerdp2 /sec:tls /size:95% /u:username /d:AD /p:XXX /v:X.X.X.X' Works fine on FreeBSD and Linux obviously, on OpenBSD they keep back on RC version of freerdp2 as they do not have that timer_create() interface, but it works there too with same command Trying to find what may be wrong, but that patch from FreeBSD may be pointing to those cmake tests (had no time yet to dive in pkgsrc after years and try to see what is what there and what is patched if anything at all) Code itself https://github.com/FreeRDP/FreeRDP/blob/master/winpr/libwinpr/CMakeLists.txt contains checks which FreeBSD added as a patch in ports. Does it mean that similar patch is needed for pkgsrc too? Martin
Re: Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
On 17.11.2020 11:22, Bodie wrote: On 17.11.2020 10:48, Martin Husemann wrote: On Tue, Nov 17, 2020 at 09:32:39AM +0100, Bodie wrote: [09:28:48:378] [2337:82f08000] [ERROR][com.winpr.synch.timer] - InitializeWaitableTimer: os specific implementation is missing I don't get that, so the failure does not happen for all architectures/ versions of NetBSD. Maybe something is broken with the cmake test for that? Remote end is Windows 2016 server (and rdesktop can't connect to those, but xfreerdp2 can (if it does not fail on POSIX timers of course) Using eg. this: xfreerdp2 /sec:tls /size:95% /u:username /d:AD /p:XXX /v:X.X.X.X' Works fine on FreeBSD and Linux obviously, on OpenBSD they keep back on RC version of freerdp2 as they do not have that timer_create() interface, but it works there too with same command Trying to find what may be wrong, but that patch from FreeBSD may be pointing to those cmake tests (had no time yet to dive in pkgsrc after years and try to see what is what there and what is patched if anything at all) Code itself https://github.com/FreeRDP/FreeRDP/blob/master/winpr/libwinpr/CMakeLists.txt contains checks which FreeBSD added as a patch in ports. Does it mean that similar patch is needed for pkgsrc too? I think it relates to this file: https://github.com/akallabeth/FreeRDP/blob/60bf33f79d55c493eca89c8e570c6e543affd82a/winpr/libwinpr/synch/CMakeLists.txt where only if(FREEBSD) is defined? Martin
Re: Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
On 17.11.2020 15:19, nia wrote: On Tue, Nov 17, 2020 at 11:22:24AM +0100, Bodie wrote: Works fine on FreeBSD and Linux obviously, on OpenBSD they keep back on RC version of freerdp2 as they do not have that timer_create() interface, but it works there too with same command The code in 2.0.0-rc1 is the same, though? Don't know what were the reasons on OpenBSD to stay on rc1, at least did not find anything regarding this. But POSIX timer change come in rc3 https://github.com/FreeRDP/FreeRDP/pull/4608
Re: Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
On 17.11.2020 18:06, nia wrote: I read the actual code that uses POSIX timers, it hasn't changed at all in the various release candidates. It all started with this https://github.com/FreeRDP/FreeRDP/issues/4592 If you want to simulate building with POSIX timer support disabled, you can do the following: BUILDLINK_TRANSFORM+= rm:-DWITH_POSIX_TIMER The FreeBSD-related PR you linked to enables Linux epoll emulation for a specific code path. If you want to test if that code path is reached, edit the "os specific implementation is missing" messages in work/freerdp-2.1.2/winpr/libwinpr/synch/timer.c. Note that there are two such messages, and both are identical. It would be useful to know which one is being triggered. It's possible we need to either: 1) Enable the "__APPLE__" code paths in that file on NetBSD too. 2) Borrow the epoll emulation code. I can't test this because I don't have a Windows machine to connect to... I can test as I do have access to various versions of Windows. In fact I am testing in any case as it will be good to have working. Probably I will start with going to current to see the difference as Martin says it somewhat works for him
Re: Tunneling in NetBSD
On 17.11.2020 21:58, Brett Lymn wrote: On Mon, Nov 16, 2020 at 03:50:21PM +0200, Andreas Gustafsson wrote: Greg Troxel wrote: > My suggestion is openvpn. [...] > You do need to set up certificates Not if you use the static key encryption mode. Whilst this is correct the OP did mention android which could mean a mobile device on the internet. In this case, certificate based identity is the simplest and most secure way of identifying the end points. Years ago I used NetBSD to configure a vpn end point for a clint, I used hybrid xauth which was a combination of a certificate as well as username/password that allowed two classes of access to the network, one being restricted to certain services and another admin role that had broader access. The clients were mostly windows pcs. Certainly, start with preshared keys to get the basic vpn config working even if you plan something more complex, debugging a psk setup is comparatively easy. Once psk is working switch the auth to what is desired to debug that. Or something way easier? https://www.wireguard.com/
Re: Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
On 17.11.2020 18:16, Bodie wrote: On 17.11.2020 18:06, nia wrote: I read the actual code that uses POSIX timers, it hasn't changed at all in the various release candidates. It all started with this https://github.com/FreeRDP/FreeRDP/issues/4592 If you want to simulate building with POSIX timer support disabled, you can do the following: BUILDLINK_TRANSFORM+= rm:-DWITH_POSIX_TIMER The FreeBSD-related PR you linked to enables Linux epoll emulation for a specific code path. If you want to test if that code path is reached, edit the "os specific implementation is missing" messages in work/freerdp-2.1.2/winpr/libwinpr/synch/timer.c. Note that there are two such messages, and both are identical. It would be useful to know which one is being triggered. It's possible we need to either: 1) Enable the "__APPLE__" code paths in that file on NetBSD too. 2) Borrow the epoll emulation code. I can't test this because I don't have a Windows machine to connect to... I can test as I do have access to various versions of Windows. In fact I am testing in any case as it will be good to have working. Probably I will start with going to current to see the difference as Martin says it somewhat works for him So here is the test: netbsd$ xfreerdp2 --version This is FreeRDP version 2.1.2 (2.1.2) netbsd$ uname -a NetBSD netbsd 9.99.75 NetBSD 9.99.75 (GENERIC) #0: Tue Nov 17 04:50:29 UTC 2020 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 netbsd$ compiled freerdp2 from current pkgsrc against Windows server 2016 build 1607: [07:01:46:382] [19612:dbca8000] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [07:01:46:382] [19612:dbca8000] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [07:01:46:439] [19612:dbca8000] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem [07:01:46:458] [19612:dbca8000] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd [07:01:46:459] [19612:dbca8000] [ERROR][com.winpr.synch.timer] - InitializeWaitableTimer: os specific implementation is missing netbsd$ This is without any modifications anywhere.
Re: Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
On 17.11.2020 18:06, nia wrote:
I read the actual code that uses POSIX timers, it hasn't changed at all
in the various release candidates.
If you want to simulate building with POSIX timer support disabled,
you can do the following:
BUILDLINK_TRANSFORM+= rm:-DWITH_POSIX_TIMER
Well but it is known that freerdp2 will not connect without those POSIX
timers
The FreeBSD-related PR you linked to enables Linux epoll emulation for
a specific code path.
Well initially they put another ifdef for FREEBSD, but it was removed by
this
https://github.com/FreeRDP/FreeRDP/issues/4592
Funny how they mention they do not want to "whitelist" every OS, but yet
in
code they left whitelists/ifdefs for Apple :-D
If you want to test if that code path is reached, edit the
"os specific implementation is missing" messages in
work/freerdp-2.1.2/winpr/libwinpr/synch/timer.c.
I tested ;-)
[19:36:37:151] [7164:29fd6000] [INFO][com.freerdp.gdi] - Local
framebuffer format PIXEL_FORMAT_BGRX32
[19:36:37:151] [7164:29fd6000] [INFO][com.freerdp.gdi] - Remote
framebuffer format PIXEL_FORMAT_RGB16
[19:36:37:203] [7164:29fd6000] [INFO][com.winpr.clipboard] - initialized
POSIX local file subsystem
[19:36:37:228] [7164:29fd6000]
[INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake
backend for rdpsnd
[19:36:37:228] [7164:29fd6000] [ERROR][com.winpr.synch.timer] -
InitializeWaitableTimer: Line 248 of code, 1st apperance
so we are here:
240 #ifdef HAVE_SYS_TIMERFD_H
241 timer->fd = timerfd_create(CLOCK_MONOTONIC,
TFD_NONBLOCK);
242
243 if (timer->fd <= 0)
244 return -1;
245
246 #elif defined(__APPLE__)
247 #else
248 WLog_ERR(TAG, "%s: Line 248 of code, 1st
apperance", __FUNCTION__);
249 result = -1;
250 #endif
Note that there are two such messages, and both are identical.
It would be useful to know which one is being triggered.
It's possible we need to either:
1) Enable the "__APPLE__" code paths in that file on NetBSD too.
2) Borrow the epoll emulation code.
Based on error above and snippet of the code and the fact that
different OSs were
before whitelisted in libwinpr/synch/synch.h which is not the case now:
28
29 #include
30
79 #ifdef HAVE_SYS_TIMERFD_H
80 #include
81 #include
82 #include
83 #include
84 #endif
101 #ifdef WITH_POSIX_TIMER
102 timer_t tid;
103 struct itimerspec timeout;
104 #endif
Isn't it then just a problem during compile not picking up proper
libraries/paths
towards NetBSD implementation of POSIX timer?
But then I can see this in libwinpr/synch/CMakeLists.txt:
if(FREEBSD)
winpr_include_directory_add(${EPOLLSHIM_INCLUDE_DIR})
winpr_library_add_private(${EPOLLSHIM_LIBS})
endif()
I can't test this because I don't have a Windows machine to connect
to...
Trying to find under /usr/pkgsrc/net/freerdp2/work some details from
compile time what was picked - if it will be there of course.
Re: firefox52 core dump on RPI2 NetBSD9.1
On 19.11.2020 03:08, Mayuresh wrote: On Wed, Nov 18, 2020 at 08:32:42AM +0530, Mayuresh wrote: Is nobody else facing this problem? The image and packages both are downloaded from above locations, I have built nothing at my end. Have filed port-arm/55812. Request attention please. Stuck without a browser totally. I have eg. armv7$ firefox52 Assertion failure: !joinable(), at /scratch/work/www/firefox52/work/firefox-52.9.0esr/js/src/threading/Thread.h:122 Memory fault (core dumped) armv7$ Core was generated by `firefox52'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7af78c70 in _lwp_kill () from /usr/lib/libc.so.12 [Current thread is 1 (process 1)] (gdb) where #0 0x7af78c70 in _lwp_kill () from /usr/lib/libc.so.12 #1 0x7723ea08 in ?? () from /usr/pkg/lib/firefox52/libxul.so #2 0x7af789f8 in __vfork14 () from /usr/lib/libc.so.12 Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) Based on discussion on other list you were given tips what to do, did you test them? Besides based on your description you picked up totally wrong platform for your job. Raspberry Pi 2 is having maxium of 1GB RAM if it is B model. Firefox needs at least 512MB https://www.mozilla.org/en-US/firefox/52.0esr/system-requirements/ But that is minimum. Modern overbloated web browsers like Firefox and Chrome needs A LOT of memory just for regular tasks. Eg. Firefox 82 needs at least 2GB of RAM in case of 64bit platform, currently it eats about 1,6GB on my PC with about 12 tabs open doing nothing, except of writing this email. Even if you will get it running then you can't rely on it for some huge tasks with JavaScript which adds even more misery in to this mix. If this is Severity - critical for you and you are stuck without browser completely then you did something seriously wrong in planning phase of whatever project you're in, because it means you do not have backup platform or better to say more suited platform for the task at hands ;-) Sad status of web browsers on arm architecture is one of the results of "funny" cycle 90's IE only -> 2000's different options available -> Now's Linux/Chrome or die (MS Edge anynone? :-)); with Firefox still catching up somewhat
Re: firefox52 core dump on RPI2 NetBSD9.1
On 19.11.2020 09:24, Mayuresh wrote: On Thu, Nov 19, 2020 at 08:27:22AM +0100, Bodie wrote: Based on discussion on other list you were given tips what to do, did you test them? If there are any tips that I missed, please do point out. [ If you are referring to a post that says my toolchain might be invalid, I already pointed out that I did not build anything at my end. I have downloaded the binary packages and binary OS image. ] Yes that is the post https://mail-index.netbsd.org/port-arm/2020/11/17/msg007061.html It is pointing out that there may something happen during build of binary package on NetBSD end and how to check this is to compile it on your end on -stable or even -current. If compile on your end from pkgsrc2020Q3 create same result then it may be worth of PR Besides based on your description you picked up totally wrong platform for your job. I am using this device for several years and have used firefox on it. It used to work fine till NetBSD 8 (or 7 I don't recollect). I can make do with 1 tab and when not needed, can switch off js. Of late I was using Raspbian on the device and wanted to switch back to the latest NetBSD version. And did you notice during those years how browsers requirements raised regarding HW and got thin regarding range of supported OSs? If this is Severity - critical for you and you are stuck without browser completely then you did something seriously wrong in planning phase of whatever project you're in, because it means you do not have backup platform or better to say more suited platform for the task at hands ;-) Not really, both the points. As I said I have been using NetBSD on this device and I have a fallback option to Raspbian. So you have fallback, even more reasons to not report as critical. One package issues is very different from eg. port not booting at all Basically, I myself had reported the .strtab issues long back in 8.99 - I think that was in the context of squid probably. I got to know in this thread that those have been fixed. So it's a bit surprising that they are recurring. And they are occurring with a binary download of both the OS image and packages. Hence I thought they should be wider interest. Easy answer. Lack of resources. It is easy to find something wrong, it is harder to get hands dirty in code. For me eg. issues with freerdp2 on amd64. I am fully aware there may not be quick fix and requires a lot of compile, reading and such from my side, but it is part of the fun. I'd request inputs on the .strtab issue and why it occurs on all binary download with nothing built at my end. Whether NetBSD suits my device and whether the device suits firefox - let me experiment. May be it proves to be unsuitable but let's take one issue at a time. But do you know for sure that those binary downloads are correct? That something from pkgsrc is able to compile and create binary package which you can start does not mean it is running as it should ;-) Eg. my Orange Pi One with 9.1 -stable Memory: 211M Act, 134M Inact, 9784K Wired, 13M Exec, 320M File, 68M Free with just tmux and 2 sessions (File part is occupied after some pkgin runs) I know for 100% that this platform is not suitable for any modern FF or Webkit/Webengine variant even if there will be more RAM. It is learning or small server/IoT platform playground. For web with eg. links and such. I know will be nice to have modern platform with available HW where one can at least get close in responsiveness of GUI of 80's/90's non-i386 computers, but that approach will turn industry upside down :-)
Re: firefox52 core dump on RPI2 NetBSD9.1
On 19.11.2020 10:54, Mayuresh wrote: On Thu, Nov 19, 2020 at 10:14:29AM +0100, Bodie wrote: And did you notice during those years how browsers requirements raised regarding HW and got thin regarding range of supported OSs? pkgsrc maintains older versions say firefox52 which helps. They can't maintain something what is over 2 years old when vendor support it only for over 1 year https://support.mozilla.org/en-US/kb/firefox-esr-release-cycle It just happens to be build mostly and runs somewhat so that there is some "modern" GUI web browser available on the platform raspbian has a custom build of FF which is lightweight - what exactly they do, I do not know, but it works pretty well. https://archive.raspbian.org/raspbian/pool/main/f/firefox-esr/ they have all those versions because Firefox is providing browser for Windows, Apple, Linux and nothing else. Code and performance between BSD are very different plus reading this https://wiki.netbsd.org/ports/evbarm/raspberry_pi/ it still seems that there is some work ahead for full support (even if it is in "cornerstone" areas) So you have fallback, even more reasons to not report as critical. One package issues is very different from eg. port not booting at all Fair enough. Whoever has the access, please feel free to revise. My perspective is this: It's happening on a formally released image and is something that was supposed to have been fixed. Is potentially a wrong image lurking around (note wrong armv7.img i.e. _potentially_, and I hope it's untrue, hence I adjudged it so.) I do not know internals, but building those packages takes a lot of time on these platforms or somewhere in the chain wrong toolchain version was used so everything is possible. Or because earm, earmv6hf and evbarm does not have any Firefox at all then maybe someone just forgot to remove it from infrastructure for building on earmv7hf ;-) Just 1 correction to my mail, though it doesn't matter to the problem description. I reported the device as RPI2, but it's RPI3B (I actually have 1 each, and am migrating both from raspbian to 9.1 simultaneously, 3B as a desktop and 2 for some other use. Hence I might have erred when reporting.) Nice model, however still only 1GB of RAM. Will be interesting for the check of the problem to install current on it and trying to compile Firefox. Plus you will have Bluetooth supported there :-)
Re: firefox52 core dump on RPI2 NetBSD9.1
On 19.11.2020 16:12, Mayuresh wrote: On Thu, Nov 19, 2020 at 03:32:20PM +0100, Bodie wrote: I do not know internals, but building those packages takes a lot of time on these platforms or somewhere in the chain wrong toolchain version was used so everything is possible. Or because earm, earmv6hf and evbarm does not have any Firefox at all then maybe someone just forgot to remove it from infrastructure for building on earmv7hf ;-) In my last stint of usage of NetBSD on Pi I used to use pkgsrc for everything notwithstanding time it used to take. Having done it for long I feel fatigued about restarting it and hence was looking forward to use binary. Yes, compiling should be only for developers or when you are looking for a problem. But again, not enough resources here I suppose (even those Joyent mirrors are broken - tried 2 days ago) Anyway, will probably try building on qemu. It will be even slower, but I can at least leave it running on a server. actually I am gonna try it on my Orange Pi One, but that will take forever for sure. At least it will be good to know how much time it takes to build such old binary blob :-) Unless that board will not end in flames of course I still wish to know whether strtab errors are necessarily from the pkg layer or is something in the base wrong - and in turn armv7.img is faulty. I am just noticing the lightening symbol on the screen also. At 8/8.99 stage there was a fix to this by copying some firmware files and it had worked for me. This was supposed to be fixed in 9 but is still lurking there - another reason I wonder whether something went wrong with the image. Plus you will have Bluetooth supported there :-) Yes, read about that. But I do not have a use case. On board Wifi will be greater a motivation to switch to current. I read it has reached a stage where it is established that it 'can work'. Hopefully by 10 it will be in.
Re: firefox52 core dump on RPI2 NetBSD9.1
On 19.11.2020 17:25, tlaro...@polynum.com wrote:
On Thu, Nov 19, 2020 at 09:03:12PM +0530, Mayuresh wrote:
On Thu, Nov 19, 2020 at 04:22:11PM +0100, Bodie wrote:
> > I still wish to know whether strtab errors are necessarily from the
> > pkg layer or is something in the base wrong - and in turn armv7.img is
> > faulty.
And any comment / confirmation on this from anyone?
One of the strong point of NetBSD is that the system (including X11)
can be crosscompiled.
You should probably start by cross-compiling the system, including X11,
for your target.
I have done so for an Olimex board, without knowing anything about Arm
at the beginning, and with the documentation/howtos available.
Developers have made this quite easy.
It will allow you to know if the problem is with the packages (that,
unfortunately, for the huge majority, can not be cross-compiled) or
with
the system.
From your original message, invoking problem with glib if I remember
correctly, I verified in the /etc/mtree/ spec files: glib is not
provided by the base system. So the best bet is that the problem is
not
with the system but with the package (or one of its dependencies),
since it takes a huge amount of time to compile, and it has not been
updated after the correction of binutils, because this version was
already considered obsolete. Hence the binaries
are left other versions pre-dating the fixes.
Note: I don't say that the packages compiled with the fixed toolchain
will not exhibit the problem. I just say that since there is already
this problem, that can cause linking problems, using these already
problematic binaries is a dead end.
HTH,
Yeah it does not seem even to compile, but true is that this is quite
weak platform to compile on this (Orange Pi One)
--- cairo-xlib-screen.lo ---
In file included from
/usr/pkgsrc/graphics/cairo/work/.x11-buildlink/include/freetype2/freetype/freetype.h:24:0,
from
/usr/pkgsrc/graphics/cairo/work/.x11-buildlink/include/fontconfig/fcfreetype.h:28,
from cairo-fontconfig-private.h:49,
from cairo-xlib-screen.c:66:
/usr/pkgsrc/graphics/cairo/work/.x11-buildlink/include/freetype2/freetype/config/ftconfig.h:44:10:
fatal error: freetype/config/integer-types.h: No such file
or directory
#include
^
compilation terminated.
--- cairo-xlib-surface.lo ---
--- cairo-xlib-screen.lo ---
*** [cairo-xlib-screen.lo] Error code 1
make[3]: stopped in /usr/pkgsrc/graphics/cairo/work/cairo-1.16.0/src
--- cairo-xlib-surface.lo ---
CC cairo-xlib-surface.lo
cairo-xlib-surface.c: In function '_cairo_xlib_surface_create_internal':
cairo-xlib-surface.c:1753:7: warning: missed loop optimization, the loop
counter may overflow [-Wunsafe-loop-optimizations]
if (&d->visuals[k] == visual) {
^
cairo-xlib-surface.c: In function 'cairo_xlib_surface_create':
cairo-xlib-surface.c:1876:6: warning: missed loop optimization, the loop
counter may overflow [-Wunsafe-loop-optimizations]
if (visual == &depth->visuals[v])
^
1 error
make[3]: stopped in /usr/pkgsrc/graphics/cairo/work/cairo-1.16.0/src
*** [all] Error code 2
make[2]: stopped in /usr/pkgsrc/graphics/cairo/work/cairo-1.16.0/src
1 error
make[2]: stopped in /usr/pkgsrc/graphics/cairo/work/cairo-1.16.0/src
*** [all-recursive] Error code 1
make[1]: stopped in /usr/pkgsrc/graphics/cairo/work/cairo-1.16.0
1 error
make[1]: stopped in /usr/pkgsrc/graphics/cairo/work/cairo-1.16.0
*** [all] Error code 2
make: stopped in /usr/pkgsrc/graphics/cairo/work/cairo-1.16.0
1 error
make: stopped in /usr/pkgsrc/graphics/cairo/work/cairo-1.16.0
*** Error code 2
Stop.
make[2]: stopped in /usr/pkgsrc/graphics/cairo
*** Error code 1
Stop.
make[1]: stopped in /usr/pkgsrc/graphics/cairo
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/www/firefox52
1774.57s real 1413.80s user 557.26s system
$
Re: firefox52 core dump on RPI2 NetBSD9.1
On 19.11.2020 19:31, Mayuresh wrote: On Thu, Nov 19, 2020 at 05:25:33PM +0100, tlaro...@polynum.com wrote: It will allow you to know if the problem is with the packages Let me begin with that hypothesis. I'll try to do binary installation of firefox52 on a qemu instance. Then try to build it by cutting down as many options as feasible. The error in question is coming from dbus, so a hope is it may go away by switching off dbus. If that doesn't happen, can pick and build some packages. No, it will not go away. My errors happened when dbus was not running at all A couple of more questions: 1. Which is the highest firefox version which is rust free? Is it 52 (may be that's why it's retained?) 2. What are the chances of getting rust-bin on armv7? Seems it's there for Linux-aarch64 only (among arm).
Re: Bump [q] gradle on NetBSD 9.1 (amd64) with OpenJDK 11 -- does not work
On 21.11.2020 03:49, ts1000 wrote:
Thank you for the follow up in regards to gradle on openjdk11 with
NetBSD 9.1
0) Running NetBSD 9.1 amd64 within Virtual Box on windows host.
Allocated to it the box 8gb and 4 cores
the underlying disk (that vbox is using is an Intel SSD)
1) following your suggestion I installed openJDK8 from binary packages
(I use pkgin)
and:
gradle status
worked with that older version of the openJDK (I tried both the most
recent gradle 6.7 and older gradle 5.4 .. both work)
2) OpenJDK11 from binary packages the above command does not work
3) OpenJDK11 from my rebuild (using pkgsrc) the above command does not
work either
it basically hangs as I described earlier, the full message dump is:
nbsd1$ gradle -d status
2020-11-21T02:11:20.275+ [DEBUG]
[org.gradle.internal.nativeintegration.services.NativeServices]
Native-platform is not available.
2020-11-21T02:11:20.549+ [INFO]
[org.gradle.internal.nativeintegration.services.NativeServices]
Initialized native services in: /home/v/.gradle/native
2020-11-21T02:11:20.623+ [LIFECYCLE]
[org.gradle.launcher.cli.DebugLoggerWarningAction]
#
WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
WARNING
Debug level logging will leak security sensitive information!
https://docs.gradle.org/6.7/userguide/logging.html#sec:debug_security
#
2020-11-21T02:11:21.000+ [DEBUG]
[org.gradle.internal.nativeintegration.filesystem.services.FileSystemServices]
Native-platform file system integration is not available. Continuing
with fallback.
2020-11-21T02:11:21.108+ [DEBUG]
[org.gradle.internal.nativeintegration.filesystem.services.FileSystemServices]
Using Jdk7Symlink implementation as symlink.
2020-11-21T02:11:22.275+ [DEBUG]
[org.gradle.launcher.daemon.client.DaemonClient] Executing build
04bc315f-ebb4-4e65-b3f9-60b4eb16d648 in daemon client {pid=6432}
2020-11-21T02:11:22.298+ [DEBUG]
[org.gradle.internal.remote.internal.inet.InetAddresses] Adding IP
addresses for network interface lo0
2020-11-21T02:11:22.298+ [DEBUG]
[org.gradle.internal.remote.internal.inet.InetAddresses] Is this a
loopback interface? true
2020-11-21T02:11:22.299+ [DEBUG]
[org.gradle.internal.remote.internal.inet.InetAddresses] Adding
loopback address /127.0.0.1
2020-11-21T02:11:22.299+ [DEBUG]
[org.gradle.internal.remote.internal.inet.InetAddresses] Adding IP
addresses for network interface wm0
2020-11-21T02:11:22.300+ [DEBUG]
[org.gradle.internal.remote.internal.inet.InetAddresses] Is this a
loopback interface? false
2020-11-21T02:11:22.300+ [DEBUG]
[org.gradle.internal.remote.internal.inet.InetAddresses] Adding remote
address /10.0.2.15
2020-11-21T02:11:22.387+ [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire
shared lock on daemon addresses registry.
2020-11-21T02:11:22.408+ [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on
daemon addresses registry.
2020-11-21T02:11:22.424+ [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on
daemon addresses registry.
2020-11-21T02:11:22.434+ [DEBUG]
[org.gradle.launcher.daemon.registry.PersistentDaemonRegistry] Getting
daemon stop events
2020-11-21T02:11:22.435+ [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire
shared lock on daemon addresses registry.
2020-11-21T02:11:22.435+ [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on
daemon addresses registry.
2020-11-21T02:11:22.435+ [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on
daemon addresses registry.
2020-11-21T02:11:22.441+ [INFO]
[org.gradle.launcher.daemon.registry.PersistentDaemonRegistry]
Removing 0 daemon stop events from registry
2020-11-21T02:11:22.448+ [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire
exclusive lock on daemon addresses registry.
2020-11-21T02:11:22.454+ [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on
daemon addresses registry.
2020-11-21T02:11:22.467+ [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on
daemon addresses registry.
2020-11-21T02:11:22.476+ [LIFECYCLE]
[org.gradle.launcher.daemon.client.DefaultDaemonConnector] Starting a
Gradle Daemon (subsequent builds will be faster)
2020-11-21T02:11:22.657+ [DEBUG]
[org.gradle.launcher.daemon.client.DefaultDaemonStarter] Using daemon
args: [/usr/pkg/java/openjdk11/bin/java, --add-opens,
java.base/java.util=ALL-UNNAMED, --add-opens,
java.base/java.lang=ALL-UNNAMED, --add-opens,
java.base/java.lang.invoke=ALL-UNNAMED, --add-opens,
java.prefs/java.util.prefs=ALL-UNNAMED, -XX:MaxMetaspaceSize=256m,
-XX:+HeapDumpOnOutOfMemoryError, -Xms256m, -Xmx512m,
-Dfile.encoding=US-ASCII, -Duser.country=US, -Duser.lan
Re: Bump [q] gradle on NetBSD 9.1 (amd64) with OpenJDK 11 -- does not work
On 21.11.2020 19:59, ts1000 wrote: Greg, Bodie thank you for suggesting to look for ktrace.out, after running: ktrace -i gradle status Indeed the dump was there. Now I know how to use ktrace, at least supreficially. It's not a Linux. It's a BSD. Everything is in the system without need to look for it over Google ;-) https://man.netbsd.org/ktrace.1 I ran kdump on it, got an ASCII and started looking for abnormalities. It seems that gradle is: placing a lock on a file somewhere in ~/.gradle directory then, I presume it writes to it. Then it tries to remove the lock, and then close the file. Somewhere there there seem to be an error. There is also an error about a file missing: 15850 25 java NAMI "/usr/share/nls/nls.alias.db" I am not sure what this file represents or if it is relevant. https://man.netbsd.org/nls.7 and because you play with Java then maybe this one too https://www.oracle.com/database/technologies/faq-nls-lang.html but looking on current system there is just this: $ ls -l /usr/share/nls/nls* -r--r--r-- 1 root wheel 1520 Nov 20 21:01 /usr/share/nls/nls.alias $ files with .db added are often used on systems with huge files like this and turning them in tho this format makes them quicker for lookup and such so maybe if you will just create db version out of it with eg. https://man.netbsd.org/cap_mkdb.1 (not tested by me, but it is for getting idea) And from there on, I see timeouts.. i am presuming that because that file is not properly closed 15850 17 java RET ___lwp_park60 -1 errno 60 Connection timed out again use perfect man pages ;-) https://man.netbsd.org/_lwp_park.2 And then the rest of the code, may be not releasing some lock/semaphore because the file is not accessible. Which is why I am seeing that any gradle commands just hang. That's my interpretation of what's going on. The whole trace file converted to ascii is like 98Mb with over 1mln lines. So cannot post it. But here is a short exerpt that I am using for the study: "org.gradle.cache.internal.DefaultFileLockManager" 15850 2 java RET write 48/0x30 15850 2 java CALL write(0xfe,0x7db1b97fb830,2) 15850 2 java GIO fd 254 wrote 2 bytes "] " 15850 2 java RET write 2 15850 2 java CALL write(0xfe,0x7db1b97fb7d0,0x2c) 15850 2 java GIO fd 254 wrote 44 bytes "Releasing lock on daemon addresses registry." 15850 2 java RET write 44/0x2c 15850 2 java CALL __gettimeofday50(0x7db1b97fda10,0) 15850 2 java RET __gettimeofday50 0 15850 2 java CALL __clock_gettime50(3,0x7db1b97fc550) 15850 2 java RET __clock_gettime50 0 15850 2 java CALL _lwp_unpark_all(0x7db1b9a400f8,1,0x7db1b9667a40) 15850 2 java RET _lwp_unpark_all 0 15850 2 java CALL write(0xfe,0x7db1b97fb6f0,1) 15850 13 java RET ___lwp_park60 0 15850 2 java GIO fd 254 wrote 1 bytes "\n" 15850 2 java RET write 1 15850 2 java CALL __clock_gettime50(3,0x7db1b97fe850) 15850 2 java RET __clock_gettime50 0 15850 2 java CALL __clock_gettime50(3,0x7db1b97fe6c0) 15850 2 java RET __clock_gettime50 0 15850 12 java CALL __clock_gettime50(3,0x7db1989dcb60) 15850 2 java CALL fcntl(0x111,F_SETLK,0x7db1b97fe5b0) 15850 12 java RET __clock_gettime50 0 15850 2 java RET fcntl 0 15850 2 java CALL __fstat50(0x111,0x7db1b97fe8e0) 15850 2 java RET __fstat50 0 15850 2 java CALL lseek(0x111,0,0,1) 15850 2 java RET lseek 17/0x11 15850 2 java CALL ftruncate(0x111,0,0x11) 15850 2 java RET ftruncate 0 15850 12 java CALL __clock_gettime50(3,0x7db1989dcb60) 15850 2 java CALL lseek(0x111,0,0x11,0) 15850 13 java CALL __gettimeofday50(0x7db1981ffc10,0) 15850 2 java RET lseek 17/0x11 15850 12 java RET __clock_gettime50 0 15850 13 java RET __gettimeofday50 0 15850 2 java CALL fcntl(0x111,F_SETLK,0x7db1b97fe8b0) 15850 2 java RET fcntl 0 15850 13 java CALL __clock_gettime50(3,0x7db1981ff8d0) 15850 13 java RET __clock_gettime50 0 15850 2 java CALL fcntl(0x111,F_SETLK,0x7db1b97fe7c0) 15850 13 java CALL __clock_gettime50(3,0x7db1981ff9a0) 15850 2 java RET fcntl 0 15850 13 java RET __clock_gettime50 0 15850 2 java CALL close(0x111) 15850 2 java RET close 0 15850 13 java CALL __clock_gettime50(3,0x7db1981ff9c0) 15850 13 java RET __clock_gettime50 0 15850 2 java CALL __clock_gettime50(3,0x7db1b97feca0) 15850 13 java CALL mmap(0x7db19333,0x4,PROT_READ|PROT_WRITE,0x1012,0x,0,0) 15850
Re: Bump [q] gradle on NetBSD 9.1 (amd64) with OpenJDK 11 -- does not work
On 21.11.2020 19:59, ts1000 wrote: Greg, Bodie thank you for suggesting to look for ktrace.out, after running: ktrace -i gradle status Indeed the dump was there. Now I know how to use ktrace, at least supreficially. I ran kdump on it, got an ASCII and started looking for abnormalities. It seems that gradle is: placing a lock on a file somewhere in ~/.gradle directory then, I presume it writes to it. Then it tries to remove the lock, and then close the file. Somewhere there there seem to be an error. There is also an error about a file missing: 15850 25 java NAMI "/usr/share/nls/nls.alias.db" I am not sure what this file represents or if it is relevant. And from there on, I see timeouts.. i am presuming that because that file is not properly closed 15850 17 java RET ___lwp_park60 -1 errno 60 Connection timed out And then the rest of the code, may be not releasing some lock/semaphore because the file is not accessible. Which is why I am seeing that any gradle commands just hang. That's my interpretation of what's going on. The whole trace file converted to ascii is like 98Mb with over 1mln lines. So cannot post it. But here is a short exerpt that I am using for the study: "org.gradle.cache.internal.DefaultFileLockManager" 15850 2 java RET write 48/0x30 15850 2 java CALL write(0xfe,0x7db1b97fb830,2) 15850 2 java GIO fd 254 wrote 2 bytes "] " 15850 2 java RET write 2 15850 2 java CALL write(0xfe,0x7db1b97fb7d0,0x2c) 15850 2 java GIO fd 254 wrote 44 bytes "Releasing lock on daemon addresses registry." 15850 2 java RET write 44/0x2c 15850 2 java CALL __gettimeofday50(0x7db1b97fda10,0) 15850 2 java RET __gettimeofday50 0 15850 2 java CALL __clock_gettime50(3,0x7db1b97fc550) 15850 2 java RET __clock_gettime50 0 15850 2 java CALL _lwp_unpark_all(0x7db1b9a400f8,1,0x7db1b9667a40) 15850 2 java RET _lwp_unpark_all 0 15850 2 java CALL write(0xfe,0x7db1b97fb6f0,1) 15850 13 java RET ___lwp_park60 0 15850 2 java GIO fd 254 wrote 1 bytes "\n" 15850 2 java RET write 1 15850 2 java CALL __clock_gettime50(3,0x7db1b97fe850) 15850 2 java RET __clock_gettime50 0 15850 2 java CALL __clock_gettime50(3,0x7db1b97fe6c0) 15850 2 java RET __clock_gettime50 0 15850 12 java CALL __clock_gettime50(3,0x7db1989dcb60) 15850 2 java CALL fcntl(0x111,F_SETLK,0x7db1b97fe5b0) 15850 12 java RET __clock_gettime50 0 15850 2 java RET fcntl 0 15850 2 java CALL __fstat50(0x111,0x7db1b97fe8e0) 15850 2 java RET __fstat50 0 15850 2 java CALL lseek(0x111,0,0,1) 15850 2 java RET lseek 17/0x11 15850 2 java CALL ftruncate(0x111,0,0x11) 15850 2 java RET ftruncate 0 15850 12 java CALL __clock_gettime50(3,0x7db1989dcb60) 15850 2 java CALL lseek(0x111,0,0x11,0) 15850 13 java CALL __gettimeofday50(0x7db1981ffc10,0) 15850 2 java RET lseek 17/0x11 15850 12 java RET __clock_gettime50 0 15850 13 java RET __gettimeofday50 0 15850 2 java CALL fcntl(0x111,F_SETLK,0x7db1b97fe8b0) 15850 2 java RET fcntl 0 15850 13 java CALL __clock_gettime50(3,0x7db1981ff8d0) 15850 13 java RET __clock_gettime50 0 15850 2 java CALL fcntl(0x111,F_SETLK,0x7db1b97fe7c0) 15850 13 java CALL __clock_gettime50(3,0x7db1981ff9a0) 15850 2 java RET fcntl 0 15850 13 java RET __clock_gettime50 0 15850 2 java CALL close(0x111) 15850 2 java RET close 0 15850 13 java CALL __clock_gettime50(3,0x7db1981ff9c0) 15850 13 java RET __clock_gettime50 0 15850 2 java CALL __clock_gettime50(3,0x7db1b97feca0) 15850 13 java CALL mmap(0x7db19333,0x4,PROT_READ|PROT_WRITE,0x1012,0x,0,0) 15850 13 java RET mmap 138201632276480/0x7db19333 15850 2 java RET __clock_gettime50 0 15850 12 java CALL __clock_gettime50(3,0x7db1989dbca0) 15850 2 java CALL write(0xfe,0x7db1b97fbd70,0x1c) 15850 12 java RET __clock_gettime50 0 15850 2 java GIO fd 254 wrote 28 bytes "2020-11-21T17:30:40.618+" 15850 2 java RET write 28/0x1c 15850 2 java CALL write(0xfe,0x7db1b97fbd70,2) 15850 2 java GIO fd 254 wrote 2 bytes " [" 15850 2 java RET write 2 15850 2 java CALL write(0xfe,0x7db1b97fbd70,5) 15850 2 java GIO fd 254 wrote 5 bytes "DEBUG" 15850 2 java RET write 5 15850 2 java CALL write(0xfe,0x7db1b97fbd70,3) 15850
Re: Bump - Non-functional xfreerdp2 on 8.1 STABLE - missing POSIX timer_create?
On 17.11.2020 13:53, Uwe Klaus wrote:
On Mon, 16 Nov 2020, Bodie wrote:
original questions is now nearly one year old
https://mail-index.netbsd.org/pkgsrc-users/2019/12/10/msg029983.html
There was no response and I can confirm that problem still exists on
9.1 stable amd64 and evbarm. Are developers
at least aware that there is such problem and freerdp2 is not working
with newer Windows hosts over RDP?
here is my quick and possibly dirty patch
diff /root/Patches/synch_timer.c
/tmp/pkgsrc/net/freerdp2/work.nb9-amd64/freerdp-2.1.2/winpr/libwinpr/synch/timer.c
246,253d245
< #elif defined(__NetBSD__)
< timer->fd = kqueue();
< if (timer->fd <= 0)
< {
< free(timer);
< return -1;
< }
<
Hi,
it works with this patch against servers where it was before throwing
error from this email chain.
Tested here:
$ sysctl kern.version
kern.version = NetBSD 9.99.75 (GENERIC) #0: Fri Nov 20 20:01:16 UTC 2020
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
$
with pkgsrc from 21.11.2020
Best regards,
Uwe Klaus
--
Re: Tunneling in NetBSD
On 22.11.2020 15:41, Rhialto wrote: On Mon 16 Nov 2020 at 07:07:15 -0700, Andy Ruhl wrote: Just a general question to this thread: How do clients use OpenVPN? Do you have to install it, and is it widely available? My basic research suggests that most clients will have to install it. And is there a way to make it so that only some programs use the VPN? Say, a single process, or a single user. Or perhaps a single instance of qemu, if that's more convenient to arrange. There are many, like rdomains in OpenBSD which is basically PolicyBasedRouting in Linux over ip(8) command or similar can be achieved with authpf in pf firewall, but don't know which of those is available in NetBSD. For VPN there is for sure way better (only in current as of now): https://man.netbsd.org/wg.4 -Olaf.
Re: Firefox alternatives with JS : luakit?
On 22.11.2020 18:11, Mayuresh wrote: On Sun, Nov 22, 2020 at 03:46:37PM +0100, Riccardo Mottola wrote: Let me know if you want to play, help, try to compile it yourself or need a binary. Or maybe it could even go in pkgsrc I just tried *today* to compile on NetBSD/9.1 on my ThinkPad T30 (Pentium4M) and it comes up fine... wip/arcticfox would be nice to start giving it a try. One of my requirements is to edit MSOffice documents on office.com. Would it work with that? This one is way bigger problem https://docs.microsoft.com/en-us/microsoftteams/unsupported-browsers when even Microsoft went for Chrome/Chromium as core for Edge. From IE only 90's, we are getting to Chrome/Chromium only 2000's :-) But this is promising https://www.webrtcinwebkit.org/ On those "strange" browsers will be your online Outlook that old OWA interface, but still usable of course as an email client. Here you have that sad reality https://support.microsoft.com/en-us/office/which-browsers-work-with-office-for-the-web-ad1303e0-a318-47aa-b409-d3a5eb44e452
Re: Bump [q] gradle on NetBSD 9.1 (amd64) with OpenJDK 11 -- does not work
On 22.11.2020 06:56, ts1000 wrote: Hello, unfortunately I am not yet able to figure out what's wrong. I think there is something wrong with OpenJDK11 port for netbsd or some OS feature that it relies on, does not work as JDK 11 expects. I do not think there is a problem with Gradle, at all. I have tried Gradle 6.7 and the old 5.4 and they both work with OpenJDK8 on Netbsd 9.1 However, my source code needs at least OpenJDK11, so cannot use 8. I also tried running under root, just to see if there was something about permissions.. but no luck I ran gradle with --no-daemon, no luck either. I have rebuilt OpenJDK11 from pkgsrc, twice -- no luck I have installed OpenJDK11 by pkgin from binary repo -- no luck. I have changed my locale from C to UTF8 -- no luck. I have been looking at the output of kdump/ktrace all day today. Unfortunately I cannot spot anything that I could investigate further. There are over 1mln lines there just from ' gradle status'. Most are getttime calls, bunch of memory maps. Some timeouts, but I see them not just at the end of ktrace when it hangs, but also early on. So I am at loss at the moment. DTrace for the victory I would say ;-) Start with this one http://dlc.openindiana.org/docs/osol/20090715/DYNMCTRCGGD/html/chp-intro-5.html That example for rw.d works just fine at least on NetBSD current (but I think on 9.1 stable too) Those system calls to lwp are covered by available providers: $ sudo dtrace -l -P syscall | grep lwp 812syscall _lwp_create entry 813syscall _lwp_create return 814syscall _lwp_exit entry 815syscall _lwp_exit return 816syscall _lwp_self entry 817syscall _lwp_self return 818syscall _lwp_wait entry 819syscall _lwp_wait return 820syscall_lwp_suspend entry 821syscall_lwp_suspend return 822syscall _lwp_continue entry 823syscall _lwp_continue return 824syscall _lwp_wakeup entry 825syscall _lwp_wakeup return 826syscall _lwp_getprivate entry 827syscall _lwp_getprivate return 828syscall _lwp_setprivate entry 829syscall _lwp_setprivate return 830syscall _lwp_kill entry 831syscall _lwp_kill return 832syscall _lwp_detach entry 833syscall _lwp_detach return 834syscall compat_50__lwp_park entry 835syscall compat_50__lwp_park return 836syscall _lwp_unpark entry 837syscall _lwp_unpark return 838syscall _lwp_unpark_all entry 839syscall _lwp_unpark_all return 840syscall_lwp_setname entry 841syscall_lwp_setname return 842syscall_lwp_getname entry 843syscall_lwp_getname return 844syscall_lwp_ctl entry 845syscall_lwp_ctl return 1062syscall compat_60__lwp_park entry 1063syscall compat_60__lwp_park return 1150syscall _lwp_park entry 1151syscall _lwp_park return $ With predicate like /errno = 60/ you can get for start at least how many times it happens during your run without modifying anything and soon you will learn way more how to get details which will be very usable in your work anyway. Sure you can somewhat get some of the results with ktrace/ktruss, but as you saw digging out of those million lines is not exactly fun On 2020-11-22 03:02, Kamil Rytarowski wrote: I just ran into it independently on NetBSD/amd64 current 9.99.x. On 20.11.2020 02:59, ts1000 wrote: Hello, wanted to bump up my question to see if anybody could help. Also, if
Re: Bump [q] gradle on NetBSD 9.1 (amd64) with OpenJDK 11 -- does not work
On 22.11.2020 23:50, ts1000 wrote: Thank you. I noticed that when building openJDK11 there was an option to enable 'dtrace' support. I thought that dtrace is not ktrace, so I did not enable it. Should I first rebuild OpenJDK11 with dtrace support ? Not needed for sure. Dtrace is just there in system $ sudo dtrace -l | wc -l 52623 $ and not so bad compared to OpenIndiana $ sudo dtrace -l | wc -l │[19:37:58:322] [4591:0002] [INFO][com.freerdp.client.x11] - Closed from X1 83420 $ that stuff in OpenJDK can be additional support for probes and developers or specific Java probes as mentioned here on FBSD https://forums.freebsd.org/threads/dtrace-openjdk12.71470/ and here is related info too https://github.com/AdoptOpenJDK/openjdk-build/issues/1242 BTW it is a tool you have available on NetBSD, FreeBSDm OpenIndiana, Illumos, SmartOS, Apple (Xcode/Instruments), Solaris 10,11 and probably soon even on Windows https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/dtrace I found even some good material working even on Gradle, but not sure how much of that is applicable here, still Java comes from Sun/Oracle as well as Dtrace so not everything may be there https://www.oracle.com/technetwork/systems/hands-on-labs/hol-uncover-jdk8-secrets-dtrace-2798366.html On 2020-11-22 19:47, Bodie wrote: On 22.11.2020 06:56, ts1000 wrote: Hello, unfortunately I am not yet able to figure out what's wrong. I think there is something wrong with OpenJDK11 port for netbsd or some OS feature that it relies on, does not work as JDK 11 expects. I do not think there is a problem with Gradle, at all. I have tried Gradle 6.7 and the old 5.4 and they both work with OpenJDK8 on Netbsd 9.1 However, my source code needs at least OpenJDK11, so cannot use 8. I also tried running under root, just to see if there was something about permissions.. but no luck I ran gradle with --no-daemon, no luck either. I have rebuilt OpenJDK11 from pkgsrc, twice -- no luck I have installed OpenJDK11 by pkgin from binary repo -- no luck. I have changed my locale from C to UTF8 -- no luck. I have been looking at the output of kdump/ktrace all day today. Unfortunately I cannot spot anything that I could investigate further. There are over 1mln lines there just from ' gradle status'. Most are getttime calls, bunch of memory maps. Some timeouts, but I see them not just at the end of ktrace when it hangs, but also early on. So I am at loss at the moment. DTrace for the victory I would say ;-) Start with this one http://dlc.openindiana.org/docs/osol/20090715/DYNMCTRCGGD/html/chp-intro-5.html That example for rw.d works just fine at least on NetBSD current (but I think on 9.1 stable too) Those system calls to lwp are covered by available providers: $ sudo dtrace -l -P syscall | grep lwp 812syscall _lwp_create entry 813syscall _lwp_create return 814syscall _lwp_exit entry 815syscall _lwp_exit return 816syscall _lwp_self entry 817syscall _lwp_self return 818syscall _lwp_wait entry 819syscall _lwp_wait return 820syscall_lwp_suspend entry 821syscall_lwp_suspend return 822syscall _lwp_continue entry 823syscall _lwp_continue return 824syscall _lwp_wakeup entry 825syscall _lwp_wakeup return 826syscall _lwp_getprivate entry 827syscall _lwp_getprivate return 828syscall _lwp_setprivate entry 829syscall _lwp_setprivate return 830syscall _lwp_kill entry 831syscall _lwp_kill return 832syscall _lwp_detach entry 833syscall _lwp_detach return 834syscall compat_50__lwp_park entry 835syscall compat_50__lwp_park return 836syscall _lwp_unpark entry 837syscall _lwp_unpark return 838syscall _lwp_unpark_all entry 839syscall
Re: Firefox alternatives with JS : luakit?
On 23.11.2020 11:09, Sad Clouds wrote: On Mon, 23 Nov 2020 06:24:17 +0100 (CET) "Thomas Mueller" wrote: from Sad Clouds: > On Sun, 22 Nov 2020 16:29:27 +0530 > Mayuresh wrote: > > In the interim, would appreciate any feedback on luakit or other > > alternatives (with JS support). > x86 running Linux and Opera web browser. I gave up on Firefox years > ago. Unfortunately Opera don't provide binaries for NetBSD, but you > could try Linux emulation. I use Otter browser, which is in pkgsrc, FreeBSD ports, and haikuports. One good feature is being able to fake the user-agent for sites like Chase online banking that refuse to allow access if the user-agent is not to their software's liking Tom I had stability issues with Otter browser, random crashes, etc. Same thing happened with Firefox on sparc64. I just stick to x86 for desktop applications, where sparc64 and arm are more for tinkering and server applications. The web technology used to be small and lean many years ago, but now there is too much complexity and bloat. Because of this, it is becoming a monoculture of a handful of browser engines - Blink and Gecko. Don't even try to innovate, you'll be buried by the cost and complexity. Which is why everybody is switching to Blink, whether they like it or not. Those new Apple M1 CPUs are very interesting. As a HW. For sure they will improve situation on ARM field, but for Apple mostly :-) And in browsers it will be like you describe and as I said, we are returning to 90's, this time not with IE, but with Chrome
Re: GeForce - double crash with nouveau (boot and X11)
On 24.11.2020 02:14, Riccardo Mottola wrote: Hi all,, I got a used laptop and sadly it has a nvidia 7300 card Sadly because I know they are troublesome - they work(ed) well on linux and freebsd until they stopped providing a current binary legacy driver, then you can trash it, apparently. I read that nouveau supports it, so let's try! FreeBSD has no nouveau, so, let's try NetBSD! CD-ROM in, boot crashes. I need to boot -c and disable nouveau. I install NetBSD and of course the next reboot, it will hang again, I disable nouveau (I have done screeshot with the backtrace) With nouveau in the kernel disabled, I do try X11. Does it make sense at all to ty the nouveau driver if it is disabled in the kernel? I don't know if it is needed for console only or for both console and X11. I get garbage on the screen and if I change console, I get a reboot! yay! And a rebot an empty Xorg file Fine, I try the trick of telnet into the box, start X "remote"... and run it. What I see at the end is: [ 464.423] (==) Not automatically adding GPU devices [ 464.423] (==) Max clients allowed: 256, resource mask: 0x1f [ 464.423] (**) FontPath set to: /usr/X11R7/lib/X11/fonts/misc/, /usr/X11R7/lib/X11/fonts/TTF/, /usr/X11R7/lib/X11/fonts/Type1/, /usr/X11R7/lib/X11/fonts/75dpi/, /usr/X11R7/lib/X11/fonts/100dpi/, /usr/X11R7/lib/X11/fonts/misc/, /usr/X11R7/lib/X11/fonts/TTF/, /usr/X11R7/lib/X11/fonts/Type1/, /usr/X11R7/lib/X11/fonts/75dpi/, /usr/X11R7/lib/X11/fonts/100dpi/ [ 464.423] (**) ModulePath set to "/usr/X11R7/lib/modules" [ 464.423] Number of created screens does not match number of detected devices. Configuration failed. [ 464.423] (EE) Server terminated with error (2). Closing log file. I notice that X went through all the drivers and that the driver list is doubled even (every driver appears twice). So I think nouveau has an issue. Now the next bet would be to try the old "nv" driver. I cobble together a quick xorg file, but I get garbage and it says that no GPUs are found and get a crash. I restart, disable loading of all modules and this time i get "garbage" on the screen, but if I move the mouse I see a square garbage moving! so something "is alive", no errors in Xorg.log except: [ 252.202] (EE) DMA drain timeout Any suggestions? I'd like to get nv working but even more nouveau of course (here I think some kernel and drm debugging is required) What version of NetBSD did you try? Did you check with current snapshot? https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/images/ I am almost tempted to try out Linux to see if nouveau works on that card (it should work, per spec) and/or if nv works there as a "reference" against BSD, but it is of course extra effort and I need a second hard disk to poke with that maybe, while hopefully we debug NetBSD Riccardo
Re: How to see disk I/O per process in NetBSD?
On 27.11.2020 13:45, Bartosz Maciejewski wrote: Hello, I will repost what I've wrote on reddits r/netbsd as there are no replys there, maybe here I will have more luck :) Is there any way to see which process is doing read and writes on file system? I know iostat, but it showin summary. For example, below xbd0 which is mount point of / have some huge writes of 12 MB/s. I can't tackle it down to single process. |tty xbd0 xbd1 xbd2 xbd3 xbd4 xbd5 CPU tin tout KB/t t/s MB/s KB/t t/s MB/s KB/t t/s MB/s KB/t t/s MB/s KB/t t/s MB/s KB/t t/s MB/s us ni sy in id 0 0 26.58 479 12.42 25.29 5 0.123 17.77 13 0.226 12.45 11 0.136 25.64 12 0.300 13.25 45 0.581 8 0 11 0 81 | I need something similiar to iotop from Linux, or sorting option 'm' from FreeBSD ( top -m io -o total) Check 'man systat' for general overview, 'man fstat' for getting to know what processes are using that file/mount or for display of open files by that process. And for details use dtrace or start with included program once you identify with fstat name of the program then eg. like this: sudo opensnoop -n date x UIDPID COMM FD PATH x 1000 1362 date 0 /etc/ld.so.conf x 1000 1362 date 3 /lib/libutil.so.7 x 1000 1362 date 3 /lib/libc.so.12 x 1000 1362 date 3 /etc/localtime x 1000 1362 date 3 /usr/share/zoneinfo/posixrules x ^C x x In general things from here http://dlc.openindiana.org/docs/osol/20090715/DYNMCTRCGGD/html/chp-intro.html works fine Even glances doesn't show proper I/O - everything is 0/0
