CVS commit: src/sys/dev/usb

2021-06-13 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Jun 13 07:51:09 UTC 2021 Modified Files: src/sys/dev/usb: uaudio.c Log Message: Don't use aprint* for non-autoconf errors. Also print status value. To generate a diff of this commit: cvs rdiff -u -r1.170 -r1.171

CVS commit: src/sys/dev/usb

2021-06-13 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Jun 13 07:51:09 UTC 2021 Modified Files: src/sys/dev/usb: uaudio.c Log Message: Don't use aprint* for non-autoconf errors. Also print status value. To generate a diff of this commit: cvs rdiff -u -r1.170 -r1.171

CVS commit: src/sys/dev/usb

2021-06-13 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Jun 13 07:49:43 UTC 2021 Modified Files: src/sys/dev/usb: uaudio.c Log Message: Don't ignore detach errors from children. To generate a diff of this commit: cvs rdiff -u -r1.169 -r1.170 src/sys/dev/usb/uaudio.c Please

CVS commit: src/sys/dev/usb

2021-06-13 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Jun 13 07:49:43 UTC 2021 Modified Files: src/sys/dev/usb: uaudio.c Log Message: Don't ignore detach errors from children. To generate a diff of this commit: cvs rdiff -u -r1.169 -r1.170 src/sys/dev/usb/uaudio.c Please

Re: 9.1 panic in ccb/iscsi

