From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Cc: axp-hardware@talisman.alphalinux.org
Subject: Alpha: bad unaligned access handling
Date: Wed, 14 Feb 2001 15:48:09 +0100 [thread overview]
Message-ID: <20010214154808.A15974@lug-owl.de> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1882 bytes --]
Hi!
With my currently installed ping (netkit-ping 0.10-6 from Debian Woody)
I get unaligned accesses:
ping(15953): unaligned trap at 00000001200030e4: 0000000120026b34 29 1
ping(15953): unaligned trap at 0000000120003110: 0000000120026b2c 29 2
The worse part is: they seem to be handled The Wrong Way:
[jbglaw@air:/home/jbglaw] $> ping -c 1 localhost
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=13.8 ms
wrong data byte #8 should be 0x8 but was 0xdc
c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b
2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
--- localhost ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 13.8/13.8/13.8 ms
This is on a NoName Alpha box, running 2.4.0-test8-pre1 (with very good
uptimes), but I think 2.4.2-pre2 would do the same (wrong) things as
arch/alpha/kernel/traps.c wasn't really changed since ages... I don't
know much about alpha assemlbly language so somebody else should have
a look at that;( Btw., when such an unaligned trap has happened, I also
get transmit timeouts on my network card (which is:
00:0c.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, tx_status 00 status e000.
Flags; bus-master 1, full 1; dirty 1470429(13) current 1470445(13).
Transmit list 477a42d0 vs. fffffc00077a42d0.
0: @fffffc00077a4200 length 80000042 status 00000042
...
MfG, JBG
--
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
"insmod vi.o and there we go..." (Alexander Viro on linux-kernel)
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next reply other threads:[~2001-02-14 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 14:48 Jan-Benedict Glaw [this message]
2001-02-14 17:11 ` Alpha: bad unaligned access handling Carlos Carvalho
2001-02-14 17:26 ` Sean Hunter
2001-02-14 17:38 ` Carlos Carvalho
2001-02-14 17:46 ` Sean Hunter
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=20010214154808.A15974@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=axp-hardware@talisman.alphalinux.org \
--cc=linux-kernel@vger.kernel.org \
/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