Quoting Ravi Kumar B S <[EMAIL PROTECTED]>:

> Dmitri wrote:

> >In worst case, presence of printk's moves the memory around, and you have
> >a stray pointer somewhere that reads or writes past the allocated
> >memory. With printks in place, this pointer happens to point to a safe
> >place; without them all fails.

> thanks. but the thing is that the cleaned up code works on another of my 
> machine. and is not working only in a particular machine. i see the 
> configuration as same in both the machines.

I doubt you have two *identical* computers. If you are accessing the wrong
memory then the content of that memory is important. But in any case, if
I were you, I would review the diffs between two sources first, and if I
can't see anything obvious I would put some of printk back to see what
happens (or to remove some from the other source).

Dmitri

-- 
"Whoa...I did a 'zcat /vmlinuz > /dev/audio' and I think I heard God..."
(mikecd on #Linux)

Attachment: msg04482/pgp00000.pgp
Description: PGP signature

Reply via email to