linux-kernel - Re: bug: kobject_add failed for audio with -EEXIST

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] [day] [month] [year] [list]

Message-Id: <1166458451.11560.5.camel@imap.mvista.com>
Date:	Mon, 18 Dec 2006 08:14:10 -0800
From:	Daniel Walker <dwalker@...sta.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org, Takashi Iwai <tiwai@...e.de>
Subject: Re: bug: kobject_add failed for audio with -EEXIST

On Mon, 2006-12-18 at 16:53 +0100, Ingo Molnar wrote:
> an allyesconfig bootup generates the driver core warning below, in 
> alsa_card_dummy_init().
> 
> 	Ingo
> 
> ------------------>
> Calling initcall 0xc1ee1d35: alsa_card_dummy_init+0x0/0x8a()
> PM: Adding info for platform:snd_dummy.0
> kobject_add failed for audio with -EEXIST, don't try to register things with the same name in the same directory.

This is i386 or x86_64? This one, and the others, your been sending look
like initcall ordering issues. For instance, some alsa init usually runs
after alsa_card_dummy_init() , but in your kernel alsa_card_dummy_init()
runs first. It's a problem even in the same initcall level.

Daniel

-
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/