public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Jaak Ristioja <jaak@ristioja.ee>, Peter Geis <pgwipeout@gmail.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	linux-media@vger.kernel.org, linux-input@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: Linux 4.16 Kernel Boot Crash
Date: Wed, 4 Apr 2018 15:54:19 -0300	[thread overview]
Message-ID: <20180404155419.0740c805@vento.lan> (raw)
In-Reply-To: 87in97up15.fsf@intel.com

Em Wed, 4 Apr 2018 16:26:22 +0300
Jaak Ristioja <jaak@ristioja.ee> escreveu:

> Hello, all!
> 
> I experience the same issue with a Lenovo ThinkPad T440p (LENOVO
> 20AN006VMS/20AN006VMS, BIOS GLET90WW (2.44 ) 09/13/2017). I tried to
> bisect v4.15..v4.16 but failed.

Could you post the complete dmesg? I also need the .config used
to build the Kernel.

From its call trace:

[   43.177492] Call Trace:
[   43.177498]  ? devres_add+0x5f/0x70
[   43.177502]  rmi_f54_probe+0x437/0x470 [rmi_core]
[   43.177505]  rmi_function_probe+0x25/0x30 [rmi_core]
[   43.177507]  driver_probe_device+0x310/0x480

It looks that this was generated by an input driver 
drivers/input/rmi4/rmi_f54.c, with could be doing something wrong when
registering at the media core.

From the logs, the warn on is happening at 
drivers/media/v4l2-core/v4l2-dev.c:945, e. g:

        /* Should not happen since we thought this minor was free */
        WARN_ON(video_device[vdev->minor] != NULL);

That was probably called here:

	drivers/input/rmi4/rmi_f54.c:   ret = video_register_device(&f54->vdev, VFL_TYPE_TOUCH, -1);

Thanks,
Mauro

  parent reply	other threads:[~2018-04-04 18:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6a0009be-cbf8-671e-9d7d-c78340e93f58@gmail.com>
2018-04-04 12:36 ` Linux 4.16 Kernel Boot Crash Jani Nikula
     [not found]   ` <5ac4d275.1c69fb81.9f4be.b26eSMTPIN_ADDED_MISSING@mx.google.com>
2018-04-04 16:56     ` Peter Geis
2018-04-04 18:54   ` Mauro Carvalho Chehab [this message]
2018-04-05  9:57   ` Mauro Carvalho Chehab
2018-04-05 10:03     ` Mauro Carvalho Chehab
2018-04-05 10:08     ` Hans Verkuil

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=20180404155419.0740c805@vento.lan \
    --to=mchehab@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jaak@ristioja.ee \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=pgwipeout@gmail.com \
    /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