Niels de Vos | 1 Nov 12:24 2011

Re: 11.3.0 release candidate 4 (build 883) released

Hi Gary,

On Mon, Oct 31, 2011 at 6:41 PM, Gary Martin <garycmartin <at> googlemail.com> wrote:
...
> I've just been testing Telescope-12 on the XO-1.75 running the new 883 build, first the good news, the
camera is showing up correctly in Record and Telescope, fab! :) Now the not so hot:
> - While in Telescope-12, clicking the digital zoom toolbar button completely locked up the XO-1.75
(re-testing with an XO-1 the digital zoom works ok).
> - After some waiting and many attempted keyboard shortcuts, I decided to power down. Clicking the power
hardware button did not trigger the usual shut down screen during this particular lockup case; clicking
the power button twice (assuming it might just be the gfx that had locked-up) had no effect; finally I held
down the power button for some seconds until the power led flashes and then the hard powers off.
> - On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown
metadata. None of the three entries allow invoking the details view or raise their palette so can not be
erased via the Sugar Journal UI. The three corrupt entries will be an entry for Browse where I visited
ASLO to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance
entry for the Telescope that was running when the XO locked up.
> Given the nature of the hard power off I understand why some data would not have been synched to disk, but
just wanted to raise this case here. I guess the actionable items might be:
> 1) fixing Telescope-12's digital zoom not to lock up an XO-1.75 (I don't have an XO-1.5 to test but I
re-checked on an XO-1 which still worked fine).
> 2) Seeing why the XO-1.75 hard crashed, I'm assuming something camera driver related may have borked
badly (I do have a serial cable here for un-bricking an XO-1.75 but don't know my way around that side of
things very well).

I tried to reproduce with Telescope, and I get an oops/hang as well.
The same oops is already filed as https://dev.laptop.org/ticket/11128.

Using a serial console for logging may show if it is a panic/crash or
a hang (like a very busy loop). If you unbricked your XO-1.75 with an
(Continue reading)

Niels de Vos | 1 Nov 12:49 2011

Re: 11.3.0 release candidate 4 (build 883) released

On Tue, Nov 1, 2011 at 11:24 AM, Niels de Vos <devos <at> fedoraproject.org> wrote:
> Hi Gary,
>
> On Mon, Oct 31, 2011 at 6:41 PM, Gary Martin <garycmartin <at> googlemail.com> wrote:
> ...
>> I've just been testing Telescope-12 on the XO-1.75 running the new 883 build, first the good news, the
camera is showing up correctly in Record and Telescope, fab! :) Now the not so hot:
>> - While in Telescope-12, clicking the digital zoom toolbar button completely locked up the XO-1.75
(re-testing with an XO-1 the digital zoom works ok).
>> - After some waiting and many attempted keyboard shortcuts, I decided to power down. Clicking the power
hardware button did not trigger the usual shut down screen during this particular lockup case; clicking
the power button twice (assuming it might just be the gfx that had locked-up) had no effect; finally I held
down the power button for some seconds until the power led flashes and then the hard powers off.
>> - On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown
metadata. None of the three entries allow invoking the details view or raise their palette so can not be
erased via the Sugar Journal UI. The three corrupt entries will be an entry for Browse where I visited
ASLO to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance
entry for the Telescope that was running when the XO locked up.
>> Given the nature of the hard power off I understand why some data would not have been synched to disk, but
just wanted to raise this case here. I guess the actionable items might be:
>> 1) fixing Telescope-12's digital zoom not to lock up an XO-1.75 (I don't have an XO-1.5 to test but I
re-checked on an XO-1 which still worked fine).
>> 2) Seeing why the XO-1.75 hard crashed, I'm assuming something camera driver related may have borked
badly (I do have a serial cable here for un-bricking an XO-1.75 but don't know my way around that side of
things very well).
>
> I tried to reproduce with Telescope, and I get an oops/hang as well.
> The same oops is already filed as https://dev.laptop.org/ticket/11128.
>
> Using a serial console for logging may show if it is a panic/crash or
(Continue reading)

Sascha Silbe | 1 Nov 13:02 2011

Re: [Sugar-devel] 11.3.0 release candidate 4 (build 883) released

Excerpts from Gary Martin's message of 2011-10-31 19:41:21 +0100:

> - On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown
metadata. None of the three entries allow invoking the details view or raise their palette so can not be
erased via the Sugar Journal UI. The three corrupt entries will be an entry for Browse where I visited ASLO
to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance entry
for the Telescope that was running when the XO locked up.

Please provide copies of shell.log and datastore.log and a tarball of
~/.sugar/default/datastore.

If the data store contains information you'd prefer not to make public,
you can send me the tarball privately (encrypted with my PGP key) or put
it on sunjammer for me to pick up. Otherwise please open a new ticket
[1] and attach the files there.

Sascha

[1] https://bugs.sugarlabs.org/newticket?component=sugar&version=0.94.x&severity=Major&distribution=OLPC
--

-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/
_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel
Gonzalo Odiard | 1 Nov 13:09 2011

