[OLPC New Zealand] [Testing] Testing Summary, Auckland - 21 April 2012

Kevin Gordon kgordon420 at gmail.com
Tue Apr 24 10:54:05 EDT 2012


On Tue, Apr 24, 2012 at 6:46 AM, Tabitha Roder <tabitha at tabitha.net.nz>wrote:

> Testing Summary, Auckland - 21 April 2012
> Who: Elaine, John, Oliver, Tabitha, Tom
>
> 12.1.0 os7 on XO-1.75
> Sundance (C1 model) had the wifi driver crash shortly after or maybe
> during boot. Symptoms was no eth0 in ifconfig. This doesn’t appear to
> be exactly the same as http://dev.laptop.org/ticket/11778 fixed in os8
> but perhaps it has the same root cause and is fixed too? We only saw
> this problem on Sundance, we didn't see any wifi disturbances in our
> other XO-1.75s (which are C2 models). There is more of this dmesg
> trace if anyone is interested.
>
> Apr 20 23:30:23 (none) udisksd[734]: Acquired the name
> org.freedesktop.UDisks2 on the system message bus
> Apr 20 23:30:54 (none) kernel: [   37.848677] PM: Syncing filesystems ...
> done.
> Apr 20 23:30:54 (none) kernel: [   37.851363] Freezing user space
> processes ...
> Apr 20 23:30:54 (none) kernel: [   57.862935] Freezing of tasks failed
> after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0):
> Apr 20 23:30:54 (none) kernel: [   57.862961] udevd           D
> c0388ecc     0   196    164 0x000a0001
> Apr 20 23:30:54 (none) kernel: [   57.863026] [<c0388ecc>]
> (__schedule+0x31c/0x3a8) from [<c0389750>]
> (schedule_timeout+0x18/0x1d8)
> Apr 20 23:30:54 (none) kernel: [   57.863056] [<c0389750>]
> (schedule_timeout+0x18/0x1d8) from [<c0389120>]
> (wait_for_common+0xc8/0x1ac)
> Apr 20 23:30:54 (none) kernel: [   57.863096] [<c0389120>]
> (wait_for_common+0xc8/0x1ac) from [<c01e09e0>]
> (_request_firmware+0x2c8/0x3ec)
> Apr 20 23:30:54 (none) kernel: [   57.863126] [<c01e09e0>]
> (_request_firmware+0x2c8/0x3ec) from [<c01e0b18>]
> (request_firmware+0x14/0x18)
> Apr 20 23:30:54 (none) kernel: [   57.863202] [<c01e0b18>]
> (request_firmware+0x14/0x18) from [<bf040e84>]
> (lbs_get_firmware+0xe4/0x1b8 [libertas])
> Apr 20 23:30:54 (none) kernel: [   57.863271] [<bf040e84>]
> (lbs_get_firmware+0xe4/0x1b8 [libertas]) from [<bf05897c>]
> (if_sdio_probe+0x528/0xfa8 [libertas_sdio])
> Apr 20 23:30:54 (none) kernel: [   57.863309] [<bf05897c>]
> (if_sdio_probe+0x528/0xfa8 [libertas_sdio]) from [<c025ea88>]
> (sdio_bus_probe+0x8c/0xf8)
> Apr 20 23:30:54 (none) kernel: [   57.863345] [<c025ea88>]
> (sdio_bus_probe+0x8c/0xf8) from [<c01d6d74>]
> (driver_probe_device+0x134/0x274)
> Apr 20 23:30:54 (none) kernel: [   57.863373] [<c01d6d74>]
> (driver_probe_device+0x134/0x274) from [<c01d6f1c>]
> (__driver_attach+0x68/0x8c)
> Apr 20 23:30:54 (none) kernel: [   57.863401] [<c01d6f1c>]
> (__driver_attach+0x68/0x8c) from [<c01d5b88>]
> (bus_for_each_dev+0x48/0x8c)
> Apr 20 23:30:54 (none) kernel: [   57.863428] [<c01d5b88>]
> (bus_for_each_dev+0x48/0x8c) from [<c01d6570>]
> (bus_add_driver+0xec/0x258)
> Apr 20 23:30:54 (none) kernel: [   57.863455] [<c01d6570>]
> (bus_add_driver+0xec/0x258) from [<c01d7444>]
> (driver_register+0xa8/0x130)
> Apr 20 23:30:54 (none) kernel: [   57.863489] [<c01d7444>]
> (driver_register+0xa8/0x130) from [<bf05d070>]
> (if_sdio_init_module+0x70/0x110 [libertas_sdio])
> Apr 20 23:30:54 (none) kernel: [   57.863534] [<bf05d070>]
> (if_sdio_init_module+0x70/0x110 [libertas_sdio]) from [<c002a414>]
> (do_one_initcall+0x90/0x160)
> Apr 20 23:30:54 (none) kernel: [   57.863571] [<c002a414>]
> (do_one_initcall+0x90/0x160) from [<c0074240>]
> (sys_init_module+0x15d4/0x1764)
> Apr 20 23:30:54 (none) kernel: [   57.863603] [<c0074240>]
> (sys_init_module+0x15d4/0x1764) from [<c0030180>]
> (ret_fast_syscall+0x0/0x30)
>
> Browse is still very unstable. Logging in to google docs causes it to
> crash on the first document list screen after login.
> http://blog.makezine.com causes it to crash. Last time I tried
> slashdot also caused it to crash, but this time it didn’t, so I guess
> the problem does depend on exactly what the website is showing. In
> every case where browse crashed, it still appeared as the active
> activity in the center of the home screen even though it had
> disappeared.
>
> Firefox 10 installed via yum worked well on google docs.
>
> Build 215 11.3.1-au on XO-1.5:
> The release notes at
> http://dev.laptop.org.au/projects/xo-au/wiki/120_release_notes don’t
> explain the changes since RC2
>
> The new startup and shutdown screens are cute.
> write colours change ok, type face size change ok, type  bold italic
> underline ok, insert table ok
> write start from journal ok
> browse worked
> Moon works
> Memorize works when playing alone but couldnt collaborate - appears in
> neighbourhood but doesn’t join properly
> Maze works
> Speak works - collaborate voice chat works
> Record - took and viewed picture, took and viewed video
> implode - works
> visual match works
> clock - it says what time is it on bottom of screen but there is no
> further writing, talking clock says what time is it but doesn’t tell
> you the time
> numbers works
> physics works
> stopwatch works
> ruler works
> measure - first time the lines were massive, restart with start new
> and there is no lines, on laptop restart seems to be resolved
> tam tam mini works
> arithmetic works
> poll works
> tuxmath works
> tuxpaint works - drew, wrote, stamped and saved
> help works
> spirolaterals works
> chat started by ivy - could join and see ivy and poppycopy
> fototoon works
>
> We experienced the usual collaboration problems on AP wifi with
> internet access, some laptops could see each other in the
> neighbourhood and some could not.


