Re: pkg OSVERSION problem

2018-02-04 Thread O. Hartmann 
Am Sat, 27 Jan 2018 10:23:28 +0100
"Ronald Klop"  schrieb:

> On Sat, 27 Jan 2018 08:36:58 +0100, O. Hartmann   
> wrote:
> 
> > Am Thu, 25 Jan 2018 21:38:27 +0100
> > Jan Kokemüller  schrieb:
> >  
> >> On 25.01.2018 21:19, Ronald Klop wrote:  
> >> > I know there should be multiple updates of packages.
> >> > Even with -o OSVERSION it does not give any new pkgs anymore.
> >> > What will help this?  
> >>
> >> I've just had the same issue and solved it by forcefully updating the
> >> package database:
> >>
> >> # pkg -o OSVERSION=1200056 update -f
> >> # pkg -o OSVERSION=1200056 upgrade
> >>
> >>
> >> -Jan
> >> ___
> >> 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"  
> >
> > Thanks,
> >
> > I'll give it a try.
> >
> > regards,
> >
> > Oliver
> >  
> 
> Thanks also. It kicked pkg upgrade into upgrading again, but in the end I  
> missed libdl.so (clang 6?) which was fixed by updating my system to  
> 1200056 anyway. Otherwise Firefox wouldn't start.
> So although the OSVERSION check is annoying it does warn for actual  
> problems.
> 
> Regards,
> Ronald.
> ___
> 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"

I tried and it worked as expected!

Thanks a lot.

Oliver

-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgpsgu77Zhmpo.pgp
Description: OpenPGP digital signature

Re: Lenovo T470s Questions

2018-02-04 Thread Tomoaki AOKI 
Hi, Michael.
Noticed your previous post after sending mine. :-)

Fallback code for older ThinkPads looks reasonable and gives no new
(not known) regression.

As I don't have new (0x200) ThinkPads (T420 is my latest),
I cannot review and test for new protocol and functionality.
Sorry.

Just FYI, `acpidump -d -t DSDT | fgrep MHKV` on my T420 claims
"Method (MHKV, 0, NotSerialized)" only. So it would go fallback way.

Preferrably, user(s) of latest (i.e, T480) models pops in and report
this worked or not. [Is there one more protocol like 0x300?]


Thanks for your work!


On Fri, 2 Feb 2018 12:38:47 +0100
Michael Gmelin  wrote:

