Re: 14.0-CURRENT boots fine but keyboard does not work

El día martes, septiembre 05, 2023 a las 03:24:30p. m. -0600, Warner Losh escribió: > On Tue, Sep 5, 2023 at 2:22 PM Steve Kargl > wrote: > > > On Tue, Sep 05, 2023 at 01:29:34PM -0600, Warner Losh wrote: > > > +/* > > > + * Some Chromebooks don't confirm to the google comment above so

Re: 14.0-CURRENT boots fine but keyboard does not work

On Tue, Sep 5, 2023 at 2:22 PM Steve Kargl wrote: > On Tue, Sep 05, 2023 at 01:29:34PM -0600, Warner Losh wrote: > > +/* > > + * Some Chromebooks don't confirm to the google comment above so do > the > > s/confirm/conform ? > > > > + * Chromebook workaround for all <= 2018 coreboot

Re: 14.0-CURRENT boots fine but keyboard does not work

On Tue, Sep 05, 2023 at 01:29:34PM -0600, Warner Losh wrote: > +/* > + * Some Chromebooks don't confirm to the google comment above so do the s/confirm/conform ? > + * Chromebook workaround for all <= 2018 coreboot systems that have a > + * 'blank' version. At least once Acer

Re: 14.0-CURRENT boots fine but keyboard does not work

Can you try this patch? (it's cut and paste inline, so if it fails, can you apply it by hand... it's pretty straight forward)... The reason is in the comments... Not 100% sure about using the version being all spaces, though... Nor the year 2018, honestly, but it beats having a longish list (see

Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" possible file odd result

Just FYI: For the specific machine/storage media combination used for the openzfs import testing, the following combination seemed to work well relative to the subject of the "odd result": A) /etc/sysctl.conf having "vfs.zfs.per_txg_dirty_frees_percent=30" B) autotrim off but use of "zpool trim

Re: 14.0-CURRENT boots fine but keyboard does not work

El día martes, septiembre 05, 2023 a las 11:07:07a. m. -0600, Warner Losh escribió: > > https://cgit.freebsd.org/src/commit/?id=319d2bf407b3762da6f1c67ffe8dce2fee587aaf > > > > > > > > You could try to undo that patch and build a new kernel. > > > > > > > ... > > No. Let's see if I can puzzle

Re: Possible regression in main causing poor performance

In message , Mark Millard write s: > On Sep 5, 2023, at 08:58, Cy Schubert wrote: > > > In message <20230830204406.24fd...@slippy.cwsent.com>, Cy Schubert = > writes: > >> In message <20230830184426.gm1...@freebsd.org>, Glen Barber writes: > >>>=20 > >>>=20 > >>> On Mon, Aug 28, 2023 at

Re: Possible regression in main causing poor performance

On Sep 5, 2023, at 08:58, Cy Schubert wrote: > In message <20230830204406.24fd...@slippy.cwsent.com>, Cy Schubert writes: >> In message <20230830184426.gm1...@freebsd.org>, Glen Barber writes: >>> >>> >>> On Mon, Aug 28, 2023 at 06:06:09PM -0700, Mark Millard wrote: Has any more been

Re: 14.0-CURRENT boots fine but keyboard does not work

On Tue, Sep 5, 2023 at 12:13 AM Matthias Apitz wrote: > El día lunes, septiembre 04, 2023 a las 12:10:56p. m. -0600, Warner Losh > escribió: > > > On Mon, Sep 4, 2023, 11:40 AM Michael Gmelin wrote: > > > > > This could also be related: > > > > > > > > > >

Re: FYI: ^T use during poudriere bulk vs. /bin/sh operation: I got a "Unsafe ckmalloc() call" Abort trap that left a mess

On Mon, Sep 04, 2023 at 05:16:56PM -0700, Mark Millard wrote: > During a (zfs based) poudriere bulk -a run a ^T got a: > Unsafe ckmalloc() call > Abort trap (core dumped) > My attribution to ^T handling is unverified: I did not find the > sh.core file. It is just what the timing looked like.

Re: Possible issue with linux xattr support?

On Tue, Sep 05, 2023 at 07:52:52AM +0200, Felix Palmen wrote: > * Dmitry Chagin [20230904 21:49]: > > On Mon, Sep 04, 2023 at 08:43:02PM +0200, Felix Palmen wrote: > > > I guess I'll now do a full rebuild of my linuxulator userspace branch on > > > a kernel with that patch, just to be sure it

Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" possible file odd result

On Sep 5, 2023, at 00:00, Mark Millard wrote: > On Sep 4, 2023, at 22:06, Mark Millard wrote: > >> . . . > > So I tried 30 for per_txg_dirty_frees_percent for 2 contexts: > autotrim on > vs. > autotrim off > > where there was 100 GiByte+ to delete after a poudriere > bulk run. > > autotrim

Re: Possible issue with linux xattr support?

On Tue, Sep 05, 2023 at 07:52:52AM +0200, Felix Palmen wrote: > * Dmitry Chagin [20230904 21:49]: > > On Mon, Sep 04, 2023 at 08:43:02PM +0200, Felix Palmen wrote: > > > I guess I'll now do a full rebuild of my linuxulator userspace branch on > > > a kernel with that patch, just to be sure it

Re: Stray characters in command history

i'm experiencing kind of similar issue. unsure why or how. i have 13.2. console is sc. the other side, via serial, is running current. uart is from usb serial adapter. other side has native soc uart. when i establish connection to that thing with cu, which is embedded board btw, and log in, i get

Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned

On Sep 4, 2023, at 22:06, Mark Millard wrote: > On Sep 4, 2023, at 18:39, Mark Millard wrote: > >> On Sep 4, 2023, at 10:05, Alexander Motin wrote: >> >>> On 04.09.2023 11:45, Mark Millard wrote: On Sep 4, 2023, at 06:09, Alexander Motin wrote: > per_txg_dirty_frees_percent is

Re: 14.0-CURRENT boots fine but keyboard does not work

El día lunes, septiembre 04, 2023 a las 12:10:56p. m. -0600, Warner Losh escribió: > On Mon, Sep 4, 2023, 11:40 AM Michael Gmelin wrote: > > > This could also be related: > > > > > > https://cgit.freebsd.org/src/commit/?id=319d2bf407b3762da6f1c67ffe8dce2fee587aaf > > > > You could try to undo