Re: inconsistent lock state in 2.6.29-rc6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Meelis Roos <mroos@xxxxxxxx>
Date: Wed, 22 Apr 2009 22:53:44 +0300 (EEST)

>> > This another problem from my 6-CPU E3000 - just got it while compiling 
>> > 2.6.29-rc7 but the compilation continues fine.
>> > 
>> > [  412.896568] =================================
>> > [  412.964373] [ INFO: inconsistent lock state ]
>> > [  413.016474] 2.6.29-rc6 #2
>> > [  413.047705] ---------------------------------
>> > [  413.099822] inconsistent {softirq-on-W} -> {in-softirq-W} usage.
>> > [  413.171717] cc1/2007 [HC0[0]:SC1[1]:HE0:SE0] takes:
>> > [  413.230048]  (call_function_lock){-+..}, at: [<000000000049003c>] generic_smp_call_function_interrupt+0x11c/0x1c0
>> > [  413.353010] {softirq-on-W} state was registered at:
>> 
>> Please try this patch:
> 
> It seems to work. When I got my E3000 hooked up to electricity again 
> four days ago, I compiled the latest git and found this patch already 
> included. It has seen some stress since, and a reboot into .30-rc3, aga 
> still seems to work fine. Thank you for taking care of it!

Thank you for testing.
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux