cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 21082] Machine Check Exception on Athlon X2
Date: Sun, 24 Oct 2010 23:29:19 GMT	[thread overview]
Message-ID: <201010242329.o9ONTJZP006302@demeter1.kernel.org> (raw)
In-Reply-To: <bug-21082-12968@https.bugzilla.kernel.org/>

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


Thomas Renninger <trenn@suse.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |trenn@suse.de
          Component|cpufreq                     |x86-64
         AssignedTo|cpufreq@vger.kernel.org     |platform_x86_64@kernel-bugs
                   |                            |.osdl.org
            Product|Power Management            |Platform Specific/Hardware




--- Comment #1 from Thomas Renninger <trenn@suse.de>  2010-10-24 23:29:12 ---
This is most probably unrelated to CPU freq and powernow-k8 driver.
I expect the backtrace does not always point to powernow-k8 driver?

> As far as I can tell, this only happens when X is running as i build gentoo
> with out problems.
I saw something similar, also related to the X driver.
It was very hard to reproduce (run two different 3D X applications in parallel,
then it would throw such an MCE after 2-30 minutes...) and hang up.
The fix was about missing TLB flushes related to ioremap.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

      reply	other threads:[~2010-10-24 23:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-24 15:27 [Bug 21082] New: Machine Check Exception on Athlon X2 bugzilla-daemon
2010-10-24 23:29 ` bugzilla-daemon [this message]

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=201010242329.o9ONTJZP006302@demeter1.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@vger.kernel.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