> 
> 
> On Fri, 2 Feb 2018 20:23:32 +0900
> Tomoaki AOKI  wrote:
> 
> > Not 100% sure but possibly some (one?) EisaId are (is) missing in
> > ibm_ids definition of sys/dev/acpi_support/acpi_ibm.c.
> > Currently it contains "IBM0068" and "LEN0068".
> > 
> > Run `acpidump -d -t | fgrep EisaId` as root on your T470s and look for
> > EisaId something other than...
> > 
> >   IBM0068
> >   LEN0068
> >   IBM3780
> >   PNP
> > 
> > If there's something new, insert them (it) to 
> >   static char*ibm_ids[] = {"IBM0068", "LEN0068", NULL};
> > line of sys/dev/acpi_support/acpi_ibm.c, between "LEN0068" and "NULL".
> > 
> > If there's none, it's over my hand. :-(
> > There could be some incompatibility, like struct member change etc.
> 
> Hi Tomoaki,
> 
> Could you please take a look at this?
> 
> https://reviews.freebsd.org/D14103
> 
> Thanks,
> Michael
> 
> 
> 
> > 
> > See my web page [1] of part "Note for limitations of ACPI in ThinkPad
> > T420" and The FreeBSD Forums' thread noted there [2] for more info.
> > Although old, but part of them can be useful.
> > 
> > [1] http://www.dec.sakura.ne.jp/~junchoon/machine/freebsd-e.html
> > [2] https://forums.freebsd.org/threads/26759/
> > 
> > 
> > On Thu, 1 Feb 2018 21:13:05 -0500
> > Bridger Dyson-Smith  wrote:
> > 
> > > Hi list and Michael -
> > > 
> > > I received a T470s at work and decided to jump into the CURRENT end
> > > of the FreeBSD pool. I have a weird acpi_ibm issue and I'm not sure
> > > where to start trying to diagnose the issue.
> > > 
> > > # uname -a
> > > FreeBSD spanner 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328126: Thu
> > > Jan 18 15:25:44 UTC 2018 r...@releng3.nyi.freebsd.org:/
> > > usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
> > > 
> > > I've loaded acpi_ibm via /boot/loader.conf:
> > > acpi_ibm_load="YES"
> > > 
> > > and the module shows as being loaded:
> > > # kldstat | grep acpi_ibm
> > > 81 0x8278e000 7570 acpi_ibm.ko
> > > 
> > > However, I don't have any of the sysctl knobs available; e.g.
> > > # sysctl -a | grep acpi_ibm
> > > #
> > > 
> > > or
> > >  # sysctl dev.acpi_ibm.0.fan_speed
> > > sysctl: unknown oid 'dev.acpi_ibm.0.fan_speed'
> > > 
> > > I've (tried) to look through the commit messages on svn-src-head,
> > > but I'm not seeing anything specifically related to acpi work, or I
> > > just don't know what I'm looking at (a definite possibility).
> > > 
> > > Would someone be able to provide a bit of debugging direction here?
> > > Reviewing `dmesg -a` doesn't tell me anything specific about
> > > acpi_ibm.
> > > 
> > > Thanks in advance for your time and trouble.
> > > Bridger
> > > ___
> > > 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" 
> > 
> > 
> 
> 
> 
> -- 
> Michael Gmelin
> ___
> 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"
> 


-- 
Tomoaki AOKI
___
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"

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-04 Thread O. Hartmann 
Am Sun, 4 Feb 2018 12:28:54 +0100
"O. Hartmann"  schrieb:

> Am Sat, 3 Feb 2018 14:04:17 +0100
> Dimitry Andric  schrieb:
> 
> > On 3 Feb 2018, at 11:43, O. Hartmann  wrote:  
> > > 
> > > Am Tue, 30 Jan 2018 00:09:07 +0100
> > > Dimitry Andric  schrieb:
> > >> On 30 Jan 2018, at 00:01, Dimitry Andric  wrote:
> > >>> On 29 Jan 2018, at 19:39, O. Hartmann  wrote:   
> > >>>  
> >  
> >  Last weekend I updated a CURRENT server to recent CURRENT, > r328400 
> >  and
> >  performed updates of the ports tree. Since Sunday, I receive 
> >  segmenatation
> >  faults (SIG 11) when accessing the server, especially with setup of 
> >  nextcloud,
> >  refdb, phpldapadmin and any other access with LDAP backend (all 
> >  https).
> > ...  
> > > Starting program: /usr/local/sbin/httpd -X
> > > [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] 
> > > (2)No such
> > > file or directory: AH00075: Failed to enable the 'httpready' Accept 
> > > Filter [Sat Feb
> > > 03 11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No 
> > > such file or
> > > directory: AH00075: Failed to enable the 'dataready' Accept Filter [New 
> > > LWP 101096
> > > of process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of 
> > > process
> > > 59320] [New LWP 101103 of process 59320]
> > > [New LWP 101102 of process 59320]
> > > [New LWP 101110 of process 59320]
> > > [New LWP 101107 of process 59320]
> > > [New LWP 101098 of process 59320]
> > > [New LWP 101099 of process 59320]
> > > [New LWP 101108 of process 59320]
> > > [New LWP 101112 of process 59320]
> > > [New LWP 101101 of process 59320]
> > > [New LWP 101104 of process 59320]
> > > [New LWP 101097 of process 59320]
> > > [New LWP 101106 of process 59320]
> > > [New LWP 10 of process 59320]
> > > [New LWP 101100 of process 59320]
> > > [LWP 101096 of process 59320 exited]
> > > 
> > > Thread 11 received signal SIGSEGV, Segmentation fault.
> > > [Switching to LWP 101108 of process 59320]
> > > 0x000802300382 in ?? () from 
> > > /usr/local/lib/php/20131226-zts/opcache.so
> > 
> > Run the "backtrace" command there, please.  If it doesn't give any
> > function names, try setting WITH_DEBUG=1 in the environment, then
> > rebuilding the mod_php56 port (and optionally also the php56 and
> > apache24 ports themselves), to add debug info.
> > 
> > -Dimitry
> >   
> www/mod_php56: env WITH_DEBUG=1 make reinstall (prior to that, I had to "pkg 
> delete" the
> port www/mod_php56 first). When having mod_php56 rebuilt with DEBUG on as 
> recommended
> and performing command sequence to enter gdb, run -X, the Apache 2.4 now 
> crashes
> immediately and not when the URL is called by the browser triggering the 
> fault. This is
> what I get then:
> 
> bt
> #0  0x00080208b382 in ?? () from 
> /usr/local/lib/php/20131226-zts/opcache.so
> #1  0x000802088e1a in ?? () from 
> /usr/local/lib/php/20131226-zts/opcache.so
> #2  0x000802085f12 in ?? () from 
> /usr/local/lib/php/20131226-zts/opcache.so
> #3  0x000802085cf3 in zend_accel_script_optimize ()
> from /usr/local/lib/php/20131226-zts/opcache.so #4  0x00080207a393 in ?? 
> ()
> from /usr/local/lib/php/20131226-zts/opcache.so #5  0x0008020799d6 in
> persistent_compile_file () from /usr/local/lib/php/20131226-zts/opcache.so #6
> 0x00080195d33c in zend_execute_scripts ()
> from /usr/local/libexec/apache24/libphp5.so #7  0x0008018f47a3 in
> php_execute_script () from /usr/local/libexec/apache24/libphp5.so #8
> 0x0008019f1015 in ?? () from /usr/local/libexec/apache24/libphp5.so #9
> 0x002563d7 in ap_invoke_handler () #10 0x0029005d in
> ap_process_async_request () #11 0x0028ca2d in 
> ap_process_http_connection () #12
> 0x0026e3b7 in ap_run_process_connection () #13 0x00080152827f in 
> ?? ()
> from /usr/local/libexec/apache24/mod_mpm_event.so #14 0x000801527e11 in 
> ?? ()
> from /usr/local/libexec/apache24/mod_mpm_event.so #15 0x0008005d2476 in 
> ?? ()
> from /lib/libthr.so.3 #16 0x in ?? ()
> Backtrace stopped: Cannot access memory at address 0x7fffde1ef000
> 
> 

I forgot to mention, that I already have rebuilt www/apache24 via portmaster 
-df and I
also have rebuild all php ports/modules installed including php56 itself (but 
without
debugging, it takes a while on that box).


-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgpGqL2iZgMnS.pgp
Description: OpenPGP digital signature

Re: HEAD amd64 seems unhappy

2018-02-04 Thread David Wolfskill 
On Sat, Feb 03, 2018 at 08:38:22PM -0600, Josh Paetzel wrote:
> --- all_subdir_lib/libngatm ---
> /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of 
> comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal
> se [-Werror,-Wtautological-type-limit-compare]
> if (portno == 0 || portno > 0x)
>~~ ^ ~~
> 1 error generated.
> *** [cc_port.o] Error code 1
> 
> This code hasn't changed in ages so I can only assume it's clang or such.
> 

My update of head/amd64 from r328830 to r328838 was rather quick
and quite painless this morning (00:05:15 elapsed time... on my
laptop; build machine was < 00:05:00, as I didn't need to re-authenticate
to sudo for the shutdown).

So: I didn't see the issue.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
The circus around that memo helps confirm that Mr. Trump is unfit for office.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-04 Thread Maurizio Vairani 
2018-01-29 18:38 GMT+01:00 John Nielsen :

> [ resending from correct email address ]
>
> On Jan 29, 2018, at 6:05 AM, Maurizio Vairani 
> wrote:
>
> I am running
> # uname
> -a
>
> FreeBSD  12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52
> UTC 2018 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.
> amd64/sys/GENERIC
> amd64
>
> After compiling the kernel module as discussed in this thread :
> https://lists.freebsd.org/pipermail/freebsd-current/
> 2018-January/068272.html
>
> I can boot FreeBSD via iSCSI using iPXE. But when the isboot, the iSCSI
> boot driver version 0.2.13, starts I receive a panic:
> https://mega.nz/#!tkVwBBKA!PUj14-Za6KCNaoo9hxuXORRLQoWkb4LMvTdUA1BorD4
>
> Any idea?
>
>
> Bummer!
>
> Aoyama-san-
>
> Are you still maintaining isboot? Can you help debug this issue on FreeBSD
> 12-CURRENT?
>
> Once we get it working I will update the port with whatever is needed and
> send you the patches in case you'd like to cut a new release.
>
> Thank you!
>

I have solved the issue changing the function isboot_ifup() in the source
file isboot.c.

static int
isboot_ifup(struct ifnet *ifp)
{
struct socket *so;
struct ifreq ifr;
struct thread *td;
int error;

td = curthread;
error = socreate(AF_INET, , SOCK_DGRAM, 0, td->td_ucred, td);
if (error) {
printf("%s: socreate, error=%d\n", __func__, error);
return (error);
}

/* boot NIC */
memset(, 0, sizeof(ifr));
strlcpy(ifr.ifr_name, ifp->if_xname, sizeof(ifr.ifr_name));

/* set IFF_UP */
error = ifioctl(so, SIOCGIFFLAGS, (caddr_t), td);
if (error) {
printf("%s: ifioctl SIOCGIFFLAGS, error=%d\n", __func__, error);
return (error);
}

ifr.ifr_flags |= IFF_UP;
error = ifioctl(so, SIOCSIFFLAGS, (caddr_t), td);
if (error) {
printf("%s, ifioctl SIOCSIFFLAGS, error=%d\n", __func__, error);
return (error);
}
soclose(so);
return (0);
}

I have added a socket in the ifioctl() call as in the
/usr/src/sys/nfs/bootp_subr.c source.
Please let me know if you prefer a patch.
--
Regards,
Maurizio
___
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"

Re: HEAD amd64 seems unhappy

2018-02-04 Thread Dimitry Andric 
On 4 Feb 2018, at 03:38, Josh Paetzel  wrote:
> 
> --- all_subdir_lib/libngatm ---
> /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of 
> comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal
> se [-Werror,-Wtautological-type-limit-compare]
>if (portno == 0 || portno > 0x)
>   ~~ ^ ~~
> 1 error generated.
> *** [cc_port.o] Error code 1
> 
> This code hasn't changed in ages so I can only assume it's clang or such.

This is because of r328816, which requires you to update your toolchain
to at least r328381.  E.g. please run either "make buildworld" or "make
kernel-toolchain" before building your kernel.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-04 Thread Andriy Gapon 
On 04/02/2018 11:50, Maurizio Vairani wrote:
> I have added a socket in the ifioctl() call as in the
> /usr/src/sys/nfs/bootp_subr.c source.
> Please let me know if you prefer a patch.

A patch here https://reviews.freebsd.org/ would be the best.

-- 
Andriy Gapon
___
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"

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

2018-02-04 Thread O. Hartmann 
Am Sat, 3 Feb 2018 11:17:06 +0100
"O. Hartmann"  schrieb:

> Am Sat, 3 Feb 2018 11:10:53 +0300
> Vladimir Zakharov  schrieb:
> 
> > Hello, Oliver!
> > 
> > On Fri, Feb 02, 2018, O. Hartmann wrote:  
> > > On Thu, 1 Feb 2018 12:10:30 +0300
> > > Vladimir Zakharov  wrote:
> > > 
> > > > Hello!
> > > > 
> > > > For some time (about a week) building and installing kernel fails with
> > > > the error "Variable OBJTOP is recursive." when going to build/install
> > > > module from ports.
> > > > 
> > > > Last successful build was at r328426. Next build at r328527 failed and
> > > > still broken at r328649.
> > > > 
> > > > Without PORTS_MODULES building and installing kernel succeeds. Another
> > > > workaround: ignore error and build/install module directly from ports.
> > > > 
> > > 
> > > I have had the very same issue!
> > > 
> > > You need to perform a "installworld" first (just comment out the 
> > > PORTS_MODULES=
> > > parts of /etc/src.conf or /etc/make.conf, buildworld and buildkernel 
> > > (maybe not
> > > a full buildworld, but I do not know the state of your source tree) and 
> > > perform
> > > a regular installation of the world.  It could be something easier by 
> > > direkctly
> > > install-only the mk-portions, but recently, some changes to world (LLVM) 
> > > made
> > > it worth anyway to buildworld.
> > > 
> > > As recommended by others earlier on this list according to this subject, 
> > > this
> > > procedure makes the problem go away.
> > 
> > Thanks for your answer. Unfortunately, this didn't help.
> >   
> 
> You are correct! I made a mistake and had the portions still commented out. 
> I'm very
> sorry.
> 
> This remains a bug!
> 

This problem has been introduced with

svn commit: r328489 - head/sys/conf

The the appropriate list for reference.

oh
-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgpFzlyQrHsoq.pgp
Description: OpenPGP digital signature

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-04 Thread O. Hartmann 
Am Sat, 3 Feb 2018 14:04:17 +0100
Dimitry Andric  schrieb:

> On 3 Feb 2018, at 11:43, O. Hartmann  wrote:
> > 
> > Am Tue, 30 Jan 2018 00:09:07 +0100
> > Dimitry Andric  schrieb:  
> >> On 30 Jan 2018, at 00:01, Dimitry Andric  wrote:  
> >>> On 29 Jan 2018, at 19:39, O. Hartmann  wrote:  
>  
>  Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and 
>  performed
>  updates of the ports tree. Since Sunday, I receive segmenatation faults 
>  (SIG 11)
>  when accessing the server, especially with setup of nextcloud, refdb, 
>  phpldapadmin
>  and any other access with LDAP backend (all https).  
> ...
> > Starting program: /usr/local/sbin/httpd -X
> > [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] 
> > (2)No such
> > file or directory: AH00075: Failed to enable the 'httpready' Accept Filter 
> > [Sat Feb 03
> > 11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No such 
> > file or
> > directory: AH00075: Failed to enable the 'dataready' Accept Filter [New LWP 
> > 101096 of
> > process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of process 
> > 59320]
> > [New LWP 101103 of process 59320]
> > [New LWP 101102 of process 59320]
> > [New LWP 101110 of process 59320]
> > [New LWP 101107 of process 59320]
> > [New LWP 101098 of process 59320]
> > [New LWP 101099 of process 59320]
> > [New LWP 101108 of process 59320]
> > [New LWP 101112 of process 59320]
> > [New LWP 101101 of process 59320]
> > [New LWP 101104 of process 59320]
> > [New LWP 101097 of process 59320]
> > [New LWP 101106 of process 59320]
> > [New LWP 10 of process 59320]
> > [New LWP 101100 of process 59320]
> > [LWP 101096 of process 59320 exited]
> > 
> > Thread 11 received signal SIGSEGV, Segmentation fault.
> > [Switching to LWP 101108 of process 59320]
> > 0x000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so 
> >  
> 
> Run the "backtrace" command there, please.  If it doesn't give any
> function names, try setting WITH_DEBUG=1 in the environment, then
> rebuilding the mod_php56 port (and optionally also the php56 and
> apache24 ports themselves), to add debug info.
> 
> -Dimitry
> 
www/mod_php56: env WITH_DEBUG=1 make reinstall (prior to that, I had to "pkg 
delete" the
port www/mod_php56 first). When having mod_php56 rebuilt with DEBUG on as 
recommended and
performing command sequence to enter gdb, run -X, the Apache 2.4 now crashes 
immediately
and not when the URL is called by the browser triggering the fault. This is 
what I get
then:

bt
#0  0x00080208b382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so
#1  0x000802088e1a in ?? () from /usr/local/lib/php/20131226-zts/opcache.so
#2  0x000802085f12 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so
#3  0x000802085cf3 in zend_accel_script_optimize ()
from /usr/local/lib/php/20131226-zts/opcache.so #4  0x00080207a393 in ?? ()
from /usr/local/lib/php/20131226-zts/opcache.so #5  0x0008020799d6 in
persistent_compile_file () from /usr/local/lib/php/20131226-zts/opcache.so #6
0x00080195d33c in zend_execute_scripts () from 
/usr/local/libexec/apache24/libphp5.so
#7  0x0008018f47a3 in php_execute_script ()
from /usr/local/libexec/apache24/libphp5.so #8  0x0008019f1015 in ?? ()
from /usr/local/libexec/apache24/libphp5.so #9  0x002563d7 in 
ap_invoke_handler
() #10 0x0029005d in ap_process_async_request () #11 0x0028ca2d 
in
ap_process_http_connection () #12 0x0026e3b7 in 
ap_run_process_connection ()
#13 0x00080152827f in ?? () from 
/usr/local/libexec/apache24/mod_mpm_event.so
#14 0x000801527e11 in ?? () from 
/usr/local/libexec/apache24/mod_mpm_event.so
#15 0x0008005d2476 in ?? () from /lib/libthr.so.3
#16 0x in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffde1ef000


-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgpPDWol2DJ2G.pgp
Description: OpenPGP digital signature

Re: HEAD amd64 seems unhappy

2018-02-04 Thread Michael Tuexen 
> On 4. Feb 2018, at 11:24, Dimitry Andric  wrote:
> 
> On 4 Feb 2018, at 03:38, Josh Paetzel  wrote:
>> 
>> --- all_subdir_lib/libngatm ---
>> /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of 
>> comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal
>> se [-Werror,-Wtautological-type-limit-compare]
>>  if (portno == 0 || portno > 0x)
>> ~~ ^ ~~
>> 1 error generated.
>> *** [cc_port.o] Error code 1
>> 
>> This code hasn't changed in ages so I can only assume it's clang or such.
> 
> This is because of r328816, which requires you to update your toolchain
> to at least r328381.  E.g. please run either "make buildworld" or "make
> kernel-toolchain" before building your kernel.
I get this error when doing a buildworld... Using r328861.

Best regards
Michael
> 
> -Dimitry
> 

___
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"

Re: Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel. crashes

2018-02-04 Thread Cy Schubert 
In message <1JOKDx2CeRUWS-ZzfU-7hCpDv4Yb0eMqlfrGzV-DnL89_Qg9MMxTZqdZJNu5
FMckEUy
rF3KwemDLaSlMY20vAlIW332XEhUTh3qcihfQfv8=@protonmail.com>, Taavi writes:
> see subject

Try rebuilding and reinstalling virtualbox-ose-kmod.


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX:     Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


___
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"

Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel. crashes

2018-02-04 Thread Taavi 
see subject

thank you
t

Sent with [ProtonMail](https://protonmail.com) Secure Email.
___
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"

Re: HEAD amd64 seems unhappy

2018-02-04 Thread Stefan Hagen 

Dimitry Andric wrote:
On 4 Feb 2018, at 03:38, Josh Paetzel  wrote:


--- all_subdir_lib/libngatm ---
/usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of 
comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal
se [-Werror,-Wtautological-type-limit-compare]
   if (portno == 0 || portno > 0x)
  ~~ ^ ~~
1 error generated.
*** [cc_port.o] Error code 1

This code hasn't changed in ages so I can only assume it's clang or such.


This is because of r328816, which requires you to update your toolchain
to at least r328381.  E.g. please run either "make buildworld" or "make
kernel-toolchain" before building your kernel.


I get the same error. It actually comes up at "make buildworld".
Running "make kernel-toolchain" before did not help. I'm on r328860.

Best Regards,
Stefan
___
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"

Re: HEAD amd64 seems unhappy

2018-02-04 Thread Michael Tuexen 
> On 4. Feb 2018, at 21:40, Dimitry Andric  wrote:
> 
> On 4 Feb 2018, at 20:59, Michael Tuexen  wrote:
>> 
>>> On 4. Feb 2018, at 11:24, Dimitry Andric  wrote:
>>> On 4 Feb 2018, at 03:38, Josh Paetzel  wrote:
 
 --- all_subdir_lib/libngatm ---
 /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of 
 comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal
 se [-Werror,-Wtautological-type-limit-compare]
if (portno == 0 || portno > 0x)
   ~~ ^ ~~
 1 error generated.
 *** [cc_port.o] Error code 1
 
 This code hasn't changed in ages so I can only assume it's clang or such.
>>> 
>>> This is because of r328816, which requires you to update your toolchain
>>> to at least r328381.  E.g. please run either "make buildworld" or "make
>>> kernel-toolchain" before building your kernel.
>> I get this error when doing a buildworld... Using r328861.
> 
> This should now be fixed by r328863.  The MK_SYSTEM_COMPILER logic did
> not build a cross-tools toolchain, so you were still getting warnings
> from the (old) compiler in your base system.
I can confirm that it works now.

Thanks for the quick fix!

Best regards
Michael
> 
> -Dimitry
> 

___
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"

Re: HEAD amd64 seems unhappy

2018-02-04 Thread Dimitry Andric 
On 4 Feb 2018, at 20:59, Michael Tuexen  wrote:
> 
>> On 4. Feb 2018, at 11:24, Dimitry Andric  wrote:
>> On 4 Feb 2018, at 03:38, Josh Paetzel  wrote:
>>> 
>>> --- all_subdir_lib/libngatm ---
>>> /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of 
>>> comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal
>>> se [-Werror,-Wtautological-type-limit-compare]
>>> if (portno == 0 || portno > 0x)
>>>~~ ^ ~~
>>> 1 error generated.
>>> *** [cc_port.o] Error code 1
>>> 
>>> This code hasn't changed in ages so I can only assume it's clang or such.
>> 
>> This is because of r328816, which requires you to update your toolchain
>> to at least r328381.  E.g. please run either "make buildworld" or "make
>> kernel-toolchain" before building your kernel.
> I get this error when doing a buildworld... Using r328861.

This should now be fixed by r328863.  The MK_SYSTEM_COMPILER logic did
not build a cross-tools toolchain, so you were still getting warnings
from the (old) compiler in your base system.

-Dimitry



signature.asc
Description: Message signed with OpenPGP