Running this on my alpha gives (gcc 4.0.2):
3000
0123456A01234567
Andrew Morton wrote:
Because networking does read/write short fields in various packet
header structures. Results are illustrated in a following example:
char foo[] __attribute__((aligned(8))) = 0123456701234567;
int
[EMAIL PROTECTED] wrote:
And the output in the kernel ring buffer is:
dmesg | grep xmit
ei_start_xmit(): skb-data unaligned fc0019be55d5 align to
fc001ef37620
length 60
Very weird. The length seems to indicate that this packet went through
skb_padto. However, I can't see how
On Sun, Apr 23, 2006 at 03:43:22PM +1000, Herbert Xu wrote:
Can you please put some printks in to find out if
1) skb_padto is being called.
2) Is the input to skb_padto aligned?
I'd also help if you could print out the contents of the packet itself.
--
Visit Openswan at
Looks like PIO at unaligned addresses doesn't work on alpha...
Begin forwarded message:
Date: Fri, 21 Apr 2006 02:35:45 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bug 6421] New: kernel 2.6.10-2.6.16 on alpha: arch/alpha/kernel/io.c,
iowrite16_rep() BUG_ON((unsigned long)src
Ingo Oeser [EMAIL PROTECTED] wrote:
Stephen Hemminger wrote:
Looks like PIO at unaligned addresses doesn't work on alpha...
Maybe this should be fixed similiar to ioread32_rep in
arch/alpha/kernel/io.c?
I think so, but Ivan thinks networking is bust:
Ivan Kokshaysky [EMAIL
