From: Jesse Barnes <jbarnes@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc1-mm2
Date: Tue, 30 Mar 2004 11:44:26 -0800
User-Agent: KMail/1.6.1
Cc: Andrew Morton <akpm@osdl.org>
References: <20040317201454.5b2e8a3c.akpm@osdl.org> <200403301127.05151.jbarnes@sgi.com> <20040330113620.33d01d9c.akpm@osdl.org>
In-Reply-To: <20040330113620.33d01d9c.akpm@osdl.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200403301144.26050.jbarnes@sgi.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 974
Lines: 23

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/