From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: "kobject add failed" Date: Thu, 03 May 2007 17:40:54 +0100 Message-ID: References: <907625E08839C4409CE5768403633E0B018E1CBB@sefsexmb1.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <907625E08839C4409CE5768403633E0B018E1CBB@sefsexmb1.amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Petersson, Mats" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Looks like a dom0 kernel bug? -- Keir On 3/5/07 16:39, "Petersson, Mats" wrote: > When runnign two scripts for hvm save/restore iterations at the same > time, I got this message after around 150 (combined between the two > scripts). The one process is now stuck on "saving"... > > kobject_add failed for tap0 with -EEXIST, don't try to register things > with the > same name in the same directory. > > Call Trace: > [] kobject_add+0x16e/0x199 > [] class_device_add+0xaf/0x441 > [] kobject_get+0x12/0x17 > [] register_netdevice+0x23b/0x30b > [] :tun:tun_chr_ioctl+0x272/0x4db > [] do_filp_open+0x2d/0x3d > [] do_ioctl+0x55/0x6b > [] vfs_ioctl+0x252/0x26b > [] sys_ioctl+0x59/0x7a > [] tracesys+0xa7/0xb3