qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] seek help for AER
Date: Tue, 21 Feb 2017 09:07:45 -0700	[thread overview]
Message-ID: <20170221090745.7aea1461@t450s.home> (raw)
In-Reply-To: <58AC14C1.60603@cn.fujitsu.com>

On Tue, 21 Feb 2017 18:21:53 +0800
Cao jin <caoj.fnst@cn.fujitsu.com> wrote:

> Hi,
> 
> First, sorry for such a long time delay on the AER job. I was on 12 days
> holiday, and start to work on the patch 2 weeks ago, because I use a
> newer version kernel(4.10 rc8) to start off the work, several tiny
> problems slow me.
> 
> Now I meet a confusing issue on aer_inject module. When I use aer_inject
> command before, it says:
> 
>     Error: Failed to write, No such device
> 
> then in dmesg, it says:
> 
>     pcieport 0000:00:09.0: aer_inject: AER device not found
> 
> and then I add some debug line in find_aer_device_iter() to check
> device->bus-name, find that it is "pci", so that is why I can't inject,
> it should have been "pci_express". But everything is same as before
> except a newer host kernel.
> 
> I still don't have a clue on this problem for almost 2 days, could you help?

If it only happens with a new host kernel, I would suggest finding a
kernel where it works and bisecting between working and non-working
kernels to find the commit that introduced the change.  You may have
found a regression in the kernel that should be reported upstream.
Thanks,

Alex

  reply	other threads:[~2017-02-21 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 10:21 [Qemu-devel] seek help for AER Cao jin
2017-02-21 16:07 ` Alex Williamson [this message]
2017-02-22  6:31   ` Cao jin

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=20170221090745.7aea1461@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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).