From: Andrew Morton <akpm@osdl.org>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: stern@rowland.harvard.edu, linux-kernel@vger.kernel.org,
torvalds@osdl.org, cpufreq@www.linux.org.uk
Subject: Re: Linux v2.6.18-rc3
Date: Tue, 1 Aug 2006 21:59:19 -0700 [thread overview]
Message-ID: <20060801215919.8596da9d.akpm@osdl.org> (raw)
In-Reply-To: <4807377b0608012131mf160bc3iff724910191b521@mail.gmail.com>
On Tue, 1 Aug 2006 21:31:22 -0700
"Jesse Brandeburg" <jesse.brandeburg@gmail.com> wrote:
> On 7/31/06, Alan Stern <stern@rowland.harvard.edu> wrote:
> > On Mon, 31 Jul 2006, Andrew Morton wrote:
> >
> > > core_initcall() would suit. That's actually a bit late for this sort of
> > > thing, but we can always add a new section later if it becomes a problem.
> > > I'd suggest that we ensure that srcu_notifier_chain_register() performs a
> > > reliable BUG() if it gets called too early.
> >
> > Here's a patch to test. I can't try it out on my machine because
> > 2.6.18-rc2-mm1 (even without the patch) crashes partway through a
> > suspend-to-disk, in a way that's extremely hard to debug. Some sort of
> > spinlock-related bug occurs within ioapic_write_entry.
>
> can't test because I also can't suspend or hibernate with rc2-mm1
> (resume causes hard hang with the backlight and screen off) The issue
> i reported was against linus' 2.6.18-rc3 kernel.
>
This might help?
author Jiri Slaby <ku@bellona.localdomain> Tue, 01 Aug 2006 01:16:13 +0159
--- a/arch/i386/kernel/io_apic.c
+++ b/arch/i386/kernel/io_apic.c
@@ -2360,6 +2360,7 @@ static int ioapic_resume(struct sys_devi
reg_00.bits.ID = mp_ioapics[dev->id].mpc_apicid;
io_apic_write(dev->id, 0, reg_00.raw);
}
+ spin_unlock_irqrestore(&ioapic_lock, flags);
for (i = 0; i < nr_ioapic_registers[dev->id]; i ++)
ioapic_write_entry(dev->id, i, entry[i]);
-
next prev parent reply other threads:[~2006-08-02 4:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0607292320490.4168@g5.osdl.org>
[not found] ` <4807377b0607302113i4e984ff6j1ebae5562148907c@mail.gmail.com>
2006-07-31 4:27 ` Linux v2.6.18-rc3 Andrew Morton
2006-07-31 14:54 ` Alan Stern
2006-07-31 15:11 ` Andrew Morton
2006-07-31 15:59 ` Alan Stern
2006-07-31 20:34 ` Alan Stern
2006-08-02 4:31 ` Jesse Brandeburg
2006-08-02 4:59 ` Andrew Morton [this message]
2006-08-02 19:57 ` Jesse Brandeburg
2006-08-02 20:16 ` Rafael J. Wysocki
2006-08-02 20:23 ` Russell King
2006-08-02 20:26 ` Rafael J. Wysocki
2006-08-02 20:32 ` Dave Jones
2006-08-02 20:58 ` Russell King
2006-08-02 21:01 ` Dave Jones
2006-08-02 21:18 ` Linus Torvalds
2006-08-02 21:38 ` Russell King
2006-08-02 22:04 ` Linus Torvalds
2006-08-02 22:05 ` Russell King
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=20060801215919.8596da9d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cpufreq@www.linux.org.uk \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@osdl.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