Build failed in Jenkins: Build-UFS-image #2885

See -- [...truncated 1541 lines...] ./cddl/usr.sbin/dtrace/common/ustack missing (created) ./cddl/usr.sbin/dtrace/common/vars missing (created) ./cddl/usr.sbin/dtrace/common/version missing (created) ./

Build failed in Jenkins: Build-UFS-image #2886

See -- [...truncated 1541 lines...] ./cddl/usr.sbin/dtrace/common/ustack missing (created) ./cddl/usr.sbin/dtrace/common/vars missing (created) ./cddl/usr.sbin/dtrace/common/version missing (created) ./

Build failed in Jenkins: Build-UFS-image #2888

See -- [...truncated 1541 lines...] ./cddl/usr.sbin/dtrace/common/ustack missing (created) ./cddl/usr.sbin/dtrace/common/vars missing (created) ./cddl/usr.sbin/dtrace/common/version missing (created) ./

Unstable kernel (dumbbell) crashes

Hello. I have been away from my FreeBSD system for over 7 months. The first on my return was to update world/kernel then do a full poudriere run for all my packages. The process had many problems; I'm reporting items below as FYI. I'm tracking https://github.com/dumbbell/freebsd.git for my Radeo

Re: Unstable kernel (dumbbell) crashes

I forgot version data, sorry. 11.0-CURRENT #0 831e725(master): Wed Dec 16 ___ 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: Unstable kernel (dumbbell) crashes

On Sun, 20 Dec 2015 20:04:20 +0200, Beeblebrox wrote: > Hello. > > I have been away from my FreeBSD system for over 7 months. The first on my > return was to update world/kernel then do a full poudriere run for all my > packages. The process had many problems; I'm reporting items below as FY

Build failed in Jenkins: Build-UFS-image #2889

See -- [...truncated 1541 lines...] ./cddl/usr.sbin/dtrace/common/ustack missing (created) ./cddl/usr.sbin/dtrace/common/vars missing (created) ./cddl/usr.sbin/dtrace/common/version missing (created) ./

Panic from vesa_configure()

Hey guys, I got the panic below with r292509. For some reason, "call doadump" didn't work (any idea why?), so I took a picture. I checked today's commits, there doesn't seem to be to be a fix. Any clue? https://people.freebsd.org/~jlh/vesa_panic.jpg Regards, -- Jeremie Le Hen j...@freebsd.or

Re: Panic from vesa_configure()

On Sun, Dec 20, 2015 at 4:02 PM, Jeremie Le Hen wrote: > For some reason, "call doadump" > didn't work (any idea why?), so I took a picture. > I have no idea about the panic, but doadump failed because the crash happened too early for the dump device to be configured yet. ___

Re: Panic from vesa_configure()

can you copy/paste the file:line that each of those stackframes represents? I may have an idea or two.. -a On 20 December 2015 at 15:40, Ryan Stone wrote: > On Sun, Dec 20, 2015 at 4:02 PM, Jeremie Le Hen wrote: > >> For some reason, "call doadump" >> didn't work (any idea why?), so I took a

Re: Unstable kernel (dumbbell) crashes

Le 20/12/2015 19:04, Beeblebrox a écrit : > Hello. Hi! > I have been away from my FreeBSD system for over 7 months. The first > on my return was to update world/kernel then do a full poudriere run > for all my packages. The process had many problems; I'm reporting > items below as FYI. I'm trac

Build failed in Jenkins: Build-UFS-image #2890

See -- Started by upstream project "Build_Image_and_Run_Tests_in_Bhyve_HEAD" build number 1879 originally caused by: Started by upstream project "FreeBSD_HEAD" build number 3655 originally caused by:

failure to enumerate AMD Carrizo boost states

Dear all, I run CURRENT on a laptop with an AMD Carrizo (A12-8800B) which should have multiple boost states (Pb) according to the official specifications (see [1] and [2] pages 59 and 63). CURRENT fails to enumerate them and therefore only runs at base clock. A thread on freebsd-acpi [3] did unfo

ssh and HPN

So was there ever a result as to whether HPN still plays a useful role in the current openSSH? I haven't seen any note in the openssh docs about adding bigger window support and that is a definite requirement when you are on the end of a 500mSec RTT like I am, but the last time we discussed it,