2021-06-12 Thread Michael van Elst
ci4...@gmail.com (Chavdar Ivanov) writes: >> istgt is the iSCSI server. >> The crash is about the in-kernel iscsi initiator. >The first sentence in the first message in the thread says 'I can see >some panics on a server that exports iSCSI volumes (istgt on >a CCB device' (CCB later corrected as

Re: 9.1 panic in ccb/iscsi

2021-06-12 Thread Michael van Elst
The crash is about the in-kernel iscsi initiator. -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."

Re: 9.1 panic in ccb/iscsi

2021-06-12 Thread Michael van Elst
joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes: >> If you have a version of the kernel with debug symbols, you could >> use addr2line to identify the instruction that caused the uvm_fault >> at address 0x802280cc. Without debug symbols it is not >> that easy. > I

Re: 9.1 panic in ccb/iscsi

2021-06-12 Thread Michael van Elst
joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes: > Hello, > I can see some panics on a server that exports iSCSI volumes (istgt on >a CCB device) to some workstations. dmesg always contains this kind of >backtrace : That would be on the workstation that uses the

Re: st.c update has broken dump multi-tape support

2021-06-12 Thread Michael van Elst
On Sat, Jun 12, 2021 at 11:17:14AM +0200, Frank Kardel wrote: > Hi ! > > Look pretty good so far, ... can we remove following marked lines which are > already > taken care of in ststart1 complete case? I guess so. -- Michael van Elst

Re: st.c update has broken dump multi-tape support

2021-06-11 Thread Michael van Elst
mlel...@serpens.de (Michael van Elst) writes: >I'm currently testing >http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/st.diff Works for me: DUMP: Found /dev/rdk0 on / in /etc/fstab DUMP: Date of this level 0 dump: Sat Jun 12 00:24:45 2021 DUMP: Date of last level 0 dump: the epoch

Re: st.c update has broken dump multi-tape support

2021-06-11 Thread Michael van Elst
bl...@internode.on.net (Brett Lymn) writes: >Here is the patch that makes multi-tape dumps work for me: I'm currently testing http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/st.diff It's a bit cumbersome to do multi-tape dumps if your disk has 11GB data and the tape fits 40GB uncompressed.

Re: st.c update has broken dump multi-tape support

2021-06-10 Thread Michael van Elst
in ststart1(). Greetings, -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."

Re: st.c update has broken dump multi-tape support

2021-06-10 Thread Michael van Elst
On Thu, Jun 10, 2021 at 12:02:19PM +0200, Michael van Elst wrote: > If you don't like the fake errno, the function needs to return > two values, the error value and a boolean to finish the > unqueued request. Cleaner, but more changes. E.g. (not even compile-tested): In

Re: st.c update has broken dump multi-tape support

2021-06-10 Thread Michael van Elst
o that the fake errno is replaced with end-of-file. If you don't like the fake errno, the function needs to return two values, the error value and a boolean to finish the unqueued request. Cleaner, but more changes. Greetings, -- Michael van

CVS commit: src/usr.sbin/postinstall

2021-06-06 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Mon Jun 7 05:29:22 UTC 2021 Modified Files: src/usr.sbin/postinstall: postinstall.in Log Message: Don't overwrite changed autofs config files. To generate a diff of this commit: cvs rdiff -u -r1.38 -r1.39

CVS commit: src/usr.sbin/postinstall

2021-06-06 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Mon Jun 7 05:29:22 UTC 2021 Modified Files: src/usr.sbin/postinstall: postinstall.in Log Message: Don't overwrite changed autofs config files. To generate a diff of this commit: cvs rdiff -u -r1.38 -r1.39

CVS commit: src/sys/dev

2021-06-06 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Jun 6 11:48:55 UTC 2021 Modified Files: src/sys/dev: ipmi.c Log Message: Fail open when ipmi device was found. Clear sc_envsys on failure to prevent double-free. To generate a diff of this commit: cvs rdiff -u -r1.5 -r1.6

CVS commit: src/sys/dev

2021-06-06 Thread Michael van Elst
/ipmi.c Sun Jun 6 11:48:55 2021 @@ -1,4 +1,4 @@ -/* $NetBSD: ipmi.c,v 1.5 2020/08/17 08:34:36 nonaka Exp $ */ +/* $NetBSD: ipmi.c,v 1.6 2021/06/06 11:48:55 mlelstv Exp $ */ /* * Copyright (c) 2019 Michael van Elst @@ -76,7 +76,7 @@ */ #include -__KERNEL_RCSID(0, "$NetBSD: ipmi.c,v 1.5

CVS commit: src/sys/dev/iscsi

2021-06-06 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Jun 6 10:40:14 UTC 2021 Modified Files: src/sys/dev/iscsi: iscsi_main.c Log Message: Provide missing file ops. Before a simple read() would panic the kernel. No longer fail close(). To generate a diff of this commit: cvs

CVS commit: src/sys/dev/iscsi

2021-06-06 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Jun 6 10:40:14 UTC 2021 Modified Files: src/sys/dev/iscsi: iscsi_main.c Log Message: Provide missing file ops. Before a simple read() would panic the kernel. No longer fail close(). To generate a diff of this commit: cvs

CVS commit: src/sys/dev/iscsi

2021-06-06 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Jun 6 10:39:10 UTC 2021 Modified Files: src/sys/dev/iscsi: iscsi_send.c Log Message: Schedule command timeout without connection lock being held to prevent a deadlock. To generate a diff of this commit: cvs rdiff -u

CVS commit: src/sys/dev/iscsi

2021-06-06 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Jun 6 10:39:10 UTC 2021 Modified Files: src/sys/dev/iscsi: iscsi_send.c Log Message: Schedule command timeout without connection lock being held to prevent a deadlock. To generate a diff of this commit: cvs rdiff -u

Re: dump/restore out of range inode

2021-06-05 Thread Michael van Elst
pr...@cam.ac.uk (Patrick Welche) writes: >How can gdb not see a spcl anywhere? /usr/include/protocols/dumprestore.h:#define spcl u_spcl.s_spcl spcl is just a define that got resolved by the compiler.

Re: procfs difference between NetBSD and Linux

2021-06-04 Thread Michael van Elst
mar...@duskware.de (Martin Husemann) writes: >And any software requiring a procfs mount to work correctly is not portable >(for some sense of portable). The bad behaviour is not restricted to procfs. % pwd /tmp/x % ls -l total 4 -rw-r--r-- 1 mlelstv wheel 6 Jun 4 16:20 mountpoint2 % echo

Re: procfs difference between NetBSD and Linux

2021-06-03 Thread Michael van Elst
k...@munnari.oz.au (Robert Elz) writes: >Date:Thu, 3 Jun 2021 09:12:52 - (UTC) >From:mlel...@serpens.de (Michael van Elst) >Message-ID: > | namei() return EEXIST when it works on a CREATE operation and > | crosses a mountpoint. >Could we p

Re: dump/restore out of range inode

2021-06-03 Thread Michael van Elst
pr...@cam.ac.uk (Patrick Welche) writes: > DUMP: Child 29322 returns LOB status 213 >213=0xd5 That's octal. Return status 0213 = 139 -> WCOREFLAG(==128) + signal 11. >Can this happen if the original filesystem is broken? At a distance >it just looks as though restore hasn't read a symbol table

Re: procfs difference between NetBSD and Linux

2021-06-03 Thread Michael van Elst
rhia...@falu.nl (Rhialto) writes: >On Thu 03 Jun 2021 at 09:12:52 -0000, Michael van Elst wrote: >> What happens: >>=20 >> namei() return EEXIST when it works on a CREATE operation and >> crosses a mountpoint. >>=20 >> procfs cheats in that the directory

Re: procfs difference between NetBSD and Linux

2021-06-03 Thread Michael van Elst
sim...@netbsd.org (Simon Burge) writes: >Jaromir wrote: >> > On 3/06/21 9:58 am, Mark Davies wrote: >> > > done - https://bugzilla.samba.org/show_bug.cgi?id=14727 >> > >> > And looks like they are throwing it back as a kernel bug >> > >> > https://bugzilla.samba.org/show_bug.cgi?id=14727#c3 >>

Re: Cisco USB serial console compatiblity?

2021-06-02 Thread Michael van Elst
buh...@nfbcal.org (Brian Buhrow) writes: > hello. Does anyone know what USB serial chip the Cisco USB serial > console is closest to >in our USB serial drivers list? the vendor code for the device I'm talking >about is: 0x05a6 >and the product code is: 0x0009. The umodem(4) driver is

CVS commit: src/sys/dev/dkwedge

2021-06-02 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Wed Jun 2 17:56:41 UTC 2021 Modified Files: src/sys/dev/dkwedge: dk.c Log Message: Clear sc_mode only on last close. To generate a diff of this commit: cvs rdiff -u -r1.104 -r1.105 src/sys/dev/dkwedge/dk.c Please note that

CVS commit: src/sys/dev/dkwedge

2021-06-02 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Wed Jun 2 17:56:41 UTC 2021 Modified Files: src/sys/dev/dkwedge: dk.c Log Message: Clear sc_mode only on last close. To generate a diff of this commit: cvs rdiff -u -r1.104 -r1.105 src/sys/dev/dkwedge/dk.c Please note that

CVS commit: src/sys/dev/dkwedge

2021-06-02 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Wed Jun 2 15:59:08 UTC 2021 Modified Files: src/sys/dev/dkwedge: dk.c Log Message: Copy mode of open wedges with the same parent and validate it. Remove race on mode value when closing. To generate a diff of this commit: cvs

CVS commit: src/sys/dev/dkwedge

2021-06-02 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Wed Jun 2 15:59:08 UTC 2021 Modified Files: src/sys/dev/dkwedge: dk.c Log Message: Copy mode of open wedges with the same parent and validate it. Remove race on mode value when closing. To generate a diff of this commit: cvs

Re: Devices.

2021-06-02 Thread Michael van Elst
wo...@planix.ca ("Greg A. Woods") writes: >My understanding w.r.t. the rationale FreeBSD used in deciding to remove >the block devices was that FreeBSD never really buffered/cached by >device in the first place. Also, according to PHK in his 2002 BSDCan >paper about FreeBSD's /dev, "In FreeBSD

Re: Devices.

2021-05-30 Thread Michael van Elst
mueller6...@twc.com ("Thomas Mueller") writes: >Where do I find the "enough dk* nodes" mode? Would it be in the kernel >config? I never saw it. You can run devpubd. When a wedge and thus the dk* unit attaches, it runs the 01-makedev hook that creates the device node in /dev.

Re: Devices.

2021-05-30 Thread Michael van Elst
mueller6...@twc.com ("Thomas Mueller") writes: >It's a nuisance not to be able to recognize all partitions on a >GPT-partitioned drive because not enough dk* nodes have been configured. >FreeBSD even distinguishes between USB or SCSI disks and SATA disks, and >between GPT partitions and

CVS commit: src/share/man/man8/man8.x86

2021-05-30 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 30 06:05:24 UTC 2021 Modified Files: src/share/man/man8/man8.x86: boot.8 Log Message: Add "root" command to pass a root specification. To generate a diff of this commit: cvs rdiff -u -r1.24 -r1.25

CVS commit: src/share/man/man8/man8.x86

2021-05-30 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 30 06:05:24 UTC 2021 Modified Files: src/share/man/man8/man8.x86: boot.8 Log Message: Add "root" command to pass a root specification. To generate a diff of this commit: cvs rdiff -u -r1.24 -r1.25

CVS commit: src/sys

2021-05-29 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 30 05:59:23 UTC 2021 Modified Files: src/sys/arch/i386/stand/boot: boot2.c src/sys/arch/i386/stand/efiboot: boot.c src/sys/arch/i386/stand/lib: biosdisk.c biosdisk.h exec.c src/sys/lib/libsa:

CVS commit: src/sys

2021-05-29 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 30 05:59:23 UTC 2021 Modified Files: src/sys/arch/i386/stand/boot: boot2.c src/sys/arch/i386/stand/efiboot: boot.c src/sys/arch/i386/stand/lib: biosdisk.c biosdisk.h exec.c src/sys/lib/libsa:

Re: Devices.

2021-05-29 Thread Michael van Elst
dholland-t...@netbsd.org (David Holland) writes: >This was all based on the experience of adding discard and adding the >dispatching for it as a first-class [bc]devsw op rather than an ioctl: >it was a pain because it ultimately required touching _every_ driver, >not just the ones that needed to

Re: 9.1: boot-time delay? [WORKAROUND FOUND]

2021-05-27 Thread Michael van Elst
etings, -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."

Re: 9.1: boot-time delay? [WORKAROUND FOUND]

2021-05-26 Thread Michael van Elst
mlel...@serpens.de (Michael van Elst) writes: >Either direction mstohz or hztoms should better always round up to >guarantee a minimal delay. And both should be replaced by hztous()/ustohz(). Microseconds allow a time value of ~35 minutes as 32bit signed integer, which should be a safe

Re: 9.1: boot-time delay? [WORKAROUND FOUND]

2021-05-26 Thread Michael van Elst
mo...@rodents-montreal.org (Mouse) writes: >How heavily is hztoms used? (I would expect mstohz to be used far more >heavily.) sys/dev/acpi/acpi_cpu_cstate.c: sc->sc_cstate_sleep = hztoms(acpitimer_delta(end, start)) * 1000; sys/dev/spkr_audio.c: audiobell(sc->sc_audiodev, xhz,

Re: 9.1: boot-time delay? [WORKAROUND FOUND]

2021-05-25 Thread Michael van Elst
bou...@antioche.eu.org (Manuel Bouyer) writes: >Another issue could be mstohz() called with a delay too short; >mstohz() will round it up to 1 tick. # define mstohz(ms) ((unsigned int)((ms + 0ul) * hz / 1000ul)) If mstohz() would round up to full ticks, it could actually avoid some pitfalls.

Re: Anyone using a Jabra USB Headset with -current?

2021-05-24 Thread Michael van Elst
0; } Static int Greetings, -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."

Re: Constructing a GPT disk image

2021-05-23 Thread Michael van Elst
br...@nmsu.edu (Brook Milligan) writes: >- create an empty image file by, for example, dd if=3D/dev/zero of=disk.img ... >- label image file with gpt create disk.img >- create partitions on image file: gpt add disk.image -t ffs ... >- configure vnconfig: vnconfig -c vnd0 disk.image >- find

Re: Constructing a GPT disk image

2021-05-23 Thread Michael van Elst
br...@nmsu.edu (Brook Milligan) writes: >- vnconfig seems to want a file that corresponds to a single partition, = >not a partitioned disk. vnconfig wants a file that corresponds to a partitioned disk. >Is this a correct procedure? Is it the best option? What would be = >needed to recognize

Re: Anyone using a Jabra USB Headset with -current?

2021-05-23 Thread Michael van Elst
mlel...@serpens.de (Michael van Elst) writes: >A Jabra Evolve 75 fails like yours: >uaudio0 at uhub3 port 2 configuration 1 interface 0 >uaudio0: vendor 0b0e (0x0b0e) Jabra Evolve 75 (0x2465), rev 2.00/2.32, addr 4 >uaudio0: autoconfiguration error: no usable endpoint fo

Re: Anyone using a Jabra USB Headset with -current?

2021-05-23 Thread Michael van Elst
jarle.greipsl...@norid.no (Jarle Greipsland) writes: >Excerpts from dmesg (after I plugged in the cable): >[71.345366] uaudio0 at uhub1 port 2 configuration 1 interface 0 >[71.345366] uaudio0: vendor 0b0e (0x0b0e) Jabra Evolve 65 (0x030c), rev >2.00/2.91, addr 2 >[71.355369] uaudio0:

CVS commit: src/sys/dev/dkwedge

2021-05-22 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sat May 22 13:43:50 UTC 2021 Modified Files: src/sys/dev/dkwedge: dk.c Log Message: Handle read-only parent devices. Currently this only affects xbd(4). Other disk drivers succeed opening read-only disks as read-write and only

CVS commit: src/sys/dev/dkwedge

2021-05-22 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sat May 22 13:43:50 UTC 2021 Modified Files: src/sys/dev/dkwedge: dk.c Log Message: Handle read-only parent devices. Currently this only affects xbd(4). Other disk drivers succeed opening read-only disks as read-write and only

Re: remserial and usb converters

2021-05-22 Thread Michael van Elst
jmitc...@bigjar.com (Jason Mitchell) writes: >    The remserial command is: >remserial -d -p 48310 -s "9600 sane" /dev/ttyu0 & Works fine for me, except it's ttyU0 and configuring "sane" may not be what you need. For e.g. a console, use "raw". I prefer to use conserver which adds some

CVS commit: src/sys/dev/usb

2021-05-16 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 16 09:17:23 UTC 2021 Modified Files: src/sys/dev/usb: uvideo.c Log Message: close pipe before freeing frame length array. To generate a diff of this commit: cvs rdiff -u -r1.59 -r1.60 src/sys/dev/usb/uvideo.c Please

CVS commit: src/sys/dev/usb

2021-05-16 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 16 09:17:23 UTC 2021 Modified Files: src/sys/dev/usb: uvideo.c Log Message: close pipe before freeing frame length array. To generate a diff of this commit: cvs rdiff -u -r1.59 -r1.60 src/sys/dev/usb/uvideo.c Please

CVS commit: src/sys/dev/spi

2021-05-16 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 16 08:48:20 UTC 2021 Modified Files: src/sys/dev/spi: spi.c Log Message: Protect ioctl and declare MPSAFE. To generate a diff of this commit: cvs rdiff -u -r1.17 -r1.18 src/sys/dev/spi/spi.c Please note that diffs are

CVS commit: src/sys/dev/spi

2021-05-16 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 16 08:48:20 UTC 2021 Modified Files: src/sys/dev/spi: spi.c Log Message: Protect ioctl and declare MPSAFE. To generate a diff of this commit: cvs rdiff -u -r1.17 -r1.18 src/sys/dev/spi/spi.c Please note that diffs are

CVS commit: src/sys/dev/wscons

2021-05-16 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 16 08:46:38 UTC 2021 Modified Files: src/sys/dev/wscons: wsdisplay_vcons.c Log Message: Try to guess attributes better. To generate a diff of this commit: cvs rdiff -u -r1.52 -r1.53 src/sys/dev/wscons/wsdisplay_vcons.c

CVS commit: src/sys/dev/wscons

2021-05-16 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 16 08:46:38 UTC 2021 Modified Files: src/sys/dev/wscons: wsdisplay_vcons.c Log Message: Try to guess attributes better. To generate a diff of this commit: cvs rdiff -u -r1.52 -r1.53 src/sys/dev/wscons/wsdisplay_vcons.c

CVS commit: src/sys/dev/wscons

2021-05-16 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 16 08:44:26 UTC 2021 Modified Files: src/sys/dev/wscons: wsdisplay_vcons.c Log Message: No need to check cell count. To generate a diff of this commit: cvs rdiff -u -r1.51 -r1.52 src/sys/dev/wscons/wsdisplay_vcons.c

CVS commit: src/sys/dev/wscons

2021-05-16 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun May 16 08:44:26 UTC 2021 Modified Files: src/sys/dev/wscons: wsdisplay_vcons.c Log Message: No need to check cell count. To generate a diff of this commit: cvs rdiff -u -r1.51 -r1.52 src/sys/dev/wscons/wsdisplay_vcons.c

Re: Problem reports for version control systems

2021-05-02 Thread Michael van Elst
b...@update.uu.se (Johnny Billquist) writes: >And as a "fun" fact. On my 4000/90, it takes about 3h after I start a >cvs update until I actually start having any network traffic... A SCSI SSD could help. :)

