Re: did someone break SMP on amd64-current?

[Hisashi T Fujinaka <htodd%twofifty.com@localhost>]

On Fri, 18 Feb 2011, Hisashi T Fujinaka wrote:

> On Fri, 18 Feb 2011, Jukka Ruohonen wrote:
>
> > On Thu, Feb 17, 2011 at 09:17:10AM -0800, Hisashi T Fujinaka wrote:
> > > On Thu, 17 Feb 2011, Jukka Ruohonen wrote:
> > >
> > > > On Wed, Feb 16, 2011 at 10:55:55PM -0800, Hisashi T Fujinaka wrote:
> > > > > acpicpu0: failed to evaluate _TSS: AE_AML_BAD_RESOURCE_VALUE
> > > > > acpicpu1 at acpi0 (CPU1): ACPI CPU
> > > > >
> > > > > Is that expected?
> > > >
> > > > Of course not. Can you try what the following printf-diff yields?
> > >
> > > Where would those show up? On boot dmesg and /var/log/messages didn't
> > > change at all.
> >
> > Should be fixed now. It was harmless, given that T-state are not used for
> > anything ATM. Thanks for the report.
> >
> > - Jukka.
> >
> > PS. We try keep acpi(4) noisy so that better understanding of the issues 
> > can
> >    be gained. As this area is essentially non-deterministic, you can not
> >    just look things from a data sheet, but have to additionally think "what
> >    the BIOS writer meant" and "what would Windows do". Thus the verbose
> >    error/debug reporting.
>
> Thanks. I've been trying to get amd64-current to build. I'll let you
> know if I see any problems after it does.

top seems to see eight cores, but fah6 (folding@home from
http//folding.stanford.edu) only sees one core.

--
Hisashi T Fujinaka - htodd%twofifty.com@localhost
BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte