On Tue, Jan 17, 2012 at 5:09 PM, Marcelo/Porks wrote:
> Hi guys, I do not know if this is the correct mail list to report this.
>
> I'm trying to compile the port x11-wm/awesome but failed with the error:
>
> [ 37%] Building C object CMakeFiles/awesome.dir/common/tokenize.c.o
> Linking C executabl
Hi guys, I do not know if this is the correct mail list to report this.
I'm trying to compile the port x11-wm/awesome but failed with the error:
[ 37%] Building C object CMakeFiles/awesome.dir/common/tokenize.c.o
Linking C executable awesome
[ 37%] Built target awesome
Scanning dependencies of ta
on 17/01/2012 17:34 m...@freebsd.org said the following:
> 2012/1/17 Gleb Smirnoff :
>> New panic has been introduced somewhere between
>> r229851 and r229932, that happens on shutdown if
>> kernel has WITNESS and doesn't have WITNESS_SKIPSPIN.
[**]
>> Uptime: 1h0m17s
>> Rebooting...
>> panic: mtx
On Mon, Jan 16, 2012 at 03:54:02PM -0800, Steve Kargl wrote:
> On Mon, Jan 16, 2012 at 10:38:04PM +0100, Dimitry Andric wrote:
> > On 2012-01-16 21:42, Steve Kargl wrote:
> > >Is anyone else seeing svn getting stuck while
> > >updating /usr/src on an update-to-date freebsd-current?
> >
> > I saw t
On Thu, 2012-01-12 at 07:45:34 +, Bjoern A. Zeeb wrote:
> Hey,
>
> after two years I had the opportunity to run the build option survey,
> initially done by phk, again. The number of options seems to have grown
> quite a bit it felt. I have not even looked at the results yet but here
> they
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
On 01/17/2012 03:57, Octavian Rinciog wrote:
> Jan 13 14:41:58 freebsd dhclient[1734]: em0: not found
You need to update your world and kernel together. The ability to run
new kernel on an old world (as is the usual upgrade method) was broken a
little while ago, and the compatibility shims to fix
On Tue, Jan 17, 2012 at 07:34:23AM -0800, m...@freebsd.org wrote:
m> 2012/1/17 Gleb Smirnoff :
m> > New panic has been introduced somewhere between
m> > r229851 and r229932, that happens on shutdown if
m> > kernel has WITNESS and doesn't have WITNESS_SKIPSPIN.
m> >
m> > Uptime: 1h0m17s
m> > Reboot
On Tue, Jan 17, 2012 at 01:57:48PM +0200, Octavian Rinciog wrote:
O> Hello!
O>
O> After updating to FreeBSD 10.0-CURRENT #0 r230054, I can't do anymore
O> dhclient on em0.
O>
O> [root@freebsd ~]# uname -a
O> FreeBSD freebsd 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r230054: Fri Jan
O> 13 14:29:36 EET
Hi,
* Monthadar Al Jaberi , 20120117 18:17:
> But now I get another error when installworld
I suspect something unrelated to my change is the culprit. Can you make
sure your source tree is not modified, for example by checking out using
a different cvsup mirror?
Thanks,
--
Ed Schouten
On Mon, Jan 16, 2012 at 9:54 PM, Ed Schouten wrote:
> Hi Monthadar,
>
> * Monthadar Al Jaberi , 20120116 18:48:
>> I updated my source tree to lastest and buildworld and buildkernel
>> without error. but installworld gives this error:
>>
>> install: posix_memalign.3.gz: No such file or directory
>
2012/1/17 Gleb Smirnoff :
> New panic has been introduced somewhere between
> r229851 and r229932, that happens on shutdown if
> kernel has WITNESS and doesn't have WITNESS_SKIPSPIN.
>
> Uptime: 1h0m17s
> Rebooting...
> panic: mtx_lock_spin: recursed on non-recursive mutex cnputs_mtx @
> /usr/src
On Friday, January 13, 2012 10:27:13 pm aconnoll...@yahoo.co.jp wrote:
> Please try this patch:
>
> Index: sys/dev/atkbdc/atkbdc_isa.c
> ===
> --- atkbdc_isa.c(revision 230009)
> +++ atkbdc_isa.c(working copy)
> @@ -87,6 +87,7
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 root@freebsd:/usr/obj/usr/head/sys/GENERIC
i386
[root@freebsd ~]# cat /var/log/m
New panic has been introduced somewhere between
r229851 and r229932, that happens on shutdown if
kernel has WITNESS and doesn't have WITNESS_SKIPSPIN.
Uptime: 1h0m17s
Rebooting...
panic: mtx_lock_spin: recursed on non-recursive mutex cnputs_mtx @
/usr/src/head/sys/kern/kern_cons.c:500
cpuid = 0
15 matches
Mail list logo