daily CVS update output

2024-03-20 Thread NetBSD source update
Updating src tree: U src/crypto/external/bsd/openssl/lib/libcrypto/crypto.expsym P src/distrib/amd64/ramdisks/common/Makefile.ramdisk P src/distrib/i386/ramdisks/common/Makefile.ramdisk P src/distrib/sets/lists/debug/module.md.amd64 P src/distrib/sets/lists/debug/module.md.i386 P

Re: glitches in framebuffer console - NL/CR

2024-03-20 Thread Robert Elz
Date:Wed, 20 Mar 2024 20:37:09 +0100 From:Riccardo Mottola Message-ID: | Certain programs however print out the text by making only a NL and no | CR, All programs (well, almost all) do that. Normally the tty driver adds a \r after (or before) each \n on

Re: gdb crashes on current

2024-03-20 Thread Patrick Welche
On Wed, Mar 20, 2024 at 11:33:30PM +0500, Vitaly Shevtsov wrote: > Hello! > > It seems that gdb from base NetBSD image doesn't work with netbsd's > libcurses in tui mode: > > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x756547929fba in _lwp_kill () from

Re: glitches in framebuffer console - NL/CR

2024-03-20 Thread Valery Ushakov
On Wed, Mar 20, 2024 at 20:37:09 +0100, Riccardo Mottola wrote: > Boot, dmesg, login come up fine, no issue. > > Certain programs however print out the text by making only a NL and no > CR, making a staircase effect. > E.g. pkgin or dhcpcd do that. > Sometimes in this situation also keyboard

Re: gdb crashes on current

2024-03-20 Thread Rhialto
On Thu 21 Mar 2024 at 00:29:40 +0500, Vitaly Shevtsov wrote: > Hello! > > It's when you run it with the `-tui` option - text user interface. > Also you can toggle it with C-x C-a or with "tui enable" and "tui disable", too... It can be kind of nice, when it works. -Olaf. -- ___ Olaf 'Rhialto'

Re: gdb crashes on current

2024-03-20 Thread Vitaly Shevtsov
cli is the main mode in gdb but it also has a built-in pseudo graphic mode :) On Thu, Mar 21, 2024 at 12:48 AM Justin Parrott wrote: > > The last I checked gdb it was a command line interfaced system. > > On Wed, Mar 20, 2024 at 3:47 PM Vitaly Shevtsov wrote: >> >> Sorry, what do you mean? :)

Re: gdb crashes on current

2024-03-20 Thread Vitaly Shevtsov
Sorry, what do you mean? :) It's native pseudo graphic interface On Thu, Mar 21, 2024 at 12:34 AM Justin Parrott wrote: > > Is that not the Default? > > On Wed, Mar 20, 2024 at 3:30 PM Vitaly Shevtsov wrote: >> >> Hello! >> >> It's when you run it with the `-tui` option - text user interface.

glitches in framebuffer console - NL/CR

2024-03-20 Thread Riccardo Mottola
Hi, I noticed that the first console (the standard one) in case of framebuffer enabled cards has strange issues. I noticed this on 9.3 as well as on 10RC on different systems and AMD vs. Intel video card I report it on this ML because t Boot, dmesg, login come up fine, no issue. Certain

Re: gdb crashes on current

2024-03-20 Thread Vitaly Shevtsov
Hello! It's when you run it with the `-tui` option - text user interface. Also you can toggle it with C-x C-a https://sourceware.org/gdb/current/onlinedocs/gdb.html/TUI.html On Thu, Mar 21, 2024 at 12:21 AM Justin Parrott wrote: > > What is TUI mode? > > On Wed, Mar 20, 2024 at 2:34 PM Vitaly

Automated report: NetBSD-current/i386 build success

2024-03-20 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the first successful build: 2024.03.20.18.47.59 riastradh src/sys/dev/acpi/apei_hest.c 1.2 Logs can be found at:

gdb crashes on current

2024-03-20 Thread Vitaly Shevtsov
Hello! It seems that gdb from base NetBSD image doesn't work with netbsd's libcurses in tui mode: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x756547929fba in _lwp_kill () from /usr/lib/libc.so.12 [Current thread is 1 (process 12621)] (gdb) bt #0 0x756547929fba in

Automated report: NetBSD-current/i386 build failure

2024-03-20 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2024.03.20.17.11.44. An extract from the build.sh output follows: # link fujhk/fujhk.kmod

live-USB on SanDisk Cruzer Glide (was: Re: USB hubs/controllers detached before umass devices)

2024-03-20 Thread John D. Baker
On Sat, 16 Mar 2024, John D. Baker wrote: > On Sat, 16 Mar 2024, John D. Baker wrote: > > > The only difference is that the USB devices with netbsd-10 are > > branded SanDisk and the ones with -current are branded PNY. I've just completed a dump/restore to swap the i386 live images so that

Re: Strange sensor names for amdzentemp(4)

2024-03-20 Thread Paul Goyette
On Wed, 20 Mar 2024, J. Hannken-Illjes wrote: # envstat -d amdzentemp0 Current CritMax WarnMax WarnMin CritMin Unit cpu0 temperature:55.125 degC cpu0 ccd0 temperature:36.375 degC

Re: Strange sensor names for amdzentemp(4)

2024-03-20 Thread J. Hannken-Illjes
> On Mar 20, 2024, at 4:27 PM, Paul Goyette wrote: > > Oddly, I am seeing the following sensor info. Note that the config > doesn't even contain ``ccd''. (Previous incarnations of this config > _did_ have ccd, but it's been completely removed when I changed to > use raidframe...) > > #

Strange sensor names for amdzentemp(4)

2024-03-20 Thread Paul Goyette
Oddly, I am seeing the following sensor info. Note that the config doesn't even contain ``ccd''. (Previous incarnations of this config _did_ have ccd, but it's been completely removed when I changed to use raidframe...) # envstat -d amdzentemp0 Current CritMax