Subject: Re: Panic when bringing up network bridge
To: <>
From: Francis Koclas <netbsd@geekrants.org>
List: port-cobalt
Date: 04/26/2006 07:27:18
Izumi Tsutsui wrote:
> Okay, "transmit timeout" is caused by lost TX interrupts,
> and "link state changed" is caused by reset of tlp after timeout.
> Maybe some stray interrupts block tlp interrupts,
> or inappropriate interrupt level is set in some place?
>
> Could you check interrupt/network statistics before and after brconfig,
> i.e. could you post result of commands:
> # netstat -i; vmstat -c 3 -i 1; brconfig bridge0 up; vmstat -c 3 -i 1
> or something?
> ---
> Izumi Tsutsui
Here are the results:
1) setup the bridge
(not enabled)
2) netstat -i
http://geekrants.org/francis/netbsd/cobalt/netstat.png
3) vmstat -c 3 -i 1
http://geekrants.org/francis/netbsd/cobalt/vmstat0.png
4) enabled the bridge
5) vmstat -c 3 -i 1
http://geekrants.org/francis/netbsd/cobalt/vmstat1.png
It took quite a while to be able to run the second vmstat.. a couple
seconds after enabling the bridge, both green/orange lights for both
ethernet ports stayed light up constantly for a good 30 seconds or so,
freezing even the serial console. The results were taken are right after
it would let me type in the console again.
Looks like quite an interrupt storm..
Thank for your continued support :)
Francis