From: george anzinger <george@mvista.com>
To: Pavel Machek <pavel@ucw.cz>,
Linus Torvalds <torvalds@transmeta.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] High-res-timers part 2 (x86 platform code) take 6
Date: Sat, 26 Oct 2002 09:19:23 -0700 [thread overview]
Message-ID: <3DBAC08B.780FEA05@mvista.com> (raw)
In-Reply-To: 3DBAB90F.CEF29920@mvista.com
george anzinger wrote:
>
> Pavel Machek wrote:
> >
> > Hi!
> >
> > > This patch, in conjunction with the "core" high-res-timers
> > > patch implements high resolution timers on the i386
> > > platforms. The high-res-timers use the periodic interrupt
> > > to "remind" the system to look at the clock. The clock
> >
> > This scares me:
> >
> > +#define fail_message \
> > +"High-res-timers:
> > >-<--><-->-<-->-<-->-<--><-->-<-->-<-->-<-->-<-->-<-->-<-->-<\n"\
> > +"High-res-timers: >Failed to find the ACPI pm timer
> > <\n"\
> > +"High-res-timers: >-<--><-->-<-->-<-->-<-->Boot will fail in
> > Calibrate Delay <\n"\
> > +"High-res-timers: >Supply a valid default pm timer address
> > <\n"\
> > +"High-res-timers: >or get your BIOS to turn on ACPI support.
> > <\n"\
> > +"High-res-timers: >See CONFIGURE help for more information.
> > <\n"\
> > +"High-res-timers:
> > >-<--><-->-<-->-<-->-<--><-->-<-->-<-->-<-->-<-->-<-->-<-->-<\n"
> >
> > Does that mean our boot has now so much junk in it that we start
> > adding ascii art for "important" messages?
>
> Well, Yes! It does. However, the problem here is that this
> is detected prior to enabling the console so, unless the
> boot can limp along until that happens, this message will
> not be seen. I have seen both conditions...
This, of course is the problem, the message appears buried
in the noise prior to the actual boot failure (assuming it
is printed at all).
>
> I am open to suggestions...
>
> Thanks for looking.
>
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
prev parent reply other threads:[~2002-10-26 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 7:06 [PATCH 2/2] High-res-timers part 2 (x86 platform code) take 6 george anzinger
2002-10-23 9:38 ` Pavel Machek
2002-10-26 15:47 ` george anzinger
2002-10-26 16:19 ` george anzinger [this message]
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=3DBAC08B.780FEA05@mvista.com \
--to=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@transmeta.com \
/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