Re: xhci "device problem, disabling port 5"

2021-04-25 Thread Michael van Elst
rhia...@falu.nl (Rhialto) writes: >> sudo drvctl -r -a usbdevif uhub1 >>=20 >> should work. >It works in the sense that it doesn't give any error. But it has no >noticable effect either, unfortunately. No messages printed on the >console, visible via dmesg or /var/log/messages. It does not

Re: xhci "device problem, disabling port 5"

2021-04-25 Thread Michael van Elst
rhia...@falu.nl (Rhialto) writes: >hexander$ sudo drvctl -r uhub1 >drvctl: DRVRESCANBUS: Invalid argument A bus can have the notion of an "interface attribute" that you must pass. uhub knows about "usbifif" for network interfaces and "usbdevif" for other devices like umass. sudo drvctl -r -a

Re: GCC 10 available for testing etc. in -current.

2021-04-18 Thread Michael van Elst
ll...@must-have-coffee.gen.nz (Lloyd Parkes) writes: >On 17/04/21 6:30 pm, Lloyd Parkes wrote: >> I am using the Mercurial repository at https://anonhg.NetBSD.org/src >> for fetching the source code because it's nice and quick >I've been running CVS for more than two hours now, and it has

CVS commit: src/share/mk

2021-04-17 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sat Apr 17 09:39:33 UTC 2021 Modified Files: src/share/mk: bsd.own.mk Log Message: Use GCC10 for all amd64 including XEN kernels. To generate a diff of this commit: cvs rdiff -u -r1.1240 -r1.1241 src/share/mk/bsd.own.mk

