On Sat, May 04, 2024 at 12:12:35AM +0300, Andrius V wrote:
> On Fri, May 3, 2024 at 3:59 PM Andrius V wrote:
> >
> > Hi,
> >
> > Today I reinstalled one of my systems (NetBSD 10) and while setting up
> > newly created user's password I received a panic. Since then system
> > always panics in the s
On Fri, Dec 08, 2023 at 06:13:42PM +0100, Manuel Bouyer wrote:
> Hello again
> I see a second rare panic running ATF tests on Xen:
> lib/libc/regex/t_exhaust (236/949): 1 test cases
> regcomp_too_big: [ 1254.5816543] panic: kernel diagnostic assertion
> "uvmexp.swpgonly > 0" failed: file "/usr
On Tue, Oct 31, 2023 at 10:17:25PM -0700, bch wrote:
> > I think we can just use SMAP_DISABLE/SMAP_ENABLE like in the standard
> > copyinstr() in sys/arch/amd64/amd64/copy.S.
>
>
> Yeah - I saw that, saw the registered function, the release notes…
>
> I followed the hint in the notes, and the ae
On Mon, Dec 05, 2022 at 11:32:38AM +0100, Matthias Petermann wrote:
> Hi Chuck,
>
> Am 22.11.22 um 07:10 schrieb Chuck Silvers:
> []
> > as you noted in your later mail, this is documented only in the fsck_ffs
> > manpage
> > since it only applies to fsck_ffs a
On Fri, Nov 18, 2022 at 09:09:22AM +0100, Matthias Petermann wrote:
> Hello Chuck, hello all
>
> I have done some tests with a current build. I did a complete
> reinstallation. I noticed a few small things that I would like to point out.
> Some of the things are probably not caused by the current
Hi folks,
On Wednesday I'll be committing the changes that I proposed a while back
that restore UFS2 backward-compatibility with previous NetBSD releases
and create a new "UFS2ea" variant of UFS2 that supports extended attributes.
The previous discussion of this issue started with this post:
http
On Tue, Jul 19, 2022 at 08:46:07AM +0200, Matthias Petermann wrote:
> Hello,
>
> On 13.07.22 12:30, Matthias Petermann wrote:
>
> > I can now confirm that reverting the patch also solved my problem. Of
> > course I first fell into the trap, because I had not considered that the
> > ZFS code is lo
On Tue, May 24, 2022 at 07:51:08AM -0400, Greg Troxel wrote:
>
> Chuck Silvers writes:
>
> > The introduction in NetBSD's implementation of UFS2 of the extended
> > attribute code from FreeBSD has introduced a compatibility problem
> > with previous releases of
On Tue, May 24, 2022 at 06:25:34AM -, Michael van Elst wrote:
> c...@chuq.com (Chuck Silvers) writes:
>
> > - fsck will take a new option "-c ea" to specify that an existing UFS2
> > file system should be converted to support extended attributes
> >
The introduction in NetBSD's implementation of UFS2 of the extended
attribute code from FreeBSD has introduced a compatibility problem
with previous releases of NetBSD. The explanation of this problem is
a bit involved and requires knowing some history, so please bear with me
as I explain.
On 200
On Mon, May 02, 2022 at 08:16:42PM +0200, Manuel Bouyer wrote:
> On Mon, May 02, 2022 at 11:13:45AM -0700, Chuck Silvers wrote:
> > it looks like the diff won't apply as-is, but I think the concept still
> > applies.
> >
> > note that there have been a LOT of chan
On Mon, May 02, 2022 at 10:12:02PM +0200, Michael van Elst wrote:
> On Sun, May 01, 2022 at 01:24:01PM -0700, Chuck Silvers wrote:
> > On Tue, Apr 05, 2022 at 02:10:36PM -, Michael van Elst wrote:
> > > I see both in almost every pbulk run.
> >
> > pleas
On Mon, May 02, 2022 at 08:16:42PM +0200, Manuel Bouyer wrote:
> On Mon, May 02, 2022 at 11:13:45AM -0700, Chuck Silvers wrote:
> > it looks like the diff won't apply as-is, but I think the concept still
> > applies.
> >
> > note that there have been a LOT of chan
On Mon, May 02, 2022 at 12:55:39PM +0200, Manuel Bouyer wrote:
> On Sun, May 01, 2022 at 01:24:01PM -0700, Chuck Silvers wrote:
> > On Tue, Apr 05, 2022 at 02:10:36PM -, Michael van Elst wrote:
> > > w...@netbsd.org (Thomas Klausner) writes:
> > > >I never saw
On Tue, Apr 05, 2022 at 02:10:36PM -, Michael van Elst wrote:
> w...@netbsd.org (Thomas Klausner) writes:
> >I never saw the cmake hang myself. I still see hangs in guile.
>
>
> I see both in almost every pbulk run.
please try this patch for the cmake variation of this hang:
http://www.net
On Wed, Dec 29, 2021 at 08:01:53PM +0100, Matthias Petermann wrote:
> Hello,
>
> On 27.12.21 06:20, Matthias Petermann wrote:
> > I did not try to move the file around as you recommended because I would
> > like to ask if there is anything I can do at this point to gather more
> > diagnostic data
On Thu, Dec 23, 2021 at 12:30:14PM +0100, Matthias Petermann wrote:
> Hello,
>
> for tracking down an FFS issue in current I would appreciate some advice.
> There is a NetBSD 9.99.92 Xen/PV VM (storage provided by file backed VND).
> The kernel is built from ~2012-11-27 CVS source. The root partit
On Sun, Aug 01, 2021 at 02:42:59PM +0100, Robert Swindells wrote:
>
> Thomas Klausner wrote:
> >I've just tried updating the .net program 'torrentzip'
> >(archivers/torrentzip) to the latest version. The current pkgsrc
> >version can be run by calling 'mono' on it (the package installs a
> >wrapp
On Sun, Jan 17, 2021 at 08:03:20PM +0200, Andreas Gustafsson wrote:
> The cause of the 1000+ new test failures has now been narrowed down to
> the following commit:
>
> 2021.01.16.23.50.49 chs src/sys/rump/librump/rumpkern/rump.c,v 1.352
> 2021.01.16.23.51.50 chs src/sys/arch/arm/arm/psc
hi Yorick,
On Sat, Nov 28, 2020 at 12:39:56AM +0200, Yorick Hardy wrote:
> May I ask if you have an opinion on this patch? I have
> not noticed any bad behaviour if it is omitted but, if I read
> the code correctly, I don't think it is correct to fall through
> for this case.
this function is ver
Hi Yorick,
On Fri, Nov 27, 2020 at 06:29:07PM +0200, Yorick Hardy wrote:
>
> I think that uvm_mremap did not keep pace with changes in uvm.
> This patch seems to fix it for me, although I have only tested
> for two days so far (I am usually able to trigger the panic by
> now ... but lets see).
Y
On Mon, Nov 09, 2020 at 11:21:56AM +1100, Paul Ripke wrote:
> On Sat, Nov 07, 2020 at 06:33:26PM +0300, Valery Ushakov wrote:
> > I've upgraded my Krups (64MB RAM, diskless) to 9.99.75 as of Nov 6 and
> > the machine is locking up at boot time in rc.d/fccache. If I disable
> > fccache in rc.conf i
On Tue, Nov 10, 2020 at 02:11:32PM +, Patrick Welche wrote:
> On Tue, Nov 10, 2020 at 05:26:26AM -0800, Chuck Silvers wrote:
> > On Tue, Nov 10, 2020 at 11:40:08AM +, Patrick Welche wrote:
> > > My 4 Nov -current/amd64 build box seems to be building slowly, with a lot
On Tue, Nov 10, 2020 at 11:40:08AM +, Patrick Welche wrote:
> My 4 Nov -current/amd64 build box seems to be building slowly, with a lot
> of "biowait", e.g. watching the RES of a cc1plus slowly crawl up to SIZE
> at around 3M per 5s.
>
> Is 10G of "Wired" normal? (32G RAM + 64G swap)
> (lots o
On Sat, Nov 07, 2020 at 06:33:26PM +0300, Valery Ushakov wrote:
> I've upgraded my Krups (64MB RAM, diskless) to 9.99.75 as of Nov 6 and
> the machine is locking up at boot time in rc.d/fccache. If I disable
> fccache in rc.conf it boots but then eventually locks up when
> makemandb is run. The m
On Tue, Oct 27, 2020 at 01:18:26PM +0100, Thomas Klausner wrote:
> I'm still running a September 17 kernel, and I see rare NFS corruption.
>
> Basically, I'm rezipping a lot of zip archives (~2TB) that are on NFS
> and four of them had blocks of 0 bytes afterwards, not much. For the
> ones I kept,
On Wed, Oct 21, 2020 at 09:26:49AM +0100, Patrick Welche wrote:
> Booted a yesterday's source amd64 kernel, and on reboot
>
> [ 17037.8583948] unmounting 0xfef63b813000 / (/dev/dk14)...
> [ 17037.8583948] forcefully unmounting / (/dev/dk14)...
> [ 17037.8783949] dk14 at wd4 (root) deleted
> [
On Wed, Oct 21, 2020 at 08:30:17PM +0900, Rin Okuyama wrote:
> On 2020/10/21 20:10, Andreas Gustafsson wrote:
> > Two days ago, the NetBSD Test Fixture wrote:
> > > This is an automatically generated notice of new failures of the
> > > NetBSD test suite.
> > >
> > > The newly failing test cases ar
On Mon, Oct 19, 2020 at 08:49:01AM +0200, Thomas Klausner wrote:
> Hi!
>
> I updated to 9.99.74/amd64 from last night to test the bugfix for the NFS
> problem in 9.99.73, started a bulk build and went to bed.
>
> In the morning the machine had hung hard, I couldn't even get into
> DDB. From the l
On Sun, Oct 11, 2020 at 11:19:16PM +0200, Thomas Klausner wrote:
> Hi!
>
> I've recently updated from 9.99.73 from Sep 17 to one of Oct 5.
>
> I've had serious file system corruption. Mostly in mercurial and
> sqlite3 databases, but also in normal files.
what platform is this on?
> Some of the
this should be fixed now.
sorry about that, the problem did not happen for me and
it took me forever to find a way that I could reproduce it.
-Chuck
On Sat, Aug 15, 2020 at 09:01:53PM +0300, Andreas Gustafsson wrote:
> Hi chs,
>
> At least i386, amd64, and sparc are all panicing on boot since t
On Thu, Jul 30, 2020 at 08:52:43AM +0100, Chavdar Ivanov wrote:
> > if you have done that and are still crashing due to corruption in your
> > root file system, then we still have another bug in the kernel somewhere.
>
> So it seems to me; the peculiarities here are that in both cases / is
> a GPT
On Thu, Jul 30, 2020 at 08:52:43AM +0100, Chavdar Ivanov wrote:
> So it seems to me; the peculiarities here are that in both cases / is
> a GPT slice and that I have 'log' as a mount option; it was suggested
> 'posix1eacls' should be used on its own.
I tried with both "posix1eacls" and "log", and
On Wed, Jul 29, 2020 at 06:13:03PM +0100, Chavdar Ivanov wrote:
> On Wed, 29 Jul 2020 at 08:33, Matthias Petermann wrote:
> >
> > Hello Chavdar,
> >
> > Am 28.07.2020 um 18:48 schrieb Chavdar Ivanov:
> > > This being a place people are trying samba4 as a DC, I got a
> > > repeatable panic on one o
On Thu, Jul 23, 2020 at 08:09:11PM -0400, Christos Zoulas wrote:
> Be very careful and use a separate partition for sysvol because Matthias
> reported
> fs corruption which I have not looked at yet.
I committed a fix for the fs corruption bug just now.
If you have tried this samba provisioning st
eventually I realized that the aiodone_queue workqueue thread was
made redundant long ago... we no longer need this mechanism to hand off
any specific iodone processing to a worker thread because these days
all iodone processing is done in a (softint) worker thread.
I just commited a patch to remov
On Thu, Feb 06, 2020 at 04:31:47PM -0800, Rob Newberry wrote:
> Hi.
>
> I spent last weekend -- and a few days this week -- tracking down a problem
> that exists in current.
> I found a workaround, but I don't know what the "proper" fix is.
> Digging through the VM layer and debugging with printf
On Mon, Dec 02, 2019 at 07:10:52PM +, Andrew Doran wrote:
> Hello,
>
> In light of the recent discussion, and having asked Jaromir his thoughts on
> the subject, we both think it's time to enable this by default, so it gets
> wider testing. Is there a good reason not to?
>
> Cheers,
> Andrew
On Sun, Jun 03, 2018 at 10:27:06PM +0300, Valery Ushakov wrote:
> # compile libctf/ctf_error.lo
> cc -pipe -O2 -DCTF_OLD_VERSIONS
> -I/home/uwe/work/netbsd/ro/src/tools/libctf/../compat
> -I/home/uwe/work/netbsd/ro/src/tools/libctf/../../external/cddl/osnet/sys
> -I/home/uwe/work/netbsd/r
On Sat, Dec 02, 2017 at 04:35:17PM +, Patrick Welche wrote:
> When trying to build pkgsrc/net/wget on -current/amd64, I see
>
> --- wget.info ---
> /tmp/pkgsrc/net/wget/work.x86_64/.tools/bin/makeinfo: Cannot vfork (Resource
> temporarily unavailable)
> --- ./wget.info ---
> /tmp/pkgsrc/net/w
On Wed, May 03, 2017 at 02:20:14AM +0200, Christian Groessler wrote:
> On 05/03/17 01:57, Sevan Janiyan wrote:
> > On 03/05/2017 00:04, Christian Groessler wrote:
> > > I guess curlwp. What's "l" for, anyway?
> > light.
> > LWP == Ligdh Weight Process
>
>
> Yes, that was already clear to me :-)
>
On Tue, Dec 23, 2014 at 04:59:07PM +0100, Havard Eidnes wrote:
> Hi,
>
> I'm running netbsd-7 code on my new Lenovo T430 laptop. I'm
> using code from November 27 at the moment, with the DRM/KMS
> kernel, and there are a few glitches:
>
> 1) Sometimes the rendering of images e.g. in a web browse
On Sun, Feb 09, 2014 at 10:52:24AM +0100, Onno van der Linden wrote:
> I wrote:
>
> > $ /emul/linux/usr/bin/uname -bagger
> > : invalid option -- 'b'
> > Try ' --help' for more information.
> >
> > That error output should have been something like
> > --> uname: invalid option -- 'b'
> > --> Try
On Mon, Jul 15, 2013 at 05:01:27PM -0400, Thor Lancelot Simon wrote:
> On Mon, Jul 15, 2013 at 01:01:51PM -0500, John D. Baker wrote:
> >
> > I discovered all this today and enabled "ukphy" to get more information
> > and perhaps make it work better. That confirmed which PHY I had. Then
> > I fl
44 matches
Mail list logo
