On Tue, 30 Jul 2002, yaelgilad wrote:
> The decoded oops shows a function trace which does not seem logical; e.g.
> function A calling function B where this is impossible in the code, as well
> as same function name appearing more than once. I have seen cases where,
> due to a memory glitch, the oops is wrong.
> Therefore, the only information I can trust is the sigbus message which I
> mentioned,
> which is outputted with printk.
> I know that's not a lot, but that's what I got :-(
Can you find out which instruction it is? it'd just require putting the
following;
sigbus:
printk(__FUNCTION__":insn=%d\n", insn.i_format.opcode);
die_if_kernel ("Unhandled kernel unaligned access", regs);
By looking at the code you could be trying to access a bad
pointer/address?
Cheers,
Zwane
DISCLAIMER: I know zip about MIPS
--
function.linuxpower.ca
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
