From: "J. Bruce Fields" <bfields@fieldses.org>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] APM: fix interrupts enabled in device_power_up
Date: Tue, 15 Mar 2005 17:33:39 -0500 [thread overview]
Message-ID: <20050315223339.GF11916@fieldses.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0503120806001.17127@montezuma.fsmlabs.com>
On Sat, Mar 12, 2005 at 08:21:29AM -0700, Zwane Mwaikambo wrote:
> On Sat, 12 Mar 2005, 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.
> >
> > Mar 12 07:07:31 puzzle kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64
> > Mar 12 07:07:31 puzzle kernel: arch/i386/kernel/time.c:179: spin_lock(arch/i386/kernel/time.c:c0603c28) already locked by arch/i386/kernel/time.c/309
> > Mar 12 07:07:31 puzzle kernel: arch/i386/kernel/time.c:316: spin_unlock(arch/i386/kernel/time.c:c0603c28) not locked
>
> APM was calling device_power_down and device_power_up with interrupts
> enabled, resulting in a few calls to get_cmos_time being done with
> interrupts enabled (rtc_lock needs to be acquired with interrupts
> disabled).
Thanks, I haven't been following the discussion carefully, but for
what's it worth I did apply that patch and now (a few suspend-resume
cycles later) haven't seen the spin_lock warning or seen any other ill
effects.
Let me know if there's any testing it would be useful for me to do.
--Bruce Fields
> Signed-off-by: Zwane Mwaikambo <zwane@arm.linux.org.uk>
>
> ===== arch/i386/kernel/apm.c 1.72 vs edited =====
> --- 1.72/arch/i386/kernel/apm.c 2005-01-20 22:02:11 -07:00
> +++ edited/arch/i386/kernel/apm.c 2005-03-12 08:17:52 -07:00
> @@ -1202,10 +1202,11 @@
> }
>
> device_suspend(PMSG_SUSPEND);
> + local_irq_disable();
> device_power_down(PMSG_SUSPEND);
>
> /* serialize with the timer interrupt */
> - write_seqlock_irq(&xtime_lock);
> + write_seqlock(&xtime_lock);
>
> /* protect against access to timer chip registers */
> spin_lock(&i8253_lock);
> @@ -1216,20 +1217,22 @@
> * We'll undo any timer changes due to interrupts below.
> */
> spin_unlock(&i8253_lock);
> - write_sequnlock_irq(&xtime_lock);
> + write_sequnlock(&xtime_lock);
> + local_irq_enable();
>
> save_processor_state();
> err = set_system_power_state(APM_STATE_SUSPEND);
> restore_processor_state();
>
> - write_seqlock_irq(&xtime_lock);
> + local_irq_disable();
> + write_seqlock(&xtime_lock);
> spin_lock(&i8253_lock);
> reinit_timer();
> set_time();
> ignore_normal_resume = 1;
>
> spin_unlock(&i8253_lock);
> - write_sequnlock_irq(&xtime_lock);
> + write_sequnlock(&xtime_lock);
>
> if (err == APM_NO_ERROR)
> err = APM_SUCCESS;
> @@ -1237,6 +1240,7 @@
> apm_error("suspend", err);
> err = (err == APM_SUCCESS) ? 0 : -EIO;
> device_power_up();
> + local_irq_enable();
> device_resume();
> pm_send_all(PM_RESUME, (void *)0);
> queue_event(APM_NORMAL_RESUME, NULL);
> @@ -1255,17 +1259,22 @@
> {
> int err;
>
> + local_irq_disable();
> device_power_down(PMSG_SUSPEND);
> /* serialize with the timer interrupt */
> - write_seqlock_irq(&xtime_lock);
> + write_seqlock(&xtime_lock);
> /* If needed, notify drivers here */
> get_time_diff();
> - write_sequnlock_irq(&xtime_lock);
> + write_sequnlock(&xtime_lock);
> + local_irq_enable();
>
> err = set_system_power_state(APM_STATE_STANDBY);
> if ((err != APM_SUCCESS) && (err != APM_NO_ERROR))
> apm_error("standby", err);
> +
> + local_irq_disable();
> device_power_up();
> + local_irq_enable();
> }
>
> static apm_event_t get_event(void)
next prev parent reply other threads:[~2005-03-15 22:36 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 [this message]
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
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=20050315223339.GF11916@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=zwane@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®