cpu errors on laptop

zux · 08-28-2008, 01:58 AM

the laptop works normally but I keep getting these errors in /var/log/messages:

Code:

Aug 28 09:49:56 tofiks logger: ACPI group processor / action CPU0 is not defined
Aug 28 09:49:56 tofiks logger: ACPI group processor / action CPU1 is not defined

also I don't think that it's the same problem but i keep getting these errors in dmesg:

Code:

hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success

janhe · 08-28-2008, 05:25 AM

Quote:

Originally Posted by zux

the laptop works normally but I keep getting these errors in /var/log/messages:

Code:

Aug 28 09:49:56 tofiks logger: ACPI group processor / action CPU0 is not defined
Aug 28 09:49:56 tofiks logger: ACPI group processor / action CPU1 is not defined

Your system sends ACPI events about your processors to the acpi handler. The handler doesn't know what to do with them, and gives that message in /var/log/messages. If you aren't missing any features you want to have, you can ignore them.

Quote:

Originally Posted by zux

also I don't think that it's the same problem but i keep getting these errors in dmesg:

Code:

hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success

I've been googling a bit, and there seems quite a lot of info about it. (also on this forum!) Try searching for

Code:

no DRQ after issuing MULTWRITE_EXT

and look if there's something that might help you.

If you find something that you don't understand, you can always come back and ask another (more specific) question.

zux · 08-31-2008, 12:30 PM

hmm, just a moment ago my /var/log/messages was 1,3 GB
full with messages about CPU

maybe someone knows a good how to about ACPI.
I'm also interested in other stuff about acpi so a good howto would be great

first of all i want to get rid of those CPU messages filling my logs

keefaz · 08-31-2008, 12:46 PM

Maybe look in the /etc/acpi/acpi_handler.sh script

Code:

case "$1" in
  button)
    case "$2" in
      power) /sbin/init 0
         ;;
      *) logger "ACPI action $2 is not defined"
         ;;
    esac
    ;;
  *)
    logger "ACPI group $1 / action $2 is not defined"
    ;;
esac

You can do a quick hack to block errors filling the /var/log/messages, like

Code:

case "$1" in
  button)
    case "$2" in
      power) /sbin/init 0
         ;;
      *) logger "ACPI action $2 is not defined"
         ;;
    esac
    ;;
  processor) 
    case "$2" in
      CPU0) # do nothing
      ;;
      CPU1) # do nothing
      ;;
    esac
    ;;
  *)
    logger "ACPI group $1 / action $2 is not defined"
    ;;
esac

But it could be more interesting to investigate what process sends the CPU0 and CPU1 command to this script