On 12/16/08, Ryusuke Konishi <[email protected]> wrote: > Debugging STR problem is usually hard. > I don't know the magic bullet for it. > > If you can change the screen to an active console using > Ctrl-Alt-F[1-7] (in case of Debian) during the lockup, you may > identify the process and function causing the problem:
Like I said, the laptop would completely lock up and not respond to any key press. > - In case not applying nilfs2 to the root directory. > - without X environment. > - without the cleaner daemon. (i.e. STRs after killing the cleanerd) > - without writable mount (i.e. STRs without remount r/w) > > Any ideas? If I recall correctly, every time when I had this was after the laptop had at least one resume from suspend-to-ram. Only in one occation it locked up immediately. Other times, it kept working for hours and I could suspend it and wake it up again without problem. So maybe I'll repeat this, and try out the conditions you mentioned. I'll post again when I have more info. Thanks! -- Regards, Paul Liu Yale Haskell Group http://www.haskell.org/yale _______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
