From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Slaby Subject: Re: PROBLEM: Serial error Date: Tue, 27 May 2008 16:14:09 +0200 Message-ID: <483C1731.2060408@gmail.com> References: <1211836442.5745.1.camel@roswell.ausics.net> <483B3B7C.1000306@gmail.com> <483C0CDD.2000409@gmail.com> <1211895684.1698.10.camel@roswell.ausics.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from fg-out-1718.google.com ([72.14.220.153]:18527 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753689AbYE0OOK (ORCPT ); Tue, 27 May 2008 10:14:10 -0400 Received: by fg-out-1718.google.com with SMTP id 19so1533039fgg.17 for ; Tue, 27 May 2008 07:14:08 -0700 (PDT) In-Reply-To: <1211895684.1698.10.camel@roswell.ausics.net> Sender: linux-serial-owner@vger.kernel.org List-Id: linux-serial@vger.kernel.org To: "Noel (Sourceforge)" Cc: linux-kernel@vger.kernel.org, Alan Cox , linux-serial@vger.kernel.org Noel (Sourceforge) napsal(a): > On Tue, 2008-05-27 at 23:30, Jiri Slaby wrote: >> Jiri Slaby napsal(a): >>> On 05/26/2008 11:14 PM, Noel (Sourceforge) wrote: >>>> serial comms error with smsclient >2.6.25 , worked fine up until and >>>> including 2.6.24.7 >> There is >2.6.25. It means post 2.6.26-rc1 inclusively? >> > > Yes, it broke as of 2.6.25 , I also obtained .1 through .4 and still > broken in each, I have not tried 2.6.26-rc1 as I assume the code > breaking this is still in the tree > > > >> If you double checked this, trying to CC Alan if he doesn't have a clue. >> For reference: >> http://lkml.org/lkml/2008/5/26/260 > > Yes, checked. Ah, this one goes through platform driver (why do you load istallion and stallion drivers?). 8250.c driver changes: Alan Cox (3): serial: Coding style serial8250: coding style 8250: enable rate reporting via termios Will Newton (1): 8250.c: support specifying DW APB UARTs in device platform_data Nothing seems intrusive, but whatever changes in the rest of the serial might have caused it. Could you bisect it? I think it would be fast. git-bisect v2.6.25 v2.6.24 -- drivers/char/ drivers/serial/