If this is not relevant, please ignore ....  :-)

In our little test ab we have also experienced some anomalies in the
neighbourhood view.  We experienced that with certain AP's - after about 8
laptops come up and are attached to the WPA2 AP - that the neighbourhood
view on the laptops no longer consistently or reliably shows all of the
laptops.  Seems to vary between 8 and 10 showing on the screen before it
stops.  However, all of the newly joined laptops (we use 20) can still get
out to the internet through the AP, and all can still ping each other.

Unfortunately, this symptom seems to appear only on our TP-link running
Open WRT and our Buffalo running DD-WRT.  The view shows all 20 of the
laptops when we use our Cisco or Cradlepoint AP's - both of which are
running their proprietary firmware.  We have a tech volunteer here who is
investigating whether there might be a setting within the open-source
firmware for the TP-Link and Buffaloes that might better be able to handle
these items.    One theory he is exploring is whether the AP is fracking
the multicast.  However, we have no experimental proof as to the real cause
yet.

Perhaps also of interest is that all 20 also show up perfectly in the
neighbourhood view if we use ad-hoc instead of the AP, ,as they are powered
up one after the other.  Also, for this test, we are running these machines
all at build 883, so and they are a mix of 1.0s and 1.5s.  So, for us, this
symptom is neither F17 not 1.75 dependent.  We have also found that
deleting the network history before each test invocation helps to not have
a 'moving target'.

