From: Len Brown <lenb@kernel.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Linus' tree broken?
Date: Mon, 23 Jul 2007 17:47:57 +0000 [thread overview]
Message-ID: <200707231347.57366.lenb@kernel.org> (raw)
In-Reply-To: <46A4B026.9030307@sgi.com>
On Monday 23 July 2007 12:05, Luck, Tony wrote:
> > Have anyone else had seen issues with the Linus git tree failing to
> > boot? I'm trying a pull as of this morning and it seems to hang when
> > it's brining up the ethernet devices.
> >
> > It's not locking up, just the boot scripts never continues - happens
> > both on SLES10 and FC7 roots :(
> >
> > Just wanted to check before spending real time on it.
>
> Pulled Linus' tree (the -rc1 commit is at the head) and it built
> and booted on my tiger. Only new strange stuff in the dmesg is a
> lot of
>
> ACPI Exception (processor_throttling-0084): AE_NOT_FOUND, Evaluating _PTC [20070126]
> ACPI Exception (processor_throttling-0147): AE_NOT_FOUND, Evaluating _TSS [20070126]
>
> messages (this pair of message repeats 16 times)
ignore those, they're harmless and going away shortly.
-Len
next prev parent reply other threads:[~2007-07-23 17:47 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 [this message]
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
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=200707231347.57366.lenb@kernel.org \
--to=lenb@kernel.org \
--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 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.