From: Chris Rankin <rankincj@yahoo.com>
To: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: Linux-2.6.17: PMTimer results for another PCI chipset
Date: Mon, 26 Jun 2006 18:44:12 +0100 (BST) [thread overview]
Message-ID: <20060626174412.76248.qmail@web52905.mail.yahoo.com> (raw)
In-Reply-To: <20060626120847.GA6272@rhlx01.fht-esslingen.de>
--- Andreas Mohr <andi@rhlx01.fht-esslingen.de> wrote:
> Yeah, but this is no problem anyway, since it's neither in the blacklisted
> nor in the graylisted area, IOW it's whitelisted and should work
> without delays.
> Or do you get the "The chipset may have PM-Timer Bug" message here??
>
> > 00:1f.0 Class 0601: 8086:2440 (rev 05)
>
> #define PCI_DEVICE_ID_INTEL_82801BA_0 0x2440
Nope, it's all good. But since this chipset was released between the one which definitely has the
bug and one which might have the bug, I thought that it was worth testing it for real.
Cheers,
Chris
___________________________________________________________
Try the all-new Yahoo! Mail. "The New Version is radically easier to use" The Wall Street Journal
http://uk.docs.yahoo.com/nowyoucan.html
next prev parent reply other threads:[~2006-06-26 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060620100800.GB5040@disjunkt.com>
2006-06-20 10:19 ` Linux 2.6.17: PM-Timer bug warning? Andreas Mohr
2006-06-20 13:03 ` Jean-Daniel Pauget
2006-06-20 14:58 ` OGAWA Hirofumi
2006-06-20 15:16 ` Andreas Mohr
2006-06-23 18:22 ` [PATCH -mm] clocksource: add PM Timer bug hunting notes Andreas Mohr
2006-06-25 20:42 ` Linux-2.6.17: PMTimer results for another PCI chipset Chris Rankin
2006-06-26 12:08 ` Andreas Mohr
2006-06-26 17:44 ` Chris Rankin [this message]
2006-06-26 18:02 ` Andreas Mohr
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=20060626174412.76248.qmail@web52905.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=hirofumi@mail.parknet.co.jp \
--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®