Re: [RFC 2] userconf(4): 2nd proposal

2023-11-05 Thread RVP
Oh, I like the idea (I've always wanted a mechanism to list drivers etc. using patterns); it's just the syntax that sticks in the craw. Too many meta-chars. there. OTOH, `cmd -p xyz* *abc' doesn't need much thought. And, aliases are pretty standard too. But, this is your show, n'est pas...? Don't let me stop you! -RVP

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread RVP
a `-g' group flag: uc> list -g # list all "groups" uc> list -g drmkms # list devices in group drmkms uc> disable -g drmkms # disable group drmkms -RVP

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread RVP
supporting boot.cfg, Definition in boot.cfg was the intent. -RVP

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread RVP
On Sat, 4 Nov 2023, RVP wrote: 1) Allowing shell-like patterns (not hard to implement): uc> disable *drm* *usb$ # all with `drm' anywhere and those ending in Ah, since these are shell-like patterns there's not need for a `$' to denote EOL. So: uc> disable *drm* *usb

Re: [RFC 2] userconf(4): 2nd proposal

2023-11-04 Thread RVP
# exact match 1 (index) 2) Having an alias facility: uc> alias drm_disable=disable i915*; disable *radeon*; ... uc> drm_disable # executes: RHS text (no recursive expansion) uc> alias drm_disable= # remove alias `drm_disable' -RVP

Re: kern.boottime drift after boot?

2023-10-12 Thread RVP
if the machines have actually rebooted for the updates to "take". But, as abs@ just scoped out, it can have other uses too... -RVP

Re: kern.boottime drift after boot?

2023-10-11 Thread RVP
On Wed, 11 Oct 2023, Simon Burge wrote: RVP wrote: I think what David's looking for is something akin to Linux's /proc/sys/kernel/random/boot_id something which only changes on every boot but is otherwise stable. I'm curious how well this boot_id works on Linux for things like a embedded

Re: kern.boottime drift after boot?

2023-10-10 Thread RVP
and run ntpdate. kern.boottime should now jump forwards by a minute. I think what David's looking for is something akin to Linux's /proc/sys/kernel/random/boot_id something which only changes on every boot but is otherwise stable. -RVP

Re: GPT attributes in dkwedge [PATCH]

2023-09-25 Thread RVP
. Eg. ``` gop=0 ``` on its own line will work with a 9.x bootloader. But the 10.x bootloader needs a `gop 0' in a `menu=' entry to have the same effect. -RVP

Re: Hard link creation witout write access

2023-09-07 Thread RVP
played with this after christos@ added the knobs last year[1], and then sort(1) broke badly. See PR 56775. Expect further squalls if this is turned on by default. -RVP [1]: https://mail-index.NetBSD.org/tech-security/2022/03/25/msg001108.html

Re: Anonymous vnodes?

2023-06-26 Thread RVP
* or VOP_* functions?) If this idea is indeed not possible, should/could I implement something like this? (If so, how?) You could extend what shm_open() currently does on NetBSD: create a unique temp. file in /var/shm; immediately unlink it, return the fd. -RVP

Re: flock(2): locking against itself?

2023-03-30 Thread RVP
ation". -RVP

Re: proposed cpuctl modification

2023-03-03 Thread RVP
The `ucode' command in cpuctl.8 may need fixing up: 1. cpuno `-1' to update all CPUs looks like that is for Xen-only (on amd64). 2. cpuno `-2' to update current CPU doesn't get passed to the kernel because cpuset_set() returns EINVAL. -RVP

Re: Finding the slot in the ioconf table a module attaches to?

2023-02-01 Thread RVP
as been removed from the new module framework. Can someone point me in the correct direction as to where to look for the replacement function for this macro with the new module framework? These should help you: /usr/src/sys/modules/examples/readhappy/readhappy.c /usr/src/sys/conf/majors* -RVP

Re: How to build a custom module under NetBSD--9.x and newer?

