On Wed, May 12, 1999 at 06:41:15PM +0200, Gianmarco Giovannelli
wrote:
> Ok... it's a bit long ... (Tell me there isn't a command to write the trace
> output on a disk :-)
>
> After the panic make by "screen" ...
> >trace
> Stopped at ttyflush+0x48: movl 0x14(%eax), %eax
[chop]
> A nightmare
On Wednesday, 12 May 1999 at 18:41:15 +0200, Gianmarco Giovannelli wrote:
> At 12/05/99, you wrote:
>>
>> At least put DDB in your kernel, type "trace" when it
>> panics and tell us what it says.
>
> Ok... it's a bit long ... (Tell me there isn't a command to write the trace
> output on a disk :-)
> Pardon, but I am not be able to figure by myself what you asked to me...
> If you can explain me step by step in a newbie way I can do everything ...
> The crashes is easily reproducible...
No offense, but are you sure you should even be running -current? A
certain amount of skill in doing such
At 12/05/99, you wrote:
>Ok, what I'd like you to do is, run this command,
> nm -n /kernel | more
>the output is the list of symbols in the kernel sorted by their addresses
>(the left-most column), page through the output, find symbols around the
>address 0xc0155ca4, and send me those symbol
At 12/05/99, you wrote:
>
>At least put DDB in your kernel, type "trace" when it
>panics and tell us what it says.
Ok... it's a bit long ... (Tell me there isn't a command to write the trace
output on a disk :-)
After the panic make by "screen" ...
>trace
Stopped at ttyflush+0x48: movl 0x14(%eax)
ingle user
login!
Geoff.
> -Original Message-
> From: Poul-Henning Kamp [mailto:p...@critter.freebsd.dk]
> Sent: 12 May 1999 05:56
> To: Geoff Rehmet
> Cc: lu...@watermarkgroup.com; curr...@freebsd.org
> Subject: Re: panic ! panic ! panic !
>
>
>
> At l
At least put DDB in your kernel, type "trace" when it
panics and tell us what it says.
In message <19990512154854.78032.qm...@rucus.ru.ac.za>, "Geoff Rehmet" writes:
>Luoqi Chen writes :
>
>I'm trying to get a crash dump myself, but the kernel I have
>right now, is screwing up my keyboard, and I
Luoqi Chen writes :
I'm trying to get a crash dump myself, but the kernel I have
right now, is screwing up my keyboard, and I cannot even log
in!
I will try again.
Geoff.
> > After make world this morning I received this panic :
> >
> > Fatal trap 12: page fault while in kernel mode
> > fault vi
At 12/05/99, you wrote:
>>
>Could you show us the symbols around the faulting instruction at 0xc0155ca4?
>It would be even better if you have a crash dump and the gdb backtrace.
Pardon, but I am not be able to figure by myself what you asked to me...
If you can explain me step by step in a newbi
> After make world this morning I received this panic :
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x14
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc0155ca4
> stack pointer = 0x10:0xc6864d64
> frame pointer = 0x10:0xc6864d78
> co
10 matches
Mail list logo
