[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:
>
> > This is what I got. The system is still in that state, so let me know if
> > you want me to try anything else (or any other SysReq commands):
>
> Can you hit SysRq-P a few more times to see where it's looping?

Ok, I did ( about 20 times). It always prints the same IP?

>>>>
SysRq: Show Regs

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>]

SysRq: Show Regs

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>]

SysRq: Show Regs

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>]

SysRq: Show Regs

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>]


SysRq: Show Regs

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>]
SysRq: Show Regs

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>]

SysRq: Show Regs

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>]

SysRq: Show Regs

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>]

SysRq: Show Regs

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>]
....
....
....




I'm not quite sure what this means (i.e. how Sysreq-p works). This seems to
imply that the processor is halted at this location. Or it could mean that
the EIP printed is from the code printing this stuff, which would always be
from the
same location of course (but this would be practically usless info, as it
does
not tell you anything). Do you know? Does SysReq-p print the current
*actual*execution of the code that the time the key was received?
I'm doing this through a serial console, not through a keyboard.

It could also mean, of course that I was highly unlucky and managed to get
the
same EIP in about 20 different tests even though the processor is in a pretty
tight loop.


>
>
> > 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>]
>
> And can you look up c0107193, c01071f5, c0105000 and c0100192 in your
> System.map? Preferably down to the exact line of code if they're in JFFS2
> (gdb and gcc -g are your friends)

>
>
> In fact, could you convert the whole of the SysRq-T output to symbols too?
> Passing it through ksymoops ought to be able to do that for you, if given
> the correct System.map file.

Ok, I'll try to do that.

Vipin


To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo@xxxxxxx.com