supported_max_cstates shows the count of supported C-states (in this
case 1 and 3?), not the actual C-state number, according to
https://defect.opensolaris.org/bz/show_bug.cgi?id=7884
-Albert
___
opensolaris-code mailing list
opensolaris-code@opensolaris
On Sat, 2010-10-16 at 21:49 -0400, Edward Ned Harvey wrote:
> > From: Garrett D'Amore [mailto:garr...@damore.org]
> >
> > TBH, This requires significant investigation, and probably nobody with
> > sufficient skill has enough time, or vice versa. :-)
> >
> > File a bug so it doesn't get lost. On
> From: Garrett D'Amore [mailto:garr...@damore.org]
>
> TBH, This requires significant investigation, and probably nobody with
> sufficient skill has enough time, or vice versa. :-)
>
> File a bug so it doesn't get lost. On www.illumos.org, too, please.
I'll try illumos ... But ... Where would
On Fri, 2010-10-15 at 21:36 -0400, Edward Ned Harvey wrote:
> > From: opensolaris-code-boun...@opensolaris.org [mailto:opensolaris-
> > code-boun...@opensolaris.org] On Behalf Of Edward Ned Harvey
>
> No responses? Not even to this part? Anybody out there??? ;-)
>
TBH, This requires significa
> From: opensolaris-code-boun...@opensolaris.org [mailto:opensolaris-
> code-boun...@opensolaris.org] On Behalf Of Edward Ned Harvey
No responses? Not even to this part? Anybody out there??? ;-)
> Is this mailing list a good place to reach out to kernel developers, or
> whoever would be appro
Correct me if I'm wrong, but current_cstate should never be greater than
supported_max_cstates, right?
There are a lot of reports out there, of systems crashing, due to problems
with cstate, and generally people go into BIOS and disable cstates. Call it
a "workaround." But it would be nice if
