From: Steven Cole <elenstev@mesatop.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Stephen Hemminger <shemminger@osdl.org>,
linux-kernel@vger.kernel.org,
Russell King <rmk+serial@arm.linux.org.uk>
Subject: Re: Problem with PPPD on dialup with 2.6.11-bk1 and later; 2.6.11 is OK
Date: Fri, 11 Mar 2005 17:51:21 -0700 [thread overview]
Message-ID: <200503111751.22138.elenstev@mesatop.com> (raw)
In-Reply-To: <4231FBFD.7000103@tmr.com>
On Friday 11 March 2005 01:13 pm, Bill Davidsen wrote:
> Stephen Hemminger wrote:
> >>Stephen Hemminger also wrote: (Someting's busted with serial in 2.6.11 latest)
> >>
> >>>Some checkin since 2.6.11 has caused the serial driver to
> >>>drop characters. Console output is chopped and messages are garbled.
> >>>Even the shell prompt gets truncated.
> >
> >
> >>Searching lkml archive, I found:
> >>http://marc.theaimsgroup.com/?l=linux-kernel&m=111031501416334&w=2
> >>
> >>I also found that reverting that patch made the problem go away for 2.6.11-bk1.
> >
> >
> >
> > Yes, this patch is the problem. A fix showed up today.
> > Current kernels work fine, thanks.
>
> Could someone who has the patch broken out send it to -stable? Serial
> not working is a non-trivial issue given the number of people who use
> dialup either full time or as a fallback connection.
>
The fix is in:
http://linus.bkbits.net:8080/linux-2.5/cset@422db58ceIvopUVZvMGAN6mhZZ3nPQ?nav=index.html|src/|src/drivers|src/drivers/serial|related/drivers/serial/8250.c
Since the breakage which this fix is for didn't appear until after 2.6.11,
a patch to 2.6.11.x is not required.
Steven
next prev parent reply other threads:[~2005-03-12 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 2:14 Steven Cole
2005-03-10 21:21 ` Stephen Hemminger
2005-03-11 20:13 ` Bill Davidsen
2005-03-12 0:51 ` Steven Cole [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 23:57 Steven Cole
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=200503111751.22138.elenstev@mesatop.com \
--to=elenstev@mesatop.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+serial@arm.linux.org.uk \
--cc=shemminger@osdl.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
all inboxes | Powered by JetHome®