Re: Kernel traces coming back with trash/clutter

[John Anthony Kazos Jr.]

> > > 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
> > 
> > Perhaps you have something looping that's outputting KERN_DEBUG with a
> > null message? Or one of your diagnostic printk statements includes
> > KERN_DEBUG with no actual message?
> > 
> No, they are all KERN_DEBUG<space>"some string here", almost all with
> some formatted output as well.  Could I be overloading the printk
> output buffer, as in possibly too tightly repeated/looped code to be
> able to output it all?

It is possible, I suppose. Is what you're working on open-source? If so, 
you could send it to me and I could try and reproduce it here and track it 
down. If you want me to, that is. (If you do send, please include a 
".config".)

Otherwise, I couldn't tell you what it might be. Make sure all your 
messages end with '\n', make sure you're not accidentally using the wrong 
formatting codes and it's backing over previous output with ^H or 
something. You could confirm or rule out the possibility of overflowing 
the printk buffers by writing a dummy module with a tight loop of nothing 
but printk statements with counters to see if you can get it to asplode.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/