12.2-RELEASE buildworld fail at cddl/zfs / libuutil.so

[Tomasz CEDRO]

Hello world!

I cannot buildworld for 12.2-RELEASE. Using /usr/src as svn or git no 
matter (its set to releng/12.2). Did clean /usr/obj. Any hints welcome :-)


# uname -a
FreeBSD hexagon 12.2-RELEASE-p1 FreeBSD 12.2-RELEASE-p1 GENERIC  amd64

# /usr/bin/time -h make buildkernel buildworld NO_CLEAN=1
(..)
===> bin/tests (all)
===> cddl (all)
===> cddl/lib (all)
===> cddl/lib/drti (all)
===> cddl/lib/libavl (all)
===> cddl/lib/libctf (all)
===> cddl/lib/libdtrace (all)
===> cddl/lib/libnvpair (all)
===> cddl/lib/libumem (all)
===> cddl/lib/libuutil (all)
===> cddl/lib/libzfs_core (all)
===> cddl/lib/libzfs (all)
===> cddl/lib/libzpool (all)
===> cddl/lib/tests (all)
===> cddl/sbin (all)
===> cddl/sbin/zfs (all)
cc -target x86_64-unknown-freebsd12.2 
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -fno-common 
-I/usr/src/cddl/contrib/opensolaris/lib/libzpool/common 
-I/usr/src/cddl/compat/opensolaris/include 
-I/usr/src/cddl/compat/opensolaris/lib/libumem 
-I/usr/src/sys/cddl/compat/opensolaris 
-I/usr/src/cddl/contrib/opensolaris/head 
-I/usr/src/cddl/contrib/opensolaris/lib/libuutil/common 
-I/usr/src/cddl/contrib/opensolaris/lib/libzfs/common 
-I/usr/src/cddl/contrib/opensolaris/lib/libzfs_core/common 
-I/usr/src/cddl/contrib/opensolaris/lib/libumem/common 
-I/usr/src/cddl/contrib/opensolaris/lib/libnvpair 
-I/usr/src/sys/cddl/contrib/opensolaris/uts/common 
-I/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs 
-I/usr/src/sys/cddl/contrib/opensolaris/common/zfs 
-DNEED_SOLARIS_BOOLEAN -g -O0 -std=gnu99 -fstack-protector-strong 
-Wno-pointer-sign -Wno-unknown-pragmas -Wno-empty-body 
-Wno-string-plus-int -Wno-unused-const-variable 
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality 
-Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef 
-Wno-address-of-packed-member -Wno-switch -Wno-switch-enum 
-Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments   -o 
zfs.full zfs_main.o zfs_iter.o   -ljail  -lnvpair  -luutil  -lzfs_core 
-lzfs
ld: error: /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/libuutil.so: 
undefined reference to __assfail

cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error code 1

Stop.
make[5]: stopped in /usr/src/cddl/sbin/zfs
*** Error code 1
(..)
39m18.71s real  33m45.09s user  4m10.23s sys

--
CeDeROM, SQ7MHZ, https://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 12.2-RELEASE buildworld fail at cddl/zfs / libuutil.so

[Tomasz CEDRO]

Hello PARV :-)

On 27.01.2021 12:52, parv/freebsd wrote:
> What is the git commit hash (for others)?

For the 12.2-RELEASE:

# git branch
  main
* releng/12.2
  stable/12

# git log --pretty=oneline | head
97eb1441ca7b602510a81fd512d830563998b3e7 PS/2 Synaptics touchpad 
identification fix.
2120d07af09cb830873554ba5405c5d3e51b41cc Fix OpenSSL NULL pointer 
de-reference.
fc825298b84729facaced36d32c3fc8d111648c1 Add UPDATING entries and bump 
version.
85b4a006794d02f6e0e2f53bca3782732932a7c2 Fix multiple vulnerabilities in 
rtsold.
229d311aa42306953eb45bc55a8c5ca97312025e Fix ICMPv6 use-after-free in 
error message handling.
7b3386dba21f57907931b2e6f09f741633ea3349 Fix race condition in callout 
CPU migration.

0b4300a472c89506709341530788ad9815c05bd3 Fix uninitialized variable in ipfw.
d20c61bbc2792d5c256d4d3a1c62156ccc9eb66a Update timezone database 
information.
30710f108d29a61635778e82f300781a097caec4 Fix execve/fexecve system call 
auditing.
1d21fe9cea3f530b4cfca495632d5a1595a32270 - Switch releng/12.2 from RC3 
to RELEASE. - Add the anticipated 12.2-RELEASE date to UPDATING.  Fix 
a missing colon in the previous UPDATING entry while here. - Set a 
static __FreeBSD_version.


The first one is a simple one liner that I want to test for PS/2 
Synaptics mux identification fix.





# /usr/bin/time -h make buildkernel buildworld NO_CLEAN=1
.   ^ ^ ^ ^ ^ ^
Perhaps try with cleaning out first buildworld, then kernel?


Well I did remove all from /usr/obj, build failed, then checked out 
/usr/src from svn, build failed, then checked out /usr/src from git, and 
it failed.


Just to make sure this is not a local environment problem I have 
switched to stable/12 branch (that is 12-STABLE) and it builds fine!!


# git branch
  main
  releng/12.2
* stable/12

