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. [Bug 329] New: SIM holder/microSD holder is crappy.
([EMAIL PROTECTED])
2. [Bug 329] New: SIM holder/microSD holder is crappy.
([EMAIL PROTECTED])
3. [Bug 330] New:
uboot-gta01-1.2.0+svnnow-r4_6db7d0af2336c126e4d4b2f248cc23516bdd46a8_1557-do_compile
([EMAIL PROTECTED])
4. [Bug 330] New:
uboot-gta01-1.2.0+svnnow-r4_6db7d0af2336c126e4d4b2f248cc23516bdd46a8_1557-do_compile
([EMAIL PROTECTED])
5. [Bug 321] ftdi_eeprom often fails silently
([EMAIL PROTECTED])
6. [Bug 321] ftdi_eeprom often fails silently
([EMAIL PROTECTED])
7. [Bug 321] ftdi_eeprom often fails silently
([EMAIL PROTECTED])
8. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
9. [Bug 330]
uboot-gta01-1.2.0+svnnow-r4_6db7d0af2336c126e4d4b2f248cc23516bdd46a8_1557-do_compile
([EMAIL PROTECTED])
10. [Bug 330]
uboot-gta01-1.2.0+svnnow-r4_6db7d0af2336c126e4d4b2f248cc23516bdd46a8_1557-do_compile
([EMAIL PROTECTED])
11. [Bug 331] New: uboot fails to build cause lowlevel_foo.bin is
not built for smdk2440 and hxd8 boards
([EMAIL PROTECTED])
12. [Bug 226] dfu-util-native do_deploy tries to install from
wrong source filename ([EMAIL PROTECTED])
13. [Bug 332] New: site.conf refers to nonexistent openalchemy
files ([EMAIL PROTECTED])
14. [Bug 325]
uboot-gta01-1.2.0+svnnow-r4_0_200703292112-do_compile
([EMAIL PROTECTED])
15. [Bug 325]
uboot-gta01-1.2.0+svnnow-r4_0_200703292112-do_compile
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=329
Summary: SIM holder/microSD holder is crappy.
Product: Neo1973 Hardware
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: GSM Modem
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
...in particular, it allows locking improperly inserted microSD card, and it
allows locking improperly inserted SIM card.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=329
Summary: SIM holder/microSD holder is crappy.
Product: Neo1973 Hardware
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: GSM Modem
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
...in particular, it allows locking improperly inserted microSD card, and it
allows locking improperly inserted SIM card.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=330
Summary: uboot-gta01-1.2.0+svnnow-
r4_6db7d0af2336c126e4d4b2f248cc23516bdd46a8_1557-
do_compile
Product: OpenMoko
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: autobuilds
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The package failed to build at 20070329220004
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=330
Summary: uboot-gta01-1.2.0+svnnow-
r4_6db7d0af2336c126e4d4b2f248cc23516bdd46a8_1557-
do_compile
Product: OpenMoko
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: autobuilds
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The package failed to build at 20070329220004
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=321
------- Additional Comments From [EMAIL PROTECTED] 2007-03-30 03:43 -------
I'm now automatically cycling upstream VBUS in order to exercise the
board initialization. Unfortunately, the board now consistently uses the
default settings :-(
During my testing, I observed that VCC5 doesn't look good. There is
a typical cycle if I limit the current drawn from upstream VBUS to about
50-200 mA:
http://people.openmoko.org/~werner/dbgnp.jpg
CH1 is VCC5 (= VBUS from upstream), CH2 is CS of the AT93C56A
(I often also only get the first burst on CH2, and it stays low
during the anomaly, so don't pay too much attention to CH2.)
That spike around -500 ms from the center looks a bit disturbing.
This is what it looks like magnified:
http://people.openmoko.org/~werner/dbgnp-zoom.jpg
I've not been able to correlate this to any signal changing at
exactly the same time. However, LED7 begins its long blink about
7-8 ms before VCC5 collapses, and several other signals change
around that time as well.
If I allow a larger current, VCC5 doesn't break down as much, but
still shows a disturbance. So my suspicion is that something is
briefly causing a short, which then upsets the system.
I think this needs looking at by the hardware group.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=321
------- Additional Comments From [EMAIL PROTECTED] 2007-03-30 03:43 -------
I'm now automatically cycling upstream VBUS in order to exercise the
board initialization. Unfortunately, the board now consistently uses the
default settings :-(
During my testing, I observed that VCC5 doesn't look good. There is
a typical cycle if I limit the current drawn from upstream VBUS to about
50-200 mA:
http://people.openmoko.org/~werner/dbgnp.jpg
CH1 is VCC5 (= VBUS from upstream), CH2 is CS of the AT93C56A
(I often also only get the first burst on CH2, and it stays low
during the anomaly, so don't pay too much attention to CH2.)
That spike around -500 ms from the center looks a bit disturbing.
This is what it looks like magnified:
http://people.openmoko.org/~werner/dbgnp-zoom.jpg
I've not been able to correlate this to any signal changing at
exactly the same time. However, LED7 begins its long blink about
7-8 ms before VCC5 collapses, and several other signals change
around that time as well.
If I allow a larger current, VCC5 doesn't break down as much, but
still shows a disturbance. So my suspicion is that something is
briefly causing a short, which then upsets the system.
I think this needs looking at by the hardware group.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=321
------- Additional Comments From [EMAIL PROTECTED] 2007-03-30 03:43 -------
I'm now automatically cycling upstream VBUS in order to exercise the
board initialization. Unfortunately, the board now consistently uses the
default settings :-(
During my testing, I observed that VCC5 doesn't look good. There is
a typical cycle if I limit the current drawn from upstream VBUS to about
50-200 mA:
http://people.openmoko.org/~werner/dbgnp.jpg
CH1 is VCC5 (= VBUS from upstream), CH2 is CS of the AT93C56A
(I often also only get the first burst on CH2, and it stays low
during the anomaly, so don't pay too much attention to CH2.)
That spike around -500 ms from the center looks a bit disturbing.
This is what it looks like magnified:
http://people.openmoko.org/~werner/dbgnp-zoom.jpg
I've not been able to correlate this to any signal changing at
exactly the same time. However, LED7 begins its long blink about
7-8 ms before VCC5 collapses, and several other signals change
around that time as well.
If I allow a larger current, VCC5 doesn't break down as much, but
still shows a disturbance. So my suspicion is that something is
briefly causing a short, which then upsets the system.
I think this needs looking at by the hardware group.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=137
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=192
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=204
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=232
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=330
------- Additional Comments From [EMAIL PROTECTED] 2007-03-30 07:12 -------
I don't know why creating attachments fails but the log can be viewed at
http://ewi546.ewi.utwente.nl/
tinderbox/showbuilds.pl?tree=OpenMoko
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=330
------- Additional Comments From [EMAIL PROTECTED] 2007-03-30 07:12 -------
I don't know why creating attachments fails but the log can be viewed at
http://ewi546.ewi.utwente.nl/
tinderbox/showbuilds.pl?tree=OpenMoko
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=331
Summary: uboot fails to build cause lowlevel_foo.bin is not built
for smdk2440 and hxd8 boards
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The Makefiles in boards/smdk2440 and boards/hxd8 are missing the additional
targets which build the lowlevel_foo.bin files.
This causes the bitbake recipe to file in the do_compile task.
No patch included, cause I don't know whether you want to build lowlevel_foo.bin
for those boards or not.
-- Rod
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=226
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-30 08:13 -------
Fixed already in the bitbake recipe. No longer a problem.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=332
Summary: site.conf refers to nonexistent openalchemy files
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: OE bitbake recipes / build system
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
This causes a spurious warning from BitBake.
Either the OA stuff should be removed, or the OA stuff should be made an
official part of the build.
-- Rod
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=325
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From [EMAIL PROTECTED] 2007-03-30 10:39 -------
*** This bug has been marked as a duplicate of 324 ***
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=325
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From [EMAIL PROTECTED] 2007-03-30 10:39 -------
*** This bug has been marked as a duplicate of 324 ***
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
