On Wed, Mar 12, 2008 at 02:37:44PM +0200, Gilad Ben-Yossef wrote:
> Dan Kenigsberg wrote:
> >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? Might it be the fact that in the same time
> >other
> >processes are playing with brctl {addif,delif} ?
> >
> >A quick peek at the brctl code show no reference to abort(), so it probably
> >comes from a deeper place. Any guess from where?
> >
>
> It means brctl caught a SIGSEGV.
>
> Run "dmesg" after one of these incidents. I have a feeling the results
> will be interesting.
>
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
--
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]
