All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 65554] New: CPU lock with nouveau_fan_update
Date: Sun, 09 Jun 2013 00:20:39 +0000	[thread overview]
Message-ID: <bug-65554-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1444 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=65554

          Priority: medium
            Bug ID: 65554
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: CPU lock with nouveau_fan_update
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: ddamienn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

Created attachment 80540
  --> https://bugs.freedesktop.org/attachment.cgi?id=80540&action=edit
kernel log

Kernel logs report "Watchdog detected hard LOCKUP on cpu 1". It has occurred
once per day for the last three days. Each time, it happens seemingly randomly
- monitor is turned off, I'm connected remotely via SSH but system is idle.

This is on ArchLinux with xf86-video-nouveau 1.0.7. The machine is ~2.5 years
old and has been very solid until now. My video card is: 01:00.0 VGA compatible
controller: NVIDIA Corporation GT216 [GeForce GT 220] (rev a2).

I have attached the kernel log. I also note that I don't know why the 'PTHERM'
events would be occurring - this was while the connected monitor was off and I
was only connected remotely via SSH.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2839 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2013-06-09  0:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09  0:20 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-65554-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-06-09  0:40   ` [Bug 65554] CPU lock with nouveau_fan_update bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-09  1:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-14 20:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-65554-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.