From: "Huang\, Ying" <ying.huang@intel.com>
To: Michael Welling <mwelling@ieee.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Johan Hovold <johan@kernel.org>,
"Markus Pargmann" <mpa@pengutronix.de>, <lkp@01.org>
Subject: Re: [LKP] [lkp] [gpio] 3c702e9987: kmsg.user_verbs:couldn't_register_device_number
Date: Mon, 15 Feb 2016 10:39:11 +0800 [thread overview]
Message-ID: <8760xqd7e8.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20160214080643.GA31304@qwerty.qwertyembedded> (Michael Welling's message of "Sun, 14 Feb 2016 02:06:43 -0600")
Michael Welling <mwelling@ieee.org> 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
next prev parent reply other threads:[~2016-02-15 2:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 6:59 [lkp] [gpio] 3c702e9987: kmsg.user_verbs:couldn't_register_device_number kernel test robot
2016-02-14 8:06 ` Michael Welling
2016-02-14 17:42 ` Linus Walleij
2016-02-14 17:49 ` Greg KH
2016-02-14 17:56 ` Linus Walleij
2016-02-14 19:05 ` Greg KH
2016-02-14 19:51 ` Michael Welling
2016-02-14 23:49 ` Greg KH
2016-02-15 4:21 ` Michael Welling
2016-02-14 17:48 ` Linus Walleij
2016-02-15 2:39 ` Huang, Ying [this message]
2016-02-15 9:36 ` [LKP] " Linus Walleij
2016-02-23 6:35 ` Huang, Ying
2016-02-23 21:50 ` Michael Welling
2016-02-24 16:01 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760xqd7e8.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mpa@pengutronix.de \
--cc=mwelling@ieee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox