From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 74002] New: [un]docking Lenovo W530 results in interrupt storm
Date: Thu, 23 Jan 2014 23:38:42 +0000 [thread overview]
Message-ID: <bug-74002-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1450 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=74002
Priority: medium
Bug ID: 74002
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: [un]docking Lenovo W530 results in interrupt storm
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: jcollins-u0TlgVUp4POoiH3BShWgcg@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Created attachment 92699
--> https://bugs.freedesktop.org/attachment.cgi?id=92699&action=edit
vbios
Running a 3.13 kernel, built from upstream git repository (commit
d8ec26d7f8287f5788a494f56e8814210f0e64be).
I'm able to consistently generate an ongoing interrupt storm by [un]docking my
Lenovo W530 when using the nouveau driver. This problem was first noticed
under a 3.10 kernel and associated nouveau driver. I then switched to the
above 3.13 kernel for the MSI interrupt support and to see if the problem
persisted.
The attached nouveau.interrupts is the output of read_interrupts, the source
for which is here: http://www.darnok.org/xen/read_interrupts.c. This file
shows the interrupts generated during 5 second intervals.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2908 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-01-23 23:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 23:38 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-74002-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-01-23 23:39 ` [Bug 74002] [un]docking Lenovo W530 results in interrupt storm bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-23 23:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-23 23:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-23 23:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-23 23:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-24 0:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-24 3:14 ` [Bug 74002] [NVE7] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-24 3:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-24 4:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-24 4:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-24 6:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-24 18:17 ` [Bug 74002] [NVE7] [un]plugging DP-3 on " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-24 20:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-19 16:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-05 8:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-11 23:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:42 ` 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-74002-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.