On Thu, Mar 13, 2008 at 03:59:35PM +0200, Dan Kenigsberg wrote:
On Thu, Mar 13, 2008 at 01:16:46PM +0200, Dan Shimshoni wrote:
Dan,
- It could be that you encountered (or discovered) a kernel BUG
with the locking mechansim of bridge devices.
- What I would suggest is the
On Thu, Mar 13, 2008 at 02:08:05PM +1100, Amos Shapira wrote:
On Thu, Mar 13, 2008 at 3:29 AM, Dan Kenigsberg
[EMAIL PROTECTED] wrote:
Thanks for the idea. What could cause SIGSEGV on brctl?
My dmesg has a lot of noise, but no segfault visible.
Mar 9 04:53:49 w kernel: device if_11
Dan,
- It could be that you encountered (or discovered) a kernel BUG
with the locking mechansim of bridge devices.
- What I would suggest is the following:
- First, If you can give more details (kernel version / disto) it would help.
- Second, if you can post this mailing list the
On Thu, Mar 13, 2008 at 11:14:04AM +, Amos Shapira wrote:
On Thu, Mar 13, 2008 at 8:43 AM, Dan Kenigsberg [EMAIL PROTECTED]
wrote:
On Thu, Mar 13, 2008 at 02:08:05PM +1100, Amos Shapira wrote:
On Thu, Mar 13, 2008 at 3:29 AM, Dan Kenigsberg
[EMAIL PROTECTED] wrote:
Thanks for
On Thu, Mar 13, 2008 at 01:16:46PM +0200, Dan Shimshoni wrote:
Dan,
- It could be that you encountered (or discovered) a kernel BUG
with the locking mechansim of bridge devices.
- What I would suggest is the following:
- First, If you can give more details (kernel version /
Hi List,
I'm creating tun interfaces, deleting them, and connecting them to a bridge (not
necessarily in that order).
Occasionally, brctl aborts in what looks like a call to abort(2). I get
/bin/sh: line 1: 30963 Aborted sudo /usr/sbin/brctl show sw0
Now what may be causing it?
On Thu, Mar 13, 2008 at 3:29 AM, Dan Kenigsberg
[EMAIL PROTECTED] wrote:
Thanks for the idea. What could cause SIGSEGV on brctl?
My dmesg has a lot of noise, but no segfault visible.
Mar 9 04:53:49 w kernel: device if_11 entered promiscuous mode
Mar 9 04:53:49 w kernel: sw0: port
