Openmoko Bug #2180: stable-tracking: 'rxserr' UART messages

Openmoko Public Trac bugs at docs.openmoko.org
Tue Jan 20 15:59:04 CET 2009


#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
 Reporter:  laforge          |          Owner:  openmoko-kernel         
     Type:  defect           |         Status:  new                     
 Priority:  high             |      Milestone:  FSO                     
Component:  System Software  |        Version:                          
 Severity:  major            |       Keywords:  gps s3x24xx_serial rxerr
 Haspatch:  0                |      Blockedby:                          
Estimated:                   |    Patchreview:                          
 Blocking:                   |   Reproducible:                          
-----------------------------+----------------------------------------------

Comment(by andy):

 Understood...

 Jan 15 11:40:15 debian-gta02 kernel: rxerr: port ch=0x2c, rxs=0x00000001

 is just before the blowup

 got 552 bytes from:
 '061412",145,"00570061006C007400650072002000260020004D00610072006700720069007400680020002F0048"\r\n+CPBR:
 82,\x00"41794336783",145,"00570061006C00740065007200200026002000400680020002F004D"\r\n+CPBR:

 where it seems a \x00 byte appeared

 when I look at what the rxs thing is printing, it is the error status
 register, bit 1 suggests "overrun".  What exactly "overrun" means on a
 FIFO UART as a character error indication I dunno yet.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac


More information about the openmoko-kernel mailing list