lkml.org 
[lkml]   [2011]   [Aug]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Very strange data loss with jsm driver
    On 08/02/2011 11:22 AM, Lennart Sorensen wrote:
    > On Tue, Aug 02, 2011 at 11:17:52AM -0300, Breno Leitao wrote:
    > > Well, I finally tested it over here, and what I found is:
    > >
    > > If the line has a \r among the first 16 bytes, then the information
    > > is TXed immediately. If there is no \r in the first 16 bytes, then the
    > > information seems to be buffered.
    >
    > Where in the driver is this happening?
    Well, I just found it doing some test cases.

    Enabling the driver debug, I found that ->intr is not being called on
    the "incorrect" case.

    This is the diff of the logs:

    jsm 0005:02:00.0: finish
    jsm 0005:02:00.0: start
    jsm 0005:02:00.0: finish
    -jsm 0005:02:00.0: drivers/tty/serial/jsm/jsm_neo.c:1131 uart_poll: 301
    -jsm 0005:02:00.0: drivers/tty/serial/jsm/jsm_neo.c:1161 port: 0 type: 3
    -jsm 0005:02:00.0: drivers/tty/serial/jsm/jsm_neo.c:750 isr: 2
    -jsm 0005:02:00.0: MOD_STAT: sending to parse_modem_sigs
    -jsm 0005:02:00.0: neo_parse_modem: port: 0 msignals: 0
    -jsm 0005:02:00.0: Port: 0 DTR: 0 RTS: 0 CTS: 0 DSR: 0 RI: 0 CD: 0
    jsm 0005:02:00.0: start
    jsm 0005:02:00.0: Close. HUPCL set, dropping DTR/RTS
    jsm 0005:02:00.0: finish
    -jsm 0005:02:00.0: finish.

    Anyway, I am still debugging it.

    PS: I will look at the stats regression after I fix this one, ok ?



    \
     
     \ /
      Last update: 2011-08-02 16:53    [W:0.021 / U:30.216 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site