Hi Olliver,
> Do you still have this with the 3.4.7* series? Yes. > Yes I have seen the same on 3.4.79+ too. At least head of commits is > '8ea347bcb4b4a5e50ec0343afac579e933ce8402'. Tried exactly this version with the same result. I think the problem started with the upstream merge of the new LZO code, which was in 3.4.67. I'm not 100% sure, but it may be related to the newly introduced unaligned data access feature. Could it be that the alignment checking is not disabled in the CPU at the time this code is run? -- Ruediger "Rudi" Ihle -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
