* [Bug 65554] New: CPU lock with nouveau_fan_update
@ 2013-06-09 0:20 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-65554-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
0 siblings, 1 reply; 4+ messages in thread
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ @ 2013-06-09 0:20 UTC (permalink / raw)
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW
[-- 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug 65554] CPU lock with nouveau_fan_update
[not found] ` <bug-65554-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
@ 2013-06-09 0:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-09 1:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-14 20:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2 siblings, 0 replies; 4+ messages in thread
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ @ 2013-06-09 0:40 UTC (permalink / raw)
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW
[-- Attachment #1.1: Type: text/plain, Size: 1529 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65554
--- Comment #1 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
nouveau_fan_update:
spin_lock_irqsave(&fan->lock, flags);
/* schedule next fan update, if not at target speed already */
if (list_empty(&fan->alarm.head) && target != duty) {
u16 bump_period = fan->bios.bump_period;
u16 slow_down_period = fan->bios.slow_down_period;
...
ptimer->alarm(ptimer, delay * 1000 * 1000, &fan->alarm);
If delay is somehow 0, the ->alarm will cause nouveau_fan_update to get called
immediately. Can you add a printk to that function that shows the values? (This
may end up totally flooding your dmesg too... but I think the values may be the
same across prints.)
e.g.
diff --git a/drivers/gpu/drm/nouveau/core/subdev/therm/fan.c
b/drivers/gpu/drm/nouveau/core/subdev/therm/fan.c
index c728380..9453afd 100644
--- a/drivers/gpu/drm/nouveau/core/subdev/therm/fan.c
+++ b/drivers/gpu/drm/nouveau/core/subdev/therm/fan.c
@@ -88,7 +88,7 @@ nouveau_fan_update(struct nouveau_fan *fan, bool immediate,
int target)
delay = min(bump_period, slow_down_period) ;
else
delay = bump_period;
-
+ nv_info(therm, "Scheduling fan update in %d (slow: %d, bump:
%d)\n", delay, slow_down_period, bump_period);
ptimer->alarm(ptimer, delay * 1000 * 1000, &fan->alarm);
}
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2318 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
^ permalink raw reply related [flat|nested] 4+ messages in thread
* [Bug 65554] CPU lock with nouveau_fan_update
[not found] ` <bug-65554-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-06-09 0:40 ` [Bug 65554] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
@ 2013-06-09 1:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-14 20:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2 siblings, 0 replies; 4+ messages in thread
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ @ 2013-06-09 1:01 UTC (permalink / raw)
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW
[-- Attachment #1.1: Type: text/plain, Size: 659 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65554
--- Comment #2 from ddamienn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ---
(In reply to comment #1)
> If delay is somehow 0, the ->alarm will cause nouveau_fan_update to get
> called immediately. Can you add a printk to that function that shows the
> values? (This may end up totally flooding your dmesg too... but I think the
> values may be the same across prints.)
Thanks for your help. I will try to add the printk. The lock has made the
machine inaccessible remotely, so it'll be a couple of days until I can post
the results.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1428 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug 65554] CPU lock with nouveau_fan_update
[not found] ` <bug-65554-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-06-09 0:40 ` [Bug 65554] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-09 1:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
@ 2013-06-14 20:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2 siblings, 0 replies; 4+ messages in thread
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ @ 2013-06-14 20:24 UTC (permalink / raw)
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW
[-- Attachment #1.1: Type: text/plain, Size: 809 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65554
ddamienn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from ddamienn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ---
I've had the debug statement active for the last few days, but the error hasn't
re-occurred. I discovered that my video card's fan was only working
intermittently, which a clean seems to have fixed. Since the inactive fan
likely caused the error I was seeing, I am closing this bug report as invalid.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2121 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-06-14 20:24 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-09 0:20 [Bug 65554] New: CPU lock with nouveau_fan_update bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-65554-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-06-09 0:40 ` [Bug 65554] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-09 1:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-14 20:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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.