# git log --pretty=oneline | head
f56d7f838f5b3aa0f55b10406eaa7eb760a3ba18 elfctl: prefix disable flags 
with "no"
d7e23b5cdd8465bd50f88b1e38cb695a361a26f5 elfctl: allow features to be 
specified by value
49d3dcb041f058880486e3489ca79c9476ac7abf elfctl: add backwards 
compatibility for "no" prefixes
70cdab054c8ffe7f5561ab8f31db33ee62d12c9c rctl(4): support throttling 
resource usage to 0
7baf7a45385962d06cd2a2213109b910d40a7936 ndis: Per user request, delay 
removal to 14
2a0be7b0331c5245418cdf2893c8ba6b42a0afa5 VFS_QUOTACTL: Remove needless 
casts of arg

085997e8f05e69c66a8ffc0804b275a386ba1ca8 contrib/tzdata: import tzdata 2021a
5071cbacfb343f024bc1c9969aa43d20daa8241a safexcel: Simplify request 
allocation
804d63c0ee8f56dfac29e1fe5879740a3549d0cb safexcel: Handle command/result 
descriptor exhaustion gracefully
24ee73604483152baff9e5e3cf61047eb1c3 safexcel: Add counters for some 
resource exhaustion conditions


# /usr/bin/time -h make buildkernel buildworld release -j12
(..)
cc -target x86_64-unknown-freebsd12.2 
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -c -O2 -pipe 
-fno-strict-aliasing  -g -nostdinc  -I. -I/usr/src/sys 
-I/usr/src/sys/contrib/ck/include -I/usr/src/sys/contrib/libfdt 
-D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer 
-fdebug-prefix-map=./machine=/usr/src/sys/amd64/include 
-fdebug-prefix-map=./x86=/usr/src/sys/x86/include -mcmodel=kernel 
-mno-red-zone -mno-mmx -mno-sse -msoft-float 
-fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector 
-gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef 
-Wno-pointer-sign -D__printf__=__freebsd_kprintf__ 
-Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas 
-Wno-error-tautological-compare -Wno-error-empty-body 
-Wno-error-parentheses-equality -Wno-error-unused-function 
-Wno-error-pointer-sign -Wno-error-shift-negative-value 
-Wno-address-of-packed-member -Wno-format-zero-length  -mno-aes -mno-avx 
 -std=iso9899:1999 -Werror  vers.c

ctfconvert -L VERSION -g vers.o
--- kernel.full ---
linking kernel.full
ctfmerge -L VERSION -g -o kernel.full ...
  text  data   bssdec hex   filename
  23861318   1836970   3798784   29497072   0x1c216f0   kernel.full