CVS commit: src/share/mk

2021-04-17 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sat Apr 17 09:39:33 UTC 2021 Modified Files: src/share/mk: bsd.own.mk Log Message: Use GCC10 for all amd64 including XEN kernels. To generate a diff of this commit: cvs rdiff -u -r1.1240 -r1.1241 src/share/mk/bsd.own.mk

Re: Resize window size

2021-04-14 Thread Michael van Elst
On Wed, Apr 14, 2021 at 08:57:29PM +0200, Rhialto wrote: > On Wed 14 Apr 2021 at 17:38:05 +0200, Michael van Elst wrote: > > The window height calculation in add_window.c differs from those > > done in functions_win_moveresize.c and win_resize.c. Aligning > > the code

CVS commit: src/sys/compat/netbsd32

2021-04-14 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Wed Apr 14 16:26:23 UTC 2021 Modified Files: src/sys/compat/netbsd32: netbsd32_ioctl.c netbsd32_ioctl.h Log Message: Add DIOCGDISKINFO compat. To generate a diff of this commit: cvs rdiff -u -r1.118 -r1.119

CVS commit: src/sys/compat/netbsd32

2021-04-14 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Wed Apr 14 16:26:23 UTC 2021 Modified Files: src/sys/compat/netbsd32: netbsd32_ioctl.c netbsd32_ioctl.h Log Message: Add DIOCGDISKINFO compat. To generate a diff of this commit: cvs rdiff -u -r1.118 -r1.119

