On 2021-May-23, at 00:08, Mark Millard via freebsd-current wrote:
> On 2021-May-22, at 22:16, Warner Losh wrote:
>
>> On Sat, May 22, 2021 at 10:44 PM Mark Millard via freebsd-arm
>> wrote:
>> # mount -onoatime 192.168.1.187:/usr/ports/ /mnt/
>> # diff -r /us
On 2021-May-22, at 22:16, Warner Losh wrote:
> On Sat, May 22, 2021 at 10:44 PM Mark Millard via freebsd-arm
> wrote:
> # mount -onoatime 192.168.1.187:/usr/ports/ /mnt/
> # diff -r /usr/ports/ /mnt/ | more
> nvme0: cpl does not map to outstanding cmd
> cdw0: sqhd:
0-CURRENT #1
main-n246854-03b0505b8fe8-dirty: Sat May 22 16:25:04 PDT 2021
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-dbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-DBG-CA72
arm64 aarch64 1400013 1400013
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
media present.
Port 3 apparently had the USB3 SSD boot media (the
same media that the FreeBSD loader got the kernel
from before the above).
Cutting power and starting over did not get the
problem again (so far).
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-3' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-4' to stop... done
Wai
n to completion.
>>
>> When I retried after rebooting and scrubbing (no
>> problems found), the problem did not repeat.
>>
>> I do not have more information nor a way to repeat
>> the problem on demand, unfortunately.
>>
>> Details of the vintage of the
shot for mm's patched build in git
context.
merge-base: 7381bbee29df959e88ec59866cf2878263e7f3b2
merge-base: CommitDate: 2021-03-12 20:29:42 +
7381bbee29df (freebsd/main, freebsd/HEAD, pure-src, main) cam: Run all
XPT_ASYNC ccbs in a dedicated thread
n245444 (--first-parent --count for merge-base)
The s
On 2021-May-5, at 17:01, Yuri Pankov wrote:
> Mark Millard via freebsd-current wrote:
>> Context:
>>
>> # gpart show -pl da0
>> => 40 468862048da0 GPT (224G)
>> 40 532480 da0p1 efiboot0 (260M)
>> 532520 2
19:52:14 2021
config:
NAMESTATE READ WRITE CKSUM
zroot ONLINE 0 0 0
da0p3 ONLINE 0 0 0
errors: No known data errors
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in e
On 2021-May-5, at 05:28, Mark Millard wrote:
> On 2021-May-5, at 02:47, Andriy Gapon wrote:
>
>> On 05/05/2021 01:59, Mark Millard via freebsd-current wrote:
>>> I had a:
>>> # zfs list -tall
>>> NAME USED AVAIL
On 2021-May-4, at 20:26, Mark Millard wrote:
> On 2021-May-4, at 13:38, Mark Millard wrote:
>
>> [The first buidlworld is still in process. So while waiting . . .]
>>
>> On 2021-May-4, at 10:31, Mark Millard wrote:
>>
>>> I probably know why
On 2021-May-5, at 02:47, Andriy Gapon wrote:
> On 05/05/2021 01:59, Mark Millard via freebsd-current wrote:
>> I had a:
>> # zfs list -tall
>> NAME USED AVAIL REFER MOUNTPOINT
>> . . .
>> zroot/DESTDIRs/13_0R-CA72
On 2021-May-4, at 13:38, Mark Millard wrote:
> [The first buidlworld is still in process. So while waiting . . .]
>
> On 2021-May-4, at 10:31, Mark Millard wrote:
>
>> I probably know why the huge count of differences this time
>> unlike the original report . . .
&
name -apKU
FreeBSD CA72_4c8G_ZFS 13.0-RELEASE FreeBSD 13.0-RELEASE #0
releng/13.0-n244733-ea31abc261ff-dirty: Thu Apr 29 21:53:20 PDT 2021
root@CA72_4c8G_ZFS:/usr/obj/BUILDs/13_0R-CA72-nodbg-clang/usr/13_0R-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
arm64 aarch64 1300139 1300139
===
Mark Milla
gt; worth submitting a PR? or is bsdinstall legacy and I need to use some
> other method. I've not tried releng/12.2 yet.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
htt
[The first buidlworld is still in process. So while waiting . . .]
On 2021-May-4, at 10:31, Mark Millard wrote:
> I probably know why the huge count of differences this time
> unlike the original report . . .
>
> Previously I built based on a checked-in branch as part of
> m
ad
return loads(fp.read(),
File "/usr/local/lib/python3.7/codecs.py", line 504, in read
newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 18:
invalid start byte
Not exactly an obvious error message for the issue.
===
.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-uns
[Just adding readelf -S info since it seems to show more.]
On 2021-May-4, at 10:01, Mark Millard wrote:
> On 2021-May-4, at 08:51, Mark Millard wrote:
>
>> On 2021-May-4, at 06:01, Ed Maste wrote:
>>
>>> On Mon, 3 May 2021 at 22:26, Mark Millard wrote:
>>
On 2021-May-4, at 08:51, Mark Millard wrote:
> On 2021-May-4, at 06:01, Ed Maste wrote:
>
>> On Mon, 3 May 2021 at 22:26, Mark Millard wrote:
>>>
>>> But I'll note that I've built and stalled py37-diffoscope
>>> (new to me). A basic quick
On 2021-May-4, at 06:01, Ed Maste wrote:
> On Mon, 3 May 2021 at 22:26, Mark Millard wrote:
>>
>> But I'll note that I've built and stalled py37-diffoscope
>> (new to me). A basic quick test showed that it reports:
>>
>> W: diffoscope.main: Fuzzy-matching i
On 2021-May-3, at 21:27, Mark Millard wrote:
> On 2021-May-3, at 19:26, Mark Millard wrote:
>
>> On 2021-May-3, at 10:51, Mark Millard wrote:
>>
>>> On 2021-May-3, at 07:47, Ed Maste wrote:
>>>
>>>> On Thu, 29 Apr 2021 at 02:
On 2021-May-3, at 19:26, Mark Millard wrote:
> On 2021-May-3, at 10:51, Mark Millard wrote:
>
>> On 2021-May-3, at 07:47, Ed Maste wrote:
>>
>>> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current
>>> wrote:
>>>>
>>
On 2021-May-3, at 10:51, Mark Millard wrote:
> On 2021-May-3, at 07:47, Ed Maste wrote:
>
>> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current
>> wrote:
>>>
>>> Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping and
>>> /usr
On 2021-May-3, at 07:47, Ed Maste wrote:
> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current
> wrote:
>>
>> Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping and
>> /usr/obj/DESTDIRs/13_0R-CA7-poud/sbin/ping differ
>> Files /usr/obj/DESTDI
printf("\n%23s %012jx %012jx %08jx ", type,
+ (uintmax_t)map->md_phys, (uintmax_t)map->md_virt,
(uintmax_t)map->md_pages);
if (map->md_attr & EFI_MD_ATTR_UC)
printf("UC ");
===
Mark Mi
[Just a resend: asking the question on the list
less than an hour before the UTC month change
might not be all that effective relative to
those that just web browse the list to read it.]
On 2021-Apr-30, at 16:21, Mark Millard wrote:
> Context . . .
>
> I've been experimenting
ZFS versioning is independent
between 13 and 14.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any m
are about such differences.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "
On 2021-Apr-25, at 08:14, Graham Perrin wrote:
> On 23/04/2021 08:39, Mark Millard via freebsd-current wrote:
>
>> [3]
>
>
> With regard to mounting ZFS file systems in single user mode
>
> What's currently footnote 3 will probabl
j/DESTDIRs/13_0R-CA7-for-chroot/var/db/etcupdate/
I have not checked on if "etcupdate build" has a similar issue
vs. not.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing
touched on the file server and would make time ordered
finding of things (such as for build-less approximate bisecting)
far more reasonable.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org
ng / writable at this
stage either.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
-- 1 root wheel 26552108 Apr 9 07:39:21 2021 kernel.txz
# ls -Tla /usr/freebsd-dist/
ls: /usr/freebsd-dist/: No such file or directory
NOTE: creating /usr/freebsd-dist/ with a copy of the MANIFEST
file in it was enough to get past this issue: it is doing
Archive Extraction now.
===
Mark Millard
On 2021-Mar-10, at 10:09, Olivier Houchard wrote:
> On Tue, Mar 09, 2021 at 03:39:42PM -0800, Mark Millard via freebsd-arm wrote:
>> After using poudriere to build ports for native cortex-a72
>> on the MACCHIATObin Double Shot (and similarly for
>> cortex-a57 on
On 2021-Mar-9, at 22:00, Mark Millard wrote:
[Trying to be timely about reporting new information
because of 13.0 not having much time left.]
> On 2021-Mar-9, at 21:11, Mark Millard wrote:
>
>> On 2021-Mar-9, at 19:17, Mark Millard wrote:
>>
>> [My only testing c
On 2021-Mar-9, at 21:11, Mark Millard wrote:
> On 2021-Mar-9, at 19:17, Mark Millard wrote:
>
> [My only testing context for this has been main, not 13.0.
> But it might be a 13.0 worry.]
>
>> Using the quickest to so-far-reliably-fail type of example from
>>
On 2021-Mar-9, at 19:17, Mark Millard wrote:
[My only testing context for this has been main, not 13.0.
But it might be a 13.0 worry.]
> Using the quickest to so-far-reliably-fail type of example from
> another thread I used truss to see what happens, here filtered
> down to two
- UNKNOWN FreeBSD32 SYSCALL 542 --
83316 100123: #542(0xcd54,0x0) = 0 (0x0)
-- UNKNOWN FreeBSD32 SYSCALL 2 --
83842 100199:
83316 100123: #2() = 83842 (0x14782)
-- UNKNOWN FreeBSD32 SYSCALL 6 --
-- UNKNOW
On 2021-Mar-9, at 17:18, Mark Millard wrote:
> On 2021-Mar-9, at 15:39, Mark Millard wrote:
>
>> After using poudriere to build ports for native cortex-a72
>> on the MACCHIATObin Double Shot (and similarly for
>> cortex-a57 on the OverDrive 1000) I attempted to d
On 2021-Mar-9, at 15:39, Mark Millard wrote:
> After using poudriere to build ports for native cortex-a72
> on the MACCHIATObin Double Shot (and similarly for
> cortex-a57 on the OverDrive 1000) I attempted to do my
> usual bulk build targeting cortex-a7 via poudriere-devel:
>
fc
GENERIC-NODBG arm armv7 145 145
The host system reports:
# ~/fbsd-based-on-what-freebsd-main.sh
merge-base: bad9fa56620eb82395c5ab66d300e91a0222dde2
merge-base: CommitDate: 2021-03-06 21:46:28 +
e48a1c379bfc (HEAD -> mm-src) mm-src snapshot for mm's patched build in git
context.
bad9
On 2021-Mar-5, at 17:35, Mark Millard wrote:
> Yasuhiro Kimura yasu at utahime.org wrote on
> Fri Mar 5 23:34:59 UTC 2021 :
>
>> From: Konstantin Belousov
>> Subject: Re: Waiting for bufdaemon
>> Date: Fri, 5 Mar 2021 22:43:58 +0200
>>
>>> My b
natives [ACPI-fast(900)
i8254(0) TSC-low(-100) dummy(-100)] failed to make a
usable environment.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.
# sysctl -ad | wc
11153 57922 604736
# sysctl -a | wc
13080 29457 449667
So: not a trivial amount of material.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
http
On 2021-Feb-17, at 11:44, Kyle Evans wrote:
> On Tue, Feb 16, 2021 at 7:29 PM Kyle Evans wrote:
>>
>> On Tue, Feb 16, 2021 at 7:23 PM Mark Millard via freebsd-current
>> wrote:
>>>
>>> I historically on occasion have done something like:
>>>
On 2021-Feb-17, at 01:29, Hans Petter Selasky wrote:
> On 2/17/21 1:58 AM, Mark Millard via freebsd-current wrote:
>> stand/kshim/bsd_kernel.h has its own define of __FreeBSD_version and
>> seems to have last had it changed in the main branch as shown below.
>> Is it as
On 2021-Feb-16, at 15:37, Mark Millard wrote:
> On 2021-Feb-16, at 11:49, Brandon Bergren wrote:
>
>> It looks like there were recently some fixes to release.sh, that just got
>> backported to 13. I wonder if the problem is the packages themselves being
>>
shot for mm's patched build in git
context.
3acea07c1873 (pure-src) Restore the augmented strlen commentary
FreeBSD FBSDFHUGE 14.0-CURRENT FreeBSD 14.0-CURRENT mm-src-n244686-c1845d00f818
GENERIC-NODBG amd64 amd64 144 1400004
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in e
n
-#define__FreeBSD_version 110
+#define__FreeBSD_version 130
#include
#include
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.o
e.sh would have to contribute
as a side effect of its prior use in some way for that
sequence, if I understand right.
>
> On Tue, Feb 16, 2021, at 12:20 PM, Mark Millard wrote:
>> There are other reports of a:
>>
>> pkg: Warning: Major OS version upgrade detected. Run
ruary/120154.html
Steve Kargl:
https://lists.freebsd.org/pipermail/freebsd-ports/2021-February/120298.html
https://lists.freebsd.org/pipermail/freebsd-ports/2021-February/120314.html
(The last for Steve K. is about how solved.)
But I cannot not tell if there is a common cause or a common
solution.
On 2021-Feb-16, at 02:22, Harry Schmalzbauer wrote:
> Am 16.02.2021 um 11:08 schrieb Mark Millard:
>> On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote:
>>> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current:
>>>> On 2021-Feb-13, at 16:40, Warner Lo
On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote:
> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current:
>> On 2021-Feb-13, at 16:40, Warner Losh wrote:
>>
>>> Are you aware of gpart create?
>>>
>>> Warner
>> From which I derive
adwell,
skylake, skylake-avx512, skx, cascadelake, cooperlake, cannonlake,
icelake-client, icelake-server, tigerlake, knl, knm, k8, athlon64, athlon-fx,
opteron, k8-sse3, athlon64-sse3, opteron-sse3, amdfam10, barcelona, btver1,
btver2, bdver1, bdver2, bdver3, bdver4, znver1, znver2, x86-64
# cc -
On 2021-Feb-13, at 17:38, Warner Losh wrote:
> On Sat, Feb 13, 2021, 6:36 PM Mark Millard wrote:
>
> On 2021-Feb-13, at 16:40, Warner Losh wrote:
>
> > Are you aware of gpart create?
> >
> > Warner
>
> From which I derive that I had an implicit, incorrec
.
So I need to find such a drive another way, something
I was not even trying to do.
That answers my question. Thanks.
Mark
>> On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current
>> wrote:
>> I plugged in a new Optane and booted FreeBSD on the
>> ThreadRipper 1
004
But this is not a new thing, more of a "still true"
thing.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
ight when what was being looked at was
from stable/12 after it was branched (or some other such
mis-matched example) and that he was indicating that the
mismatches are misleading, especially if one does not know to
expect them.
Part of the issue is that nothing else on the commit page
indica
ith the one that has "?h=stable/12&" shows stable/12
in the upper right and copy/ptase of the commit link show does
include "?h=stable/12&" text. Further activity from there
continues to have the text.
Of course if one does a range search for the id, the context
is lost.
eBSD 14.0-CURRENT mm-src-n244686-c1845d00f818
GENERIC-NODBG arm64 aarch64 144 144
and had no troubles doing so.
The other systems will all be updated to be based on
the 3acea07c1873 source code vintage.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early
c88
GENERIC-NODBG amd64 amd64 143 143
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
volved might avoid later getting cylinder
checksum failure notices.
I hope this proves of some help, but, if it is not, I'm unlikely
to have more information, sorry.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
On 2021-Jan-23, at 21:37, Mark Millard wrote:
> On 2021-Jan-22, at 01:45, Mark Millard wrote:
>
>> Given an already built, installed and booted system version, I've
>> noted a big difference for META_MODE in 2 rebuild contexts (no
>> source updates involved):
&g
to be the same type of "UNEXPECTED
SOFT UPDATE INCONSISTENCY" issue on an old
2-socket/2-cores-each PowerMac G5 powerpc64
configuration that was running main from after
5cc52631b3b8 .
So, in this case, I do not expect that the problem
is special to Ryzen or related CPUs.
===
Mark Millard
m
if there was a problem about a month ago, there may be another
problem as well as the above that was something else, the above just
happens first now.)
Looks like emulators/virtualbox-ose-kmod needs to track the kernel
change(s).
===
Mark Millard
marklmi at
names like main-armv7 ,
main-armv6 , main-mips , or main-mip64 . So I assume
that those are not being experimented with yet.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
On 2021-Jan-24, at 23:37, Mark Millard wrote:
>
>> How cat one track multiple branches with git without keeping entirely
>> separate trees?
>
> There are multiple possibilities here and it is not
> clear which you are hoping for.
>
> A) You could be trying to
== 2756 total to also have a separate one for
stable/13 in, say, /usr/fbsd/stable-13-shallow/ .
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailma
to wait for free pages before retrying
the page fault handler
# sysctl -d vm.pfault_oom_attempts
vm.pfault_oom_attempts: Number of page allocation attempts in page fault
handler before it triggers OOM handling
I hope that helps.
===
Mark Millard
marklmi at yahoo.com
( d
On 2021-Jan-22, at 01:45, Mark Millard wrote:
> Given an already built, installed and booted system version, I've
> noted a big difference for META_MODE in 2 rebuild contexts (no
> source updates involved):
>
> *) Prior buildworld buildkernel, installkernel, installworld, bo
need to
contribute to what needs to be rebuilt (just based on being newer). So
the option to ignore (some of?) them could be useful in making META_MODE
builds quicker.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar
On 2021-Jan-21, at 09:24, Mark Millard wrote:
> Ulrich Spörlein uqs at FreeBSD.org wrote on
> Wed Jan 20 09:49:49 UTC 2021 :
>
>>While here, drop the redundant branch name from the git output and don't
>>count commits in shallow clones.
>>
>
>
t to use more like <=1800 MiByte to
avoid what the documentation warns about for tradeoffs
for having too much swap space.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://l
On 2021-Jan-19, at 17:42, Mark Millard wrote:
> On 2021-Jan-18, at 21:12, Mark Millard wrote:
>
>> On 2021-Jan-18, at 19:19, Mark Millard wrote:
>>
>>> . . .
>>>> FYI: I re-established my access to a RPi2B V1.1 and made
>>>> i
On 2021-Jan-18, at 21:12, Mark Millard wrote:
> On 2021-Jan-18, at 19:19, Mark Millard wrote:
>
>> . . .
>>> FYI: I re-established my access to a RPi2B V1.1 and made
>>> it report: "maximum recommended amount (468832 pages)"
>>>
>
On 2021-Jan-18, at 19:19, Mark Millard wrote:
> . . .
>> FYI: I re-established my access to a RPi2B V1.1 and made
>> it report: "maximum recommended amount (468832 pages)"
>>
>> (The figure can vary some from release to release.)
>>
>> 468832
) arm64: fix early
devmap assertion
FreeBSD OPiP2E_RPi2v11 13.0-CURRENT FreeBSD 13.0-CURRENT
mm-src-c255938-g4180404713ec GENERIC-NODBG arm armv7 1300135 1300135
This suggests that you should be able to build on the RPi2B v1.1,
using -j4, with appropriate configuration for what and how to build.
It is
On 2021-Jan-17, at 19:19, Mark Millard wrote:
> On 2021-Jan-17, at 17:50, bob prohaska wrote:
>
>> On Sun, Jan 17, 2021 at 12:30:51PM -0800, Mark Millard wrote:
>>>
>>>
>>> On 2021-Jan-17, at 09:40, bob prohaska wrote:
>>>
>>>>
On 2021-Jan-17, at 17:50, bob prohaska wrote:
> On Sun, Jan 17, 2021 at 12:30:51PM -0800, Mark Millard wrote:
>>
>>
>> On 2021-Jan-17, at 09:40, bob prohaska wrote:
>>
>>> On Sat, Jan 16, 2021 at 03:04:04PM -0800, Mark Millard wrote:
>>>>
On 2021-Jan-17, at 09:40, bob prohaska wrote:
> On Sat, Jan 16, 2021 at 03:04:04PM -0800, Mark Millard wrote:
>>
>> Other than -j1 style builds (or equivalent), one pretty much
>> always needs to go looking around for a non-panic failure. It
>> is uncommon for all
reen mode for VT VGA backend is graphics (unless we are running on
hypervisor or hw.vga.textmode is set to 1). Using hw.vga.textmode
for loader does remove possibility to have graphical mode VT VGA with
text mode loader.
screen.textmode can have possible values "0" to disable te
ics (unless we are running on
hypervisor or hw.vga.textmode is set to 1). Using hw.vga.textmode
for loader does remove possibility to have graphical mode VT VGA with
text mode loader.
screen.textmode can have possible values "0" to disable text mode,
and "1"
On 2021-Jan-16, at 14:03, bob prohaska wrote:
> On Sat, Jan 16, 2021 at 11:17:52AM -0800, Mark Millard wrote:
>>
>>
>> On 2021-Jan-16, at 07:55, bob prohaska wrote:
>>
>>> On Fri, Jan 15, 2021 at 09:25:00PM -0800, Mark Millard wrote:
>>>&
On 2021-Jan-16, at 07:55, bob prohaska wrote:
> On Fri, Jan 15, 2021 at 09:25:00PM -0800, Mark Millard wrote:
>>
>> On 2021-Jan-15, at 20:37, bob prohaska wrote:
>>
>>> While playing with -current on armv7 using a raspberry pi 2 v1.1
>>> an e
sole.
>
> In past occurrences, an old kernel (pre-git) worked through the problem.
> If a restart of make buildworld doesn't get past the stoppage I'll check
> again.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
BSD 13.0.
powerpc (old PowerMac G4):
WARNING: Device "agp" is Giant locked and may be deleted before FreeBSD
13.0.
WARNING: Device "consolectl" is Giant locked and may be deleted before
FreeBSD 13.0.
Note: FreeBSD has boot problems for various powerpc64 and 32-bit
powerpc Po
In the interest of documenting some variability . . .
While not readily reproducible, on a ThreadRipper 1950X
that I have access to, a recent reboot had one "system
thread" time out: bufspacedaemon-3 . The rest of the
"system thread" list behaved normally.
===
Mark Millard
On 2021-Jan-12, at 13:11, Mark Millard wrote:
> PowerMac G5's and G4's with not much in them or connected to them report:
>
> WARNING: Device "openfirm" is Giant locked and may be deleted before FreeBSD
> 13.0.
> WARNING: Device "kbd" is Giant locked and
if this one is modal in some way and it I happen to
be using a mode that avoided the usage. (I do not normally run an
unpatched FreeBSD on old PowerMacs as well.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebs
). This initial material displays in screen.textmode="1" style before
the display switches to the screen.textmode="0" style of display for alter
output. (I'm not complaining, just noting the visible sequence.)
===
Mark Millard
marklmi at
On 2021-Jan-6, at 09:51, Cy Schubert wrote:
> In message <63a29589-22b5-495b-8e0d-14e13091d...@yahoo.com>, Mark Millard
> write
> s:
>>
>>
>> On 2021-Jan-5, at 17:54, David Wolfskill wrote:
>>
>>> On Wed, Jan
t; It's a medium-light blue, so it's easy enough to read (unlike a navy
> blue, for example).
FYI: whiteish on black (or at least something very dark)
in my hw.vga.textmode="1" context. I saw everything here
as well. I did not take videos to do detailed inspections.
I did not notic
>>> toomas
>>>
>>
>> the 58661b3ba9eb should hopefully fix the loader text mode issue, it would
>> be cool if you can verify:)
>>
>> thanks,
>> toomas
>
> I think, I got it fixed (at least idwer did confirm for his system, thanks).
>
On 2021-Jan-5, at 13:28, Mark Murray wrote:
>> On 5 Jan 2021, at 20:15, Mark Millard wrote:
>>
>> The machine is a MACCHIATOBin Double Shot.
>
> Thanks for the warning :-)
>
> I'm using an MBin/DS as my firewall/gateway, and in its Copious Free Time™,
> an
r range of behavior
for the cortex-a72 is involved here.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
ed differences.
Afterwards, the changes in the tree at /usr/src can be merged via a
regular merge.
END QUOTE
I do not remember mergemaster having a bootstrap stage in setting
it up, a stage that should be executed before /usr/src (or whatever)
is updated. So the pro
On 2020-Dec-22, at 13:31, Mark Millard wrote:
> On 2020-Dec-22, at 13:06, bob prohaska wrote:
>
>> On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
>>>
>>> what does "pkg install git" do for you? NB: I use "pkg install gi
content.
Checking out stable/12 from the clone should be possible after the above, but
that is not what I've been doing.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
status.freebsd.org/builds?type=package does
not yet seem to include ampere2.nyi.freebsd.org based builds.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd
501 - 600 of 1311 matches
Mail list logo
