On Fri, 5 Nov 1999 13:27:01 +0100, Daniel Tryba
<muaddib@arrakis.stack.nl> said:
> I get this after a succesfull shutdown (the most annoying part is that
> the serialsysreq doesn't work anymore at this point :( Normal sysrequest
> on the machine itself still works):
...
> Please stand by while rebooting the system
> Unable to handle kernel paging request at virtual address 0000000000000001
> kjournald(6): Oops 0
...
> pc = [<fffffc000031fe08>] ra = [<fffffc000031fcf4>]
> Trace: [<fffffc0000329b7c>] [<fffffc0000310f14>] [<fffffc000031f07c>] [<fffffc00
0031f020> ] [<fffffc000031eac8>] [<fffffc00003207f8>] [<fffffc000031f07c>] [<ffff
fc000037e204> ] [<fffffc00003108c8>] [<fffffc000037e060>] [<fffffc000037e020>]
I really need those call trace addresses decoded from the System.map for
that kernel before I can do much with this report. See
"linux/Documentation/oops-tracing.txt"
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/