Resize window size

2021-04-14 Thread Michael van Elst
ect.height is only the height of the ":" string, which isn't tall enough to display arbitrary characters. I don't know if or how you accept patches, but if you think this is correct, feel free to use it. Greetings, -- Michae

Re: NetBSD 9.1 amd64 base X11: hypersensitive touchpad

2021-04-12 Thread Michael van Elst
mayur...@acm.org (Mayuresh) writes: >pms0: synaptics_probe: Not synaptics. >It's not synaptics, but in an older log that I shared Linux did treat it >as so. You could replace the pms_synaptics_probe_init() function with something that just sets the capabilities flags that you assume to be

Re: NetBSD 9.1 amd64 base X11: hypersensitive touchpad

2021-04-12 Thread Michael van Elst
mayur...@acm.org (Mayuresh) writes: >Seems so now. I have posted a link to my 2017 post where Linux was also >using synaptics for the same device and it was working fine. So worth a >try if it works even partly (+ whatever we can achieve with sysctl option >tuning). I'm not sure if that was

CVS commit: xsrc/external/mit/ctwm/dist

2021-04-12 Thread Michael van Elst
Module Name:xsrc Committed By: mlelstv Date: Mon Apr 12 06:42:31 UTC 2021 Modified Files: xsrc/external/mit/ctwm/dist: add_window.c Log Message: Reapply font calculation fix. To generate a diff of this commit: cvs rdiff -u -r1.3 -r1.4

