freebsd-stable Digest, Vol 349, Issue 7
freebsd-sta...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. 7.3-RELEASE make release requires wrong version of perl
(David Boyd)
2. Re: Powerd and est / eist functionality (John Long)
3. FreeBSD 8.0 SCSI Boot (Doug Hardie)
4. Re: Powerd and est / eist functionality (Ian Smith)
5. Re: Many processes stuck in zfs (Stefan Bethke)
----------------------------------------------------------------------
Message: 1
Date: Fri, 26 Mar 2010 16:09:33 -0400
From: "David Boyd" <David...@insightbb.com>
Subject: 7.3-RELEASE make release requires wrong version of perl
To: <freebsd...@freebsd.org>
Message-ID: <OJEBKOFDEOADELCOBJC...@insightbb.com>
Content-Type: text/plain; charset="iso-8859-1"
Attempting make release results in error complaining that perl-5.8.9
installs into the same locations as perl-5.10.1.
This seems similar to the problem I encountered with make release when NODOC
was not set.
The complaint then was that ghostscript8-nox11 installs into the same
locations as ghostscrip8.
Any help would be appreciated.
Thanks.
------------------------------
Message: 2
Date: Fri, 26 Mar 2010 16:46:40 -0700
From: John Long <fb...@sstec.com>
Subject: Re: Powerd and est / eist functionality
To: Alexander Motin <m...@FreeBSD.org>
Cc: FreeBSD-STABLE Mailing List <freebsd...@FreeBSD.org>
Message-ID: <5.2.1.1.2.201003...@mail.sstec.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed
At 01:31 AM 3/26/2010, Alexander Motin wrote:
>John Long wrote:
>>>Have you tried C2? Are you running the latest BIOS? And perhaps your
>>>ACPI ASL may be amenable to repair, if Gigabyte ACPI is broken here?
>
>As I can see, your ACPI reports C3 state support. You may try it also.
>Here is my notes about power and C3 also:
>http://wiki.freebsd.org/TuningPowerConsumption
>Alexander Motin
Hi, you have achieved good results with your laptop tuning, 50% power
reduction.
I tried the disable thing and got what I thought would happen.
hint.p4tcc.0.disabled=1
hint.acpi_throttle.0.disabled=1
Since est is not working on this system then it falls back to p4tcc and
throttle but if they are disabled then powerd chokes with "lookup freq: no
such file or directory" and does not run.
I did locate est.c under cpufreq dir. It looks to be from 2004/5 era and
alas the cpu lookups in there are most all from that time frame also. I
find this bit of code:
/*
* Probe for supported CPU settings. First, check our static table of
* settings. If no match, try using the ones offered by acpi_perf
* (i.e., _PSS). We use ACPI second because some systems (IBM R/T40
* series) export both legacy SMM IO-based access and direct MSR access
* but the direct access specifies invalid values for _PSS.
*/
static int
est_get_info(device_t dev)
{
struct est_softc *sc;
uint64_t msr;
int error;
sc = device_get_softc(dev);
msr = rdmsr(MSR_PERF_STATUS);
error = est_table_info(dev, msr, &sc->freq_list);
if (error)
error = est_acpi_info(dev, &sc->freq_list);
if (error)
error = est_msr_info(dev, msr, &sc->freq_list);
if (error) {
printf(
"est: CPU supports Enhanced Speedstep, but is not recognized.\n"
"est: cpu_vendor %s, msr %0jx\n", cpu_vendor, msr);
return (ENXIO);
}
return (0);
}
Therein looks to be the problem, the msr table/freq_list lookup is just way
out of date and fails to load est and therefore the fallback to p4tcc for
powerd which is useless for reduction. I need to get est running so that it
handles the P-states which include the voltage reduction. There are a
couple other places where it tests and sets flags that may be relevant but
it is a little bit more work and a little over my head than I was looking
for. Maybe ACPI is just not giving enough info and the asl can be modified
but I do not know enough about it or much of any of this.. There is a whole
box of worms in acpica dir. I looked thru acpi_perf.c but the rabbit trail
looks a bit daunting. There are briar patches throughout.
Maybe Colin Percival or Nate Lawson can shed some light on this and if it
is reasonable to do an update for that bit of code/table. If there were a
prog that could invoke est.c and have it spit out the factors it sees for a
clue as to just what might be needed to get it loaded, that would be helpful.
>> est: CPU supports Enhanced Speedstep, but is not recognized.
>> est: cpu_vendor GenuineIntel, msr 6160b2506000b25
is meaningless to me :-(
I do realize that there have been hundreds of cpus and factors since that
time, maybe a wildcard lookup of some sort would suffice. To just get this
thing loaded because the rest of the code looks clever and good. Also, if
some discovery here helps the project and saves a few watts times thousands
of us then it might be worth pursuing but if the general consensus is not
worth the trouble then I understand.
John
btw: I had tried C3 earlier and C2 also, they both save about 1 watt max
and C3 is quite a dramatic thing to do considering the crucial parts of the
system it shuts down. For a laptop that would be okay but this is going to
be a relatively busy server running dns, apache, nat etc. I do not think it
will have much time to sleep but with the speed of a c2d it will not been
too busy either, always just a few percent. Therein lies my desire, to get
the voltage down when the freq is low and still allow demand speed to be
there if needed.
------------------------------
Message: 3
Date: Fri, 26 Mar 2010 17:18:30 -0700
From: Doug Hardie <bc...@lafn.org>
Subject: FreeBSD 8.0 SCSI Boot
To: FreeBSD-STABLE Mailing List <freebsd...@freebsd.org>
Message-ID: <548D66CF-4FAA-4D4D...@lafn.org>
Content-Type: text/plain; charset=us-ascii
I tried to upgrade a 7.2 system to 8.0. It uses a SCSI drive. It works fine on 7.2. However, it would appear that during the upgrade process when running make delete-old (?) there is a note about make delete-old-libs (?). Don't do that at that point. End of system. Make installworld fails miserably. Unfortunately rebooting caused numerous problems. First the /etc/fstab was listed as corrupt. Then it quit booting altogether. A complete reload from the disc 1 goes nowhere either. It installs just fine but when it goes to reboot, All I get is F1 followed by a bunch of increasing #s. Any key just adds more to the list. I have tried with both the standard and FreeBSD boot managers with the same result. Is there anyway to get it to boot off the SCSI drive? I couldn't find anything related to this in the forums etc.
------------------------------
Message: 4
Date: Sat, 27 Mar 2010 16:35:36 +1100 (EST)
From: Ian Smith <smi...@nimnet.asn.au>
Subject: Re: Powerd and est / eist functionality
To: Jeremy Chadwick <fre...@jdc.parodius.com>
Cc: Alexander Motin <m...@freebsd.org>, FreeBSD-STABLE Mailing List
<freebsd...@freebsd.org>
Message-ID: <2010032715...@sola.nimnet.asn.au>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Fri, 26 Mar 2010, Jeremy Chadwick wrote:
[ leaving the MB monitoring stuff alone for your expert attention :-]
> > It jumped up in vcore a little there with powerd. C1E and C2E which
> > include P-states are what I am really after and I think that the
> > bios by itself provides those changes better than any other changes
> > in these settings.
>
> ...and this would fall under the est(4) subset driver for cpufreq(4).
Just checking, I know nothing about these so far, but are you suggesting
that John having C1E and C2E enabled in BIOS may be affecting ACPI/EST
detection, and that things may be different were these disabled?
If that's not what you meant, could you expand a little?
John: you may want to explore where this comes together in kern_cpu.c
where you'll see those cpufreq debugging messages you quoted. Some of
the more gritty documentation may be found browsing with something like:
% less /sys/{sys,kern,amd64/include}/*cpu*.[ch]
cheers, Ian
------------------------------
Message: 5
Date: Sat, 27 Mar 2010 08:08:27 +0100
From: Stefan Bethke <s...@lassitu.de>
Subject: Re: Many processes stuck in zfs
To: Pawel Jakub Dawidek <p...@FreeBSD.org>
Cc: FreeBSD Stable <freebsd...@freebsd.org>
Message-ID: <807E774E-2473-422A...@lassitu.de>
Content-Type: text/plain; charset=us-ascii
Am 10.03.2010 um 12:02 schrieb Pawel Jakub Dawidek:
> Once the deadlock occur, enter DDB and send me the output of:
>
> ps
> show alllocks
> show lockedvnods
> show allchains
> alltrace
panic: deadlkres: possible deadlock detected for 0xffffff000c66e000, blocked for 1801490 ticks
I've saved a core, and can try to look at more things. The text dump is at http://www.lassitu.de/freebsd/core.txt.13
show alllocks and show lockedvnods only gave me a "no such command" error. Otherwise, the full output is at http://www.lassitu.de/freebsd/zfs_panic.txt.
Thanks,
Stefan
--
Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811
------------------------------
End of freebsd-stable Digest, Vol 349, Issue 7
**********************************************