All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Steven Cole <elenstev@mesatop.com>,
	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 15:13:49 -0500	[thread overview]
Message-ID: <4231FBFD.7000103@tmr.com> (raw)
In-Reply-To: <20050310132114.5eda19d7@dxpl.pdx.osdl.net>

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.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-03-11 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10  2:14 Problem with PPPD on dialup with 2.6.11-bk1 and later; 2.6.11 is OK Steven Cole
2005-03-10 21:21 ` Stephen Hemminger
2005-03-11 20:13   ` Bill Davidsen [this message]
2005-03-12  0:51     ` Steven Cole
  -- 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=4231FBFD.7000103@tmr.com \
    --to=davidsen@tmr.com \
    --cc=elenstev@mesatop.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 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.