Re: 2.6.20 BUG: soft lockup detected on CPU#0!

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ingo Molnar
Date: Thursday, February 8, 2007 - 1:06 am

* Andrew Morton <akpm@linux-foundation.org> wrote:


hm, not so the latest & lamest in my experience. The commit that made it 
quite robust was 6687a97d4041f996f725902d2990e5de6ef5cbe5, as of March 
2006, and first showed up in 2.6.17. (OTOH, since the merge of lockdep 
the main source of soft lockups in the field has been quite severely 
reduced. Nevertheless it's still good to have it around, occasionally 
there happen other types of soft lockups too, in open-coded loops, etc.)

	Ingo
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
2.6.20 BUG: soft lockup detected on CPU#0!, Lukasz Trabinski, (Wed Feb 7, 4:02 pm)
Re: 2.6.20 BUG: soft lockup detected on CPU#0!, Andrew Morton, (Wed Feb 7, 9:47 pm)
Re: 2.6.20 BUG: soft lockup detected on CPU#0!, Ingo Molnar, (Thu Feb 8, 1:06 am)
Re: 2.6.20 BUG: soft lockup detected on CPU#0!, Andrew Morton, (Thu Feb 8, 1:15 am)
Re: 2.6.20 BUG: soft lockup detected on CPU#0!, Eric Dumazet, (Thu Feb 8, 2:16 am)
Re: 2.6.20 BUG: soft lockup detected on CPU#0!, Ingo Molnar, (Thu Feb 8, 2:56 am)
Re: 2.6.20 BUG: soft lockup detected on CPU#0!, Andrew Morton, (Thu Feb 8, 3:12 am)
Re: 2.6.20 BUG: soft lockup detected on CPU#0!, Lukasz Trabinski, (Thu Feb 8, 8:51 am)