CVS commit: xsrc/external/mit/ctwm/dist

2021-04-12 Thread Michael van Elst
Module Name:xsrc Committed By: mlelstv Date: Mon Apr 12 06:42:31 UTC 2021 Modified Files: xsrc/external/mit/ctwm/dist: add_window.c Log Message: Reapply font calculation fix. To generate a diff of this commit: cvs rdiff -u -r1.3 -r1.4

Re: NetBSD 9.1 amd64 base X11: hypersensitive touchpad

2021-04-12 Thread Michael van Elst
mayur...@acm.org (Mayuresh) writes: >On Mon, Apr 12, 2021 at 05:16:37AM -0000, Michael van Elst wrote: >> >options PMS_SYNAPTICS_TOUCHPAD # Enable support for Synaptics Touchpads >> >> It's a compile-time option for the pms driver to include code that >> handl

Re: NetBSD 9.1 amd64 base X11: hypersensitive touchpad

2021-04-11 Thread Michael van Elst
mayur...@acm.org (Mayuresh) writes: >On Sun, Apr 11, 2021 at 08:15:03PM +0200, Martin Husemann wrote: >> grep '^pms' /var/run/dmesg.boot >pms0 at pckbc2 (aux slot) >wsmouse0 at pms0 mux 0 >But the following line in the kernel config is enabled. How is it supposed >to play a role? The name

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