2023-01-31 Thread RVP
-f drm.txt $NetBSD: drm_agpsupport.c,v 1.13 2022/07/19 22:24:33 riastradh Exp $ $NetBSD: drm_pci_module.c,v 1.7 2018/08/28 03:41:39 riastradh Exp $ $ ``` You might have a similar situation with two MODULE(...) in the sources comprising your module. Dunno how to fix this though... -RVP

Re: ATA TRIM?

2022-12-12 Thread RVP
_blocks is the maximum no. of 512-byte DSM packets which the drive will accept. In your case, 8 blocks = 4K. Therefore your drive can trim, in a single DSM request, a maximum of 8 * 64 * 512 * 65535 = ~16 GB You clearly know a lot more about the relevant commands than I do, Clearly not :-( -

Re: ATA TRIM?

2022-12-09 Thread RVP
On Fri, 9 Dec 2022, RVP wrote: OK, so any requests >4K will have to be packaged into further range requests [...] This isn't right. Bytes 7 & 8 of a TRIM range request form a counter. So, a counter of 1 = (1 x max_dsm_blocks); 2 = (2 x max_dsm_blocks) up to 0x counts. And you can

Re: ATA TRIM?

2022-12-09 Thread RVP
ata/ata_da.c Hope this helps, -RVP

Re: ATA TRIM?

2022-12-09 Thread RVP
.) What is the value of `max_dsm_blocks' that your drive reports? Unfortunately, atactl(8) doesn't show this currently. -RVP

Re: ATA TRIM?

2022-12-08 Thread RVP
to userland.) [...] Why? cmd.flags specifies AT_WAIT, and as I remarked above it is indeed waiting, so cmd, on the kernel stack, should outlive the I/O attempt. OK, I now see that the *_exec_command()s in 5.2 do wait if AT_WAIT is set. 9.X does a ata_wait_cmd() for this. -RVP

Re: ATA TRIM?

2022-12-08 Thread RVP
ec_command(wd->drvp,); printf("TRIM %s: returned %d\n",device_xname(wd->sc_dev),rv); return(0); } break; Ah, shouldn't `cmd' be allocated memory rather than being a locally-scoped variable? -RVP

Re: ATA TRIM?

2022-12-08 Thread RVP
return(0); ata_exec_command() will start the command, but, the completion of it is usually signalled by an interrupt. Presumably, the 9.2 ATA-related code takes care of this as ata_exec_command() takes a `xfer' parameter rather than a bare command struct. How does 5.2 wait for ATA command completion? -RVP

Re: Limiting malloc to the low 2GB?

2022-11-28 Thread RVP
On Tue, 29 Nov 2022, Valery Ushakov wrote: Me too :) But that works for now. Will need to RTFS. Would setrlimit(RLIMIT_AS), setrlimit(RLIMIT_DATA) work for you? -RVP

Re: Limiting malloc to the low 2GB?

2022-11-28 Thread RVP
very large allocations). -RVP

Re: Limiting malloc to the low 2GB?

2022-11-28 Thread RVP
the old `src/lib/libbsdmalloc' which only uses sbrk(). -RVP

Re: Open master pty (/dev/ptmx) non blocking

2022-09-23 Thread RVP
& O_NONBLOCK) { + return EINVAL; + } + Or: ``` if (flags & ~(O_RDWR | O_NOCTTY)) return EINVAL; ``` -RVP

Re: Open master pty (/dev/ptmx) non blocking

2022-09-23 Thread RVP
not have been pulled up to -9.x) -RVP

Re: Open master pty (/dev/ptmx) non blocking

2022-09-23 Thread RVP
e new file descriptor. The posix_openpt() function shall fail when oflag contains other values. So, O_NONBLOCK is, at least, _definitely_ non-portable. Best to use fcntl() here and not depend on a Linux-specific behaviour. -RVP

Re: framebuffer refresh rate and geometry

2022-04-12 Thread RVP
have the time, but, somebody who _knows_ this stuff would obviously make quicker progress. -RVP

Re: framebuffer refresh rate and geometry

2022-04-12 Thread RVP
is the only way DRM runs properly on my HW. -RVP

Re: framebuffer refresh rate and geometry

2022-04-11 Thread RVP
On Mon, 11 Apr 2022, Paul Goyette wrote: On Mon, 11 Apr 2022, RVP wrote: On Mon, 11 Apr 2022, Michael van Elst wrote: N.B. if the display driver provides EDID data to wscons it can be queried with wsconsctl -d edid newdrm seems to have lost this ability (since, at least, Oct '21

Re: framebuffer refresh rate and geometry

2022-04-11 Thread RVP
IGPU). -RVP

Re: valgrind

2022-03-22 Thread RVP
On Tue, 22 Mar 2022, Joerg Sonnenberger wrote: Am Mon, Mar 21, 2022 at 11:09:41PM + schrieb RVP: Sanitizers are OK, but, they don't seem to work in some cases: Neither case is a memory leak. They are both reachable memory allocations. Yah: Reachable is what valgrind reports too

re: valgrind

2022-03-21 Thread RVP
oid) { char* p = mkbuf(1000); memset(p, '\0', 1000); return 0; } $ clang -Wall -g -fsanitize=address -o 2 static_alloc.c $ env ASAN_OPTIONS=detect_leaks=1 ./2 $ --- Valgrind, of course, detects both those leaks. -RVP PS. Mouse's email server will, as usual, reject mails sent from SD

