Re: [PATCH] PM-Timer: doesn't use workaround if chipset is not buggy

Andreas Mohr <[email protected]> writes:

> Should I do a public request for chipset testing?
> (I wrote a small test app here that would hopefully identify a buggy
> chipset).

I think almost ICH4 is not buggy.  But probably current approach is safe.
So, I added "pmtmr_good" to disable the workaround instead.

I posted probably similar one for mainly ICH4 users.
http://marc.theaimsgroup.com/?l=linux-kernel&m=114297656924494&w=2

> Data that I have collected from internet snippets (mostly Intel errata
> documents):
> Affected (PCI ID / rev):
>   - ICH4???
>   - PIIX4 A0 (0x7113 / 00?), A1 (0x7113 / 00?), B0 (0x7113 / 01?)
>   - PIIX4E A0 (0x7113 / 02?)
> Probably fixed (PCI ID / rev):
>   - PIIX4M A0 (0x7113 / 03?)
>
> My Toshiba Satellite 4280 seems to have non-buggy PIIX4M
> (since it's PCI rev. 03), haven't had time to test reliability yet, though.

I tested PIIX4E (yes, really buggy), ICH7, VT88237. And ICH6 was
reported as sane.

Thanks.
-- 
OGAWA Hirofumi <[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] PM-Timer: doesn't use workaround if chipset is not buggy
    • From: Andreas Mohr <[email protected]>

• References:
  • gettimeofday order of magnitude slower with pmtimer, which is default
    • From: bert hubert <[email protected]>
  • Re: gettimeofday order of magnitude slower with pmtimer, which is default
    • From: john stultz <[email protected]>
  • Re: gettimeofday order of magnitude slower with pmtimer, which is default
    • From: OGAWA Hirofumi <[email protected]>
  • Re: gettimeofday order of magnitude slower with pmtimer, which is default
    • From: Con Kolivas <[email protected]>
  • [PATCH] PM-Timer: doesn't use workaround if chipset is not buggy
    • From: OGAWA Hirofumi <[email protected]>
  • Re: [PATCH] PM-Timer: doesn't use workaround if chipset is not buggy
    • From: Andreas Mohr <[email protected]>

• Prev by Date: Re: [rfc][patch] Avoid taking global tasklist_lock for single threadedprocess at getrusage()
• Next by Date: [patch] Ignore MCFG if the mmconfig area isn't reserved in the e820 table
• Previous by thread: Re: [PATCH] PM-Timer: doesn't use workaround if chipset is not buggy
• Next by thread: Re: [PATCH] PM-Timer: doesn't use workaround if chipset is not buggy
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]