2021-04-11 Thread Michael van Elst
wo...@planix.ca ("Greg A. Woods") writes: >system was suffering the effects of accessing the corrupted filesystem I >was experimenting with. Note the SIGSEGV's from processes apparently >after the kernel has gone into its halt-spin loop (this is the first >time I've seen this particular

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

2021-04-11 Thread Michael van Elst
wo...@planix.ca ("Greg A. Woods") writes: >SALVAGE? [yn] ^Cada0: disk error cmd=write 8145-8152 status: fffe That seems to be a message from the disk driver: /* Operation not supported (only happens on barrier writes). */ #define BLKIF_RSP_EOPNOTSUPP -2 If I understand that correctly, a

Re: I think I've found why Xen domUs can't mount some file-backed disk images! (vnd(4) hides labels!)

2021-04-11 Thread Michael van Elst
k...@munnari.oz.au (Robert Elz) writes: >Date:Sun, 11 Apr 2021 18:14:44 - (UTC) >From:mlel...@serpens.de (Michael van Elst) >Message-ID: > | + spb = vnd->sc_geom.vng_secsize / DEV_BSIZE; >Do we know for sure here that vng_secsize >=

Re: I think I've found why Xen domUs can't mount some file-backed disk images! (vnd(4) hides labels!)

2021-04-11 Thread Michael van Elst
wo...@planix.ca ("Greg A. Woods") writes: > } else if (vnd->sc_size >= (32 * 64)) { > /* >- * Size must be at least 2048 DEV_BSIZE blocks >- * (1M) in order to use this geometry. >+ * The file's

CVS commit: src/sys/dev

2021-04-11 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Apr 11 18:18:39 UTC 2021 Modified Files: src/sys/dev: vnd.c Log Message: Provide a default preferred I/O size. To generate a diff of this commit: cvs rdiff -u -r1.279 -r1.280 src/sys/dev/vnd.c Please note that diffs are

CVS commit: src/sys/dev

2021-04-11 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Apr 11 18:18:39 UTC 2021 Modified Files: src/sys/dev: vnd.c Log Message: Provide a default preferred I/O size. To generate a diff of this commit: cvs rdiff -u -r1.279 -r1.280 src/sys/dev/vnd.c Please note that diffs are

CVS commit: src/sys/dev

2021-04-11 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Apr 11 18:17:22 UTC 2021 Modified Files: src/sys/dev: vnd.c Log Message: Don't truncate disk size to full cylinders. To generate a diff of this commit: cvs rdiff -u -r1.278 -r1.279 src/sys/dev/vnd.c Please note that diffs

CVS commit: src/sys/dev

2021-04-11 Thread Michael van Elst
Module Name:src Committed By: mlelstv Date: Sun Apr 11 18:17:22 UTC 2021 Modified Files: src/sys/dev: vnd.c Log Message: Don't truncate disk size to full cylinders. To generate a diff of this commit: cvs rdiff -u -r1.278 -r1.279 src/sys/dev/vnd.c Please note that diffs

Re: I think I've found why Xen domUs can't mount some file-backed disk images! (vnd(4) hides labels!)

2021-04-11 Thread Michael van Elst
wo...@planix.ca ("Greg A. Woods") writes: > dg->dg_secperunit = > ((vnd->sc_size * DEV_BSIZE) + DEV_BSIZE - 1) / > vnd->sc_geom.vng_secsize; @@ -2104,11 +2108,12 @@ static void vnd_set_geometry(struct vnd_softc *vnd) { struct disk_geom *dg = >sc_dkdev.dk_geom;

Re: I think I've found why Xen domUs can't mount some file-backed disk images! (vnd(4) hides labels!)

2021-04-11 Thread Michael van Elst
jaromir.dole...@gmail.com (=?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?=) writes: >Le dim. 11 avr. 2021 =C3=A0 17:51, Robert Elz a =C3=A9c= >rit : >> >> Date:Sun, 11 Apr 2021 14:25:40 - (UTC) >> From:mlel...@serpens.de (Michael van

Re: I think I've found why Xen domUs can't mount some file-backed disk images! (vnd(4) hides labels!)

2021-04-11 Thread Michael van Elst
k...@munnari.oz.au (Robert Elz) writes: >Date:Sun, 11 Apr 2021 14:25:40 - (UTC) >From:mlel...@serpens.de (Michael van Elst) >Message-ID: > | + dg->dg_secperunit = vnd->sc_size / DEV_BSIZE; >While it shouldn't make any difference for

Re: I think I've found why Xen domUs can't mount some file-backed disk images! (vnd(4) hides labels!)

2021-04-11 Thread Michael van Elst
bou...@antioche.eu.org (Manuel Bouyer) writes: >On Sun, Apr 11, 2021 at 01:28:46PM -0000, Michael van Elst wrote: >> bou...@antioche.eu.org (Manuel Bouyer) writes: >> >> >The size of the disk is indeed 790528 in the xenstore (and the dom0's >> >kernel message)

Re: I think I've found why Xen domUs can't mount some file-backed disk images! (vnd(4) hides labels!)

2021-04-11 Thread Michael van Elst
bou...@antioche.eu.org (Manuel Bouyer) writes: >The size of the disk is indeed 790528 in the xenstore (and the dom0's >kernel message) but I don't know where this comes from. >The file is definitively 791121 sectors long: vnd computes a fake geometry based on 1MB cylinders. 791121 truncated to

Re: I think I've found why Xen domUs can't mount some file-backed disk images! (vnd(4) hides labels!)

2021-04-11 Thread Michael van Elst
wo...@planix.ca ("Greg A. Woods") writes: >I'm thinking (esp. given what I see from "od -c < /dev/rvnd0d") that >what's wrong is the vnd(4) driver is (also?) imposing some >mis-interpreted idea about the number of cylinders and heads or >something like that, especially given that "fdisk vnd0" is

Re: cmake hang ... again

2021-04-06 Thread Michael van Elst
jo...@bec.de (Joerg Sonnenberger) writes: >On Tue, Apr 06, 2021 at 04:49:58PM -0000, Michael van Elst wrote: >> Otherwise I see several infinite loops, a python deadlock in the samba4 build >> and, new, the kdelibs4 build stalls for kfiltertest_automoc.cpp. >The samba4 th

Re: cmake hang ... again

2021-04-06 Thread Michael van Elst
bou...@antioche.eu.org (Manuel Bouyer) writes: >I see the same thing in bulk builds, with various kde packages. >When I asked I've been told that this was a known issue, but without fix ... There are several issues that hang builds. The cmake hang usually responds well to a SIGSTOP followed by

Re: regarding the changes to kernel entropy gathering

2021-04-05 Thread Michael van Elst
h...@netbsd.org (Havard Eidnes) writes: >I also presented a workaround for this problem; if you are reasonably >certain that you actually have mixed in a sufficient number of bits of >sufficient quality into the randomness pool (see "rndctl -l -v"), you >can do Isn't that the same as before?

Re: regarding the changes to kernel entropy gathering

2021-04-05 Thread Michael van Elst
h...@uninett.no (Havard Eidnes) writes: >Well, if I'm not mistaken, the actual implementation was tested, >not just a theoretical study of the design. And, as I said, >thermal noise is one of the well-known physical systems which >provide actual entropy. That's probably why other sources of

Re: regarding the changes to kernel entropy gathering

2021-04-05 Thread Michael van Elst
jo...@bec.de (Joerg Sonnenberger) writes: >Part of the problem here is that most of the non-RNG data sources are >easily observable either from the local system (e.g. any malicious user) >or other VMs on the same machine (in case of a hypervisor) or local >machines on the same network (in case of

Re: how do I mount a read-only filesystem from the "root device" prompt?

2021-04-05 Thread Michael van Elst
wo...@planix.ca ("Greg A. Woods") writes: >Given the layers of devices and code involved, perhaps it might be >possible to just honour the original mode requested by the code opening >the first partition to mount a filesystem, and then to upgrade the vnode >to write mode if/when that mount is

Re: how do I mount a read-only filesystem from the "root device" prompt?

2021-04-04 Thread Michael van Elst
wo...@planix.ca ("Greg A. Woods") writes: >So with Xen one can export a "disk" (disk, file, LVM partiion, etc.) >with "access=ro", and that is enforced. >However if one tries to mount such a disk in a domU as root, it fails. > root on dk1 > vfs_mountroot: can't open root device,

Re: blocklistd: How to keep my dynamic IP from getting blocked

2021-03-31 Thread Michael van Elst
mayur...@acm.org (Mayuresh) writes: >Thanks. Here the IP to whitelist is dynamic. I can arrange to put it in a >file, but it may change and the file will be modified accordingly. What's >a good way out to handle this? If you can store the whitelist in a file, you can define a file-based npf

Re: blocklistd: How to keep my dynamic IP from getting blocked

2021-03-31 Thread Michael van Elst
mayur...@acm.org (Mayuresh) writes: >Strangely autossh manages to fail auth irking blocklistd and that ends up >blocking access to all devices at home as they share the same external >dynamic IP. (Let's keep aside why autossh manages to fail auth for now.) >Alternatively does it need to be done

<    5   6   7   8   9   10   11   12   13   14   >