Further, we have done no testing on collaboration, at present we are just
looking longingly at the pretty screen of neighbourhood view , in these
various AP environments, since our present goal is to select a robust , yet
affordable, AP.

Cheers

KG


> The following error was found in
> shell.log on the laptop which could see the fewest other laptops,
> maybe it is relevant?
> ---------------------------------------------------------------------------
> KeyError                                  Traceback (most recent call last)
>
> /usr/lib/python2.7/site-packages/jarabe/desktop/meshbox.pyo in
> _buddy_removed_cb(self=<MeshBox object at 0x943af54 (SugarMeshBox at
> 0x9528000)>, model=<Neighborhood object at 0x943af7c
> (jarabe+model+neighborhood+Neighborhood at 0x94aa550)>,
> buddy_model=<BuddyModel object at 0x98bfe64 (SugarBuddyModel at
> 0x965d970)>)
>    476
>    477     def _buddy_removed_cb(self, model, buddy_model):
> --> 478         self._remove_buddy(buddy_model)
>    479
>    480     def _activity_added_cb(self, model, activity_model):
>
> /usr/lib/python2.7/site-packages/jarabe/desktop/meshbox.pyo in
> _remove_buddy(self=<MeshBox object at 0x943af54 (SugarMeshBox at
> 0x9528000)>, buddy_model=<BuddyModel object at 0x98bfe64
> (SugarBuddyModel at 0x965d970)>)
>    501     def _remove_buddy(self, buddy_model):
>    502         logging.debug('MeshBox._remove_buddy')
> --> 503         icon = self._buddies[buddy_model.props.key]
>    504         self._layout.remove(icon)
>    505         del self._buddies[buddy_model.props.key]
>
> KeyError:
> dbus.ByteArray('AAAAB3NzaC1kc3MAAACBAJWiIvUwljHfFgstBHomgdpIruyznshP9c5o/CU1jdOGJHxuWvf+oU7amc8Y7rMU4O0qu08epYEtXOehQ+5qkWQUkc4VNp9/dtFWaLuJKtlvWji6Vweb30+V+h7k3XWWYDNKYMxy6tsTxFwgogs5UyFsYwamI4AyM31G4Zhi43wDAAAAFQCWvYrgJehqtpBXsk6xkfJkVH9HuQAAAIBbfKn+M5dvh37qI1O8iuNOUkt5VylDTBuaMTn9KHoKUaHfiF7XuTayRRSNm0Aq9MRMud+aW4YTl5Lma2LMH1zf+d95+Rz4ZQBW86zcxqY+JYFjGZPfQWx7NiYGqP5Wn6ywkz9vIvdiM1ezXZvDWSNhZB3VBURFCyGSPSiiissOAQAAAIAmFexQH2n12a//vgf4MztFuHTUN5/qATlu3z2rFZtrXFLDU+tPD4XQkwcqqCJPf64eaxGS6epLWpcDJgcq016+W1tneB6eApYwSUBq+d1CLYFXbKXW1gPMLgBOndImt5UxhyoBm4vb7yZIkAxrltr4IgUXEEDslDvfl/WYm2YulQ==',
> variant_level=1)
> 1334968899.686694 WARNING root: No gtk.AccelGroup in the top level window.
> 1334968899.687723 WARNING root: No gtk.AccelGroup in the top level window.
> 1334968903.151219 ERROR dbus.connection: Exception in handler for D-Bus
> signal:
> Traceback (most recent call last):
>  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 214,
> in maybe_handle_message
>    self._handler(*args, **kwargs)
>  File "/usr/lib/python2.7/site-packages/jarabe/model/neighborhood.py",
> line 455, in __buddy_activities_changed_cb
>    self._update_buddy_activities(buddy_handle, activities)
>  File "/usr/lib/python2.7/site-packages/jarabe/model/neighborhood.py",
> line 516, in _update_buddy_activities
>    self._remove_buddy_from_activity(buddy_handle, activity_id)
>  File "/usr/lib/python2.7/site-packages/jarabe/model/neighborhood.py",
> line 533, in _remove_buddy_from_activity
>    self._buddy_handles[buddy_handle],
> KeyError: dbus.UInt32(3L)
> 1334969021.092348 WARNING root: _Account.__set_current_activity_cb
>
> The timezone in Date & Time in my settings does not scroll to make the
> selected timezone visible when you open the dialog and also when you
> use the search box.
>
> The following error appears in log of Record and Browse every time we quit:
> ---------------------------------------------------------------------------
> OSError                                   Traceback (most recent call last)
>
> /usr/lib/python2.7/site-packages/dbus/connection.pyo in
> msg_reply_handler(message=<dbus.lowlevel.MethodReturnMessage object>)
>    584         def msg_reply_handler(message):
>    585             if isinstance(message, MethodReturnMessage):
> --> 586
>                 reply_handler(*message.get_args_list(**get_args_opts))
>    587             elif isinstance(message, ErrorMessage):
>    588
> error_handler(DBusException(name=message.get_error_name(),
>
> /usr/lib/python2.7/site-packages/sugar/activity/activity.pyo in
> __save_cb(self=<Record object at 0x994d374 (SugarActivity at
> 0x9715988)>)
>    582             self._session.will_quit(self, True)
>    583         elif self._closing:
> --> 584             self._complete_close()
>    585
>    586     def __save_error_cb(self, err):
>
> /usr/lib/python2.7/site-packages/sugar/activity/activity.pyo in
> _complete_close(self=<Record object at 0x994d374 (SugarActivity at
> 0x9715988)>)
>    887         if os.path.exists(POWERD_INHIBIT_DIR):
>    888             path = os.path.join(POWERD_INHIBIT_DIR,
> str(os.getpid()))
> --> 889             os.unlink(path)
>    890
>    891     def close(self, skip_save=False):
>
> OSError: [Errno 2] No such file or directory:
> '/var/run/powerd-inhibit-suspend/3109'
> Exited with status 0, pid 3109 data (None, <open file '<fdopen>', mode
> 'w' at 0xab894f0>,
> '/home/olpc/.sugar/default/logs/org.laptop.RecordActivity-1.log',
> 'bfa3e93b40825d2a603af2cc8ddec11d60f6d551')
>
> Measure on Ivy and Rosella behaves differently. With the same input
> settings, Ivy has a much lower level even with the laptops side by
> side and even after swapping them so it isn’t a position effect. Tank
> is like Ivy.  Has there been a change to the audio hardware? Ivy is an
> early production XO-1.5 SKU99, Tank is an even earlier XO-1.5_C2,
> Rosella is a recent production XO-1.5 (made late 2011 I believe?).
> It’s not clear which motherboard they have, the first line of the Open
> Firmware prompt starts OLPC D4 on Ivy and OLPC DA on Rosella, is this
> the Open Firmware “cpu-model” referred to on
> http://wiki.laptop.org/go/XO_1.5_C5 and friends?
>
> There doesn’t seem to be a way to control the sound level in record
> when recording sound or video.
>
> Browse seems to have the same error logged on quit that we see in
> Record, but we also see the following error on every startup:
> Error in sys.excepthook:
> Traceback (most recent call last):
>  File "/usr/lib/python2.7/site-packages/sugar/logger.py", line 72, in
> _except_hook
>    from IPython.ultraTB import AutoFormattedTB
> RuntimeError: maximum recursion depth exceeded
>
> Original exception was:
> RuntimeError: maximum recursion depth exceeded
> Error in sys.excepthook:
> Traceback (most recent call last):
>  File "/usr/lib/python2.7/site-packages/sugar/logger.py", line 72, in
> _except_hook
>    from IPython.ultraTB import AutoFormattedTB
> RuntimeError: maximum recursion depth exceeded
>
> The openfirmware power log collector did not work on the Australian
> build, complaining:
> <buffer at ....>:194: Can’t open directory
> The /home/olpc/power-logs directory exists. It worked ok on the
> XO-1.75 and they are attached.
>
> Kind regards
> Tabitha Roder
>
> _______________________________________________
> Testing mailing list
> Testing at lists.laptop.org
> http://lists.laptop.org/listinfo/testing
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/olpc-nz/attachments/20120424/4166f6d2/attachment-0001.html>


More information about the OLPC-NZ mailing list