From owner-freebsd-hackers@freebsd.org Mon Mar 11 10:58:11 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B152153D253 for ; Mon, 11 Mar 2019 10:58:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76F1690D08 for ; Mon, 11 Mar 2019 10:58:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x2BAvmrE025976 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 11 Mar 2019 12:57:51 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x2BAvmrE025976 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x2BAvltO025974; Mon, 11 Mar 2019 12:57:47 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 11 Mar 2019 12:57:47 +0200 From: Konstantin Belousov To: Hans Petter Selasky Cc: "O'Connor, Daniel" , FreeBSD Hackers Subject: Re: USB stack getting confused Message-ID: <20190311105747.GT2492@kib.kiev.ua> References: <20190309192330.GO2492@kib.kiev.ua> <20190310094758.GP2492@kib.kiev.ua> <35f69493-4bbb-4142-b61a-3e90adc8777b@selasky.org> <20190310102629.GQ2492@kib.kiev.ua> <40bf77e0-47a5-6edc-b5d0-58e3c44988ac@selasky.org> <030A0C16-4508-4C7C-A87C-72B69B15EDF5@dons.net.au> <1BBD445B-9A27-4BE7-9B60-04BE0814D7CA@dons.net.au> <1692bbc5-02f4-d0e9-a290-219f045ff55b@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1692bbc5-02f4-d0e9-a290-219f045ff55b@selasky.org> User-Agent: Mutt/1.11.3 (2019-02-01) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 10:58:11 -0000 On Mon, Mar 11, 2019 at 09:27:56AM +0100, Hans Petter Selasky wrote: > On 3/11/19 7:27 AM, O'Connor, Daniel wrote: > > I just realised I can check procstat for open file, derp. > > > > [maarsytest 6:26] ~> procstat -f 2324|grep 0.5.0| wc > > 64 640 4928 > > > > So I guess that is why it is giving ENOMEM, I'm leaking FDs! If I am interpreting the output right, it is only 634 (or close) file descriptors opened. Too many fds errors are ENFILE when too many file descriptors in the system already exist, limited by kern.maxfiles, and EMFILE when per-process lmit is exceeded (resource RLIMIT_NOFILE). So your ENOMEM must come from something else. > > That looks like a bug in your application?? > > Which USB API are you using? > > --HPS