HEADS UP: ACPI update - thermal management
This is just a heads-up to let folks know that I've committed some early code to handle thermal management under ACPI. This should DTRT with active cooling (fans, etc.). It won't help with passive cooling yet (we need to sort out the processor device control first), and it may well have problems (there are places where the specification is vague about what should be in the namespace and my ability to test these options is limited). Testing and feedback would be welcome. I'll try to get the new ACPI CA stuff merged tomorrow, unless there are too many people bugging me at Usenix. 8) Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
booting off multiple disks
I have a system that I need to boot either stable or current, each with it's own root filesystem. I am having problems with the configuration of the system on the second drive, in that the kernel (current) loads and boots, but it is using the root filesystem of stable. My configuration is: Jun 28 08:39:29 /boot/kernel/kernel: isa0: ISA bus on isab0 Jun 28 08:39:29 /boot/kernel/kernel: atapci0: Intel PIIX4 ATA33 control ler port 0x3460-0x346f at device 18.1 on pci0 Jun 28 08:39:29 /boot/kernel/kernel: ata0: at 0x1f0 irq 14 on atapci0 Jun 28 08:39:29 /boot/kernel/kernel: ata1: at 0x170 irq 15 on atapci0 snip Jun 28 08:39:30 /boot/kernel/kernel: ad0: DMA limited to UDMA33, non-ATA 66 compliant cable Jun 28 08:39:30 /boot/kernel/kernel: ad0: 28629MB QUANTUM FIREBALLP LM3 0 [58168/16/63] at ata0-master UDMA33 Jun 28 08:39:30 /boot/kernel/kernel: ad2: 8063MB IBM-DHEA-38451 [16383 /16/63] at ata1-master UDMA33 snip Jun 28 08:39:30 /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s1a I had switch the values of ata.0 and ata.1 in /boot/device.hints, but it didn't make any difference. Simply put I have stable on ad0 and current on ad2, and when I boot a kernel from a drive I want the root filesystem to be on the drive. Can anyone point me to any man pages that might explain(hint) at how to accomplish this? Thank you in advance. Jeff Fellin Bell Labs, Murray Hill, NJ (908) 582-7673 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: ACPI update - thermal management
On Wed, 27 Jun 2001, Mike Smith wrote: This is just a heads-up to let folks know that I've committed some early code to handle thermal management under ACPI. This should DTRT with active cooling (fans, etc.). It won't help with passive cooling yet (we need to sort out the processor device control first), and it may well have problems (there are places where the specification is vague about what should be in the namespace and my ability to test these options is limited). If you want people to test this they should be able to compile it ;-) I suggest you add the missing 'dev/acpica/acpi_powerres.c optional acpica' to sys/conf/files Regards Patrick -- Patrick Guelat, ImproWare AG Network Services, CH-4133 Pratteln Mail: [EMAIL PROTECTED] - Phone: +41 61 826 93 00 (ext: 13) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: booting off multiple disks
On Thu, Jun 28, 2001 at 10:29:18AM -0400, Jeff Fellin wrote: I have a system that I need to boot either stable or current, each with it's own root filesystem. I am having problems with the configuration of the system on the second drive, in that the kernel (current) loads and boots, but it is using the root filesystem of stable. You should check the fstab entry from your -current. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Kernel panics with debug.witness_watch=0
-CURRENT kernel panics when booting with debug.witness_watch tunable set to 0 in loader. It looks like witness_assert function should not do anything in this case. Attached patch fixes the problem for me. The panic I am getting looks like that: panic: Lock (sx) fork list not locked @ ../../kern/kern_fork.c:590. Debugger(panic) Stopped at Debugger+0x44: pushl %ebx db trace Debugger(c034ff7b) at Debugger+0x44 panic(c0353360,c0350540,c034da0e,c034da2a,24e) at panic+0x70 witness_assert(c03e3c00,2,c034da2a,24e,0) at witness_assert+0x9f _sx_sunlock(c03e3c00,c034da2a,24e,c03c7c30,c0b3dad0) at _sx_sunlock+0x8e fork1(c0426e00,20014,c0426de0) at fork1+0x1c6a create_init(0,4eec00,4ee000,0,c012f0b2) at create_init+0x18 mi_startup() at mi_startup+0x90 begin() at begin+0x29 db The patch: Index: subr_witness.c === RCS file: /usr/ncvs/src/sys/kern/subr_witness.c,v retrieving revision 1.77 diff -u -r1.77 subr_witness.c --- subr_witness.c 2001/06/27 06:27:29 1.77 +++ subr_witness.c 2001/06/28 20:27:57 @@ -1351,6 +1351,9 @@ #ifdef INVARIANT_SUPPORT struct lock_instance *instance; + if (lock-lo_witness == NULL || witness_dead) + return; + if ((lock-lo_class-lc_flags LC_SLEEPLOCK) != 0) instance = find_instance(curproc-p_sleeplocks, lock); else if ((lock-lo_class-lc_flags LC_SPINLOCK) != 0) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Kernel panics with debug.witness_watch=0
On 28-Jun-01 Alexander N. Kabaev wrote: -CURRENT kernel panics when booting with debug.witness_watch tunable set to 0 in loader. It looks like witness_assert function should not do anything in this case. Attached patch fixes the problem for me. Ok. Committed, thanks. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Touch pad problem on HP n5470 Laptop
I can't get the mouse working on a new HP Pavilion 5470 laptop. I just installed and cvsuped, made world and get this in my dmesg. It's my guess that the second atkbd0/psm1 are the problem. Does anyone have an idea what I should do? atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 atkbd1: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd1 at atkbd1 psm1: unable to allocate the IRQ resource (12). The BIOS has an auto/both option for the touch pad and/or an external mouse. Unfortunately there is no touch pad only option. Thanks, ed --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Touch pad problem on HP n5470 Laptop
At 09:31 PM 6/28/2001 -0700, Edwin Culp wrote: I can't get the mouse working on a new HP Pavilion 5470 laptop. I just installed and cvsuped, made world and get this in my dmesg. It's my guess that the second atkbd0/psm1 are the problem. Does anyone have an idea what I should do? atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 atkbd1: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd1 at atkbd1 psm1: unable to allocate the IRQ resource (12). The BIOS has an auto/both option for the touch pad and/or an external mouse. Unfortunately there is no touch pad only option. Thanks, ed I'm have the same problem on a dual pentium pro machine. Intel PR440FX Something has changed in the psm code. I must admit today was the first time I tried using the mouse. I mostly access this machine over the network or com port, so I can't say when this started. I don't remember ever seeing reference to psm1 I only have 1 mouse on this machine and there is only 1 in the kernel config file. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Touch pad problem on HP n5470 Laptop
According to Manfred Antar: this started. I don't remember ever seeing reference to psm1 I only have 1 mouse on this machine and there is only 1 in the kernel config file. Re-read messages in -current a few weeks ago, the problem was mentionned and the solution was too. Remove the atkbd and psm hints from either /boot/device.hints or in your kernel config file. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
