public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: folkert <folkert@vanheusden.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: 2.6.25 upgraded to 2.6.36: serial app stops working
Date: Tue, 30 Nov 2010 08:42:32 -0800	[thread overview]
Message-ID: <20101130164232.GB18017@kroah.com> (raw)
In-Reply-To: <20101130162754.GI5654@belle.intranet.vanheusden.com>

On Tue, Nov 30, 2010 at 05:27:55PM +0100, folkert wrote:
> Hi,
> 
> I upgraded my linux system to 2.6.36. Now suddenly my serial driver for
> my MSF receiver stopped working. Two things I noticed: I need to open
> the serial device (/dev/ttyS0, a regular uart, see below) with O_NDELAY
> for open() to return at all. Then something funny happens: I read bytes
> from the device (at 50bps) which runs fine for a while but then suddenly
> I get a burst of '0x00' bytes - precisely at the point at which the MSF
> radio device sends a timecode! So I think the device fiddles with one of
> the pins of the serial port confusing the linux serial driver. This
> worked fine upto and including 2.6.25 (maybe later too) but with 2.6.36
> this fails.
> Anyone an idea what might go wrong here? And how to fix it?

Any chance you could use 'git bisect' on the kernel tree to see what
caused the change?  Moving from .25 to .36 is a huge jump, many many
years of development and loads of things have changed so we need some
help to narrow the problem down.

thanks,

greg k-h

  reply	other threads:[~2010-11-30 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 16:27 2.6.25 upgraded to 2.6.36: serial app stops working folkert
2010-11-30 16:42 ` Greg KH [this message]
2012-06-27 20:26   ` folkert
2010-12-07 12:08 ` folkert

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=20101130164232.GB18017@kroah.com \
    --to=greg@kroah.com \
    --cc=folkert@vanheusden.com \
    --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