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. Re: Openmoko Bug #2215: distros using fso-gsm0710muxd will
not register (Openmoko Public Trac)
2. Openmoko Bug #2226: [passwd] crashes (glibc-free()) when NEW
password length > 8 (Openmoko Public Trac)
3. Re: Openmoko Bug #2206: Can't mount GadgetFS on OM.
(Openmoko Public Trac)
4. Re: Openmoko Bug #2216: Call = there is no sound
(Openmoko Public Trac)
5. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
6. Re: Openmoko Bug #2215: distros using fso-gsm0710muxd will
not register (Openmoko Public Trac)
--- Begin Message ---
#2215: distros using fso-gsm0710muxd will not register
-----------------------------+----------------------------------------------
Reporter: BillK | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: System Software | Version:
Severity: normal | Keywords: gsm0710muxd GSM modem
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by BillK):
ok, found the difference, but needs a serial guru to make sense of it:)
I straced qtopia (working) and the mux (not working) and found that there
is a difference in the termio c_cflags used.
qtopia: c_cflags=0x18b2
mux: c_cflags=0x800018b2
According to "bits/termio.h" (if I have decoded it right) the mux is
setting CRTSCTS flowcontrol.
However, this is again set a couple of lines later using an IOCTL. qtopia
only sets CRTSCTS using the IOCTL.
if I use stty to force it off, the repeating " AT COMMAND READY" messages
stop, and I can again communicate with the modem via minicom etc. If the
bit is set, all I get are the messages.
The weirdest part is that after it uses the ioctl, qtopia appears to have
reset the uart to 0x800018b2 (which is actually what I expect), and keeps
working.
I have not been able to get the mux to behave this way so far, however I
can cure the "AT COMM..." messages by just turning CRTSCTS off using the
"stty" command.
BillK
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2215#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2226: [passwd] crashes (glibc-free()) when NEW password length > 8
---------------------+------------------------------------------------------
Reporter: leadman | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone: Om2008.12
Component: Distro | Version: current svn head
Severity: normal | Keywords: passwd glibc free crash aborted feeds
gdb backtrace strace
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
1) Images: daily , testing, 2009.01.20
testing-om-gta02-20090120.uImage.bin
openmoko-testing-om-gta02.rootfs.jffs2
2) Description:
as an unprivileged user, `passwd` command crashes when changing password
to new one, which is longer than 8 characters. Seems to be NOT affected
when calling `passwd` as root.
3) Steps to reproduce:
r...@om-gta02:~# adduser test
r...@om-gta02:~# passwd test
Changing password for test
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
Enter new password: /* I have entered password of 10
characters length */
Re-enter new password: /* I have entered password of 10
characters length */
Password changed.
r...@om-gta02:~# su test /* OR r...@om-gta02:~# su - test */
t...@om-gta02:~$ passwd
Changing password for test
Old password:
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
Enter new password: /* I have entered password of 10
characters length */
*** glibc detected *** passwd: free(): invalid next size (fast):
0x0001f878 ***
Aborted
( Above is pretty self explaining, but well, if you guys really need
this... here are next steps.)
4) Current result
Currently unprivileged user is unable to change his/her password
5) Expected result
Unprivileged user is expected to be able to change his/her password
6) Reproducible
Always
Attachements:
gdb-passwd.txt
list_installed.txt
opkg
strace-passwd.txt
./opkg:
all-feed.conf
arch.conf
armv4t-feed.conf
Multiverse-feed.conf
navit-feed.conf
om-gta02-feed.conf
P.S.I couldn't find info what to fill into "Blocking" "CC"(my email?) and
"Blocked by"
--
Kind regards
LeadMan
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2226>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2206: Can't mount GadgetFS on OM.
-------------------------+--------------------------------------------------
Reporter: frankmpunkt | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Comment(by frankmpunkt):
I need to correct myself: The patch works as expected (i forgot to remove
g_ether). Anyway, I think it is inode.c (gadgetfs), that needs to be
fixed. Gadgetfs probes the chipset with a fake driver with USB_SPEED_LOW.
But all udc drivers (amd5536udc.c atmel_usba_udc.c fsl_usb2_udc.c
goku_udc.c lh7a40x_udc.c m66592-udc.c omap_udc.c pxa27x_udc.c pxa2xx_udc.c
and finally s3c2410_udc.c) throw an error for drivers with wrong speed
configuration. In combination with all those drivers gadgetfs' probing
would fail. Only dummy_hdc seems to support all possible speed-values...
Anyway, once gadgetfs is mounted, it is usable in combination with
s3c2410_udc, since the user space application that uses gadgetfs should
seem to do chipset-dependent configuration (like http://www.linux-
usb.org/gadget/usb.c does). I wrote a gadget for gadgetfs based on this
example application and i am happy to report, that it works just fine with
OM.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2206#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2216: Call = there is no sound
----------------------+-----------------------------------------------------
Reporter: octavsly | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: Om2008.12
Component: unknown | Version: GTA02v6
Severity: major | Keywords: call, mute, no sound, no audio
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
----------------------+-----------------------------------------------------
Comment(by xbaldauf):
This bug still persists as of
http://git.openmoko.org/?p=kernel.git;a=commit;h=5b3137236f5d5665774f9705220b3fe6c1e23692
( Fri, 30 Jan 2009 16:23:54 +0000 (16:23 +0000) ):
* no sound when phoning
* no sound when the phone is ringing
* no sound when doing playback by mplayer
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2216#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by xbaldauf):
Well,
I've been compiling
http://git.openmoko.org/?p=kernel.git;a=commit;h=5b3137236f5d5665774f9705220b3fe6c1e23692
and booting from this kernel (with "glamo3362.slow_memory=1" appended to
the kernel command line). However, there is no audio (neither when phoning
nor when using mplayer or when being called and the phone should ring)
(which looks like bug https://docs.openmoko.org/trac/ticket/2216), and
thus I cannot use this kernel for daily use, and thus I cannot reliably
test whether the bug still appears.
So for practical reasons, I'd recommend setting this bug as blocked by
#2216 .
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2215: distros using fso-gsm0710muxd will not register
-----------------------------+----------------------------------------------
Reporter: BillK | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: System Software | Version:
Severity: normal | Keywords: gsm0710muxd GSM modem
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by mickey):
No serial expert either, but let me add to the mystery. My device works
perfectly with gsm0710muxd although stty -F /dev/ttySAC0 emits the same
parameters as your nonworking one.
I can't find a way to enable the line 0 discipline (tried with ioctl
TIOCSETD) or change rows/columns here either.
Could this be some race in the kernel?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2215#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
