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 #2073: voice-recording.state + arecord:
Unable to handle kernel NULL pointer dereference at virtual
address 00000000 (Openmoko Public Trac)
2. Re: Openmoko Bug #2240: removing/reloading g_ether not
working (Openmoko Public Trac)
3. Re: Openmoko Bug #2240: removing/reloading g_ether not
working (Openmoko Public Trac)
4. Re: Openmoko Bug #2240: removing/reloading g_ether not
working (Openmoko Public Trac)
5. Re: Openmoko Bug #2254: No usb pressed/released event with
2.6.28/2.6.29 (Openmoko Public Trac)
6. Openmoko Bug #2276: illume battery module shows -1% as the
battery charge state / GTA01 (Openmoko Public Trac)
7. Re: Openmoko Bug #2276: illume battery module shows -1% as
the battery charge state / GTA01 (Openmoko Public Trac)
8. Re: Openmoko Bug #2254: No usb pressed/released event with
2.6.28/2.6.29 (Openmoko Public Trac)
--- Begin Message ---
#2073: voice-recording.state + arecord: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: ALSA
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Changes (by joerg):
* cc: jo...@… (added)
Comment:
Sushama
Please could you explain why you removed my CC?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2073#comment:23>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2240: removing/reloading g_ether not working
-------------------------+--------------------------------------------------
Reporter: frankmpunkt | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Comment(by lindi):
A reliable way to crash the kernel is
{{{
insmod g_ether.ko.2
sleep 1
ifconfig usb0 up
sleep 1
ifconfig usb0 down
sleep 1
rmmod g_ether # ip link still shows usb0
sleep 2
insmod g_ether.ko.2 # now uses usb1 instead of usb0
sleep 2
ifconfig usb0 up # crash when dev_open tries to use usb0
sleep 2
}}}
I can even do "ifconfig usb0 up" after I have removed the g_ether module
completely.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2240#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2240: removing/reloading g_ether not working
-------------------------+--------------------------------------------------
Reporter: frankmpunkt | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Comment(by lindi):
It seems that "insmod g_ether.ko" calls register_netdev() but "rmmod
g_ether" does not call unregister_netdev(). I think the calls _should_ go
like
{{{
insmod g_ether.ko
init()
usb_composite_register()
usb_gadget_register_driver()
driver->bind() = eth_bind()
gether_setup()
register_netdev()
rmmod g_ether
cleanup()
usb_composite_unregister()
usb_gadget_unregister_driver()
driver->unbind() = eth_unbind()
gether_cleanup()
unregister_netdev()
}}}
but the problem is that in s3c2410_udc.c
* usb_gadget_register_driver calls bind() but
* usb_gadget_unregister_driver() does not call unbind().
I checked that _every other_ usb_gadget_unregister_driver in the kernel
does call unbind(), for example
* atmel_usba_udc.c
* pxa25x_udc.c
* omap_udc.c
* fsl_usb2_udc.c
so why does s3c2410_udc.c not call unbind()?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2240#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2240: removing/reloading g_ether not working
-------------------------+--------------------------------------------------
Reporter: frankmpunkt | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Comment(by lindi):
If I just call unbind() from usb_gadget_unregister_driver I can
successfully alternate between g_serial and g_ether as many times as I
like. Can you please test and review this patch?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2240#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2254: No usb pressed/released event with 2.6.28/2.6.29
---------------------+------------------------------------------------------
Reporter: Defiant | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: unknown | Version: unspecified
Severity: normal | Keywords: usb event4 2.6.28 pressed released
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by lindi):
li...@ginger:~$ sudo evtest /dev/input/event4
Input driver version is 1.0.0
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "Neo1973 Buttons"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 119 (Pause)
Event code 169 (Phone)
Event type 5 (?)
Event code 2 (?)
so it definitely is not at least event4. However, it could be
li...@ginger:~$ sudo evtest /dev/input/event0
Input driver version is 1.0.0
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0
Input device name: "PCF50633 PMU events"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 116 (Power)
Event type 22 (Power)
Testing ... (interrupt to exit)
Can you see that name with the old kernel? I placed a breakpoint to
pcf50633_input_irq() but it does not trigger when I insert the wall
charger to freerunner. However, the interrupt count of pcf50633 in
/proc/interrupts is incremented by two.
I'm trying to figure out how to break on interrupt next..
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2254#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2276: illume battery module shows -1% as the battery charge state / GTA01
-----------------------------+----------------------------------------------
Reporter: arhuaco | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
We should be able to monitor voltage.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2276>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2276: illume battery module shows -1% as the battery charge state / GTA01
-----------------------------+----------------------------------------------
Reporter: arhuaco | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
How is this a kernel issue? Doesn't "voltage_now" sysfs file show voltage
for you?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2276#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2254: No usb pressed/released event with 2.6.28/2.6.29
---------------------+------------------------------------------------------
Reporter: Defiant | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: unknown | Version: unspecified
Severity: normal | Keywords: usb event4 2.6.28 pressed released
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by lindi):
When I plug the wall charger to freerunner I see
{{{
#0 pcf50633_irq (irq=53, data=0xc79bdc00) at
/local/lindi/neolinux/drivers/mfd/pcf50633-core.c:446
#1 0xc007f4b8 in handle_IRQ_event (irq=53, action=0xc79cc7a0) at
/local/lindi/neolinux/kernel/irq/handle.c:335
#2 0xc0080b48 in handle_level_irq (irq=53, desc=0xc03927f0) at
/local/lindi/neolinux/kernel/irq/chip.c:375
#3 0xc0039fc4 in s3c_irq_demux_extint8 (irq=53, desc=<value optimized
out>) at /local/lindi/neolinux/include/linux/irq.h:312
#4 0xc002e054 in asm_do_IRQ (irq=21, regs=<value optimized out>) at
/local/lindi/neolinux/include/linux/irq.h:312
#5 0xc002ea38 in __irq_svc ()
}}}
and after that in pcf50633_irq_worker() pcf_int[] has {0x84, 0x0, 0x0,
0x0, 0x0} which seems to correspond to
PCF50633_INT1_USBINS = 0x04, /* USB inserted */
However, pcf50633_input_probe() only registers itself for the
PCF50633_IRQ_ONKEYR and PCF50633_IRQ_ONKEYF events so that it can
report when power button is pressed:
Event: time 946686973.644550, type 1 (Key), code 116 (Power), value 1
Event: time 946686973.645172, -------------- Report Sync ------------
Event: time 946686973.884483, type 1 (Key), code 116 (Power), value 0
Event: time 946686973.884558, -------------- Report Sync ------------
Should that Power2 event be added back? I think I know how to add it
if it is considered useful.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2254#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
