http://bugzilla.kernel.org/show_bug.cgi?id=6049





------- Additional Comments From [EMAIL PROTECTED]  2006-02-14 09:43 -------
> Why is pci=noacpi being used?

My system booted for kernels <= v2.6.15 either with "acpi=off" or
"noapic" or "pci=noacpi". Boot option "noapic" made problems with
suspend-to-RAM, so I took "pci=noacpi". Now, I after much testing those
problems turned out to be a simple missconfiguration of acpid's
button/power event handler:

When booting in IOAPIC mode either together with pci=nacpi or or not I
did *not* get right after transition from suspend-to-RAM to
On-power-state a "button/power" event. So I had no problem with the
simple button/power-handler

  [EMAIL PROTECTED]:~$ cat /etc/acpi/actions/my_powerbtn.sh
  #!/bin/sh
  echo mem > /sys/power/state

But with "noapic" no matter if I have "pci=noacpi" or not I *do* get a
"button/power" event right after resuming from supend-to-ram (by
touching my powerbutton) and so my system got back in S3-State...

No I use the improved better handler

  [EMAIL PROTECTED]:~$ cat /etc/acpi/actions/my_powerbtn.sh
  #!/bin/sh
  # suspend to mem (S3, "mem") on button/power acpi event
  POWERBTN="/var/run/powerbtn.eid"

  suspend_to_mem() {
      echo $eid > $POWERBTN
      echo mem > /sys/power/state
  }
  # event arguments "%e" look like
  # button/power PWRF 00000080 0000002e
  eid=$(printf "%u\n" 0x${4}) # simple hexadecimal to integer conversion

  if [ -f "$POWERBTN" ]
  then
        # catch and ignore button/power event on transition to power-on state
        read oeid < "$POWERBTN"
        if [ $(($eid - $oeid )) -ne 1 ]; then
                suspend_to_mem
        fi
  else
        suspend_to_mem
  fi

and all works fine with noapic.

> I expect if you boot with "pci=noacpi" and "noapic"
> together, then this system will work no matter
> how the EC is set up, yes?

You are right. System boots. Interrupt increases. button/power and
button/lid events are all right. So no problem with EC for me any more.
Thank you very much!!!

But my system now works just with option "noapic" fine and video-console
resumes better with "acpi_sleep=s3_bios". So I do not use ec_intr=0 or
pci=noacpi any more. I think in general it' s better to use ACPI for IRQ
routing, yes? 

I think this bug is resolved? But better you will decide that. Any chance 
that users won't have to experiment with incomprehensible boot options in 
the future?

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to