From: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
To: Joe Lawrence <joe.lawrence@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: sudipm.mukherjee@gmail.com, gregkh@linuxfoundation.org
Subject: Re: [ppdev] sysfs warning on qemu boot
Date: Wed, 9 Nov 2016 17:04:38 +0000 [thread overview]
Message-ID: <58235726.6000903@codethink.co.uk> (raw)
In-Reply-To: <0039c5ca-0a77-968c-7356-07977242474b@redhat.com>
Hi Joe,
On 09/11/16 16:00, Joe Lawrence wrote:
> Hi Sudip,
>
> I hit a sysfs_warn_dup inside QEMU running 4.9.0-rc4 (I suspect earlier
> versions as well, but this is the first upstream I've run in a while).
> This warning looks like something the kernel test robot ran into a few
> months ago:
Yes, 0day reported, but I was unable to reproduce it with the config
file that was given. Can you please send me your .config file and I will
try to reproduce this on my setup, and if I am not able to then i will
have to disturb you for debugging and testing.
--
Regards
Sudip
next prev parent reply other threads:[~2016-11-09 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 16:00 [ppdev] sysfs warning on qemu boot Joe Lawrence
2016-11-09 17:04 ` Sudip Mukherjee [this message]
2016-11-09 18:41 ` Joe Lawrence
2016-11-11 21:14 ` Sudip Mukherjee
2016-11-11 22:16 ` Joe Lawrence
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=58235726.6000903@codethink.co.uk \
--to=sudip.mukherjee@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=joe.lawrence@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
/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