From: Benjamin LaHaise <bcrl@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: lonely wolf <wolfy@nobugconsulting.ro>, linux-kernel@vger.kernel.org
Subject: Re: probable hardware bug: clock timer configuration lost
Date: Thu, 20 Sep 2001 22:16:10 -0400 [thread overview]
Message-ID: <20010920221610.A14451@redhat.com> (raw)
In-Reply-To: <3BAA9008.9837EA52@nobugconsulting.ro> <E15kEkB-0006nQ-00@the-village.bc.nu>
In-Reply-To: <E15kEkB-0006nQ-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Sep 21, 2001 at 02:04:39AM +0100
On Fri, Sep 21, 2001 at 02:04:39AM +0100, Alan Cox wrote:
> Its harmless. When we detect this we restore the state of the chip
> correctly. If anything I should kill the printk but I'd still like to
> figure the precise errata issue out
Odd, I just got this during booting of my ALi based boards (never had seen
it before). Are we certain the test is correct?
-ben
next prev parent reply other threads:[~2001-09-21 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 0:55 probable hardware bug: clock timer configuration lost lonely wolf
2001-09-21 1:04 ` Alan Cox
2001-09-21 2:16 ` Benjamin LaHaise [this message]
2001-09-21 9:49 ` lonely wolf
2001-09-21 11:54 ` Alan Cox
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=20010920221610.A14451@redhat.com \
--to=bcrl@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=wolfy@nobugconsulting.ro \
/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