>Also, I'd like to respond to the person (sorry, I forgot your name!) who
Andrea ;-).
>suggested I used the print-eip patch:
>
>The print-eip patch won't help me. When my machines freak out the kernel
>usually stays partialli alive, scrolling Aiee or eth0 error messages
>constantly. Only rarely do they lock up completely. This would afaik make
>print-eip completely pointless..
If you don' t see the Oops you should try to press Alt-Gr+Sroll-Lock and
write down some EIP address. If this don' t work my patch can help a lot.
The Oops you postesd earlier are not useful. You must give us the resolved
addresses filtering the Oopses through ksymoops. I hope you will find some
docs if you don' t know how to do it yet ;-).
After all I don' t think that the Oopses/print-eip of 2.0.33 can help at
all since the bug probably (or at least I think so) is somewhere and
probably it corrput some mem area. Then some piece of code will use that
mem area and we will see the Oops as it was due the piece of code...
At first we must understand if the mem squezee that came out before the
hang is due to a bug or it can be a normal condition that only in 2.0.3?
_then_ cause a crash.
Andrea[s] Arcangeli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu