Date:Mon, 15 Apr 2024 12:32:22 -0600
From:Brook Milligan
Message-ID: <68be1f36-3f4e-4345-b629-96bd3f74f...@nmsu.edu>
| >> kernel page fault trap, code 0
| >> Stopped in pid 0.0 (system) at netbsd:uvm_page_redim+0x2e9: addq
$0x1,0(%?dx)
| >> uvm_page_redim() at
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 output
Date:Mon, 18 Mar 2024 20:40:57 -0700 (PDT)
From:Paul Goyette
Message-ID:
| Why do we have drvctl(8) and gpt(8) (for example only, there are
| others) which put the device-to-act-on at the end of the command:
|
| gpt [-Hnqrv] [-m mediasize] [-s sectorsize]
Date:Tue, 5 Mar 2024 10:03:35 -0800 (PST)
From:Paul Goyette
Message-ID:
| The resulting device, however, is a gpt device (with one wedge
| named ``Builds'').
Sounds normal enough.
| There is an entry for ccd0 in /etc/fstab,
How did that get there? fstab sh
Date:Mon, 4 Mar 2024 17:31:22 -0800 (PST)
From:Paul Goyette
Message-ID:
| Is there a reason that checking disks (vi fsck) happens before the ccd
| and.or cgd drivers can create their devices? It's hard to check on ccd0
| before it exists!
Really?
On my syste
Date:Sat, 27 Jan 2024 09:11:58 +0100
From:Martin Husemann
Message-ID: <20240127081158.gb16...@mail.duskware.de>
| Because the declaration in the relevant header is already there,
Now that Christos moved the function around, that declaration in the
header is just no
Date:Fri, 26 Jan 2024 21:09:30 +0100
From:Adam
Message-ID: <7be03ef0-a516-4102-951a-be8a0d468...@netbsd.org>
| Why not just change the order?
Christos has done that now, so I guess that more or less "fixes" the
issue.
I didn't want to do it that way, as it still l
Date:Fri, 26 Jan 2024 16:54:13 +0100
From:Adam
Message-ID:
| The above is a hack. IMHO my fix is a cleaner one.
The question is really why we're building libc functions (for the tools
libcompat) without _LIBC_INTERNAL defined. I think it should be.
| Anyway,
Date:Thu, 25 Jan 2024 20:12:36 +0100
From:Adam
Message-ID:
| Correct, _LIBC_INTERNAL is not defined for tools/compat.
I wonder what the difference is between your environment, and
a standard build on a NetBSD host.
| MD2Transform() must be defined for MD2Update
Date:Thu, 25 Jan 2024 09:20:50 +0100
From:Adam
Message-ID: <39200422-f15b-42c6-87c0-b23f92d13...@netbsd.org>
| > Today, the build fails while making tools:
| >
Please show me the full command line for the compile which
is producing that error (and confirm all yo
I have made some hacks which seem to have the amd64 build working again.
I an looking at i386 now, and will then try evbarm builds.
But there's no way I can build all 73 of the ports - so if you're a
builder of HEAD on the less common ports, now would be a good time to
try.
I have a kind of feeli
Date:Sat, 20 Jan 2024 10:50:27 +0100
From:Adam
Message-ID: <29d271cd-36ed-4890-ace2-fa209685b...@netbsd.org>
| NetBSD-current fails to build on aarch64.
Update to HEAD (after receiving this e-mail) and try again. I think it
is "fixed" now - but the fix is as UGLY
Date:Sat, 20 Jan 2024 11:02:36 +0100
From:Martin Husemann
Message-ID: <20240120100236.gb14...@mail.duskware.de>
| Robert fixed it in the meantime.
Not that particular one I didn't, didn't know about that particular
breakage, will look at it now.
kre
Date:Thu, 21 Dec 2023 20:26:29 +0100
From:=?ISO-8859-1?Q?Fekete_Zolt=E1n?=
Message-ID: <8bc45468-b662-4615-9c61-9981bd2b1...@minux.hu>
| Using USB would have been a good starting point from a hardware
| availability perspective.
It probably still could be, Martin
Date:Fri, 15 Dec 2023 18:51:47 +0300
From:Valery Ushakov
Message-ID:
| Can you run the status command with sh -x?
Actually run it with -X instead (the rc stuff fiddles with fd's so
much it is possible it might steal some of the -x output otherwise).
sh -X
Date:Mon, 09 Oct 2023 12:41:30 +0100
From:Roy Marples
Message-ID: <18b143e0358.f3fff8a9957587.8373038006501947...@marples.name>
I haven't read the patched (or unpatched) code, but this change makes no
sense to me:
| diff --git a/src/script.c b/src/script.c
| inde
Sorry, no, I can't test, the system looks to have died, and certainly
needs repairs, it looks as if the cooler might be dead (not sure about
the cpu at the minute, it won't even boot to the stage where the BIOS
enables the display)
However, much of what your patch does (according to your descripti
Date:Sun, 2 Jul 2023 11:43:35 +0200
From:Michael van Elst
Message-ID:
| Yes. That bit also triggers powerd.
So my current guess (and it is no more than that) would be that if
powerd happens to notice that happening, which would require it to
look at just the right
Date:Sun, 2 Jul 2023 08:11:59 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| In the end that means the chip either won't reach it's maximum turbo
| speed, or only for a shorter time, or only when cooled better. The
| value that corresponds
Date:Sat, 1 Jul 2023 13:18:50 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| To support the "turbo" speeds, you need higher voltages and it is plausible
| that the voltages need to be set for the worst case because switching the
| clock to
Date:Thu, 29 Jun 2023 20:18:31 +0200
From:Michael van Elst
Message-ID:
| Unless there is a BIAS on those numbers and the real values are maybe 15
| degrees higher.
That's exactly what they were. I added some extra debug code to
coretemp.c, to tell me what was
Date:Thu, 29 Jun 2023 20:18:31 +0200
From:Michael van Elst
Message-ID:
| Unless there is a BIAS on those numbers and the real values are maybe 15
| degrees higher.
Probably 20. That would be more realistic.
| I can also easily imagine that temperatures rise
Another reply to multiple messages in one, but starting from the last
one this time, as it is the most important I think.
Date:Thu, 29 Jun 2023 13:52:03 +0200
From:Michael van Elst
Message-ID:
| One possibility would be that the 3401 mode didn't enable turbo frequ
Date:Thu, 29 Jun 2023 12:03:33 +0200
From:Rhialto
Message-ID:
| In your cpu this may be the case too, which would give confusing results
| if you're not aware of the possibility.
It is, and I'm aware of it. I'm not sure why Michael wanted to know
whether the sp
Date:Thu, 29 Jun 2023 08:27:05 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| You could run a benchmark like 'openssl speed sha256' and compare
| the 3400 MHz target and the target and step lower.
First, my userland (that I run most of the t
Date:Thu, 29 Jun 2023 05:39:23 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| When this happens, is the machine actually running at 3400 MHz?
How do I tell? But if you mean what does machdep.cpu.frequency.current
report, then yes, that is 34
Date:Wed, 28 Jun 2023 23:46:24 + (UTC)
From:RVP
Message-ID:
| You can set a lower "critical-max" property on the CPU temps. in
| /etc/envsys.conf to make powerd trigger a shutdown at a lower temperature.
| Say, 75C?
Yex, I know, but at the minute I am not
Date:Wed, 28 Jun 2023 15:08:17 +0900
From:Masanobu SAITOH
Message-ID: <1b1763d8-f565-612c-9336-9fb71d496...@execsw.org>
| Please test the following diff:
| https://www.netbsd.org/~msaitoh/coretemp-20230628-0.dif
Done that, doesn't seem to make any difference.
I am going to reply to several messages in one reply...
But first, thanks for looking at this at all, x86 processors
have always been black magic to me.
Date:Wed, 28 Jun 2023 05:06:11 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| coretemp tem
Hi all.
I'm currently running HEAD from about June 14. My system has been
having what appear to be temperature related issues (those are not
the point of this e-mail).
As part of attempting to deal with (or diagnose) what is happening
there, I switched the CPU frequency to go slower (slower CPU
Date:Sat, 27 May 2023 20:26:06 - (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| Perhaps add a flag to the mount command to not do the realpath check?
No longer needed, hannken@ provided a fix for the tests. I didn't
consider that one as a real
Date:Fri, 26 May 2023 02:29:05 + (UTC)
From:NetBSD Test Fixture
Message-ID: <168506814541.4954.15559262820055138...@babylon5.netbsd.org>
| The newly failing test cases are:
|
| fs/nfs/t_rquotad:get_nfs_be_1_both
| fs/nfs/t_rquotad:get_nfs_be_1_grou
Date:Sat, 29 Apr 2023 20:18:13 +0100
From:Chavdar Ivanov
Message-ID:
| KDTRACE_HOOKS undefined, SDT_PROBE2 and 4 define to _nothing, the
| abovementioned variables are used in the invocations of these
| macros...
Working on it now.
kre
Date:Mon, 13 Mar 2023 19:40:18 + (UTC)
From:NetBSD Test Fixture
Message-ID: <167873641838.21770.3334724647239982...@babylon5.netbsd.org>
| This is an automatically generated notice of a NetBSD-current/i386
| build failure.
|
| The failure occurred on babyl
Note that below, the indented descriptions of what the issue is
about are just intended as a guide to allow readers of this message
to decide which Austin Group bug issues are worth looking at. They're
just my paraphrase of what it is all about, and aren't guaranteed to be
even very close to corre
POSIX has added new fcntl() locking types
F_OFD_GETLK
F_OFD_SETLK
F_OFD_SETLKW
("Open File Descriptor" locks - persist as long
as the file * remains existing for the file, then
go away).
For the details see
https://austingroupbugs.net/view.php?id=768#c6096
Omit th
Date:Sat, 7 Jan 2023 20:41:01 + (UTC)
From:NetBSD Test Fixture
Message-ID: <167312406178.23291.2878684022518773...@babylon5.netbsd.org>
| The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
| using sources from CVS date 2023.01.07.19.41.30.
Thi
Date:Sun, 8 Jan 2023 02:46:48 + (UTC)
From:NetBSD Test Fixture
Message-ID: <167314600759.7791.10321313004943192...@babylon5.netbsd.org>
| The NetBSD-current/i386 build is working again.
Note that this does not relate to the current build failure, this message
Date:Sat, 7 Jan 2023 13:41:13 +0530
From:Mayuresh
Message-ID: <20230107081113.bdzqjxuihxxszvmr@localhost>
| Now stripping off all the context and just seeking to know the difference
| between these two drivers:
|
| $ config -x | grep i915
| #i915drm*
Date:Mon, 2 Jan 2023 10:39:45 +0100
From:Martin Husemann
Message-ID: <20230102093945.gb...@mail.duskware.de>
| Note that the official daily builds also use this (and have been failing
| since new binutils have been enabled for x86).
They should be back working ag
Date:Sun, 1 Jan 2023 19:17:54 -0800 (PST)
From:Paul Goyette
Message-ID:
| FWIW, touch(1)ing all copies of bfd.info gets us past the ``build.sh
| tools'' successfully. I have seen no new issues.
I just updated to get Matt's changes (no arbitrary touching in the
Date:Mon, 02 Jan 2023 12:17:11 +1100
From:matthew green
Message-ID: <10634.1672622...@splode.eterna.com.au>
| can you update and post the latest failures?
Will do.
kre
Date:Mon, 02 Jan 2023 03:45:16 +1100
From:matthew green
Message-ID: <8109.1672591...@splode.eterna.com.au>
| it's not seen by most because it depends upon the timestamps of
| some files..
I am also having issues (with very recently updated sources).
I wonder if
Date:Fri, 09 Dec 2022 06:48:23 -0500
From:Greg Troxel
Message-ID:
| Not MESSAGE; this is not a "your hair is on fire" thing.
Probably not, but I'm not a samba user (or a user of anything which
might use samba) so the importance eludes me.
| And it's not just Ne
Date:Thu, 8 Dec 2022 20:21:26 +0100
From:Martin Husemann
Message-ID: <20221208192126.gb...@mail.duskware.de>
| Now the question: should the default install really use this new FFS type,
| or should it default to plain FFSv2?
I'd suggest FFSv2, but that's not muc
Date:Sun, 6 Nov 2022 09:54:35 -0400 (AST)
From:Jared McNeill
Message-ID:
| It's not used to discover processors by OSes because typically that is
| done well before the AML interpreter is brought online.'
Yes, the CPUs are all discovered earlier.
| The error
Date:Sat, 5 Nov 2022 11:53:33 + (UTC)
From:RVP
Message-ID:
| HID ACPI0007 looks like a processor object: ACPI v6.5 Section 8.4:
| https://uefi.org/specifications
Thanks.
A processor device description if I understand what I read at that URL,
though the ACPI
This is just (well mostly) curiosity, it doesn't seem to
affect anything that I know about, but during autoconfig,
the kernel (any 9.99.x I have tried I think) prints
acpi0: autoconfiguration error: failed to activate ACPI0007
64 times during the boot sequence (this one is from 9.99.105)
I wa
Date:Tue, 1 Nov 2022 13:29:19 +0300
From:Valery Ushakov
Message-ID:
| On Tue, Nov 01, 2022 at 10:05:19 +0100, Thomas Klausner wrote:
| > Oct 31 07:52:59 yt dhcpcd[3496]: wm0: requesting DHCPv6 information
| > Oct 31 07:53:52 yt syslogd[4885]: last message repea
Date:Sun, 30 Oct 2022 02:23:22 + (UTC)
From:NetBSD Test Fixture
Message-ID: <166709660251.4897.4957055195986461...@babylon5.netbsd.org>
| An extract from the build.sh output follows:
|
| ./usr/share/zoneinfo/America/Rainy_River
| ./usr/share/zonein
Date:Wed, 12 Oct 2022 11:12:31 +
From:Chavdar Ivanov
Message-ID: <1665573114107.3142740811.698765...@gmail.com>
| Funny enough, even under zsh, the following works just fine:
|
| dir() { (/bin/ls -al "$@" | less;) }
That's an entirely different thing, tha
Date:Wed, 12 Oct 2022 12:13:05 +0200
From:Thomas Klausner
Message-ID:
| dir() { ls -al "$@" | less; }
|
| On -current (9.99.100 kernel from Oct 9, Userland from Sep 21, zsh
| from May), when I CTRL-Z the less(1) and then want to go back in, it
| doesn't wor
Date:Sun, 18 Sep 2022 09:17:22 +0200
From:Thomas Klausner
Message-ID:
| I think this is http://gnats.netbsd.org/56900
Yes, clearly that. But please ignore this for now - turns out
my automation to dig out and boot the most recent kernel failed,
it was running so
I just got the following panic, from running the ATF tests, after an amd64
build of HEAD (updated sources within the past 24 hours). Aside from Jason's
driver changes (which can't be relevant, this system has none of those
devices) I don't think I'm missing any meaningful changes from HEAD as
i
Date:Fri, 9 Sep 2022 11:10:36 +0200
From:Rhialto
Message-ID:
| How does the UEFI system decide what to boot?
There are a whole set of variables in UEFI internal storage
One group of those are named BOOT where the is a 4
digit hex value. Its value is irre
Date:Thu, 8 Sep 2022 08:07:44 -0700 (PDT)
From:Paul Goyette
Message-ID:
| I got my menu back. Just had to put it at /efi/boot.cfg (ie, at the
| root of the EFI partition).
That's interesting, not where it is supposed to be placed - I hadn't
tried putting one th
Date:Thu, 8 Sep 2022 07:46:14 -0700 (PDT)
From:Paul Goyette
Message-ID:
| (The EFI partition is still marked ``bootme''.)
That one you should probably turn off - bootme (the UEFI "where to boot"
flag) should be on the NetBSD root partition.
Or not there at all, a
Date:Wed, 7 Sep 2022 20:37:43 -0700 (PDT)
From:Paul Goyette
Message-ID:
| I tried to run gpt biosboot (and specified -i 1 for the partition)
| and I also ran installboot.
You didn't show the GPT tables for this system, so "-i 1" means nothing
to anyone but you a
Date:Wed, 7 Sep 2022 13:39:08 -0700 (PDT)
From:Paul Goyette
Message-ID:
| I have completely disconnected the wd0 and wd1 hard drives, and now
| the motherboard/BIOS can't find something (primary boot?). It does
| not give any helpful messages (no messages at a
Date:Sun, 4 Sep 2022 09:54:37 -0700
From:"Stephen M. Jones"
Message-ID: <5668c5a7-471a-4c20-a802-c5cf17a92...@sdf.org>
| amanda#newfs -02 -F -s 105468549120 /dev/rld1d
I assume the -02 is really -O2, but the problem here is that the
filesystem is being generated wi
Date:Mon, 15 Aug 2022 11:54:11 +0200
From:"os...@fessel.org"
Message-ID: <6f327000-66c8-4b11-8792-2aad37d45...@fessel.org>
| And cloning 9.99.95 just panics (syscall (number 5). while trying
| cnopen().
If you can, try a very recent HEAD (certainly must be 9.99.
Date:Sun, 14 Aug 2022 15:52:35 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| N.B. It would be nice if there were a (MI) boot option that could be used
| to influence HZ without recompiling. Booting into ddb and patching hz
| and a few deri
Date:Sun, 14 Aug 2022 00:28:38 +0200
From:Joerg Sonnenberger
Message-ID:
| Does the interrupt rate match HZ?
Yes. I rebooted the system I tested yesterday (which behaved just the
same as reported then .. which I guess was technically the early hours
of this morn
Date:Sun, 14 Aug 2022 00:28:38 +0200
From:Joerg Sonnenberger
Message-ID:
| I'm more wondering about the LAPIC frequency here. That one is normally
| used to drive the clockintr and if that frequency is off, interrupt rate
| would be off too. Does the interrupt
Date:Sat, 13 Aug 2022 17:41:05 +0200
From:Michael van Elst
Message-ID:
| If you boot the kernel in debug mode (netbsd -x),
I did.
| you may see output like:
which was:
[ 1.03] cpu0: TSC freq CPUID 341760 Hz
[ 1.03] cpu0: TSC freq from CPUI
Date:Sat, 13 Aug 2022 14:44:46 +
From:Taylor R Campbell
Message-ID: <20220813144453.af03d60...@jupiter.mumble.net>
| When _userland_ opens the raw /dev/rdkN _character_ device, for a
| wedge on (say) raid0, the _kernel_ will do the equivalent of opening
| th
Date:Sun, 7 Aug 2022 09:17:52 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| Does this help ?
|
| Index: sys/arch/x86/x86/cpu.c
Finally got a chance to test that patch properly - sorry for the delay.
The result: "not much" if anything a
Turns out that I was misled by cvs diff ... I did that on the kernel
after the previous crash, just to verify that nothing unexpected had
happened, but forgot that that diffs the checked out version against
the version it was checked out from. When I saw no diffs from
specfs_vnode.c I jumped to t
OK, ignore the previous crash - whatever it was, either it was some
weird one off, or it was something unrelated that has been fixed in
the past 18 hours (and caused in the period not long before that).
I did as I said, updated the src tree again, backed out your dk.c patch,
and rebuilt the kernel
Date:Sat, 13 Aug 2022 12:10:46 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| That panic should be fixed by now, it was an inverted assertion.
OK, thanks - I did see it gone in my latest test (the message about
which was delayed getting to mai
Date:Fri, 12 Aug 2022 23:35:26 +
From:Taylor R Campbell
Message-ID: <20220812233531.8c22560...@jupiter.mumble.net>
| Can you try _reverting_ specfs_blockopen.patch, and _applying_ the
| attached dkopenclose.patch, and see if you can reproduce any crash?
OK,
Date:Fri, 12 Aug 2022 21:07:14 +
From:Taylor R Campbell
Message-ID: <20220812210719.ca66b60...@jupiter.mumble.net>
| Here's a hypothesis about what happened.
|
| - You have a RAID volume, say raid0, with a GPT partitioning it.
|
| - raid0 is configured w
Date:Fri, 12 Aug 2022 17:10:47 +
From:Taylor R Campbell
Message-ID: <20220812171053.3e95260...@jupiter.mumble.net>
| I added a couple more assertions (spec_vnops.c 1.213).
OK, once again, crash on first boot - but this time (as I had only
one new kernel to test
Date:Fri, 12 Aug 2022 16:40:13 +
From:Taylor R Campbell
Message-ID: <20220812164019.34ded60...@jupiter.mumble.net>
| This is extremely unlikely. You might try removing the assertion that
| it tripped on, KASSERT(!sd->sd_opened), so that it has the opportunity
Date:Thu, 11 Aug 2022 13:01:34 +
From:Taylor R Campbell
Message-ID: <20220811130139.b310860...@jupiter.mumble.net>
| If that still doesn't help, you could try the attached patch (which
| I'm not committing at the moment because it changes the kernel ABI).
|
Date:Thu, 11 Aug 2022 13:01:34 +
From:Taylor R Campbell
Message-ID: <20220811130139.b310860...@jupiter.mumble.net>
| If you cvs up spec_vnops.c to 1.211, you may get a different assertion
| firing, or not; which assertion fires now might potentially help to
A few times recently, I have seen the following panic (from 9.99.99)
[36.426616] panic: kernel diagnostic assertion "sd->sd_closing" failed:
file "/readonly/release/testing/src/sys/miscfs/specfs/spec_vnops.c", line 1725
[36.426616] cpu0: Begin traceback...
[36.426616] vpanic() at netb
Date:Sun, 7 Aug 2022 09:17:52 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| Does this help ?
I'll try it and let you know. Thanks.It might take a few days.
kre
Date:Thu, 4 Aug 2022 12:49:35 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| The measurement runs with enabled interrupts. If you have lots of interrupts
| or interrupts that take some time, the measurement is biased.
|
| Console output c
Date:Wed, 3 Aug 2022 22:30:34 +
From:David Holland
Message-ID:
| so if your previous kernel was fairly old and you
| still have older boot logs lying around you might check them for
| such notices.
This is an entirely new system, the oldest kernel it has e
The test is fixed now.
kre
Date:Wed, 20 Jul 2022 21:18:33 + (UTC)
From:RVP
Message-ID:
| Yes indeed. src/sys/arch/x86/x86/genfb_machdep.c:1.17 _has_ fixed this
| little issue quite satisfactorily. Thank you, Michael :)
Oh, yes, Sorry - meant to send a message like that a couple of day
Date:Wed, 20 Jul 2022 15:08:52 +0200
From:Matthias Petermann
Message-ID:
| [] virtio2 at pci3 dev 0 function 0
| [] virtio2: console device (rev. 0x01)
| [] virtio2: autoconfiguration error: no matching child driver; not=20
| configured
That is p
Date:Sat, 16 Jul 2022 00:20:41 + (UTC)
From:RVP
Message-ID:
| On Fri, 15 Jul 2022, Robert Elz wrote:
| > If that is all it is, it is barely worth fixing ... though this
| > must have happened sometime in the 9.99.9[78] series (sometime
| > af
POSIX is planning to add readlink(1) in the next version. Nothing
special to say about that (makes no real difference to us, we have it
already, they will specify only the common options.)
But while doing that, they looked at the -f option, and saw in coreutils
that their man page says to use re
Date:Sat, 16 Jul 2022 06:09:26 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| For the green color it doesn't matter if the order is BGR or RGB.
| For cyan, the wrong order gives "brown" which is a dark yellow.
I tossed up what to call the co
Date:Fri, 15 Jul 2022 13:32:55 +0900
From:Masanobu SAITOH
Message-ID: <87553319-950b-7dad-ac64-29d2c25d1...@execsw.org>
| Could you show me the full dmesg with verbose output?
I could, but it turns out to be about a megabyte, so unless you need
to see all that nois
Date:Fri, 15 Jul 2022 05:12:10 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| Does the color shift also happen after a cold boot ?
Yes, it is yellow, rather than cyan, when the system boots,
cold or warm (or if booting warm after linux had bor
Date:Fri, 15 Jul 2022 05:12:10 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| Does the color shift also happen after a cold boot ?
Not sure, I rarely do that, and don't think I ever have for a kernel
intended to have cyan text. I will try it
Date:Fri, 15 Jul 2022 13:32:55 +0900
From:Masanobu SAITOH
Message-ID: <87553319-950b-7dad-ac64-29d2c25d1...@execsw.org>
| Could you show me the full dmesg with verbose output?
Sure, it will take me a bit to get to a state where I can reboot again.
You do realize t
Date:Thu, 14 Jul 2022 23:17:36 + (UTC)
From:RVP
Message-ID: <259960d6-9f5d-56c9-6f15-46766387f...@sdf.org>
| Works OK for me with an updated-just-now customized (ie. just a lot of stuff
| removed) GENERIC.
My kernel is similar (though still has too much unnec
Hi,
I just booted a kernel that I built (from up to date at the time)
HEAD sources about 24 hours ago.
Everything seemed to be working fine - until I noticed that all of
my clocks (there are several, gkrellm, window manager, a dclock,
and an xtu) were all wildly wrong (as in, were moving time for
Date:Sun, 10 Jul 2022 14:04:23 +1200
From:Lloyd Parkes
Message-ID:
| On 10/07/22 00:55, Roland Illig wrote:
| > Shouldn't there be an automatic check for these? Running this check
| > after a "make distribution" should be fairly easy.
|
| That sounds like
Ah, OK, thanks, somehow I missed the absence of the rcvar= line.
kre
Does someone know of a reason for a setting for the rc.conf
(rc.d/*) variable raidframeparity to be omitted from rc.defaults/rc.conf ?
To me that looks like an oversight.
Assuming I correct that, does anyone know of a reason it should not
default to YES ?
That is, does anyone know of a likely re
Currently readlink(1) and stat(1) (and I do mean the man pages)
have a very unhealthy relationship.
They're currently bound together based upon the accident of
their parentage - that is, there is no readlink.c, readlink
the command is accomplished by using stat with a particular
set of options.
Date:Wed, 08 Jun 2022 02:28:46 +1000
From:matthew green
Message-ID: <28927.1654619...@splode.eterna.com.au>
| i like this.
Thanks.
| please finish it.
Done, more or less - still needs work on the -x and -y outputs
(particularly for -xI).
The header format chan
I am having a similar problem (though with ssh, rather than scp).
I have long had a setup where I run tunnels over ssh (in both
directions) between munnari.oz.au and me at home. The latter
(me@home) has a new 9.99.97 system in the process of being installed.
I have a pseudo-host "work" (not a pa
| Date: Fri, 3 Jun 2022 21:08:15 +0200
| From: Reinoud Zandijk
| Well I'd like to add another point! Fixed i915 DRM support!
That's not needed for the branch (nor are other bugs, known or otherwise)
but should certainly be fixed (if it hasn't already, I thought some
progress had been made
Date:Wed, 25 May 2022 14:07:09 -0400
From:Greg Troxel
Message-ID:
| kre@ disagrees with me about it being wrong;
Only mildly, I can see your point. My reply was sent before I
saw yours.
| the mbone was a particular overlay network, a social phenomenon,
yes.
1 - 100 of 524 matches
Mail list logo
