@maresh
no, there are no hardcoded dependencies beyond the basic boot setup, as long as
the fis partitioning is the same and initramfs is used as explained above there
should be no issues.
your description sounds like a race between kernel and hardware (timing issue)
...
my theory would be
Could you please attach the updated Babbage 2 RedBoot as well? I tried
reproducing, but I can't boot using the B1 RedBoot.
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I didn't find the 200925 RedBoot source drop, only 200918; are you
blocking on this for release?
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I took a rootfs with GNOME I had prepared for Babbage 2 which was
working fine there, moved that to Babbage 1; it's on a SATA disk which I
plug via an USB adapter. I could boot this using the new RedBoot
attached to this bug report (candidate 200925 I guess) and it would
trigger the described
I confirmed that I'm using the proper RedBoot versions above; with FSL
200918 - built 09:45:10, Apr 29 2009 I still get the bug. This is FSL
binary.
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of
: Tuesday, June 30, 2009 9:12 AM
To: Mahadevan Mahesh-R9AADQ
Subject: [Bug 392716] Re: notification area applets crash on login
I didn't find the 200925 RedBoot source drop, only 200918; are you
blocking on this for release?
--
notification area applets crash on login
https://bugs.launchpad.net/bugs
Still with the same kernel, I tried with Ubuntu's RedBoot FSL 200910 -
built 14:12:08, Apr 7 2009 as extracted from the jaunty/karmic
redboot-imx51-babbage 200910-0ubuntu2 armel .deb and I don't get the
issue. (I only get the mixer applet warning which is due to lack of
sound support.)
--
To: Mahadevan Mahesh-R9AADQ
Subject: [Bug 392716] Re: notification area applets crash on login
Could you please attach the updated Babbage 2 RedBoot as well? I tried
reproducing, but I can't boot using the B1 RedBoot.
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
So this time the dmesg was different! I see this delta:
-mc13892 Rev 0.0 FinVer 0 detected
+mc13892 Rev 1.1 FinVer 0 detected
and this:
-eth0: ethernet 00:00:00:00:00:00
+eth0: ethernet 00:00:45:67:89:ab
There is a difference though: I did a hot reboot instead of a cold reboot. In
particular
30, 2009 10:03 AM
To: Mahadevan Mahesh-R9AADQ
Subject: [Bug 392716] Re: notification area applets crash on login
I took a rootfs with GNOME I had prepared for Babbage 2 which was
working fine there, moved that to Babbage 1; it's on a SATA disk which I
plug via an USB adapter. I could boot
So in all bad boots, eth0's HWaddr was 00:00:00:00:00:00, and in all
good boots it was set properly; I think this just indicates that RedBoot
does more platform init in the old Ubuntu versions than in the newer FSL
binaries.
--
notification area applets crash on login
To: Mahadevan Mahesh-R9AADQ
Subject: [Bug 392716] Re: notification area applets crash on login
I confirmed that I'm using the proper RedBoot versions above; with FSL
200918 - built 09:45:10, Apr 29 2009 I still get the bug. This is FSL binary.
--
notification area applets crash on login
https
Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Loïc
Minier
Sent: Tuesday, June 30, 2009 10:21 AM
To: Mahadevan Mahesh-R9AADQ
Subject: [Bug 392716] Re: notification area applets crash on login
Still with the same kernel, I tried with Ubuntu's RedBoot FSL 200910
Comparing a good cold and hot reboot, I saw no big difference; mostly timing
and clock:
-pmic_rtc pmic_rtc.1: setting system clock to 2009-06-30 15:22:04 UTC
(1246375324)
+pmic_rtc pmic_rtc.1: setting system clock to 1970-01-01 00:00:21 UTC (21)
--
notification area applets crash on login
Including Alan in the e-mail thread.
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Loïc
Minier
Sent: Tuesday, June 30, 2009 10:26 AM
To: Mahadevan Mahesh-R9AADQ
Subject: [Bug 392716] Re: notification area applets crash on login
So this time
Ok, I booted with RedBoot 200918, still got the issue, stopped gdm,
checked the date and it was Tue Aug 14 06:58:02 WEST 1923.
I set the date with date -s, restarted gdm, and didn't have the issue
anymore.
I tried resetting the date to 'Tue Aug 14 06:58:02 WEST 1923', but could
NOT as it's an
So my understanding is:
- some redboot + kernel combo doesn't set RTC correctly on boot anymore; it
looks like it's because the I2C chip isn't initialized properly:
redboot-200918/dmesg-bad:sgtl5000-i2c 1-000a: Device initialisation failed
redboot-200925/dmesg-bad:sgtl5000-i2c 1-000a: Device
(all tests on Babbage 1)
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Note that with the broken RedBoot, I get a zeroed MAC address which prevents
bringing up the network here.
# ifup eth0
SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address
after setting the MAC manually, it works.
** Package changed: gnome-applets (Ubuntu)
In the Babbage1 case, the kernel, rootfs, and initrd are unchanged. I
have changed redboot only. So no kernel config changes or changes to
the initrd scripts/modules. ifconfig shows a loopback device in the
failing case. And networking is working.
In the Babbage2 case there is no initrd, so
i dont think the plain dd to the device will work,
http://people.ubuntu.com/~ogra/arm/babbage/redboot-install has a script
that slightly reflects how the bootloader is currently set up (still
work in progress, but i hope to integrate it in the reboot-tools package
in karmic which should make it
I have gone back and forth between redboot versions that work/don't work
using dd. I can do fis list and fc -l and capture the results and
compare good to bad and see that the listed information is not changed.
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
I also have replicated the bug using the vmlinuz and initrd from /boot.
I copied them to a host machine, used gzip -d to decompress the
initrd, and uploaded them using tftp with redboot, adding the unchanged
exec line. So I really think the only change here (in the Babbage1
case) is redboot, not
thanks a lot for the detailed description, that helps a lot to narrow
down the problem :)
sorry if i appear like a PITA, but i want to make absolutely sure we only have
a single point of change ...
running flash-kernel on teh installed system will have the same effect btw, we
eleminated the
so while debugging that issue on our side it seems that the MAC address
for eth0 isnt set at all ... that seems to be related to the issue
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of Ubuntu
Yeah, that's fine, I agree it is good to be real exact about what
changed and what didn't, so I'm totally fine with any questions you have
on my setup.
Are you seeing the failure of the applets after login?
I started down the path of DebuggingProgramCrash, not sure which program
to pursue as the
We narrowed down to code in Redboot that is causing this error message
to Pop up.
We removed the macro:
RedBoot_init(babbage_power_init, RedBoot_INIT_PRIO(900)); which was used
to call the function babbage_power_init
and instead call the babbage_power_init() function directly earlier from one
if you are only changing redboot but keep kernel and initramfs the same,
does it behave sanely ? i suspect there is either a kernel config option
missing or some service/device that is expected to start in initramfs
isnt available ...
also does ifconfig show you a running loopback device in the
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
one other (rather hackish) hint if you want to test a proper
kernel/initramfs setup as ubuntu uses it:
(well, one way would be to base on a ubuntu kernel package, add your
patchset and just build that, since this will call the proper
postinstall scripts, use the needed configuration options for
If possible, can you please also give the output of fconfig with both
the old and new Redboots to see if any command line arguments to the
kernel have changed?
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a
** Attachment added: Updated RedBoot for babbage1
http://launchpadlibrarian.net/28442516/mx51_babbage_redboot-no-padding.bin
** Description changed:
Binary package hint: gnome-applets
Release: Ubuntu 9.04 (modified, see below) on Babbage1 or Babbage2.
- The error is that
** Tags added: armel
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
33 matches
Mail list logo
