From: Veaceslav Falico <vfalico@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Zdenek Kabelac <zkabelac@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux.nics@intel.com,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: kobject_add_internal failed for msi_irqs with -EEXIST
Date: Fri, 27 Sep 2013 18:01:25 +0200 [thread overview]
Message-ID: <20130927160125.GB14139@redhat.com> (raw)
In-Reply-To: <CAErSpo6L-Ud08=JPM7d=RYuPO=UFvq_9hZGbne0iQnCHiFbuHQ@mail.gmail.com>
On Fri, Sep 27, 2013 at 09:58:28AM -0600, Bjorn Helgaas wrote:
>[+cc Veaceslav, linux-pci]
>
>On Fri, Sep 27, 2013 at 7:34 AM, Zdenek Kabelac <zkabelac@redhat.com> wrote:
>> Hi
>>
>> With recent build of 3.12-rc2 I'm getting this warning report from kernel:
>> (hw Lenovo T61, C2D, 4GB Ram)
>> (repost since linux-kernel@ rejected my gmail email....)
>
>This looks related to the MSI/kobject issues Veaceslav is working on.
>See http://lkml.kernel.org/r/1379382464-7920-2-git-send-email-vfalico@redhat.com
>and related messages.
>
>We don't have a resolution yet. If you have
>CONFIG_DEBUG_KOBJECT_RELEASE=y, you could try turning that off. I
>don't know if it would help, and it would only be a temporary
>workaround anyway.
I've looked at the original post -
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg510798.html
hope that's it - and it seems that it's disabling DEBUG_KOBJECT_RELEASE
won't help - the warning is about the re-registering, not about freeing it.
As a workaround I'd suggest adding some kind of delay between removing and
adding the msi - as in - rmmod e1000e; sleep 1; modprobe e1000e; - or
something like that, so that there is enough time for the /msqi_irqs/ to go
away.
>
>Bjorn
next prev parent reply other threads:[~2013-09-27 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5245896A.70705@redhat.com>
2013-09-27 15:58 ` kobject_add_internal failed for msi_irqs with -EEXIST Bjorn Helgaas
2013-09-27 16:01 ` Veaceslav Falico [this message]
2013-09-27 19:01 ` Zdenek Kabelac
2013-10-01 13:00 ` Veaceslav Falico
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=20130927160125.GB14139@redhat.com \
--to=vfalico@redhat.com \
--cc=bhelgaas@google.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux.nics@intel.com \
--cc=zkabelac@redhat.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;
as well as URLs for NNTP newsgroup(s).