From: Lee Revell <rlrevell@joe-job.com>
To: george@mvista.com
Cc: Andrew Morton <akpm@osdl.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: spin_lock error in arch/i386/kernel/time.c on APM resume
Date: Sat, 12 Mar 2005 16:18:31 -0500 [thread overview]
Message-ID: <1110662312.7723.16.camel@mindpipe> (raw)
In-Reply-To: <4233111A.5070807@mvista.com>
On Sat, 2005-03-12 at 07:56 -0800, George Anzinger wrote:
> J. Bruce Fields wrote:
> > On APM resume this morning on my Thinkpad X31, I got a "spin_lock is
> > already locked" error; see below. This doesn't happen on every resume,
> > though it's happened before. The kernel is 2.6.11 plus a bunch of
> > (hopefully unrelated...) NFS patches.
> >
> > Any ideas?
> >
> Yesterday's night mare, todays bug :(
>
Wait, so this is the same theoretical bug you discussed in the
do_timer_interrupt thread?
Wow, a real schroedinbug...
Lee
prev parent reply other threads:[~2005-03-12 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 13:11 spin_lock error in arch/i386/kernel/time.c on APM resume J. Bruce Fields
2005-03-12 15:21 ` [PATCH] APM: fix interrupts enabled in device_power_up Zwane Mwaikambo
2005-03-15 22:33 ` J. Bruce Fields
2005-03-15 22:40 ` Zwane Mwaikambo
2005-03-12 15:56 ` spin_lock error in arch/i386/kernel/time.c on APM resume George Anzinger
2005-03-12 16:25 ` Zwane Mwaikambo
2005-03-12 16:36 ` Venkatesh Pallipadi
2005-03-12 16:46 ` Zwane Mwaikambo
2005-03-12 17:45 ` Venkatesh Pallipadi
2005-03-12 18:04 ` George Anzinger
2005-03-12 19:58 ` Zwane Mwaikambo
2005-03-12 20:25 ` George Anzinger
2005-03-13 18:35 ` Pavel Machek
2005-03-14 23:49 ` George Anzinger
2005-03-15 0:08 ` Pavel Machek
2005-03-15 9:04 ` George Anzinger
2005-03-12 21:14 ` Barry K. Nathan
2005-03-12 21:18 ` Lee Revell [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=1110662312.7723.16.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=bfields@fieldses.org \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.