Jenkins build is still unstable: FreeBSD_HEAD #167

[jenkins-admin]

See 

___
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: Booting FreeBSD on a RPI3

[Ted W.]

I too anxiously await the widespread availability of FreeBSD on the Pi3. 
If you're like me and just can't wait the image below does boot but does 
not have network support:


https://people.freebsd.org/~andrew/arm64/rpi3-20160306.img.xz

On 03/30/2016 04:11 PM, Gala IT wrote:

Nice to know, thanks a lot :)


El 30 març 2016, a les 1:38, Adrian Chadd  va escriure:

Hi,

It's under active development right now. Stay tuned.


-a


On 29 March 2016 at 13:58, Gala IT  wrote:

Hi,

Being that it’s a 64-bit system and RPI2 images don’t work, is there any 
procedure already established to build an image to boot on a Raspberry Pi 3?

Should Crochet work? How?

Thanks,
David.
___
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"

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


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

Jenkins build is unstable: FreeBSD_HEAD #166

[jenkins-admin]

See 

___
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: Keeping OptionalObsoleteFiles.inc up to date

[Ngie Cooper]

On Thu, Apr 7, 2016 at 1:59 PM, Olivier Cochard-Labbé
 wrote:
> Hi,
>
> I'm trying to use "make delete-old" specifying WITHOUT_ keyword for
> removing some no-more used set of files.
>
> I've start by testing WITHOUT_TOOLCHAIN:
> - Some of files related to clang are correctly delete
> - But there are still lot's of others (like /usr/bin/cc)
>
> Then I've checked tools/build/mk/OptionalObsoleteFiles.in and found that
> lot's files are missing in the ".if ${MK_TOOLCHAIN} == no" section.
>
> I've started a new run of phk's build_options_survey script:
> https://people.freebsd.org/~olivier/build_option_survey_20160406/
>
> And wonder if it's possible to automatically generate the list of
> conditional files to be put in OptionalObsoleteFiles.in from the result of
> a build_option_survey script ?

amdmi3 had a method for doing this, but I think it was a bit of a
brute force approach (I could be wrong).

The release-pkg project branch method seems like the best way to go
about it though because it would kind of do the sanity checking for
us...

Thanks!
-Ngie
___
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"

Panic in pfsync_sendout()

[Jeremie Le Hen]

Hey,

I happen to have pfsync in my kernel but I don't use it. I do use pf though.
It panics when my jails are starting.  No idea if it's related or not.

I managed to grab a core with "call doadump()" but I can't open it
with kgdb(1).  I get:
# kgdb /boot/kernel.panic/kernel vmcore.3
[...]
Attempt to extract a component of a value that is not a structure pointer.
Attempt to extract a component of a value that is not a structure pointer.
kgdb: kvm_read: invalid address (0x0)
#0  0x in ?? ()


"bt" doesn't work, "info threads" yields hundreds of:
* 51 Thread 0 (PID=0: /zil_clean)  0x in ?? ()


Why is that?  This should work since How can I get a proper one?

DDB spit the following stacktrace (this is amd64):

Fatal trap 9: general protection fault while in kernel mode
[...]
pfsync_sendout() at pfsync_sendout+0x1d0
pfsyncintr() at pfsyncintr+0x42
intr_event_execute_handlers()
ithread_loop()


-- 
Jeremie Le Hen
j...@freebsd.org
___
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"

Build failed in Jenkins: FreeBSD_HEAD #165

[jenkins-admin]

See 

--
Started by an SCM change
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/freebsd/freebsd-ci.git # 
 > timeout=10
Fetching upstream changes from https://github.com/freebsd/freebsd-ci.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/freebsd/freebsd-ci.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 926429031e0241da821577c12b4b8f7db789e7e1 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 926429031e0241da821577c12b4b8f7db789e7e1
 > git rev-list 926429031e0241da821577c12b4b8f7db789e7e1 # timeout=10
