It only means that an alignment constraint is not met, therefore the kernel catches the unaligned access and performs manually the fetch to overcome the alignment constraint. It is slower as 1 unaligned read requires 2 aligned reads, but it is acceptable as the kernel knows how to do it (it is a feature).

It is logged because on sparc architecture memory access alignement constraints should have been respected therefore it is unusual for the kernel to catch such accesses.