From: Jesse Barnes <jbarnes@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.5-rc1-mm2
Date: Tue, 30 Mar 2004 11:27:05 -0800 [thread overview]
Message-ID: <200403301127.05151.jbarnes@sgi.com> (raw)
In-Reply-To: <20040317201454.5b2e8a3c.akpm@osdl.org>
On Wednesday 17 March 2004 8:14 pm, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.5-rc1/2.6
>.5-rc1-mm2/
>
> - Dropped the early-x86-cpu-detection patches, as these appear to be the
> source of recent early-crash problems.
>
> - Several fixes against the new writeback code.
>
> - Several fixes against the new block unplugging code.
I just tracked down a hang I've been seeing in the 2.6.5-rcX-mm trees to this
release. The symptom is that the machine hangs sometime during init script
startup, usually at around the time swap space is enabled (using pretty stock
Red Hat scripts). Before I look into it any further, are there any patches
that I should look at dropping to see if the hang goes away?
The hang occurs all the way through 2.6.5-rc3-mm1, but Linus' 2.6.5-rc3
release works fine.
Thanks,
Jesse
next prev parent reply other threads:[~2004-03-30 19:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 4:14 2.6.5-rc1-mm2 Andrew Morton
2004-03-18 16:01 ` 2.6.5-rc1-mm2 John Cherry
2004-03-18 20:31 ` USB: gphoto2 hangs, device disconnection oddity (was Re: 2.6.5-rc1-mm2) Sean Neakums
2004-03-19 9:27 ` 2.6.5-rc1-mm2 Marc-Christian Petersen
2004-03-30 19:27 ` Jesse Barnes [this message]
2004-03-30 19:36 ` 2.6.5-rc1-mm2 Andrew Morton
2004-03-30 19:44 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-31 19:02 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-31 20:06 ` 2.6.5-rc1-mm2 Andrew Morton
2004-03-31 23:15 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-31 23:56 ` 2.6.5-rc1-mm2 Andrew Morton
2004-03-31 23:58 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-04-01 0:16 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-04-01 19:28 ` 2.6.5-rc1-mm2 Jesse Barnes
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=200403301127.05151.jbarnes@sgi.com \
--to=jbarnes@sgi.com \
--cc=akpm@osdl.org \
--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