From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751749AbcBOCjQ (ORCPT ); Sun, 14 Feb 2016 21:39:16 -0500 Received: from mga02.intel.com ([134.134.136.20]:6572 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751561AbcBOCjP (ORCPT ); Sun, 14 Feb 2016 21:39:15 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,448,1449561600"; d="scan'208";a="914983875" From: "Huang\, Ying" To: Michael Welling Cc: Arnd Bergmann , Greg Kroah-Hartman , Linus Walleij , LKML , Johan Hovold , "Markus Pargmann" , Subject: Re: [LKP] [lkp] [gpio] 3c702e9987: kmsg.user_verbs:couldn't_register_device_number References: <87ziv3n5fp.fsf@yhuang-dev.intel.com> <20160214080643.GA31304@qwerty.qwertyembedded> Date: Mon, 15 Feb 2016 10:39:11 +0800 In-Reply-To: <20160214080643.GA31304@qwerty.qwertyembedded> (Michael Welling's message of "Sun, 14 Feb 2016 02:06:43 -0600") Message-ID: <8760xqd7e8.fsf@yhuang-dev.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Michael Welling writes: > On Sun, Feb 14, 2016 at 02:59:06PM +0800, kernel test robot wrote: >> FYI, we noticed the below changes on >> >> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git chardev >> commit 3c702e9987e261042a07e43460a8148be254412e ("gpio: add a userspace chardev ABI for GPIOs") >> >> >> [ 1.951191] user_verbs: couldn't register device number > > Looks like user_verbs is using a static device node setup. > > enum { > IB_UVERBS_MAJOR = 231, > IB_UVERBS_BASE_MINOR = 192, > IB_UVERBS_MAX_DEVICES = 32 > }; > > #define IB_UVERBS_BASE_DEV MKDEV(IB_UVERBS_MAJOR, IB_UVERBS_BASE_MINOR) > > Something tells me that a new GPIO chardev is taking this spot. > > It looks like the device is documented to be using the range: > https://www.kernel.org/doc/Documentation/devices.txt > > Could you run cat /proc/devices? > Sorry, the test mechanism is not flexible enough to run some shell command in test system. Could you provide a specialized debug kernel to dump the necessary information in kernel log? We can collect dmesg easily. Best Regards, Huang, Ying