At 12:21 PM 6/20/2003 -0400, Robert Watson wrote:
>If you have a version of the kernel in question on disk and with debugging
>symbols, could you attach gdb -k to it and send us the results of:
>
> l *0xc01f6212
>
>That will provide a bit more information about where the panic is
>occuring. This
At 12:21 PM 6/20/2003 -0400, Robert Watson wrote:
>If you have a version of the kernel in question on disk and with debugging
>symbols, could you attach gdb -k to it and send us the results of:
>
> l *0xc01f6212
>
>That will provide a bit more information about where the panic is
>occuring. This
At 12:21 PM 6/20/2003 -0400, Robert Watson wrote:
>If you have a version of the kernel in question on disk and with debugging
>symbols, could you attach gdb -k to it and send us the results of:
>
> l *0xc01f6212
>
>That will provide a bit more information about where the panic is
>occuring. This
If you have a version of the kernel in question on disk and with debugging
symbols, could you attach gdb -k to it and send us the results of:
l *0xc01f6212
That will provide a bit more information about where the panic is
occuring. This is likely a NULL pointer dereference.
Robert N M Watson
