HEADS UP: ACPI update - thermal management

2001-06-28 Thread Mike Smith
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

booting off multiple disks

2001-06-28 Thread Jeff Fellin
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:

Re: HEADS UP: ACPI update - thermal management

2001-06-28 Thread Patrick Guelat
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

Re: booting off multiple disks

2001-06-28 Thread Bernd Walter
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

Kernel panics with debug.witness_watch=0

2001-06-28 Thread Alexander N. Kabaev
-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 @

RE: Kernel panics with debug.witness_watch=0

2001-06-28 Thread John Baldwin
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

Touch pad problem on HP n5470 Laptop

2001-06-28 Thread Edwin Culp
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

Re: Touch pad problem on HP n5470 Laptop

2001-06-28 Thread Manfred Antar
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:

Re: Touch pad problem on HP n5470 Laptop

2001-06-28 Thread Ollivier Robert
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