From: Patrick McHardy <kaber@trash.net>
To: Ramon Casellas <ramon.casellas@cttc.es>
Cc: "'J. K. Cliburn'" <jcliburn@gmail.com>,
'Jarek Poplawski' <jarkao2@gmail.com>,
netdev@vger.kernel.org
Subject: Re: atl1 warn_on_slowpath help
Date: Wed, 29 Oct 2008 17:47:49 +0100 [thread overview]
Message-ID: <490893B5.6090806@trash.net> (raw)
In-Reply-To: <B936998C7BAD4852B0CD9AB17E72CFD0@CTTCA769C54C37>
Ramon Casellas wrote:
>> -----Mensaje original-----
>> De: J. K. Cliburn [mailto:jcliburn@gmail.com]
>
>> Can you please try the attached patch from Patrick and see if it fixes
>> your kernel warning?
>
> I applied the patch to linux.2.6.27.2 (already patched for VLAN support on
> ATL1 devices as per Jay fix). Patch applied cleanly and there was no warn on
> slow path on dmesg after the reboot, with fully functional VLAN (broken in
> atl cards since 2.6.26)
>
> Linux failamp 2.6.27.2 #1 SMP Wed Oct 29 14:22:49 CET 2008 i686 GNU/Linux
>
> 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
> UP qlen 1000
> link/ether 00:1f:c6:bb:75:fa brd ff:ff:ff:ff:ff:ff
> inet 1.1.1.91/24 brd 1.1.1.255 scope global eth0
> inet6 fe80::21f:c6ff:febb:75fa/64 scope link
> valid_lft forever preferred_lft forever
>
> 4: eth0.200@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP
> link/ether 00:1f:c6:bb:75:fa brd ff:ff:ff:ff:ff:ff
> inet 10.1.1.91/24 brd 10.1.1.255 scope global eth0.200
> inet6 fe80::21f:c6ff:febb:75fa/64 scope link
> valid_lft forever preferred_lft forever
> 5: eth0.300@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP
> link/ether 00:1f:c6:bb:75:fa brd ff:ff:ff:ff:ff:ff
> inet 192.168.100.91/24 brd 192.168.100.255 scope global eth0.300
> inet6 fe80::21f:c6ff:febb:75fa/64 scope link
> valid_lft forever preferred_lft forever
>
> I played a bit with tshark:
>
> failamp:/mnt# tshark -i eth0.300
> Running as user "root" and group "root". This could be dangerous.
> Capturing on eth0.300
> 0.000000 Cisco_35:9a:11 -> PVST+ STP Conf. Root =
> 33068/00:0e:84:50:ff:80 Cost = 12 Port = 0x8011
>
> Thanks for your efforts. Let me know if you need further testing.
This seems to be enough, thanks a lot.
next prev parent reply other threads:[~2008-10-29 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 0:08 atl1 warn_on_slowpath help Jay Cliburn
2008-10-29 7:15 ` Jarek Poplawski
2008-10-29 8:12 ` Patrick McHardy
2008-10-29 10:17 ` Patrick McHardy
2008-10-29 12:51 ` J. K. Cliburn
2008-10-29 12:54 ` Patrick McHardy
2008-10-29 14:15 ` Ramon Casellas
2008-10-29 16:47 ` Patrick McHardy [this message]
2008-10-29 13:03 ` Jarek Poplawski
2008-10-29 13:09 ` Patrick McHardy
2008-10-29 13:22 ` Jarek Poplawski
2008-10-29 13:26 ` Patrick McHardy
2008-10-29 14:04 ` Jarek Poplawski
2008-10-29 16:40 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=490893B5.6090806@trash.net \
--to=kaber@trash.net \
--cc=jarkao2@gmail.com \
--cc=jcliburn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ramon.casellas@cttc.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).