aboutsummaryrefslogtreecommitdiffstats
path: root/arch/powerpc/mm/hugetlbpage.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2008-12-12 09:19:50 +0000
committerPaul Mackerras <paulus@samba.org>2008-12-16 13:48:18 +1100
commit23e0e8afafd9ac065d81506524adf3339584044b (patch)
tree2bbc2c95e49687be2f499096ccc7c94ddecb823b /arch/powerpc/mm/hugetlbpage.c
parenta4c74ddd5ea3db53fc73d29c222b22656a7d05be (diff)
downloadkernel_samsung_smdk4412-23e0e8afafd9ac065d81506524adf3339584044b.tar.gz
kernel_samsung_smdk4412-23e0e8afafd9ac065d81506524adf3339584044b.tar.bz2
kernel_samsung_smdk4412-23e0e8afafd9ac065d81506524adf3339584044b.zip
powerpc/cell/axon-msi: Fix MSI after kexec
Commit d015fe995 'powerpc/cell/axon-msi: Retry on missing interrupt' has turned a rare failure to kexec on QS22 into a reproducible error, which we have now analysed. The problem is that after a kexec, the MSIC hardware still points into the middle of the old ring buffer. We set up the ring buffer during reboot, but not the offset into it. On older kernels, this would cause a storm of thousands of spurious interrupts after a kexec, which would most of the time get dropped silently. With the new code, we time out on each interrupt, waiting for it to become valid. If more interrupts come in that we time out on, this goes on indefinitely, which eventually leads to a hard crash. The solution in this commit is to read the current offset from the MSIC when reinitializing it. This now works correctly, as expected. Reported-by: Dirk Herrendoerfer <d.herrendoerfer@de.ibm.com> Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Michael Ellerman <michael@ellerman.id.au> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'arch/powerpc/mm/hugetlbpage.c')
0 files changed, 0 insertions, 0 deletions