Andrew Morton a écrit :
> Brice Goglin <[email protected]> wrote:
>
>>I was seeing a lockup with several -mm releases since 2.6.12-rc2-mm1
>>(IIRC). With 2.6.12-rc2-mm1, I remember getting the lockup a few minutes
>>after boot time.
>>With 2.6.12-rc3-mm1, I waited several days before getting it.
>>But, I finally caught this one with netconsole. So here it is:
>>
>>BUG: soft lockup detected on CPU#0!
>>Pid: 0, comm: swapper
>>EIP: 0060:[<c02d40a5>] CPU: 0
>>EIP is at _spin_unlock_irqrestore+0x5/0x30
>> EFLAGS: 00000286 Not tainted (2.6.12-rc3-mm1=Pignouf)
>>EAX: c18e8160 EBX: c18e8160 ECX: 00000001 EDX: 00000286
>>ESI: c18e0160 EDI: dbf96c64 EBP: ffffffff DS: 007b ES: 007b
>>CR0: 8005003b CR2: b6e43000 CR3: 0e912000 CR4: 00000690
>> [<c012a635>] __mod_timer+0xc5/0xf0
>
>
> It could be the timer bug. Can you try it with Oleg's fix?
Ok, thanks.
I applied it on top of mm2 and started praying for a few days
until something happens or not.
Brice
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
