All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66761] ACPI "Firmware Bug" (IGPU, Z01I) causes trouble
Date: Sun, 11 Jan 2015 23:28:56 +0000	[thread overview]
Message-ID: <bug-66761-2300-0ci5dZ3OKx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-66761-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=66761

--- Comment #10 from KernelBug <3fdd1e5d@opayq.com> ---
Don't mean to hijack a bug report, but I'm also getting ACPI Warning messages,
and wanted to know, are there kernel modules related to this I can blacklist?

Or anything I can do to fix these?

Also are these releated to smbus?


ACPI Warning: SystemIO range 0x000000000000f000-0x000000000000f01f conflicts
with OpRegion 0x000000000000f000-0x000000000000f00f (\SMB0)
(20140926/utaddress-258)
ACPI Warning: SystemIO range 0x000000000000f000-0x000000000000f01f conflicts
with OpRegion 0x000000000000f000-0x000000000000f00f (\_SB_.PCI0.SBUS.SMBI)
(20140926/utaddress-258)



thank you

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-01-11 23:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-66761-2300@https.bugzilla.kernel.org/>
2013-12-09  2:42 ` [Bug 66761] ACPI "Firmware Bug" (IGPU, Z01I) causes trouble bugzilla-daemon
2013-12-09 10:25 ` bugzilla-daemon
2014-12-17 21:47 ` bugzilla-daemon
2015-01-11 23:28 ` bugzilla-daemon [this message]
2015-02-05  4:35 ` bugzilla-daemon
2015-02-10  6:21 ` bugzilla-daemon
2015-02-10  6:22 ` bugzilla-daemon

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=bug-66761-2300-0ci5dZ3OKx@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.