Hi,
On 30.06.23 07:07, Brian Buhrow wrote:
hello. Yes, this behavior is expected. It ensures that there is no
conflict between the
device on the domu end of the vif port and the device on the dom0 end. This is
more
sane behavior than FreeBSD, which zeros out the MAC address on the
hello. Yes, this behavior is expected. It ensures that there is no
conflict between the
device on the domu end of the vif port and the device on the dom0 end. This is
more
sane behavior than FreeBSD, which zeros out the MAC address on the dom0 side of
the vif.
-thanks
-Brian
Hello,
On 29.06.23 11:58, Matthias Petermann wrote:
While I do not want to praise the evening before the dayyou deserve
some feedback. Both the synthetic test with ssh/dd and my real payload
with ssh/dump have been running for easily 6 hours without interruption
this morning. I took the
Updating src tree:
P src/distrib/sets/lists/man/mi
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/external/apache2/mDNSResponder/prepare-import.sh
P src/external/apache2/mDNSResponder/dist/mDNSPosix/PosixDaemon.c
P src/lib/libc/gen/vis.c
P src/share/man/man4/Makefile
P src/share/man/man4/npflog.4
P
On Thu, Jun 29, 2023 at 08:59:18PM +0700, Robert Elz wrote:
>
> When I set 3400, which is what I have right now, if that dropped to low 30's,
> or high 20's, or just stayed the same while idling as your processor does,
> then that would all make sense. But it doesn't. I am running at 3400 now,
Another reply to multiple messages in one, but starting from the last
one this time, as it is the most important I think.
Date:Thu, 29 Jun 2023 13:52:03 +0200
From:Michael van Elst
Message-ID:
| One possibility would be that the 3401 mode didn't enable turbo
On Thu, Jun 29, 2023 at 06:01:28PM +0700, Robert Elz wrote:
> It is, and I'm aware of it. I'm not sure why Michael wanted to know
> whether the speed was actually being altered or not,
One possibility would be that the 3401 mode didn't enable turbo frequencies
but actually throttled the CPU
On Thu, Jun 29, 2023 at 12:03:33PM +0200, Rhialto wrote:
> On Thu 29 Jun 2023 at 16:50:27 +0700, Robert Elz wrote:
> > And then for fun, at 3401 ... this one I needed to run the test several
> > times until the kernel picked one of the fastest processors to run it on
>
> When I was muddling with
On Thu, Jun 29, 2023 at 04:50:27PM +0700, Robert Elz wrote:
> It looks to me as if the frequency adjustments are working properly,
Then it gets really strange what the temperature sensor would see.
One possibility would be that the Tjmax value is actually changed
dynamically (maybe some SMM
Date:Thu, 29 Jun 2023 12:03:33 +0200
From:Rhialto
Message-ID:
| In your cpu this may be the case too, which would give confusing results
| if you're not aware of the possibility.
It is, and I'm aware of it. I'm not sure why Michael wanted to know
whether the
Hi Brian,
On 26.06.23 16:17, Brian Buhrow wrote:
hello. A couple of quick questions based on the convrsation and the
snippets of logs
shown in the e-mails.
1. Is the MAC address shown in the ARP replies the correct one for the dom0?
No reason it
should be wrong, but it's worth
On Thu 29 Jun 2023 at 16:50:27 +0700, Robert Elz wrote:
> And then for fun, at 3401 ... this one I needed to run the test several
> times until the kernel picked one of the fastest processors to run it on
When I was muddling with estd to dynamically slow down my cpus when not
in use, I was told
Hi,
On 26.06.23 15:37, RVP wrote:
On Mon, 26 Jun 2023, Matthias Petermann wrote:
Could it still be an ARP related issue? I did a simplified version of
the test this morning:
Try this test: since you have static IP- & MAC-addresses everywhere in
your setup, just add them as static ARP
Date:Thu, 29 Jun 2023 08:27:05 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| You could run a benchmark like 'openssl speed sha256' and compare
| the 3400 MHz target and the target and step lower.
First, my userland (that I run most of the
k...@munnari.oz.au (Robert Elz) writes:
> | When this happens, is the machine actually running at 3400 MHz?
>How do I tell?
You could run a benchmark like 'openssl speed sha256' and compare
the 3400 MHz target and the target and step lower.
> | >The motherboard is an AsRock Z690 Taichi.
> |
Date:Thu, 29 Jun 2023 05:39:23 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| When this happens, is the machine actually running at 3400 MHz?
How do I tell? But if you mean what does machdep.cpu.frequency.current
report, then yes, that is
16 matches
Mail list logo
