On 12/19/22 21:07, Kevin Lo wrote:
On Mon, Dec 19, 2022 at 03:50:45PM -0500, Geoff Steckel wrote:
Thanks for all the suggestions:
sysctl kern.pool_debug=1 = no change
known working board in same slot = no change
hardware version is indeed 0609
em(4) in same slot = works
test using old rge
7.2 in an ASRock J4105M - same crash, much faster (8G vs 32G memory?)
Geoff Steckel
with if_rge.c?
Perhaps the AMD 5600G or the B550 chipset have quirks not seen before?
I could possibly install FreeBSD if that would give any information.
thanks again,
Geoff Steckel
76880 + 16 0x64000403b8f3400 != 0x46b8689556980a7
(panic on test 2 - all previous data identical)
fd800b118d40 + 16 0x64000409da03400 != 0x5be8fd0cf17429b
thanks for any input,
Geoff Steckel
On 5/28/22 5:22 PM, Crystal Kolipe wrote:
There certainly are people using this behaviour of the loopback address(es)
in creative ways on non-OpenBSD systems:
https://timkay.com/solo/
Changing it on those systems will likely break various users' scripts in
unexpected ways.
The script
Ran a grep to find unneccessary NULL checks before free(3) and found
some in dhclient(8) and makefs(8).
Geoff Hill
Index: sbin/dhclient/dhclient.c
===
RCS file: /cvs/src/sbin/dhclient/dhclient.c,v
retrieving revision 1.659
diff -u
Looking at the ed25519 code, these defines are unused. They appear to be unused
upstream as well (in djt's supercop ed25519/ref implementation), so maybe this
should be suggested there instead of deviating. Up to you.
Index: usr.bin/signify/fe25519.c
> you need a space between the arg and punctuation
Fixed.
> you can find trivial errors like that if you run your changes through
> mandoc:
>
> $ mandoc -Tlint event.3
Thanks, that is good to know. Should have kept mdoc(7
documentation but it stalled.
Here's a patch that adds the function synopsis and a brief description
of how watermarks work separately for read and write. Mostly copied from
the function declaration comments in event.h.
ok?
Geoff Hill
Index: event.3
The imsg_init(3) man page currently doesn't make it clear whether
this library can be used for remote communication.
The current text reads:
The imsg functions provide a simple mechanism for communication
between processes using sockets. Each transmitted message is
guaranteed to be
Right now the printf(3) family of manpages make no reference to errno.
Glancing at __vfprintf, it appears that most of the erroneous paths do
set errno.
Should the manual be amended to reflect this behavior, so that users
have a documented way to determine the cause of failure in such cases?
One semicolon should do just fine here.
Index: dev/usb/xhci.c
===
RCS file: /cvs/src/sys/dev/usb/xhci.c,v
retrieving revision 1.72
diff -u -p -r1.72 xhci.c
--- dev/usb/xhci.c 10 Mar 2017 11:18:48 - 1.72
+++
> Any reason to not replace the somewhat arbitary earlier test
> for this?
I chose to keep the condition simpler and the existing constraints intact for
minimal impact, but I would agree it's better to consolidate with the existing
check.
Your diff looks good to me, +1.
Fix possible reads past the end of the buffer.
Found by random fuzz testing (zzuf). Without the fix the fuzzer crashes
in several seconds; with the patch, the fuzzer runs clean for hours.
Index: midiplay.c
===
RCS file:
? */
if (mcopy)
(void) looutput(ifp, mcopy, dst, rt);
Does the loopback for a simplex interface for IPv6 happen somewhere else?
thanks!
Geoff Steckel
in this area soon?
thanks
Geoff Steckel
state matching.
It looks like TIME_EXCEEDED packets can't match because of
the different rdomains and therefore get dropped invisibly.
Comments? Flames? RTFMs?
thanks
Geoff Steckel
sufficient
memory barriers was painful. I don't remember how to make that request.
Geoff Steckel
where packets were dropped with no record. I inserted counters
to get at least a global count. It's conceptually very ugly to silently fail
in a vital part of the network stack. It's definitely a frustrating
inconvenience.
Geoff Steckel
On 01/24/2014 02:09 PM, Henning Brauer wrote:
* Ted Unangst t...@tedunangst.com [2014-01-24 17:48]:
Are people still using sk, gem, or hme (!) in pps performance critical
situations?
doesn't make sense to do so, and hasn't in a long time...
Performance critical? Well, given the pathetic
security
failures.
The internet is an extremely hostile place.
need to know and need to access must be your rules.
block everything else.
geoff steckel
.
If the file is written out, the file is destroyed.
IMnsHO, that is fatally flawed.
Returning an error for an impossible character translation is specified
in the archaic version of the Unicode standard I read.
That is not useful in an editor.
Geoff Steckel
On 08/23/2012 06:55 PM, Stefan Sperling wrote:
On Thu, Aug 23, 2012 at 05:32:51PM -0400, Geoff Steckel wrote:
Using iconv in an editor is EXTREMELY dangerous without complex precautions.
Given a file containing characters not valid in the current locale,
it will at minimum prevent viewing
1GHz) Pentium boards, the idle interrupt time was
1-2%. That was deemed acceptable. Slow interrupt processing for Ethernet
interfaces was far more painful and important to fix.
Geoff Steckel
Index: sys/kern/sysv_msg.c
===
RCS file: /cvs/src/sys/kern/sysv_msg.c,v
retrieving revision 1.24
diff -u -r1.24 sysv_msg.c
--- sys/kern/sysv_msg.c20 May 2011 16:06:25 -1.24
+++ sys/kern/sysv_msg.c3 Feb 2012 23:58:45
On 01/03/2012 01:28 PM, Gregor Best wrote:
On my system, the patch causes wpi to timeout during firmware upload,
resulting in a non-working WiFi card.
The dmesg doesn't say anything more besides that. Is there anything I
can do to provide more useful data?
--
Gregor Best
[demime 1.01d
?)
makes physio() likely not to use copyin/copyout
There may be definition disfunctions with OHCI similar to
those with EHCI. There's a suspicious malloc().
I'll look at them later.
Happy new year!
Geoff Steckel
Diffs and dmesg:
Index: arch/amd64/amd64/bus_dma.c
by tweaking net.inet.tcp.footshooter.sbmax?
footshooter.net.sbmax perhaps? Such a hierarchy could be populated with
all the parameters it's, umm, unwise to tweak without a lot of
knowledge. A 90% frivolous suggestion.
Geoff Steckel
, perhaps
limited to (arbitrarily) 50% of physical memory?
Geoff Steckel
. It will save the maintainer's sanity
when the kernel or library changes or adds functionality. 99.9% of the
reporting code will never be executed. Trade that cost against weeks of
frustration.
I'd be glad to share gory descriptions of weeks spent chasing unreported
errors off line.
Geoff
would be harder, and I'd like any available wisdom first.
I have a reason to push disks as fast as hardware
allows and want to reduce software-induced bottlenecks
as much as possible.
thanks!
Geoff Steckel
shows at least dev/ic/osiopvar.h doesn't compute
DMA resources from MAXPHYS. There are probably other 17s buried
in ugly places.
It doesn't seem to help disk I/O speed at all.
It *does* decrease interrupt rate to about 400/sec.
Now to try some other tests. Grumble.
Geoff Steckel
at freebsd aio code which might not map to openbsd low
level routines the swapper code which might (though single threaded)
be a good place to start for low level code.
All opinions welcome!
thanks
Geoff Steckel
for ones read once and/or written once per program
invocation.
geoff steckel
gwes at oat mumble com
34 matches
Mail list logo