From owner-acpi-jp@jp.FreeBSD.org Thu Aug 21 22:30:55 2003
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id h7LDUti14972;
	Thu, 21 Aug 2003 22:30:55 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from hermes.nixsys.be (postfix@hermes.nixsys.be [2001:ab8:2007:0:20c:6eff:fe4b:23f])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with ESMTP/inet6 id h7LDUr014966
	for <acpi-jp@jp.freebsd.org>; Thu, 21 Aug 2003 22:30:54 +0900 (JST)
	(envelope-from philip@nixsys.be)
Received: by hermes.nixsys.be (Postfix, from userid 1001)
	id BBA9151; Thu, 21 Aug 2003 15:30:51 +0200 (CEST)
From: Philip Paeps <philip+freebsd@paeps.cx>
To: acpi-jp@jp.FreeBSD.org
Message-ID: <20030821133049.GB654@hermes.nixsys.be>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
X-Date-in-Rome: ante diem XII Kalendas Septembres MMDCCLVI ab Urbe Condida
X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879
X-Message-Flag: Get a proper mailclient!  Mutt: <http://www.mutt.org/>
User-Agent: Mutt/1.5.4i
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Thu, 21 Aug 2003 15:30:51 +0200
X-Sequence: acpi-jp 2604
Subject: [acpi-jp 2604] Asus L3H notebook issues
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: philip+freebsd@paeps.cx
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+030821

Hi guys!

I have an Asus L3500H notebook on which I've installed FreeBSD-CURRENT.  Most
things are working rather well, as I expected, but there are some ACPI issues
bothering me.  Perhaps someone can help me :-)

When the machine goes into S1, either by pressing the button or closing the
lid, the screen doesn't completely turn off, rather I get a random number
(between none and a screenfull) of vertical lines all over it.  Disabling ACPI
and just closing the lid blanks the screen properly.  Additionally, when
entering S1, I get this message from the kernel:

  Aug 21 13:19:33 hermes kernel: fwohci0: fwohci_pci_suspend

I can only return from S1 by pressing the power button.  I don't know if
that's normal, I thought I could just press any old key?  That's a minor issue
though.  When I return from S1, everything appears to work fine, but I get the
following messages from the kernel:

  Aug 21 13:19:33 hermes kernel: ata0: resetting devices ..
  Aug 21 13:19:33 hermes kernel: usb0: 1 scheduling overruns
  Aug 21 13:19:33 hermes kernel: usb1: 1 scheduling overruns
  Aug 21 13:19:33 hermes kernel: usb2: 1 scheduling overruns
  Aug 21 13:19:33 hermes kernel: done
  Aug 21 13:19:33 hermes kernel: ata1: resetting devices ..
  Aug 21 13:19:34 hermes kernel: done
  Aug 21 13:19:34 hermes kernel: fwohci0: fwohci_pci_resume: power_state = 0x00000000
  Aug 21 13:19:34 hermes kernel: fwohci0: Phy 1394a available S400, 2 ports.
  Aug 21 13:19:34 hermes kernel: fwohci0: Link S400, max_rec 2048 bytes.
  Aug 21 13:19:34 hermes kernel: fwohci0: Initiate bus reset
  Aug 21 13:19:34 hermes kernel: fwohci0: BUS reset
  Aug 21 13:19:34 hermes kernel: fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode
  Aug 21 13:19:34 hermes kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
  Aug 21 13:19:34 hermes kernel: firewire0: bus manager 0 (me)
  Aug 21 13:19:34 hermes kernel: fwohci0: unrecoverable error

Is that something to worry about, or is that just 'normal'?  I don't like the
sound of the unrecoverable error bit too much.

Some relevant details (dmesg, kernel config, acpidump) are at:

  <http://www.paeps.cx/~philip/acpi/>

Trying to compile the asl with iasl gives quite a few errors.  There's some
information about them on Google, but not nearly enough for me to fix them,
and I don't trust myself fiddling about too much which things like that.

Also, this might be completely unrelated, but I noticed it by accident while
trying things with ACPI on and off.  With ACPI on, I get a message about
'sio1' in my dmesg:

  sio1: configured irq 3 not in bitmap of probed irqs 0
  sio1: port may not be enabled

When ACPI is disabled, I don't get that.  There's only one serial port on the
machine, so I'm not sure where this comes from.  There is an ir-port (which
I've not even tried to find yet :-)), so it might be related to that?

Any ideas?

Thanks!

 - Philip

-- 
Philip Paeps                                          Please don't CC me, I am
                                                       subscribed to the list.

  BOFH Excuse #118:
    the router thinks its a printer.
