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 93] test 4GB microSD card compatibility
      ([EMAIL PROTECTED])
   2. [Bug 749] New: OpenMoko will not boot without /etc/pointercal
      present ([EMAIL PROTECTED])
   3. [Bug 750] New: Stale patch on QEMU configure
      ([EMAIL PROTECTED])
   4. [Bug 675] Failed to compile perl (fresh install)
      ([EMAIL PROTECTED])
   5. [Bug 751] New: /etc/init.d/gsmd stop - kills own shell-script
      ([EMAIL PROTECTED])
   6. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
   7. [Bug 677] I/O errors on heavy microSD writes
      ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=93





------- Additional Comments From [EMAIL PROTECTED]  2007-08-24 15:46 -------
Transfer a 800MB file over scp gives a lot more errors in dmesg and scp shows an
IO error after transfer.

This really looks more like a general s3cmci driver problem already noted in:
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677



------- 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=749

           Summary: OpenMoko will not boot without /etc/pointercal present
           Product: OpenMoko
           Version: 2007.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: touchscreen/key click
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


If /etc/pointercal is not present then the calibration program is meant to be
run on boot.

If I remove /etc/pointercal and reboot, OpenMoko hangs at the "Please wait while
starting UI" screen.

I have seen this when using a build where the pointercal package has been
excluded and also after booting OpenMoko, running `rm /etc/pointercal` in the
terminal and rebooting.

NOTE: I do not possess a Neo 1973 and so have only observed this with qemu.



------- 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=750

           Summary: Stale patch on QEMU configure
           Product: OpenMoko
           Version: 2007.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: OE bitbake recipes  / build system
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


qemu-native-0.8.2+cvs20070613-r2 (current HEAD) configure.patch seems to be old.

It appears that the patch was against an earlier version of configure.
The patched line still exists in the configure, but at a different place and
with different follower lines.

Workaround is to manually patch the configure file and touch the bitbake stamp
file to indicate patch has been applied.

NOTE: Running task 3154 of 3492 (ID: 1184,
/home/moko2/org.openembedded.dev/packages/qemu/qemu-native_cvs.bb, do_patch)
NOTE: package qemu-native-0.8.2+cvs20070613: started
NOTE: package qemu-native-0.8.2+cvs20070613-r2: task do_patch: started
NOTE: Applying patch 'configure.patch'
ERROR: Error in executing: 
ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1  
Output:
Applying patch configure.patch
patching file configure
Hunk #1 FAILED at 482.
1 out of 1 hunk FAILED -- rejects in file configure
Patch configure.patch does not apply (enforce with -f)
ERROR: Printing the environment of the function
ERROR: Error in executing: 
ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1  
Output:
Applying patch configure.patch
patching file configure
Hunk #1 FAILED at 482.
1 out of 1 hunk FAILED -- rejects in file configure
Patch configure.patch does not apply (enforce with -f)
ERROR: Printing the environment of the function
ERROR: Error in executing: 
ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1  
Output:
Applying patch configure.patch
patching file configure
Hunk #1 FAILED at 482.
1 out of 1 hunk FAILED -- rejects in file configure
Patch configure.patch does not apply (enforce with -f)
ERROR: Printing the environment of the function
ERROR: Build of
/home/moko2/org.openembedded.dev/packages/qemu/qemu-native_cvs.bb do_patch 
failed
Traceback (most recent call last):
  File "/home/moko2/bitbake/bin/bitbake", line 134, in <module>
    main()
  File "/home/moko2/bitbake/bin/bitbake", line 131, in main
    cooker.cook()
  File "/home/moko2/bitbake/lib/bb/cooker.py", line 552, in cook
    return self.buildTargets(pkgs_to_build)
  File "/home/moko2/bitbake/lib/bb/cooker.py", line 466, in buildTargets
    failures = rq.execute_runqueue()
  File "/home/moko2/bitbake/lib/bb/runqueue.py", line 403, in execute_runqueue
    self.execute_runqueue_internal()
  File "/home/moko2/bitbake/lib/bb/runqueue.py", line 531, in
execute_runqueue_internal
    self.cooker.tryBuild(fn, False)
  File "/home/moko2/bitbake/lib/bb/cooker.py", line 125, in tryBuild
    return self.tryBuildPackage(fn, item, self.configuration.cmd, the_data,
build_depends)
  File "/home/moko2/bitbake/lib/bb/cooker.py", line 98, in tryBuildPackage
    bb.build.exec_task('do_%s' % task, the_data)
  File "/home/moko2/bitbake/lib/bb/build.py", line 292, in exec_task
    execute(None, task)
  File "/home/moko2/bitbake/lib/bb/build.py", line 281, in execute
    exec_func(item, localdata)
  File "/home/moko2/bitbake/lib/bb/build.py", line 98, in exec_func
    exec_func_python(func, d)
  File "/home/moko2/bitbake/lib/bb/build.py", line 117, in exec_func_python
    utils.better_exec(comp,g,tmp, bb.data.getVar('FILE',d,1))
  File "/home/moko2/bitbake/lib/bb/utils.py", line 144, in better_exec
    exec code in context
  File "do_patch", line 4, in <module>
  File "do_patch", line 2, in do_patch
  File "/home/moko2/bitbake/lib/bb/build.py", line 98, in exec_func
    exec_func_python(func, d)
  File "/home/moko2/bitbake/lib/bb/build.py", line 117, in exec_func_python
    utils.better_exec(comp,g,tmp, bb.data.getVar('FILE',d,1))
  File "/home/moko2/bitbake/lib/bb/utils.py", line 144, in better_exec
    exec code in context
  File "base_do_patch", line 4, in <module>
  File "base_do_patch", line 2, in base_do_patch
  File "/home/moko2/bitbake/lib/bb/build.py", line 98, in exec_func
    exec_func_python(func, d)
  File "/home/moko2/bitbake/lib/bb/build.py", line 117, in exec_func_python
    utils.better_exec(comp,g,tmp, bb.data.getVar('FILE',d,1))
  File "/home/moko2/bitbake/lib/bb/utils.py", line 144, in better_exec
    exec code in context
  File "patch_do_patch", line 100, in <module>
  File "patch_do_patch", line 98, in patch_do_patch
  File "<bb>", line 339, in Resolve
__builtin__.CmdError: Command Error: exit status: 1  Output:
Applying patch configure.patch
patching file configure
Hunk #1 FAILED at 482.
1 out of 1 hunk FAILED -- rejects in file configure
Patch configure.patch does not apply (enforce with -f)



------- 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=675





------- Additional Comments From [EMAIL PROTECTED]  2007-08-24 21:42 -------
Where do we get 2007.2 from?

http://buildhost.openmoko.org/snapshots/ only shows 2007.4 and 2007.8.

I'm having the same issue on Gentoo, 2.6.22-r2 kernel. A quick search on
"asm/page.h" made me wonder if it was a Gentoo issue which was supposedly fixed
by emerging the v2.6.22-r2 linux headers (~x86 masked), but that hasn't helped
either: /usr/include/asm still does not include page.h to build this source 
code.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
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=751

           Summary: /etc/init.d/gsmd stop - kills own shell-script
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gsmd
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


When calling "killall gsmd" in stop(), the shellscript kills itself. 

therefore

* restart()/reload() and
* "rm -f /var/lock/subsys/gsmd" in stop()

are not working. Maybe the script should be renamed to gsmd.sh?



------- 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=112
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
  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=301
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=700
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=704



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]



------- Additional Comments From [EMAIL PROTECTED]  2007-08-25 10:21 -------
Just... I see it here, too, with phase 0 openmoko and card that was provided
with it.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to