Re: Depreciate and remove gbde
On Oct 24, 2015, at 12:06 PM, John-Mark Gurney wrote: > The thing I like most about encryption is that when I RMA a bad > drive, I don't have to worry about my data leaking if I am unable > to overwrite all the data... You are optimistic if you believe that. We ($WORK) factor the cost of DOA/warranty drives into our operational budget. They never get RMAed. We drill them when they die. --lyndon signature.asc Description: Message signed with OpenPGP using GPGMail
Re: AHC - 29160 interrupts not functioning?
On 10/18/15 17:37, Patrick Hess wrote: [ .. ] > I can send you a full verbose dmesg if that's of any help to you. > >> "Timedout SCBs already complete. Interrupts may not be functioning." >> when given any significant load :-( > > Just extracted an entire ports tree on that machine with no issues. > Can you give an example of a workload that causes these problems? Do you have "options AHC_ALLOW_MEMIO" in your kernel config? The machine I have running is an old Dell PowerApp 100 (700MHz Pentium-III) running about 4 jails :-( imb ___ 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: Quick test building a module cross all targets and architectures
On 26 October 2015 at 11:23, Konstantin Belousov wrote:
> On Mon, Oct 26, 2015 at 11:03:07AM -0700, John Baldwin wrote:
>> On Monday, October 26, 2015 10:11:43 AM Hans Petter Selasky wrote:
>> > Hi,
>> >
>> > We have NO_MODULES for building kernel without modules, but no NO_KERNEL
>> > to only build the modules.
>> >
>> > What do you think about the following patch:
>> >
>> > > diff --git a/sys/conf/kern.post.mk b/sys/conf/kern.post.mk
>> > > index ddf828e..f0920df 100644
>> > > --- a/sys/conf/kern.post.mk
>> > > +++ b/sys/conf/kern.post.mk
>> > > @@ -32,7 +32,11 @@ KERN_DEBUGDIR?= ${DEBUGDIR}
>> > >
>> > > .for target in all clean cleandepend cleandir clobber depend install \
>> > > obj reinstall tags
>> > > +.if !defined(NO_KERNEL)
>> > > ${target}: kernel-${target}
>> > > +.else
>> > > +${target}:
>> > > +.endif
>> > > .if !defined(MODULES_WITH_WORLD) && !defined(NO_MODULES) &&
>> > > exists($S/modules)
>> > > ${target}: modules-${target}
>> > > modules-${target}:
>> >
>> > It allows only a single module with MODULES_OVERRIDE= and NO_KERNEL=YES
>> > to be built with universe in very little time. This can save a lot of
>> > build time when changes are limited to a set of kernel modules.
>>
>> Can you just use something like MODULES_WITH_WORLD instead?
>>
>> make tinderbox MAKE_JUST_WORLDS=yes SUBDIR_OVERRIDE=sys/modules
>> MODULES_OVERRIDE=foo
>>
>> (If it's only 1 module directory you can probably just use SUBDIR_OVERRIDE
>> directly?)
>>
>> make tinderbox MAKE_JUST_WORLDS=yes SUBDIR_OVERRIDE=sys/modules/foo
>>
>
> In any variant, this proposal sounds strange. Almost all in-kernel
> code is compiled both for kernel and for modules. I am only aware of
> exceptions for i915kms, which was done for a reason which is no longer
> valid. In other words, if your goal is to check that the change does not
> break compilation of some kernel code, then it is wrong to not compile
> kernels.
>
> Note that kernel and modules compilation environments are differrent.
No, the goal isn't that - it's to do things like "let's recompile usb
+ usb modules, unload, load to test."
It's not a substitute for the "test a full build"; it's for testing
things that are easily tested as modules - usb, wlan, etc.
-a
___
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: Quick test building a module cross all targets and architectures
On Mon, Oct 26, 2015 at 11:03:07AM -0700, John Baldwin wrote:
> On Monday, October 26, 2015 10:11:43 AM Hans Petter Selasky wrote:
> > Hi,
> >
> > We have NO_MODULES for building kernel without modules, but no NO_KERNEL
> > to only build the modules.
> >
> > What do you think about the following patch:
> >
> > > diff --git a/sys/conf/kern.post.mk b/sys/conf/kern.post.mk
> > > index ddf828e..f0920df 100644
> > > --- a/sys/conf/kern.post.mk
> > > +++ b/sys/conf/kern.post.mk
> > > @@ -32,7 +32,11 @@ KERN_DEBUGDIR?= ${DEBUGDIR}
> > >
> > > .for target in all clean cleandepend cleandir clobber depend install \
> > > obj reinstall tags
> > > +.if !defined(NO_KERNEL)
> > > ${target}: kernel-${target}
> > > +.else
> > > +${target}:
> > > +.endif
> > > .if !defined(MODULES_WITH_WORLD) && !defined(NO_MODULES) &&
> > > exists($S/modules)
> > > ${target}: modules-${target}
> > > modules-${target}:
> >
> > It allows only a single module with MODULES_OVERRIDE= and NO_KERNEL=YES
> > to be built with universe in very little time. This can save a lot of
> > build time when changes are limited to a set of kernel modules.
>
> Can you just use something like MODULES_WITH_WORLD instead?
>
> make tinderbox MAKE_JUST_WORLDS=yes SUBDIR_OVERRIDE=sys/modules
> MODULES_OVERRIDE=foo
>
> (If it's only 1 module directory you can probably just use SUBDIR_OVERRIDE
> directly?)
>
> make tinderbox MAKE_JUST_WORLDS=yes SUBDIR_OVERRIDE=sys/modules/foo
>
In any variant, this proposal sounds strange. Almost all in-kernel
code is compiled both for kernel and for modules. I am only aware of
exceptions for i915kms, which was done for a reason which is no longer
valid. In other words, if your goal is to check that the change does not
break compilation of some kernel code, then it is wrong to not compile
kernels.
Note that kernel and modules compilation environments are differrent.
___
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: Quick test building a module cross all targets and architectures
On Monday, October 26, 2015 10:11:43 AM Hans Petter Selasky wrote:
> Hi,
>
> We have NO_MODULES for building kernel without modules, but no NO_KERNEL
> to only build the modules.
>
> What do you think about the following patch:
>
> > diff --git a/sys/conf/kern.post.mk b/sys/conf/kern.post.mk
> > index ddf828e..f0920df 100644
> > --- a/sys/conf/kern.post.mk
> > +++ b/sys/conf/kern.post.mk
> > @@ -32,7 +32,11 @@ KERN_DEBUGDIR?= ${DEBUGDIR}
> >
> > .for target in all clean cleandepend cleandir clobber depend install \
> > obj reinstall tags
> > +.if !defined(NO_KERNEL)
> > ${target}: kernel-${target}
> > +.else
> > +${target}:
> > +.endif
> > .if !defined(MODULES_WITH_WORLD) && !defined(NO_MODULES) &&
> > exists($S/modules)
> > ${target}: modules-${target}
> > modules-${target}:
>
> It allows only a single module with MODULES_OVERRIDE= and NO_KERNEL=YES
> to be built with universe in very little time. This can save a lot of
> build time when changes are limited to a set of kernel modules.
Can you just use something like MODULES_WITH_WORLD instead?
make tinderbox MAKE_JUST_WORLDS=yes SUBDIR_OVERRIDE=sys/modules
MODULES_OVERRIDE=foo
(If it's only 1 module directory you can probably just use SUBDIR_OVERRIDE
directly?)
make tinderbox MAKE_JUST_WORLDS=yes SUBDIR_OVERRIDE=sys/modules/foo
--
John Baldwin
___
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: What changed in rc.d infrastructure in last months?
On Monday, October 26, 2015 04:38:21 AM Adrian Chadd wrote: > On 26 October 2015 at 01:27, Lev Serebryakov wrote: > > Hello NGie, > > > > Sunday, October 25, 2015, 11:09:03 PM, you wrote: > > > > > >> Ok, this is really not making sense from a design perspective. > >> `ifconfig_` is being overloaded for starting up hostap’s (even though > >> ifconfig itself doesn’t support hostap — only `wlanmode ap`). I don’t > > ifconfig doesn't support dhcp either, but dhclient is run via "DHCP" in > > `ficonfig_` > > > >> understand why it was done this way instead of just creating additional > >> variables for `hostapd_` > > Long time ago there was simple `hostapd_enable` and `hostapd_interfaces` :) > > But it doesn't allow to automagically start hostapd for hotplugged (i.e. > > USB) interfaces. On the other hand, automatic DHCP on hot-plugged > > interfaces have sense and automatic hostapd doesn't, IMHO. > > This sounds like the same issue as double-running wpa_supplicant. > > I thought this was fixed already :( Would someone please figure out a > cleanish solution to this? I'd really appreciate it. Note that /etc/pccard_ether bails right away if the interface is marked up without doing anything. That is what is supposed to make devd events at boot get ignored. (See the initial loop in pccard_ether_start().) -- John Baldwin ___ 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: Quick test building a module cross all targets and architectures
+1 to this thankyou!
-adrian
On 26 October 2015 at 02:11, Hans Petter Selasky wrote:
> Hi,
>
> We have NO_MODULES for building kernel without modules, but no NO_KERNEL to
> only build the modules.
>
> What do you think about the following patch:
>
>> diff --git a/sys/conf/kern.post.mk b/sys/conf/kern.post.mk
>> index ddf828e..f0920df 100644
>> --- a/sys/conf/kern.post.mk
>> +++ b/sys/conf/kern.post.mk
>> @@ -32,7 +32,11 @@ KERN_DEBUGDIR?= ${DEBUGDIR}
>>
>> .for target in all clean cleandepend cleandir clobber depend install \
>> obj reinstall tags
>> +.if !defined(NO_KERNEL)
>> ${target}: kernel-${target}
>> +.else
>> +${target}:
>> +.endif
>> .if !defined(MODULES_WITH_WORLD) && !defined(NO_MODULES) &&
>> exists($S/modules)
>> ${target}: modules-${target}
>> modules-${target}:
>
>
> It allows only a single module with MODULES_OVERRIDE= and NO_KERNEL=YES to
> be built with universe in very little time. This can save a lot of build
> time when changes are limited to a set of kernel modules.
>
> --HPS
> ___
> 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"
Re: What changed in rc.d infrastructure in last months?
On 26 October 2015 at 01:27, Lev Serebryakov wrote: > Hello NGie, > > Sunday, October 25, 2015, 11:09:03 PM, you wrote: > > >> Ok, this is really not making sense from a design perspective. >> `ifconfig_` is being overloaded for starting up hostap’s (even though >> ifconfig itself doesn’t support hostap — only `wlanmode ap`). I don’t > ifconfig doesn't support dhcp either, but dhclient is run via "DHCP" in > `ficonfig_` > >> understand why it was done this way instead of just creating additional >> variables for `hostapd_` > Long time ago there was simple `hostapd_enable` and `hostapd_interfaces` :) > But it doesn't allow to automagically start hostapd for hotplugged (i.e. > USB) interfaces. On the other hand, automatic DHCP on hot-plugged > interfaces have sense and automatic hostapd doesn't, IMHO. This sounds like the same issue as double-running wpa_supplicant. I thought this was fixed already :( Would someone please figure out a cleanish solution to this? I'd really appreciate it. -a ___ 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"
Quick test building a module cross all targets and architectures
Hi,
We have NO_MODULES for building kernel without modules, but no NO_KERNEL
to only build the modules.
What do you think about the following patch:
diff --git a/sys/conf/kern.post.mk b/sys/conf/kern.post.mk
index ddf828e..f0920df 100644
--- a/sys/conf/kern.post.mk
+++ b/sys/conf/kern.post.mk
@@ -32,7 +32,11 @@ KERN_DEBUGDIR?= ${DEBUGDIR}
.for target in all clean cleandepend cleandir clobber depend install \
obj reinstall tags
+.if !defined(NO_KERNEL)
${target}: kernel-${target}
+.else
+${target}:
+.endif
.if !defined(MODULES_WITH_WORLD) && !defined(NO_MODULES) && exists($S/modules)
${target}: modules-${target}
modules-${target}:
It allows only a single module with MODULES_OVERRIDE= and NO_KERNEL=YES
to be built with universe in very little time. This can save a lot of
build time when changes are limited to a set of kernel modules.
--HPS
___
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: Make installworld fails on file not found (Error code 71)
> > It looks like a problem with WITHOUT_MANCOMPRESS. > > I am looking into it. > A fix is now committed. It has been broken since June. > Regards, > Bryan Drewery Thanks for the fix, computer is now busy with NetBSD update from 6.99.44 (16 months old) to 7.99.21 for both amd64 and i386, but I intend to get back to the FreeBSD update after that is done. I checked /etc/src.conf and found WITHOUT_MANCOMPRESS=yes WITHOUT_DOCCOMPRESS=yes I looked in other directions for the problem and would have just been wasting time and computer energy. Compressed man pages can be a nuisance, and not really necessary or helpful with today's big hard drives and USB sticks. Good I was able to expose a bug of four months' standing. UPDATE: buildworld succeeded, but installworld crashed to the debugger prompt: Fatal trap 12: page fault while in kernel mode Reboot attempt, both with custom kernel and GENERIB, failed: /libc/libc.so.7: version FBSD_1.3 required by /bin/sh not defined GENERIB is kernel config derived from GENERIC but with some outdated devices unlikely to be found on a modern computer system removed, and some wireless drivers including rsu added. So now that FreeBSD installation is not bootable. I ran fsck_ffs -y /dev/dk9 from NetBSD 7.99.21 (current) i386, /dev/dk9 being NetBSD's version of the FreeBSD partition name. I can say "make installworld" likely failed because, after interrupted (crashed) installworld, userland was out of sync. I have another FreeBSD partition, 10.1-STABLE amd64, dating to January 29, 2015, could boot into that and try to update both that (10.2-STABLE) and the messed-up FreeBSD-current installation (with HEAD/current). MicroNet Fantom external hard drives, 1 TB to 5 TB, USB 3.0 and eSATA, look attractive now, back up a whole OS installation, eSATA figures to work better than USB 3.0: better for FreeBSD and NetBSD, and better recognition at boot time by motherboard/BIOS/UEFI. Tom ___ 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: What changed in rc.d infrastructure in last months?
Hello NGie, Sunday, October 25, 2015, 11:09:03 PM, you wrote: > Ok, this is really not making sense from a design perspective. > `ifconfig_` is being overloaded for starting up hostap’s (even though > ifconfig itself doesn’t support hostap — only `wlanmode ap`). I don’t ifconfig doesn't support dhcp either, but dhclient is run via "DHCP" in `ficonfig_` > understand why it was done this way instead of just creating additional > variables for `hostapd_` Long time ago there was simple `hostapd_enable` and `hostapd_interfaces` :) But it doesn't allow to automagically start hostapd for hotplugged (i.e. USB) interfaces. On the other hand, automatic DHCP on hot-plugged interfaces have sense and automatic hostapd doesn't, IMHO. -- Best regards, Levmailto:l...@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"