Re: procfs files vs symlink

2022-01-16 Thread RVP
to address the earlier issue, though you didn't actually say that. No problem. I honestly was going to leave it at DT_UNKNOWN (until the weekend), but then, your post goaded me into fixing it properly pronto :) -RVP

Re: procfs files vs symlink

2022-01-14 Thread RVP
: exe is a link:procfs_readlink(); emul is a reg. file:procfs_doemul(): { DT_LNK, N("emul"),PFSemul,NULL }, { DT_REG, N("exe"), PFSexe, procfs_validfile }, $ ls -l /proc/self/emul /proc/self/exe -r--r--r-- 1 rvp rvp6 Jan 14 20:23 /pro

Re: procfs files vs symlink

2022-01-13 Thread RVP
case DTYPE_PIPE:return DT_FIFO; + case DTYPE_SOCKET: return DT_SOCK; + case DTYPE_KQUEUE: /*FALLTHROUGH*/ + case DTYPE_MISC:/*FALLTHROUGH*/ + case DTYPE_SEM: return DT_LNK; /* symlinks */ + default:return DT_UNKNOWN; + } +} + /* * convert decimal ascii to int */ ---END--- Thx, -RVP

Re: procfs files vs symlink

2022-01-13 Thread RVP
() if dirent.d_type is DT_UNKNOWN; otherwise, take dirent.d_type as valid and save a syscall.) A note in dirent.3 that procfs (and some others?) will always return DT_UNKNOWN would be a good idea, I think. Thanks, -RVP

Re: procfs files vs symlink

2022-01-12 Thread RVP
y, being cached by ls(1). 1954 1954 ls CALL close(4) passwd db now opened at 4 which now is a regular file. 1954 1954 ls CALL open(0x7d92705b0006,0x40,0) 1954 1954 ls NAMI "/etc/pwd.db" 1954 1954 ls RET open 4 Now ls(1) does the listing:

Re: block/dk devices and lseek()

2021-12-04 Thread RVP
able, then I can simplify the patch in PR# 56530. Thanks again, -RVP

block/dk devices and lseek()

2021-11-30 Thread RVP
# $ sudo ./a.out /dev/rdk0 0 $ sudo ./a.out /dev/dk0 0 Thx, -RVP

Re: wsvt25 backspace key should match terminfo definition

2021-11-24 Thread RVP
' and also a new `erase2=^H' like FreeBSD does? It seemed extravagant to have 2 erase chars. when I first encountered it, but, now I'm beginning to see why... -RVP

Re: wsvt25 backspace key should match terminfo definition

2021-11-23 Thread RVP
On Tue, 23 Nov 2021, Michael van Elst wrote: r...@sdf.org (RVP) writes: The kernel currently defines the backspace key as: $ fgrep CERASE /usr/include/sys/ttydefaults.h #define CERASE 0177 There is no 'defined as', in particular with emulated terminals that aren't even the same

Re: wsvt25 backspace key should match terminfo definition

2021-11-22 Thread RVP
definitions (and the FreeBSD console) go for ^H. -RVP

wsvt25 backspace key should match terminfo definition

2021-11-22 Thread RVP
/terminfo/w/wsvt25 wsvt25|NetBSD wscons in 25 line DEC VT220 mode, [...] kbs=^H $ Thanks, -RVP

Re: if_ethersubr.c: if_ierrors -> if_iqdrops?

2021-11-22 Thread RVP
? 0x0008 = 0x0800 # ETHERTYPE_IP 0x0006 = 0x0600 # ETHERTYPE_NS I'll test it when I get back. Thx, -RVP

Re: kaveri_mec2.bin file missing

2021-11-20 Thread RVP
rence to kaveri_mec2.bin? You could copy that file over from a Linux distro. On Ubuntu 19.04: $ ls -l /lib/firmware/radeon/kaveri_mec* -rw-r--r-- 1 rvp rvp 17024 12 Jul 2019 /media/lib/firmware/radeon/kaveri_mec.bin -rw-r--r-- 1 rvp rvp 17024 12 Jul 2019 /media/lib/firmware/radeon/kaveri_mec2.bin $ -RVP

Re: if_ethersubr.c: if_ierrors -> if_iqdrops?

2021-11-11 Thread RVP
hat. The alc driver isn't reporting any received error counts at any rate. Thanks, -RVP

Re: if_ethersubr.c: if_ierrors -> if_iqdrops?

