From: Greg KH <gregkh@linuxfoundation.org>
To: "Mats Kärrman" <Mats.Karrman@tritech.se>
Cc: "linux-ppp@vger.kernel.org" <linux-ppp@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: Suspecting kernel timing bug in ppp or tty drivers
Date: Tue, 11 Mar 2014 18:50:19 +0000 [thread overview]
Message-ID: <20140311185019.GA32618@kroah.com> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C5B180A77@post.tritech.se>
On Tue, Mar 11, 2014 at 09:41:56AM +0000, Mats Kärrman wrote:
> On Monday, March 10, 2014 8:40 PM, Greg KH wrote:
> > On Mon, Mar 10, 2014 at 01:36:36PM +0000, Mats Kärrman wrote:
> >> Some data about the system:
> >> - PPP daemon v2.4.5
> >> - Linux kernel v3.2.51 (same error with v2.6.35 though)
> >
> > That's a really old kernel version, can you try 3.13 or newer? Lots of
> > work has been done in the tty layer since 3.2 was released.
> >
>
> Thanks for your reply Greg!
>
> For various reasons I'd prefer to go to the long-term release 3.12.y, would
> that be sufficient or do you think the changes made to 3.13 are critical?
It's a good place to start testing, and better than 3.2 :)
> (Btw. You recently set a tag for 3.12.14 but the tip of 3.12.y is 3.12.13
> according to git pull and kernel.org cgit, how come?)
I messed up and forgot to push the tree, should be fine now.
> As the MPC5125 is not main-line and I have some drivers for proprietary
> hardware the porting and re-testing will take me at least a week I guess.
Why aren't these drivers and arch code upstream?
greg k-h
next prev parent reply other threads:[~2014-03-11 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 13:36 Suspecting kernel timing bug in ppp or tty drivers Mats Kärrman
2014-03-10 19:40 ` Greg KH
2014-03-11 9:41 ` Mats Kärrman
2014-03-11 18:50 ` Greg KH [this message]
2014-03-12 7:54 ` Mats Kärrman
2014-03-12 12:14 ` terry white
2014-03-12 14:04 ` Peter Hurley
2014-03-25 9:51 ` Mats Kärrman
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=20140311185019.GA32618@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Mats.Karrman@tritech.se \
--cc=linux-ppp@vger.kernel.org \
--cc=linux-serial@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