From: Uros Prestor <uros@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] possible bug in the efi real time clock
Date: Sat, 09 Sep 2000 19:51:03 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205470@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205465@msgid-missing>
Stephane Eranian wrote:
> > 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?
> >
> Hard to tell from this description. Could you give more details
> like what does appear on the screen ? Could you capture the "tombstone"
> (regs dump) and send it to me. I don't have a Bigsur B1 so I can't
> really reproduce the problem.
What happens is a complete system lockup. There is no kernel register dump,
panic or oops. The screen just goes blank. You can lock up the box by
simply running /sbin/hwclock.
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.
Uros
--
Uros Prestor
uros@turbolinux.com
next prev parent reply other threads:[~2000-09-09 19:51 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 [this message]
2000-09-10 4:21 ` Stephane Eranian
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-105590678205470@msgid-missing \
--to=uros@turbolinux.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 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.