Jenkins build is back to normal : FreeBSD_HEAD-tests2 #1036

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On Saturday, May 09, 2015 07:27:51 AM David Wolfskill wrote: > Ref. -- > similar symptoms. And again, I captured screenshots on a phone, but > FreeBSD doesn't seem to recognize the (USB-attached) phone as something > that might act like a

UMA initialization failure with 48 core ARM64

Hi, I am experiencing an early failure of UMA on an ARM64 platform with 48 cores enabled. I get a kernel panic during initialization of VM. Here is the boot log (lines with 'MST:' are my own debug printfs). Copyright (c) 1992-2015 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1

CFR - watchdogd exit timeout

I would like to add a new feature to watchdogd(8): -x option to specify the watchdog timeout to leave in effect when the program exits (currently behavior is to disable the watchdog on exit). The change is available for review... https://reviews.freebsd.org/D2556 -- Ian

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On Fri, May 15, 2015 at 11:40:44AM -0400, John Baldwin wrote: > On Saturday, May 09, 2015 07:27:51 AM David Wolfskill wrote: > > Ref. -- > > similar symptoms. And again, I captured screenshots on a phone, but > > FreeBSD doesn't seem to r

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On Friday, May 15, 2015 11:39:56 AM David Wolfskill wrote: > On Fri, May 15, 2015 at 11:40:44AM -0400, John Baldwin wrote: > > On Saturday, May 09, 2015 07:27:51 AM David Wolfskill wrote: > > > Ref. -- > > > similar symptoms. And again, I

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On Fri, May 15, 2015 at 02:59:10PM -0400, John Baldwin wrote: > ... > Hummm, the only recent change is 281544, but that should be in your working > kernel. Yes; that dates from 14 April, and I had been doing daily build/boots of head/i386 through thta period without incident. Absent something com

Jenkins build became unstable: FreeBSD_HEAD-tests2 #1037

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Build failed in Jenkins: FreeBSD_HEAD_i386 #137

See Changes: [pfg] Break apart the gnu_inline attribute and use "artificial" if available. In general it is bad practice to use the gnu_inline attribute but we will need it in special cases like FORTIFY_SOURCE. In this specific case

Build failed in Jenkins: FreeBSD_HEAD #2769

See Changes: [pfg] Break apart the gnu_inline attribute and use "artificial" if available. In general it is bad practice to use the gnu_inline attribute but we will need it in special cases like FORTIFY_SOURCE. In this specific case it

Re: UMA initialization failure with 48 core ARM64

> On May 15, 2015, at 11:30 AM, Michał Stanek wrote: > > Hi, > > I am experiencing an early failure of UMA on an ARM64 platform with 48 > cores enabled. I get a kernel panic during initialization of VM. Here is > the boot log (lines with 'MST:' are my own debug printfs). > > Copyright (c) 1992

Re: [RFC] Replace gnu groff in base by heirloom doctools

Hi Bapt & current@ > I think keeping a fully functionnal roff(7) toolchain part of the > base system is very good on a unix. Yes, Unix has always also been a tool to get jobs done (aka PWB), as well as merely recompile more Unix. Ditto FreeBSD. > From what I could check I cannot find any regr

Jenkins build is back to normal : FreeBSD_HEAD #2770

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is back to stable : FreeBSD_HEAD-tests2 #1038

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is back to normal : FreeBSD_HEAD_i386 #138

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"