Re: svn - but smaller?
One of my teammates and I were just doing a write up on this very issue, On Jan 23, 2013, at 10:55 AM, Mike Tancsa wrote: > On 1/23/2013 10:37 AM, Oliver Brandmueller wrote: >> >> But my main concern is the system sources anyway. freebsd-update is not >> feasible for me, as described in the original post. >> > Actually, if you build the port minus the NEON option, its as bad in > terms of dependencies. THE UGLY Source for SVN: 496M (+) Source for FreeBSD 9.1: 746M (actual) (df output details below) --- THE BAD After 15+ years of FreeBSD use, I remember what a great thing cvsup was when it hit. However, SVN presents several problems for OS use (again): 1) License. Many of SVN's dependencies will never be available in the FreeBSD source. While this is totally OK for development, SVN is 3rd party software, this is unacceptable to force as 'the' respected path for OS source builds. 2) Heft: cvsup/csup was excellent for 1 thing: grabbing a REL branch. Perhaps grabbing STABLE or CURRENT. Systems administrators could QA/test new branches on massive numbers of servers quickly and efficiently. THE GOOD We've just resolved this for ourselves, and are wrapping it in a clean sh script: (I'd love to know where we can send it for input when we're done?) 40 lines of shell could get the jist of what users really need: - Download the src using fetch(1) fetch ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/9.1-RELEASE/src.txz - Extract the tarball (to /usr/src, or wherever). tar -xf src.txz We're hacking out some simple script add-ons out right now for ourselves, to make this more CVSUP like: + flag to keep source tarball somewhere (instead of merely un-tarring it in a pipe) + flag to un-tar source to a particular directory + flag to specify OS version + flag to specify RELEASE, STABLE, CURRENT (if they exist, CURRENT may be tricky?) + define source server/mirror + source config in /etc, (or rc.conf ?), if exists -- Nice-to-have extra features (some necessary for us): + define protocol (tricky), e.g. ftp/http/https/other + after unpacking, run against mtree (possibly kept on separate server or locally) to validate sources + exit non-zero if particular conditions exist + checksum tarball (possibly against checksums kept on separate server or locally) to validate sources + exit non-zero if particular conditions exist + flags to override/change tar options ++ also nice to have, more cvsup features, (I need to read through man page again for a sanity check) -- Regarding SVN: I know the SVN change is a profound leap foreword in source management and collaboration, (I've carried many shops through CVS/SVN/GIT migrations as an SA). Developing/hacking in the FreeBSD source is already simpler, though as an outsider, (no commit bit), the transition has been expectedly rough-edged :) On Jan 23, 2013, at 10:06 AM, Ronald Klop wrote: > I've read about this initiative. > http://svnweb.freebsd.org/base/user/des/svnsup/ > Maybe you can help there. Aside from the heft/licence issues I noted above, it's a bit late to consider this, cvsup is going away: - the *ports* CVS/csup infrastructure is going to be disabled on Feburary 28th - the *source* CVS/csup infrastructure is deprecated, but doesn't have a definite end-date On Wed, Jan 23, 2013 at 04:12:22PM +0100, Frank Staals wrote: >> I'm kind of surprised for the need of this though. Why not simply use >> portsnap if you are not actively developing ports? > On Jan 23, 2013, at 10:37 AM, Oliver Brandmueller wrote: > But my main concern is the system sources anyway. freebsd-update is not > feasible for me, as described in the original post. For users/administrators, to merely fetch OS sources for a given branch, it goes against the grain of nearly every reason users use FreeBSD to say 'just use svn'. Additionally, it's not been fun recently to 'just use portssnap', when the actual binary ports servers have gone through the recent security incident, (as well as all the changes). I'm not meaning to be negative here, but this has slid pretty far away from the ideals that *BSD users care about. Best, .ike # uncompressed canonical sources for svn (I believe I missed some dependencies of the dependencies) du -d 1 -h 5.5M./apr-1.4.6 5.3M./sqlite-amalgamation-3071300 13M./libtool-2.4.2 79M./perl-5.16.2 4.0M./neon-0.29.6 66M./Python-2.7.1 153M./db-5.3.21 55M./subversion-1.7.8 8.6M./m4-1.4.16 3.0M./expat-2.1.0 12M./pkg-config-0.27.1 3.0M./gdbm-1.10 67M./gettext-0.18.1.1 21M./libiconv-1.14 496M. ## FreeBSD 9.1 Source $ pwd ; du -d 1 -h /usr/src 3.2M./bin 11M./cddl 316M./contrib 40M./crypto 2.0M./etc 3.7M./games 5.9M./gnu 1.1M./include 484k./kerberos5 31M./lib 2.1M./libexec 1.3M./release 32k./rescue 7.2M./sbin 3.6M./secure 39M./share 200M./sys 44M./tools
Re: svn - but smaller?
On Jan 23, 2013, at 2:17 PM, Emanuel Haupt wrote: > Oliver Brandmueller wrote: >> Hi, >> >> in ancient times there was cvsup. cvsup was a PITA if you wanted (or >> needed) to install it via ports, the only reasonable way was to use >> pkg_add for that if you didn't want to pollute your system with >> otherwise unneeded software. >> >> Then there came csup. Small, in the base. You could install FreeBSD >> and the first task (for me and my environment) was often to simply >> csup to -STABLE (or a known good version of that) and to build an >> up-to-date and customised system. Like tayloring make.conf and >> src.conf to my needs and leave out most of the stuff I don't need on >> my system and in the kernel. Software and drivers that aren't there >> can't fail and won't be a security problem. >> >> Times have been changing, we're now up to svn. svn is far more modern >> than cvs and there are pretty good reasons to use it. >> >> However, I either overlook something important or we are now at the >> point we had with cvsup in the early days: The software I need to >> (source-)update the system doens't come with the base and installing >> svn is a PITA. It pulls in a whole lot of dependencies, at the time >> being in FBSD-9.1-R I cannot even pkg_add -r subversion out of the >> box. And in the end I have my system polluted with software and >> libraries I don't really need in many cases for anything else. >> >> So, is there some alternative small svn client, that leaves a >> drastically smaller footprint probably somewhere around, probably >> even in the ports or is there anything I'm missing? The current >> situaion for me is a bit annoying. From the user's or admin's point >> of view at least. I didn't even see an option in svn to not build the >> server components, which would probably already help to make things >> smaller? >> >> Thanx, >> Oliver On Jan 23, 2013, at 2:09 PM, Peter Wemm wrote: > On Wed, Jan 23, 2013 at 9:05 AM, Isaac (.ike) Levy > wrote: > >> 1) License. Many of SVN's dependencies will never be available in the >> FreeBSD source. >> While this is totally OK for development, SVN is 3rd party software, this is >> unacceptable to force as 'the' respected path for OS source builds. > > Don't confuse the excessive ports default settings as dependencies. > You can make a quite mean and lean svn client. I did a 100% > BSD-license-compatible src/contrib/svn style proof-of-concept back > when we were planning what to do. Things like gdbm and bdb are not > required and are license contamination that we don't need. But that's > the fault of the port, not a fundamental property of using svn. On Jan 23, 2013, at 2:17 PM, Emanuel Haupt wrote: > devel/subversion already has an option to build a static version. A > solution could be to create a stub port (devel/subversion-static) > similar to: > > shells/bash-devel > shells/bash-static-devel > > dns/ldns > dns/py-ldns > > That way the package build cluster would create a package of the static > version which wouldn't pull in any runtime dependencies. > > Emanuel Peter, this work sounds great, and sounds like it would make a great stub port itself! I'd love to see whatever you have remaining from the proof-of-concept work, to perhaps help expand it into 'devel/subversion-lite' or 'devel/subversion-static' ? I'd happily use it for development. -- However, SVN for development use is not what the point, this thread is about using, administrating, and maintaining FreeBSD systems- not about development process. And in that case, SVN is still a fairly massive toolset for the simple task of fetching REL, STABLE, or CURRENT: Source for SVN-alone:55M Source for FreeBSD 9.1: 746M That's still over 7% of the size of the entire OS. I believe it's not at all necessary to have anything except the base FreeBSD OS, to update/install FreeBSD. -- A NYC*BUG list user posted this reminder, we've been here before: > Deja-vu… This reminds me of cvsup+modula-3. > > http://www.mavetju.org/mail/view_message.php?list=freebsd-current&id=209027 I'll keep hacking on our shell utility, and will post the PR to this thread. Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: svn - but smaller?
On Jan 23, 2013, at 9:40 AM, Oliver Brandmueller wrote: > Hi, > > in ancient times there was cvsup. ... > Then there came csup. ... > Times have been changing, we're now up to svn. ... > alternative small svn client I'm trying to consolidate notes on this topic, here: https://wiki.freebsd.org/UsersFetchingSource (Aiming to condense some clarity for as many parts of the situation as I can). Please feel to make edits (esp. if you are a committer who knows something I don't!), or email me with corrections and I'll put them in! Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: svn - but smaller?
Hi Peter, On Jan 24, 2013, at 6:13 AM, Peter Jeremy wrote: > On 2013-Jan-23 15:40:50 +0100, Oliver Brandmueller wrote: >> in ancient times there was cvsup. cvsup was a PITA if you wanted (or >> needed) to install it via ports, the only reasonable way was to use >> pkg_add for that if you didn't want to pollute your system with >> otherwise unneeded software. > > There was also ctm(1). ctm is small, BSD-licensed and has been part > of FreeBSD forever (almost). Thanks to stephen@, ctm deltas for > various src trees, as well as the entire SVN repo are still available. > c[v]sup can do things than aren't possible with ctm but I would expect > that most people who currently use c[v]sup could readily migrate to > using ctm. > > See http://www.freebsd.org/doc/handbook/ctm.html for details. > > Note that mirroring the actual SVN repo via ctm requires some patches. > There is a README and patches in > ftp://ftp.freebsd.org/pub/FreeBSD/CTM/svn-cur/ > > -- > Peter Jeremy Thank you for adding the ctm bits in the page, I'm deeply intrigued by possibly solving this problem with bits *already* in base?!! https://wiki.freebsd.org/action/diff/UsersFetchingSource?action=diff&rev1=6&rev2=7 However, even after reading the handbook page, I just don't quite understand how to use it on a modern system. (The handbook page isn't too helpful, nor is the man page- perhaps I'm looking at it backwards) Could you help clarify: - does CTM go away with the CVS servers? - do CTM-compatable patch/delta files exist on project repos? - what is the cleanest path to using CTM? (e.g. is the patch you mention required) -- Say I have a bare 9.1 install, no ports, haven't downloaded any base/src or ports yet. How do I go about using ctm(1) to fetch REL or STABLE to /usr/src, command by command? Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: svn - but smaller?
On CTM, On Jan 27, 2013, at 10:54 PM, Stephen Montgomery-Smith wrote: > On 01/27/2013 09:24 PM, Isaac (.ike) Levy wrote: >> On Jan 24, 2013, at 6:13 AM, Peter Jeremy wrote: >>> On 2013-Jan-23 15:40:50 +0100, Oliver Brandmueller wrote: >>>> in ancient times there was cvsup. >> >> Thank you for adding the ctm bits in the page, I'm deeply intrigued by >> possibly solving this problem with bits *already* in base?!! ... >> - does CTM go away with the CVS servers? >> - do CTM-compatable patch/delta files exist on project repos? >> - what is the cleanest path to using CTM? (e.g. is the patch you mention >> required) ... >> Say I have a bare 9.1 install, no ports, haven't downloaded any base/src or >> ports yet. >> How do I go about using ctm(1) to fetch REL or STABLE to /usr/src, command >> by command? > > First, you don't need any patches to get started. > > Suppose you want to keep up with 9.x-stable. Then you look at the ftp > site ftp://ftp.freebsd.org/pub/FreeBSD/CTM/src-9/, look at the latest > xEmpty file, and fetch it. Then create an empty directory /usr/src, and > then do > cd /usr/src && ctm the-xEmpty-file-you-downloaded. > No need to decompress the file first. > Then fetch from the same web site all the files whose number is greater > than the xEmpty file you downloaded and do > cd /usr/src && ctm the-rest-of-the-files* > > Now in /usr/src, you will have a reasonably up to date version of > 9.x-stable. > > You can keep it up to date by getting more files, either from the ftp > site, or by email, and doing again > cd /usr/src && ctm the-rest-of-the-files* > It will automatically ignore the files already applied. > > Similar instructions for all the other stable/currents and ports. Main > thing to remember - start with an empty directory. > > Also making local changes is not permitted. If ctm tries to modify a > file whose md5 checksum has changed, it will quit with an error message. > (But it won't leave your system in an unusable state - if you put that > file back to its original state, then ctm will work again.) > > Now, if you want something not offered by ctm (e.g. 8.2-release), then > you need to use svn. You can get svn via ctm. But you (1) need to > apply the patch, (2) install the svn port, and (3) install the xz port > if your FreeBSD is really old. Thank you Stephen, ctm(1) is quite rad, but I see now how it doesn't really replace the 'one-liner' pull of c[v]sup… I updated the wiki page with an example from your notes, https://wiki.freebsd.org/UsersFetchingSource -- With that, 2 questions: - I'm wondering if there is a clean/reliable way to pull an index of the CTM deltas? (This is still very far from the one-liner c[v]sup had become, it would be great to check for new delta files in a simple automated manner.) - does CTM go away with the CVS servers, e.g. who/how is it supported supported and maintained going foreword under SVN? Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: svn - but smaller?
On Jan 27, 2013, at 10:27 PM, John Mehr wrote: > On Sun, 27 Jan 2013 16:03:35 -0500 > "Isaac (.ike) Levy" wrote: >> On Jan 25, 2013, at 8:27 PM, John Mehr wrote: >>> On Fri, 25 Jan 2013 10:27:23 +0100 >>> Oliver Brandmueller wrote: >>>> Also I'd like to mention John Mehr, who's work on a "lightweight, >>>> dependency-free, BSD licensed program to pull source using the svn >>>> protocol" (couldn't say it better, so I use his words :-)). Hope this will >>>> make it into ports soon and in the long run even to base! >>> Thank you for the kind words. If all goes well (I'm still wearing my >>> "Crown of Naive Optimism") I should have something ready for show-and-tell >>> in the next week or so and I'll be submitting it as a new port soon after >>> that. >> John, Pullin' for you man! >> If you make progress, please give a shout and I'll note it in this page: >> https://wiki.freebsd.org/UsersFetchingSource >> Best, >> .ike > > Hello, > > I think I've got all of the protocol issues sorted out as good as they'll > probably get. I can't get the exact file permissions from the get-file > requests -- it only lets me know which ones are executable. Setting > executables to 0755 and non-executables to 0644 would work for all files in > my copy of /usr/src except for /usr/src/usr.bin/lex/mkskel.sh (0744) and > /usr/src/usr.sbin/pkg_install/tkpkg (0754). Since they're both executable > for root, unless there's an issue, we could probably let it slide and assign > them 0755 permissions. > > All I have left at this point is to add support for command line > configuration options, add comments, tidy everything up, get it to conform to > the "man style" guidelines and test it against a remote repository. Hey Jonn, this news is better than my Monday AM coffee. Once you have something working, however crudely, I'd love to link/post/reference it on the growing wiki page- so folks can give it a whirl. https://wiki.freebsd.org/UsersFetchingSource (If this project succeeds, it will neatly get rid of the purpose of the page!) Thanks- Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: svn - but smaller?
On CTM: On Jan 28, 2013, at 9:09 AM, Stephen Montgomery-Smith wrote: >> - I'm wondering if there is a clean/reliable way to pull an index of the CTM >> deltas? (This is still very far from the one-liner c[v]sup had become, it >> would be great to check for new delta files in a simple automated manner.) >> > > Not sure what you mean. You can do "ctm -l file-name" and it will tell > you what files are modified in that delta. And for ports, you have the > usual "make fetchindex." But that is about it. I'm sorry I wasn't clear enough- I meant: On the FTP server, is there an index of which CTM delta files are on the FTP server? I'd like to automate fetching just the new deltas... If there was perhaps 1 file with a consistent name, I could fetch that on a nightly basis and fetch the other CTM files. >> - does CTM go away with the CVS servers, e.g. who/how is it supported >> supported and maintained going foreword under SVN? >> > > No. CTM is now completely dependent on svn. I create the CTM deltas on > a computer owned by the University of Missouri. Cool. Is there any redundancy for this process, for example, deltas being created out on the east/west mirrors? Perhaps as an SVN post-commit hook? Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: svn - but smaller?
>> On CTM: Taking the CTM questions over to ctm-users@ Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: svn - but smaller?
On Jan 27, 2013, at 10:27 PM, John Mehr wrote: > Hello, > > I think I've got all of the protocol issues sorted out as good as they'll > probably get. I can't get the exact file permissions from the get-file > requests -- it only lets me know which ones are executable. Setting > executables to 0755 and non-executables to 0644 would work for all files in > my copy of /usr/src except for /usr/src/usr.bin/lex/mkskel.sh (0744) and > /usr/src/usr.sbin/pkg_install/tkpkg (0754). Since they're both executable > for root, unless there's an issue, we could probably let it slide and assign > them 0755 permissions. > > All I have left at this point is to add support for command line > configuration options, add comments, tidy everything up, get it to conform to > the "man style" guidelines and test it against a remote repository. John, All, Just a quick announce re. "svnup" utility is really exciting/important work- I wanted to give a shout that I re-focued my shell based c[v]sup workalike, and I'm gunnin' for a basically functional utility this weekend sometime. The folks managing ctm(1) deltas on the distribution servers, have kicked in some help to make this happen on the server side. Just to be clear: I'm not trying to compete or confuse- the "svnup" work is terribly important to me- but I (and some colleagues) need a workalike *asap*. With that, I'll keep driving updates from all around into the wiki page: https://wiki.freebsd.org/UsersFetchingSource Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: svn - but smaller?
On Feb 23, 2013, at 7:36 PM, John Mehr wrote: > Hello all, > I've believe I've made just about all of the progress optimizing svnup > as I can and I've just submitted it as a new port. With my ~ 350kb/s > DSL connection, it now takes just under 30 minutes to download a fresh > base/releng/8.3 tree using svnup (Subversion's svn takes approximately > 12 minutes). Incremental updates, such as tracking one of the stable > branches takes only 2-3 minutes. > For anyone that wants to preview the port before it gets added to the > ports tree (assuming I got the send-pr correct), the tarball is located > at: > http://jcm.dsl.visi.com/freebsd/svnup/svnup-0.5.tar.xz > Please let me know if you find any issues. If anyone has any info about sunup(1) making it's way into base, please tell me so I can kill this page: https://wiki.freebsd.org/UsersFetchingSource (After trying to catch up on the relevant lists, I just updated that 'status page' on the FreeBSD wiki.) -- John, this is spectacular- thank you! Rocket- .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: svn - but smaller?
On Mar 11, 2013, at 12:53 AM, Ian Smith wrote: > On Sun, 10 Mar 2013 20:33:50 -0400, Isaac (.ike) Levy wrote: >> On Feb 23, 2013, at 7:36 PM, John Mehr wrote: >> >>> Hello all, >>> I've believe I've made just about all of the progress optimizing svnup >>> as I can and I've just submitted it as a new port. With my ~ 350kb/s >>> DSL connection, it now takes just under 30 minutes to download a fresh >>> base/releng/8.3 tree using svnup (Subversion's svn takes approximately >>> 12 minutes). Incremental updates, such as tracking one of the stable >>> branches takes only 2-3 minutes. >>> For anyone that wants to preview the port before it gets added to the >>> ports tree (assuming I got the send-pr correct), the tarball is located >>> at: >>> http://jcm.dsl.visi.com/freebsd/svnup/svnup-0.5.tar.xz >>> Please let me know if you find any issues. >> >> If anyone has any info about sunup(1) making it's way into base, please tell >> me so I can kill this page: >> >> https://wiki.freebsd.org/UsersFetchingSource >> >> (After trying to catch up on the relevant lists, I just updated that 'status >> page' on the FreeBSD wiki.) >> >> -- >> John, this is spectacular- thank you! >> >> Rocket- >> .ike > > Cool. > > The link to svnup above is stale however, now at 0.56. Best use the > link (as on your wiki page) of http://jcm.dsl.visi.com/freebsd/svnup/ > and go from there. > > Also, I wouldn't be in a hurry to kill that wiki page, lots of useful > info still there, even when it becomes only for historical reference. > > cheers, Ian Thanks Ian, makes sense. I already had the base URL in there- but you're right that the thread URL to this post yields a confusing download (that tarball no longer exists). To avoid confusion, yet leave breadcrumbs to get back to this thread, I changed the link thread to refer to John Mehr's original post to list. Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amdtemp does not find my CPU.
On Mar 15, 2013, at 3:16 PM, Jim Ohlstein wrote: > On 3/15/13 12:15 PM, Zoran Kolic wrote: >> After I installed 9.1 amd64 on node with amd 8120, >> I was not able to read temperatures out of the box. >> I fetched source for head module and compiled. And >> loaded module. Still nothing. I assume my cpu is >> a bit different. >> Best regards > > The module from head "works" for me with an 8120 on 9.1 stable (r247893) > though the results are inconsistent. I am not certain of how useful they > are. > > # sysctl hw.model > hw.model: AMD FX(tm)-8120 Eight-Core Processor > > # kldstat | grep amd > 51 0x8183e000 1043 amdtemp.ko > > # sysctl -a | grep dev.amdtemp > dev.amdtemp.0.%desc: AMD CPU On-Die Thermal Sensors > dev.amdtemp.0.%driver: amdtemp > dev.amdtemp.0.%parent: hostb4 > dev.amdtemp.0.sensor_offset: 0 > dev.amdtemp.0.core0.sensor0: 47.7C > > > Here are results taken at 0.1 second intervals using a shell script: > > dev.amdtemp.0.core0.sensor0: 42.1C > dev.amdtemp.0.core0.sensor0: 42.2C > dev.amdtemp.0.core0.sensor0: 42.0C > dev.amdtemp.0.core0.sensor0: 42.1C > dev.amdtemp.0.core0.sensor0: 41.8C > dev.amdtemp.0.core0.sensor0: 41.7C > dev.amdtemp.0.core0.sensor0: 51.1C > dev.amdtemp.0.core0.sensor0: 51.0C > dev.amdtemp.0.core0.sensor0: 50.7C > dev.amdtemp.0.core0.sensor0: 50.5C > dev.amdtemp.0.core0.sensor0: 50.1C > dev.amdtemp.0.core0.sensor0: 49.8C > dev.amdtemp.0.core0.sensor0: 49.5C > dev.amdtemp.0.core0.sensor0: 49.2C > dev.amdtemp.0.core0.sensor0: 49.2C > > > and again: > > dev.amdtemp.0.core0.sensor0: 41.5C > dev.amdtemp.0.core0.sensor0: 41.2C > dev.amdtemp.0.core0.sensor0: 40.8C > dev.amdtemp.0.core0.sensor0: 40.8C > dev.amdtemp.0.core0.sensor0: 41.0C > dev.amdtemp.0.core0.sensor0: 41.3C > dev.amdtemp.0.core0.sensor0: 41.6C > dev.amdtemp.0.core0.sensor0: 41.3C > dev.amdtemp.0.core0.sensor0: 54.0C > dev.amdtemp.0.core0.sensor0: 53.7C > dev.amdtemp.0.core0.sensor0: 53.3C > dev.amdtemp.0.core0.sensor0: 53.1C > dev.amdtemp.0.core0.sensor0: 52.7C > dev.amdtemp.0.core0.sensor0: 52.3C > dev.amdtemp.0.core0.sensor0: 52.1C > dev.amdtemp.0.core0.sensor0: 51.7C > dev.amdtemp.0.core0.sensor0: 51.5C > > You can see during each series there are sudden increases of over 9C and > almost 13C respectively. > > The same effect is seen if I track any of the individual cores with > "dev.cpu.[0-7].temperature". Here's an example with a 9C jump in 0.1 second. > > dev.cpu.3.temperature: 41.5C > dev.cpu.3.temperature: 41.5C > dev.cpu.3.temperature: 41.7C > dev.cpu.3.temperature: 41.7C > dev.cpu.3.temperature: 41.3C > dev.cpu.3.temperature: 41.0C > dev.cpu.3.temperature: 40.7C > dev.cpu.3.temperature: 49.8C > dev.cpu.3.temperature: 49.5C > dev.cpu.3.temperature: 49.2C > dev.cpu.3.temperature: 48.8C > dev.cpu.3.temperature: 48.6C > dev.cpu.3.temperature: 48.2C > dev.cpu.3.temperature: 48.0C > > I don't have hands on access to this box as it's in a datacenter 1000 > miles from me, but the techs there had a look and all "seems to be OK". I get the same problem as Zoran's original post. My issue, after enabling the kernel module in loader.conf and rebooting, I don't see the temperature sysctl values. Fresh 9.1-REL, amd64 (ISO Image, not yet updated from 9.1-REL head) AMD A8-5500 CPU, full dmesg can be found here: http://www.nycbug.org/?action=dmesgd&dmesgid=2450 I was thinking of compiling-in "device amdtemp" this weekend- anyone know of anything else I can do to help provide a clear and easily reproducible test case? Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amdtemp does not find my CPU.
On Mar 15, 2013, at 3:30 PM, Isaac (.ike) Levy wrote: > I get the same problem as Zoran's original post. On Mar 13, 2013, at 6:45 AM, Peter Ankerstål wrote: > On 03/13/2013 11:16 AM, Milan Obuch wrote: > >> >> you need to try amdtemp.c from CURRENT aka HEAD. I did it for both >> E-350 and C-60 CPU and it works for me. If you need something more to >> test it, I can help, but it is really easy. >> >> Regards, >> Milan >> > > Thanks! That worked nicely! > > Regards, > Peter Apologies, please disregard my post: I recently started filtering to be sure to read freebsd-stable@, I did not know that stable@ was also aliased to this list. Therefore, I only saw a couple posts, yet missed all the actual thread. Best, .ike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
