On 4/24/07, John Anthony Kazos Jr. <[EMAIL PROTECTED]> wrote:
> > 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"some string here
> > > 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>
On 4/24/07, John Anthony Kazos Jr. <[EMAIL PROTECTED]> wrote:
>
> 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>
> I am experimenting with the kernel (CentOSv4.4 x86_64, 2.6.9-42.0.10)
> and I have added a number of traces in some relatively sensitive code
> in the page cache and some i/o functions.
>
> I am getting this odd content in the trace log (dmesg), and I cannot
> figure out what it is or why it is
I am experimenting with the kernel (CentOSv4.4 x86_64, 2.6.9-42.0.10)
and I have added a number of traces in some relatively sensitive code
in the page cache and some i/o functions.
I am getting this odd content in the trace log (dmesg), and I cannot
figure out what it is or why it is there.
429
5 matches
Mail list logo