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 #2232: unplugging with gadgetfs causes
panic: "softlockup: blocked tasks" (Openmoko Public Trac)
2. Re: Openmoko Bug #2232: unplugging with gadgetfs causes
panic: "softlockup: blocked tasks" (Openmoko Public Trac)
3. Re: Openmoko Bug #2232: unplugging with gadgetfs causes
panic: "softlockup: blocked tasks" (Openmoko Public Trac)
4. Re: Openmoko Bug #2232: unplugging with gadgetfs causes
panic: "softlockup: blocked tasks" (Openmoko Public Trac)
5. Re: Openmoko Bug #2232: unplugging with gadgetfs causes
panic: "softlockup: blocked tasks" (Openmoko Public Trac)
6. Re: Openmoko Bug #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
--- Begin Message ---
#2232: unplugging with gadgetfs causes panic: "softlockup: blocked tasks"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by balajirrao):
Hum, I'm not able to see it - it seems that you've attached the one
without modifications.
And, what about the problem ? Does it still show up with the patch applied
?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2232#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2232: unplugging with gadgetfs causes panic: "softlockup: blocked tasks"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
On my desktop computer all bulk reads in step 5.3 seem to fail with "-2".
Therefore I need to test this patch on my laptop where sink-source-reader
works.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2232#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2232: unplugging with gadgetfs causes panic: "softlockup: blocked tasks"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
This time "lsusb -vvv" on laptop just took a really long time and
eventually showed only the hub. Hitting ctrl-c on usb.c does not seem to
kill it now:
{{{
li...@ginger:~/scm/usb-root/sink$ sudo ./usb -r 1.3 -p 1
/dev/gadget/s3c2410_udc ep0 configured
serial="1.3"
^Creset source fd: Interrupted system call
^Creset sink fd: Interrupted system call
ep0 stall: Identifier removed
^Cep0 read after poll: Interrupted system call
}}}
Shouldn't there be a kernel space patch to fix the issue? Bad userland
software should not be able to crash the kernel.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2232#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2232: unplugging with gadgetfs causes panic: "softlockup: blocked tasks"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
After a while I got another crash with same backtrace:
{{{
4007.055000] gta02_udc_command S3C2410_UDC_P_DISABLE
4167.195000] INFO: task usb:3713 blocked for more than 120 seconds.
4167.200000] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
4167.205000] usb D c03a6cbc 0 3713 1
4167.215000] [<c03a6900>] (schedule+0x0/0x430) from [<bf01c504>]
(ep_io+0x1fc/0x24c [gadgetfs])
4167.220000] [<bf01c308>] (ep_io+0x0/0x24c [gadgetfs]) from [<bf01cf1c>]
(ep_write+0x104/0x120 [gadgetfs])
4167.230000] [<bf01ce18>] (ep_write+0x0/0x120 [gadgetfs]) from
[<c00b21d4>] (vfs_write+0xb8/0x148)
4167.245000] r8:c0034048 r7:00001c00 r6:c6303f78 r5:40972200 r4:c4e416e0
4167.250000] [<c00b211c>] (vfs_write+0x0/0x148) from [<c00b232c>]
(sys_write+0x4c/0x7c)
4167.255000] r7:00000004 r6:c4e416e0 r5:00000000 r4:00000000
4167.260000] [<c00b22e0>] (sys_write+0x0/0x7c) from [<c0033ea0>]
(ret_fast_syscall+0x0/0x2c)
4167.265000] r6:4004b000 r5:40974490 r4:409744d8
4167.270000] no locks held by usb/3713.
4167.275000] Kernel panic - not syncing: softlockup: blocked tasks
4167.280000] Rebooting in 10 seconds..<3>RCU detected CPU 0 stall
(t=834039/600 jiffies)
4170.195000] [<c03a6390>] (dump_stack+0x0/0x14) from [<c0085bd8>]
(check_cpu_stall+0x80/0x100)
4170.195000] [<c0085b58>] (check_cpu_stall+0x0/0x100) from [<c0085c70>]
(__rcu_pending+0x18/0xa8)
4170.195000] r6:c782a080 r5:c04cb700 r4:c09a0924
4170.195000] [<c0085c58>] (__rcu_pending+0x0/0xa8) from [<c0085d18>]
(rcu_pending+0x18/0x4c)
4170.195000] r5:00000000 r4:00000000
4170.195000] [<c0085d00>] (rcu_pending+0x0/0x4c) from [<c005f944>]
(update_process_times+0x40/0x64)
4170.195000] [<c005f904>] (update_process_times+0x0/0x64) from
[<c0037e38>] (timer_tick+0x100/0x128)
4170.195000] r6:00000000 r5:00000000 r4:c04c8d48
4170.195000] [<c0037d38>] (timer_tick+0x0/0x128) from [<c0044d90>]
(s3c2410_timer_interrupt+0x10/0x18)
4170.195000] r4:c04c6524
4170.195000] [<c0044d80>] (s3c2410_timer_interrupt+0x0/0x18) from
[<c00830c8>] (handle_IRQ_event+0x2c/0x68)
4170.195000] [<c008309c>] (handle_IRQ_event+0x0/0x68) from [<c00846d8>]
(handle_edge_irq+0x12c/0x178)
4170.195000] r7:c04c9eac r6:c04c6524 r5:0000001e r4:c04c9e78
4170.195000] [<c00845ac>] (handle_edge_irq+0x0/0x178) from [<c0033064>]
(__exception_text_start+0x64/0x84)
4170.195000] r8:00000002 r7:00000003 r6:00004000 r5:00000000 r4:0000001e
4170.195000] [<c0033000>] (__exception_text_start+0x0/0x84) from
[<c0033a38>] (__irq_svc+0x38/0xc8)
4170.195000] Exception stack(0xc782df10 to 0xc782df58)
4170.195000] df00: 00017a8f 00000000
000001e5 c04c9378
4170.195000] df20: 00000000 00000ab5 c04f5040 000003e8 c04f5044 c04c936c
c04c9378 c782df64
4170.195000] df40: c782df58 c782df58 c03a6460 c01a4b0c 20000013 ffffffff
4170.195000] r5:f4000000 r4:ffffffff
4170.195000] [<c03a63a4>] (panic+0x0/0x134) from [<c0082994>]
(check_hung_uninterruptible_tasks+0x11c/0x17c)
4170.195000] r3:00000001 r2:c09a08fc r1:00000001 r0:c04562ec
4170.195000] [<c0082878>] (check_hung_uninterruptible_tasks+0x0/0x17c)
from [<c0082a9c>] (watchdog+0xa8/0xe4)
4170.195000] [<c00829f4>] (watchdog+0x0/0xe4) from [<c006ae68>]
(kthread+0x60/0x94)
4170.195000] [<c006ae08>] (kthread+0x0/0x94) from [<c0058d80>]
(do_exit+0x0/0x2a4)
4170.195000] r6:00000000 r5:00000000 r4:00000000
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2232#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2232: unplugging with gadgetfs causes panic: "softlockup: blocked tasks"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by balajirrao):
The thing is, usb.c goes to an uninterruptible sleep and there's no way
for it to get out of it. That is what the log says - 'INFO: task usb:3713
blocked for more than 120 seconds.'
To fix this non-killability with ^c is what I sent the patch for! You're
right, it looks like there are races somewhere in the code
s3c2410-udc/gadgetfs code that prevents the task from getting out of
sleep. It might also be preferable to use killable sleep here. I'll try to
reproduce the problem and see what can be done.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2232#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: System Software | Version:
Severity: major | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by Sascha):
I found that the delay is introduced by a busy wait in
glamo_mci_send_request. The call graph looks like this:
{{{
arch/arm/kernel/irq.c asm_do_IRQ(21)
include/linux/irq.h generic_handle_irq(21)
arch/arm/plat-s3c24xx/irq.c s3c_irq_demux_extint8(21, desc)
include/linux/irq.h generic_handle_irq(56)
drivers/mfd/glamo/glamo-core.c glamo_irq_demux_handler(56, desc)
arch/arm/include/asm/hw_irq.h desc_handle_irq(92, desc)
drivers/mfd/glamo/glamo-mci.c glamo_mci_irq(92, desc)
drivers/mfd/glamo/glamo-mci.c glamo_mci_irq_host(host)
drivers/mfd/glamo/glamo-mci.c glamo_mci_send_request(mmc)
}}}
{{{
Feb 15 18:20:28 gta02 kernel: [21474811.755000] glamo_mci_send_request:
5874 us - 22770 polls
Feb 15 18:20:28 gta02 kernel: [21474811.755000] asm_do_IRQ(21): 6170 us
Feb 15 18:20:34 gta02 kernel: [21474817.000000] glamo_mci_send_request:
6195 us - 24007 polls
Feb 15 18:20:34 gta02 kernel: [21474817.000000] asm_do_IRQ(21): 6509 us
Feb 15 18:20:34 gta02 kernel: [21474817.015000] glamo_mci_send_request:
6354 us - 24627 polls
Feb 15 18:20:34 gta02 kernel: [21474817.015000] asm_do_IRQ(21): 6646 us
Feb 15 18:22:33 gta02 kernel: [ 99.735000] glamo_mci_send_request: 5109
us - 58541 polls
Feb 15 18:22:33 gta02 kernel: [ 99.735000] asm_do_IRQ(21): 5433 us
Feb 15 18:22:49 gta02 kernel: [ 115.380000] glamo_mci_send_request: 7170
us - 376570 polls
Feb 15 18:22:49 gta02 kernel: [ 115.380000] asm_do_IRQ(21): 7492 us
Feb 15 18:22:49 gta02 kernel: [ 115.385000] rxerr: port=1 ch=0x00,
rxs=0x00000001
Feb 15 18:28:24 gta02 kernel: [ 450.320000] glamo_mci_send_request: 6284
us - 276284 polls
Feb 15 18:28:24 gta02 kernel: [ 450.320000] asm_do_IRQ(21): 6557 us
Feb 15 18:28:24 gta02 kernel: [ 450.335000] glamo_mci_send_request: 6225
us - 334202 polls
Feb 15 18:28:24 gta02 kernel: [ 450.335000] asm_do_IRQ(21): 6507 us
Feb 15 18:28:24 gta02 kernel: [ 450.355000] rxerr: port=1 ch=0x04,
rxs=0x00000001
Feb 15 18:28:29 gta02 kernel: [ 455.275000] glamo_mci_send_request: 8298
us - 303475 polls
Feb 15 18:28:29 gta02 kernel: [ 455.275000] asm_do_IRQ(21): 8624 us
}}}
The number of polls suggests that we lose timer interrupts (at 200 Hz we
can only measure 2 * 5 ms)...
Can we really have a delay of ~ 1 second here? This would explain why a 64
byte fifo can overrun at 9600 baud.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:23>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
