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:44:26 -0800 [thread overview]
Message-ID: <200403301144.26050.jbarnes@sgi.com> (raw)
In-Reply-To: <20040330113620.33d01d9c.akpm@osdl.org>
On Tuesday 30 March 2004 11:36 am, Andrew Morton wrote:
> I don't see anything especially hangy in 2.6.5-rc1-mm2 - maybe it's
> something which was sucked in via one of the "external trees". rc3-mm1
> boots OK on my ia64 box.
Well, like I said, the BK trees (both Linus' linux-2.5 and David's
to-linus-2.5) continue to work, all the way up through today, and
2.6.5-rc1-mm1 worked too.
> Do you not have the means to work out where things are stuck at?
It looks like there's a bug in the sysrq implementation in the sn_serial
driver. Once the initial console is opened, sysrq no longer works. All I've
determined so far is that both CPUs in my box are in cpu_idle somewhere...
Anyway, I'll keep looking.
Thanks,
Jesse
next prev parent reply other threads:[~2004-03-30 19:44 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 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-30 19:36 ` 2.6.5-rc1-mm2 Andrew Morton
2004-03-30 19:44 ` Jesse Barnes [this message]
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=200403301144.26050.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.