Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
--- Begin Message ---
#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 lindi):
I think I just hit this bug twice on my gta02V5 with andy-tracking
a3587e4ed77974ad:
I was running gpsd on FR and streaming gps data over usb network to
laptop. GSM, bluetooth, wifi and backlight were all off. Twice during the
openstreetmap mapping trip the phone just froze and watchdog kicked in
after a while. ramconsole logs ended with
<7>[45124.025000] rxerr: port=1 ch=0xb1, rxs=0x00000007
<7>[45124.030000] rxerr: port=1 ch=0x2c, rxs=0x00000007
<7>[45124.035000] rxerr: port=1 ch=0x4e, rxs=0x00000004
<7>[45124.040000] rxerr: port=1 ch=0x2e, rxs=0x00000004
<7>[45124.045000] rxerr: port=1 ch=0x24, rxs=0x00000004
<7>[45124.050000] rxerr: port=1 ch=0x14, rxs=0x00000006
<7>[45124.055000] rxerr: port=1 ch=0x25, rxs=0x00000006
<7>[45124.060000] rxerr: port=1 ch=0x35, rxs=0x00000004
<7>[45124.065000] rxerr: port=1 ch=0x43, rxs=0x00000006
<7>[45124.070000] rxerr: port=1 ch=0x89, rxs=0x00000006
<7>[45124.075000] rxerr: port=1 ch=0xb1, rxs=0x00000006
<7>[45124.080000] rxerr: port=1 ch=0x2c, rxs=0x00000006
<7>[45124.085000] rxerr: port=1 ch=0x89, rxs=0x00000006
<7>[45124.090000] rxerr: port=1 ch=0x62, rxs=0x00000006
<7>[45124.095000] rxerr: port=1 ch=0x2c, rxs=0x00000006
<7>[45124.100000] rxerr: port=1 ch=0x89, rxs=0x00000006
<7>[45124.105000] rxerr: port=1 ch=0x62, rxs=0x00000006
<7>[45124.110000] rxerr: port=1 ch=0x2c, rxs=0x00000006
<7>[45124.115000] rxerr: port=1 ch=0x4a, rxs=0x00000006
<7>[45124.120000] rxerr: port=1 ch=0xaa, rxs=0x00000004
<7>[45124.125000] rxerr: port=1 ch=0x33, rxs=0x00000004
<7>[45124.130000] rxerr: port=1 ch=0xd2, rxs=0x00000004
<7>[45124.135000] rxerr: port=1 ch=0x41, rxs=0x00000005
<7>[45124.140000] rxerr: port=1 ch=0x56, rxs=0x00000005
<7>[45124.145000] rxerr: port=1 ch=0xd5, rxs=0x00000007
<7>[45124.150000] rxerr: port=1 ch=0xb1, rxs=0x00000007
<7>[45124.155000] rxerr: port=1 ch=0x2c, rxs=0x00000007
<7>[45124.160000] rxerr: port=1 ch=0x39, rxs=0x00000004
and
<7>[21474658.310000] rxerr: port=1 ch=0x50, rxs=0x00000004
<7>[21474658.310000] rxerr: port=1 ch=0x54, rxs=0x00000004
<7>[21474658.315000] rxerr: port=1 ch=0xb1, rxs=0x00000006
<7>[21474658.320000] rxerr: port=1 ch=0x2c, rxs=0x00000006
<7>[21474658.325000] rxerr: port=1 ch=0x89, rxs=0x00000006
<7>[21474658.330000] rxerr: port=1 ch=0x62, rxs=0x00000006
<7>[21474658.335000] rxerr: port=1 ch=0x30, rxs=0x00000004
<7>[21474658.340000] rxerr: port=1 ch=0x62, rxs=0x00000006
<7>[21474658.345000] rxerr: port=1 ch=0x30, rxs=0x00000004
<7>[21474658.350000] rxerr: port=1 ch=0x52, rxs=0x00000006
<7>[21474658.355000] rxerr: port=1 ch=0x34, rxs=0x00000006
<7>[21474658.360000] rxerr: port=1 ch=0x6a, rxs=0x00000006
I have not tried any of the patches yet since I need to figure out how to
make this bug occur again first.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:32>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
