Re: ThinkPad: reboots after successful shutdown -p
I had it and filed a bug report. It only happens in UEFI loader and that only on one of my machines, but not the other. With kindest regards, Kostya Berger On Wednesday, 17 March 2021, 19:38:57 GMT+3, Unbound wrote: On 2021-03-17 00:01, Xin Li via freebsd-current wrote: > On 3/16/21 9:45 PM, Warner Losh wrote: >> >> >> On Tue, Mar 16, 2021 at 10:18 PM Xin Li > <mailto:delp...@freebsd.org>> wrote: >> >> On 11/17/19 23:14, Xin Li wrote: >> > Hi, >> > >> > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the >> > system would shut down and seemingly powered off, then it would >> restart >> > after about 5-10 seconds. >> > >> > Is this a known issue? Arguably this is not necessarily a FreeBSD >> > issue, but it seems that the Windows 10 installation doesn't have the >> > problem, so I guess there might be some difference between our and >> > Windows's shutdown sequence. >> >> I've found a workaround for this, for the record, setting >> hw.efi.poweroff=0 would make the laptop to correctly shutdown. >> >> However I don't see anything wrong with sys/dev/efidev/efirt.c's >> implementation of EFI shutdown; it appears to be essentially the same >> as >> implemented in command_poweroff() in stand/efi/loader/main.c, but >> 'poweroff' would work just fine in loader.efi. >> >> Can someone familiar with the code shed me some light here? :-) >> >> It looks like what Linux did was to prefer ACPI S5, unless it's not >> available or the system have HW_REDUCED flag in FADT, so if we do >> something similar it would fix the issue for me, but according to >> bugs.freebsd.org/233998 <http://bugs.freebsd.org/233998> that's not >> the case for at least Conor's system >> (_S5 appears to be in the ACPI dump), so I think it's something else... >> >> >> For me, interrupt storm on shutdown has been the causes of issues like >> this... >> >> Any chance you can eliminate that as a possibility? > > Hmm, that's a good question -- is there a way to tell after the screen > was turned off? > > Before the screen was turned off, there doesn't appear to be interrupt > storm. The system was performing a typical FreeBSD shutdown procedure: > All buffers synced, showed uptime, destroyed GELI devices, spin down the > SATA devices, shutdown the cardreader (rtsx0), detached all USB devices > (hidraw1, hidbus, usbhid1, ubt0, uhub0), screen turned slightly red for > a very brief period (maybe side effect of turning off the backlight), > then goes off. > > I think most of FreeBSD drivers would turn off interrupt from the device > before detaching, but I haven't looked into all of my devices; but from > what I have seen on screen (captured a 60fps video and can share if that > helps), there doesn't appear to be an interrupt storm before that. > > Cheers, FWIW this also happened to me a few weeks ago after a fresh install. I've since wiped the disk and repurposed the hardware. So I can't now reproduce it. But it wasn't a laptop. So it's not isolated to them. Sorry I can't offer anything more. I just wanted to mention this to indicate that it's not a _too_ terribly isolated case. It was Intel CPU/graphics. In case that says anything to anyone. If it matters, I can get/offer more info on the hardware. --Chris ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 13-alpha2 libncurses removal breaks ports build
Builds OK from inside clean install. Which is all I needed this far. Thank you. With kindest regards, Kostya Berger On Sunday, 24 January 2021, 17:53:41 GMT+3, Kostya Berger wrote: OK, building ports against a clean installation of 13.0-ALPHA2 has no problem with ncurses. But devel/glib20 fails for no obvious reason closer to the end of building process... I just wonder: do I need to report this to port maintainers or wait till it settles up somehow? A good deal of ports depend on it. With kindest regards, Kostya Berger On Sunday, 24 January 2021, 01:40:57 GMT+3, Kostya Berger wrote: Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING about how one should handle the removal of libncurses.so.9 from base. Source UPDATING only says:ncurses installation has been modified to only keep the widechar enabled version. Incremental build is broken for that change, so it requires a clean build. If that means to just build all ports anew, then it doesn't work as ports don't seem to incorporate any change related to this one. It would seem default configuration should take into account this, but it doesn't. The ports just use --with-libncurses-prefix=/usr, and there is no ncurses libs found there. This make it skip MOST of the ports I'm using. Working Copy Root Path: /usr/ports URL: https://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 562417 Node Kind: directory Schedule: normal Last Changed Author: 0mp Last Changed Rev: 562417 Last Changed Date: 2021-01-23 23:01:38 +0300 (Sat, 23 Jan 2021) With kindest regards, Kostya Berger ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 13-alpha2 libncurses removal breaks ports build
OK, building ports against a clean installation of 13.0-ALPHA2 has no problem with ncurses. But devel/glib20 fails for no obvious reason closer to the end of building process... I just wonder: do I need to report this to port maintainers or wait till it settles up somehow? A good deal of ports depend on it. With kindest regards, Kostya Berger On Sunday, 24 January 2021, 01:40:57 GMT+3, Kostya Berger wrote: Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING about how one should handle the removal of libncurses.so.9 from base. Source UPDATING only says:ncurses installation has been modified to only keep the widechar enabled version. Incremental build is broken for that change, so it requires a clean build. If that means to just build all ports anew, then it doesn't work as ports don't seem to incorporate any change related to this one. It would seem default configuration should take into account this, but it doesn't. The ports just use --with-libncurses-prefix=/usr, and there is no ncurses libs found there. This make it skip MOST of the ports I'm using. Working Copy Root Path: /usr/ports URL: https://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 562417 Node Kind: directory Schedule: normal Last Changed Author: 0mp Last Changed Rev: 562417 Last Changed Date: 2021-01-23 23:01:38 +0300 (Sat, 23 Jan 2021) With kindest regards, Kostya Berger ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
13-alpha2 libncurses removal breaks ports build
Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING about how one should handle the removal of libncurses.so.9 from base. Source UPDATING only says:ncurses installation has been modified to only keep the widechar enabled version. Incremental build is broken for that change, so it requires a clean build. If that means to just build all ports anew, then it doesn't work as ports don't seem to incorporate any change related to this one. It would seem default configuration should take into account this, but it doesn't. The ports just use --with-libncurses-prefix=/usr, and there is no ncurses libs found there. This make it skip MOST of the ports I'm using. Working Copy Root Path: /usr/ports URL: https://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 562417 Node Kind: directory Schedule: normal Last Changed Author: 0mp Last Changed Rev: 562417 Last Changed Date: 2021-01-23 23:01:38 +0300 (Sat, 23 Jan 2021) With kindest regards, Kostya Berger ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
nvidia-driver-390 fails to find screens
Was there any significant change in the base code, so that Nvidia driver suddenly can't find usable displays upon the update to r363439 ?Error message: NVIDIA(GPU-0): Failed to select a display subsystem. Отправлено из Yahoo Почты для Android ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
В ответ на: Re: ? ????? ??: Re: FYI: forum web site is .. unreadable
Can it be due to some interference/filtering by your router or your ISP? I have never EVER seen such problem in Firefox on ANY system. Did you try from Windows from the same place? Anyway, you can try resetting your Firefox to defaults. Отправлено из Yahoo Почты для Android вт, 23 июн. 2020 в 17:55 Steffen Nurpmeso написал(-а): Gary Jennejohn wrote in <20200623130733.658b4...@ernst.home>: |On Tue, 23 Jun 2020 09:05:06 + (UTC) |Kostya Berger wrote: | |> Looks fine in my Firefox. No such problems. Locally built Firefox. ... |> , 23 __. 2020 __ 10:32 Niclas Zeising se> __(-__): On 2020-06-23 08:48, Gary Jennejohn wrote: |>> On Tue, 23 Jun 2020 01:14:52 +0200 |>> Steffen Nurpmeso wrote: ... |>>> Normally i do not do forums (web interface etc etc), but i was |>>> interested in ZFS encryption support and so i searched, and found |>>> a page[1].__ Now when i open that on a glibc Linux box with |>>> |>>>__ __ #?0|kent:src$ prt-get info firefox-bin ... |>>>__ __ Version:__ __ __ 77.0.1 .. |>>> i.e. Mozilla.com-compiled firefox, then i see a small forum |>>> "frame" on the right side, it is right of the "Foundation" link in |>>> the link bar.__ It is just large enought to place "To be honest," |>>> in a single line, on a, well, pretty wide screen. |>>> |>>>__ __ [1] https://forums.freebsd.org/threads/native-encryption-of-zfs.70\ |>>>284/ |>>> |>>> Ciao, and good night from Germany, |>>> |>> |>> I see exactly the same bad formatting with the standard firefox \ |>> port.__ All the |>> text is pushed to the right. |>> |>> seamonkey works, but it's been removed from ports. |> |> It looks fine on my 1080p display, using Firefox from FreeBSD packages. | |I just installed the latest firefox from the package repository and \ |the forum page |is still mis-formatted. | |This is the only website of the many I use which displays this error. | |My display is 2560x1440 (probably irrelevant). Not really all that \ |important |to me in any case. I have registered myself at the forum, but it is still unusable even thereafter. I looked at the source but i miss two decades of CSS etc. development to truly understand what there is, and since even the stylesheets are generated via monstrous URLs from a PHP script (!!) i cannot tell at all what is going on, to give a hint. But FreeBSD is not a marginal side note, even if i do not have a FreeBSD system with X display right now. Accessing forums.freebsd.org via lynx "looks much better", but it says "JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.". Forums are not for me, it was just for your interest. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
openzfs-kmod build error
CURRENT r362292 sysutils/openzfs-kmod build aborts with error:... /usr/ports/sysutils/openzfs-kmod/work/zfs-c0eb5c35e/module/os/freebsd/zfs/zfs_vfsops.c:128:19: error: incompatible pointer types initializing 'vfs_checkexp_t *' (aka 'int (*)(struct mount *, struct sockaddr *, unsigned long *, struct ucred **, int *, int *)') with an expression of type 'int (vfs_t *, struct sockaddr *, int *, struct ucred **, int *, int **)' (aka 'int (struct mount *, struct sockaddr *, int *, struct ucred **, int *, int **)') [-Werror,-Wincompatible-pointer-types] .vfs_checkexp = zfs_checkexp, ^~~~ /usr/ports/sysutils/openzfs-kmod/work/zfs-c0eb5c35e/module/os/freebsd/zfs/zfs_vfsops.c:1911:56: error: incompatible pointer types passing 'int *' to parameter of type 'uint64_t *' (aka 'unsigned long *') [-Werror,-Wincompatible-pointer-types] return (vfs_stdcheckexp(zfsvfs->z_parent->z_vfs, nam, extflagsp, ^ /usr/src/sys/sys/mount.h:980:17: note: passing argument to parameter here vfs_checkexp_t vfs_stdcheckexp; ^ /usr/ports/sysutils/openzfs-kmod/work/zfs-c0eb5c35e/module/os/freebsd/zfs/zfs_vfsops.c:1912:32: error: incompatible pointer types passing 'int **' to parameter of type 'int *'; dereference with * [-Werror,-Wincompatible-pointer-types] credanonp, numsecflavors, secflavors)); ^~ * /usr/src/sys/sys/mount.h:980:17: note: passing argument to parameter here vfs_checkexp_t vfs_stdcheckexp; ^ 3 errors generated. *** Error code 1 Stop. With kindest regards, Kostya Berger ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
В ответ на: Re: FYI: forum web site is .. unreadable
Looks fine in my Firefox. No such problems. Locally built Firefox. Отправлено из Yahoo Почты для Android вт, 23 июн. 2020 в 10:32 Niclas Zeising написал(-а): On 2020-06-23 08:48, Gary Jennejohn wrote: > On Tue, 23 Jun 2020 01:14:52 +0200 > Steffen Nurpmeso wrote: > >> Hello. >> >> Normally i do not do forums (web interface etc etc), but i was >> interested in ZFS encryption support and so i searched, and found >> a page[1]. Now when i open that on a glibc Linux box with >> >> #?0|kent:src$ prt-get info firefox-bin >> Name: firefox-bin >> Path: /usr/ports/opt >> Version: 77.0.1 >> Release: 1 >> Description: Firefox binary >> URL: http://www.mozilla.com >> Maintainer: Fredrik Rinnestam, fredrik at crux dot guru >> Dependencies: gtk3,dbus-glib >> >> i.e. Mozilla.com-compiled firefox, then i see a small forum >> "frame" on the right side, it is right of the "Foundation" link in >> the link bar. It is just large enought to place "To be honest," >> in a single line, on a, well, pretty wide screen. >> >> [1] https://forums.freebsd.org/threads/native-encryption-of-zfs.70284/ >> >> Ciao, and good night from Germany, >> > > I see exactly the same bad formatting with the standard firefox port. All the > text is pushed to the right. > > seamonkey works, but it's been removed from ports. > It looks fine on my 1080p display, using Firefox from FreeBSD packages. Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
В ответ на: Re: editors/libreoffice PDF export/printing broken
No need to pkg upgrade. They are all freshly installed from official repo. Clean install, new fresh user. The same in my second install, Synth built local repo. Same thing. And I'm talking about the PDF button in LO interface. Or File> Export to PDF. Отправлено из Yahoo Почты для Android пн, 22 июн. 2020 в 20:22 Gleb Popov<6year...@gmail.com> написал(-а): On Mon, Jun 22, 2020 at 9:04 PM Kostya Berger wrote: > r362292In editors/libreoffice 6.4.4 PDF export is broken, including also > PDF print to file. Tried with locally built 6.4.4 and pre-built package > 6.4.4.2 from official repo (separate installation for testing purposes). > Symptoms: of all content only graphics/tables elements get exported to > PDF. No text. PS printing is all right.As regards PDF printing to file in > general, it still works fine in Firefox. Only LO is affected. I filed a bug > report as well. > > With kindest regards, > Kostya Berger > Hum, can't reproduce this on my side. Can you do `pkg upgrade`, maybe some dependency is out of date? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
editors/libreoffice PDF export/printing broken
r362292In editors/libreoffice 6.4.4 PDF export is broken, including also PDF print to file. Tried with locally built 6.4.4 and pre-built package 6.4.4.2 from official repo (separate installation for testing purposes). Symptoms: of all content only graphics/tables elements get exported to PDF. No text. PS printing is all right.As regards PDF printing to file in general, it still works fine in Firefox. Only LO is affected. I filed a bug report as well. With kindest regards, Kostya Berger ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ? ????? ??: vnc can't connect to socket
BTW, I was not using it purposefully. I think I used it because it was
suggested by TigerVNC viewer itself. The original connect dialogue, I think,
had that address in it. So I used it, and it worked. This is how I remember it.
Other than that I NEVER used this wildcard address unless suggested by
documentation in certain configurations.
With kindest regards,
Kostya Berger
On Monday, 22 June 2020, 16:56:41 GMT+3, Michael Tuexen
wrote:
> On 21. Jun 2020, at 23:12, Rodney W. Grimes
> wrote:
>
>>> On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote:
>>>>> On 21. Jun 2020, at 14:28, Kostya Berger
>>>>> wrote:
>>>>>
>>>>> Ok, it turns out, it gives the previously mentioned error only if I
>>>>> use VNC server string 0.0.0.0:5900 (as I always did). in my VNC
>>>>> client.But when replaced with127.0.0.1:5900it connects all right.
>>>>
>>>> I don't hink 0.0.0.0 is a valid destination address you can use in
>>>> connect(). Using 127.0.0.1 should
>>>> be fine.
>>
>> I do not believe that this is a destination address when your talking
>> about 0.0.0.0:5900 on the VNC server side, that is a wild card accept
>> any address and if this has been broken.. it must be fixed!
>>
>>>> I guess, https://svnweb.freebsd.org/changeset/base/361752 is the
>>>> relevant commit here.
>>>>
>>>
>>> *BSD has always accepted 0 as a synonym for localhost (and iirc, linux
>>> does not). If this no longer works, it's a regression which is going
>>> to cause existing applications and scripts to fail. At the very least
>>> it deserves an entry in UPDATING.
>>
>> I am not aware of that, but can not deny it either, and just confirmed
>> it to be true:
>> root {1002}# telnet 0.0.0.0 22
>> Trying 0.0.0.0...
>> Connected to 0.0.0.0.
>> Escape character is '^]'.
>> SSH-2.0-OpenSSH_7.8 FreeBSD-20180909
>
> And to add the netstat data to show what connected:
> tcp4 0 0 127.0.0.1.22 127.0.0.1.43135 ESTABLISHED
> tcp4 38 0 127.0.0.1.43135 127.0.0.1.22 ESTABLISHED
>
> Can we back this commit out, discuss it in next weeks call,
> and then find a way forward?
>
>>
>> INADDR_ANY is the wildcard listen address, but as a destination what code
>> remapped
>> it to 127.0.0.1?
>>
>> We should very seriously consider restoring this behavior.
Reallowing 0.0.0.0 is covered by https://reviews.freebsd.org/D25401
Best regards
Michael
>>
>>> -- Ian
>>>
>>>> Best regards
>>>> Michael
>>>>> ?? ?? Yahoo ? ??? Android
>>>>>
>>>>> ??, 21 ???. 2020 ? 9:40 Kostya Berger
>>>>> ???(-?): Hi,upgraded to 362292 via buildworld.Now I cannot
>>>>> connect to my bhyve guest as I used to: neither via VNC nor via
>>>>> RDP.VNC gets error: unable to connect the socket. Address family
>>>>> not supported by protocol family (47).
>>>>> Neither can I ping my bhyve IP (it uses a separate NIC and should
>>>>> have no problems)
>>>>> Internet connectivity is ok and I can ping other hosts on my
>>>>> network.
>>>>> In 359997 all works fine.
>>>>> ?? ?? Yahoo ? ??? Android
>>>>> ___
>>>>> freebsd-current@freebsd.org mailing list
>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>>>> To unsubscribe, send any mail to "
>>>>> freebsd-current-unsubscr...@freebsd.org"
>>>>
>>>> ___
>>>> freebsd-current@freebsd.org mailing list
>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>>> To unsubscribe, send any mail to "
>>>> freebsd-current-unsubscr...@freebsd.org"
>>>>
>>>
>>> ___
>>> freebsd-current@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>>>
>>>
>>
>> --
>> Rod Grimes rgri...@freebsd.org
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>>
>
> --
> Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
В ответ на: Re: В ответ на: vnc can't connect to socket
Oh, I see, thank you. Отправлено из Yahoo Почты для Android вс, 21 июн. 2020 в 15:54 Michael Tuexen написал(-а): > On 21. Jun 2020, at 14:28, Kostya Berger wrote: > > Ok, it turns out, it gives the previously mentioned error only if I use VNC > server string 0.0.0.0:5900 (as I always did). in my VNC client.But when > replaced with127.0.0.1:5900it connects all right. I don't hink 0.0.0.0 is a valid destination address you can use in connect(). Using 127.0.0.1 should be fine. I guess, https://svnweb.freebsd.org/changeset/base/361752 is the relevant commit here. Best regards Michael > Отправлено из Yahoo Почты для Android > > вс, 21 июн. 2020 в 9:40 Kostya Berger написал(-а): > Hi,upgraded to 362292 via buildworld.Now I cannot connect to my bhyve guest > as I used to: neither via VNC nor via RDP.VNC gets error: unable to connect > the socket. Address family not supported by protocol family (47). > Neither can I ping my bhyve IP (it uses a separate NIC and should have no > problems) > Internet connectivity is ok and I can ping other hosts on my network. > In 359997 all works fine. > Отправлено из Yahoo Почты для Android > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
В ответ на: vnc can't connect to socket
Ok, it turns out, it gives the previously mentioned error only if I use VNC server string 0.0.0.0:5900 (as I always did). in my VNC client.But when replaced with127.0.0.1:5900it connects all right. Отправлено из Yahoo Почты для Android вс, 21 июн. 2020 в 9:40 Kostya Berger написал(-а): Hi,upgraded to 362292 via buildworld.Now I cannot connect to my bhyve guest as I used to: neither via VNC nor via RDP.VNC gets error: unable to connect the socket. Address family not supported by protocol family (47). Neither can I ping my bhyve IP (it uses a separate NIC and should have no problems) Internet connectivity is ok and I can ping other hosts on my network. In 359997 all works fine. Отправлено из Yahoo Почты для Android ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
vnc can't connect to socket
Hi,upgraded to 362292 via buildworld.Now I cannot connect to my bhyve guest as I used to: neither via VNC nor via RDP.VNC gets error: unable to connect the socket. Address family not supported by protocol family (47). Neither can I ping my bhyve IP (it uses a separate NIC and should have no problems) Internet connectivity is ok and I can ping other hosts on my network. In 359997 all works fine. Отправлено из Yahoo Почты для Android ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
release name
Could somebody, please, explain this: Am I right to assume that CURRENT or "head" release number is now 12.0?For in that case I'll have to reduild the ports in case of upgrading my system to the current head, right?Because my current system was build well before the 11.0-alpfha releases statred appearing. Sent from Yahoo Mail on Android ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: error running context: operation timed out
Ok, seems to be working now :) Sent from Yahoo Mail on Android On Sun, Apr 3, 2016 at 22:03, Kostya Berger<berger...@yahoo.co.uk> wrote: Cannot download svn sources, times out. Even tried svn.freebsd.org with the same result. Sent from Yahoo Mail on Android ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
error running context: operation timed out
Cannot download svn sources, times out. Even tried svn.freebsd.org with the same result. Sent from Yahoo Mail on Android ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel memory leak with x11/nvidia-driver
Here are the results of the test you've suggested on my system (r293722),
nvidia-driver-304-304.128 -- two runs with the break of 40 minutes:
active inactive wire cache free total
85441 282221 280649 0 100455 748766
85488 282235 280655 0 100391 748769
85500 282240 280657 0 100372 748769
83226 283338 280692 0 101513 748769
82816 282439 280687 0 102827 748769
[14:01 - 1.52]
[kostya@notebook2 9] ~ $ >sudo sh test.sh
active inactive wire cache free total
82280 302769 304025 0 58081 747155
82273 302783 304021 0 58081 747158
82247 302809 304021 0 58081 747158
82239 302816 304009 0 58094 747158
82076 302995 304010 0 58077 747158
82080 303002 304010 0 58066 747158
[15:44 - 1.52]
Hope this helps and you can see some tendency you're after. With kindest
regards,
Kostya Berger
On Thursday, 4 February 2016, 3:56, Ultima <ultima1...@gmail.com> wrote:
Just tested your script, there is definitely a memory leak.
I also ran into really weird behavior. Running your script
in tmux after starting and stopping an xorg session a few,
tmux completely froze in the session. Creating a new
window in the session was also completely frozen,
however this is only visually as commands still worked,
just showed a blank black screen.
Also unloading the kernel modules for
nvidia and nvidia-modeset (new as of 358.16ish) did
not free the memory.
On Wed, Feb 3, 2016 at 8:24 PM, Ultima <ultima1...@gmail.com> wrote:
> Apologies, this should have been in my initial reply.
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201340
> or here for attachment
> https://bz-attachments.freebsd.org/attachment.cgi?id=165694
>
> I haven't actually had a chance to do anything after upgrading
> from stable other than see the corrupted console for myself.
> Lack of time =/
>
> On Wed, Feb 3, 2016 at 2:41 PM, Eric van Gyzen <vangy...@freebsd.org>
> wrote:
>
>> On 02/03/2016 10:54, Eric van Gyzen wrote:
>> > I just set up a new desktop running head with x11/nvidia-driver. I've
>> > discovered a memory leak where pages disappear from the queues, never to
>> > return. Specifically, the total of
>> > v_active_count
>> > v_inactive_count
>> > v_wire_count
>> > v_cache_count
>> > v_free_count
>> > drops, eventually becoming /much/ less than v_page_count.
>>
>> Here is a script to log the data:
>>
>> #!/bin/sh
>>
>> readonly QUEUES="active inactive wire cache free total"
>> readonly FORMAT="%s\t%s\t%s\t%s\t%s\t%s\n"
>>
>> vm_page_counts() {
>> for queue in $QUEUES; do
>> if [ "$queue" != "total" ]; then
>> sysctl -n vm.stats.vm.v_${queue}_count
>> fi
>> done
>> }
>>
>> sum() {
>> s=0
>> while [ $# -gt 0 ]; do
>> s=$((s + $1))
>> shift
>> done
>> echo $s
>> }
>>
>> print_counts() {
>> counts="`vm_page_counts`"
>> printf "$FORMAT" $counts `sum $counts`
>> }
>>
>> printf "$FORMAT" $QUEUES
>> print_counts
>> while sleep 60; do
>> print_counts
>> done
>>
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org
>> "
>>
>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
build wirh GCC -- supported?
Hi, everyone. Is GCC supported for building CURRENT? And if so, how do I set it to be default compiler?Thank you very much for the answer. Kostya Berger Sent from Yahoo Mail on Android ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: webcamd & cuse4bsd
Well, this seems to be either hardware or software (driver code) bug. After `usbconfig -d ugen1.4 reset` webcamd restarting sometimes creates the device /dev/video0 -- sometimes,, but not every time. More often than not it doesn't. So there's no method seen in this behaviour so far. I wonder how I could debug this. Sent from Yahoo Mail on Android On Wed, Dec 16, 2015 at 1:22, Kostya Berger<berger...@yahoo.co.uk> wrote: Ok, I failed to make it clear enough: the module is loaded on boot. This was what was actually meant by the expression "when the system starts". By contrast, loading on demand is... well, loading "on demand". These are two ways of starting a program, "on demand", as opposite to "when the system starts". Please, correct me if I'm wrong here.Yet the situation is as I described. That's what I'm actually reporting. Just now I've done a reboot, and here we go again: all modules loaded, /dev/cuse persent, the message telling me "webcam is already running on ugen1.4.0" (my web-camera) -- and NO /dev/video0. Though it hits me now, there are 3 devices /dev/usb/1.4.*. Maybe 1.4.0 is not the correct one? Sent from Yahoo Mail on Android On Tue, Dec 15, 2015 at 23:54, Allan Jude<allanj...@freebsd.org> wrote: On 2015-12-15 14:13, Kostya Berger wrote: > You misread my message, sorry. I said the devices are not created EVERY > TIME the system starts. Rather, it becomes A MATTER OF CHANCE. That is, > sometimes they are, sometimes they aren't. > (with the modules not loaded it would be stable NO) > > > Sent from Yahoo Mail on Android > <https://overview.mail.yahoo.com/mobile/?.src=Android> > > On Tue, Dec 15, 2015 at 23:01, Allan Jude > <allanj...@freebsd.org> wrote: > > On 2015-12-15 13:37, Kostya Berger wrote: > > > There is this problem I'm experiencing with webcamd (set to > webcamd_enable=YES) and cuse4bsd: special devices /dev/video0 and > /dev/cuse are NOT cteated every time on system start. Rather, it > becomes a matter of chance.Have the same problem on RELEASE & STABLE > as well. > > > > Sent from Yahoo Mail on Android > > ___ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org > " > > > > In /boot/loader.conf try adding: > > cuse_load="YES" > > this will load the module, and should ensure the devices are available > before webcamd starts. > > -- > Allan Jude > The module is loaded 'on demand', but obviously something it not loading it on-demand when you want it. Forcing it to always be loaded, should solve your problem. -- Allan Jude ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
webcamd & cuse4bsd
There is this problem I'm experiencing with webcamd (set to webcamd_enable=YES) and cuse4bsd: special devices /dev/video0 and /dev/cuse are NOT cteated every time on system start. Rather, it becomes a matter of chance.Have the same problem on RELEASE & STABLE as well. Sent from Yahoo Mail on Android ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
KLD: (nvidia.ko) is missing dependencies (boot message)
Hi everyone. I'm on 11.0-CURRENT #0 r289580 I didn't find this in any archives, so I'm posting it here. Mine is a ZFS based system and I'm booting using GRUB2, not the FreeBSD loader.However, this works just fine on FreeBSD 10.2 etc. But on 11.0-CURRENT this appears in boot message:... KLD file linux.ko is missing dependencies KLD file nvidia.ko is missing dependencies ...Accordingly, nvidia.ko is not loaded on boot. But when I afterwards manually `kldload nvidia`, it works just fine and the driver gets loaded. Not sure if this is related, but on shutdown/reboot I also have some ZFS related debug output, of which I can only send a photo. Not attaching it now as I'm not sure how the mailing list software will react to this, but I'm ready to send it on demand. With kindest regards, Kostya Berger ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
