8:22 a.m.
Hi all,
I have installed Fedora 19 rootfs on my OMAP5432 uEVM board and booted
successfully with a patched upstream kernel. Everything looks fine except
the following message when booting:
Starting Terminate Plymouth Boot Screen...
dm.c: 1701
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/usr/lib/python2.7/site-packages/initial_setup/__main__.py", line 5, in
<module>
from pyanaconda.users import Users
File "/usr/lib/python2.7/site-packages/pyanaconda/__init__.py", line 36, in
<module>
from pyanaconda.bootloader import get_bootloader
File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 32, in
<module>
from blivet.devicelibs import mdraid
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 68, in
<module>
from devices import *
File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 105, in
<module>
from devicelibs import dm
File "/usr/lib/python2.7/site-packages/blivet/devicelibs/dm.py", line 25, in
<module>
import block
File "/usr/lib/python2.7/site-packages/block/__init__.py", line 23, in
<module>
from device import MultiPath, RaidDev, RaidSet, BlockDev, DeviceMaps, \
File "/usr/lib/python2.7/site-packages/block/device.py", line 259, in
<module>
class MPNameCache(_IUD):
File "/usr/lib/python2.7/site-packages/block/device.py", line 264, in
MPNameCache
for map in _dm.maps():
MemoryError
[ 17.228284] usb 1-3: link qh8-0001/edcd9b80 start 2 [1/0 us]
[ 17.235653] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 18.703451] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 18.712073] smsc95xx 1-3:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
Although I don't think it is a big deal, is there anyone who could tell me
what problem it might be?
Thanks.
Chen Baozi
8:41 a.m.
On Thu, Aug 22, 2013 at 09:22:11PM +0800, Chen Baozi wrote:
File "/usr/lib/python2.7/site-packages/block/device.py",
line 264, in MPNameCache
for map in _dm.maps():
MemoryError
usually this is python running out of memory and a malloc failing.
Did you have swap enabled and attached at the time?
--Kyle
11:58 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 22 Aug 2013 09:41:24 -0400
Kyle McMartin <kyle(a)redhat.com> wrote:
On Thu, Aug 22, 2013 at 09:22:11PM +0800, Chen Baozi wrote:
> File "/usr/lib/python2.7/site-packages/block/device.py", line
> 264, in MPNameCache for map in _dm.maps():
> MemoryError
usually this is python running out of memory and a malloc failing.
Did you have swap enabled and attached at the time?
specifically this is initial-setup trying to run and failing. something
ive seen happen on some boards with small amounts of ram.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlIWQ1QACgkQkSxm47BaWfdPRQCgpr7filrQlmG6b/whtPYRvOWI
vkEAn3aod3p7JM/ubEYy3tcQlhiRt7gz
=zK8x
-----END PGP SIGNATURE-----
12:29 p.m.
Hiya,
We have seen initial-setup fail the same way for other boards with
less memory, and assumed it's a memory pressure type problem.
The OMAP5 uevm board contains 2 GiB of memory, and should not be
having this problem.
I would suggest open a BZ for this incident.
@Chen,
As a work around please mount the rootfs and change the root password
in the /etc/shadow file manually.
Thanks,
-Jon Disnard
fas: parasense
irc: masta
On Thu, Aug 22, 2013 at 11:58 AM, Dennis Gilmore <dennis(a)ausil.us> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 22 Aug 2013 09:41:24 -0400
Kyle McMartin <kyle(a)redhat.com> wrote:
> On Thu, Aug 22, 2013 at 09:22:11PM +0800, Chen Baozi wrote:
> > File "/usr/lib/python2.7/site-packages/block/device.py", line
> > 264, in MPNameCache for map in _dm.maps():
> > MemoryError
>
> usually this is python running out of memory and a malloc failing.
> Did you have swap enabled and attached at the time?
specifically this is initial-setup trying to run and failing. something
ive seen happen on some boards with small amounts of ram.
Dennis
--
-Jon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlIWQ1QACgkQkSxm47BaWfdPRQCgpr7filrQlmG6b/whtPYRvOWI
vkEAn3aod3p7JM/ubEYy3tcQlhiRt7gz
=zK8x
-----END PGP SIGNATURE-----
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
6:57 p.m.
On Aug 23, 2013, at 1:29 AM, Jon <jdisnard(a)gmail.com> wrote:
Hiya,
We have seen initial-setup fail the same way for other boards with
less memory, and assumed it's a memory pressure type problem.
The OMAP5 uevm board contains 2 GiB of memory, and should not be
having this problem.
I would suggest open a BZ for this incident.
@Chen,
As a work around please mount the rootfs and change the root password
in the /etc/shadow file manually.
Thanks, I've already done it. So everything running Fedora 19 is fine
except this problem, :)
Baozi
Thanks,
-Jon Disnard
fas: parasense
irc: masta
On Thu, Aug 22, 2013 at 11:58 AM, Dennis Gilmore <dennis(a)ausil.us> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, 22 Aug 2013 09:41:24 -0400
> Kyle McMartin <kyle(a)redhat.com> wrote:
>
>> On Thu, Aug 22, 2013 at 09:22:11PM +0800, Chen Baozi wrote:
>>> File "/usr/lib/python2.7/site-packages/block/device.py", line
>>> 264, in MPNameCache for map in _dm.maps():
>>> MemoryError
>>
>> usually this is python running out of memory and a malloc failing.
>> Did you have swap enabled and attached at the time?
>
> specifically this is initial-setup trying to run and failing. something
> ive seen happen on some boards with small amounts of ram.
>
> Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iEYEARECAAYFAlIWQ1QACgkQkSxm47BaWfdPRQCgpr7filrQlmG6b/whtPYRvOWI
> vkEAn3aod3p7JM/ubEYy3tcQlhiRt7gz
> =zK8x
> -----END PGP SIGNATURE-----
>
_______________________________________________
> arm mailing list
> arm(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm
--
-Jon
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm 
2:34 a.m.
On Fri, Aug 23, 2013 at 12:57 AM, Chen Baozi <baozich(a)gmail.com> wrote:
On Aug 23, 2013, at 1:29 AM, Jon <jdisnard(a)gmail.com> wrote:
> Hiya,
>
>
> We have seen initial-setup fail the same way for other boards with
> less memory, and assumed it's a memory pressure type problem.
>
> The OMAP5 uevm board contains 2 GiB of memory, and should not be
> having this problem.
>
> I would suggest open a BZ for this incident.
>
> @Chen,
> As a work around please mount the rootfs and change the root password
> in the /etc/shadow file manually.
Thanks, I've already done it. So everything running Fedora 19 is fine
except this problem, :)
Is that using the default Fedora kernel? If so which version?
Peter
3:23 a.m.
On Fri, Aug 23, 2013 at 08:34:25AM +0100, Peter Robinson wrote:
On Fri, Aug 23, 2013 at 12:57 AM, Chen Baozi
<baozich(a)gmail.com> wrote:
>
> On Aug 23, 2013, at 1:29 AM, Jon <jdisnard(a)gmail.com> wrote:
>
> > Hiya,
> >
> >
> > We have seen initial-setup fail the same way for other boards with
> > less memory, and assumed it's a memory pressure type problem.
> >
> > The OMAP5 uevm board contains 2 GiB of memory, and should not be
> > having this problem.
> >
> > I would suggest open a BZ for this incident.
> >
> > @Chen,
> > As a work around please mount the rootfs and change the root password
> > in the /etc/shadow file manually.
>
> Thanks, I've already done it. So everything running Fedora 19 is fine
> except this problem, :)
>
Is that using the default Fedora kernel? If so which version?
No, it isn't. I used the upstream kernel with some patches from TI branch
built by myself.
Interestingly, when I tried to boot dom0 under xen on OMAP5432, there is no
such problem.
Cheers,
Baozi
3:52 a.m.
On Fri, Aug 23, 2013 at 04:23:24PM +0800, Chen Baozi wrote:
On Fri, Aug 23, 2013 at 08:34:25AM +0100, Peter Robinson wrote:
> On Fri, Aug 23, 2013 at 12:57 AM, Chen Baozi <baozich(a)gmail.com> wrote:
>
> >
> > On Aug 23, 2013, at 1:29 AM, Jon <jdisnard(a)gmail.com> wrote:
> >
> > > Hiya,
> > >
> > >
> > > We have seen initial-setup fail the same way for other boards with
> > > less memory, and assumed it's a memory pressure type problem.
> > >
> > > The OMAP5 uevm board contains 2 GiB of memory, and should not be
> > > having this problem.
> > >
> > > I would suggest open a BZ for this incident.
> > >
> > > @Chen,
> > > As a work around please mount the rootfs and change the root password
> > > in the /etc/shadow file manually.
> >
> > Thanks, I've already done it. So everything running Fedora 19 is fine
> > except this problem, :)
> >
>
> Is that using the default Fedora kernel? If so which version?
No, it isn't. I used the upstream kernel with some patches from TI branch
built by myself.
Interestingly, when I tried to boot dom0 under xen on OMAP5432, there is no
such problem.
Sorry, it does still have. It was just overlaped by other logs.
Cheers,
Baozi
6:55 p.m.
On Aug 22, 2013, at 9:41 PM, Kyle McMartin <kyle(a)redhat.com> wrote:
On Thu, Aug 22, 2013 at 09:22:11PM +0800, Chen Baozi wrote:
> File "/usr/lib/python2.7/site-packages/block/device.py", line 264, in
MPNameCache
> for map in _dm.maps():
> MemoryError
usually this is python running out of memory and a malloc failing.
Did you have swap enabled and attached at the time?
No. But my board has 2GB physical memory…
Cheers,
Baozi
--Kyle
3892
days inactive
3893
days old
8 comments
5 participants
participants (5)
-
Chen Baozi -
Dennis Gilmore -
Jon -
Kyle McMartin -
Peter Robinson