2021-11-08 Thread RVP
On Mon, 8 Nov 2021, Jason Thorpe wrote: On Nov 7, 2021, at 11:07 PM, RVP wrote: So, I hacked up a small patch to put most of these into the "if_iqdrops" bucket. The rest (following FreeBSD) remain as errors. LGTM! On Mon, 8 Nov 2021, Christos Zoulas wrote: As far as I'm conc

if_ethersubr.c: if_ierrors -> if_iqdrops?

2021-11-07 Thread RVP
bytes, 2159 multicasts, 192 queue drops output: 25821 packets, 5636368 bytes, 37 multicasts inet6 fe80::5246:5dff:fe32:6754%alc0/64 flags 0 scopeid 0x1 inet 192.168.68.121/24 broadcast 192.168.68.255 flags 0 $ whereas, before, all those would've been errors instead. Tha

Re: Where's f_audioctx set?

2021-07-13 Thread RVP
() in audio.c: 1. fills audio_file_t *af; 2. calls fd_allocfile(, ); 3. does fd_clone() with `af' as last param; 4. fd_clone() does fp->f_data = af; 5. f_data is just f_undata.fd_data And, since f_undata is a union, step 4 sets fd_audioctx. -RVP

Re: Kernel 9.1 panic with azalia

2021-06-25 Thread RVP
On Fri, 25 Jun 2021, tlaro...@polynum.com wrote: But if azalia is not supported anymore because it crashes the kernel, shouldn't it be removed and not simply be commented out? I think that your message is the first indication that azalia(4) is slowly bit-rotting... -RVP

Re: Kernel 9.1 panic with azalia

2021-06-25 Thread RVP
has the `azalia' driver commented out; hdaudio(4) is used instead. Try the same. -RVP

Re: Kernel 9.1 panic with azalia

2021-06-25 Thread RVP
On Fri, 25 Jun 2021, RVP wrote: On Fri, 25 Jun 2021, tlaro...@polynum.com wrote: But if azalia is not supported anymore because it crashes the kernel, shouldn't it be removed and not simply be commented out? I think that your message is the first indication that azalia(4) is slowly bit

Re: maximum limit of files open with O_EXLOCK

2021-06-19 Thread RVP
On Sat, 19 Jun 2021, nia wrote: No, the error is ENOMEM ("Cannot allocate memory"), not EMFILE ("Too many open files"). That would be too easy. You're running the program as root, where the limit on locks doesn't apply. Oops, so it is--my mistake. -RVP

Re: maximum limit of files open with O_EXLOCK

2021-06-19 Thread RVP
in 9.99.82 NetBSD 9.99.82 (GENERIC) #0: Sat May 8 19:36:28 UTC 2021 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 -RVP

Re: one remaining mystery about the FreeBSD domU failure on NetBSD XEN3_DOM0

2021-04-11 Thread RVP
** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2 files, 2 used, 124907 free (27 frags, 15610 blocks, 0.0% fragmentation) * FILE SYSTEM IS CLEAN * $ sudo mount /dev/da0p1 /media $ sudo umount /media $ -RVP

Re: one remaining mystery about the FreeBSD domU failure on NetBSD XEN3_DOM0

2021-04-11 Thread RVP
: newfs -O1 /dev/... Otherwise, you get that "Invalid quota magic number" error because newfs creates a UFSv2 FS on FreeBSD. -RVP

Re: regarding the changes to kernel entropy gathering

2021-04-07 Thread RVP
On Tue, 6 Apr 2021, RVP wrote: On Tue, 6 Apr 2021, Taylor R Campbell wrote: Why do you say that? We do incorporate many sources that are not well-studied -- every keystroke, for example, and the CPU cycle counter at the time of the keystroke, affects the output of /dev/urandom

Re: regarding the changes to kernel entropy gathering

2021-04-06 Thread RVP
oscillators. -RVP

Re: regarding the changes to kernel entropy gathering

2021-04-04 Thread RVP
kern.entropy.use_pooh_poohed_sources=1 would not be a bad thing for some users--with all appropriate sysinst warnings of course. Or, perhaps statistical tests of the raw in-kernel sources will demonstrate exactly why things like timing jitter have been pooh-poohed in the literature? -RVP PS

Re: regarding the changes to kernel entropy gathering

2021-04-04 Thread RVP
on RDRAND/RDSEED-based and estimator-based as in your patch) would be useful here. Binary packages already have the dieharder RNG tester. Then, there is John Walker's ent for PRNGs: https://fourmilab.ch/random/ NIST has some too, I believe (I can't locate them right now). -RVP PS. Is there a way

Re: nothing contributing entropy in Xen domUs? or dom0!!!

2021-04-01 Thread RVP
has RDSEED/RDRAND. -RVP

