On Fri, Jul 31, 2009 at 8:28 AM, Meelis Roos <mroos@xxxxxxxx> wrote: > > > Please see http://www.parisc-linux.org/faq/kernelbug-howto.html > > Well, I can not find anything about interpreting SER PIM data there? Are you sure? There are basic explanations about the info we need. For instance: "- The r02 register is the "return pointer" - it indicates the calling function - The IAOQ contents specify the address of the instruction where the fault occured." Of course they are undecoded, that's why you need to be able to objdump the kernel. > My system is 2-CPU L1000, that I forgot to re-mention as I reported to > my old report that anyone but me had probably forgotten. Using GSP. > ALso, I rebooted the hanging computer using 'RS' from GSP, not 'TC' - > does that garble PIM data? After HPMC, RS is ok. Remember to always ser clearpim after collecting the info. > > Anyway, from the output below, I suspect maybe we have some kernel functions > > that are not in the right section, since the error happens right after > > "Freeing unused kernel memory"? > > No, the real problem is below, this badness on SMP I was told to ignore > here on this list in spring. The real problem happens after tuli driver > loading and PCI configuration of the cards. From these, I only have the > SER PIM data, no kernel backtrace. PIM will contain relevant (though undecoded) information, so that's already good to have. HTH -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
