combination vm.pfault_oom_attempts and vm.pfault_oom_wait
to values that could contribute to a sustained period of
saturating the USB channel.
(I have no detailed knowledge of how the tradeoffs work
for the competing uses of the USB channel. So I can not
validly claim to know that the above is realistic.)
===
Mark Millard
marklmi at yahoo.com
ngs worth looking for?
>
> Right now I'm using in /etc/rc.conf the line
> sshd_flags="-E /var/log/sshd_debug.log"
> which is already quite verbose. Is there a better
> option that emphasizes errors over normal traffic?
I'm not likely to identify such, unfortunately.
===
Mark Millard
marklmi at yahoo.com
www.zefox.org86.2%29 160.4 144.9
102.1 160.5 28.6
www.zefox.org ended up at 17. and stayed there
once it got there.
I've no clue if this observation is of any use.
===
Mark Millard
marklmi at yahoo.com
On 2022-May-2, at 08:53, bob prohaska wrote:
> On Mon, May 02, 2022 at 08:56:12AM +0200, Hans Petter Selasky wrote:
> [reply at end]
>> On 5/2/22 03:13, bob prohaska wrote:
>>> On Sun, May 01, 2022 at 05:10:59PM -0700, Mark Millard wrote:
>>> [reply at end]
>
On 2022-May-1, at 16:27, bob prohaska wrote:
> On Sun, May 01, 2022 at 12:58:45PM -0700, Mark Millard wrote:
>>
>> Looks like there is some problem getting past
>> gig1-1-1.gw.davsca11.sonic.net .
>>
>
> That seems independent of my own internal connection pro
On 2022-May-1, at 12:15, Mark Millard wrote:
> On 2022-May-1, at 11:12, bob prohaska wrote:
>
>> On Sat, Apr 30, 2022 at 06:39:57PM -0700, Bakul Shah wrote:
>>> On Apr 29, 2022, at 7:12 PM, bob prohaska wrote:
>>>>
>>>> Since about Dece
-0-0-0.cr1.scrmca13.sonic.net (135.180.179.166) 30.373 ms
gig1-1-1.gw.wscrca11.sonic.net (50.1.36.106) 35.567 ms
0.xe-0-0-0.cr1.scrmca13.sonic.net (135.180.179.166) 31.146 ms
15 gig1-1-1.gw.davsca11.sonic.net (50.1.36.110) 31.513 ms
gig1-1-1.gw.wscrca11.sonic.net (50.1.36.106) 31.203 ms
gig1-1-1.gw.davsca11.sonic.net (50.1.36.110) 31.354 ms
16 gig1-1-1.gw.davsca11.sonic.net (50.1.36.110) 30.125 ms * 31.996 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
^C
(There did not seem to be much point in having it continue.)
===
Mark Millard
marklmi at yahoo.com
On 2022-Apr-30, at 18:11, bob prohaska wrote:
> On Fri, Apr 29, 2022 at 08:14:27PM -0700, Mark Millard wrote:
>> On 2022-Apr-29, at 19:12, bob prohaska wrote:
>>
>>> Since about December of 2021 I've been noticing problems with
>>> wired network co
nd any ideas! If some essential
> details have been omitted please indicate and I'll try to
> supply them.
>
My questions and suggestions are all not network-knowledge
specific. My background does not span the public network
related material, sorry.
(Some of this duplicates some off-list activity.)
===
Mark Millard
marklmi at yahoo.com
[The USB I/O problem.]
On 2022-Mar-13, at 13:46, Mark Millard wrote:
>> FreeBSD pelorus.zefox.org 13.1-STABLE FreeBSD 13.1-STABLE #24
>> stable/13-n249989-b85d0d603c5: Sat Mar 12 17:47:19 PST 2022
>> b...@pelorus.zefox.org:/usr/obj/usr/src/arm64.aarch64
sbtest
> Makefile usb_control_ep_test.c usb_msc_test.c
> usbtest.c
> Makefile.depend usb_modem_test.cusb_msc_test.h
> usbtest.h
>
> Is there any guidance on what they do? I couldn't find a man page.
>
===
Mark Millard
marklmi at yahoo.com
On 2022-Feb-17, at 00:02, Mark Millard wrote:
> On 2022-Feb-16, at 15:18, bob prohaska wrote:
>
>> [changed subject to more clearly reflect the symptoms]
>>
>> On Mon, Feb 14, 2022 at 09:59:23PM -0800, Mark Millard wrote:
>>>>>>> Since I
On 2022-Feb-16, at 15:18, bob prohaska wrote:
> [changed subject to more clearly reflect the symptoms]
>
> On Mon, Feb 14, 2022 at 09:59:23PM -0800, Mark Millard wrote:
>>>>>> Since I have a context working based on the kernel in:
>>>>>>
>>&
13 matches
Mail list logo