[Pipeline] Allocate node : Start
Still waiting to schedule task
Waiting for next available executor on jenkins-10.freebsd.org
Resuming build
Aborted by rodrigc
[Pipeline] Allocate node : End
[Pipeline] Allocate node : Start
Running on master in /usr/local/jenkins/workspace/FreeBSD_HEAD
[Pipeline] node {
[Pipeline] step
___
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"

Keeping OptionalObsoleteFiles.inc up to date

[Olivier Cochard-Labbé]

Hi,

I'm trying to use "make delete-old" specifying WITHOUT_ keyword for
removing some no-more used set of files.

I've start by testing WITHOUT_TOOLCHAIN:
- Some of files related to clang are correctly delete
- But there are still lot's of others (like /usr/bin/cc)

Then I've checked tools/build/mk/OptionalObsoleteFiles.in and found that
lot's files are missing in the ".if ${MK_TOOLCHAIN} == no" section.

I've started a new run of phk's build_options_survey script:
https://people.freebsd.org/~olivier/build_option_survey_20160406/

And wonder if it's possible to automatically generate the list of
conditional files to be put in OptionalObsoleteFiles.in from the result of
a build_option_survey script ?

Regards,

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

Opteron 6100-series "Magny-Cours" [Was: [HEADSUP] new x86 smp topology detection code]

[Andriy Gapon]

If anyone uses FreeBSD head on a system with "Magny-Cours" CPU(s), could you
please test the following patch?
http://dpaste.com/0XRSXZB.txt
I am interested in kern.sched.topology_spec sysctl before and after the patch.
Also, lines containing "ID shift" from a dmesg of a verbose boot (before and 
after).

Thank you!

On 04/04/2016 19:31, Andriy Gapon wrote:
> 
> 
> I've just committed new code for detecting SMP (processor and cache) topology 
> on
> x86 systems.  Please be aware.
> 
> If you get any panics or crashes that look like they might be caused by this
> change please send a copy of a report to me.
> 
> Another thing to watch is kern.sched.topology_spec.
> Please check if the reported topology reasonably matches what you expect on 
> your
> system.
> You can install hwloc package (devel/hwloc) and then run lstopo -p --no-io to
> double-check the topology (--output-format ascii would produce a nice 
> ASCII-art
> diagram).
> 
> I hope that you see only improvements :-)
> 
>  Forwarded Message 
> Subject: svn commit: r297558 - in head/sys: kern sys x86/x86
> Date: Mon, 4 Apr 2016 16:09:29 + (UTC)
> From: Andriy Gapon 
> To: src-committ...@freebsd.org, svn-src-...@freebsd.org, 
> svn-src-h...@freebsd.org
> 
> Author: avg
> Date: Mon Apr  4 16:09:29 2016
> New Revision: 297558
> URL: https://svnweb.freebsd.org/changeset/base/297558
> 
> Log:
>   new x86 smp topology detection code
> 
>   Previously, the code determined a topology of processing units
>   (hardware threads, cores, packages) and then deduced a cache topology
>   using certain assumptions.  The new code builds a topology that
>   includes both processing units and caches using the information
>   provided by the hardware.
> 
>   At the moment, the discovered full topology is used only to creeate
>   a scheduling topology for SCHED_ULE.
>   There is no KPI for other kernel uses.
> 
>   Summary:
>   - based on APIC ID derivation rules for Intel and AMD CPUs
>   - can handle non-uniform topologies
>   - requires homogeneous APIC ID assignment (same bit widths for ID
> components)
>   - topology for dual-node AMD CPUs may not be optimal
>   - topology for latest AMD CPU models may not be optimal as the code is
> several years old
>   - supports only thread/package/core/cache nodes
> 
>   Todo:
> - AMD dual-node processors
> - latest AMD processors
> - NUMA nodes
> - checking for homogeneity of the APIC ID assignment across packages
> - more flexible cache placement within topology
> - expose topology to userland, e.g., via sysctl nodes
> 
>   Long term todo:
> - KPI for CPU sharing and affinity with respect to various resources
>   (e.g., two logical processors may share the same FPU, etc)
> 
>   Reviewed by:mav
>   Tested by:  mav
>   MFC after:  1 month
>   Differential Revision:  https://reviews.freebsd.org/D2728
> 
> Modified:
>   head/sys/kern/subr_smp.c
>   head/sys/sys/smp.h
>   head/sys/x86/x86/mp_x86.c

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