I guarantee you that a simple interface list with ifconfig un-stucks the
net on my setup, at lest in the case (master is wired, unplug ethernet,
fail to wireless) I agree that it doesn't makes much sense, but no matter
how unlikely it seems, it is a **fact**.
>
> I don't believe in merely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/17/13, 11:28 PM, dan_partelly wrote:
>
> What claims you do not "believe" ? Not important anyway. This is
> engineering, so you need not believe, you need to know. Go and
> replicate the bug. You will know then.
I don't believe in merely doi
What claims you do not "believe" ? Not important anyway. This is
engineering, so you need not believe, you need to know. Go and replicate
the bug. You will know then.
>
> I don't really believe these claim.
>
> I had similar issue in the past and found an 'arp -a -d' would "fix"
> it so I di
Jean-Sébastien Pédron wrote, On 12/17/2013 22:20:
On 16.12.2013 08:36, d...@gmx.com wrote:
Still nobody wants to apply Robert Noland's DRM patch?
What problem(s) does this patch fix?
It fixes non-deterministic lockups when the (old, drm1) r300 drivers are used.
According to John Baldwin [1]
2013/12/17 Jean-Sébastien Pédron :
> On 17.12.2013 13:19, Markiyan Kushnir wrote:
>> Left my desktop (new Xorg, newcons, radeonkms) for a couple of minutes
>> and found it rebooted after a panic. Never seen this kind of panic
>> before.
>
> That's weird: the code leading to this panic in unreachabl
Mark,
On Tue, Dec 17, 2013 at 08:13:20PM +0100, Mark Martinec wrote:
M> Under 9.2 the following could be used to build an IPv6-only kernel:
M>
M> /sys/amd64/conf/TEST :
M>
M> include GENERIC
M> makeoptions MKMODULESENV+="WITHOUT_INET_SUPPORT="
M> nooptions INET
M>
M>
M> Now with stable/1
Hi,
On Tue, 17 Dec 2013 17:02:03 -0800
Xin Li wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 12/17/13 09:34, Allan Jude wrote:
> > If I am am understanding correctly, Dan and Nikolai say that just
> > running 'ifconfig' brings the lagg back to life. Why would that
> > make a
TB --- 2013-12-17 19:30:17 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-12-17 19:30:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
On 17 December 2013 17:21, Navdeep Parhar wrote:
> Any plans to get kernel debugging working?
It's on the roadmap, but no concrete plans or timeline yet.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curr
TB --- 2013-12-17 19:30:17 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-12-17 19:30:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/17/13 09:34, Allan Jude wrote:
> If I am am understanding correctly, Dan and Nikolai say that just
> running 'ifconfig' brings the lagg back to life. Why would that
> make a difference at all? Running ifconfig with no parameters
> shouldn't be
On 18.12.2013 01:27, Nathan Whitehorn wrote:
> On 12/17/13 15:32, Aleksandr Rybalko wrote:
>> On Tue, 17 Dec 2013 14:12:05 -0600
>> Nathan Whitehorn wrote:
>>
>>> On 12/17/13 14:07, Steve Kargl wrote:
On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
> To get VT switching wh
On 12/17/13 15:32, Aleksandr Rybalko wrote:
On Tue, 17 Dec 2013 14:12:05 -0600
Nathan Whitehorn wrote:
On 12/17/13 14:07, Steve Kargl wrote:
On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
To get VT switching when using KMS drivers (ATI, Intel) please use
newcons: https://wik
On Wed, Dec 18, 2013 at 12:15:52AM +0200, Aleksandr Rybalko wrote:
> On Tue, 17 Dec 2013 12:07:56 -0800
> Steve Kargl wrote:
>
> > On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
> > >
> > > To get VT switching when using KMS drivers (ATI, Intel) please use
> > > newcons: https://
Any plans to get kernel debugging working?
On 12/17/13 14:15, Ed Maste wrote:
> The in-tree snapshot of LLDB is at a point where it's usable and
> suitable for wider testing on amd64, and so I intend to enable it by
> default in the near future.
>
> Further information on the FreeBSD port of LLD
On Tue, 17 Dec 2013 14:03:43 -0800
Maksim Yevmenkin wrote:
> Hello Aleksandr
>
> >> would anyone object to this patch?
> >
> > It is good idea, but sometimes shutdown sequence longer than some
> > H/W watchdogs even support.
> > I have one board which can do only 20sec maximum time.
>
> yes. it
The in-tree snapshot of LLDB is at a point where it's usable and
suitable for wider testing on amd64, and so I intend to enable it by
default in the near future.
Further information on the FreeBSD port of LLDB is on the wiki, at
https://wiki.freebsd.org/lldb
On my desktop LLDB added about 5 minut
On Tue, 17 Dec 2013 12:07:56 -0800
Steve Kargl wrote:
> On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
> >
> > To get VT switching when using KMS drivers (ATI, Intel) please use
> > newcons: https://wiki.freebsd.org/Newcons or if that is not
> > possible, force the use of the ves
On Tue, Dec 17, 2013 at 2:00 PM, Andriy Gapon wrote:
> on 17/12/2013 20:53 Maksim Yevmenkin said the following:
>> hello,
>>
>> would anyone object to this patch?
>>
>> max
>>
>> Index: src/etc/rc.d/watchdogd
>> ===
>> --- src/etc/rc.
Hello Allan
> I've been seeing an issue where sometimes my system seems to hang after
> the shutdown. where not stopping the watchdog might help. I wonder if it
> would be best to make some kind of rc.conf variable to allow the user to
> opt for one or the other, keeping the current behaviour for
Hello Aleksandr
>> would anyone object to this patch?
>
> It is good idea, but sometimes shutdown sequence longer than some H/W
> watchdogs even support.
> I have one board which can do only 20sec maximum time.
yes. its up to the user to configure appropriate watchdog timeout.
this features is mo
on 17/12/2013 20:53 Maksim Yevmenkin said the following:
> hello,
>
> would anyone object to this patch?
>
> max
>
> Index: src/etc/rc.d/watchdogd
> ===
> --- src/etc/rc.d/watchdogd (revision 2999)
> +++ src/etc/rc.d/watchdogd
hello,
would anyone object to this patch?
max
Index: src/etc/rc.d/watchdogd
===
--- src/etc/rc.d/watchdogd (revision 2999)
+++ src/etc/rc.d/watchdogd (working copy)
@@ -39,4 +39,7 @@
pidfile="/var/run/${name}.pid"
load_
On 17.12.2013 13:19, Markiyan Kushnir wrote:
> Left my desktop (new Xorg, newcons, radeonkms) for a couple of minutes
> and found it rebooted after a panic. Never seen this kind of panic
> before.
That's weird: the code leading to this panic in unreachable, because
there's no way currently (that I
On 2013-12-17 16:28, Aleksandr Rybalko wrote:
> On Tue, 17 Dec 2013 10:53:02 -0800
> Maksim Yevmenkin wrote:
>
>> hello,
> Hi Maksim!
>
>> would anyone object to this patch?
> It is good idea, but sometimes shutdown sequence longer than some H/W
> watchdogs even support.
> I have one board which c
On Tue, 17 Dec 2013 14:12:05 -0600
Nathan Whitehorn wrote:
> On 12/17/13 14:07, Steve Kargl wrote:
> > On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
> >> To get VT switching when using KMS drivers (ATI, Intel) please use
> >> newcons: https://wiki.freebsd.org/Newcons or if that
On Tue, 17 Dec 2013 10:53:02 -0800
Maksim Yevmenkin wrote:
> hello,
Hi Maksim!
>
> would anyone object to this patch?
It is good idea, but sometimes shutdown sequence longer than some H/W
watchdogs even support.
I have one board which can do only 20sec maximum time.
>
> max
>
> Index: src/
On 16.12.2013 08:36, d...@gmx.com wrote:
> Still nobody wants to apply Robert Noland's DRM patch?
What problem(s) does this patch fix?
--
Jean-Sébastien Pédron
signature.asc
Description: OpenPGP digital signature
On Tue, Dec 17, 2013 at 12:15:33PM -0800, Adrian Chadd wrote:
> On Dec 17, 2013 2:08 PM, "Steve Kargl"
> wrote:
>
> > On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
> > >
> > > To get VT switching when using KMS drivers (ATI, Intel) please use
> > > newcons: https://wiki.freebsd.
Under 9.2 the following could be used to build an IPv6-only kernel:
/sys/amd64/conf/TEST :
include GENERIC
makeoptions MKMODULESENV+="WITHOUT_INET_SUPPORT="
nooptions INET
Now with stable/10 the:
make buildkernel KERNCONF=TEST
fails while building xen support:
[...]
cc -c -O2 -pipe -f
On 12/17/13 14:07, Steve Kargl wrote:
On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
To get VT switching when using KMS drivers (ATI, Intel) please use
newcons: https://wiki.freebsd.org/Newcons or if that is not possible,
force the use of the vesa driver for xorg.
It appears t
On Saturday, December 14, 2013 8:22:41 pm Justin Hibbits wrote:
> On Thu, 12 Dec 2013 14:15:47 -0500
> John Baldwin wrote:
>
> > On Wednesday, December 11, 2013 5:40:30 pm Justin Hibbits wrote:
> > > On Wed, Dec 11, 2013 at 1:26 PM, John Baldwin
> > > wrote:
> > > > On Thursday, December 05, 201
I'm rapidly wondering if building this way should become unsupported. Too
muxh unknown stuff is needed at startup and wed have to load all firmware
bits to make it remotely work.
On Dec 17, 2013 2:08 PM, "Steve Kargl"
wrote:
> On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
> >
>
Ive no idea sorry. Its likely an ifnet change and not anything WiFi
specific. :(
On Dec 17, 2013 12:04 PM, "dan_partelly" wrote:
>
> Yes, this is correct. A simple list of the interfaces with ifconfig
> makes the system recover and restart activity on the secondary port.
> Its a good starting poi
On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
>
> To get VT switching when using KMS drivers (ATI, Intel) please use
> newcons: https://wiki.freebsd.org/Newcons or if that is not possible,
> force the use of the vesa driver for xorg.
>
It appears that newcons is unusable with a
Yes, this is correct. A simple list of the interfaces with ifconfig
makes the system recover and restart activity on the secondary port.
Its a good starting point to hunt down the problem. One of the ioctls sent
has this "side effect".
Dan
> If I am am understanding correctly, Dan and Nikolai
On 12/17/13 12:34, Allan Jude wrote:
> On 2013-12-17 10:54, Adrian Chadd wrote:
>> Hi,
>>
>> The MAC of the lagg needs to be the same as the wireless interface.
>>
>> I'm going to just state right now that using lagg as the failover
>> method for doing wireless/wired integration isn't supported by
On 2013-12-17 10:54, Adrian Chadd wrote:
> Hi,
>
> The MAC of the lagg needs to be the same as the wireless interface.
>
> I'm going to just state right now that using lagg as the failover
> method for doing wireless/wired integration isn't supported by me. If
> someone wants to make it supported t
No problem. Can you point me to the relevant source files in the
kernel tree, please ?
Dan
On Tue, 17 Dec 2013 08:43:09 -0800, Adrian Chadd
wrote:
> I'm the wireless stack maintainer and I currently don't support that.
>
> Sorry.
>
>
>
> -a
>
> On 17 December 2013 08:10, dan_partelly wr
On 17 December 2013 08:12, Nikolai Lifanov wrote:
> Also, this method is still described in the handbook:
> https://www.freebsd.org/doc/handbook/network-aggregation.html#networking-lagg-wired-and-wireless
>
> If this isn't supposed to work, then the handbook needs to be updated.
I'd be really ha
I'm the wireless stack maintainer and I currently don't support that.
Sorry.
-a
On 17 December 2013 08:10, dan_partelly wrote:
> On Tue, 17 Dec 2013 07:54:52 -0800, Adrian Chadd
> wrote:
>> Hi,
>
> All 3 MACs are the same. wpi0 is set to the MAC of bg0. Wlan0 inherits the
> MAC of
> wpi0. La
On 12/17/13 10:54, Adrian Chadd wrote:
> Hi,
>
> The MAC of the lagg needs to be the same as the wireless interface.
>
> I'm going to just state right now that using lagg as the failover
> method for doing wireless/wired integration isn't supported by me. If
> someone wants to make it supported t
On Tue, 17 Dec 2013 07:54:52 -0800, Adrian Chadd
wrote:
> Hi,
All 3 MACs are the same. wpi0 is set to the MAC of bg0. Wlan0 inherits the
MAC of
wpi0. Lagg0 is set up to the MAC of master. So everything checks out. All
are the same.
I have to check if the systems sends packets to the gateway af
On 12/17/13 10:54, Adrian Chadd wrote:
> Hi,
>
> The MAC of the lagg needs to be the same as the wireless interface.
>
> I'm going to just state right now that using lagg as the failover
> method for doing wireless/wired integration isn't supported by me. If
> someone wants to make it supported t
Hi,
The MAC of the lagg needs to be the same as the wireless interface.
I'm going to just state right now that using lagg as the failover
method for doing wireless/wired integration isn't supported by me. If
someone wants to make it supported then they need to claim it. :)
-a
On 17 December 2
TB --- 2013-12-17 07:40:17 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-12-17 07:40:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
On 12/17/13 08:06, dan_partelly wrote:
>
> Hi all,
>
> I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as
> described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop.
>
> What happens is:
>
> If I boot the system with the Ethernet cable attached, I correctly get
> la
TB --- 2013-12-17 07:40:17 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-12-17 07:40:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
..and I believe that is the one thing that drove me away from
freebsd-update.
On 17 December 2013 16:03, Glen Barber wrote:
> On Tue, Dec 17, 2013 at 03:53:22PM +0300, Odhiambo Washington wrote:
> > Aha! I already blew away the 10-CURRENT, downloaded the RC and installed
> > (on VMware). Now I
Hi all,
I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as
described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop.
What happens is:
If I boot the system with the Ethernet cable attached, I correctly get
lagg0 active port on master- bg0- and the network is working
/var/log/messages (cut out everything before approx an hour before the
panic) and Xorg log of the panicked session:
https://drive.google.com/file/d/0B9Q-zpUXxqCnX3IzY3BHMGRSVkk/edit?usp=sharing
https://drive.google.com/file/d/0B9Q-zpUXxqCna3pfTVl2dWZraTg/edit?usp=sharing
--
Markiyan.
2013/12/
On Tue, Dec 17, 2013 at 03:53:22PM +0300, Odhiambo Washington wrote:
> Aha! I already blew away the 10-CURRENT, downloaded the RC and installed
> (on VMware). Now I can play with the stuff, including unbound,
> freebsd-update.
> BTW, I always used csup, then moved to svn on my systems. This
> freeb
Aha! I already blew away the 10-CURRENT, downloaded the RC and installed
(on VMware). Now I can play with the stuff, including unbound,
freebsd-update.
BTW, I always used csup, then moved to svn on my systems. This
freebsd-update (sorry I always felt scared about it), how does it handle a
situation
On Tue, Dec 17, 2013 at 10:49 AM, Odhiambo Washington
wrote:
>
>
> Why does this fail? I have never used freebsd-update before. It's my 1st
> time.
>
My understanding is that freebsd-update can't track changes between
different svn revisions. It doesn't have a clue about -CURRENT or
-STABLE as it
On Tue, Dec 17, 2013 at 11:49:39AM +0300, Odhiambo Washington wrote:
> Someone please help me here:
>
> root@fbsd10:/usr/src/contrib/unbound # uname -a
> FreeBSD fbsd10 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r254222: Sun Aug 11
> 20:14:02 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENER
14:00:~$ uname -a
FreeBSD mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #1
r259227: Thu Dec 12 10:17:56 EET 2013
r...@mkushnir.mooo.com:/usr/obj/usr/src/sys/MAREK amd64
Left my desktop (new Xorg, newcons, radeonkms) for a couple of minutes
and found it rebooted after a panic. Never seen thi
Fair enough. I will use svn instead. I've never liked freebsd-update.
On 17 December 2013 11:58, Niilo Kajander wrote:
> On Tue, Dec 17, 2013 at 10:49 AM, Odhiambo Washington
> wrote:
> >
> >
> > Why does this fail? I have never used freebsd-update before. It's my 1st
> > time.
> >
>
> My unde
Someone please help me here:
root@fbsd10:/usr/src/contrib/unbound # uname -a
FreeBSD fbsd10 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r254222: Sun Aug 11
20:14:02 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC
amd64
root@fbsd10:/usr/src/contrib/unbound # freebsd-update upgrade -r 10.0
58 matches
Mail list logo
