Linux Ethernet Bridging - May 2011 - [Bridge] [Bugme-new] [Bug 35992] New: Regression: oops when using a bridge interface with tg3

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

2.6.38->2.6.39 regression, appears to be bridge-related.  There's a
partial screencap of the oops linked below.

Bernd, it would be helpful if you could set the screen to more rows
(50?) and then retake that photo.  Documentation/svga.txt might help
out.  Thanks.


On Fri, 27 May 2011 15:28:17 GMT
bugzilla-daemon at bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=35992
> 
>            Summary: Regression: oops when using a bridge interface with
>                     tg3
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.39
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Network
>         AssignedTo: drivers_network at kernel-bugs.osdl.org
>         ReportedBy: bzed at debian.org
>         Regression: Yes
> 
> 
> Created an attachment (id=59712)
>  --> (https://bugzilla.kernel.org/attachment.cgi?id=59712)
> backtrace image
> 
> Using a bridge interface with
> - eth0 from a Tigeon3 card (Broadcom Corporation NetXtreme BCM5704 Gigabit
> Ethernet [14e4:1648] (rev 10))
> - 3 veth interfaces from LXC
> results in a kernel oops on 2.6.39. Up and until 2.6.38.7 I did not run
into
> the issue.
> 
> Unfortunately I'm only able to provide a screenshot or a part of the
backtrace
> as I don't have a proper serial console available.
> 
> -- 
> Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.

On 05/28/2011 12:21 AM, Andrew Morton wrote:
> 2.6.38->2.6.39 regression, appears to be bridge-related.  There's a
> partial screencap of the oops linked below.
The oops happens as soon as I add the lxc veth interface to the bridge, before
everything works as expected.


A new, full screenshot is attached
https://bugzilla.kernel.org/attachment.cgi?id=59732


(For yet unknows reasons I can't access the serial port redirection via ssh
and
I won't be able to attach a real serial port cable before Monday, so I'm
afraid
you have to work with the screenshot for now.)

> Bernd, it would be helpful if you could set the screen to more rows
> (50?) and then retake that photo.  Documentation/svga.txt might help
> out.  Thanks.
(the kernel says that vga=... is deprecated, guess that documentation is
outdated?)

Thanks and cheers,

Bernd

-- 
 Bernd Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Le samedi 28 mai 2011 ? 10:58 +0200, Bernd Zeimetz a ?crit
:
> On 05/28/2011 12:21 AM, Andrew Morton wrote:
> > 2.6.38->2.6.39 regression, appears to be bridge-related. 
There's a
> > partial screencap of the oops linked below.
> 
> The oops happens as soon as I add the lxc veth interface to the bridge,
before
> everything works as expected.
> 
> 
> A new, full screenshot is attached
> https://bugzilla.kernel.org/attachment.cgi?id=59732
> 
> 
> (For yet unknows reasons I can't access the serial port redirection via
ssh and
> I won't be able to attach a real serial port cable before Monday, so
I'm afraid
> you have to work with the screenshot for now.)
> 
> 
> > Bernd, it would be helpful if you could set the screen to more rows
> > (50?) and then retake that photo.  Documentation/svga.txt might help
> > out.  Thanks.
> 
> (the kernel says that vga=... is deprecated, guess that documentation is
outdated?)
> 
OK, this sounds like an already fixed bug.

(commit : 33eb9873a283a bridge: initialize fake_rtable metrics)

Could you try latest linux-2.6 tree ?

By the way, if panic stills happen, could you try netconsole ?

Here I just add
"netconsole=4444 at 192.168.20.108/eth1,4444 at
192.168.20.112/00:1e:0b:ec:c3:e4" to my boot param

192.168.20.108 is my ip addr,
192.168.20.112 the ip addr of "remote machine",
00:1e:0b:ec:c3:e4 the mac addr of "remote machine"

On "remote machine" I start : netcat -l -u -p 4444 </dev/null


Thanks