Re: [Sugar-devel] 11.3.0 release candidate 4 (build 883) released

Reproduced here, datastore.log does not show anything, but shell.log show:

Trying to open Detail View:

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/jarabe/journal/journalactivity.py", line 206, in __detail_clicked_cb
    self._show_secondary_view(object_id)
  File "/usr/lib/python2.7/site-packages/jarabe/journal/journalactivity.py", line 228, in _show_secondary_view
    metadata = model.get(object_id)
  File "/usr/lib/python2.7/site-packages/jarabe/journal/model.py", line 551, in get
    metadata = _get_datastore().get_properties(object_id, byte_arrays=True)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.IOError: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/dbus/service.py", line 702, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/python2.7/site-packages/carquinyol/datastore.py", line 355, in get_properties
    metadata = self._metadata_store.retrieve(uid)
  File "/usr/lib/python2.7/site-packages/carquinyol/metadatastore.py", line 41, in retrieve
    return metadatareader.retrieve(metadata_path, properties)
IOError: Couldn't open metadata directory /home/olpc/.sugar/default/datastore///metadata

Moving the mouse over the icon:

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/sugar/graphics/palettewindow.py", line 939, in __motion_notify_event_cb
    self.notify_mouse_enter()
  File "/usr/lib/python2.7/site-packages/sugar/graphics/palettewindow.py", line 629, in notify_mouse_enter
    self._ensure_palette_exists()
  File "/usr/lib/python2.7/site-packages/sugar/graphics/palettewindow.py", line 624, in _ensure_palette_exists
    palette = self.parent.create_palette()
  File "/usr/lib/python2.7/site-packages/jarabe/journal/listview.py", line 615, in create_palette
    metadata = tree_model.get_metadata(self.props.palette_invoker.path)
  File "/usr/lib/python2.7/site-packages/jarabe/journal/listmodel.py", line 103, in get_metadata
    return model.get(self[path][ListModel.COLUMN_UID])
  File "/usr/lib/python2.7/site-packages/jarabe/journal/model.py", line 551, in get
    metadata = _get_datastore().get_properties(object_id, byte_arrays=True)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.IOError: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/dbus/service.py", line 702, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/python2.7/site-packages/carquinyol/datastore.py", line 355, in get_properties
    metadata = self._metadata_store.retrieve(uid)
  File "/usr/lib/python2.7/site-packages/carquinyol/metadatastore.py", line 41, in retrieve
    return metadatareader.retrieve(metadata_path, properties)
IOError: Couldn't open metadata directory /home/olpc/.sugar/default/datastore///metadata

Gonzalo


On Tue, Nov 1, 2011 at 9:02 AM, Sascha Silbe <sascha-ml-reply-to-2011-4 <at> silbe.org> wrote:
Excerpts from Gary Martin's message of 2011-10-31 19:41:21 +0100:

> - On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown metadata. None of the three entries allow invoking the details view or raise their palette so can not be erased via the Sugar Journal UI. The three corrupt entries will be an entry for Browse where I visited ASLO to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance entry for the Telescope that was running when the XO locked up.

Please provide copies of shell.log and datastore.log and a tarball of
~/.sugar/default/datastore.

If the data store contains information you'd prefer not to make public,
you can send me the tarball privately (encrypted with my PGP key) or put
it on sunjammer for me to pick up. Otherwise please open a new ticket
[1] and attach the files there.

Sascha

[1] https://bugs.sugarlabs.org/newticket?component=sugar&version=0.94.x&severity=Major&distribution=OLPC
--
http://sascha.silbe.org/
http://www.infra-silbe.de/

_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel


_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel
Gonzalo Odiard | 1 Nov 13:46 2011

Re: [Sugar-devel] 11.3.0 release candidate 4 (build 883) released

New ticket #11372 was created with the content of a corrupted datastore.

Gonzalo

_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel
Paul Fox | 1 Nov 15:47 2011

XO bluetooth support

it seems that there's more interest in bluetooth support on the XO
laptops than there has been in the past -- unsurprising, i guess,
given the number of bt devices now available.

i don't know how quickly we can get the support into an OLPC release, but
regardless, i'd like to solicit input on what support, exactly, we
should provide in the kernel.  i know that i, personally, don't know
the linux bluetooth stack well enough to know what kernel modules are
required.

userspace support is a different, somewhat less pressing issue, since
yum update works for many (but not all, i realize) of our users.

please update http://dev.laptop.org/ticket/11285 with specific
suggestions or requirements.  if someone would like to open an
equivalent ticket for userspace package requirements, that would be
dandy as well.

thanks!
paul
=---------------------
 paul fox, pgf <at> laptop.org
Peter Robinson | 1 Nov 15:58 2011
Picon

Re: XO bluetooth support

