Re: [gentoo-user] [OT] Very slow POST process
On 29/11/2023 00:16, Michael wrote: Thanks Dan, will do. I was planning to take it apart soon to replace the HDD with an SSD, so this would be the first thing to check. I expect finding a replacement unit will be difficult. Every Lenovo RTC battery seems to have a different part number. I know laptops are different from desktops, but I think every desktop mobo I've come across uses a 3032 battery. See if you can find out what the standard definition of the lenovo battery is, hopefully they just use internal part numbers for a totally standard item. Cheers, Wol
Re: [gentoo-user] Emerge load again
On Monday, 27 November 2023 15:39:33 GMT Peter Humphreey wrote: > Hello list, > > I still can't see how portage limits the load. Today I'm emerging > libreoffice, and it's spending almost the whole time working with 4 CPU > threads. But: > > $ grep -e '\-j' -e distcc /etc/portage/make.conf > EMERGE_DEFAULT_OPTS="--jobs=18 --load-average=30 --backtrack=200 -- > autounmask=n --keep-going --nospinner" > FEATURES="distcc userfetch buildpkg network-sandbox parallel-install sandbox > userpriv usersandbox" > MAKEOPTS="-j18" > > I found a suggestion to use distcc in the installation handbook, which I > hadn't seen there before, so I went searching for it and found how to do it. > It usually works well, in this case starting 18 packages before starting LO > itself. grep -rw doesn't find '4' anywere relevant under /etc/portage/ . > Other times it just doesn't help at all. > > What am I missing? In absence of other contributions I'll offer a theoretical explanation, based on random observations on my systems. You have specified as many as 18 packages to be emerged in parallel x up to 18 make jobs each. The result of [18 x 18 = 324] is to be limited by a total load average of 30. If there were more than 18 packages listed to be emerged and there were no dependencies between them to restrict how many could start emerging in parallel, you would observe =<18 packages being emerged in parallel. This alone will not breach the load limit of 30. Let's assume all 18 packages had a large codebase to need at least 18 make jobs each. Sooner or later you'd have 18 parallel emerges all trying to run 18 make jobs. Were this to occur the load limit restriction would kick in and you would see only up to 30 jobs listed in top, with individual package processes alternating in the top list of make threads. Here's my hypothesis explaining your own observation with libreoffice. As a package or more finished emerging, libreoffice's turn comes up. Soon libreoffice starts to execute make jobs, but any of the following may apply: 1. There are only 4 out of 30 jobs available, because other packages are already using 26, throughout your window of observation. 2. Libreoffice sequencing of make jobs is mostly linear with succeeding make jobs waiting on output from their predecessors. 3. Libreoffice source code is not optimised for high parallelism - I recall when it was hardcoded at -j1 just a few years ago. Before this restriction was added, any bug reporters were advised to try again after limiting make to -j1. Next time I'm building libreoffice on a beefier system I'll keep an eye out for the number of jobs to see what it gets up to. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Emerge load again
On Wednesday, 29 November 2023 10:26:36 GMT Michael wrote: > Here's my hypothesis explaining your own observation with libreoffice. As a > package or more finished emerging, libreoffice's turn comes up. Soon > libreoffice starts to execute make jobs, but any of the following may > apply: > > 1. There are only 4 out of 30 jobs available, because other packages are > already using 26, throughout your window of observation. Nope. Nothing else in progress. > 2. Libreoffice sequencing of make jobs is mostly linear with succeeding make > jobs waiting on output from their predecessors. That's possible, but it doesn't seem likely with such a huge code base. And why four processes, specifically and consistently? > 3. Libreoffice source code is not optimised for high parallelism - I recall > when it was hardcoded at -j1 just a few years ago. Before this restriction > was added, any bug reporters were advised to try again after limiting make > to -j1. Yes, that was common to many packages for a long time because of incomplete optimisation. > Next time I'm building libreoffice on a beefier system I'll keep an eye out > for the number of jobs to see what it gets up to. That would help, yes. The contribution of distcc isn't clear to me yet, as I said before. Sometimes it's the bee's knees; other times it might just as well not be there. I don't like mysteries... :) -- Regards, Peter.
Re: [gentoo-user] Emerge load again
On Mon, Nov 27, 2023 at 10:39 AM Peter Humphreey wrote:l > > What am I missing? I have much less powerful hardware than you but libreoffice (as a stand-alone build) generates many more threads than 4 on my “cluster”. I’m also using distcc. On the main box, I set MAKEOPTS=“-j17 -l6” On the other two less powerful ones -l is 5 and 3, but -j is the same. On the main box, /etc/distcc/hosts contains localhost/11 sophie/5,lzo tobey/3,lzo —localslots=11 —localslots_cpp=11 On sophie and tobey (my less powerful boxes) the hosts file contains something similar but specific to those boxes. The localslots and localslots_cpp numbers are 3 on tobey and 5 on sophie, and the order in which the machines are mentioned changes (local machine first, then remote machines in order of power). This configuration is the result of a lot of experimentation rather than just a theoretical calculation. The various guides that discuss how to tune these numbers for best performance were modestly helpful in explaining what the tuning parameters mean, but experimenting and watching the resulting performance was the best teacher. Hope this helps. John Blinka
Re: [gentoo-user] Emerge load again
On Wednesday, 29 November 2023 14:12:39 GMT John Blinka wrote: > On Mon, Nov 27, 2023 at 10:39 AM Peter Humphreey > wrote:l > > > What am I missing? > > I have much less powerful hardware than you but libreoffice (as a > stand-alone build) generates many more threads than 4 on my “cluster”. I’m > also using distcc. > > On the main box, I set > MAKEOPTS=“-j17 -l6” > On the other two less powerful ones -l is 5 and 3, but -j is the same. > > On the main box, /etc/distcc/hosts contains > localhost/11 sophie/5,lzo tobey/3,lzo —localslots=11 —localslots_cpp=11 > > On sophie and tobey (my less powerful boxes) the hosts file contains > something similar but specific to those boxes. The localslots and > localslots_cpp numbers are 3 on tobey and 5 on sophie, and the order in > which the machines are mentioned changes (local machine first, then remote > machines in order of power). > > This configuration is the result of a lot of experimentation rather than > just a theoretical calculation. The various guides that discuss how to tune > these numbers for best performance were modestly helpful in explaining what > the tuning parameters mean, but experimenting and watching the resulting > performance was the best teacher. > > Hope this helps. > > John Blinka I don't use distcc, so I can't add anything useful to its application on Peter's requirements, but a quick test by Peter would be to start a single emerge of libreoffice on its own and observe if it is still limited to 4 threads with and without distcc. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Abnormal processor temperature.
Michael, On Tuesday, 2023-11-28 10:13:56 +, you wrote: > ... > I suggested enabling the SPI modules because they are used by the CPU to > communicate with various sensors, adjust clock frequency between components > and thereafter to receive signals a/synchronously to control temperatures. What exactly do you suggest? My kernel (6.1.57) configuration contains: $ grep SPI /usr/src/linux/.config|grep -v SPIN CONFIG_SCSI_SPI_ATTRS=y # CONFIG_SPI is not set # SPI RTC drivers CONFIG_RTC_I2C_AND_SPI=y # SPI and I2C RTC drivers $ I played a little with the "/" and "?" commands of "make menuconfig", activated "CONFIG_SPI" and found a lot of controllers and drivers, but nothing obvious to enable additionally. However, apparently activating "CONFIG_SPI" also activated CONFIG_NET_VENDOR_ADI=y CONFIG_SND_SPI=y CONFIG_SPI_DYNAMIC=y CONFIG_SPI_MASTER=y Is this what you are suggesting? Sincerely, Rainer
Re: [gentoo-user] Re: Abnormal processor temperature.
On Wednesday, 29 November 2023 17:34:48 GMT Dr Rainer Woitok wrote: > Michael, > > On Tuesday, 2023-11-28 10:13:56 +, you wrote: > > ... > > I suggested enabling the SPI modules because they are used by the CPU to > > communicate with various sensors, adjust clock frequency between > > components > > and thereafter to receive signals a/synchronously to control temperatures. > > What exactly do you suggest? My kernel (6.1.57) configuration contains: > >$ grep SPI /usr/src/linux/.config|grep -v SPIN >CONFIG_SCSI_SPI_ATTRS=y ># CONFIG_SPI is not set ># SPI RTC drivers >CONFIG_RTC_I2C_AND_SPI=y ># SPI and I2C RTC drivers >$ > > I played a little with the "/" and "?" commands of "make menuconfig", > activated "CONFIG_SPI" and found a lot of controllers and drivers, but > nothing obvious to enable additionally. However, apparently activating > "CONFIG_SPI" also activated > >CONFIG_NET_VENDOR_ADI=y >CONFIG_SND_SPI=y >CONFIG_SPI_DYNAMIC=y >CONFIG_SPI_MASTER=y > > Is this what you are suggesting? > > Sincerely, > Rainer It depends on the hardware, this is what I have enabled on an AMD MoBo: ~ $ grep SPI /usr/src/linux/.config CONFIG_UNINLINE_SPIN_UNLOCK=y CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_RWSEM_SPIN_ON_OWNER=y CONFIG_LOCK_SPIN_ON_OWNER=y CONFIG_ARCH_USE_QUEUED_SPINLOCKS=y CONFIG_QUEUED_SPINLOCKS=y # CONFIG_INET6_ESPINTCP is not set CONFIG_SCSI_SPI_ATTRS=y CONFIG_SPI=y CONFIG_SPI_MASTER=y # CONFIG_SPI_MEM is not set # SPI Master Controller Drivers # CONFIG_SPI_ALTERA is not set # CONFIG_SPI_AXI_SPI_ENGINE is not set # CONFIG_SPI_BITBANG is not set # CONFIG_SPI_CADENCE is not set # CONFIG_SPI_DESIGNWARE is not set # CONFIG_SPI_NXP_FLEXSPI is not set # CONFIG_SPI_GPIO is not set # CONFIG_SPI_MICROCHIP_CORE is not set # CONFIG_SPI_MICROCHIP_CORE_QSPI is not set # CONFIG_SPI_LANTIQ_SSC is not set # CONFIG_SPI_OC_TINY is not set # CONFIG_SPI_PXA2XX is not set # CONFIG_SPI_ROCKCHIP is not set # CONFIG_SPI_SC18IS602 is not set # CONFIG_SPI_SIFIVE is not set # CONFIG_SPI_MXIC is not set # CONFIG_SPI_XCOMM is not set # CONFIG_SPI_XILINX is not set # CONFIG_SPI_ZYNQMP_GQSPI is not set CONFIG_SPI_AMD=m # SPI Multiplexer support # CONFIG_SPI_MUX is not set # SPI Protocol Masters # CONFIG_SPI_SPIDEV is not set # CONFIG_SPI_LOOPBACK_TEST is not set # CONFIG_SPI_TLE62X0 is not set # CONFIG_SPI_SLAVE is not set CONFIG_SPI_DYNAMIC=y # SPI GPIO expanders # end of SPI GPIO expanders # CONFIG_SENSORS_LTC2947_SPI is not set # CONFIG_MFD_DA9052_SPI is not set # CONFIG_MFD_MC13XXX_SPI is not set # CONFIG_MFD_TPS65912_SPI is not set # CONFIG_MFD_ARIZONA_SPI is not set # CONFIG_MFD_WM831X_SPI is not set # CONFIG_SND_SPI is not set # SPI RTC drivers CONFIG_RTC_I2C_AND_SPI=y # SPI and I2C RTC drivers # CONFIG_HWSPINLOCK is not set signature.asc Description: This is a digitally signed message part.
