All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [ALSA] e6a1b7e880: kmsg.parport#:cannot_grant_exclusive_access_for_device_portman
Date: Fri, 18 May 2018 22:40:31 +0100	[thread overview]
Message-ID: <CADVatmPp=zSc+NqhhAsik1r_kvheUGrjwG8siX7fDfiwztxNvg@mail.gmail.com> (raw)
In-Reply-To: <20180517015410.GI4134@yexl-desktop>

[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]

Hi Xiaolong,

This is expected behaviour. lp0 has already registered with the
parport at 3.931898 sec.
So, when portman tries to register for exclusive access, it is denied
as another device has
already registered with the parport. And parport code says:
/*
 * If a device is already registered and this new
 * device wants exclusive access, then no need to
 * continue as we can not grant exclusive access to
 * this device.
 */

Similar error is with ks0108 also in your dmesg.

--
Regards
Sudip

On Thu, May 17, 2018 at 2:54 AM, kernel test robot
<xiaolong.ye@intel.com> wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: e6a1b7e88046055989b8b59c1d648fda4e606f34 ("ALSA: portman2x4 - use new parport device model")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu Nehalem -smp 2 -m 512M
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> [    4.394883] parport0: cannot grant exclusive access for device portman
>
>
>
> To reproduce:
>
>         git clone https://github.com/intel/lkp-tests.git
>         cd lkp-tests
>         bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
>
>
>
> Thanks,
> Xiaolong

  reply	other threads:[~2018-05-18 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17  1:54 [lkp-robot] [ALSA] e6a1b7e880: kmsg.parport#:cannot_grant_exclusive_access_for_device_portman kernel test robot
2018-05-18 21:40 ` Sudip Mukherjee [this message]
2018-05-19  7:43   ` Ye Xiaolong

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='CADVatmPp=zSc+NqhhAsik1r_kvheUGrjwG8siX7fDfiwztxNvg@mail.gmail.com' \
    --to=sudipm.mukherjee@gmail.com \
    --cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.