[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: JFFS2 stuck again.
David Woodhouse wrote:
> On Tue, 10 Apr 2001, Vipin Malik wrote:
> > Ok, I did ( about 20 times). It always prints the same IP?
> Good. So it's in a tight loop. The SysRq-P function is supposed to ensure
> that it doesn't actually print addresses in the keyboard handler - I
> assume that also works for serial SysRq. Even so - there'd be useful
> information in the backtrace.
> What function contains c0107193?
Ok, a little more info:
The call trace (the last line) of:
EIP: 0010:[<c0107193>] CPU: 0 EFLAGS: 00000246
EAX: 00000000 EBX: c0107170 ECX: c116a260 EDX: c025e000
ESI: c025e000 EDI: c025e000 EBP: 0008e000 DS: 0018 ES: 0018
CR0: 8005003b CR2: 4000101c CR3: 03fb8000 CR4: 00080010
Call Trace: [<c01071f5>] [<c0105000>] [<c0100192>]
from System.map yields...
[<c01071f5>] -> inside the function "cpu_idle()"
[<c0105000>] -> The function call "empty_bad_page()"
[<c0100192>] -> The label "L6" in arch/i386/kernel/head.S, which ,makes no
sense as that portion of the
jmp L6 # main should never return here, but
# just in case, we know what happens.
The EIP should be at this location then. How did it get to c0107193, which
is inside the function "default_idle()"?!!!
Aargh!!! What's going on??
To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to firstname.lastname@example.org