From: Stephane Eranian <eranian@frankl.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] possible bug in the efi real time clock
Date: Sun, 10 Sep 2000 04:21:51 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205480@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205465@msgid-missing>
Uros,
> > > On the BigSur B1 stepping with BIOS 60 machine, it crashes when running
> > > the hwclock. Could it be a bug in the efi real time clock?
> > >
Our 4-way A3 with Build50 is showing similar behavior. However the system
is up and running fine with test8.
I looked at the efirtc driver one more time. The ioctl() to read the clock
fails because EFI.GetTime() returns an error. This is new to me. I need to
investigate why it is so. The reason why /proc/efirtc does not fails is
because of a missing test on the return values of the 2 EFI calls to read
the time. You get random results back. I will fix this today.
I am suspecting something is wrong in EFI with Build50 and up.
> I think this symptom was around for a long time. On pretty much all the
> distributions we shipped you could observe a brief video glitch during the
> boot when the system was setting hardware clock. Usually, the screen would
> go blank for a split second and then get switched on again. Why this would
> happen while running hwclock is beyond me. I do recall somebody with a Lion
> system observing a hard lockup. The workaround was to disable running
> hwclock on boot. Nobody here had time to poke around what was going on,
> though.
>
I saw this thing too recently on an A2 with Build59 but the system works
fine.
--Stephane
next prev parent reply other threads:[~2000-09-10 4:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-09 1:36 [Linux-ia64] possible bug in the efi real time clock aip
2000-09-09 4:21 ` Stephane Eranian
2000-09-09 19:51 ` Uros Prestor
2000-09-10 4:21 ` Stephane Eranian [this message]
2000-09-11 21:19 ` H . J . Lu
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=marc-linux-ia64-105590678205480@msgid-missing \
--to=eranian@frankl.hpl.hp.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