Hmm.. All I get is those two lines until I do the SysRq.
Here goes:
woah.. too much I couldn't read it this time :(
I did "alt-SysRq-s" and it just flooded the screen with code trace..
the Last line is :
Code: 8b 06 83 f8 01 75 09 83 fd 11 0f 85 37 01 00 00 85 c0 75 1e
Aiee, killing interrupt handler.
----
At which point it is solid.
I'll switch to doing this in ramdisk to avoid the fsck.
Damn, I never put ramdisk into that kernel. Big mistake.
I'll do it for 2.1.115 .. should be the same bug.
[ time ]
Hmm..
Same two lines and thats it.. now doing 2.1.115 :
However.. on reading sysrq.txt I havenow done a "alt-sysrq-p"
and got this:
EIP: 0010:[<c0116114>] EFLAGS: 00000246
EAX: 00000000 EBX: c0e96a00 ECX: c0ee4000 EDX: 00000001
ESI: 00000020 EDI: c0e90351 EBP: c0e90340 DS: 0018 ES: 0018
CR0: 80050033 CR2: 0804a330 CR3: 00101000
further invocations give the same value..
so...
system.map
well.. that told me a lot :(
c0116030 T panic
c0116130 T sys_syslog
I kind of knew that :(
Ok here goes with the "alt-sysrq-s"
SysRq: Emergency Sync
Nothing else.. :(
repeat invocations -- same thing.
Oh wait.. this is ramdisk.. duhhhhhhh.
heh
Hmm... alt-sysrq-t
shows a mount process at the end of the list :
mount 12 D c0106000 0 36 29
sig: 0 0000000000000000 00000000fffbfeff : X
c0106000 T init_task_union
c0106000 T this_must_match_init_task
Great.
Well.., I'm learning things.. but I don't think I am getting anywhere.
What can I say.. its the cd. :)
Peter
-- pjordan at blackwire.com 436-0829 Black Wire Media "The meaning of a value is determined by how it is used" : Ousterhout
- 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.altern.org/andrebalsa/doc/lkml-faq.html