From: Christian Kastner <debian@kvr.at>
To: intel-gfx@lists.freedesktop.org
Subject: Macbook Air 6, 2: i915-related interrupt storm after Yosemite update
Date: Sat, 01 Nov 2014 18:08:00 +0100 [thread overview]
Message-ID: <54551370.10001@kvr.at> (raw)
Hi,
I have a Macbook Air (2013) (6,2) which until recently was working
flawlessly with Debian unstable, which I use almost exclusively on that
machine. I did keep the OSX installation, mainly because it's the only
way to get firmware updates.
Recently, in a moment of weakness, I said "yes" to the offer of
upgrading OSX to Yosemite. Since then, whenever I boot Debian, there is
an i915-related interrupt storm, with a kworker thread constantly
running at 70%.
Downgrading OSX back to Mavericks did not help. Apparently Yosemite
included firmware updates, as within OSX I am shown version numbers that
are so new they aren't even listed on Apple's homepage yet.
Here's what I see:
$ GPE=/sys/firmware/acpi/interrupts/gpe66
$ while true; doe cat $GPE; sleep 1; done
727268 enabled
757981 enabled
788576 enabled
807337 enabled
828426 enabled
...
I've tested this with 3.16 and 3.17 kernels; I was using the former for
about a month now without issue.
When I boot with modprobe.blacklist=i915, the issue disappears.
Does anyone have an idea what could be going on?
Regards,
Christian
PS: Please CC: me as I am not subscribed to this list.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2014-11-01 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 17:08 Christian Kastner [this message]
2014-11-03 15:25 ` Macbook Air 6, 2: i915-related interrupt storm after Yosemite update Daniel Vetter
2014-11-18 21:07 ` Christian Kastner
2015-02-11 9:00 ` Macbook Air 6, 2: i915-related interrupt storm after Yosemite update -- resolved Christian Kastner
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=54551370.10001@kvr.at \
--to=debian@kvr.at \
--cc=intel-gfx@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.