--- kernel.debug ---
objcopy --only-keep-debug kernel.full kernel.debug
--- kernel ---
objcopy --strip-debug --add-gnu-debuglink=kernel.debug  kernel.full kernel
--
>>> Kernel build for GENERIC completed on Wed Jan 27 08:03:22 CET 2021
--
`release' is up to date.
1h16m12.69s real5h45m44.19s user 
 28m53.59s sys



Did anyone manage to build 12.2-RELEASE from repo? :-)

--
CeDeROM, SQ7MHZ, https://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-s

Re: 12.2-RELEASE buildworld fail at cddl/zfs / libuutil.so

[Tomasz CEDRO]

On 27.01.2021 19:31, parv/freebsd wrote:
# git log --pretty=fuller --grep libuutil release/12.2.0. 
.stable/12


commit 30ec3f368d
Author:     Eugene Grosbein 
AuthorDate: Dec.2020.1206-1622 +
Commit:     Eugene Grosbein 
CommitDate: Dec.2020.1206-1622 +

     MFC r364027 by arichardson: Fix linker error in libuutil with 
recent LLVM


     This also fixes nanobsd-style build (cross-compiling).
     Original commit log:

       Not marking the function as static can result in a linker error:
       undefined reference to __assfail [--no-allow-shlib-undefined]
       I noticed this error after updating our CHERI LLVM to the latest 
upstream

       LLVM HEAD revision.

       This change effectively reverts r329984 and marks 
dmu_buf_init_user as

       static (which keeps the GCC build happy).
... above seems to (as I haven't bisected) be the fix in 12-STABLE which 
allows

the build to finish with success.
   - parv


Whoah! Mystery solved! This commit did not jump into the releng/12.2 yet 
it seems. Thank you PARV!! :-)


--
CeDeROM, SQ7MHZ, https://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Dell XPS 8940 SATA and NVMe disk controller not recognized

[Tomasz CEDRO]

Hello :-) You may take a look at http://bsd-hardware.info/ report your
hardware issues and see if other people have it working :-)

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Dell XPS 8940 SATA and NVMe disk controller not recognized

[Tomasz CEDRO]

On Sun, Apr 4, 2021, 00:10 Karl Dunn  wrote:

> That worked, precisely as it did for you: gpart list shows partitions
> and drives much to my expectations, and Win10 no longer boots.  I can
> boot windows by setting the BIOS config back to RAID.  That's not much
> of a pain.  Now to try installing 12.2-RELEASE on the SSD!
>
> Thank you very much indeed!
>

You may want to boot from windoze iso installer and try "fix boot problems"
when already in SATA controller mode.

If that does not work and machine boots in UEFI mode you may want to
adjust/select the proper EFI-BOOT partition to boot from. Usually this is
the FAT32 partition with EFI boot loader.

If that does not work you may simply re-install windoze from iso installer,
serial number is now installed in BIOS/TPM, so you will have all OS working
in SATA mode :-)

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

[Tomasz CEDRO]

Why so short End-Of-Life? Why so many fast and short releases? What for?

Why pushing problems to production? What was wrong with having one
well tested stable system for a long time?

12.0 was a problematic release. 12.1 brings even more problems.

To be honest X11 Video Acceleration DRM mess and dramatic
Virtualization with VirtualBox brings back my MacBook to the desk
because FreeBSD does not seem to be reliable desktop environment
anymore even on a decent modern machine :-(

Is it really necessary? What happened to FreeBSD? :-(

Tomek


On Tue, Feb 18, 2020 at 12:14 AM FreeBSD Security Officer wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Dear FreeBSD community,
>
> As of February 29, 2020, FreeBSD 12.0 will reach end-of-life and will no 
> longer
> be supported by the FreeBSD Security Team.  Users of FreeBSD 12.0 are strongly
> encouraged to upgrade to a newer release as soon as possible.
>
> The currently supported branches and releases and their expected end-of-life
> dates are:
>
>  +--+
>  |   Branch|   Release|  Release Date |  Estimated EoL  |
>  +-+--+---+-+
>  | stable/12   | N/A  | N/A   | June 30, 2024   |
>  +-+--+---+-+
>  | releng/12.1 | 12.1-RELEASE | November 4, 2019  | 12.2-RELEASE + 3 months |
>  +-+--+---+-+
>  | stable/11   | N/A  | N/A   | September 30, 2021  |
>  +-+--+---+-+
>  | releng/11.3 | 11.3-RELEASE | July 9, 2019  | 11.4-RELEASE + 3 months |
>  +--+
>
> Please refer to https://security.freebsd.org/ for an up-to-date list of
> supported releases and the latest security advisories.
>
> - --
> The FreeBSD Security Team
> -BEGIN PGP SIGNATURE-
>
> iQKTBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAl5LHZNfFIAALgAo
> aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD
> MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n
> 5cIqyA//ROIFtIsEDV5p02FnWClgWu3qxZ4uRyA0usM1DtZPBYjtfsFGdAU+9NvY
> EsUB3rVjWx2HNoHKySFgjLbtGdCNoae45pjLe3UiKgrbQZwXCdUl0d1y+4ZcoR0D
> cdtEY6YWio4kBHTWxd0cgCpe+Cmk3nQRB005qgvMkkCBNBGuZQcQS62CMMis3IWC
> paMcRBmzkh9HMW8e9XN2mFjGJbT2HKzY+y/Qvj3NhxenYgTzQbVwRDz4JPKz7Al+
> aVq2gLEuEgRWNFG+fBnk7qikzmV7JaXI+j/ImZnrMFBDC/ymiQMbQdt0Kxv0TsZF
> ajR18pQyoAONXoJs875HD54/Rj0rQNkKwyZNKuka5+NWR/6d9H52+iytkGqn2DLR
> Jp9slPHBW5ofC7WlgAAeV+S1Et7fWeV96hqDVRUXZstir6hM3hYEdwnQP8aFaYO9
> No+uLd6IAKBtBCK9hxOv6O6lmWjNk4LWQb6keG+zwFDCfnILdfwVE+eML7GqLzQ1
> 5s40M7gZsB//1S27WQOhKS4Vea+68meGOzGv0KkMd4gNuV/cBqVoCj52Muu3O0gK
> nbMuFHptQbL0qhFGzho4chg4TsuXs0lf28BsHYYFeEewEce7gIwCgPLQPIwLQG4h
> cv7KkgwEetngUUlyMaeKu2xCUXTaDJ3KpFkwEcol1oezaWkduwg=
> =viBR
> -END PGP SIGNATURE-
> ___
> freebsd-annou...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-announce
> To unsubscribe, send any mail to "freebsd-announce-unsubscr...@freebsd.org"



-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

[Tomasz CEDRO]

wt., 18 lut 2020, 10:20 użytkownik Steve O'Hara-Smith 
napisał:

> On Tue, 18 Feb 2020 04:23:35 +0100
> Tomasz CEDRO  wrote:
>
> > Why so short End-Of-Life? Why so many fast and short releases? What for?
>
> The new(ish) release and support policy has been announced and well
> documented, this should come as no surprise to anyone.
>
> --
> Steve O'Hara-Smith 
>

True.. but the surprise is the Linux like bleeding edge in BSD and the
quality degradation at a degree that I have just replaced my FreeBSD laptop
with a MacBook :-(

Maybe its a time to give OpenBSD a try..

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

[Tomasz CEDRO]

Hello Ed, thanks for your input :-)

On Tue, Feb 18, 2020 at 3:46 PM Ed Maste  wrote:
> > 12.0 was a problematic release. 12.1 brings even more problems.
>
> The major issue with 12.1 is a problem with the Intel graphics kernel
> module, and fixing that was held up by both 12.0 and 12.1 being
> supported. The problem will automatically resolve once 12.0 is no
> longer supported.
>
> (Yes, I wish we were able to address this issue in a way other than
> waiting for 12.0's EOL, but nobody in the FreeBSD development
> community was able to find the time to do so.)

Ah, in this case 12.0 EoL is highly desired. Now I understand. Thank you :-)

But also as this DRM user (for Intel and AMD) I have experienced the
related hiccups, problems, and problems solutions. It does not look
like a FreeBSD way, but more like Linux way. I never noticed anything
like this before. Sure, I can see this only as the end-user, maybe
tester, I did no commits, so in theory I cannot complain, but it seems
like more experienced kernel people could take part in this kind of
solution architecture and design right from start in order to prevent
avalanche of future problems and problematic solutions that will
generate more problems.

Another problem is the VirtualBox virtualization that is not really
usable anymore. I am aware of closed-source VBox Guest Additions
problem. My VM works fine for a first minute or two but then it stops
when I start working on it. With DRM and Framebuffer X11 drivers so it
does not seem related. It can consume all resources and/or break
graphics (i.e. Enlightenment WM). I have tried various permutations of
configuration and operating systems (mostly Windoze, but also Linux).
I am not sure if I am the only person having this problem as I have
asked some questions before. I know there is BHYVE but its not really
that easy to use as VBox (to be honest I did not manage to run
anything beyond examples). Simple and efficient hypervisor is a must
have nowadays in productivity work.

For a modern workstation a fairly good GPU driver and Virtualization
seems mandatory. Not to mention input devices like Trackpad. I cannot
use them reliably at this time anymore. It worked well in the past.
Thus my question - why create a new release with new features when
there are still basic features missing or incomplete.. I would really
care for productivity in the first place even if its 9.12 release :-)

I really love FreeBSD!! I advocate it in my every project and every
project I am part of. I use it as a base on my servers. It worked
really nice on my desktop, but it does not anymore. I am not really
comfortable to switch to macOS BSD but time is precious and clients
are waiting for the results..

I just wonder:
1. Maybe if Sony uses FreeBSD on their PlayStation with AMD GPU -
could they share back the solution?
2. Maybe Intel could help in development of the DRM architecture? They
have really nice R&D in Poland..

Did anyone try that? :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

[Tomasz CEDRO]

On Tue, Feb 18, 2020 at 3:51 PM Ed Maste  wrote:
>
> On Tue, 18 Feb 2020 at 05:37, Tomasz CEDRO  wrote:
> >
> > Maybe its a time to give OpenBSD a try..
>
> I really don't understand this comment, either. Certainly give OpenBSD
> a try and if it fits your needs better that's great.
>
> As far as I'm aware OpenBSD issues a release every six months and
> supports the most recent two releases, so it seems odd to me to
> complain about FreeBSD's ~1 year minor release support lifetime and 5
> year stable branch support lifetime in that context.

Its more like "lets try if what I need works better over there". Not
really the release timeline.

The release timeline problem is more related with pushing untested
features (and possible avalanche of solutions that introduce yet
another complications that we observe right now).

"The BSD Way", for me, was always about "it works solid or its not
there". Like macOS / iOS.

Unlike "The Linux Way" where things changes upside down from release
to release and each one of them has its own universe of variants. Like
Android.

I am not sure if it is that important if there is a release in 6 month
or 2 years. Not a problem at all. If in two years I get a 5 new
features that work rock solid then it seems a better choice than
getting new features every six months and have more problems on a
production because of that.

If I need to experiment there is a CURRENT branch. For well tested
features I have STABLE. For rock solid "I bet my money on that" I have
a RELEASE. Right?

I did miss the 12.0 EoL kind of fix for DRM, sorry, it seems
reasonable. I am just worried that 12.2-RELEASE will have the same
problems, if not more new problems.

Maybe I should go back to 11 and see how things work over there :-P

Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

[Tomasz CEDRO]

On Wed, Feb 19, 2020 at 8:24 PM Bengt Ahlgren  wrote:
> Tomasz CEDRO  writes:
> > Another problem is the VirtualBox virtualization that is not really
> > usable anymore. I am aware of closed-source VBox Guest Additions
> > problem. My VM works fine for a first minute or two but then it stops
> > when I start working on it. With DRM and Framebuffer X11 drivers so it
>
> My experience is that you have to enable "Use Host I/O Cache" for the
> SATA storage controller, otherwise it will lock up sooner or later.  It
> seems to not be the default.  With it enabled, I don't have any issues.

Nooo way.. that seems to help! Works slow but it works :-)

I have M2 2TB SSD using encrypted ZFS on my FreeBSD laptop.. so
clearly a VirtualBox drivers / config issue not the OS..?

Thank you Bengt for the hint! Trust in FreeBSD restored :-) :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

/usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Tomasz CEDRO]

Hello world :-)

I would like to build a 12-STABLE (/usr/src contains
svn.freebsd.org/base/stable/12) locally on strong machine (24CPU 127GB
RAM 12-1-RELEASE AMD64), then test changes on my local machine
(panasonic toughbook i5 laptop 12.1-RELEASE AMD64). This will be used
for testing kernel patches and driver development/fixes.

The goal is to have separate zroot/ROOT/stable to select and act as
the FreeBSD base. So far I have zroot/ROOT/default to use FreeBSD
12.1-RELEASE. I would like to switch between those to on boot to have
one base system stable for working and another base system for testing
on real environment.

I noticed that simple copy of /boot/kernel does not work on my target
machine. Thus I am trying to create a whole release, put a separate
system base, then on boot select different zfs container base to boot
from. I just love ZFS for that! I may even use snapshots to log and
rollback changes.

Questions:

1. Is it a good build / testing environment? Maybe there is a simpler
/ better way to cross compile binaries and test on another machine?
Both are using 12.1-RELEASE AMD64 installations so far. All /usr/local
should work both with 12.1-RELEASE and 12-STABLE right?

2. When that works, I would like to cross-compile for ARM in a similar
manner, then attach pyOCD + GDB to debug ARM target. I guess that
should work too as above?

3. During /usr/src/release/release.sh I get following error as pasted
below. Does release.sh update /usr/ports just as it snaps from svn or
it will use the /usr/porst that are just there and I need to provide
/usr/ports in a state that will be bindled into a /scratch release?

===>   docproj-2.0_14 depends on file: /usr/local/sbin/pkg - not found
===>  License BSD2CLAUSE accepted by the user
===> Fetching all distfiles required by pkg-1.14.2 for building
===>  Extracting for pkg-1.14.2
===>  License BSD2CLAUSE accepted by the user
===> Fetching all distfiles required by pkg-1.14.2 for building
=> SHA256 Checksum mismatch for freebsd-pkg-1.14.2_GH0.tar.gz.
===>  Refetch for 1 more times files:  freebsd-pkg-1.14.2_GH0.tar.gz
===>  License BSD2CLAUSE accepted by the user
=> freebsd-pkg-1.14.2_GH0.tar.gz doesn't seem to exist in /tmp/distfiles/.
=> Attempting to fetch
https://codeload.github.com/freebsd/pkg/tar.gz/1.14.2?dummy=/freebsd-pkg-1.14.2_GH0.tar.gz
freebsd-pkg-1.14.2_GH0.tar.gz Bad system call (core dumped)
=> Attempting to fetch
http://distcache.FreeBSD.org/ports-distfiles/freebsd-pkg-1.14.2_GH0.tar.gz
freebsd-pkg-1.14.2_GH0.tar.gz Bad system call (core dumped)
=> Couldn't fetch it - please try to retrieve this
=> port manually into /tmp/distfiles/ and try again.
*** Error code 1

Stop.

Any hints and comments are welcome :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Tomasz CEDRO]

Hello Ruslav and thank you for your feedback! :-)

On Sun, Apr 5, 2020 at 3:07 PM Ruslan Garipov wrote:
> On 4/4/2020 7:50 PM, Tomasz CEDRO wrote:
> > 1. Is it a good build / testing environment? Maybe there is a simpler
> > / better way to cross compile binaries and test on another machine?
> > Both are using 12.1-RELEASE AMD64 installations so far. All /usr/local
> > should work both with 12.1-RELEASE and 12-STABLE right?
> Both machines have the same architecture, therefore it is not a cross
> build, I believe.  For my direct builds (both build and consumer
> machines are x86-64) I use the procedure described in the handbook
> (``23.6. Tracking for Multiple Machines''[1]).

I know that method, thank you :-) But I also want to try out the
binary release, which seems a bit more flexible to have just
everything in one place, may be used to install on an external machine
without NFS access, etc :-)

It would be also nice to know the time cost of those two methods, so I
want to verify :-)


> > 3. During /usr/src/release/release.sh I get following error as pasted
> > below. Does release.sh update /usr/ports just as it snaps from svn or
> > it will use the /usr/porst that are just there and I need to provide
> > /usr/ports in a state that will be bindled into a /scratch release?
> A quote from release(7) man page:
>
> release.sh checks out the src/, ports/, and doc/ trees to CHROOTDIR...
>
> Therefore, release(7) "ignores" /usr/ports and uses
> ${CHROOTDIR}/usr/ports.  My build machine doesn't have access to the
> Internet, therefore, I have to define the PORTS_UPDATE_SKIP variable and
> provide ports tree into the ${CHROOTDIR}/usr/ports before
> I will call /usr/src/release/release.sh.

Okay, so the build uses totally separate CHROOT in /scratch? I wonder
if that "Bad System Call" is caused by my Host tools or the CHROOT
tools?

It looks like the /scratch has its own compiled in tools not a copy
from my host?

# diff -u /usr/bin/fetch /scratch/usr/bin/fetch
Binary files /usr/bin/fetch and /scratch/usr/bin/fetch differ


> > ===>   docproj-2.0_14 depends on file: /usr/local/sbin/pkg - not found
> > ===>  License BSD2CLAUSE accepted by the user
> > ===> Fetching all distfiles required by pkg-1.14.2 for building
> > ===>  Extracting for pkg-1.14.2
> > ===>  License BSD2CLAUSE accepted by the user
> > ===> Fetching all distfiles required by pkg-1.14.2 for building
> > => SHA256 Checksum mismatch for freebsd-pkg-1.14.2_GH0.tar.gz.
> > ===>  Refetch for 1 more times files:  freebsd-pkg-1.14.2_GH0.tar.gz
> > ===>  License BSD2CLAUSE accepted by the user
> > => freebsd-pkg-1.14.2_GH0.tar.gz doesn't seem to exist in /tmp/distfiles/.
> > => Attempting to fetch
> > https://codeload.github.com/freebsd/pkg/tar.gz/1.14.2?dummy=/freebsd-pkg-1.14.2_GH0.tar.gz
> > freebsd-pkg-1.14.2_GH0.tar.gz Bad system call (core dumped)
> /usr/src/release/release.sh defines DISTDIR=/tmp/distfiles when it
> installs the textproc/docproj port or a port from the ${EMBEDDEDPORTS}.
>
> As for why fetch(1) fails with bad system call under chrooted
> environment -- I don't know.  I failed on a port fetching only if I
> hadn't provided all necessary distfiles.  You have checksum error
> message which is causing refetching of the ports-mgmt/pkg port.
> Therefore, I believe
> ${CHROOTDIR}/tmp/distfiles/freebsd-pkg-1.14.2_GH0.tar.gz exists on your
> file system (remained from a previous fetch try?)...  May be you should
> try fetch(1) from the chrooted environment manually, to get any content?

This "Bad System Call" stops me from proceeding. I did place by hand
the required package in the right place, then it built ok, then I got
that "Bad System Call" again on install :-(

How can I get the debug symbols in /scratch binaries?

So far I can just show:
[New LWP 100764]
Core was generated by `/usr/bin/fetch -Fpr -S 3405355
http://distcache.FreeBSD.org/ports-distfiles/free'.
Program terminated with signal SIGSYS, Bad system call.
#0  0x0008003c1bca in ?? ()
(gdb) bt
#0  0x0008003c1bca in ?? ()
#1  0x00080031d144 in ?? ()
#2  0x00080031d260 in ?? ()
#3  0x0008 in ?? ()
#4  0xb650b69b3fd03fb8 in ?? ()
#5  0x7fffdd40 in ?? ()
#6  0x7fffe64c in ?? ()
#7  0x000800e1d000 in ?? ()
#8  0x002091e0 in ?? ()
#9  0x7fffdc80 in ?? ()
#10 0x7fffdc40 in ?? ()
#11 0x00080031d2f9 in ?? ()
#12 0x000800e1d000 in ?? ()
#13 0x7fffdd40 in ?? ()
#14 0x in ?? ()


