From: Colin Ian King <colin.king at canonical.com>
To: devel@acpica.org
Subject: Re: [Devel] Upgraded Haiku to ACPICA 20151218, now crashes on various systems
Date: Thu, 31 Dec 2015 18:29:36 +0000 [thread overview]
Message-ID: <56857410.8090602@canonical.com> (raw)
In-Reply-To: CAEesM74MUHvo=izm78N8s4Qb9dDHbW8UZYO5gB-_QQZG00XSZw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
On 31/12/15 18:05, waddlesplash wrote:
> Hi,
>
> I'm one of the developers of the Haiku operating system, which uses
> ACPICA as the backend for its ACPI bus manager. We recently updated to
> ACPICA 20151218 from 20150818 (merge commit: [1], update commit: [2]).
> However, since the update, a select few systems now crash on boot [3].
> I and the other developers are a bit stumped as to what's going on
> here.
>
> Is this our fault in some way? Or is ACPICA to blame here?
When I upgraded fwts to using ACPICA 20151218 I had some crashes on
startup and I tracked it down to having now to set
AcpiGbl_OverrideDefaultRegionHandlers = TRUE before
AcpiInitializeSubsystem() is called. Maybe your issue is related to
that change.
Colin
>
> -waddlesplash
>
> [1]: http://cgit.haiku-os.org/haiku/commit/?id=4dffc0abb95bbf20160457b40cd2466393836b0e&context=3&ignorews=1&ss=0
> [2]: http://cgit.haiku-os.org/haiku/commit/?id=d4fb4ebd675bcb3b6a3b307b172cdafd43b58710
> [3]: https://dev.haiku-os.org/ticket/12549#ticket
> _______________________________________________
> Devel mailing list
> Devel(a)acpica.org
> https://lists.acpica.org/mailman/listinfo/devel
>
next reply other threads:[~2015-12-31 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 18:29 Colin Ian King [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-31 18:05 [Devel] Upgraded Haiku to ACPICA 20151218, now crashes on various systems waddlesplash
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=56857410.8090602@canonical.com \
--to=devel@acpica.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.