See tinderbox log, my -wirelesss mail etc.
I'm waiting for a fix too.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/kernel-s-make-fails-in-ath-module-stable9-tp579p5777859.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
...should be fixed, as it is already reverted.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/kernel-s-make-fails-in-ath-module-stable9-tp579p5777864.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
On 2013-01-15 12:31, Jakub Lach wrote:
...should be fixed, as it is already reverted.
Yes, sorry about that breakage. It should be fixed as of r245449.
The good news is that stable/9 now has clang 3.2 release. :-)
___
freebsd-stable@freebsd.org mail
On Tue, Jan 15, 2013 at 12:29 AM, Ben Morrow wrote:
> Quoth Shawn Webb :
> >
> > I've been working on sharing a 6in4 IPv6 tunnel (via a gif device) I have
> > with Hurricane Electric (tunnelbroker.net) to my jails via epair
> devices.
> > My setup is a bit unique in that the IPv6 tunnel is behind
On Jan 11, 2013, at 2:06 PM, Fleuriot Damien wrote:
> Hello list,
>
>
> I'm running 8.3-stable r245223 from a mere 2 days ago and am in the process
> of building a custom release for our internal use as preconfigured firewalls.
>
> "make release" works pretty fine except for a few quirks here
Quoth Shawn Webb :
> On Tue, Jan 15, 2013 at 12:29 AM, Ben Morrow wrote:
> > Quoth Shawn Webb :
> > >
> > > # ifconfig bridge0
> > > bridge0: flags=8843 metric 0 mtu
> > > 1500
> > > ether 02:fe:21:34:d3:00
> > > inet6 2001:470:8142:1::1 prefixlen 64
> > > nd6 options=21
> > > id 00:00:00:00:00:00
Dear All,
Still experiencing the same hangs I reported earlier with 9.1. I've been
running a kernel with WITNESS enabled to provide more information.
During an occurrence of the hang, running show alllocks gave
Process 25777 (sysctl) thread 0xfe014c5b2920 (102567)
exclusive sleep mutex Giant
On Tue, Jan 15, 2013 at 2:54 PM, Ben Morrow wrote:
> Quoth Shawn Webb :
> > On Tue, Jan 15, 2013 at 12:29 AM, Ben Morrow wrote:
> > > Quoth Shawn Webb :
> > > >
> > > > # ifconfig bridge0
> > > > bridge0: flags=8843 metric 0
> mtu
> > > > 1500
> > > > ether 02:fe:21:34:d3:00
> > > > inet6 2001:4
Somehow there ended up a typo in the CC to freebsd-stable@freebsd.org. Last
email below:
On Tue, Jan 15, 2013 at 5:53 PM, Shawn Webb wrote:
> On Tue, Jan 15, 2013 at 4:52 PM, Ben Morrow wrote:
>
>> Quoth Shawn Webb :
>> > On Tue, Jan 15, 2013 at 2:54 PM, Ben Morrow wrote:
>> > >
>> > > ifc
At 5PM -0500 on 15/01/13 you (Shawn Webb) wrote:
>
> I figured it out. In my jail initialization scripts, I'm running '/bin/sh
> /bin/rc' after doing initial network setup. The rc script puts the
> interface in IFDISABLED mode. So if I run the ifconfig command to remove
> the flag, I'm golden.
Y
I don't know if this is relevant or not, but I deadlock was recently
fixed in the VFS code:
http://svnweb.freebsd.org/base?view=revision&revision=244795
On Tue, Jan 15, 2013 at 12:55 PM, olivier wrote:
> Dear All,
> Still experiencing the same hangs I reported earlier with 9.1. I've been
> runni
My understanding is that the locks (and pieces of kernel code) involved are
different.
Maybe someone more knowledgeable than I am can comment.
Thanks for the suggestion...
Olivier
On Tue, Jan 15, 2013 at 4:07 PM, Reed A. Cartwright wrote:
> I don't know if this is relevant or not, but I deadlock
12 matches
Mail list logo
