From: William Lee Irwin III <wli@holomorphy.com>
To: Ingo Molnar <mingo@elte.hu>, Russell King <rmk@arm.linux.org.uk>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [patch] Re: Serial Oopsen caused by global IRQ chanes
Date: Sat, 27 Jul 2002 16:01:50 -0700 [thread overview]
Message-ID: <20020727230150.GP25038@holomorphy.com> (raw)
In-Reply-To: <20020727223617.GO25038@holomorphy.com>
On Sat, Jul 27, 2002 at 08:43:04PM +0200, Ingo Molnar wrote:
>> the attached patch fixes a synchronize_irq() bug: if the interrupt is
>> freed while an IRQ handler is running (irq state is IRQ_INPROGRESS) then
On Sat, Jul 27, 2002 at 03:36:17PM -0700, William Lee Irwin III wrote:
> I'm having trouble with this one, I seem to get lots of these messages:
> pu: 12, clocks: 99983, slice: 3029
> CPU12<T0:99968,T1:60576,D:15,S:3029,C:99983>
> CPU 12 IS NOW UP!
Sorry, this is the hotplug stuff which surprised me, but is unrelated
to any deadlock (unless it's printk'ing at a bad time, which I doubt).
Thought it was an arch complaint about trying to wake already-woken cpus.
On Sat, Jul 27, 2002 at 03:36:17PM -0700, William Lee Irwin III wrote:
> ... and then the kernel deadlocks after free_initmem()'s printk().
Seems to be timing related, printk's in init/main.c made it go away.
ISTR hearing something about hotplug merge troubles, I'll investigate
that thread and report results with the fixes posted there.
Cheers,
Bill
next prev parent reply other threads:[~2002-07-27 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 18:11 Serial Oopsen caused by global IRQ chanes Russell King
2002-07-27 18:19 ` Russell King
2002-07-27 18:21 ` Ingo Molnar
2002-07-27 18:43 ` [patch] " Ingo Molnar
2002-07-27 22:36 ` William Lee Irwin III
2002-07-27 23:01 ` William Lee Irwin III [this message]
2002-07-27 23:27 ` William Lee Irwin III
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=20020727230150.GP25038@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@transmeta.com \
/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