OpenBSD Journal

ACPI update

Contributed by jj on from the have-acpi-will-test dept.

Great headway is now being made with ACPI but with some interrupt issues still lurking, it is important that you help test the ACPI code.
Marco Peereboom (marco@) writes...
Jordan just fixed a bug that affects several people that have experienced interrupt issues when enabling ACPI.
If you are one of the people that have experienced hangs or other undesired results after enabling ACPI in UKC please take this fix for a test drive.
The steps to test this fix are:
1. Check out a brand new kernel
2. Compile GENERIC and GENERIC.MP
3. Boot GENERIC with the -c option and enable acpi; assuming your new kernel is /bsd.acpi do the following:
	boot> bsd.acpi -c
	... dmesg goo...
	UKC> enable acpi
	385 acpi0 enabled
	quit
4. Repeat with GENERIC.MP
5. If you run into issues send jordan, kettenis & marco the dmesg and the dmesg with acpi enabled.

We think that there is at least one more bug in aml that we are trying to fix and this will help narrowing it down.

Thanks and happy testing.
/marco

(Comments are closed)

Comments

  1. By Nick (130.76.96.19) on http://thatoneguynick.is-a-geek.org

    I really appreciate all the hardwork. Can't wait to see the laptop support make it into the kernel.

    Comments

    1. By sthen (85.158.44.149) on

      > I really appreciate all the hardwork. Can't wait to see the laptop support make it into the kernel.

      ACPI isn't just for laptops, this needs testing on other systems too. One major thing handled by ACPI is interrupt routing and... well... it's something you want working correctly.

  2. By Yozo (221.16.18.165) on

    I'm using the current on Sony Vaio U101, ACPI stuff enabled.
    It works well, with acpiec enabled, sysctl shows acpi related variables and power button can shutdown the PC.
    I wonder if I can do other things...

    Comments

    1. By David (206.57.90.233) ryuuritekkaman@yahoo.com on beap-cf.org

      > I'm using the current on Sony Vaio U101, ACPI stuff enabled.
      > It works well, with acpiec enabled, sysctl shows acpi related variables and power button can shutdown the PC.
      > I wonder if I can do other things...
      >
      This is actually a comment/question directed at Zou. I was wondering (since I couldn't find an entry for your Sony Vaoi U101 on
      http://www.openbsd.org/i386-laptop.html ) - how well does your laptop work under OpenBSD in other areas like audio support, networking support (wired and wireless), usb support, etc... ? I'm mainly asking because my current laptop is dying and will probably need to get another one sometime soon.

      Comments

      1. By David (132.170.51.231) ryuuritekkaman@yahoo.com on

        > > I'm using the current on Sony Vaio U101, ACPI stuff enabled.
        > > It works well, with acpiec enabled, sysctl shows acpi related variables and power button can shutdown the PC.
        > > I wonder if I can do other things...
        > >
        > This is actually a comment/question directed at Zou. I was wondering (since I couldn't find an entry for your Sony Vaoi U101 on
        > http://www.openbsd.org/i386-laptop.html ) - how well does your laptop work under OpenBSD in other areas like audio support, networking support (wired and wireless), usb support, etc... ? I'm mainly asking because my current laptop is dying and will probably need to get another one sometime soon.
        >
        >

        I'm so sorry I meant Yozo not Zou (one of the professors at my university, heh).

        Comments

        1. By Yozo (221.16.18.165) on

          VAIO U101 is a sort of "old" model now.
          Sony's page http://www.vaio.sony.co.jp/Products/PCG-U101/ (in Japanese).
          wireless(prism3) and wired(intel pro/100) networking works, USB(intel 82801DB) works.
          I don't try audio(intel 82801DB AC97) and IEEE1394 yet.
          I'll send the dmesg to www@ later (-:

  3. By Anonymous Coward (62.252.32.12) on

    I'm assuming I can't just check out the -current kernel without checking out the rest of the system?

    Anyway, if I did this, what sort of things would I be looking for? Performance issues? Big warnings and errors all over my console? System instability? I'm a user, not a coder, so I really don't know what I'd be looking for ..

    Comments

    1. By Anonymous Coward (219.90.242.204) on

      > I'm assuming I can't just check out the -current kernel without checking out the rest of the system?

      Why ever not?
      Just update to a current snapshot, cvs up your src/sys directory, rebuild.


      >
      > Anyway, if I did this, what sort of things would I be looking for? Performance issues? Big warnings and errors all over my console? System instability? I'm a user, not a coder, so I really don't know what I'd be looking for ..

      System not booting would be an obvious first. Also check that all your devices work with the new interrupt routing stuff. Do you have new sensors? Have old ones disappeared?

    2. By sthen (85.158.44.155) on

      > I'm assuming I can't just check out the -current kernel without checking out the rest of the system? Depends what devices you have (/etc/firmware is now in network byte-order) and other things (istr a pfctl/kernel mismatch along the way). ftp a new bsd.rd, boot from it, upgrade to a snapshot, boot -c, enable acpi, quit, test... > Anyway, if I did this, what sort of things would I be looking for? Performance issues? Big warnings and errors all over my console? System instability? I'm a user, not a coder, so I really don't know what I'd be looking for .. bad performance, panics/hangs, network packet loss, high idle cpu, ...

      Comments

      1. By sthen (85.158.44.155) on

        (ugh, sorry about the formatting of that post).

      2. By Anonymous Coward (62.252.32.12) on

        > > I'm assuming I can't just check out the -current kernel without checking out the rest of the system?
        >
        > Depends what devices you have (/etc/firmware is now in network byte-order) and other things (istr a pfctl/kernel mismatch along the way). ftp a new bsd.rd, boot from it, upgrade to a snapshot, boot -c, enable acpi, quit, test...
        >
        > > Anyway, if I did this, what sort of things would I be looking for? Performance issues? Big warnings and errors all over my console? System instability? I'm a user, not a coder, so I really don't know what I'd be looking for ..
        >
        > bad performance, panics/hangs, network packet loss, high idle cpu, ...

        Well, I'm using ACPI right now on my acer 3004wlmi, and everything seems to work as before. No performance issues, no panics or anything of the sort. In fact, if anything I'd say things are going a bit faster..but that might well be because the network is a bit quieter at the moment.

        However, no sensors are being detected. Not sure if they are when acpi is off though, will check that out after the next reboot. If I don't reply and kick up a fuss then you can safely assume that it makes no difference :P

        Comments

        1. By Yozo (221.16.18.165) on

          > However, no sensors are being detected.

          you should enable both acpi and acpiec.
          the two devices are defined but disabled in GENERIC.

          Comments

          1. By Anonymous Coward (62.252.32.12) on

            > > However, no sensors are being detected.
            >
            > you should enable both acpi and acpiec.
            > the two devices are defined but disabled in GENERIC.
            >

            Doesn't seem to make a difference :/. No big deal, though.

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.]