Re: nothing contributing entropy in Xen domUs? or dom0!!!

2021-04-01 Thread RVP
[0-9.][0-9.]*\)') != 9.1 ] thensudo sysctl -w kern.entropy.consolidate=1 fi $ Hope that helps. -RVP PS. Generate an API key here: https://fourmilab.ch/hotbits/

Re: X vs serial console?

2021-02-11 Thread RVP
-RVP

Re: X vs serial console?

2021-02-10 Thread RVP
On Tue, 9 Feb 2021, RVP wrote: Yes. Mouse, can post the output of this: $ ls -l $(which Xorg) If the Xorg server is setuid, then you can tell it to open /dev/ttyE4 directly by adding a `vt5' to the xinit command: #! /bin/sh exec xinit /home/mouse/X/x-client -- /usr/X11R7/bin/X vt5

Re: X vs serial console?

2021-02-09 Thread RVP
On Tue, 9 Feb 2021, David Brownlee wrote: AFAIK X requires a wsdisplay to run on - which you don't seem to get with a serial console. I wonder if it might be possible to run it on genfb? Yes. Mouse, can post the output of this: $ ls -l $(which Xorg) -RVP

Re: Issues with intelfb(4) and USB keyboards

2020-12-23 Thread RVP
On Tue, 22 Dec 2020, Brian Buhrow wrote: hello. My apologies for such a naive question, but what driver should I use for the keyboard? The default, as created by X -configure, is "kbd" "kbd" is correct. There is no wskbd_drv.so in /usr/X11R7/lib/modules/drivers/ Actually, there should be no

Re: Issues with intelfb(4) and USB keyboards

2020-12-23 Thread RVP
-existent DP1 output. It has only 3 physical outputs: LVDS, VGA, HDMI. -RVP

Re: Issues with intelfb(4) and USB keyboards

2020-12-22 Thread RVP
On Tue, 22 Dec 2020, Brian Buhrow wrote: While I don't remember the exact numbers for this monitor, they look reasonable and, there is a dotclock value in there. Forgot to mention this: You can use cvt(1) or gtf(1) to generate modelines. -RVP

Re: Issues with intelfb(4) and USB keyboards

2020-12-22 Thread RVP
to read the EDID. Run a compositor if you have visual glitches: https://wiki.netbsd.org/laptops/ 3. Output of this command: $ sysctl machdep.dmi 4. Compile a new GENERIC kernel with `.load_detect_test = 1' (file: /usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_params.c) -RVP

Wrong test in vcons_invalidate_cache() in sys/dev/wscons/wsdisplay_vcons.c

2020-12-22 Thread RVP
This looks wrong: for (i = 0; i > vd->cells; i++) { Surely it is meant to be: `i < vd->cells' -RVP

Re: Issues with intelfb(4) and USB keyboards

2020-12-22 Thread RVP
) < 0) err(rc, "%s: open failed", dev); if (ioctl(fd, WSDISPLAYIO_GET_EDID, ) < 0) err(rc, "ioctl(WSDISPLAYIO_GET_EDID) failed"); fprintf(stderr, "%s EDID data_size = %u\n", dev, ei.data_size); fwrite(ebuf, 1, ei.data_size, stdout); rc = EXIT_SUCCESS; return rc; } = -RVP

Re: Issues with intelfb(4) and USB keyboards

2020-12-22 Thread RVP
://www.unitedbsd.com/d/271-wfsb/6 -RVP

Re: Issues with intelfb(4) and USB keyboards

2020-12-19 Thread RVP
8.0 and 9.1) traced to cables that don't connect the pins necessary to carry the EDID info. Quite true. I have an old ViewSonic LCD which sometimes sends *wrong*/no EDID data even when the (VGA) cables are OK. -RVP

Re: Issues with intelfb(4) and USB keyboards

2020-12-19 Thread RVP
e X driver which runs on top of `genfb'. Disable i915drmkms using the userconf facility: https://mail-index.netbsd.org/tech-x11/2020/12/10/msg002183.html -RVP

Re: Issues with intelfb(4) and USB keyboards

2020-12-19 Thread RVP
On Sat, 19 Dec 2020, RVP wrote: [ 7.124810] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/i915_drv.c:636)i915_firmware_load_error_print] *ERROR* failed to load firmware i915/skl_dmc_ver1.bin (0) [ 7.124810] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915

Re: Issues with intelfb(4) and USB keyboards

2020-12-19 Thread RVP
tem into it. Create symbolic links, if needed, from what the kernel expects (see above) to the latest `skl_*' (Skylake) versions of the same files. -RVP