Re: Almost instant crasj after boot, 100% reproducable, version from middle of summer works

Hello NGie, Saturday, October 24, 2015, 11:49:31 PM, you wrote: > Based on the stack trace you provided and commits made in the > past few weeks, wlan might be a factor. Could you please disable wlan > support and see if the panics persist? Yep. It is not WiFi-related. It is something ke

Re: EFI bootloader often trys to build itself at installworld stage

Hello NGie, Sunday, October 25, 2015, 12:35:54 AM, you wrote: > Be sure to run buildworld with -DNO_CLEAN after updating your > sources when using make installworld. Unfortunately many of the Makefiles There is NO updating sources inbetween! Maybe, kernel rebuild (as now, when I've rem

Re: EFI bootloader often trys to build itself at installworld stage

> On Oct 24, 2015, at 14:35, NGie Cooper wrote: > > >> On Oct 24, 2015, at 14:28, Lev Serebryakov wrote: >> >> Hello freebsd-current, >> >> Each other time "make installworld" from object directory created several >> hours ago >> try to build efiloader again (and fails in my case as this wo

Re: EFI bootloader often trys to build itself at installworld stage

> On Oct 24, 2015, at 14:28, Lev Serebryakov wrote: > > Hello freebsd-current, > > Each other time "make installworld" from object directory created several > hours ago > try to build efiloader again (and fails in my case as this world doesn't > contain compiler): > > ===> sys/boot/efi/loader

EFI bootloader often trys to build itself at installworld stage

Hello freebsd-current, Each other time "make installworld" from object directory created several hours ago try to build efiloader again (and fails in my case as this world doesn't contain compiler): ===> sys/boot/efi/loader (install) cc -O2 -pipe -fPIC -I/data/src/sys/boot/efi/loader -I/data

Re: Almost instant crasj after boot, 100% reproducable, version from middle of summer works

Hello NGie, Saturday, October 24, 2015, 11:49:31 PM, you wrote: >> Hello freebsd-current, >> >> I have "home router" based on Intel MoBo with integrated Arom D2500 CPU. >> It boots and works fine on -CURRENT r285355 (it is ~11 of Jun 2015). >> >> But several latest revisions (I've tried r288145

Re: Almost instant crasj after boot, 100% reproducable, version from middle of summer works

> On Oct 24, 2015, at 13:47, Lev Serebryakov wrote: > > Hello freebsd-current, > > I have "home router" based on Intel MoBo with integrated Arom D2500 CPU. > It boots and works fine on -CURRENT r285355 (it is ~11 of Jun 2015). > > But several latest revisions (I've tried r288145 month ago and

Almost instant crasj after boot, 100% reproducable, version from middle of summer works

Hello freebsd-current, I have "home router" based on Intel MoBo with integrated Arom D2500 CPU. It boots and works fine on -CURRENT r285355 (it is ~11 of Jun 2015). But several latest revisions (I've tried r288145 month ago and now r289874) crashes almost instantly after boot. It is 100% repro

FreeBSD_HEAD_i386 - Build #1497 - Fixed

FreeBSD_HEAD_i386 - Build #1497 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1497/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1497/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1497/console Change summaries: 289

Re: Depreciate and remove gbde

Julian H. Stacey wrote this message on Sat, Oct 24, 2015 at 17:58 +0200: > > >If you want a secure filesystem I think that at this particular time > > >it would be entirely reasonable to use both gbde and geli stacked on > > >top of each other[...] > > I've often wondered if multiple encryption (C

Re: Depreciate and remove gbde

For what's worth we are using modded GBDE in one of the products to provide copy protection for the firmware and encryption of user's data. GELI is nice, but it's way much more end-user oriented. Also GBDE code is very stable, which may look bad from somebody using it to protect his pr0n collection

[CFT] em(4) - Update to use Extended RX Descriptor Format

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 https://reviews.freebsd.org/D3447 I'm looking for a bunch of you folks who have em(4) and *not* lem(4) to test out this update. This matches what linux does in e1000e vs e1000 and should be a no-op for your machines. The more devices we test here

Re: Depreciate and remove gbde

> >If you want a secure filesystem I think that at this particular time > >it would be entirely reasonable to use both gbde and geli stacked on > >top of each other[...] I've often wondered if multiple encryption (CPU permitting) is sensible in case one day some method is cracked but another stay

Re: dtc(1): reproducible segmentation fault

On 24 Oct 2015, at 11:07, David Chisnall wrote: > > On 23 Oct 2015, at 17:40, Ian Lepore wrote: >> >> Don't cc me. I looked at the in-tree dtc code once and decided it's >> too flawed to try to maintain, and it supports only a subset of the >> full dts syntax. That's why we switched back to u

Re: dtc(1): reproducible segmentation fault

On 23 Oct 2015, at 17:40, Ian Lepore wrote: > > Don't cc me. I looked at the in-tree dtc code once and decided it's > too flawed to try to maintain, and it supports only a subset of the > full dts syntax. That's why we switched back to using the gnu dtc for > buildkernel. But I just discovered