Thank you! :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Tomasz CEDRO]

On Sun, Apr 5, 2020 at 4:59 PM Ruslan Garipov wrote:
> I'm sorry, I forgot to ask how do you call /usr/src/release/release.sh?
> Do you pass a configuration file to this script?
>
> By default /usr/src/release/release.sh checks out the source tree for
> the CURRENT branch (svn://svn.FreeBSD.org/base/head@rHEAD).  In this
> case (if you doesn't change it) chrooted environment definitely will
> fail to run on STABLE and/or RELEASE.
>
> May be it's easy for you to use `make release` directly.

Case solved! =)

I wrongly assumed that release will simply update this svn repo that I
am working on.. but it fetches HEAD.. so I was trying to build
13/HEAD/CURRENT on 12/STABLE/RELEASE that have different ABI thus bad
syscall.. and I need CURRENT to build CURRENT, right? :-)

I will provide a release.conf, make.conf, src.conf and maybe KERNCONF
if I need something beyond GENERIC. For now I just need to work with
12-STABLE. Good hint! :-)

Thank you Ruslan!! :-)

Tomek

ps/2: Can I provide a patch that will print out what actually is being
fetched by release.sh? That could save some time for first time users
:-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Tomasz CEDRO]

On Sun, Apr 5, 2020 at 7:53 PM Ruslan Garipov wrote:
> > I wrongly assumed that release will simply update this svn repo that I
> > am working on.. but it fetches HEAD.. so I was trying to build
> > 13/HEAD/CURRENT on 12/STABLE/RELEASE that have different ABI thus bad
> > syscall.. and I need CURRENT to build CURRENT, right? :-)
> I believe in order to build the source tree you just need a compatible
> toolchain.  So you can build the source tree for 13.0-CURRENT on
> 12.1-RELEASE system.  But you need CURRENT to **run** userland with ABI
> from the CURRENT.

