linux-kernel - Re: kobject_add_internal failed for msi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5245D626.6090209@redhat.com>
Date:	Fri, 27 Sep 2013 21:01:58 +0200
From:	Zdenek Kabelac <zkabelac@...hat.com>
To:	Veaceslav Falico <vfalico@...hat.com>
CC:	Bjorn Helgaas <bhelgaas@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>, linux.nics@...el.com,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: kobject_add_internal failed for msi_irqs with -EEXIST

Dne 27.9.2013 18:01, Veaceslav Falico napsal(a):
> 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@...hat.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.
>

I'm not readding e1000e modules myself - however I've no idea what 
NetworkManager does. Here are messages prior warning:

NetworkManager[304]: <info> monitoring kernel firmware directory '/lib/firmware'.
NetworkManager[304]: <info> rfkill1: found WiFi radio killswitch (at 
/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill1) 
(driver iwl3945)
NetworkManager[304]: <info> WiFi hardware radio set enabled
NetworkManager[304]: <info> WiFi enabled by radio killswitch; enabled by state 
file
NetworkManager[304]: <info> WWAN enabled by radio killswitch; disabled by 
state file
NetworkManager[304]: <info> WiMAX enabled by radio killswitch; enabled by 
state file
NetworkManager[304]: <info> Networking is enabled by state file
NetworkManager[304]: <info> (eth0): carrier is OFF
NetworkManager[304]: <info> (eth0): new Ethernet device (driver: 'e1000e' 
ifindex: 2)
NetworkManager[304]: <info> (eth0): exported as 
/org/freedesktop/NetworkManager/Devices/0
NetworkManager[304]: <info> (eth0): device state change: unmanaged -> 
unavailable (reason 'managed') [10 20 2]
NetworkManager[304]: <info> (eth0): bringing up device.
rpcbind: cannot create socket for udp6
rpcbind: cannot create socket for tcp6
kernel: [    5.727025] WARNING! power/level is deprecated; use power/control 
instead

So it looks like  'bringing up' causes recreation of msi_irqs ?

Zdenek

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/