From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4CC92902.4040904@domain.hid> Date: Thu, 28 Oct 2010 09:40:50 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4CC82C8D.3080808@domain.hid> <4CC84327.9070202@domain.hid> <4CC92786.3030509@domain.hid> In-Reply-To: <4CC92786.3030509@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5FBD4A17A118816B2D8B7510" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-core] [RTnet-users] Potential problem with rt_eepro100 List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anders Blomdell Cc: rtnet-developers@domain.hid, xenomai@xenomai.org, rtnet-users This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5FBD4A17A118816B2D8B7510 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 28.10.2010 09:34, Anders Blomdell wrote: > Anders Blomdell wrote: >> Anders Blomdell wrote: >>> Hi, >>> >>> I'm trying to use rt_eepro100, for sending raw ethernet packets, but = I'm >>> experincing occasionally weird behaviour. >>> >>> Versions of things: >>> >>> linux-2.6.34.5 >>> xenomai-2.5.5.2 >>> rtnet-39f7fcf >>> >>> The testprogram runs on two computers with "Intel Corporation >>> 82557/8/9/0/1 Ethernet Pro 100 (rev 08)" controller, where one comput= er >>> acts as a mirror sending back packets received from the ethernet (onl= y >>> those two computers on the network), and the other sends packets and >>> measures roundtrip time. Most packets comes back in approximately 100= >>> us, but occasionally the reception times out (once in about 100000 >>> packets or more), but the packets gets immediately received when >>> reception is retried, which might indicate a race between rt_dev_recv= msg >>> and interrupt, but I might miss something obvious. >> >> Changing one of the ethernet cards to a "Intel Corporation 82541PI=20 >> Gigabit Ethernet Controller (rev 05)", while keeping everything else=20 >> constant, changes behavior somewhat; after receiving a few 100000=20 >> packets, reception stops entirely (-EAGAIN is returned), while=20 >> transmission proceeds as it should (and mirror returns packets). >> >> Any suggestions on what to try? >=20 > Since the problem disappears with 'maxcpus=3D1', I suspect I have a SMP= =20 > issue (machine is a Core2 Quad), so I'll move to xenomai-core. > (original message can be found at=20 > http://sourceforge.net/mailarchive/message.php?msg_name=3D4CC82C8D.3080= 808%40control.lth.se=20 > ) >=20 > Xenomai-core gurus: which is the corrrect way to debug SMP issues? > Can I run I-pipe-tracer and expect to be able save at least 150 us of=20 > traces for all cpus? Any hints/suggestions/insigths are welcome... The i-pipe tracer unfortunately only saves traces for a the CPU that triggered the freeze. To have a full pictures, you may want to try my ftrace port I posted recently for 2.6.35. Jan --------------enig5FBD4A17A118816B2D8B7510 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkzJKQIACgkQitSsb3rl5xQb4wCg2VZ+jtq7yBBV2pNZ1ax6ydNZ J9MAnj4eUUrGFe2Kj5QGydFQprW5pii4 =gxwz -----END PGP SIGNATURE----- --------------enig5FBD4A17A118816B2D8B7510--