I cross-compile linux for a broadcom mips-based set-top box, and recently when I
upgraded the kernel version from 2.6.12 to 2.6.18, I noticed that executing
insmod or rmmod on a module that outputs a printk causes the serial console to
temporarily swallow a keypress.
For example, I telnet into a unit and type "insmod mymodule". On the target's
serial console, the mymodule_init_module() function does printk("Dave was
here\n");. After the insmod is done, if I make any single keypress on the
serial console, the key is not echoed. Upon making a second keypress, the first
two keys are echoed.
The problem did not exist with 2.6.12, and it does not occur when running insmod
or rmmod on a module that does not have any printk() calls.
Does anyone have advice where/how I could look for the cause of this annoying
behavior?
Thanks,
Dave
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
