[2.764009 (3/3)]
[4.272241 (2/2)]
[4.272322 (2/2)]
[4.272375 (2/2)]
[2.948002 (3/3)]
As you can see, I added printk_cpu and smp_processor_id() to the
printk timestamp output and thus it is obvious that the different
times come from different CPUs.
the
Hi,
Not sure whether the lockdep patches or something else is causing this
as I haven't checked w/o the patches yet, but I seem to be having some
confusion of printk timestamps:
Tried reverting the patches ?
That didn't help, so it's not the lockdep patches causing it. I'm still
seeing
* Johannes Berg [EMAIL PROTECTED] wrote:
Hi,
Not sure whether the lockdep patches or something else is causing this
as I haven't checked w/o the patches yet, but I seem to be having some
confusion of printk timestamps:
Tried reverting the patches ?
That didn't help, so it's
