From: "Huang\, Ying" <ying.huang@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Huang\, Ying" <ying.huang@intel.com>,
Michael Welling <mwelling@ieee.org>,
Arnd Bergmann <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.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: Tue, 23 Feb 2016 14:35:14 +0800 [thread overview]
Message-ID: <877fhw0w9p.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <CACRpkda2=P-pGktS+MXYBfjh1v-aBicg4i9T3_QPH4vNy8==kw@mail.gmail.com> (Linus Walleij's message of "Mon, 15 Feb 2016 10:36:25 +0100")
[-- Attachment #1: Type: text/plain, Size: 2750 bytes --]
Linus Walleij <linus.walleij@linaro.org> writes:
> On Mon, Feb 15, 2016 at 3:39 AM, Huang, Ying <ying.huang@intel.com> wrote:
>> Michael Welling <mwelling@ieee.org> writes:
>
>>> 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.
>
> Can you try this:
>
> diff --git a/fs/char_dev.c b/fs/char_dev.c
> index 24b142569ca9..74a2d433273e 100644
> --- a/fs/char_dev.c
> +++ b/fs/char_dev.c
> @@ -96,6 +96,8 @@ __register_chrdev_region(unsigned int major,
> unsigned int baseminor,
> goto out;
> }
> major = i;
> + pr_info("CHARDEV: allocate major %d for \"%s\"\n",
> + i, name);
> }
>
> cd->major = major;
>
> Then dmesg |grep CHARDEV should tell what we need to know.
Sorry for late, the dmesg with the patch is attached. And the output of
dmesg | grep CHARDEV is as follow:
[ 0.750037] CHARDEV: allocate major 254 for "gpiochip"
[ 0.897928] CHARDEV: allocate major 253 for "tpm"
[ 0.904196] CHARDEV: allocate major 252 for "ndctl"
[ 0.905295] CHARDEV: allocate major 251 for "dimmctl"
[ 0.909573] CHARDEV: allocate major 250 for "pps"
[ 0.913740] CHARDEV: allocate major 249 for "ptp"
[ 0.916711] CHARDEV: allocate major 248 for "iio"
[ 1.227597] CHARDEV: allocate major 247 for "bsg"
[ 1.577194] CHARDEV: allocate major 246 for "gsmtty"
[ 1.614921] CHARDEV: allocate major 245 for "ttyn"
[ 1.616044] CHARDEV: allocate major 244 for "ttyARC"
[ 1.617177] CHARDEV: allocate major 243 for "ttyRP"
[ 1.618310] CHARDEV: allocate major 242 for "ttyLP"
[ 1.620618] CHARDEV: allocate major 241 for "noz"
[ 1.621707] CHARDEV: allocate major 240 for "ttyIPWp"
[ 1.630024] CHARDEV: allocate major 239 for "telco_clock"
[ 1.632315] CHARDEV: allocate major 239 for "cmm"
[ 1.681375] CHARDEV: allocate major 238 for "hpilo"
[ 1.696757] CHARDEV: allocate major 237 for "aac"
[ 1.699338] CHARDEV: allocate major 236 for "megadev_legacy"
[ 1.704680] CHARDEV: allocate major 235 for "megaraid_sas_ioctl"
[ 1.731179] CHARDEV: allocate major 234 for "pmcsas"
[ 1.737520] CHARDEV: allocate major 233 for "nvme"
[ 2.388531] CHARDEV: allocate major 232 for "firewire"
[ 2.389743] CHARDEV: allocate major 231 for "uio"
[ 2.904429] CHARDEV: allocate major 230 for "ttySDIO"
[ 2.922374] CHARDEV: allocate major 229 for "ib_qib"
[ 2.927559] CHARDEV: allocate major 228 for "hidraw"
[ 2.952328] CHARDEV: allocate major 227 for "fwtty"
[ 2.953435] CHARDEV: allocate major 225 for "fwloop"
Best Regards,
Huang, Ying
[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 18264 bytes --]
next prev parent reply other threads:[~2016-02-23 6:36 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 ` [LKP] " Huang, Ying
2016-02-15 9:36 ` Linus Walleij
2016-02-23 6:35 ` Huang, Ying [this message]
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=877fhw0w9p.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