From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Horms <horms@verge.net.au>
Cc: linux-kernel@vger.kernel.org, 277298@bugs.debian.org
Subject: Re: RTC problem on 8208CA
Date: Tue, 3 May 2005 20:25:41 -0700 (PDT) [thread overview]
Message-ID: <20050504032541.58650.qmail@web60513.mail.yahoo.com> (raw)
In-Reply-To: <20050502051634.GA18295@verge.net.au>
At a glance this sounds like the case of having the HPET enabled causes
the RTC IRQ functionality to become crippled or non-functional. The
concept of hwclock using alarm or similar to handle broken and
misconfigured hardware is a sensible idea.
Paul.
--- Horms <horms@verge.net.au> wrote:
> Hi,
>
> I am doing some investigations into a problem that has been reported
> with RTC on some Dell Machines. It seems to be relate exclusively to
> machines that have the 8208CA ICH3 I/O Hub. I have been able to
> reproduce this on a Dell 8400, which I have access to today while I am
> on holidays. The output of lspci -v -x is attached.
>
> For reference this problem is being tracked at
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277298
>
> There are various user-space work arounds for this problem, but I would
> like to offer what I have discovered from a brief poke-around in rtc.c.
>
> An strace of hwclock looks a bit like this
>
> open("/dev/rtc", O_RDONLY|O_LARGEFILE);
> ioctl(3, RTC_UIE_ON, 0);
> read(3, ...
>
> the read never returns.
>
> If my reading of the code is correct, what is occuring is that
> rtc_read() is in its do/while loop, waiting to be rescheduled. This
> should occur once an interupt is handled by rtc_interrupt(), but I guess
> that this is not occuring. Any insights into why this might be happening
> would be more than welcome.
>
> The kernel in question is Ubuntu's 2.6.8.1, the rtc.c is identical from
> what was in linus' tree this morning. The config is also attached.
>
> Please CC me on replies
>
> Thanks
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2005-05-04 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 5:16 Horms
2005-05-04 3:25 ` Paul Gortmaker [this message]
2005-05-05 2:34 ` Horms
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=20050504032541.58650.qmail@web60513.mail.yahoo.com \
--to=p_gortmaker@yahoo.com \
--cc=277298@bugs.debian.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®