Re: update from 4.7 to 5.0
Thus spake Terry Lambert <[EMAIL PROTECTED]>: > David Schultz wrote: > > Thus spake Odhiambo Washington <[EMAIL PROTECTED]>: > > > 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. > > Can I vote for replacing "enabled" with "available", so it does > not look like it's being turned on on you, so that you have to > post to this mailing list asking about it, in the future? I second that. The message caused me a double-take the first time I saw it, too. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: update from 4.7 to 5.0
On Thu, Jan 09, 2003 at 12:17:49PM -0800, Terry Lambert wrote: > David Schultz wrote: > > Thus spake Odhiambo Washington <[EMAIL PROTECTED]>: > > > 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. > > Can I vote for replacing "enabled" with "available", so it does > not look like it's being turned on on you, so that you have to > post to this mailing list asking about it, in the future? I think what's needed is some good documentation about CPU throttling, because people are intrigued when they see it, and wonder what it does and how you tune it. I know I was surprised when, for the first time ever, I was told I could throttle my Athlon XP - I didn't even know it could be. I know it's fairly experimental, but I think this feature needs better documentation and development - for example, at the moment it's possible to set the economy_mode value to 0, which shouldn't be allowed. Other than that, it's a fantastic ACPI implementation, I'd say it's the best of any OS! -- Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: update from 4.7 to 5.0
David Schultz wrote: > Thus spake Odhiambo Washington <[EMAIL PROTECTED]>: > > 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. Can I vote for replacing "enabled" with "available", so it does not look like it's being turned on on you, so that you have to post to this mailing list asking about it, in the future? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: update from 4.7 to 5.0
* David Schultz <[EMAIL PROTECTED]> [20030109 14:56]: wrote: Hi David, Thank you for a fast response. > > 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 am going to compile a kernel with the WITNESS stuff disabled. I have rcvd 3 responses and none of them tell me about my USB interfaces. I hope this does not mean that my mobo has issues with 5.0 ;) -Wash -- Odhiambo Washington <[EMAIL PROTECTED]> "The box said 'Requires Wananchi Online Ltd. www.wananchi.com Windows 95, NT, or better,' Tel: +254 2 313985-9 +254 2 313922 so I installed FreeBSD." GSM: +254 72 743223 +254 733 744121 This sig is McQ! :-) The brain is a wonderful organ; it starts working the moment you get up in the morning, and does not stop until you get to school. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: update from 4.7 to 5.0
Thus spake Odhiambo Washington <[EMAIL PROTECTED]>: > 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 [38792/16/63] at ata0-master UDMA100 > ad2: 9771MB [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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: update from 4.7 to 5.0
In message <[EMAIL PROTECTED]>, Odhiambo Washington wrote : >acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0% > > >Where is that explained? I'd really love to know about it ;) Don't worry. This is do with ACPI CPU power management feature. Your machine is capable to change speed in two step. 1.5G/750MHz This value can also be reffered as hw.acpi.cpu.max_speed sysctl value. you can change the speed by changing hw.acpi.cpu.performance_speed sysctl value. (Your machine is desktop system, don't you?) Where is that explained? Here, or /sys/dev/acpica/acpi_cpu.c ;-) ..There are lack of document especially in sysctl value for ACPI. Regards. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
update from 4.7 to 5.0
Hello Gurus, I am not a developer so I beg to be excused if I ask anything stupid. I updated from 4.7 to 5.0 on a test machine just to get the feel of the upcoming 5.0-RELEASE. I used cvsup and so my box is 5.0-CIRRENT. I fear that term - CURRENT. Anyway, I managed a successfull update but I guess there are some gotchas that I never saw. 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. - - b e g i n d m e s g - - Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Thu Jan 9 12:03:06 EAT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/Kern5.x Preloaded elf kernel "/boot/kernel/kernel" at 0xc0618000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06180a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1699959576 Hz CPU: Pentium 4 (1699.96-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf12 Stepping = 2 Features=0x3febf9ff real memory = 335478784 (319 MB) avail memory = 318328832 (303 MB) Initializing GEOMetry subsystem netsmb_dev: loaded Pentium Pro MTRR support enabled VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc052b082 (122) VESA: ATI RAGE128 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 6 entries at 0xc00fdec0 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz unknown: I/O range not supported ^ # what could this be??? acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 pcib0: port 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xd000-0xd7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcm0: port 0xd000-0xd03f irq 11 at device 9.0 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd400-0xd47f mem 0xdf101000-0xdf10107f irq 5 at device 11.0 on pci0 xl0: Ethernet address: 00:50:da:39:d8:2f miibus0: on xl0 bmtphy0: <3c905B 10/100 internal PHY> on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: port 0xd800-0xd81f mem 0xdf00-0xdf0f,0xdf10-0xdf100fff irq 10 at device 12.0 on pci0 fxp0: Ethernet address 00:08:c7:fb:05:c2 inphy0: on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0xdc00-0xdc0f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xe000-0xe01f irq 5 at device 17.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 ^^ # these faile, yes? Maybe there is # something I missed in the kernel?? # How can I fix this? uhci1: port 0xe400-0xe41f irq 5 at device 17.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 ^^ # that too failed... uhci2: port 0xe800-0xe81f irq 5 at device 17.4 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhub2: port error, restarting port 1 uhub2: port error, giving up port 1 uhub2: port error, restarting port 2 uhub2: port error, giving up port 2 ^^^ # that too failed. pcm1: port 0xec00-0xecff irq 10 at device 17.5 on pci0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 p
