linux hangs with printk on schedule()
Quoted 3 lines
oops_in_progress++;
printk(...);
oops_in_progress--;
Thanks Robert and Andi for your help.
But the trick (avoid waking up klog by setting oops_in_progress) doesn't seem to work for me.
I did notice the code:
*********************************************
if (must_wake_klogd && !oops_in_progress)
wake_up_interruptible(&log_wait);
*****************************************
But it simply still doesn't work. :-(
I am working on implementing a new SMP scheduler. It's an OS research project. Without "printk" in the scheduler, it's really very hard to do the debugging. I don't know how other guys do in this case. Are you guys better equipped than me? I mean is debugging with gdb running on another machine (connected via serial port) a common technique? I am not sure whether it's necessary to set up an environment like that.
Haoqiang
I am working on implementing a new SMP scheduler. It's an OS research project. Without "printk" in the scheduler, it's really very hard to do the debugging. I don't know how other guys do in this case. Are you guys better equipped than me? I mean is debugging with gdb running on another machine (connected via serial port) a common technique? I am not sure whether it's necessary to set up an environment like that.
Depending on what your needs are, could you simply note or count events and do something about them later? I've a patch which inserts counters into schedule() (basically a very focused code coverage) so that you can determine later what decisions were taken (and how many times they were taken). If knowing the frequency at which a path was taken is more important than knowing specific values each time a path was hit, this patch might do it for you.
http://eaglet.rain.com/rick/linux/schedstat
If both the details and sequence is important, since this is debugging, you might try creating a, oh, 5000 member array, treated either as a circular buffer or a simple recording of the first 5000 events, in which you record your interesting event for later retrieval via (fancy) /proc or (more basic) your favorite debugger. I wouldn't advocate this for finished code, and be warned that too much intrusive debugging in a path like the scheduler can skew what you're hoping to observe. (printk's, for instance, can
be very slow compared to what's happening in the scheduler.)
Rick