date:20210327

system freeze on 14.0-CURRENT

2021-03-27 Thread Masachika ISHIZUKA

  I have trouble with recent 14.0-CURRENT 146 (e.x. main-6a762cfae,
main-3ead60236, main-25bfa4486).
  It works well on recent 14.0-CURRENT until starting firefox.
  If I start firefox (v87.0), system freeze but no core dumps.
  If it booted old kernel 145 (e.x. main-b5449c92b), firefox v87.0
is working well.

# I want to update to the newest 14.0-CURRENT because of ssl security
  problems.
-- 
Masachika ISHIZUKA
___
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: VirtualBox 6.1.18⋯, Windows (was: 13.0 RC4 might be delayed)

2021-03-27 Thread Kevin Oberman

Host is FreeBSD 13-STABLE.Guest is Win 7 which I depend on for Quicken. I
also use it to access a bank account at a bank that refuses access from any
OS other than Windows or MacOS. I managed to access it for about a year by
having Firefox lie and claim to be Windows, but that stopped working. They
make the almost humorous claim that only Windows and MacOS are adequately
secure.

At this point I have no idea if the issue is with VirtualBx or FreeBSD,
but, after seeing more details of your problem, I doubt mine is related. I
really suspect it's VirtualBox, so I will drop out of this discussion as it
appears that I don't have an issue with it. After some more work on it,
I'll open a ticket with emulators@.

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

On Fri, Mar 26, 2021 at 7:23 PM Graham Perrin 
wrote:

> On 26/03/2021 21:55, Kevin Oberman wrote:
> > On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin  > > wrote:
> >
> >
> > If I'm not mistaken:
> >
> > …
> >
> > Had nothing but frequent guest lockups on 6.1.18 with my Win7 system.
> > That was right after 6.1.18 was put into ports. Fell back to legacy
> > (v5) and will try again shortly to see if it's any better.
>
> Windows 7 guest or host?
>
> For me, Windows 10 20H2 guest is rock solid.
>
> % pkg info -x virtualbox
> virtualbox-ose-6.1.18
> virtualbox-ose-kmod-6.1.18_1
> % freebsd-version -kru
> 14.0-CURRENT
> 14.0-CURRENT
> 14.0-CURRENT
> % uname -a
> FreeBSD mowa219-gjp4-8570p 14.0-CURRENT FreeBSD 14.0-CURRENT #90
> main-n245648-66f138563be: Thu Mar 25 08:00:54 GMT 2021
> root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
> amd64
> %
>
>
___
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"

12.2-RELEASE-p4 and 13.0-RC3 versus VirtualBox

2021-03-27 Thread Graham Perrin


On 26/03/2021 20:36, Graham Perrin wrote:

On 26/03/2021 20:01, Graham Perrin wrote:

If I'm not mistaken:

* 13.0-RC3 seems to be troublesome, as a guest machine, with 
emulators/virtualbox-ose 6.1.18 as the host


…


On closer inspection: the problem is not limited 13.0-RC3.

If I save the state of a guest whilst 12.2-RELEASE-p3 runs:

* no problem after starting from the saved state.

If I upgrade to 12.2-RELEASE-p4, restart the guest then save the 
state, I can start from the saved state, however:


* no response to keyboard input

* ACPI shutdown does not begin a shutdown routine.


A screen recording of 13.0-RC3 not responding to keyboard input:



At 01:40 on the timeline, keyboard input (visible with x11/screenkey in 
the host) has no effect on the FreeBSD guest.


For me, this seems to be easily reproducible; the screen recording above 
was made soon after beginning to work with 
 
attached to a new virtual machine.


I'd like to report the bug (and maybe have a fix before 13.0-RELEASE) 
but not before someone else can confirm it. To anyone who's interested: 
find me in Matrix or IRC for #freebsd and I'll let you have a copy of 
the file below, which can be used with FreeBSD-13.0-RC3-amd64.vhd.xz


