Re: librt symbol versioning breakage (was Re: Build failure, undefined reference to __mq_oshandle)

On Mon, 30 Nov 2015, Konstantin Belousov wrote: On Sun, Nov 29, 2015 at 12:27:40PM -0500, Daniel Eischen wrote: On Sun, 29 Nov 2015, Konstantin Belousov wrote: On Sun, Nov 29, 2015 at 01:23:04AM -0500, Daniel Eischen wrote: So I found out that sometime in the last year or so, symbol version

Re: panic "ffs_checkblk: bad block" on recent -head kernels

On Thu, Dec 03, 2015 at 03:07:48PM -0800, Kirk McKusick wrote: > > Date: Thu, 3 Dec 2015 23:47:52 +0100 > > From: Mateusz Guzik > > To: Rick Macklem > > Cc: FreeBSD Current > > Subject: Re: panic "ffs_checkblk: bad block" on recent -head kernels > > > > On Thu, Dec 03, 2015 at 05:08:27PM -0500,

Re: EFI and i915kms questions

It works! Would it be helpful if I did a pull request from github, or just let you guys take it from here? Thanks for helping me figure out how to get up, and running! This will be so much better than the framebuffer driver I was having to use. Joe Maloney > On Dec 3, 2015, at 12:33 PM, Joe

Re: panic "ffs_checkblk: bad block" on recent -head kernels

> Date: Thu, 3 Dec 2015 23:47:52 +0100 > From: Mateusz Guzik > To: Rick Macklem > Cc: FreeBSD Current > Subject: Re: panic "ffs_checkblk: bad block" on recent -head kernels > > On Thu, Dec 03, 2015 at 05:08:27PM -0500, Rick Macklem wrote: >> Hi, >> >> I get a fairly reproducible panic when doi

Re: panic "ffs_checkblk: bad block" on recent -head kernels

On Thu, Dec 03, 2015 at 05:08:27PM -0500, Rick Macklem wrote: > Hi, > > I get a fairly reproducible panic when doing a full kernel build > on a 256Mbyte single core i386 when running recent kernels from -head. > > The panic is "ffs_checkblk: bad block ..". I don't actually have the > block # (alt

panic "ffs_checkblk: bad block" on recent -head kernels

Hi, I get a fairly reproducible panic when doing a full kernel build on a 256Mbyte single core i386 when running recent kernels from -head. The panic is "ffs_checkblk: bad block ..". I don't actually have the block # (although I think it's just 0xfff, given the backtrace), because it

Re: EFI and i915kms questions

FYI it’s changed a bit more, and line 372 is now line 364 with different options. Going to try this first which was now at line 364. https://github.com/pkgdemon/freebsd/commit/f72323b10a9dd6da79f0dae1a6fd68823ec66f7d Joe Maloney > On Dec 3, 2015, at 11:58 AM, Joe Maloney wrote: > > Will give

Re: EFI and i915kms questions

Will give this a try, build an image and report back for sure. Thanks! Joe Maloney > On Dec 2, 2015, at 1:39 AM, Jean-Sébastien Pédron > wrote: > > On 02/12/2015 02:00, John Baldwin wrote: >> Note that at the top of the function it invokes IICBUS_TRANSFER on a >> different >> device when for

Re: Best way to update FreeBSD 11 ?

Excerpts from Daniel Nebdal's message from Thu 03-Dec-15 01:22: > > On Wed, Dec 02, 2015 at 02:39:24PM -0700, Sergey Manucharian wrote: > >> Hello, > >> > >> What is the best way to update FreeBSD 11-CURRENT? > >> Initially I've installed it from an image from [0] a couple of months ago. > > If yo

Re: Best way to update FreeBSD 11 ?

Excerpts from David Wolfskill's message from Wed 02-Dec-15 13:43: > On Wed, Dec 02, 2015 at 02:39:24PM -0700, Sergey Manucharian wrote: > > That depends on why you are considering the update. Well, it's under development, and I'd like to have the latest version of the system for different purpose

Jenkins build is back to normal : Build-UFS-image #2841

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"

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

See -- [...truncated 1576 lines...] ./lib/libc/string missing (created) ./lib/libc/sys missing (created) ./lib/libc/time missing (created) ./lib/libc/tls missing (created) ./lib/libc/tls/dso missing (cr