Long story short I need 13-CURRENT to create a 13-CURRENT release with
release(7) because on 12-STABLE/RELEASE chroot with 13-CURRENT does
not work. I need to see how it works with `make release` :-)


> Once again: for native build `make release` may be quite easy and fast.
> release(7) guarantees "absolutely clean build environment".

Will try that `make release` as well, also for 13-CURRENT on
12-STABLE, thank you! Also will compare the time cost with the one
presented below :-)


Creating a "release" also has this advantage that I have memstick
images that I can boot from directly, test what I need, even no need
to install :-)

Here are my build times, for a release for AMD64/12-STABLE, I did not
select DOC nor PORTS to build, only Kernel and Base :-)

BUILD HOST (~$500): HP PROLIANT DL380G7X (HDD 1TB, 128GB RAM, 24vCPU =
2 x Intel Xeon X5660 @2.8GHz = 2 PACKAGES x 6 CORES x 2 HW THREADS )
INTERNET: 600/60MBit

time make clean buildkernel (16x speedup with SMP):
2472.027u 291.657s 46:34.54 98.8%   38592+3123k
195123+3315182io 80167pf+0w
-j122355.140u 282.807s 3:40.12 1198.4%  38509+3121k
190142+3361605io 71356pf+0w
-j243672.641u 382.254s 2:54.85 2319.0%  39837+3149k
218567+3361605io 64857pf+0w
-j483722.707u 352.940s 3:07.10 2178.3%  40328+3169k
214359+3361607io 66526pf+0w

