From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Tim_T_Murphy@Dell.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG][2.6.8.1] serial driver hangs SMP kernel, but not the UP kernel
Date: Fri, 29 Oct 2004 22:14:12 +0100 [thread overview]
Message-ID: <20041029221412.K31627@flint.arm.linux.org.uk> (raw)
In-Reply-To: <4B0A1C17AA88F94289B0704CFABEF1AB0B4CC5@ausx2kmps304.aus.amer.dell.com>; from Tim_T_Murphy@Dell.com on Fri, Oct 29, 2004 at 04:04:40PM -0500
On Fri, Oct 29, 2004 at 04:04:40PM -0500, Tim_T_Murphy@Dell.com wrote:
> > Shouldn't 8250_pci setup the ports already for you? If not, what
> > needs to be done to achieve this. Using setserial to setup ports
> > for PCI cards isn't the preferred way of doing this.
>
> good question, i will have to understand more to answer it though.
> our product has used this method for almost 2 years now.
Well, if you forward lspci -vvx and the "maddr" and "irqno" information
(in private mail if you prefer) then I'll fix 8250_pci to work.
> > At a guess, you've enabled "low latency" setting on this port ?
>
> yes. here's a snippet from the script:
>
> echo -n "Starting ${racsvc}: "
> # set serial characteristics for RAC device
> setserial /dev/${ttyid} \
> port 0x${maddr} irq ${irqno} ^skip_test autoconfig
> setserial /dev/${ttyid} \
> uart 16550A low_latency baud_base 1382400 \
> close_delay 0 closing_wait infinite
> # now start pppd
> /sbin/modprobe -q ppp >/dev/null 2>&1
> /sbin/modprobe -q ppp_async >/dev/null 2>&1
> daemon pppd call ${service}
> RETVAL=$?
I think dropping low_latency will work around the problem for the time
being.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-10-29 21:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 21:04 [BUG][2.6.8.1] serial driver hangs SMP kernel, but not the UP kernel Tim_T_Murphy
2004-10-29 21:14 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 23:50 Tim_T_Murphy
2005-01-06 22:47 Tim_T_Murphy
2005-01-06 23:11 ` Alan Cox
2005-01-07 0:43 ` Paul Fulghum
2005-01-07 1:54 ` Alan Cox
2005-01-07 14:04 ` Paul Fulghum
2005-01-06 14:55 Tim_T_Murphy
2004-11-01 16:06 Tim_T_Murphy
2004-11-01 14:28 Tim_T_Murphy
2004-11-01 14:35 ` Russell King
2004-10-29 23:33 Tim_T_Murphy
2004-10-29 23:30 Tim_T_Murphy
2004-10-30 16:02 ` Russell King
2004-10-29 19:55 Tim_T_Murphy
2004-10-29 20:20 ` Russell King
2004-10-29 22:18 ` Paul Fulghum
2004-10-29 23:40 ` Paul Fulghum
2004-10-30 22:43 ` Alan Cox
2004-10-31 0:26 ` Paul Fulghum
2004-10-29 21:08 ` Paul Fulghum
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=20041029221412.K31627@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=Tim_T_Murphy@Dell.com \
--cc=linux-kernel@vger.kernel.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