Date: Thu, 9 Jan 2003 03:57:17 -0800 From: David Schultz <dschultz@uclink.Berkeley.EDU> To: Odhiambo Washington <wash@wananchi.com> Cc: FBSD-BLEEDING-EDGE <freebsd-current@FreeBSD.ORG> Subject: Re: update from 4.7 to 5.0 Message-ID: <20030109115717.GA1257@HAL9000.homeunix.com> In-Reply-To: <20030109110335.GA65353@ns2.wananchi.com> References: <20030109110335.GA65353@ns2.wananchi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Odhiambo Washington <wash@wananchi.com>: > The box runs prettier, but I have some output of dmesg that I'd appreciate > some explanation on. I'll mark the portions where I seek some explanation > on the dmesg output itself. The most important one is with USB interfaces, > because they seem to NOT start at all since updating. [...] > acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0% > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Where is that explained? I'd really love to know about it ;) That's just the ACPI driver telling you that your CPU has a reduced power (half speed) mode. My -CURRENT box doesn't support ACPI, but glancing at the code, it looks like the relevant sysctls are hw.acpi.cpu.performance_speed and hw.acpi.cpu.economy_speed. Maybe someone else can point you to some real documentation, if it's written yet. > ad0: 19092MB <ST320413A> [38792/16/63] at ata0-master UDMA100 > ad2: 9771MB <Maxtor 2B010H1> [19854/16/63] at ata1-master UDMA100 > Mounting root from ufs:/dev/ad0s2a > lock order reversal > ^^^^^^^^^^^^^^^^^^ # this is another interesting one I'd love to know about. > > > 1st 0xc1bfb3f8 process lock (process lock) @ /usr/src/sys/kern/kern_descrip.c:2100 > 2nd 0xc1cf3634 filedesc structure (filedesc structure) @ /usr/src/sys/kern/kern_descrip.c:2107 This is a known issue; see arch@, subject ``Need help fixing lock ordering with filedesc, proc and pipe.'' If you do a sysctl at just the wrong time, you could deadlock the system. The probability of this happening is on the order of one in a million, so it shouldn't be a concern to you. The warning is just pointing out that possibility so the problem can be fixed. Note that the fact that you got this warning means that you have WITNESS enabled in your kernel config, which is likely to kill performance. I don't know about the other messages, but I suspect you can safely ignore them as long as nothing is going wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030109115717.GA1257>