time make clean buildworld (12.5x speedup with SMP):
32223.598u 1940.942s 9:28:07.59 100.2% 46920+3430k
563493+3074126io 234706pf+0w
-j1233644.438u 1818.147s 54:46.68 1078.9% 47324+3449k
485257+3255853io 236896pf+0w
-j2450728.732u 2556.953s 45:06.66 1968.6% 47556+3455k
560905+3255862io 229433pf+0w
-j4851129.166u 2454.564s 44:38.12 2000.7% 47630+3458k
525602+3255854io 210237pf+0w

release.sh (seems to auto-adjust -j optimization and below 2h looks
really cool):
94556.462u 5583.273s 1:43:14.24 1616.6% 50234+3336k
1457023+16921354io 615421pf+0w
-j12   94477.001u 5577.692s 1:42:59.60 1619.1% 50251+3337k
1463964+16932952io 617689pf+0w
-j24   94480.274u 5574.117s 1:43:38.89 1608.8% 50213+3336k
1468685+16931170io 617425pf+0w
-j48   94588.653u 5569.909s 1:43:10.62 1617.9% 50211+3336k
1460546+16925145io 611229pf+0w

These times may be even smaller when SSD is used instead of HDD. Also
I wonder how to utilize all RAM to speed up the compilation because I
can see 8..34GB utilization while the rest of 128GB remains unused. I
saw some ramdisk tricks I need to try that as well :-)