On Tue, Nov 1, 2011 at 2:47 PM, Paul Fox <pgf <at> laptop.org> wrote:
> it seems that there's more interest in bluetooth support on the XO
> laptops than there has been in the past -- unsurprising, i guess,
> given the number of bt devices now available.
>
> i don't know how quickly we can get the support into an OLPC release, but
> regardless, i'd like to solicit input on what support, exactly, we
> should provide in the kernel.  i know that i, personally, don't know
> the linux bluetooth stack well enough to know what kernel modules are
> required.
>
> userspace support is a different, somewhat less pressing issue, since
> yum update works for many (but not all, i realize) of our users.
>
> please update http://dev.laptop.org/ticket/11285 with specific
> suggestions or requirements.  if someone would like to open an
> equivalent ticket for userspace package requirements, that would be
> dandy as well.

Might be worth replicating the options that Fedora uses to ensure we
have a reproducible and stable as environment as upstream has to
ensure we have the least issues.

Peter
Kevin Gordon | 1 Nov 16:08 2011
Picon

Re: XO bluetooth support


On Tue, Nov 1, 2011 at 10:58 AM, Peter Robinson <pbrobinson <at> gmail.com> wrote:
On Tue, Nov 1, 2011 at 2:47 PM, Paul Fox <pgf <at> laptop.org> wrote:
> it seems that there's more interest in bluetooth support on the XO
> laptops than there has been in the past -- unsurprising, i guess,
> given the number of bt devices now available.
>
> i don't know how quickly we can get the support into an OLPC release, but
> regardless, i'd like to solicit input on what support, exactly, we
> should provide in the kernel.  i know that i, personally, don't know
> the linux bluetooth stack well enough to know what kernel modules are
> required.
>
> userspace support is a different, somewhat less pressing issue, since
> yum update works for many (but not all, i realize) of our users.
>
> please update http://dev.laptop.org/ticket/11285 with specific
> suggestions or requirements.  if someone would like to open an
> equivalent ticket for userspace package requirements, that would be
> dandy as well.

Might be worth replicating the options that Fedora uses to ensure we
have a reproducible and stable as environment as upstream has to
ensure we have the least issues.

Peter

 
I have a few various manufacturers'  USB Bluetooth adapters.  Want me to plug them in and see what dmesg spits out?  Or, were you thinking of going built-in?
 
_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel

_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel
Paul Fox | 1 Nov 16:23 2011

Re: XO bluetooth support

kevin wrote:
 > On Tue, Nov 1, 2011 at 10:58 AM, Peter Robinson <pbrobinson <at> gmail.com>wrote:
 > 
 > > On Tue, Nov 1, 2011 at 2:47 PM, Paul Fox <pgf <at> laptop.org> wrote:
 > > > it seems that there's more interest in bluetooth support on the XO
 > > > laptops than there has been in the past -- unsurprising, i guess,
 > > > given the number of bt devices now available.
 > > >
 > > > i don't know how quickly we can get the support into an OLPC release, but
 > > > regardless, i'd like to solicit input on what support, exactly, we
 > > > should provide in the kernel.  i know that i, personally, don't know
 > > > the linux bluetooth stack well enough to know what kernel modules are
 > > > required.
 > > >
 > > > userspace support is a different, somewhat less pressing issue, since
 > > > yum update works for many (but not all, i realize) of our users.
 > > >
 > > > please update http://dev.laptop.org/ticket/11285 with specific
 > > > suggestions or requirements.  if someone would like to open an
 > > > equivalent ticket for userspace package requirements, that would be
 > > > dandy as well.
 > >
 > > Might be worth replicating the options that Fedora uses to ensure we
 > > have a reproducible and stable as environment as upstream has to
 > > ensure we have the least issues.
 > >
 > > Peter
 > >
 > I have a few various manufacturers'  USB Bluetooth adapters.  Want me to
 > plug them in and see what dmesg spits out?  Or, were you thinking of going
 > built-in?

no, this isn't about hardware changes -- we're not planning any bluetooth
hardware.

i suspect peter is right, that we should simply include the
fedora options, unless someone knowledgeable can say "so-and-so
module is only there to support archaic devices that haven't been
in use for many years".

again, please update the trac ticket with any pertinent info.

paul

 > 
 > 
 > > _______________________________________________
 > > Devel mailing list
 > > Devel <at> lists.laptop.org
 > > http://lists.laptop.org/listinfo/devel
 > >

=---------------------
 paul fox, pgf <at> laptop.org
Sridhar Dhanapalan | 1 Nov 22:04 2011
Picon

XO-1.75 relative performance

I am trying to get some idea of the performance of the XO-1.75
relative to other devices on the market.

For instance, how would it compare against an iPad 1/2 and iPhone
4/4S? My guess is that the Armada 610 SoC that we use would come out
somewhere in between the A4 chip used in the original iPad and iPhone
4, and the A5 chip used in the iPad 2 and iPhone 4S.

Do we have any more accurate figures? How does the state of our
software (quality of drivers, etc.) affect this?

There's a cool demo online showing the graphics capabilities of the
Armada 610[0]. Is this achievable on the XO-1.75?

Thanks,
Sridhar

[0] http://www.youtube.com/watch?v=1s17KwfzTFY

Gmane