From: Avi Kivity <avi@redhat.com>
To: Jon Mason <mason@myri.com>
Cc: Sven Schnelle <svens@stackframe.org>,
Simon Kirby <sim@hostway.ca>,
Eric Dumazet <eric.dumazet@gmail.com>,
Niels Ole Salscheider <niels_ole@salscheider-online.de>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: [REGRESSION] e1000e failure triggered by "PCI: Remove MRRS modification from MPS setting code"
Date: Tue, 27 Sep 2011 20:01:48 +0300 [thread overview]
Message-ID: <4E82017C.3010304@redhat.com> (raw)
Commit ed2888e906b567 (merged 3.1-rc6) causes a reproducible failure
with my e1000e card here. Starting a kvm guest (which mostly consists
of shoving display updates over X over ssh, as far as the network is
concerned) locks up the card hard.
The failure is easily reproducible, will gladly test patches.
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2011-09-27 17:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 17:01 Avi Kivity [this message]
2011-09-27 17:59 ` Jon Mason
2011-09-27 18:28 ` Avi Kivity
2011-09-27 20:11 ` Jon Mason
2011-09-29 4:33 ` Benjamin Herrenschmidt
2011-09-29 13:53 ` Jon Mason
2011-09-30 0:16 ` Workaround for Intel MPS errata Jon Mason
2011-09-30 2:21 ` Jesse Brandeburg
2011-09-30 2:51 ` Jon Mason
2011-09-30 5:01 ` Bjorn Helgaas
2011-09-30 15:35 ` Jon Mason
2011-09-30 17:17 ` Bjorn Helgaas
2011-09-30 17:38 ` Jon Mason
2011-09-30 17:57 ` Bjorn Helgaas
2011-09-30 7:03 ` Rolf Eike Beer
2011-09-30 15:39 ` Jon Mason
2011-10-02 9:26 ` Avi Kivity
2011-10-03 4:58 ` Jon Mason
2011-10-03 10:11 ` Avi Kivity
2011-10-03 15:12 ` Jon Mason
2011-10-04 9:46 ` Avi Kivity
2011-10-04 13:06 ` Avi Kivity
2011-10-04 13:11 ` Jon Mason
2011-10-04 20:12 ` Jon Mason
2011-10-05 3:46 ` Jon Mason
2011-10-05 12:09 ` Avi Kivity
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=4E82017C.3010304@redhat.com \
--to=avi@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mason@myri.com \
--cc=niels_ole@salscheider-online.de \
--cc=sim@hostway.ca \
--cc=svens@stackframe.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome