From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Linus' tree broken?
Date: Tue, 24 Jul 2007 08:30:51 +0000 [thread overview]
Message-ID: <46A5B8BB.3000703@sgi.com> (raw)
In-Reply-To: <46A4B026.9030307@sgi.com>
Russ Anderson wrote:
> Neither Linus' tree (2.6.23-rc1) nor Tony's test tree (2.6.22) boot on the
> three SN2 systems I tried booting on (SLES 10 roots). Tony's test tree
> from ~3 weeks ago does boot.
>
> The last boot message is "Starting udevd".
>
> The cpu LEDs are toggling between 0 & 1 "Kernel: CPU idle".
> It doesn't panic.
>
Yeah I see the same, I can hit return on the console and it reacts but
doesn't get any further.
git commit 7dcca30a32aadb0520417521b0c44f42d09fe05c works for me - thats
the 2.6.22 Sun Jul 8 marker from Linus. And I know git
f695baf2df9e0413d3521661070103711545207a is hosed - Sun Jul 22.
Sorry just sitting waiting for a plane, don't have much time to look at
it right now.
Wonder if Tony's .config is much different from everyone else's? Mine is
an SN2 specific kernel, haven't tried GENERIC yet.
Cheers,
Jes
next prev parent reply other threads:[~2007-07-24 8:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 13:41 Linus' tree broken? Jes Sorensen
2007-07-23 16:05 ` Luck, Tony
2007-07-23 16:32 ` Jes Sorensen
2007-07-23 17:00 ` Luck, Tony
2007-07-23 17:21 ` Doug Chapman
2007-07-23 17:40 ` Luck, Tony
2007-07-23 17:47 ` Len Brown
2007-07-23 20:22 ` Jes Sorensen
2007-07-23 20:39 ` Doug Chapman
2007-07-23 20:42 ` Luck, Tony
2007-07-23 21:03 ` Russ Anderson
2007-07-23 21:17 ` Peter Chubb
2007-07-23 22:24 ` Doug Chapman
2007-07-23 22:42 ` Luck, Tony
2007-07-23 23:07 ` Doug Chapman
2007-07-24 8:30 ` Jes Sorensen [this message]
2007-07-24 8:50 ` Jes Sorensen
2007-07-24 23:21 ` Russ Anderson
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=46A5B8BB.3000703@sgi.com \
--to=jes@sgi.com \
--cc=linux-ia64@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