From: Michal Kubecek <mkubecek@suse.cz>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: regression (bisected): "modprobe parport_pc" hangs in current mainline
Date: Wed, 20 Mar 2019 22:18:13 +0100 [thread overview]
Message-ID: <20190320211813.GE29968@unicorn.suse.cz> (raw)
In-Reply-To: <CADVatmNVf+8fLsZjETx5nmYKmdQCg0Moqv5W3S0i4gtX9uMn=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
On Wed, Mar 20, 2019 at 09:30:59AM +0000, Sudip Mukherjee wrote:
> Sorry, I didn't get the chance to look at it yet and have kept it
> pending for this weekend. But just had a quick look and I was
> wondering if the machine on which you are trying the modprobe has an
> actual parallel port or the machine is not having any parallel port.
> And also will you be able to send me a dmesg please.
Attaching dmesg output from a virtual machine which doesn't seem to have
a (virtual) parallel port. This part:
[ 63.962283] parport_pc 00:05: reported by Plug and Play ACPI
[ 63.962469] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[ 64.061723] ppdev: user-space parallel port driver
was after I manually killed "/sbin/modprobe -q -- parport_lowlevel" which
was started during boot.
Tomorrow (when I'm in the office) I'll check what happens when I add
a parallel port to the VM and also send you dmesg output from the
physical machine where I first noticed the issue. I'm quite sure it has
parallel port on its motherboard but it might be disabled in BIOS, I'll
have to check.
Michal Kubecek
[-- Attachment #2: dmesg-vm-5.1-rc1.gz --]
[-- Type: application/x-gzip, Size: 20932 bytes --]
next prev parent reply other threads:[~2019-03-20 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 6:45 regression (bisected): "modprobe parport_pc" hangs in current mainline Michal Kubecek
2019-03-17 17:01 ` Sudip Mukherjee
2019-03-17 18:05 ` Michal Kubecek
2019-03-20 9:30 ` Sudip Mukherjee
2019-03-20 21:18 ` Michal Kubecek [this message]
2019-03-21 22:43 ` Sudip Mukherjee
2019-03-22 6:13 ` Michal Kubecek
2019-03-24 19:38 ` Sudip Mukherjee
2019-03-25 7:30 ` Michal Kubecek
2019-03-25 10:00 ` Sudip Mukherjee
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=20190320211813.GE29968@unicorn.suse.cz \
--to=mkubecek@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@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