On Sun, May 02, 2021 at 10:36:46AM +0200, Martin Husemann wrote:
>
> It does a posix_spawn call for:
>
> make -C test-a test-a
>
> (I tested with the "make" binary in the pkgobj dir)
No, no, it doesn't - I mixed up argv indices in gdb, it does the correct
thing
On Sun, May 02, 2021 at 10:49:20AM +0200, Martin Husemann wrote:
> On Sun, May 02, 2021 at 10:41:53AM +0200, Martin Husemann wrote:
> > On Sun, May 02, 2021 at 10:36:46AM +0200, Martin Husemann wrote:
> > >
> > > It does a posix_spawn call for:
> > >
> >
On Sun, May 02, 2021 at 10:41:53AM +0200, Martin Husemann wrote:
> On Sun, May 02, 2021 at 10:36:46AM +0200, Martin Husemann wrote:
> >
> > It does a posix_spawn call for:
> >
> > make -C test-a test-a
> >
> > (I tested with the "make" bina
On Sat, Apr 24, 2021 at 03:19:16PM +, nia wrote:
> Thank you! This works great, I'll make note of it in the NetBSD Guide's
> section
> on networking.
Another option (as rjs hinted) is to only have a vether0.ifconfig (I did
that with bridge0.ifconfig for other setups) and use ! lines to do
On Fri, Mar 26, 2021 at 06:52:04PM +0100, Hauke Fath wrote:
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x74e0e8667866 in iconv () from /lib/libc.so.12
> (gdb) bt
> #0 0x74e0e8667866 in iconv () from /lib/libc.so.12
What are your locale settings?
Martin
On Tue, Apr 06, 2021 at 03:12:45PM -0700, Greg A. Woods wrote:
> > Isn't it as simple as:
> >
> > dd bs=32 if=/dev/urandom of=/dev/random
>
> No, that still leaves the question of _when_ to run it. (And, at least
> at the moment, where to put it. /etc/rc.local?)
Of course not!
You run it
On Tue, Apr 06, 2021 at 06:24:38PM +, Koning, Paul wrote:
> > Isn't it as simple as:
> >
> > dd bs=32 if=/dev/urandom of=/dev/random
> >
> > ?
>
> That runs the risk of people thinking it adds entropy. I'd be more
> comfortable with this:
>
> dd bs=32 if=/dev/zero
On Sun, Apr 04, 2021 at 11:14:31AM -0700, John Nemeth wrote:
> I understand the need for good random sources, and won't argue
> it. My question is, how can we tell what random sources a system
> actually has, i.e. is there some flag that cpuctl identify shows
> when a system has
On Sun, Mar 28, 2021 at 10:37:38AM +0200, Thomas Klausner wrote:
> On Sat, Mar 27, 2021 at 08:39:15PM +, Chavdar Ivanov wrote:
> > In the light of the recent Wireguard vs. FreeBSD 13 shenanigans, what
> > is the present thinking about the in-kernel NetBSD implementation?
> >
> > I beg your
On Wed, Mar 31, 2021 at 12:12:31AM +, Taylor R Campbell wrote:
> This is false. If the VM host provided a viornd(4) device then NetBSD
> would automatically collect, and count, entropy from the host, with no
> manual intervention.
I would love to see instructions how to do this - I have not
On Tue, Apr 06, 2021 at 10:54:51AM -0700, Greg A. Woods wrote:
> Except it seems to be useless in practice without an initial seed,
Yes.
> And the stock implementation has no possibility of ever providing an
> initial seed at all on its own (unlike previous implementations, and of
> course
On Tue, Mar 02, 2021 at 11:14:01AM +0100, Riccardo Mottola wrote:
> oh... I use reboot... since 25 years or more... why not?
It will not shut down all server processes gracefully.
> If an unclean shutdown happens like a crash or powerloss?
Entropy will be restored to the last state saved on
On Mon, Mar 08, 2021 at 03:29:32PM -, Christos Zoulas wrote:
> Yes, we can turn on REG_GNU in regcomp in sed to support \s so that it behaves
> like gnused. Before it was silently ignoring the backslash.
Is this worth a sed command line switch (like -E) ?
Martin
On Wed, Apr 07, 2021 at 07:53:07AM -0400, matthew sporleder wrote:
> So on a brand new installation/first boot why isn't the clock a
> sufficiently random thing? (anymore?)
Becaus it isn't random?
> Hung and unusable systems are a big problem. Happening on the first
> boot is not a good first
On Wed, Apr 07, 2021 at 11:26:05AM -0500, John D. Baker wrote:
> Running under 'gdb' showed:
>
>
> (gdb) run -odi -v -q
> Starting program: /usr/sbin/sendmail -odi -v -q
> process 867 is executing new program: /usr/pkg/libexec/sendmail/sendmail
>
> Program received signal SIGILL, Illegal
On Wed, Apr 07, 2021 at 11:47:10AM -0500, John D. Baker wrote:
> ISTR that I tried that and simply got the SIGILL again. Maybe that
> was from a later sparcV9 instruction...
Yes, I think it probes for like three different instructions.
> In any case, while one may be able to do that in 'gdb',
On Wed, Apr 07, 2021 at 12:14:58PM -0700, Greg A. Woods wrote:
> > You run it once. Manually. And never again.
>
> Nope, sorry, that's not a good enough answer.
It is for the typical and default installs.
> It doesn't solve the
> problem of dealing with a lack of mutable storage.
When you
On Thu, Apr 08, 2021 at 02:36:07AM -0500, John D. Baker wrote:
> That is, before the pull-up of OpenSSL 1.1.1k, the "GHASH_ASM_SPARC"
> macro was conditionally defined iff "__arch64__" was also defined--
> likely an internal compiler definition.
>
> With -current and netbsd-9 after the pull up,
On Sat, Apr 10, 2021 at 08:38:39AM +1000, matthew green wrote:
> for a quick fix, this is OK, but long term, these are built
> for sparc64 compat32 as well, and benefit from having this
> code in place.
I have seen that (and the previous modes.inc conditionalizing it), but I
do not understand how
On Sat, Apr 10, 2021 at 04:12:55PM +1000, matthew green wrote:
> Martin Husemann writes:
> > On Sat, Apr 10, 2021 at 08:38:39AM +1000, matthew green wrote:
> > > for a quick fix, this is OK, but long term, these are built
> > > for sparc64 compat32 as well, and benefit
On Tue, Apr 20, 2021 at 10:09:47AM -0400, Jan Schaumann wrote:
> That's unfortunately not very revealing, as it merely
> shows the neighbor solicitations and router advertisements:
>
> IP6 fe80::7e12:b688:167c:785f > fe80::caa:49ff:feaf:1815: ICMP6, neighbor
> solicitation, who has
On Tue, Apr 20, 2021 at 10:30:23AM -0400, Jan Schaumann wrote:
> RTM_MISS: Lookup failed on this address: len 200, pid 0, seq 0, errno 0,
> flags: 0x40
> locks: 0 inits: 0
> sockaddrs: 0x43
> fe80::caa:49ff:feaf:1815%xennet0 link#1
> 2600:1f18:400c:b800:bc3c:63cc:7e5d:1f96
This must be
On Sun, Apr 18, 2021 at 05:44:36PM +0200, Johnny Billquist wrote:
> On 2021-04-18 17:42, Martin Husemann wrote:
> > On Sun, Apr 18, 2021 at 03:09:17PM +0200, Johnny Billquist wrote:
> > > Basically, the problem is that HAVE_GCC is there set to 8,
> >
> > Where a
On Sun, Apr 18, 2021 at 05:46:39PM +0200, Johnny Billquist wrote:
> I said in my original mail:
>
> "Building from NetBSD-8 does not work. Unsure if this is a known
> limitation."
>
> So, not building from current, but am trying to build current.
Yes, but you are overriding HAVE_GCC somehow.
On Sun, Apr 18, 2021 at 03:09:17PM +0200, Johnny Billquist wrote:
> Basically, the problem is that HAVE_GCC is there set to 8,
Where and why? This should not happen - HAVE_GCC for -current is either 9
or 10, no matter on what host / which tools you compile with.
Martin
On Sun, Apr 11, 2021 at 10:37:21AM +1000, matthew green wrote:
> > How can you invoke a make to test this (besides a full build.sh and adding
> > some output to the makefiles)?
> > Or: can you just fix and request pullup ;-)
> > I can run sparc tests (quickly) again.
>
> cd src/compat
>
On Thu, Apr 08, 2021 at 02:36:07AM -0500, John D. Baker wrote:
> -# if defined(__arch64__)
> -# define GHASH_ASM_SPARC
> -# define GCM_FUNCREF_4BIT
> +# define GHASH_ASM_SPARC
> +# define GCM_FUNCREF_4BIT
> extern unsigned int OPENSSL_sparcv9cap_P[];
> void gcm_init_vis3(u128 Htable[16],
On Wed, Apr 07, 2021 at 07:05:12AM -0400, matthew sporleder wrote:
> Is the issue gaw saw exclusive to xen first boots? Are there other
> ways to end up in his situation?
It happens on all new installations for machines with no RNG, which is
the far majority of everything but "newish" amd64 and
On Thu, Apr 15, 2021 at 01:39:23PM -0700, Brian Buhrow wrote:
> hello. I just got two panics on a system running NetBSD-9.99.77/amd64.
> Unfortunately, I
> didn't have enough swap configured to capture a dump file. However, I did
> figure out that the
> problem is in thread 6 of the
On Wed, Aug 18, 2021 at 08:43:03AM +, Thomas Mueller wrote:
> What is the current status of the entropy bug in NetBSD-current,
> which prevents building and installing some packages in pkgsrc?
I am not sure what "entropy bug" you are refering to.
There is an (admin) issue if you use "reboot"
On Wed, Sep 08, 2021 at 08:51:15AM +0100, Patrick Welche wrote:
> I see something similar in another context: when I shutdown, shutdown
> can stall on a system with dkX on cgdN, with
>
> detaching dkX
> detaching cgdN
> detaching dkX(same X)
> (hang)
>
> If the dice are rolled correctly, and
On Wed, Sep 08, 2021 at 07:57:35AM +0100, Alexander Nasonov wrote:
> The order doesn't have to be arbitrary, the kernel can be fixed
> to return disk names in a well-defined order.
You can do that today with a custom kernel and lots of hard wired
disk attachements (wd0 ... wdN instead of wd*),
On Tue, Aug 03, 2021 at 09:15:08AM -0600, Brook Milligan wrote:
>
>
> > On Aug 3, 2021, at 5:49 AM, Jonathan A. Kollasch
> > wrote:
> >
> > Which RTL8723 are you interested in? Judging by the man page alone,
> > they only support the PCIe RTL8723AE. There are other RTL8723
> > variants,
On Sat, Aug 07, 2021 at 09:54:40PM +, Dave Tyson wrote:
> One other issue I noted with the latter two boards is that ethernet no longer
> works - this may be related to changes to the phy support introduced in
> 2019,
> but I will only be able to confirm this by bisecting when I get a bit
On Tue, Dec 21, 2021 at 01:50:05AM +0900, Ryo ONODERA wrote:
> (snip)
> boot device: ld0
> root on dk1 dumps on dk2
> root file system type: ffs
> kern.module.path=/stand/amd64/9.99.92/modules
> kern info: [drm] Support vblank timestamp caching Rev 2 (21.10.2013).
> kern info: [drm] Driver
On Mon, Dec 27, 2021 at 06:58:34PM +0900, Ryo ONODERA wrote:
> Hi,
>
> My previous dmesg is confusing.
> Two messages are accidentally concatenated. The former message has no newline.
> They should be splitted as follows.
>
> panic: i915drmkms0: notice: DMC firmware homepage:
>
On Mon, Dec 27, 2021 at 12:34:10PM +0900, Ryo ONODERA wrote:
> "panic: i915drmkms0: notice: DMC firmware homepage:
Where would the firmware need to be?
/libdata/firmware/i915/skl_dmc_ver1_27.bin
obviously is not the right place.
Martin
On Tue, Nov 02, 2021 at 06:07:48PM -0700, Greg A. Woods wrote:
> I now see from the source that the mysterious "install" flag should only
> be set on one partition (though I'm still not quite sure exactly what
> it's supposed to mean, except that this is to be the root filesystem,
> though why it
On Sat, Oct 30, 2021 at 02:47:14PM +0100, Chavdar Ivanov wrote:
> Then I noticed there was a TESTWIFI configuration; I had to comment
> out some 8 or so lines, as either the devices were unknown or they
> could not attach to the corresponding busses; this now failed with:
I am using the
Hey folks,
I am still working on wlan enhancements and would like to get more different
chipsets localy testable in my hands.
I have a list of all our wlan drivers and the ones I have already marked
here:
https://wiki.NetBSD.org/Driver_state_matrix/
As you can see I lack most of the
On Thu, Oct 28, 2021 at 02:00:23PM +0100, Chavdar Ivanov wrote:
> > This page points to the https://wiki.netbsd.org/Wifi_renewal_on_hg/
> > page, which shows
> >
> > hg clone https://anonhg.netbsd.org/src-draft
>
> After I got it, I tried to build kernel and modules; the modules build
> failed in
On Thu, Jul 22, 2021 at 02:05:11PM +0300, Andrius V wrote:
> I will retest later today. Steps were simple: booted the latest image
> of that day from nycdn, updated NetBSD installation with all packages
> (system is located in USB media as well, had a bit older current
> system, mbr partitioned).
On Thu, Jul 22, 2021 at 10:17:23AM +0200, Reinoud Zandijk wrote:
> On Sun, Jul 18, 2021 at 10:22:50PM +0300, Andrius V wrote:
> > Today I upgraded my current setup from the latest nycdn image (amd64)
> > using sysinst (update flow) and I was surprised that netbsd kernel was
> > copied to file with
> > #0 0x786f41f96a74 in strncmp () from /usr/lib/libc.so.12
> > #1 0x786f41f1fd61 in __getenvslot (name=name@entry=0x786f41fb2409
> > "NLSPATH", l_name=l_name@entry=7,
> > allocate=allocate@entry=false) at /usr/src/lib/libc/stdlib/_env.c:261
> > #2 0x786f41f1fef1 in
You need to identify what the "last lockecd" location is, something
like:
gdb netbsd.gdb # or just netbsd, if you do not have a netbsd.gdb
gdb> list *(0x80ea0a90)
(I never can remember the equivalent addr2line flags for this, probably:
addr2line -a 0x80ea0a90 -e
On Fri, Jan 14, 2022 at 10:55:48AM +, pin wrote:
> Hi,
>
> As the title says, why is this the case?
> I had an install done from an image a day or two into January 2022 and it
> included /netbsd.gdb
The debug information moved, it is now stored in an external debug file
in
On Sat, Jan 15, 2022 at 02:43:43PM +, pin wrote:
> > # gdb --eval-command="file /netbsd" --eval-command="target kvm
>
> Do you mean the debug symbols are baked into the kernel now?
No, they are in an external debug symbols file. The file name
is something like netbsd-GENERIC.debug and it
On Sat, Jan 15, 2022 at 03:54:43PM +, pin wrote:
> But, just so to clarify. The debug set is not pulled by sysinst and
> it used to be.
I think it never was unless you manually select it in the sets menu.
The debug set does not strictly add functionality, so even a "full"
install does not
On Sat, Jan 15, 2022 at 03:22:24PM +, pin wrote:
> $ cd debug/
> $ ls -la
> total 32
> drwxr-xr-x 8 root wheel 512 Jan 8 18:25 .
> drwxr-xr-x 6 root wheel 512 Jan 8 18:25 ..
> drwxr-xr-x 2 root wheel 512 Jan 8 18:25 bin
> drwxr-xr-x 4 root wheel 512 Jan 8 18:25 lib
>
The kernel lock is held too long while the graphics card is configured.
I have seen that with some Nvidia cards, where I just have not been able
to boot LOCKDEBUG kernels (example in PR 55185).
You can patch out the kernel lock spinout code (so the kernel does
not limit the KERNEL_LOCK() spin
On Wed, Feb 09, 2022 at 12:51:51PM -0800, Phil Nelson wrote:
> #3 The created partitions on the disk looked good, but the machine
> wouldn't boot. After some looking around, it appears that
> sysinst does create the MSDOS partition with the efi/boot
> directory in it, but does
On Tue, Mar 01, 2022 at 06:59:46AM -0600, Robert Nestor wrote:
> Any ideas?
When it does not find the boot device, you should get a boot prompt
like:
[ 8.8237251] boot device:
[ 8.8637251] root device:
and when you enter a "?" there, it should give you a list, like:
[ 18.6737220] use
On Mon, Feb 14, 2022 at 12:54:27PM +0100, Riccardo Mottola wrote:
> [ 10879.215507] entropy: pid 6895 (python3.9) blocking due to lack of
> entropy
[..]
> seed 0 0 ???collect, v
The last line means your system did not load entropy at boot time, maybe
becaus
On Sun, Apr 03, 2022 at 05:20:37PM +, John Klos wrote:
> [ 56496.032711] uvm_fault(0x81908580, 0xbd134d9bc000, 2) -> e
> [ 56496.032711] fatal page fault in supervisor mode
> [ 56496.032711] trap type 6 code 0x2 rip 0x80c4f634 cs 0x8 rflags
> 0x10202 cr2 0xbd134d9bcc90
This is fun:
> setenv TERM xterm+256color
> infocmp
# Reconstructed from /usr/share/misc/terminfo.cdb
xterm+256color|original xterm 256-color feature,
ccc,
colors#256, pairs#65536,
On Wed, Jan 26, 2022 at 10:56:53PM -0800, Greg A. Woods wrote:
> Well, if you have a hardware RNG, or my patches, then that'll do
> something, but otherwise it's just useless noise and misdirection.
This is not true. Once there is enough entropy gathered (or the system
has been told the
On Thu, Feb 10, 2022 at 01:02:34PM +0100, Martin Husemann wrote:
> Hmm, that used to work - but I may have broken it accidently when fixing
> a similar issue for updates recently. I'll try to reproduce it.
Yes - it was my change. Testing a fix now, thanks for noticing!
Martin
On Thu, Feb 10, 2022 at 08:05:36AM -0800, Jason Thorpe wrote:
> Honestly, I think it's probably better to disable 'spinout' by
> default and have it enabled by a sysctl / option. And possibly the
> spin time adjustable by sysctl, too.
I like that.
Martin
On Mon, Jan 10, 2022 at 10:18:02PM -, Christos Zoulas wrote:
> In article
> ,
> <6b...@6bone.informatik.uni-leipzig.de> wrote:
> >Does that help?
> >
> >Regards
> >Uwe
>
> I have the same issue and I can reproduce this on demand. I have disabled
> IPv6 on this router.
Has this been fixed?
On Sat, Apr 09, 2022 at 09:16:28AM +1200, Lloyd Parkes wrote:
> I installed NetBSD current from late March by net booting netbsd-INSTALL.gz
> on and amd64 system of mine. The net boot and disk boot were both done with
> UEFI and sysinst correctly offered to create GPT filesystems for me.
>
> Even
On Sun, Apr 10, 2022 at 03:19:33PM +1200, Lloyd Parkes wrote:
> My /usr/mdec contains only boot, bootxx_ffsv1, bootxx_ffsv2, bootxx_lfsv2,
> gptmbr.bin, mbr, mbr_bootsel, and mbr_ext.
I think I have just fixed this...
Martin
On Sun, Sep 10, 2023 at 11:59:33AM +0200, Havard Eidnes wrote:
> With the caveat that I've not verified this myself, I *think*
> this depends on how you got to where you are at the moment. If
> your current up-to-date 10.0 BETA using openssl 3 was initially
> installed in the pre-openssl3 era and
On Sun, Aug 20, 2023 at 02:07:25PM +0200, Martin Husemann wrote:
> The tricky pullups are done (thanks to everyone who helped with it), and
> package builds are going - so now it looks like we will be able to
> switch from BETA to release candidate state soonish.
>
> See
&
On Sun, Sep 10, 2023 at 11:56:16AM -, Michael van Elst wrote:
> I hope that the library changes are completed soon and that we can quickly
> rebuild 2023Q2.
AFAIK they are complete now.
Martin
On Mon, Sep 11, 2023 at 09:37:19AM +0200, Christian Groessler wrote:
> Has port-evbarm/57551 been fixed? It's not running stable on my Raspberry Pi
> 3.
Unfortunately not yet.
Martin
On Thu, Aug 24, 2023 at 09:22:13AM -0400, Greg Troxel wrote:
> I ran a build, and it was erroring out with IO errors, and restarting
> kept having errors. I suspected NFS concurrency, and reran it with
> MAKE_JOBS=1 and it seems to have gone much better.
What network adapters are involved? Does
On Wed, Sep 13, 2023 at 11:07:48PM +0200, rudolf wrote:
> FWIW, the list of DRM/KMS bugs (or the list of regressions since 9) is
> missing PR #57268.
I have just added it (to the DRM/KMS list).
Martin
On Fri, Sep 15, 2023 at 12:17:58PM +0900, Masanobu SAITOH wrote:
> I think it would be good to change the default behavior from
> panic to something others because GENERIC kernel enables HEARTBEAT.
> by default. One of idea is to print warning message at sufficient intervals.
I disagree. It is
On Fri, Oct 27, 2023 at 08:49:53AM +0200, Tobias Nygren wrote:
> The header being used from the tools build was an unexpected surprise
> but such reasons are why those ifdef guards exist. So I think it
> just just be put back the way it was. The example came from
> sys/atomic.h so it shouldn't be
On Wed, Nov 01, 2023 at 10:49:12AM +0100, Thomas Klausner wrote:
> Should we back out ad's changes until he has time to look at them?
I just did that on behalf of core.
Can you test if this solves your problem?
Martin
On Fri, Sep 29, 2023 at 09:52:42AM +, Chavdar Ivanov wrote:
> Sep 29 01:53:13 ymir /netbsd: [ 228407.9443196] panic: kernel diagnostic
> assertion "offset < map->dm_mapsize" failed: file
> "/home/sysbuild/src/sys/arch/x86/x86/bus_dma.c", line 826
> bad offset 0x0 >= 0x0
[..]
> Sep 29
On Fri, Oct 13, 2023 at 05:11:47PM +0300, Andreas Gustafsson wrote:
> Even though some of the test failures were reported as an excessive
> number of separate emails and attributed to the wrong commit, the
> failures themselves are real.
Indeed, on my real hardware tests the jumps are impressive:
On Sun, Aug 20, 2023 at 12:08:01PM +, Taylor R Campbell wrote:
> > /r0/build/current/tools/amd64/bin/mips64el--netbsd-gcc
> > --sysroot=/r0/build/current/DEST/evbmips64-el -Wl,--warn-shared-textrel
> > -pie -shared-libgcc -o t_workqueue t_workqueue.o
> >
Hey folks,
after some unusual rough days for the netbsd-10 branch last week, we now
have a state that is building fine again and all tests look as expected.
We also made great progress on the icky DRM/KMS issues and overal stability.
The tricky pullups are done (thanks to everyone who helped
On Mon, Aug 14, 2023 at 09:23:37AM +0100, Chavdar Ivanov wrote:
> Hi,
> ERROR: nbctfmerge: Input file adiantum_selftest.o was partially built
> from C sources, but no CTF data was present
Can you reproduce it after removing that .o file (or the whole kernel build
directory)?
This symptom often
On Mon, Apr 25, 2022 at 10:19:13PM +, RVP wrote:
> Intel integrated GPUs on laptops don't work in all cases in UEFI mode
> (mine does not). I think it does work (mostly--there are a couple of issues
> still remaining) in BIOS compatibility (CSM) mode.
No, the failure is unrelated to BIOS vs
On Tue, May 17, 2022 at 12:48:06PM +0300, Valery Ushakov wrote:
> Any thoughts on this? The problematic scenario is that the system is
> upgraded, new MAKEDEV is run after the upgrade to (re)create the
> devices, it creates world readabile /dev/wsfont, and then an old
> kernel is booted (which is
On Wed, Jun 29, 2022 at 10:57:55AM +0200, Thomas Klausner wrote:
> I've tried overwriting the first 100MB of the 'dp' entry in my fstab
> with zeroes in the hope of getting rid of the crashdump, but that
> didn't help either. How can I get rid of the crashdump so savecore
> doesn't try again to
On Thu, Jun 23, 2022 at 02:17:28PM -0600, Brook Milligan wrote:
> Is there a script somewhere that is being used to create the bootable
> arm issues that are available on https://nycdn.netbsd.org/pub/arm/? If
> so, where?
It is build by build.sh, e.g. this is the invocation for a recent earmv7hf
On Fri, Jun 24, 2022 at 10:41:28AM +0200, Martin Husemann wrote:
> On Thu, Jun 23, 2022 at 02:17:28PM -0600, Brook Milligan wrote:
> > Is there a script somewhere that is being used to create the bootable
> > arm issues that are available on https://nycdn.netbsd.org/pub/arm/? I
On Mon, May 02, 2022 at 04:22:56PM +0200, Martin Husemann wrote:
> After a bit more than two years after the first NetBSD 9 release
> (9.0 happened February 14, 2020) and nearly a year after the last
> (so far) netbsd-9 release (9.2 happened May 12, 2021) we are in
> the final step
On Fri, Jun 03, 2022 at 10:12:44AM +0200, Eivind Nicolay Evensen wrote:
> Hello.
>
> Is there any way to get more information to understand
> what is needed to get this Steinberg UR44 to work on
> NetBSD:
>
> [ 109,152749] uaudio0 at uhub1 port 1 configuration 1 interface 0
> [ 109,152749]
On Sat, Jun 11, 2022 at 10:56:26AM -0400, Tom Lane wrote:
> Experimenting here, it seems the only case that doesn't work is
> scp -r *to* a remote directory that doesn't exist yet. Possibly
> worthy of a PR.
Yes, it is an upstream regression when they switched the default protocol.
A NetBSD PR
On Sat, Jun 11, 2022 at 04:12:17PM +0200, Thomas Klausner wrote:
> Hi!
>
> I cannot use 'scp -r' from -current to NetBSD 8 or NetBSD 9.
scp changed to use sftp by default in a recent OpenSSH update. It seems
you can use scp -O to request the legacy protocol.
Martin
On Sat, Jun 04, 2022 at 05:16:34AM +, Thomas Mueller wrote:
> My big concern with the branch is the entropy bug, where building
> many packages from pkgsrc is stopped.
Yes, you are kinda right:
https://wiki.netbsd.org/releng/netbsd-10/
"Waiting for Randot" as open point, although
I have a minor (but strange) issue with the new X setup.
My Radeon amdgpu does not fully work yet (strange colours, some drawing
artifacts, otherwise mostly ok), so I am using vesfb and wsfb_drv
(but the same effect happens with the amdgpu driver).
I hadn't updated firefox before the X server
On Tue, Jul 26, 2022 at 03:46:14PM +0300, Valery Ushakov wrote:
> On Linux clone(2) is declared only for _GNU_SOURCE, which explains why
> linux doesn't run into the name clash. I gather we should follow
> suit, as that's what the apps expect.
Yes, that is the right thing to do here, especially
After a bit more than two years after the first NetBSD 9 release
(9.0 happened February 14, 2020) and nearly a year after the last
(so far) netbsd-9 release (9.2 happened May 12, 2021) we are in
the final steps to prepare for the next really great release:
We are planning to branch netbsd-10 in
On Sat, Aug 27, 2022 at 07:58:51PM -0700, Paul Goyette wrote:
> Looks to me like there's a string that is not null-terminated, thus
> we see garbage following the string/label (serial number?) which
> reads ``PMAPPAMP1234''
Yes, it is a bug in the ioctl code used in the sysinst installer to get
On Wed, Sep 07, 2022 at 08:37:43PM -0700, Paul Goyette wrote:
> On a positive front, the BIOS seems to now recognize the NVMe as
> having a UEFI OS. Trying to boot it takes me down some new path
> having to do with SecureBoot, and I don't have time for that now.
There is typicaly a setting in
On Sun, Oct 02, 2022 at 12:28:41AM +0200, Roland Illig wrote:
> Hi,
>
> Do any of the releng builds and tests run with MALLOC_CONF=junk:true?
No.
> If not, why isn't there such a mode, and is there an alternative memory
> allocator that can find these kinds of bugs?
Using COPTS
On Wed, Aug 03, 2022 at 11:21:40PM +, RVP wrote:
> Obviously, (most of) the checksums fail:
>
> $ printf '%s\n' *.xz | fgrep -f- SHA512 | sha1 -c
> (SHA512) base.tar.xz: FAILED
I can reproduce this and will file an admin ticket.
A good way to get more information is to use curl like this:
On Mon, Aug 01, 2022 at 03:57:19PM +0200, Thomas Klausner wrote:
> The attached diff survived a complete amd64-current build. Ok to commit?
Looks good to me.
Martin
On Mon, Aug 01, 2022 at 05:11:53PM +0200, Thomas Klausner wrote:
> I don't understand why we expose __clone() in a public header at all,
> but I understand your comments to result in the attached patch.
It is used in tests:
On Sun, Dec 25, 2022 at 07:03:31PM +0530, Mayuresh wrote:
> However the firmware shows only Ubuntu among UEFI options. Do I need to
> copy some more files so that netbsd option shows up?
IIRC you have to create a "boot option" in uefi vars and store it to
use a non-default path for most UEFI
You may need to clean the binutils objdir, as the binutils vs. binutils.old
switch happened recently.
Martin
On Fri, Dec 30, 2022 at 01:04:46PM +, Chavdar Ivanov wrote:
> Hi,
>
> I am getting again a failure in binutils.old, after having cleaned four days
> ago the entire obj:
binutils.old is the wrong directory, your build should use binutils now.
You need to clean the tools/binutils obj dir.
On Fri, Jan 13, 2023 at 02:12:49PM +0100, Riccardo Mottola wrote:
> I just upgraded to 10.99.2 via sysinst. I updated pkgsrc and started
> rolling-replace.
You need to update (at least /libexec/ld.elf_so).
Martin
On Fri, Jan 13, 2023 at 07:36:53PM +0100, Riccardo Mottola wrote:
> I don't think it updatedm today is the 13th, I'd expected today or
> yesterday.. how often does releng kick it out? I thought daily
Usually about twice a day, but currently the build is broken so "latest"
does not update.
Martin
On Fri, Jan 13, 2023 at 06:37:50PM +0100, Martin Husemann wrote:
> On Fri, Jan 13, 2023 at 07:36:53PM +0100, Riccardo Mottola wrote:
> > I don't think it updatedm today is the 13th, I'd expected today or
> > yesterday.. how often does releng kick it out? I thought daily
>
>
501 - 600 of 657 matches
Mail list logo
