public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Franklin Marmon <marmon-GymH4r+vMzPQT0dZR+AlfA@public.gmane.org>
To: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Fixing broken DSDT - code suggestions for comment    please!
Date: Tue, 18 May 2004 08:19:06 -0600	[thread overview]
Message-ID: <1084889946.5037.2.camel@laptop.hydeco.com> (raw)

I've posted this question before, if its just a question that shall go
unanswered someone please let me know so I stop reposting it different
ways:

Where would start searching for information on debugging a compiled
DSDT?  The iasl compiler believes it is fine, 0 errors, 0 warnings; but
I kernel panic in the one_complete_parse phase when booting using the
custom dsdt table.

Thank you,

frm




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click

             reply	other threads:[~2004-05-18 14:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 14:19 Franklin Marmon [this message]
     [not found] ` <1084889946.5037.2.camel-t0Me6uhKnbVYViWeMKg0xQC/G2K4zDHf@public.gmane.org>
2004-05-18 15:30   ` Fixing broken DSDT - code suggestions for comment please! Bas Mevissen
  -- strict thread matches above, loose matches on Subject: below --
2004-05-28  3:52 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F84047B206A-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-05-28  7:33   ` Nate Lawson
2004-05-27  3:53 Yu, Luming
2004-05-26 15:36 Moore, Robert
     [not found] ` <37F890616C995246BE76B3E6B2DBE055E08D59-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-05-27 20:42   ` Nate Lawson
2004-05-26  2:35 Yu, Luming
2004-05-21  0:33 Brown, Len
2004-05-16  9:29 Cam
     [not found] ` <40A73460.2070407-Nk/s8sJ9yP7QXOPxS62xeg@public.gmane.org>
2004-05-17 11:27   ` Cam
2004-05-17 19:35   ` Len Brown
     [not found]     ` <1084822558.12353.365.camel-D2Zvc0uNKG8@public.gmane.org>
2004-05-18  0:54       ` Cam
     [not found]         ` <40A95EB3.5070206-Nk/s8sJ9yP7QXOPxS62xeg@public.gmane.org>
2004-05-18  1:00           ` Len Brown
     [not found]             ` <1084842006.12349.372.camel-D2Zvc0uNKG8@public.gmane.org>
2004-05-20 20:29               ` Chris McDermott
     [not found]                 ` <20040520202950.GK5920-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2004-05-21  8:51                   ` Cam

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=1084889946.5037.2.camel@laptop.hydeco.com \
    --to=marmon-gymh4r+vmzpqt0dzr+alfa@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