From: Guenter Roeck <linux@roeck-us.net>
To: Chris Murphy <bugzilla@colorremedies.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Josh Boyer <jwboyer@fedoraproject.org>,
khali@linux-fr.org, lm-sensors@lm-sensors.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: applesmc oops in 3.10/3.11
Date: Tue, 1 Oct 2013 09:24:25 -0700 [thread overview]
Message-ID: <20131001162425.GD14887@roeck-us.net> (raw)
In-Reply-To: <C10D98EE-28FE-4BFE-BDE5-1EAABF112AC2@colorremedies.com>
On Tue, Oct 01, 2013 at 09:33:13AM -0600, Chris Murphy wrote:
>
> On Oct 1, 2013, at 9:19 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>
> > On Tue, Oct 01, 2013 at 12:55:26PM +0200, Henrik Rydberg wrote:
> >>>> Warning message triggered with 3.12.0-0.rc3.git0.1.fc21.x86_64.
> >>>>
> >>>> [ 10.886016] applesmc: key count changed from 261 to 1174405121
> >>>>
> >>>
> >>> Explains the crash, but the new key count is very wrong. 1174405121 = 0x46000001.
> >>> Which I guess explains the subsequent memory allocation error in the log.
> >>>
> >>> Henrik, any idea what might be going on ? Is it possible that the previous
> >>> command failure leaves some state machine in a bad state ?
> >>
> >> I seem to recall a report on another similar state problem on newer
> >> machines, so maybe, yes. Older machines seem fine, I have never
> >> encountered the problem myself. Here is a patch to test that
> >> theory. It has been tested to be pretty harmless on two different
> >> generations.
> >>
> >> I really really do not want to add an 'if (value is insane)' check ;-)
> >>
> > Chris,
> >
> > any chance you can load this patch on an affected machine so we can get
> > test feedback ? This one is too experimental to submit upstream without
> > knowing that it really fixes the problem.
>
> Yes. What kernel.org source version should I apply it against? I'd use the non-debug config file from an equivalent version Fedora kernel, unless asked otherwise. And also should I test it on other vintages? I have here MBP4,1(2008); MBP8,2(2011), and MBP10,2(2012).
>
Only requirement is that it also includes the previous patch, so it would be
optimal if you can apply it on top of the previous image.
Thanks,
Guenter
next prev parent reply other threads:[~2013-10-01 16:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 19:06 applesmc oops in 3.10/3.11 Josh Boyer
2013-09-25 19:56 ` Guenter Roeck
2013-09-25 21:48 ` Henrik Rydberg
2013-09-25 22:08 ` Guenter Roeck
2013-09-26 6:34 ` Henrik Rydberg
2013-09-26 10:36 ` Guenter Roeck
2013-09-26 11:13 ` Henrik Rydberg
2013-09-26 10:53 ` Guenter Roeck
2013-09-26 11:11 ` Henrik Rydberg
2013-09-27 16:21 ` Josh Boyer
2013-09-27 17:12 ` Guenter Roeck
2013-09-27 17:41 ` Chris Murphy
2013-09-27 17:59 ` Guenter Roeck
2013-09-27 18:03 ` Chris Murphy
2013-09-27 23:33 ` Guenter Roeck
2013-10-01 1:57 ` Chris Murphy
2013-10-01 3:37 ` Guenter Roeck
2013-10-01 10:55 ` Henrik Rydberg
2013-10-01 15:19 ` Guenter Roeck
2013-10-01 15:33 ` Chris Murphy
2013-10-01 16:24 ` Guenter Roeck [this message]
2013-10-02 1:09 ` Chris Murphy
2013-10-02 3:51 ` Guenter Roeck
2013-10-02 3:55 ` Chris Murphy
2013-10-02 4:02 ` Guenter Roeck
2013-10-02 9:53 ` Henrik Rydberg
2013-10-02 13:30 ` Guenter Roeck
2013-10-02 16:34 ` Henrik Rydberg
2013-10-02 16:47 ` Guenter Roeck
2013-10-02 17:24 ` Henrik Rydberg
2013-10-02 18:02 ` Guenter Roeck
2013-10-02 18:33 ` Chris Murphy
2013-10-02 20:59 ` Guenter Roeck
2013-10-02 21:34 ` Chris Murphy
2013-10-02 23:32 ` Guenter Roeck
2013-10-07 23:42 ` Guenter Roeck
2013-10-07 23:46 ` Chris Murphy
2013-10-08 15:48 ` Guenter Roeck
2013-10-08 16:29 ` Henrik Rydberg
2013-10-08 16:29 ` Guenter Roeck
2013-10-09 8:29 ` Henrik Rydberg
2013-10-09 16:52 ` Guenter Roeck
2013-09-27 18:01 ` Guenter Roeck
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=20131001162425.GD14887@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bugzilla@colorremedies.com \
--cc=jwboyer@fedoraproject.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=rydberg@euromail.se \
/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