Messages in this thread | | | Date | Tue, 26 Jul 2022 15:37:31 +0100 | From | Sudeep Holla <> | Subject | Re: [-next] Lockdep warnings |
| |
On Tue, Jul 26, 2022 at 02:08:37PM +0100, Sudeep Holla wrote: > On Tue, Jul 26, 2022 at 01:50:06PM +0100, Mark Rutland wrote: > > On Tue, Jul 26, 2022 at 01:40:40PM +0100, Mark Rutland wrote: > > > [Adding Peter; I suspect this is due to the cpuidle rework] > > > > Looking again I see the cpuidle rework isn't in next, so evidently not... > > > > Yes, that is the first thing I checked and saw it wasn't in next. The first > splat I had see 2 weeks ago seem to suggest something around context_tracking > patches in the -next but I no longer see that. I haven't spent time digging > this, so thought better to post the splat on the list in the meantime. >
OK, I need to take back that the issue is only on -next. Just tested v5.19-rc8 and v5.18, both has the splat with lockdep on. It could be just that it has been a while since I booted a kernel with lockdep on.
-- Regards, Sudeep
| |