public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Dobramysl <uli-do-RbZlAiThDcE@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Gericom Supersonic ACPI hang (smi_cmd)
Date: Fri, 11 Oct 2002 17:52:39 +0200	[thread overview]
Message-ID: <3DA6F3C7.3040108@gmx.at> (raw)

Hello there again!

I posted some days ago, that I have problems getting ACPI up and running 
  on my Gericom Laptop. The Kernel just hangs without any error message.
Arndt Schoenewald suggested some Kernel Configurations to me (thanks 
again!) , but none of them did work. It seems like I have a very rare 
Version of this laptop model, with a (very) broken BIOS.
So I tried to debug that myself. I'm not a very good C Programmer and 
have no clue about the ACPI specifications, so I cannot solve this 
problem myself.
I was able to trace down the hang where acpi_enable gets called and 
itself calls acpi_hw_set_mode. This goes into the function 
acpi_os_write_port(acpi_gbl_FADT->smi_cmd, (acpi_integer) 
acpi_gbl_FADT->acpi_enable, 8), where outb gets called with port 
acpi_gbl_FADT->smi_cmd and value acpi_gbl_FADT->acpi_enable.
I think there is something wrong with the address smi_cmd. I could not 
find the part in the code where it gets set.
Tell me if I can provide more information about this problem or something.

Ulrich Dobramysl



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

             reply	other threads:[~2002-10-11 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11 15:52 Ulrich Dobramysl [this message]
     [not found] ` <000b01c27163$927d6e70$6600a8c0@rolilaptop>
2002-10-12 11:47   ` Gericom Supersonic ACPI hang (smi_cmd) Ulrich Dobramysl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DA6F3C7.3040108@gmx.at \
    --to=uli-do-rbzlaithdce@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox