| |||||||||||||
How to ruin Linus's vacationHow to ruin Linus's vacationPosted Jul 19, 2011 22:13 UTC (Tue) by smoogen (subscriber, #97)Parent article: How to ruin Linus's vacation
I wonder if this is anything related to a set of "crashes" I have had with the 3.0.0 kernels (the 2.6.39 works fine so maybe not)
https://bugzilla.redhat.com/show_bug.cgi?id=722472
I noticed that at least in rc7 it came out with a new error message versus slowing down until the deadlock indicator starts spewing "hard-locks"
(Log in to post comments)
How to ruin Linus's vacation Posted Jul 28, 2011 17:12 UTC (Thu) by pebolle (guest, #35204) [Link]
No, it's not related. That bug has to do - as far as I can tell right now - with lockdep noticing there's recursive locking going on but not being told that this is a case of expected nested locking. Well, I think the nesting is expected ...
Anyhow, the message lockdep prints, includes the neat line:
It took me a few days before I noticed that the kernel actually still was running quite OK after that disturbing message.
By the way, the reason you ran into this recently seems to be that systemd-30 is (apparently) the first program in wide use that triggers this.
|
|||||||||||||