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 scripts you are
running (for adding/deleting the tun device) and describe
the environment (how you exactly start and configure the tun devices,
etc). that cause this crash it will really help.
I, for one , will happily try to test it on two Linux machines to see
if it crash , and I believe that there will be others.
Regards,
DS
On Thu, Mar 13, 2008 at 10: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 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 5(if_11) entering learning state
> > > Mar 9 04:53:49 w kernel: sw0: topology change detected, propagating
> >
> > Enable core dumps ("ulimit -c unlimited").
>
> Did that. No traces of a segfault.
>
>
> --
> Dan Kenigsberg http://www.cs.technion.ac.il/~danken ICQ
> 162180901
>
> =================================================================
>
>
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
>
>
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
