From: Andrew Morton <akpm@osdl.org>
To: Jason Stubbs <jstubbs@work-at.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Consistent lock up on >=2.6.8
Date: Mon, 4 Oct 2004 18:58:45 -0700 [thread overview]
Message-ID: <20041004185845.471bcc55.akpm@osdl.org> (raw)
In-Reply-To: <200410051053.09587.jstubbs@work-at.co.jp>
Jason Stubbs <jstubbs@work-at.co.jp> wrote:
>
> On Tuesday 05 October 2004 04:05, Andrew Morton wrote:
> > update_defense_level() is calling si_meminfo() from timer context. But
> > si_meminfo takes non-irq-safe locks.
> >
> > Move it all to keventd context.
>
> That appears to have fixed it. I'm running my regular test and, while
> interactivity is non-existent, it hasn't locked. I'll leave it going for
> another few hours and report back to confirm.
>
> Much gratitude. I should go out and buy a kernel book so that I may some day
> be able to repay the favour. :)
You reported the bug, then you applied and ran the debug patch and then you
sent back the info which was necessary to arrive at a fix and then you
tested the fix.
How could you possibly have anything further to "repay"?
next prev parent reply other threads:[~2004-10-05 2:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 7:11 PROBLEM: Consistent lock up on >=2.6.8 Jason Stubbs
2004-10-04 8:35 ` Andrew Morton
2004-10-04 10:31 ` Jason Stubbs
2004-10-04 19:05 ` Andrew Morton
2004-10-05 1:53 ` Jason Stubbs
2004-10-05 1:58 ` Andrew Morton [this message]
2004-10-05 4:17 ` Jason Stubbs
2004-10-29 15:08 ` RESEND: Consistent lock up 2.6.8-1.521 (and 2.6.8.1 w/ high-res-timers/skas/sysemu) Andrew A.
2004-10-29 15:22 ` Andrew A.
2004-10-29 15:23 ` Andrew A.
2004-10-05 2:03 ` PROBLEM: Consistent lock up on >=2.6.8 Roland Dreier
2004-10-05 3:51 ` Andrew Morton
2004-10-05 4:05 ` Roland Dreier
2004-11-25 1:03 ` Jason Stubbs
-- strict thread matches above, loose matches on Subject: below --
2004-12-06 8:30 Chris Caputo
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=20041004185845.471bcc55.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jstubbs@work-at.co.jp \
--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