public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Soft lockup with -mm
Date: Mon, 16 May 2005 14:34:28 +0200	[thread overview]
Message-ID: <42889354.7030904@ens-lyon.org> (raw)
In-Reply-To: <427935DF.5010505@ens-lyon.org>

Brice Goglin a écrit :
> Andrew Morton a écrit :
> 
>>Brice Goglin <Brice.Goglin@ens-lyon.org> 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.

Hi Andrew,

This box is running 2.6.12-rc3-mm2 with Oleg's fix for 12 days.
Looks like the soft-lockup I was seeing is fixed.
I'll try to keep this box running -mm kernels to be sure the lockup
won't occur anymore.

Thanks,
Brice

      reply	other threads:[~2005-05-16 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 20:08 Soft lockup with -mm Brice Goglin
2005-05-04 20:23 ` Andrew Morton
2005-05-04 20:51   ` Brice Goglin
2005-05-16 12:34     ` Brice Goglin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42889354.7030904@ens-lyon.org \
    --to=brice.goglin@ens-lyon.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox