From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: Regular oops on shutdown of KVM/ARM64 machines with VGA device
Date: Tue, 30 Jun 2015 10:04:44 +0100 [thread overview]
Message-ID: <20150630090443.GA3550@leverpostej> (raw)
In-Reply-To: <CAL5wTH4wBF5e8T4Tqy1aWWAgVsM9Z-yv5mu2YrTZCg2pyW5Pog@mail.gmail.com>
On Tue, Jun 30, 2015 at 08:46:28AM +0100, Dirk M?ller wrote:
> Hi Mark,
>
> > I've seen issues with prior FW versions where the ethernet controller
> > was erroneously left active after ExitBootServices(), and would DMA
> > braodcast packets over the kernel. That resulted in similar failures to
> > what you're reporting.
> >
> > Can you reproduce the issue with all ethernet cables unplugged?
>
> not with ethernet cables unplugged, but I did ifdown on all interfaces
> and was able to trigger the issue just fine. Please note it is 100%
> reproducible in one sequence each and every time, which imho makes it
> unlikely to be a DMA scatter issue.
I see; agreed.
> > You can also try enabling CONFIG_MEMTEST (and pass memtest on the
> > command line) at boot time, which may happen to catch DMA in the act.
>
> Did not try this.
Given the above it sounds like it wouldn't help anyway ;)
Sorry for the noise!
Mark.
prev parent reply other threads:[~2015-06-30 9:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 21:16 Regular oops on shutdown of KVM/ARM64 machines with VGA device Dirk Müller
2015-06-29 10:03 ` Mark Rutland
2015-06-29 12:55 ` Marc Zyngier
2015-06-30 7:54 ` Dirk Müller
2015-06-30 10:34 ` Marc Zyngier
2015-06-30 16:16 ` Dirk Müller
2015-06-30 16:20 ` Marc Zyngier
2015-06-30 18:50 ` Christoffer Dall
2015-07-01 8:20 ` Marc Zyngier
2015-07-01 11:27 ` Catalin Marinas
2015-07-01 11:44 ` Steve Capper
2015-07-01 12:05 ` Christoffer Dall
2015-06-30 7:46 ` Dirk Müller
2015-06-30 9:04 ` Mark Rutland [this message]
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=20150630090443.GA3550@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).