> > Therefore some other aspect of the change is causing problems and I > > think that aspect is the size of the new code. > > Actually, there is a way to prove that this is indeed the bug, Meelis > what does the entry for "swapper_tsb" say in your System.map file for > a failing kernel? > > If it is not "0000000000408000", then that shows the bug. It shows the bug in the newest kernel on my V240: System.map-4.0.0:0000000000408000 T swapper_tsb System.map-4.0.0-2-sparc64-smp:0000000000408000 T swapper_tsb System.map-4.1.0:0000000000408000 T swapper_tsb System.map-4.2.0:0000000000408000 T swapper_tsb System.map-4.3.0-00063-gea2d67b:0000000000408000 T swapper_tsb System.map-4.3.0-08824-g7c623ca:0000000000408000 T swapper_tsb System.map-4.4.0-rc8-00005-gee9a7d2:0000000000408000 T swapper_tsb System.map-4.5.0-rc3:0000000000408000 T swapper_tsb System.map-4.5.0-rc4-00037-g65c23c6:0000000000408000 T swapper_tsb System.map-4.6.0-rc4-00007-g95d0c42:0000000000408028 T swapper_tsb -- Meelis Roos (mroos@xxxxxxxx) -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