Best regards :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Tomasz CEDRO]

On Wed, Apr 8, 2020 at 8:19 PM Ruslan Garipov wrote:
> > I need to see how it works with `make release` :-)
> This is what I meant when saying "you can build the source tree for
> 13.0-CURRENT on 12.1-RELEASE"; sorry if I've confused you.

No worries, my little confusion came from `make release` being a bit picky:
1. I need to buildworld first (can use -j switch, make release will
not call it).
2. I need to buildkernel first (can use -j switch, make release will
not call it).
3. Only then I can run `make release` (cannot use -j switch).

I get as good result as I need with memstick and iso images in around
19 minutes plus I can build CURRENT that way.. now I may be ready to
cross-compile :-)

3858.923u 331.683s 19:19.24 361.4%  171+561k 499674+1215072io 131833pf+0w


> Check ``Building with release.sh on -STABLE'' thread[1] on the forum.
> May be it can help you.

Thank you for the reference! :-)


> "2h looks really cool" because release(7) may build chrooted build
> environment, where it then may build port(s) and builds the target.  My
> Xeons usually spends 1.5 hours on clean release(7) (with 16 make(1)
> jobs).

A bit better but very similar result, thanks for reference.. and the
SSD hint :-)

With this power I can compile a clean firmware for my projects based
on ARM mbedOS  in 2 minutes instead 12 minutes (as compared to laptop
build) and connect the build to a git hook.. then speeding up a bit
could return a binary right away as a result of git push :-) :-)

In a free moment it would be fun to play with FreeBSD on ARM.. I have
tried that several times before but with no luck.. and I really have
different boards around to test :-)

Again GREAT THANK YOU Ruslan for your time support and all hints!! :-)

Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Tomasz CEDRO]

Summing up the time cost for a clean svn co and make buildkernel
buildworld release is around 75minutes while the chroot build with
release(7) is around 100minutes for my hardware setup. Builds using
make are more reasonable for driver fixes because then I can only
rebuild small part of the code which will result in much shorter build
times. Very nice to experience :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: URGENT: Microsoft overwrites boot loader!

[Tomasz CEDRO]

czw., 16 lip 2020, 22:20 użytkownik Don Wilde napisał:

> That's the last time I will allow this, and I'm calling those [deleted]s
> tomorrow to give them a piece of my mind. After that I will erase every
> vestige of that obscene OS from my disk.
>

I did that long time ago :-) I have one dedicated laptop if I am really
forced to use M$ crap but by all means necessary I avoid it for more than
15 years :-)

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

PKG bootstrap problem on FreeBSD 11.0-RELEASE-p1

[Tomasz CEDRO]

Hey, I have just installed 11.0-RELEASE-p1 r306420 and I cannot
bootstrap the PKG :-(

Bootstrapping pkg from
pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/quarterly, please wait...
Error fetching.

Both IP and DNS are working..

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: PKG bootstrap problem on FreeBSD 11.0-RELEASE-p1

[Tomasz CEDRO]

After make install from ports-mgmt/pkg update and install works fine.

Clearly problem with bootstrap only.

Is this a bug or feature? :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: PKG bootstrap problem on FreeBSD 11.0-RELEASE-p1

[Tomasz CEDRO]

On Thu, Oct 27, 2016 at 4:33 PM, Tomasz CEDRO  wrote:
> After make install from ports-mgmt/pkg update and install works fine.
> Clearly problem with bootstrap only.

Sorry! INSTALL DOES NOT WORK TOO. "Connection reset by peer". Server
problem then..?

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: PKG bootstrap problem on FreeBSD 11.0-RELEASE-p1

[Tomasz CEDRO]

Ugh, I am in a new place, some filtering on the wire it looks, no
problem after VPN to a different location.

FALSE ALERT SORRY! :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: PKG bootstrap FreeBSD 11.0 / VBox NAT problem

[Tomasz CEDRO]

Just for the curious. I am testing on VirtualBox (Version 5.1.8
r111374 (Qt5.5.1), macOS 10.12.1 host). Cannot bootstrap PKG on a host
with NAT enabled.I have noticed this problem occurs only when NAT is
enabled in VBox. When I use Bridged interface there is no problem. I
have noticed that outgoing packet following RST response has invalid
checksum. That may be VBox NAT problem..? Maybe someone noticed
similar behavior..

https://www.virtualbox.org/ticket/16126

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

[Tomasz CEDRO]

Hello!

I have noticed that I cannot use Xorg anymore on UEFI box with 11.0-RELEASE.
I get (EE) no screens found, before Xorg terminates.
X Server 1.17.4 (RELEASE 2015-10-28).

This happens on my new HYPERBOOK SL502VR (P650RP6-G) with nVidia
GTX1060 and INTEL and VESA does not finding any screen.

This also happens on VirtualBox when system is installed with UEFI enabled.

I had no problem starting X on a BIOS box with no UEFI.

Any hints on how to make it work? :-)

Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