FreeBSD-13.0-RC3-amd64.vhd.ova

Thanks

___
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: WITHOUT_KERNEL_SYMBOLS - *.ko now with debug_info

2021-03-27 Thread Herbert J. Skuhra

add Cc: current@

On Mon, 22 Mar 2021 02:17:11 +0100, "Herbert J. Skuhra" wrote:
> 
> On Sun, Mar 21, 2021 at 11:11:08PM +0100, Herbert J. Skuhra wrote:
> > Hi,
> > 
> > since upgrading to stable/13 I was wondering why /boot/kernel is much
> > larger. When using "WITHOUT_KERNEL_SYMBOLS=" in /etc/src.conf the
> > kernel modules now contain debug_info. OK? (I manually run "objcopy
> > --strip-debug".)
> 
> I found the following commit:
> 
> commit 9b6edf364eb05aca4709732136e92a6ab739bb36
> Author: Conrad Meyer
> Date:   Tue Jun 23 18:25:31 2020 +
> 
> If this change is correct maybe src.conf(5) should be updated:
> 
> WITHOUT_KERNEL_SYMBOLS
>  Set to not install kernel symbol files.  This option is
>  recommended for those people who have small root partitions.

???

% make -j4  buildkernel KERNCONF=GENERIC SRCCONF=/dev/null
% doas make installkernel KERNCONF=GENERIC SRCCONF=/dev/null 
KODIR=/boot/testkernel
% doas rm -rf /usr/obj/usr/src/amd64.amd64/sys/GENERIC
% cat /etc/src_tmp.conf 
WITHOUT_KERNEL_SYMBOLS=
% make -j4  buildkernel KERNCONF=GENERIC SRCCONF=/etc/src_tmp.conf
% doas make installkernel KERNCONF=GENERIC SRCCONF=/etc/src_tmp.conf 
KODIR=/boot/testkernel2
% du -sh /boot/testkernel 
 63M/boot/testkernel
(=> ~ 153M UFS or ZFS with compression=off) 
% du -sh /usr/lib/debug/boot/testkernel/
151M/usr/lib/debug/boot/testkernel/
(=> ~ 491M UFS or ZFS with compression=off)
% du -sh /boot/testkernel2
155M/boot/testkernel2
(=> ~ 494M UFS or ZFS with compression=off)

--
Herbert
___
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.0 RC4 might be delayed

2021-03-27 Thread dmilith .

It may not only be Virtualbox, but also happens under Vmware VMs.

I use Vmware Fusion 7 pro as my software build-host on top of my Mac
Pro for years now, but I can't build much with 13.0 cause regular
build processes (like sed, awk, grep, zsh) turn into zombies randomly.
Example shot from my private CI from yesterday:
http://s.verknowsys.com/12f14b0350ee3baeb8f153cd48764bc8.png

The issue doesn't happen on 12.2, 12.1, 12.0 or older releases.

I reported this issue (I'm testing it since 13-alpha) here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253718

In RC3 it feels it got even worse and happens even more often… It's a
critical release blocker if you ask me…

kind regards
Daniel

On 27/03/2021, David G Lawrence via freebsd-current
 wrote:
>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
>> wrote:
>>
>> > On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
>> > > ??? if people are having issues with ports like ???
>> >
>> > If I'm not mistaken:
>> >
>> > * 13.0-RC3 seems to be troublesome, as a guest machine, with
>> > emulators/virtualbox-ose 6.1.18 as the host
>> >
>> > * no such trouble with 12.0-RELEASE-p5 as a guest.
>> >
>> > I hope to refine the bug report this weekend.
>> >
>>
>> Had nothing but frequent guest lockups on 6.1.18 with my Win7 system.
>> That
>> was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
>> will try again shortly to see if it's any better.
>
> Kevin,
>
>Make sure you have these options in your /etc/sysctl.conf :
>
> vfs.aio.max_buf_aio=8192
> vfs.aio.max_aio_queue_per_proc=65536
> vfs.aio.max_aio_per_proc=8192
> vfs.aio.max_aio_queue=65536
>
>...otherwise the guest I/O will random hang in VirtualBox. This issue
> was
> mitigated in a late 5.x VirtualBox by patching to not use AIO, but the
> issue
> came back in 6.x when that patch wasn't carried forward.
>
> -DG
> ___
> 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"
>


-- 
--
Daniel Dettlaff
Versatile Knowledge Systems
verknowsys.com
___
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: freebsd 13 ryzen micro stutter

2021-03-27 Thread Santiago Martinez

Hi, i have the same output as @Nils B. If i run with steal =2 and dtrace 
the micro stutter doesn't happen but as soon as i stop the dtrace script 
it the stutters come back again.


Santi

On 3/27/21 10:39 AM, Santiago Martinez wrote:
Hi there, my pause are not that often ( with steal_thresh=2) , maybe 
is around 30 secs or so.


If i set the thresh to 1 or 0 they go away. Now im trying with =2 and 
schedgraph.d.


Santi


On 3/25/21 10:04 AM, Alastair Hogge wrote:

On 2021-03-23 17:34, myfreeweb wrote:
On March 23, 2021 9:11:46 AM UTC, Michael Gmelin  
wrote:


On Mon, 22 Mar 2021 23:50:52 -0400
monochrome  wrote:


After about 8 months of struggling to narrow this down I did another
search and saw this:

https://www.reddit.com/r/freebsd/comments/lc8fwo/freebsd_13_vega_64_micro_stutter_in_x/ 



I haven't seen this come up here so I thought I would bring it up.

My story started sometime before around August last year when synergy
started getting really annoying with stuttering. Pretty sure it
wasn't like that when I first started tracking 13-current in around
May 2020 (I was on 12 with scfb for a long time before that with no
issues), but since then I have tried to eliminate as many variables
as possible. First I switched to barrier instead of synergy. Shortly
after that I realized it was happening all the time and not just a
network problem, I started using foobillard to verify during tests. I
tried different RAM combinations, different network cards, a variety
of RAM timings, stripping rc.conf etc, powerd settings, also scfb,
with no effect. It is observable with ping -f, a dot or two appears
every time it glitches. It seemed much better with RC2, but now with
RC3 it seems to be back with a vengeance, and since its my main
workstation and barrier/synergy server host for several machines, it
is unbearable to use. Both Win10 and devuan3 on the same machine are
smooth with no issues. Any feedback or info would be appreciated.

Hardware:
ASRock B450M Pro4
Ryzen 2400G, no OC
32M DDR4-2933
Onboard Vega GPU, drm-fbsd13-kmod
___

Without knowing much about the issue at hand, just a few ideas:

Sysctls I would look at:
- raising *.cx_lowest
- different kern.eventtimer.timer

None of these should be an issue, but:

sysctl kern.sched.steal_thresh=1

For some reason with the default value of 2, I'm seeing weird
stuttering in youtube videos, games, etc. on a 5950X system. 1 (or 0,
IIRC) works fine.

I have noticed this too, firefox exhibits the issue frequently, however
I have
found it most noticeable in games/dhewm3[0] or Yamagi Quake 2[1]. There
is a distinct pause every 3 or 4 seconds where the simulation advances
significantly. Thanks for the kern.sched.steal_thresh pointer that has
sorted
the issue out for now.

$ dmesg | egrep '(CPU:|avail memory)'
CPU: AMD Ryzen 9 3950X 16-Core Processor (3500.02-MHz
K8-class CPU)
avail memory = 66779394048 (63685 MB)
With an AMD NAVI 8GiB GPU, the host should be able to play either game
well enuf,
Quake 2 came out in 1997 and Doom 3 2004. I am sure Quake 2 used to play
without issues on my old AMD bulldozer.


0: https://www.freshports.org/games/dhewm3/
1: https://github.com/yquake2/yquake2
___
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: freebsd 13 ryzen micro stutter

2021-03-27 Thread Santiago Martinez

Hi there, my pause are not that often ( with steal_thresh=2) , maybe is 
around 30 secs or so.


If i set the thresh to 1 or 0 they go away. Now im trying with =2 and 
schedgraph.d.


Santi


On 3/25/21 10:04 AM, Alastair Hogge wrote:

On 2021-03-23 17:34, myfreeweb wrote:

On March 23, 2021 9:11:46 AM UTC, Michael Gmelin  wrote:


On Mon, 22 Mar 2021 23:50:52 -0400
monochrome  wrote:


After about 8 months of struggling to narrow this down I did another
search and saw this:

https://www.reddit.com/r/freebsd/comments/lc8fwo/freebsd_13_vega_64_micro_stutter_in_x/

I haven't seen this come up here so I thought I would bring it up.

My story started sometime before around August last year when synergy
started getting really annoying with stuttering. Pretty sure it
wasn't like that when I first started tracking 13-current in around
May 2020 (I was on 12 with scfb for a long time before that with no
issues), but since then I have tried to eliminate as many variables
as possible. First I switched to barrier instead of synergy. Shortly
after that I realized it was happening all the time and not just a
network problem, I started using foobillard to verify during tests. I
tried different RAM combinations, different network cards, a variety
of RAM timings, stripping rc.conf etc, powerd settings, also scfb,
with no effect. It is observable with ping -f, a dot or two appears
every time it glitches. It seemed much better with RC2, but now with
RC3 it seems to be back with a vengeance, and since its my main
workstation and barrier/synergy server host for several machines, it
is unbearable to use. Both Win10 and devuan3 on the same machine are
smooth with no issues. Any feedback or info would be appreciated.

Hardware:
ASRock B450M Pro4
Ryzen 2400G, no OC
32M DDR4-2933
Onboard Vega GPU, drm-fbsd13-kmod
___

Without knowing much about the issue at hand, just a few ideas:

Sysctls I would look at:
- raising *.cx_lowest
- different kern.eventtimer.timer

None of these should be an issue, but:

sysctl kern.sched.steal_thresh=1

For some reason with the default value of 2, I'm seeing weird
stuttering in youtube videos, games, etc. on a 5950X system. 1 (or 0,
IIRC) works fine.

I have noticed this too, firefox exhibits the issue frequently, however
I have
found it most noticeable in games/dhewm3[0] or Yamagi Quake 2[1]. There
is a distinct pause every 3 or 4 seconds where the simulation advances
significantly. Thanks for the kern.sched.steal_thresh pointer that has
sorted
the issue out for now.

$ dmesg | egrep '(CPU:|avail memory)'
CPU: AMD Ryzen 9 3950X 16-Core Processor (3500.02-MHz
K8-class CPU)
avail memory = 66779394048 (63685 MB)
With an AMD NAVI 8GiB GPU, the host should be able to play either game
well enuf,
Quake 2 came out in 1997 and Doom 3 2004. I am sure Quake 2 used to play
without issues on my old AMD bulldozer.


0: https://www.freshports.org/games/dhewm3/
1: https://github.com/yquake2/yquake2
___
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"

system freeze on 14.0-CURRENT

Re: VirtualBox 6.1.18⋯, Windows (was: 13.0 RC4 might be delayed)

12.2-RELEASE-p4 and 13.0-RC3 versus VirtualBox

Re: WITHOUT_KERNEL_SYMBOLS - *.ko now with debug_info

Re: 13.0 RC4 might be delayed

Re: freebsd 13 ryzen micro stutter

Re: freebsd 13 ryzen micro stutter

7 matches

Site Navigation

Mail list logo

Footer information