On Wed, Mar 20, 2013 at 10:08:57PM +0200, Konstantin Belousov wrote:
...
I looked at the nvidia sources to check that the driver does not use
the interfaces which KBI was changed, and this is indeed the case, as
expected.
I must admit that I have no idea why buffer cache changes could
On Sat, Mar 09, 2013 at 11:59:21AM +0100, Hartmann, O. wrote:
On CURRENT, r248093, build of kernel fails due to the below shown error.
[...]
cc -c -O3 -O3 -Wno-error=unused-variable -fno-strict-aliasing
...
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
On Sat, Mar 09, 2013 at 06:06:05PM +0100, Hartmann, O. wrote:
...
No, it isn't. Same error, system is at revision:
FreeBSD 10.0-CURRENT #1 r248106: Sat Mar 9 16:44:58 CET 2013 amd64
The error is the same.
...
Please see the message I posted to ports@, a copy of which may be found
at
Whine was:
...
CC='clang' mkdep -f .depend -a-I/usr/src/sbin/fsdb/../fsck_ffs -std=gnu99
/usr/src/sbin/fsdb/fsdb.c /usr/src/sbin/fsdb/fsdbutil.c /usr/src/sbin/fsdb/../fs
ck_ffs/dir.c /usr/src/sbin/fsdb/../fsck_ffs/ea.c /usr/src/sbin/fsdb/../fsck_ffs/
fsutil.c
On Sun, Feb 24, 2013 at 07:05:34AM -0800, David Wolfskill wrote:
...hine was:
Simple patch attached; world is still building, but at least it got
through the make dependencies phase this time.
...
That was incomplete, as it didn't (also) address the change to
getdatablk().
The attached patch
On Wed, Feb 20, 2013 at 02:33:23PM -0800, Navdeep Parhar wrote:
On 02/20/13 14:25, Konstantin Belousov wrote:
On Wed, Feb 20, 2013 at 02:21:50PM -0800, Navdeep Parhar wrote:
On 02/20/13 14:14, Xin Li wrote:
Hi,
It seems that fresh -HEAD would give an unusable kernel that
overwrites
On Fri, Feb 15, 2013 at 07:01:16PM +0100, O. Hartmann wrote:
...
My boxes are one revision ahead of yours and all of them do not build
the recent sources as reported:
FreeBSD 10.0-CURRENT #0 r246825: Fri Feb 15 14:23:40 CET 2013
And by the way, we have amd64 only, no i386. Maybe this
I include
PORTS_MODULES=x11/nvidia-driver
in /etc/src.conf in order to keep nvidia-driver in sync with my kernel.
It last built OK yesterday, @r246057; @r246115, I see:
=== nvidia-driver-304.64 depends on file:
/usr/local/libdata/pkgconfig/xorg-server.pc - found
=== nvidia-driver-304.64
On Tue, Jan 29, 2013 at 11:06:02AM +0100, O. Hartmann wrote:
I receive this error since yesterday building world and it is still
sticky on most recent sources (r246057) and I was wondering why the
tinderboxes do not pick this up on the 10.0-CURRENT builds ... just for
a notice for the
On Fri, Jan 25, 2013 at 11:06:16AM +0100, O. Hartmann wrote:
Just want to note that make buildworld fails on
r245901 with the following unhealthy end:
=== kerberos5/lib/libheimbase (install)
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libheimbase.a
On Fri, Jan 18, 2013 at 09:34:26PM +0300, Sergey V. Dyatko wrote:
On Fri, 18 Jan 2013 22:17:27 +0400
Andrey Chernov a...@freebsd.org wrote:
=== usr.sbin/acpi/iasl (all)
cc -O2 -pipe -march=core2 -DACPI_ASL_COMPILER -I.
-I/usr/src/usr.sbin/acpi/iasl/../../../sys -std=gnu99
On Sat, Dec 29, 2012 at 09:38:42AM -0800, Cy Schubert wrote:
Just udated to the latest current and amd hangs at boot. Ideas?
I don't see a problem @r244855. On my build machine, /usr/ports is a
symlink to a ports working copy that resides on a ReadyNAS:
freebeast(10.0-C)[2] ls -F
On Thu, Nov 22, 2012 at 10:17:54PM -0500, Michael W. Lucas wrote:
...
13 * * * * /usr/local/etc/rc.d/apache22 restart
When this job runs, I get the following email:
Performing sanity check on apache22 configuration:
...
eval: setfib: not found
/usr/local/etc/rc.d/apache22: WARNING:
On Wed, Nov 14, 2012 at 12:43:03AM +0100, Mateusz Guzik wrote:
Hello,
avg@ suggested to include compiler version in the kernel so that it's
present in uname (and one can easly tell what was used to compile it).
Here is my attempt:
On Thu, Oct 25, 2012 at 01:41:22PM +0200, Piotr Kubaj wrote:
Is it actually possible? I've used clang before for compiling world, but
when I try to use libc++, it fails with several errors. It's a quite
recent revision, with the newest libc++ MFV.
My build machine, yesterday morning, was
Presently running:
FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #708 241627M:
Wed Oct 17 06:05:26 PDT 2012
r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386
buildkernel proceeds:
...
stage 3.2: building everything
...
=== mxge (all)
=== mxge/mxge (all)
clang
On Mon, Oct 08, 2012 at 12:04:47PM +0400, Gleb Smirnoff wrote:
David and Michael,
On Sun, Oct 07, 2012 at 10:52:13AM -0700, Garrett Cooper wrote:
G On 10/07/12 13:03, Garrett Cooper wrote:
G Maybe these revisions had something to do with it... (r241245 is
G more likely)?
G
G I
I started seeing these messages spewed (to both console
/var/log/messages) following an update from:
FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #697 241222M:
Fri Oct 5 05:32:19 PDT 2012
r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386
to
FreeBSD
On Sun, Oct 07, 2012 at 10:03:04AM -0700, Garrett Cooper wrote:
...
Maybe these revisions had something to do with it... (r241245 is
more likely)?
r241245 | glebius | 2012-10-06 03:02:11 -0700 (Sat, 06 Oct 2012) |
E.g.:
...
=== bios (all)
=== bios/smapi (all)
ctfconvert -L VERSION -g hdacc.o
clang -O2 -pipe -fno-strict-aliasing -D_KERNEL -DKLD_MODULE -nostdinc
-DHAVE_KERNEL_OPTION_HEADERS -include
/common/S4/obj/usr/src/sys/CANARY/opt_global.h -I. -I@ -I@/contrib/altq
-fno-common -g
This was on:
FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #681 240597M:
Mon Sep 17 15:34:41 PDT 2012
r...@d134.dwolf.juniper.net.:/usr/obj/usr/src/sys/CANARY i386
using clang as the C compiler:
...
=== sbin/nvmecontrol (all)
clang -O2 -pipe -std=gnu99
On Wed, Sep 12, 2012 at 11:48:45AM -0400, Kim Culhan wrote:
FreeBSD -current r240360 has a fatal trap at boot.
...
As noted yesterday, yes. You need to either revert r240344 or apply
r240367 (which reverts r240344).
FWIW, I had no trouble at r240388.
Peace,
david
--
David H. Wolfskill
In case others want to save a bit of time by using -DNOCLEAN for
buildworld, I found that after r240303 if make cleandepend isn't done,
src/cddl/lib/libnvpair build fails with a whine:
make: don't know how to make
/usr/src/cddl/lib/libnvpair/../../../sys/cddl/compat/opensolaris/sys/debug.h.
Running:
FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #669 240081M:
Tue Sep 4 05:02:11 PDT 2012
r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386
After updating sources to r240131, I see:
...
stage 3.2: building everything
...
clang -c -O -pipe -std=c99 -g
This is using clang:
...
stage 3.2: building everything
cd /usr/obj/usr/src/sys/CANARY; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386
MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
On Thu, Aug 09, 2012 at 04:15:36PM +0400, Boris Samorodov wrote:
Hi!
The kernel build fails at fresh CURRENT...
And then I get an error:
-
linking kernel.debug
cam_periph.o: In function `cam_periph_error':
/usr/src/sys/cam/cam_periph.c:1776: undefined reference to
On Sun, Jul 29, 2012 at 11:39:14AM -0700, Garrett Cooper wrote:
...
What was the previous version you booted and what's your configuration?
Thanks,
-Garrett
I'm on an x86 core duo laptop with a single SATA disk split between
Windoze-7 and FreeBSD. Nothing really special in the
This is at r238795; cut/paste of backtrace:
KDB: enter: panic
[ thread pid 12 tid 100026 ]
Stopped at kdb_enter+0x3d: movl$0,kdb_why
db bt
Tracing pid 12 tid 100026 td 0xc6755000
kdb_enter(c0f93c5f,c0f93c5f,c0f91e21,f08398f0,c1825c80,...) at kdb_enter+0x3d
On Wed, Jul 11, 2012 at 12:46:40PM -0700, Adrian Chadd wrote:
Hi,
What was the original commit which broke wlan name matching?
I can't see how a commit to usb_pf.c would fix this.
...
r238279
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Depriving
On Tue, Jul 10, 2012 at 06:50:57PM -0700, Garrett Cooper wrote:
On Tue, Jul 10, 2012 at 6:38 PM, Brandon Gooch
jamesbrandongo...@gmail.com wrote:
...
Same thing here, and I tracked it down to r238279:
http://svnweb.freebsd.org/base?view=revisionrevision=238279
Not yet sure why
On Tue, Jul 10, 2012 at 07:15:21PM -0700, Garrett Cooper wrote:
...
Curious. I was wondering about this because there's some logic in
network.subr that parses ifconfig -l output -- thinking that the
fallout might have been there.
I would be curious next to see what devd is trying to execute.
On Tue, Jul 10, 2012 at 07:36:09PM -0700, Garrett Cooper wrote:
..
Well, devd wasn't particularly happy about that:
...
My bad -- I misread the manpage.
This will work better probably:
notify 0 {
match system IFNET;
match type LINK_UP;
media-type 802.11;
On Wed, Jul 11, 2012 at 12:01:01PM +0900, Hiroki Sato wrote:
...
hr Gr, it may be due to my change of r238279. I am investigating it.
Committed a fix as r238361. Please try it.
And we have a winner! Thank you! :-)
[Sorry for the delay; I had already updated my sources to r238345 early
Just finished updating from r238227 to r238290 on the head slice of my
laptop, and was unable to make use of the wlan(4) NIC; I captured the
following via cut/paste from ttyv0:
...
Setting hostname: localhost.
Starting dhclient.
em0: no link .. giving up
/etc/rc.d/dhclient: WARNING:
Just updated my laptop's head slice from r237378 to r237440; while
it did manage to get to multi-user mode, I was only able to login as
root, and whenever I tried to do much of anything, the sell (csh) exited
with a SIGSEGV.
I finally gave it a 3-fingered salute, [Ctl-Alt-Del], and init
appeared
On Fri, Jun 22, 2012 at 06:22:16PM +0300, Konstantin Belousov wrote:
...
found at http://www/~david/FreeBSD/head_r237440.txt.
This is on i386, right ?
Yes.
Can you boot single-user and just type date in the shell ?
Does it segfault ?
If yes, does setting sysctl
On Sun, May 13, 2012 at 10:59:17PM +0900, Mitsuru IWASAKI wrote:
OK, we need some more investigation on RELENG_8 SMP.
I think Core 2 Duo can run amd64, would like to confirm
this problem can be reproduced only on i386 or not.
Could you try same thing on amd64?
Well, that will require a
On Fri, May 11, 2012 at 11:10:19AM +0900, Mitsuru IWASAKI wrote:
Hi
I've been working on suspend/resume for SMP/i386 for a week
and created patches against CURRENT, RELENG_9 and RELENG_8
available at:
http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-CURRENT-20120511.diff
...
A
On Fri, May 11, 2012 at 11:10:19AM +0900, Mitsuru IWASAKI wrote:
Hi
I've been working on suspend/resume for SMP/i386 for a week
and created patches against CURRENT, RELENG_9 and RELENG_8
available at:
http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-CURRENT-20120511.diff
On Fri, May 11, 2012 at 11:10:19AM +0900, Mitsuru IWASAKI wrote:
Hi
I've been working on suspend/resume for SMP/i386 for a week
and created patches against CURRENT, RELENG_9 and RELENG_8
available at:
http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-CURRENT-20120511.diff
On Sat, Apr 28, 2012 at 08:25:37AM +0700, Erich Dollansky wrote:
...
FreeBSD 10.0 gives me this error message:
=== kerberos5/tools (obj,depend,all)
=== kerberos5/tools/make-print-version (obj)
cd: /usr/src/kerberos5/tools/make-print-version: No such file or directory
*** [obj] Error code 2
On Sat, Apr 28, 2012 at 08:50:47AM +0700, Erich Dollansky wrote:
...
I use the following commands to do the compilation:
cd /usr/src
/usr/bin/nice -n 20 make buildworld
OK. That should build the userland OK.
Have you reviewed /usr/src/UPDATING? Near the end of that file, there
is a
After applying Dimitry Andric's patches to contrib/jemalloc and replacing
/usr/bin/as with one built last Sunday, I was finally(!) able to rebuild
head as of 234536:
FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #797
234536M: Sat Apr 21 10:23:33 PDT 2012
I update my local mirror of the SVN repo nightly, then use it to track
stable/8, stable/9, and head in the mornings -- both on my laptop on
my local build machine.
While that usually just works, head has been a bit more turbulent in
the last few days.
My last successful build of head is
On Sun, Apr 08, 2012 at 01:29:36PM +0200, O. Hartmann wrote:
I loose hair ...
Since yesterady's make world (last make world: the day before
yesterday), getting FreeBSD 10.0-CURRENT/amd64 to r234000 or so, the X11
system on all of our FreeBSD 10.0-CUR/amd64 boxes start rejecting the
start of
Kernel build @ r233941 failed for me this morning, running:
FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #525 233918M:
Thu Apr 5 04:42:37 PDT 2012
r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386
thus:
...
ototypes -Wmissing-prototypes -Wpointer-arith
On Thu, Apr 05, 2012 at 10:43:04AM +0300, Gleb Kurtsou wrote:
...
Summary: as before, I believe that the patch didn't hurt anything, but
it also doesn't restrict the usable size of /tmp to the specified size
(from /etc/fstab):
I've checked on i386 and patch worked as expected, but it
On Wed, Apr 04, 2012 at 12:50:35PM +0300, Gleb Kurtsou wrote:
...
tmpfs-32bit-size_max.patch.txt should fix the problem. I don't have i386
installations to test it myself.
Do you run PAE kernel? Could you try filling up /tmp at least to 10g.
...
After updating source to r233868, applying
On Tue, Apr 03, 2012 at 08:55:34AM -0400, John Baldwin wrote:
...
You can actually use that on 8 and 9 as well. I think it's a likely a bug
that it used VM_MEMATTR_UNCACHED in the first place and that it should
have
been using VM_MEMATTR_UNCACHEABLE all along. (Which is why I've
On Mon, Apr 02, 2012 at 01:31:19PM +0300, Gleb Kurtsou wrote:
...
You could try the patch attached. It adds support for size option suffixes
(like 1g) and introduces swap limit (part of the older patch, not sure
if it's any use).
Patch is against 10-CURRENT.
Older version:
On Mon, Apr 02, 2012 at 01:31:19PM +0300, Gleb Kurtsou wrote:
...
In any case, effective maximum usable size for tmpfs involves SIZE_MAX
(~4G) PAGE_SIZE (4K, in my case).
size_t is 64-bit on 64-bit archs.
OK. Still, the requirement that the size specification be in bytes
is
On Mon, Apr 02, 2012 at 01:31:19PM +0300, Gleb Kurtsou wrote:
...
You could try the patch attached. It adds support for size option suffixes
(like 1g) and introduces swap limit (part of the older patch, not sure
if it's any use).
Patch is against 10-CURRENT.
Older version:
I track stable/8, stable/9, and head on (different slices on) my laptop
on a daily basis. I share /usr/local among all of these: while I update
the installed ports on a daily basis, I'm unwilling to do that 3 times
daily. :-}
The x11/nvidia-driver port is one, however, that I've found helpful to
On Fri, Mar 30, 2012 at 12:18:58PM -0400, John Baldwin wrote:
...
I've sent an e-mail to the NVIDIA driver author about how best to fix this.
You can just change the driver to use VM_MEMATTR_UNCACHEABLE instead of
VM_MEMATTR_UNCACHED for now.
Thanks; I'd need to make it conditional
On Fri, Mar 30, 2012 at 01:46:58PM -0400, John Baldwin wrote:
...
You can actually use that on 8 and 9 as well. I think it's a likely a bug
that it used VM_MEMATTR_UNCACHED in the first place and that it should have
been using VM_MEMATTR_UNCACHEABLE all along. (Which is why I've renamed
the
On Thu, Mar 29, 2012 at 04:18:06PM +0200, O. Hartmann wrote:
I was wondering if there are some objections using TMPFS for /tmp and
/var/run.
...
My question is whether there are objections using TMPFS for bot /tmp/
and /var/run/ at this stage on FreeBSD 10.0-CURRENT/amd64?
I have no
On Thu, Mar 29, 2012 at 02:50:00PM -0500, Eric van Gyzen wrote:
...
However, if you always want to use tmpfs instead of stable storage,
please do not. Some people expect /tmp to be persistent. This is why
/etc/defaults/rc.conf has clear_tmp_enable=NO. Changing this would
break the POLA.
On Thu, Mar 29, 2012 at 10:07:01PM +0200, O. Hartmann wrote:
...
Aren't MDMFS backed filesystems of static size? And haven't they to be
created first before they can be used? Using TMPFS seems toi be a more
convenient way to me - dynamical (?), using a fstab entry for convenience.
One may
On Tue, Jan 17, 2012 at 01:57:48PM +0200, Octavian Rinciog wrote:
Hello!
After updating to FreeBSD 10.0-CURRENT #0 r230054, I can't do anymore
dhclient on em0.
[root@freebsd ~]# uname -a
FreeBSD freebsd 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r230054: Fri Jan
13 14:29:36 EET 2012
[-stable@ removed, as there's no need to cross-post this. dhw]
On Fri, Jan 06, 2012 at 06:50:33PM +0100, Oliver Pinter wrote:
Hi All!
When svn installed and the source stored in git, then now the version
detection failed. The attached patch fixed this situation.
...
Caveat: I don't use
On Fri, Oct 21, 2011 at 04:36:05PM -0400, John Baldwin wrote:
...
Well, as of subversion-1.7, we don't have a .svn directory in
${SYSDIR} any more -- it's only at the root of the working copy
(/usr/src, in this case). So svnversion is never invoked.
So I've just hacked my copy to
On Fri, Oct 21, 2011 at 04:36:05PM -0400, John Baldwin wrote:
I'm not sure what the best fix is. One could possibly always run svnversion
if it exists?
Sure -- and use the result as long as the exit status is 0. (It's
certainly possible that svnversion exists, but the sources in
I got to wondering why the uname -a output from my head slice no
longer showed the SVN GRN after I had updated to subversion-1.7.0.1.
First thing I checked was that svnversion existed worked; check.
Then I noticed the logic iin newvers.sh:
...
for dir in /bin /usr/bin /usr/local/bin; do
On Thu, Oct 20, 2011 at 04:48:44AM -0700, David Wolfskill wrote:
...
Well, as of subversion-1.7, we don't have a .svn directory in
${SYSDIR} any more -- it's only at the root of the working copy
(/usr/src, in this case). So svnversion is never invoked.
So I've just hacked my copy
On Fri, Oct 14, 2011 at 11:55:28AM +0400, Pavel Timofeev wrote:
That's what most people think.
Could be. But to the extent that it's true, I have no reason to believe
that it's a perspective that is held uniquely (or even principally) about
FreeBSD.
Hi!
I would like to say that most
I noted the following after updating head to r226035:
...
stage 4.4: building everything
...
cc -O2 -pipe -Dxregcomp=regcomp -Dxre_exec=re_exec -Dxregexec=regexec
-Dxre_search=re_search -Dxre_compile_fastmap=re_compile_fastmap
-Dxregerror=regerror -Dxre_comp=re_comp
On Thu, Sep 08, 2011 at 07:59:59PM +0200, Olivier Smedts wrote:
...
I augment the instructions from UPDATING, prefixing the make
installworld itself with:
rm -fr /usr/include.old mv /usr/include{,.old} \
rm -fr /usr/share/man
Thus, I have reasonable confidence that the
On Wed, Sep 07, 2011 at 05:12:45PM -0700, Kevin Oberman wrote:
...
I am particularly concerned with things like header files
(/usr/include) that might bite me if not deleted.
This isn't specific to that upgrade, but when I do a make installworld,
I augment the instructions from UPDATING,
On Fri, Aug 05, 2011 at 10:43:32AM +0200, Martin Matuska wrote:
Patch updated.
...
OK; after reverting kern/vfs_mount.c to its pre-patched status on
my laptop, I applied this most recent patch without incident; it
built boots fine, which is now running:
FreeBSD g1-222.catwhisker.org.
I've only seen this on my laptop; my build machine doesn't exhibit the
panic.
r224602 is the most recent point I've built that does not exhibit the
panic at all.
The first few lines (hand-transcribed; I have no serial console on this
laptop -- the one shortcoming it has):
shared lock of
On Thu, Aug 04, 2011 at 05:54:54AM -0700, David Wolfskill wrote:
...
I will see if I can find a commit that affected at least one of the
affected files in the above list that I can revert to avoid the panic,
but I'm a bit slow for a while yet, so I figured I'd finally get around
to posting
On Thu, Aug 04, 2011 at 04:59:32PM +0300, Kostik Belousov wrote:
...
I am sure that this is caused by r224614.
Well, see: you approached it from knowledge, while I made a
quasi-educated guess. :-}
I forgot that vn_fullpath cannot operate on the locked vnode.
And I expect you have likely
I last built head at r223421; I upgraded sources to r223471. make
buildworld was uneventful; building the kernel demonstrated that I
needed the patch from r223474, which I applied (after which building the
kernel was also uneventful).
Here's a cut/paste from serial console of my build machine
On Thu, Jun 23, 2011 at 03:21:28PM +0200, Ian FREISLICH wrote:
Hi
Just got this error making a new kernel:
You need the patch from r223474:
Author: adrian
Date: Thu Jun 23 12:11:43 2011
New Revision: 223474
URL: http://svn.freebsd.org/changeset/base/223474
Log:
add missing #define
On Thu, Jun 23, 2011 at 06:12:54PM +0300, Alexander Motin wrote:
...
SVN rev 223443 broke ATAPI support. SVN rev 223475 should fix it.
Thanks -- that did resolve the issue for me.
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Depriving a girl or boy of
On Mon, Apr 18, 2011 at 08:05:40AM -0400, John Baldwin wrote:
...
output from:
sysctl -a |grep acpi
is here: https://privatepaste.com/ca08d4658b
I suspect it is still there, but sysctl doesn't know how to display it
anymore. This is probably due to the changes with formatting of
On Mon, Apr 18, 2011 at 08:43:56AM -0700, m...@freebsd.org wrote:
I don't seem to have a hw.acpi.thermal sysctl node on my box. Can
someone please try this patch?
Well, no magic smoke leaked out when I tried it, and:
FreeBSD 9.0-CURRENT #203 r220770M: Mon Apr 18 09:51:15 PDT 2011
Sources actually updated to r219820; change from r219821 was
hand-applied. That got me through the buildworld. :-}
Building kernel modules fails, though:
stage 3.1: making dependencies
...
stage 3.2: building everything
...
=== mlx (all)
...
=== mlx4 (all)
cc -O2 -pipe -DINET6
I run powerd(8) on my laptop, and track both stable/8 and head on it (on
different slices), daily.
I am now finally(!) getting around to pointing out that it appears that:
* /etc/rc.d/powerd tries to make use of sysctl OID dev.cpu.0.freq.
* That OID exists in stable/8.
* It does not exist in
As usual, I have been tracking, building, booting head daily on my
laptop for a while.
Yesterday, having built head at r217090, I had updated to r217145,
built, and booted it OK. (I then booted from my stable/8 slice for the
rest of the day, as usual.)
This morning, I updated to r217189, but
On Mon, Dec 20, 2010 at 05:26:15PM -0500, John Baldwin wrote:
On Monday, December 20, 2010 4:38:57 pm Ivan Klymenko wrote:
?? Mon, 20 Dec 2010 16:02:46 -0500
John Baldwin j...@freebsd.org ??:
Not working :(
This was debugging, not a fix. Try this possible fix:
Index:
On Sun, Nov 14, 2010 at 09:40:45AM -0600, eculp wrote:
I build world several times a week on this machine:
9.0-CURRENT FreeBSD 9.0-CURRENT #126: Mon Nov 8 07:22:49 CST 2010
Since the above build I have not been able to get past gnu.
Today it broke at gdb :
...
Stop in
On Thu, Nov 04, 2010 at 04:53:16PM +0200, Ivan Klymenko wrote:
Hello, people!
After the upgrade to FreeBSD 9.0-CURRENT svn revision 214735 does not
build world: ...
I had no problem going from FreeBSD 9.0-CURRENT #33 r214732 to r214777.
Peace,
david
--
David H. Wolfskill
On Thu, Nov 04, 2010 at 05:15:43PM +0200, Ivan Klymenko wrote:
...
Do you use when building make option -j?
I'm using -j 3
I used -j 4.
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.
See
On Wed, Nov 03, 2010 at 08:27:02AM +0100, Bernhard Schmidt wrote:
...
There is ieee80211_notify_radio(), granted iwn(4) misses the calls.. that
function is supposed to notify upper layers about the radio state (0 = off, 1
= on). Anyways, once wpa_supplicant import/update is done, I'll
On Tue, Nov 02, 2010 at 08:40:54AM +0100, Bernhard Schmidt wrote:
I have the switch on this laptop in position to disable the wireless
device (iwn(4)). Is there some way wpa_supplicant (or something) might
be able to recognize that this is a pointless exercise?
Well iwn could
On Tue, Nov 02, 2010 at 06:30:10PM +0100, Bernhard Schmidt wrote:
Thanks. I had quick look into that and I currently do not see an easy
way to address that issue, as in tell wpa_supplicant about the device's
state. This might change though once a newer wpa_supplicant has been
imported.
FreeBSD 9.0-CURRENT #31 r214621M
Nov 1 15:09:40 d130 wpa_supplicant[569]: Failed to initiate AP scan.
Nov 1 15:10:10 d130 last message repeated 3 times
Nov 1 15:10:50 d130 last message repeated 4 times
...
Nov 1 15:11:00 d130 wpa_supplicant[569]: Failed to initiate AP scan.
Nov 1 15:11:10
On Mon, Oct 04, 2010 at 10:44:18AM +0300, Andriy Gapon wrote:
...
Interesting!
:-}
So, init thread is blocked in vfs_mountroot()-g_waitidle() waiting for geom
to
complete probing cd device, but the latter is blocked in cam_periph_getccb()
waiting for a ccb.
Can you try to reproduce this
On Fri, Oct 01, 2010 at 08:56:13PM -0500, Brandon Gooch wrote:
On Fri, Oct 1, 2010 at 8:33 PM, David Wolfskill da...@catwhisker.org wrote:
On Fri, Oct 01, 2010 at 04:30:01PM -0700, David Wolfskill wrote:
...
I found the disabling the Module Bay appears to avoid the hang --
reliably
On Fri, Oct 01, 2010 at 08:38:59PM -0700, David Wolfskill wrote:
On Fri, Oct 01, 2010 at 08:56:13PM -0500, Brandon Gooch wrote:
...
Any ideas on what mught be causing CURRENT to hang -- sometimes
-- given that it appears to involve the Modular Bay (or the specific
device
On Sun, Oct 03, 2010 at 02:52:19PM +0300, Andriy Gapon wrote:
on 03/10/2010 14:28 David Wolfskill said the following:
[snipped]
Can't you just drop to DDB prompt and examine where the threads are?
Eh -- thanks for the reality check; I needed that. :-}
OK; I enabled the KDB DDB options
On Sun, Oct 03, 2010 at 03:42:51PM -0700, Julian Elischer wrote:
...
well you got the stacktrace of the keyboard handler since you got into
ddb via the keyboard..
OK
you need to see what ELSE is running.. especially the initial threads.
and look at THOSE stacks
Ah. My lack of
I have recently acquired a new laptop (to replace the Frankenlaptop
I've been using for the last several years).
The new machine is a Dell Precision M4400, so it's pretty recent
technology compared to what I'm used to. :-}
I installed FreeBSD 8.1-R on slice 1, customized it a bit to work in my
On Fri, Oct 01, 2010 at 02:20:38PM -0700, David Wolfskill wrote:
I have recently acquired a new laptop (to replace the Frankenlaptop
I've been using for the last several years).
...
While I'm not about to assume that this indicates something wrong
with FreeBSD, I'm a bit less inclined
On Fri, Oct 01, 2010 at 04:30:01PM -0700, David Wolfskill wrote:
...
I found the disabling the Module Bay appears to avoid the hang --
reliably.
That appears to be the minimally-invasive change necessary to avoid the
hang.
Until I realized what was in the Modular Bay: the CD/CVD
On Fri, Oct 01, 2010 at 07:22:33PM -0700, Garrett Cooper wrote:
...
Any ideas on what mught be causing CURRENT to hang -- sometimes
-- given that it appears to involve the Modular Bay (or the specific
device that is in the bay during the hang)?
Do you have boot -v output?
Yes;
On Fri, Oct 01, 2010 at 08:56:13PM -0500, Brandon Gooch wrote:
...
Any ideas on what mught be causing CURRENT to hang -- sometimes
-- given that it appears to involve the Modular Bay (or the specific
device that is in the bay during the hang)?
If you haven't already, it may be worth
On Fri, Oct 01, 2010 at 08:37:50PM -0700, Garrett Cooper wrote:
...
This might sound like a stupid idea, but can you try booting with
a CD/DVD in the drive?
Ah -- sorry about that. :-(
OK; it may be a bit before I get a successful verbose boot without
ATA_CAM and with the CD/DVD drive
On Fri, Oct 01, 2010 at 08:37:50PM -0700, Garrett Cooper wrote:
...
albert(8.1-S)[11] ls -lT
total 196
-rw-r--r-- 1 david wheel 11497 Oct 1 20:19:06 2010 console.log
-rw-r--r-- 1 david wheel 60397 Oct 1 19:26:23 2010 dmesg.boot
-rw-r--r-- 1 david wheel 114752 Oct 1
501 - 600 of 885 matches
Mail list logo
