Re: Kernel unaligned access : daily-build 20070221 / kernel 2.6.18-4 / sparc netra X1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Frans Pop wrote:
> On Thursday 22 February 2007 10:34, filib wrote:
>> Feb 21 13:55:25 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port
>> 67 interval 3
>> Feb 21 13:55:25 kernel: Kernel unaligned access at TPC[5e44c8]
>> ip_rcv+0xd0/0x58c
>> Feb 21 13:55:25 kernel: Kernel unaligned access at TPC[518044]
>> ip_fast_csum+0xc/0x80
>> Feb 21 13:55:25 kernel: Kernel unaligned access at TPC[518048]
>> ip_fast_csum+0x10/0x80
>> Feb 21 13:55:25 kernel: Kernel unaligned access at TPC[51804c]
>> ip_fast_csum+0x14/0x80
>> Feb 21 13:55:25 kernel: Kernel unaligned access at TPC[518054]
>> ip_fast_csum+0x1c/0x80
>> Feb 21 13:55:25 dhclient: DHCPOFFER from 10.1.1.1
>> Feb 21 13:55:27 dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port
>> 67
>
> As far as we know these messages are harmless (the most serious effect
> being that they may flood your log files). The issue is known, but it
> will not be fixed before the release.
>
> I also don't see any actual error here: you do receive the DHCP offer, so
> it looks like the network is working correctly.
Not sure what is the case with the Linux kernel, but I know from
past experience with other kernels that having misaligned code have
consequences ranging from:
* slower code (usually half of a quarter of the regular speed)
* weird side effects like some read/write operations fail or fail
partially
* undetermined behaviour
* no ill effects
This heavily depends on the kernel and the hardware.
- --
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF3aeLY8Chqv3NRNoRAlb9AKCzOZyc3cMhbip5T32uwgeX65ekTwCcCNGF
+ao5K7LS4zM1BT23NP2AkbE=
=VQzj
-----END PGP SIGNATURE-----
Reply to: