Messages in this thread | | | Subject | Re: printk in init_module mixing with printf in insmod | Date | Fri, 19 Apr 2002 23:24:51 +0100 (BST) | From | Alan Cox <> |
| |
> printk("Hello, world\n"); > in the module are intermixed unpleasantly, yielding output like > Warning: loHello,ading foo.o world > will taint kernel > > This garbled output makes reading the debugging printk's difficult. > > I suppose this isn't terribly important, since printk's are > kind of a no-no in production, and this only affects printk's > in init_module, but it'd be nice to know what > the cleanest way to get rid of the mixing is. Adding a sleep > inside insmod seems heavyhanded. I suppose I could redirect > insmod's output to a file, sleep a bit, and then display the > file... bleah.
Probably you want to fprintf the message after the module initialise has reported completion, instead of before. I see no good way of hiding it the other way around. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |