Date: Fri, 20 Apr 2007 15:09:03 +0100 From: Thomas Sparrevohn <Thomas.Sparrevohn@btinternet.com> To: freebsd-acpi@freebsd.org Subject: Re: Allocations Errors Message-ID: <200704201509.04361.Thomas.Sparrevohn@btinternet.com> In-Reply-To: <007d01c7829d$7e2615d0$7a724170$@Sparrevohn@btinternet.com> References: <200704191141.23799.Thomas.Sparrevohn@btinternet.com> <200704191125.26484.jhb@freebsd.org> <007d01c7829d$7e2615d0$7a724170$@Sparrevohn@btinternet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 19 April 2007 17:12:12 Thomas Sparrevohn wrote: > On current - Cvsup today - I try > > > > On recent current? Try disabling the 'ram0' device > > via 'hint.ram.0.disabled=1' > > After a more systematic testing it looks like Disabling nvidia.ko is a prereq for anthing to work - Its a well know problem All tests was conducted with setting hw.acpi.osname="Windows 2001" S1 State Testing S1 state - S1 state seems to work apart from the video card not turning off when the system enters S1 state pressing the "wakeup/power combined" button brings the system back to life but it blanks out the monitor Visual identification on the power/sleep button shows S1 - e.g Blinks faster than S3 Halting the system with S5 actually shuts off the system Tested with hw.acpi.reset_video but it did no make any difference S3 State Testing S3 state - System enters S3 state with no other logged messages than Apr 20 13:48:22 w2fzz0vc03 kernel: ACPI set debug layer 'ACPI_ALL_COMPONENTS ACP I_ALL_DRIVERS' level 'ACPI_LV_VERBOSE' Apr 20 13:50:00 w2fzz0vc03 acpi: suspend at 20070420 13:50:00 Pressing the power/wakeup button reboots the system with no additional log messages I single short depression of the power button immediate initiates S5 state rather than S3 no matter how short the depression is Visual indicators shows S3 state "slow" blink S3 state leaves the disks in dirty state S5 State acpiconf -s 5 initiates shutdown but never actually powerdown the system - however mostly after a S1 state it does enter S5 state Does anybody have any other suggestions for what to do now?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704201509.04361.Thomas.Sparrevohn>