From: Greg KH <gregkh@linuxfoundation.org>
To: Max Staudt <mstaudt@suse.de>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8250: option 'force_polling' for buggy IRQs
Date: Tue, 26 Jul 2016 08:08:56 -0700 [thread overview]
Message-ID: <20160726150856.GA15676@kroah.com> (raw)
In-Reply-To: <b7ed014e-c6be-01ab-d601-08830d72f8cb@suse.de>
On Tue, Jul 26, 2016 at 01:42:13PM +0200, Max Staudt wrote:
> On 07/25/2016 07:47 PM, Greg KH wrote:
> > On Mon, Jul 25, 2016 at 07:36:15PM +0200, Max Staudt wrote:
> >> Some serial ports may not emit IRQs properly, or there may be a defect
> >> in their routing on the motherboard.
> >>
> >> This patch allows these ports to be used anyway (or until a better
> >> workaround is known for a specific platform), though with no guarantees.
> >>
> >> If you have such a buggy UART, boot Linux with 8250.force_polling=1 .
> >
> > Ick, don't add new module parameters if at all possible.
>
> I agree, I'd rather not add a parameter either, but...
>
> - It's a hardware issue
> - It needs to be handled at boot time
Why?
> - It can't be auto-detected (AFAIK)
Why not? Can't you have a quirk for this specific, broken, device?
> The idea is that this parameter allows for a workaround until someone comes
> up with a workaround or autodetection (if ever). And it can be used to
> debug future buggy hardware.
module paramters are horrid, they don't scale (which uart is this for?),
and no one ever changes them.
> >> It is essentially the kernel level version of:
> >>
> >> setserial /dev/ttySn irq 0
> >
> > Why can't you just do this instead?
>
> Because it's too late by the time we reach userspace.
>
> In case of "console=ttyS0" the decision to use polling needs to happen before
> ttyS0 is opened from userspace, as the system will otherwise hang for up to
> 30 seconds at a time. Input is mostly dropped, thus I can't even use BREAK+B
> to force reboot it.
>
> As it stands now, I can't even boot the system with "rdinit=/bin/bash".
> The force_polling option makes the system somewhat usable, albeit the serial
> output is very slow.
>
> Curiously, the kernel's printk() is as fast as it should be. It's just
> userspace that is slow. Any idea why that is the case?
Ah, then something else might be wrong here, I suggest you track this
down please.
thanks,
greg k-h
next prev parent reply other threads:[~2016-07-26 15:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 17:36 [PATCH] 8250: option 'force_polling' for buggy IRQs Max Staudt
2016-07-25 17:47 ` Greg KH
2016-07-26 11:42 ` Max Staudt
2016-07-26 15:08 ` Greg KH [this message]
2016-07-26 16:18 ` Max Staudt
2016-07-27 12:09 ` One Thousand Gnomes
2016-07-27 12:14 ` Max Staudt
2016-07-27 13:33 ` Theodore Ts'o
2016-07-27 20:01 ` One Thousand Gnomes
2016-07-28 9:59 ` Max Staudt
2016-07-28 14:47 ` Greg KH
2016-07-28 16:01 ` Theodore Ts'o
2016-07-28 18:40 ` Eric W. Biederman
2016-07-29 9:23 ` One Thousand Gnomes
2016-07-29 9:58 ` Max Staudt
2016-07-29 17:38 ` Eric W. Biederman
2016-08-01 15:27 ` One Thousand Gnomes
2016-07-25 18:19 ` kbuild test robot
2016-07-26 11:47 ` [PATCHv2] " Max Staudt
2016-07-26 11:54 ` [PATCHv3] " Max Staudt
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=20160726150856.GA15676@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mstaudt@suse.de \
/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