OpenBSD Journal

ACPI Testing for 4.1

Contributed by dwc on from the Your-mom-would-want-you-to-test-this dept.

Marco Peereboom is asking for users to perform full tests of the ACPI code from -current. All outstanding bugs have been fixed and now is the time to prepare for the 4.1 freeze!

Over the last few weeks we made some good progress.  We fixed quite 
a few subtle bugs that were causing some strange behavior in acpi.  
In fact I am virtually out of bug reports at this time so it is time 
for you to do some more testing!

Please update to -current and apply this diff:
Index: GENERIC
===================================================================
RCS file: /cvs/src/sys/arch/i386/conf/GENERIC,v
retrieving revision 1.546
diff -u -p -r1.546 GENERIC
--- GENERIC	22 Jan 2007 19:54:24 -0000	1.546
+++ GENERIC	21 Feb 2007 07:40:56 -0000
@@ -57,20 +57,20 @@ isa0	at gscpcib?
 eisa0	at mainbus0
 pci*	at mainbus0

-#option		ACPIVERBOSE
-#option		ACPI_ENABLE
+option		ACPIVERBOSE
+option		ACPI_ENABLE

-acpi0		at mainbus?	disable
-#acpitimer*	at acpi?
-#acpihpet*	at acpi?
-#acpiac*	at acpi?
-#acpibat*	at acpi?
-#acpibtn*	at acpi?
-#acpicpu*	at acpi?
-#acpidock*	at acpi?
-acpiec*		at acpi?	disable
+acpi0		at mainbus?
+acpitimer*	at acpi?
+acpihpet*	at acpi?
+acpiac*	at acpi?
+acpibat*	at acpi?
+acpibtn*	at acpi?
+acpicpu*	at acpi?
+acpidock*	at acpi?
+acpiec*		at acpi?
 acpiprt*	at acpi?
-#acpitz*	at acpi?
+acpitz*	at acpi?

 option		PCIVERBOSE
 option		EISAVERBOSE

Test acpi and send failure reports to me.  The elements I need in the
failure report are:
1. GENERIC dmesg
2. GENERIC.MP dmesg
3. GENERIC dmesg + acpi
4. GENERIC.MP dmesg + acpi
5. Your dsdt, run: acpidump -o name_of_my_machine.DSDT

tar zip it and send it to me please.

Happy testing.

(Comments are closed)

Comments

  1. By Anonymous Coward (65.243.149.146) on

    I'll have one as soon as I get a chance to figure out how to reproduce it, something to do with switching between AC and battery causing a freeze on an X40.

    Has anyone noticed bogus reporting of physical/available memory right at the start of the dmesg? I think it had something to do with the "revert PAE pmap" that happened a few days ago. My laptop is reporting somewhere around 4TB of ram, but top shows the usual 1GB.

    Comments

    1. By sthen (85.158.44.149) on

      > Has anyone noticed bogus reporting of physical/available memory right at the start of the dmesg? I think it had something to do with the "revert PAE pmap" that happened a few days ago.

      http://www.openbsd.org/cgi-bin/cvsweb.cgi/src/sys/arch/i386/i386/machdep.c, v 1.379

  2. By Anonymous Coward (24.113.149.46) on

    It's important to test this with machines other than laptops too, right?

    Comments

    1. By Brad (brad) on

      > It's important to test this with machines other than laptops too, right?

      Correct.

      Comments

      1. By Anonymous Coward (80.85.151.38) on

        > > It's important to test this with machines other than laptops too, right?

        And what about snapshot? Can I test with it ?(Like "b /bsd.mp -c" and then "enable acpi"?) I just can't set current on my machine, but it is possible to do this test from CD.

        Comments
        1. Comments

          1. By Anonymous Coward (213.120.90.67) on

            > only in a few days. Code just went in.

            Should we test each time we see acpi changes on source-changes or is that too much information?

            Comments

            1. By Marco Peereboom (marco) on http://www.peereboom.us

              > > only in a few days. Code just went in.
              >
              > Should we test each time we see acpi changes on source-changes or is that too much information?

              That might be a little much but don't forget I only care about failure reports; testing it to make sure we broke nothing is obviously useful for the community. I send out these periodicals when we fix some bugs that affect lots of people.

              Comments

              1. By jb (jb) on


                >
                > That might be a little much but don't forget I only care about failure reports; testing it to make sure we broke nothing is obviously useful for the community. I send out these periodicals when we fix some bugs that affect lots of people.


                I've been running a "GENERIC.acpi" kernel for a little while now, with all the "commented out" bits uncommented in GENERIC.

                So far, the main problem I have is bootstrapping with the acpidock* active. The kernel just hangs and does not recover.

                The system is an IBM Thinkpad 600x. I'll gladly send in dmesg output from the hang and a successful boot after doing a boot -c on the fresh kernel to disable the acpidock device.

                Comments

                1. By Andreas (84.166.76.117) on

                  > I've been running a "GENERIC.acpi" kernel for a little while now, with all the "commented out" bits uncommented in GENERIC.

                  > So far, the main problem I have is bootstrapping with the acpidock* active. The kernel just hangs and does not recover.

                  Same for me on my ThinkPad X31. dmesgs with and without acpidock is on its way...

  3. By Anonymous Coward (213.118.134.55) on

    Not doing my Acer Aspire 3004wlmi much good. Performance has degraded quite dramatically - X hangs on startup. Will see if I can get you a dmesg and an acpi dump and whatnot.

    On the bright side - I can now see my CPU temperature in sysctl ;).

  4. By Anonymous Coward (81.57.42.108) on

    Is there among the various OpenBSD live CD projects, one that uses a recent snapshot (or that follow current) ?

    Would be cool to test ACPI on all ours machines (including those with already installed systems).

  5. By Devin Smith (drs) devin@devinsmith.net on

    Testing on current with this patch stops my machine from completing the boot up. I'll try to copy the dmesg by hand soon.

    Comments

    1. By Anonymous Coward (74.13.38.20) on

      > Testing on current with this patch stops my machine from completing the boot up. I'll try to copy the dmesg by hand soon.

      Well, the normal kernel's dmesg would probably be good starting point.

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]