Hi!
> > No no... syslog timestamps are unreliable at this point. downing cpus
> > take 704.5-704.4 seconds. You need to actually watch console to see
> > when it hangs, and I suspect it is not here.
> >
>
> OK. I'll try to print the messages to the console and watch it. I hope
> the screen doesn't turn off before the problem.
>
> I have two questions though:
>
> 1) Is it a good idea to add a long udelay (like 1s) after each printk so
> that the timestamps become more reliable?
I was suggesting delays so that you had enough time to see the messages.
> 2) Where do the messages printed by the pr_debug call go? I didn't find
> them in any log. Do I have to turn on some debugging facility in the
> kernel to see them?
Adjust your syslog config to see them in logs, they should still go to
the console. (But killing klogd may be good idea.)
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
