>Yes, exclusively.
> I am getting this odd content in the trace log (dmesg), and I cannot
> figure out what it is or why it is there.
>
> <7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7>
> <7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7>
> <7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7>
> <7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7><7>
> <7><7><7><7><7>__bio_add_page: 2x ph 88>=128 || hw 88>=88 || 360448>max
> ffffffff802525d8 generic_make_request(bio 000001017c745300) 50729472, 704
"<7>" is KERN_DEBUG in <include/linux/kernel.h>, used with printk. Are you
using printk in the following forms?
printk(KERN_DEBUG "A debug message.\n");
Perhaps you have something looping that's outputting KERN_DEBUG with aNo, they are all KERN_DEBUG<space>"some string here", almost all with
null message? Or one of your diagnostic printk statements includes
KERN_DEBUG with no actual message?
Remember, if you have a string in a variable without a KERN_*Haven't tried that one - they're all of the form above.
prependation, you can do this.
printk(KERN_DEBUG "%s\n", debug_message);