[Tomasz CEDRO]

On Wed, Jan 4, 2017 at 3:47 PM, Tomasz CEDRO  wrote:
> I have noticed that I cannot use Xorg anymore on UEFI box with 11.0-RELEASE.
> I get (EE) no screens found, before Xorg terminates.
> X Server 1.17.4 (RELEASE 2015-10-28).

Some clue: DO NOT USE VESA DRIVER! USE SCFB ON UEFI HARDWARE :-)

https://wiki.freebsd.org/Graphics/SCFB

https://wiki.freebsd.org/Graphics

Still, would be nice to get at least Intel working, nVidia would be perfect! :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

[Tomasz CEDRO]

On Wed, Jan 4, 2017 at 5:08 PM, Tomasz CEDRO  wrote:
> Some clue: DO NOT USE VESA DRIVER! USE SCFB ON UEFI HARDWARE :-)

Although SCFB driver did some switch I have black screen both on
laptop and virtualbox..

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

[Tomasz CEDRO]

On Wed, Jan 4, 2017 at 5:25 PM, Tomasz CEDRO  wrote:
> Although SCFB driver did some switch I have black screen both on
> laptop and virtualbox..

It was some stuff loading really long in the background. After
recreating the setup it works!

You can use `Xorg -configure` then replace vesa with scfb and move cfg
to /etc/X11/xorg.conf.

USE SCFB ON UEFI HARDWARE INSTEAD VESA AS FALLBACK! :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

[Tomasz CEDRO]

On Wed, Jan 4, 2017 at 5:54 PM, Tomasz CEDRO  wrote:
> USE SCFB ON UEFI HARDWARE INSTEAD VESA AS FALLBACK! :-)

this also only works as root.. :\

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

if_iwm crashes kernel when loaded from /boot/loader.conf

[Tomasz CEDRO]

Hello,

I noticed a problem when loading if_iwm from /boot/loader.conf kernel
crashes as it cannot load module firmware dead loop occurs. Adding
iwm8000Cfw before if_iwm does not help.

Loading if_iwm on a running system works fine and gives operational wifi.

Intel Corporation Wireless 8260 class=0x028000 card=0x10108086
chip=0x24f38086 rev=0x3a hdr=0x00

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: crashes after upgrade to 11.1-RELEASE AMD64 / libgcc5

[Tomasz CEDRO]

Here too! I did a fresh install on a second partition the same machine, no
problem observed.. for some reason freebsd-upgrade -r fails to create a
stable system or there is some sort of base/pkg mismatch after...

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

On Sep 13, 2017 15:58, "Mr. Binary" <01100011011001...@gmail.com> wrote:

Hey!

I have upgraded from 11.0 to 11.1-RELEASE, I get constantly crashing
applications, is web browser.. this may be related to libgcc5.. any
hints how to prevent?

Firefox / Chrome / Iridium GTK, Otter QT5..

Program received signal SIGSEGV, Segmentation fault.
0x000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1
(gdb) bt
#0  0x000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1
#1  0x in ?? ()

Program received signal SIGSEGV, Segmentation fault.
0x000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1

...

--
0110001101100100
___
freebsd-questi...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

automount usb msdosfs no partition table

[Tomasz CEDRO]

Hello world :-)

I need to configure automount for a testing machine. It seems to work
fine, except for two issues:

1. Mount point does not disappear after device disappears, what makes
things harder to script when device is gone. automount -c does not
remove the mountpoint, only restarting the service does. It is a bug
or feature?

2. Automounter does not mount USB Pendrive / MSDOSFS devices that does
not have a parition table. Some USB Drives does not have valid
partition table, they appear as /dev/da0 and can be mounted with
mount_msdosfs /dev/da0 /mnt, but they are not recognised by
automounter.. how can I make it work with such devices?

Any hints appreciated :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: automount usb msdosfs no partition table

[Tomasz CEDRO]

i cannot format that device, as its the "firmware feature" that it has no
partition table.. i would have to fix the firmware.. but it would be nice
to automount it anyway as macos, linux and windoze can :-)

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: automount usb msdosfs no partition table

[Tomasz CEDRO]

On Mon, Oct 9, 2017 at 8:59 PM, Scott Bennett  wrote:
> Tomasz CEDRO  wrote:
>> i cannot format that device, as its the "firmware feature" that it has no
>> partition table.. i would have to fix the firmware.. but it would be nice
>> to automount it anyway as macos, linux and windoze can :-)
>  Well, put a partition table onto it, then.  You can use either gpart(8)
> or fdisk(8) to do that and to create a slice, and then use newfs_msdos(8) to
> create the file system.
>  I understood from your previous message that you wanted to create a FAT32
> file system on /dev/da0 rather than on /dev/da0s1, which meant on the bare
> device rather than on a slice.  Otherwise, create the partition table, create
> a slice, and proceed.

The problem is device has hardcoded filesystem, with no partition
table, all this is created by firmware on device boot, cannot get
formatted nor partitioned.. I can mount it by hand.. but it does not
get automounted.. and exactly this part is the problem and quest here
:-) :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"