All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 29372] New: KMS - radeon (Uhhuh. NMI received for unknown reason)
Date: Fri, 18 Feb 2011 10:11:51 GMT	[thread overview]
Message-ID: <bug-29372-2300@https.bugzilla.kernel.org/> (raw)

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

           Summary: KMS - radeon (Uhhuh. NMI received for unknown reason)
           Product: Drivers
           Version: 2.5
    Kernel Version: 2.6.37.x
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
        AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
        ReportedBy: tomasi@cli.di.unipi.it
                CC: alexdeucher@gmail.com
        Regression: No


I noticed that when I run:
  xset dpms force standby
or
  echo "low" > /sys/class/drm/card0/device/power_profile
for my ATI Radeon Mobile X1400 (I think r5xx) I receive this advise from
kernel:
---
  Uhhuh. NMI received for unknown reason a1 on CPU 0.
  You have some hardware problem, likely on the PCI bus.
  Dazed and confused, but trying to continue
---
or something like. With latest commit on master branch of xf86-video-ati:
   http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/
my PC go on freeze after some stanby. Now I'm using the xf86-video-ati at
latest commit at 2011-02-15 16:24:23 (4d7e1498f7d9eb50e2eddabca193fc27bde24f0e)

Best regards,
Emanuele

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

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

             reply	other threads:[~2011-02-18 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 10:11 bugzilla-daemon [this message]
2011-02-18 16:50 ` [Bug 29372] KMS - radeon (Uhhuh. NMI received for unknown reason) bugzilla-daemon
2011-02-18 22:17 ` bugzilla-daemon
2012-08-16 11:00 ` 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-29372-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.