From pratyush.linux at gmail.com  Wed Sep  1 03:52:09 2010
From: pratyush.linux at gmail.com (Pratyush Anand)
Date: Wed, 1 Sep 2010 13:22:09 +0530
Subject: PCI master abort with USB3.0 card
In-Reply-To: <AANLkTi=CdAYrU6M8y2JYZRUv07SermQe7bWaZm7EcohA@mail.gmail.com>
References: <AANLkTi=CdAYrU6M8y2JYZRUv07SermQe7bWaZm7EcohA@mail.gmail.com>
Message-ID: <AANLkTimw=HEvsGjUSA2A57Cc=xDMwf2ZheZ6WQbAThwp@mail.gmail.com>

On Wed, Sep 1, 2010 at 1:08 PM, Pratyush Anand <pratyush.linux at gmail.com> wrote:
>
> Hello Amit,
>
>
>
> We are using USB3.0 controller chip from NEC (D720200F1).
>
> Arm processor is cortex-A9.
>
>
>
> You can see the pcie implementation for my platform in this patch
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-August/024364.html
>
>
>
> Regards
>
> Pratysuh
>
>
> > Hi,
> > Can you please share the USB3.0 controller chip or the PCIe card manufacturer's name? Also, which ARM processor are you using?
> > Thanks,
> > - Amit
> >
> > On Tue, 31 Aug 2010 12:47:26 +0530 (IST) Pratyush Anand <anand_pratyush at xxxxxxxxxxx> wrote:
> >
> >> Hello All,
> >> I am using a PCIE base usb3.0 card on ARM based platform. Linux
> >> version is 2.6.32.
> >> Support of PCIE for this platform has been added by me.
> >> This usb3.0 card works well , if I connect it to host intel
> >> PC(fedora) having same linux kernel version.
> >> But , with my board I have some issue.
> >> I am able to detect the card.
> >> If I connect a mass storage device to the card , it is also detected.
> >> If I copy a small file from mass storage to root file system , it is
> >> copied well.
> >> But If I copy a big file(say 1MB) and do sync or umount operation , it
> >> fails. If I try to see pci configuration register of this card then I
> >> found that "Master abort received " bit is set.
> >> Can anyone suggest a pointer to look into it.
> >> Regards>
> >> Pratyush
> >> At the console i see following error:
> >>
> >> ------------------------------------------
> >> root at xxxxxxxxxxxx:~# mount /dev/sda1 /mnt/ root at xxxxxxxxxxxx:~# cp 1MB
> >> /mnt/ root at xxxxxxxxxxxx:~# umount /mnt/
> >> INFO: task scsi_eh_0:482 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. scsi_eh_0???? D c02c0708???? 0?? 482????? 2 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
> >> (schedule_timeout+0x20/0x1b8)
> >> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
> >> (wait_for_common+0xe0/0x178)
> >>? r7:7fffffff r6:cf9dc3ac r5:cf892080 r4:cf9dc3b0 [<c02c025c>]
> >> (wait_for_common+0x0/0x178) from [<c02c0464>]
> >> (wait_for_completion+0x18/0x1c)
> >> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c020bcfc>]
> >> (command_abort+0x94/0x9c)
> >> [<c020bc68>] (command_abort+0x0/0x9c) from [<c019f8fc>]
> >> (__scsi_try_to_abort_cmd+0x2c/0x30)
> >>? r7:cf9d2000 r6:cf9d3f84 r5:cf9dc000 r4:cfacf320 [<c019f8d0>]
> >> (__scsi_try_to_abort_cmd+0x0/0x30) from [<c01a12f0>]
> >> (scsi_error_handler+0x12c/0x358)
> >> [<c01a11c4>] (scsi_error_handler+0x0/0x358) from [<c0051150>]
> >> (kthread+0x88/0x90)
> >>? r7:c01a11c4 r6:cf9dc000 r5:cf867bb8 r4:cf9d3fbc [<c00510c8>]
> >> (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)? r7:00000000
> >> r6:00000000 r5:00000000 r4:00000000
> >> INFO: task usb-storage:483 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. usb-storage?? D c02c0708???? 0?? 483????? 2 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
> >> (schedule_timeout+0x20/0x1b8)
> >> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
> >> (wait_for_common+0xe0/0x178)
> >>? r7:7fffffff r6:cf9dc364 r5:cf892700 r4:cf9dc368 [<c02c025c>]
> >> (wait_for_common+0x0/0x178) from [<c02c0464>]
> >> (wait_for_completion+0x18/0x1c)
> >> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c01f1c40>]
> >> (usb_sg_wait+0x148/0x154)
> >> [<c01f1af8>] (usb_sg_wait+0x0/0x154) from [<c020c748>]
> >> (usb_stor_bulk_transfer_sglist+0xbc/0x110)
> >> [<c020c68c>] (usb_stor_bulk_transfer_sglist+0x0/0x110) from
> >> [<c020c7cc>] (usb_stor_bulk_srb+0x30/0x48) [<c020c79c>]
> >> (usb_stor_bulk_srb+0x0/0x48) from [<c020ccfc>]
> >> (usb_stor_Bulk_transport+0x110/0x2ac)
> >>? r4:ffc1300f
> >> [<c020cbec>] (usb_stor_Bulk_transport+0x0/0x2ac) from [<c020cec0>]
> >> (usb_stor_invoke_transport+0x28/0x314)
> >> [<c020ce98>] (usb_stor_invoke_transport+0x0/0x314) from [<c020becc>]
> >> (usb_stor_transparent_scsi_command+0x10/0x14)
> >>? r8:00000000 r7:c020de84 r6:cf9dc000 r5:cf9dc2bc r4:cf9f1fbc
> >> [<c020bebc>] (usb_stor_transparent_scsi_command+0x0/0x14) from
> >> [<c020dfd8>] (usb_stor_control_thread+0x154/0x21c)
> >> [<c020de84>] (usb_stor_control_thread+0x0/0x21c) from [<c0051150>]
> >> (kthread+0x88/0x90)
> >>? r6:cf9dc2bc r5:cf867c10 r4:cf9f1fbc
> >> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
> >> r7:00000000 r6:00000000 r5:00000000 r4:00000000
> >> INFO: task umount:1413 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. umount??????? D c02c0708???? 0? 1413?? 1407 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c00afb5c>]
> >> (bdi_sched_wait+0x10/0x18) [<c00afb4c>] (bdi_sched_wait+0x0/0x18) from
> >> [<c02c0d0c>] (__wait_on_bit+0x64/0xac) [<c02c0ca8>]
> >> (__wait_on_bit+0x0/0xac) from [<c02c0dd4>]
> >> (out_of_line_wait_on_bit+0x80/0x8c)
> >> [<c02c0d54>] (out_of_line_wait_on_bit+0x0/0x8c) from [<c00afbf4>]
> >> (sync_inodes_sb+0x90/0x15c)
> >> [<c00afb64>] (sync_inodes_sb+0x0/0x15c) from [<c00b3c78>]
> >> (__sync_filesystem+0x38/0x64)
> >>? r8:00000000 r7:cfb9d580 r6:c02c8724 r5:00000001 r4:cfac7c00
> >> [<c00b3c40>] (__sync_filesystem+0x0/0x64) from [<c00b3e88>]
> >> (sync_filesystem+0x54/0x5c)
> >>? r5:cfad2000 r4:cfac7c00
> >> [<c00b3e34>] (sync_filesystem+0x0/0x5c) from [<c0095ea8>]
> >> (generic_shutdown_super+0x38/0x118)
> >>? r5:cfad2000 r4:cfac7c00
> >> [<c0095e70>] (generic_shutdown_super+0x0/0x118) from [<c0095fa8>]
> >> (kill_block_super+0x20/0x38)
> >>? r7:cfb9d580 r6:cfb9d580 r5:00000003 r4:cf50a000 [<c0095f88>]
> >> (kill_block_super+0x0/0x38) from [<c00962d8>]
> >> (deactivate_super+0x50/0x68)
> >>? r5:c03a9b48 r4:cfac7c00
> >> [<c0096288>] (deactivate_super+0x0/0x68) from [<c00aa51c>]
> >> (mntput_no_expire+0x70/0xb0)
> >>? r5:cfb9d580 r4:cfac7c00
> >> [<c00aa4ac>] (mntput_no_expire+0x0/0xb0) from [<c00aaaf4>]
> >> (sys_umount+0x2c0/0x2f8)
> >>? r5:cfb9d598 r4:cfb9d578
> >> [<c00aa834>] (sys_umount+0x0/0x2f8) from [<c0028e40>]
> >> (ret_fast_syscall+0x0/0x2c)
> >> INFO: task flush-8:0:1414 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. flush-8:0???? D c02c0708???? 0? 1414????? 2 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0888>]
> >> (io_schedule+0x44/0x70) [<c02c0844>] (io_schedule+0x0/0x70) from
> >> [<c00b6458>] (sync_buffer+0x4c/0x54) r5:c0604248 r4:cfb07d9c
> >> [<c00b640c>] (sync_buffer+0x0/0x54) from [<c02c0bd4>]
> >> (__wait_on_bit_lock+0x64/0xac)
> >> [<c02c0b70>] (__wait_on_bit_lock+0x0/0xac) from [<c02c0c9c>]
> >> (out_of_line_wait_on_bit_lock+0x80/0x8c)
> >> [<c02c0c1c>] (out_of_line_wait_on_bit_lock+0x0/0x8c) from [<c00b6710>]
> >> (__lock_buffer+0x3c/0x44) [<c00b66d4>] (__lock_buffer+0x0/0x44) from
> >> [<c00b96d0>]
> >> (sync_dirty_buffer+0x60/0x144)
> >> [<c00b9670>] (sync_dirty_buffer+0x0/0x144) from [<c0105f48>]
> >> (fat_write_inode+0x1e4/0x218)
> >>? r5:00000000 r4:ce882160
> >> [<c0105d64>] (fat_write_inode+0x0/0x218) from [<c00af820>]
> >> (writeback_single_inode+0x10c/0x21c)
> >> [<c00af714>] (writeback_single_inode+0x0/0x21c) from [<c00b0168>]
> >> (writeback_inodes_wb+0x390/0x43c)
> >> [<c00afdd8>] (writeback_inodes_wb+0x0/0x43c) from [<c00b034c>]
> >> (wb_writeback+0x138/0x1b8)
> >> [<c00b0214>] (wb_writeback+0x0/0x1b8) from [<c00b0530>]
> >> (wb_do_writeback+0x68/0x1a0)
> >> [<c00b04c8>] (wb_do_writeback+0x0/0x1a0) from [<c00b0698>]
> >> (bdi_writeback_task+0x30/0xc0)
> >> [<c00b0668>] (bdi_writeback_task+0x0/0xc0) from [<c007b414>]
> >> (bdi_start_fn+0x78/0xd8)
> >>? r7:c007b39c r6:cf99daa8 r5:cf99dad8 r4:cf99da38 [<c007b39c>]
> >> (bdi_start_fn+0x0/0xd8) from [<c0051150>]
> >> (kthread+0x88/0x90) r7:c007b39c r6:cf99daa8 r5:cf897ef8 r4:cfb07fbc
> >> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
> >> r7:00000000 r6:00000000 r5:00000000 r4:00000000
> >> INFO: task scsi_eh_0:482 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. scsi_eh_0???? D c02c0708???? 0?? 482????? 2 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
> >> (schedule_timeout+0x20/0x1b8)
> >> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
> >> (wait_for_common+0xe0/0x178)
> >>? r7:7fffffff r6:cf9dc3ac r5:cf892080 r4:cf9dc3b0 [<c02c025c>]
> >> (wait_for_common+0x0/0x178) from [<c02c0464>]
> >> (wait_for_completion+0x18/0x1c)
> >> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c020bcfc>]
> >> (command_abort+0x94/0x9c)
> >> [<c020bc68>] (command_abort+0x0/0x9c) from [<c019f8fc>]
> >> (__scsi_try_to_abort_cmd+0x2c/0x30)
> >>? r7:cf9d2000 r6:cf9d3f84 r5:cf9dc000 r4:cfacf320 [<c019f8d0>]
> >> (__scsi_try_to_abort_cmd+0x0/0x30) from [<c01a12f0>]
> >> (scsi_error_handler+0x12c/0x358)
> >> [<c01a11c4>] (scsi_error_handler+0x0/0x358) from [<c0051150>]
> >> (kthread+0x88/0x90)
> >>? r7:c01a11c4 r6:cf9dc000 r5:cf867bb8 r4:cf9d3fbc [<c00510c8>]
> >> (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)? r7:00000000
> >> r6:00000000 r5:00000000 r4:00000000
> >> INFO: task usb-storage:483 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. usb-storage?? D c02c0708???? 0?? 483????? 2 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
> >> (schedule_timeout+0x20/0x1b8)
> >> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
> >> (wait_for_common+0xe0/0x178)
> >>? r7:7fffffff r6:cf9dc364 r5:cf892700 r4:cf9dc368 [<c02c025c>]
> >> (wait_for_common+0x0/0x178) from [<c02c0464>]
> >> (wait_for_completion+0x18/0x1c)
> >> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c01f1c40>]
> >> (usb_sg_wait+0x148/0x154)
> >> [<c01f1af8>] (usb_sg_wait+0x0/0x154) from [<c020c748>]
> >> (usb_stor_bulk_transfer_sglist+0xbc/0x110)
> >> [<c020c68c>] (usb_stor_bulk_transfer_sglist+0x0/0x110) from
> >> [<c020c7cc>] (usb_stor_bulk_srb+0x30/0x48) [<c020c79c>]
> >> (usb_stor_bulk_srb+0x0/0x48) from [<c020ccfc>]
> >> (usb_stor_Bulk_transport+0x110/0x2ac)
> >>? r4:ffc1300f
> >> [<c020cbec>] (usb_stor_Bulk_transport+0x0/0x2ac) from [<c020cec0>]
> >> (usb_stor_invoke_transport+0x28/0x314)
> >> [<c020ce98>] (usb_stor_invoke_transport+0x0/0x314) from [<c020becc>]
> >> (usb_stor_transparent_scsi_command+0x10/0x14)
> >>? r8:00000000 r7:c020de84 r6:cf9dc000 r5:cf9dc2bc r4:cf9f1fbc
> >> [<c020bebc>] (usb_stor_transparent_scsi_command+0x0/0x14) from
> >> [<c020dfd8>] (usb_stor_control_thread+0x154/0x21c)
> >> [<c020de84>] (usb_stor_control_thread+0x0/0x21c) from [<c0051150>]
> >> (kthread+0x88/0x90)
> >>? r6:cf9dc2bc r5:cf867c10 r4:cf9f1fbc
> >> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
> >> r7:00000000 r6:00000000 r5:00000000 r4:00000000
> >> INFO: task umount:1413 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. umount??????? D c02c0708???? 0? 1413?? 1407 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c00afb5c>]
> >> (bdi_sched_wait+0x10/0x18) [<c00afb4c>] (bdi_sched_wait+0x0/0x18) from
> >> [<c02c0d0c>] (__wait_on_bit+0x64/0xac) [<c02c0ca8>]
> >> (__wait_on_bit+0x0/0xac) from [<c02c0dd4>]
> >> (out_of_line_wait_on_bit+0x80/0x8c)
> >> [<c02c0d54>] (out_of_line_wait_on_bit+0x0/0x8c) from [<c00afbf4>]
> >> (sync_inodes_sb+0x90/0x15c)
> >> [<c00afb64>] (sync_inodes_sb+0x0/0x15c) from [<c00b3c78>]
> >> (__sync_filesystem+0x38/0x64)
> >>? r8:00000000 r7:cfb9d580 r6:c02c8724 r5:00000001 r4:cfac7c00
> >> [<c00b3c40>] (__sync_filesystem+0x0/0x64) from [<c00b3e88>]
> >> (sync_filesystem+0x54/0x5c)
> >>? r5:cfad2000 r4:cfac7c00
> >> [<c00b3e34>] (sync_filesystem+0x0/0x5c) from [<c0095ea8>]
> >> (generic_shutdown_super+0x38/0x118)
> >>? r5:cfad2000 r4:cfac7c00
> >> [<c0095e70>] (generic_shutdown_super+0x0/0x118) from [<c0095fa8>]
> >> (kill_block_super+0x20/0x38)
> >>? r7:cfb9d580 r6:cfb9d580 r5:00000003 r4:cf50a000 [<c0095f88>]
> >> (kill_block_super+0x0/0x38) from [<c00962d8>]
> >> (deactivate_super+0x50/0x68)
> >>? r5:c03a9b48 r4:cfac7c00
> >> [<c0096288>] (deactivate_super+0x0/0x68) from [<c00aa51c>]
> >> (mntput_no_expire+0x70/0xb0)
> >>? r5:cfb9d580 r4:cfac7c00
> >> [<c00aa4ac>] (mntput_no_expire+0x0/0xb0) from [<c00aaaf4>]
> >> (sys_umount+0x2c0/0x2f8)
> >>? r5:cfb9d598 r4:cfb9d578
> >> [<c00aa834>] (sys_umount+0x0/0x2f8) from [<c0028e40>]
> >> (ret_fast_syscall+0x0/0x2c)
> >> INFO: task flush-8:0:1414 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. flush-8:0???? D c02c0708???? 0? 1414????? 2 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0888>]
> >> (io_schedule+0x44/0x70) [<c02c0844>] (io_schedule+0x0/0x70) from
> >> [<c00b6458>] (sync_buffer+0x4c/0x54) r5:c0604248 r4:cfb07d9c
> >> [<c00b640c>] (sync_buffer+0x0/0x54) from [<c02c0bd4>]
> >> (__wait_on_bit_lock+0x64/0xac)
> >> [<c02c0b70>] (__wait_on_bit_lock+0x0/0xac) from [<c02c0c9c>]
> >> (out_of_line_wait_on_bit_lock+0x80/0x8c)
> >> [<c02c0c1c>] (out_of_line_wait_on_bit_lock+0x0/0x8c) from [<c00b6710>]
> >> (__lock_buffer+0x3c/0x44) [<c00b66d4>] (__lock_buffer+0x0/0x44) from
> >> [<c00b96d0>]
> >> (sync_dirty_buffer+0x60/0x144)
> >> [<c00b9670>] (sync_dirty_buffer+0x0/0x144) from [<c0105f48>]
> >> (fat_write_inode+0x1e4/0x218)
> >>? r5:00000000 r4:ce882160
> >> [<c0105d64>] (fat_write_inode+0x0/0x218) from [<c00af820>]
> >> (writeback_single_inode+0x10c/0x21c)
> >> [<c00af714>] (writeback_single_inode+0x0/0x21c) from [<c00b0168>]
> >> (writeback_inodes_wb+0x390/0x43c)
> >> [<c00afdd8>] (writeback_inodes_wb+0x0/0x43c) from [<c00b034c>]
> >> (wb_writeback+0x138/0x1b8)
> >> [<c00b0214>] (wb_writeback+0x0/0x1b8) from [<c00b0530>]
> >> (wb_do_writeback+0x68/0x1a0)
> >> [<c00b04c8>] (wb_do_writeback+0x0/0x1a0) from [<c00b0698>]
> >> (bdi_writeback_task+0x30/0xc0)
> >> [<c00b0668>] (bdi_writeback_task+0x0/0xc0) from [<c007b414>]
> >> (bdi_start_fn+0x78/0xd8)
> >>? r7:c007b39c r6:cf99daa8 r5:cf99dad8 r4:cf99da38 [<c007b39c>]
> >> (bdi_start_fn+0x0/0xd8) from [<c0051150>]
> >> (kthread+0x88/0x90) r7:c007b39c r6:cf99daa8 r5:cf897ef8 r4:cfb07fbc
> >> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
> >> r7:00000000 r6:00000000 r5:00000000 r4:00000000
> >> INFO: task scsi_eh_0:482 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. scsi_eh_0???? D c02c0708???? 0?? 482????? 2 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
> >> (schedule_timeout+0x20/0x1b8)
> >> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
> >> (wait_for_common+0xe0/0x178)
> >>? r7:7fffffff r6:cf9dc3ac r5:cf892080 r4:cf9dc3b0 [<c02c025c>]
> >> (wait_for_common+0x0/0x178) from [<c02c0464>]
> >> (wait_for_completion+0x18/0x1c)
> >> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c020bcfc>]
> >> (command_abort+0x94/0x9c)
> >> [<c020bc68>] (command_abort+0x0/0x9c) from [<c019f8fc>]
> >> (__scsi_try_to_abort_cmd+0x2c/0x30)
> >>? r7:cf9d2000 r6:cf9d3f84 r5:cf9dc000 r4:cfacf320 [<c019f8d0>]
> >> (__scsi_try_to_abort_cmd+0x0/0x30) from [<c01a12f0>]
> >> (scsi_error_handler+0x12c/0x358)
> >> [<c01a11c4>] (scsi_error_handler+0x0/0x358) from [<c0051150>]
> >> (kthread+0x88/0x90)
> >>? r7:c01a11c4 r6:cf9dc000 r5:cf867bb8 r4:cf9d3fbc [<c00510c8>]
> >> (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)? r7:00000000
> >> r6:00000000 r5:00000000 r4:00000000
> >> INFO: task usb-storage:483 blocked for more than 120 seconds.
> >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> >> message. usb-storage?? D c02c0708???? 0?? 483????? 2 0x00000000
> >> Backtrace:
> >> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
> >> (schedule_timeout+0x20/0x1b8)
> >> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
> >> (wait_for_common+0xe0/0x178)
> >>? r7:7fffffff r6:cf9dc364 r5:cf892700 r4:cf9dc368 [<c02c025c>]
> >> (wait_for_common+0x0/0x178) from [<c02c0464>]
> >> (wait_for_completion+0x18/0x1c)
> >> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c01f1c40>]
> >> (usb_sg_wait+0x148/0x154)
> >> [<c01f1af8>] (usb_sg_wait+0x0/0x154) from [<c020c748>]
> >> (usb_stor_bulk_transfer_sglist+0xbc/0x110)
> >> [<c020c68c>] (usb_stor_bulk_transfer_sglist+0x0/0x110) from
> >> [<c020c7cc>] (usb_stor_bulk_srb+0x30/0x48) [<c020c79c>]
> >> (usb_stor_bulk_srb+0x0/0x48) from [<c020ccfc>]
> >> (usb_stor_Bulk_transport+0x110/0x2ac)
> >>? r4:ffc1300f
> >> [<c020cbec>] (usb_stor_Bulk_transport+0x0/0x2ac) from [<c020cec0>]
> >> (usb_stor_invoke_transport+0x28/0x314)
> >> [<c020ce98>] (usb_stor_invoke_transport+0x0/0x314) from [<c020becc>]
> >> (usb_stor_transparent_scsi_command+0x10/0x14)
> >>? r8:00000000 r7:c020de84 r6:cf9dc000 r5:cf9dc2bc r4:cf9f1fbc
> >> [<c020bebc>] (usb_stor_transparent_scsi_command+0x0/0x14) from
> >> [<c020dfd8>] (usb_stor_control_thread+0x154/0x21c)
> >> [<c020de84>] (usb_stor_control_thread+0x0/0x21c) from [<c0051150>]
> >> (kthread+0x88/0x90)
> >>? r6:cf9dc2bc r5:cf867c10 r4:cf9f1fbc
> >> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
> >> r7:00000000 r6:00000000 r5:00000000 r4:00000000
> >> --------------------------------
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> linux-arm mailing list
> >> linux-arm at xxxxxxxxxxxxxxxxxxx
> >> http://lists.infradead.org/mailman/listinfo/linux-arm
> >>
>


From marek.vasut at gmail.com  Wed Sep  1 16:16:00 2010
From: marek.vasut at gmail.com (Marek Vasut)
Date: Wed, 1 Sep 2010 22:16:00 +0200
Subject: PXA320 SDIO driver
In-Reply-To: <AANLkTikZdYuHoTqSTznGL34E0Y=LgufGfMoJDR2SRcf0@mail.gmail.com>
References: <AANLkTi=KmheTUS0MPG73NbYXTXZYx-+jKdRuAD4Ctd5y@mail.gmail.com>
	<636151.37539.qm@web57902.mail.re3.yahoo.com>
	<AANLkTikZdYuHoTqSTznGL34E0Y=LgufGfMoJDR2SRcf0@mail.gmail.com>
Message-ID: <201009012216.00950.marek.vasut@gmail.com>

Dne ?t 31. srpna 2010 08:55:44 Eric Miao napsal(a):
> On Tue, Aug 31, 2010 at 2:33 PM, hong zhang <henryzhang62 at yahoo.com> wrote:
> > Eric,
> > 
> > Do you know where I can download the most recent BSP for PXA320?
> 
> I'm afraid you have to contact Marvell's sales representative for that.
> They do require an NDA for the extranet access. :-/

And everyone who saw that NDA, considering he's only a little bit sane, would 
bash his head to the wall until he'd fall unconscious ...

There are still some people who would do the board bringup for free/some amount 
of money btw. You can ask in the list.

What chipset does your wifi card utilize?

Cheers
> 
> > --- On Tue, 8/31/10, Eric Miao <eric.y.miao at gmail.com> wrote:
> >> From: Eric Miao <eric.y.miao at gmail.com>
> >> Subject: Re: PXA320 SDIO driver
> >> To: "hong zhang" <henryzhang62 at yahoo.com>
> >> Cc: linux-arm at lists.infradead.org
> >> Date: Tuesday, August 31, 2010, 12:48 AM
> >> On Tue, Aug 31, 2010 at 1:32 PM, hong
> >> zhang <henryzhang62 at yahoo.com>
> >> 
> >> wrote:
> >> > Eric,
> >> > 
> >> > 1. My kernel is 2.6.10 that has
> >> 
> >> drivers/mmc/host/pxamci.c too but no
> >> 
> >> > arch/arm/mach-pxa/pxa320.c.
> >> 
> >> That's way too old. I suggest you either use the mainline
> >> version
> >> or the BSP from Marvell.
> >> 
> >> > 2. My wifi is from REDPINE wifi with sdio interface.
> >> 
> >> Not sure about the support status of this wifi.
> >> 
> >> > ---henry
> >> > 
> >> > 
> >> > --- On Mon, 8/30/10, Eric Miao <eric.y.miao at gmail.com>
> >> 
> >> wrote:
> >> >> From: Eric Miao <eric.y.miao at gmail.com>
> >> >> Subject: Re: PXA320 SDIO driver
> >> >> To: "hong zhang" <henryzhang62 at yahoo.com>
> >> >> Cc: linux-arm at lists.infradead.org
> >> >> Date: Monday, August 30, 2010, 8:47 PM
> >> >> On Tue, Aug 31, 2010 at 7:04 AM, hong
> >> >> zhang <henryzhang62 at yahoo.com>
> >> >> 
> >> >> wrote:
> >> >> > List,
> >> >> > 
> >> >> > I look at arch/arm/mach-pxa subdirectory and
> >> 
> >> only see
> >> 
> >> >> em-x270.c has sdio related codes.
> >> >> 
> >> >> > Where should I look for PXA320 SDIO driver?
> >> >> 
> >> >> Hi Hong,
> >> >> 
> >> >> The SDIO controller driver is already there in
> >> >> drivers/mmc/host/pxamci.c.
> >> >> 
> >> >> The specific SDIO device driver really depends on
> >> 
> >> what you
> >> 
> >> >> are using.
> >> >> i.e. the SDIO driver for Marvell's 88E8385/8686
> >> 
> >> WiFi chip
> >> 
> >> >> can be found
> >> >> in drivers/net/wireless/libertas/...
> >> >> 
> >> >> > Any help will be appreciated!
> >> >> > 
> >> >> > 
> >> >> > ---henry
> >> 
> >> _______________________________________________
> >> 
> >> >> > linux-arm mailing list
> >> >> > linux-arm at lists.infradead.org
> >> >> > http://lists.infradead.org/mailman/listinfo/linux-arm
> >> >> 
> >> >> _______________________________________________
> >> >> linux-arm mailing list
> >> >> linux-arm at lists.infradead.org
> >> >> http://lists.infradead.org/mailman/listinfo/linux-arm
> >> 
> >> _______________________________________________
> >> linux-arm mailing list
> >> linux-arm at lists.infradead.org
> >> http://lists.infradead.org/mailman/listinfo/linux-arm
> 
> _______________________________________________
> linux-arm mailing list
> linux-arm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm


From henryzhang62 at yahoo.com  Wed Sep  1 21:56:46 2010
From: henryzhang62 at yahoo.com (hong zhang)
Date: Wed, 1 Sep 2010 18:56:46 -0700 (PDT)
Subject: PXA320 SDIO driver
In-Reply-To: <201009012216.00950.marek.vasut@gmail.com>
Message-ID: <179468.79923.qm@web57903.mail.re3.yahoo.com>

Mark,

REDPINE chip. 

---henry

--- On Wed, 9/1/10, Marek Vasut <marek.vasut at gmail.com> wrote:

> From: Marek Vasut <marek.vasut at gmail.com>
> Subject: Re: PXA320 SDIO driver
> To: linux-arm at lists.infradead.org
> Cc: "hong zhang" <henryzhang62 at yahoo.com>, "Eric Miao" <eric.y.miao at gmail.com>
> Date: Wednesday, September 1, 2010, 3:16 PM
> Dne ?t 31. srpna 2010 08:55:44 Eric
> Miao napsal(a):
> > On Tue, Aug 31, 2010 at 2:33 PM, hong zhang <henryzhang62 at yahoo.com>
> wrote:
> > > Eric,
> > > 
> > > Do you know where I can download the most recent
> BSP for PXA320?
> > 
> > I'm afraid you have to contact Marvell's sales
> representative for that.
> > They do require an NDA for the extranet access. :-/
> 
> And everyone who saw that NDA, considering he's only a
> little bit sane, would 
> bash his head to the wall until he'd fall unconscious ...
> 
> There are still some people who would do the board bringup
> for free/some amount 
> of money btw. You can ask in the list.
> 
> What chipset does your wifi card utilize?
> 
> Cheers
> > 
> > > --- On Tue, 8/31/10, Eric Miao <eric.y.miao at gmail.com>
> wrote:
> > >> From: Eric Miao <eric.y.miao at gmail.com>
> > >> Subject: Re: PXA320 SDIO driver
> > >> To: "hong zhang" <henryzhang62 at yahoo.com>
> > >> Cc: linux-arm at lists.infradead.org
> > >> Date: Tuesday, August 31, 2010, 12:48 AM
> > >> On Tue, Aug 31, 2010 at 1:32 PM, hong
> > >> zhang <henryzhang62 at yahoo.com>
> > >> 
> > >> wrote:
> > >> > Eric,
> > >> > 
> > >> > 1. My kernel is 2.6.10 that has
> > >> 
> > >> drivers/mmc/host/pxamci.c too but no
> > >> 
> > >> > arch/arm/mach-pxa/pxa320.c.
> > >> 
> > >> That's way too old. I suggest you either use
> the mainline
> > >> version
> > >> or the BSP from Marvell.
> > >> 
> > >> > 2. My wifi is from REDPINE wifi with
> sdio interface.
> > >> 
> > >> Not sure about the support status of this
> wifi.
> > >> 
> > >> > ---henry
> > >> > 
> > >> > 
> > >> > --- On Mon, 8/30/10, Eric Miao <eric.y.miao at gmail.com>
> > >> 
> > >> wrote:
> > >> >> From: Eric Miao <eric.y.miao at gmail.com>
> > >> >> Subject: Re: PXA320 SDIO driver
> > >> >> To: "hong zhang" <henryzhang62 at yahoo.com>
> > >> >> Cc: linux-arm at lists.infradead.org
> > >> >> Date: Monday, August 30, 2010, 8:47
> PM
> > >> >> On Tue, Aug 31, 2010 at 7:04 AM,
> hong
> > >> >> zhang <henryzhang62 at yahoo.com>
> > >> >> 
> > >> >> wrote:
> > >> >> > List,
> > >> >> > 
> > >> >> > I look at arch/arm/mach-pxa
> subdirectory and
> > >> 
> > >> only see
> > >> 
> > >> >> em-x270.c has sdio related codes.
> > >> >> 
> > >> >> > Where should I look for PXA320
> SDIO driver?
> > >> >> 
> > >> >> Hi Hong,
> > >> >> 
> > >> >> The SDIO controller driver is
> already there in
> > >> >> drivers/mmc/host/pxamci.c.
> > >> >> 
> > >> >> The specific SDIO device driver
> really depends on
> > >> 
> > >> what you
> > >> 
> > >> >> are using.
> > >> >> i.e. the SDIO driver for Marvell's
> 88E8385/8686
> > >> 
> > >> WiFi chip
> > >> 
> > >> >> can be found
> > >> >> in
> drivers/net/wireless/libertas/...
> > >> >> 
> > >> >> > Any help will be appreciated!
> > >> >> > 
> > >> >> > 
> > >> >> > ---henry
> > >> 
> > >>
> _______________________________________________
> > >> 
> > >> >> > linux-arm mailing list
> > >> >> > linux-arm at lists.infradead.org
> > >> >> > http://lists.infradead.org/mailman/listinfo/linux-arm
> > >> >> 
> > >> >>
> _______________________________________________
> > >> >> linux-arm mailing list
> > >> >> linux-arm at lists.infradead.org
> > >> >> http://lists.infradead.org/mailman/listinfo/linux-arm
> > >> 
> > >>
> _______________________________________________
> > >> linux-arm mailing list
> > >> linux-arm at lists.infradead.org
> > >> http://lists.infradead.org/mailman/listinfo/linux-arm
> > 
> > _______________________________________________
> > linux-arm mailing list
> > linux-arm at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm
> 
> _______________________________________________
> linux-arm mailing list
> linux-arm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm
> 


      


From marek.vasut at gmail.com  Wed Sep  1 22:24:17 2010
From: marek.vasut at gmail.com (Marek Vasut)
Date: Thu, 2 Sep 2010 04:24:17 +0200
Subject: PXA320 SDIO driver
In-Reply-To: <179468.79923.qm@web57903.mail.re3.yahoo.com>
References: <179468.79923.qm@web57903.mail.re3.yahoo.com>
Message-ID: <201009020424.18053.marek.vasut@gmail.com>

Dne ?t 2. z??? 2010 03:56:46 hong zhang napsal(a):
> Mark,
> 
> REDPINE chip.

It's their own in-house design? Or did they based the chip off some other chip?

Do they provide linux driver?

Cheers
> 
> ---henry
> 
> --- On Wed, 9/1/10, Marek Vasut <marek.vasut at gmail.com> wrote:
> > From: Marek Vasut <marek.vasut at gmail.com>
> > Subject: Re: PXA320 SDIO driver
> > To: linux-arm at lists.infradead.org
> > Cc: "hong zhang" <henryzhang62 at yahoo.com>, "Eric Miao"
> > <eric.y.miao at gmail.com> Date: Wednesday, September 1, 2010, 3:16 PM
> > Dne ?t 31. srpna 2010 08:55:44 Eric
> > 
> > Miao napsal(a):
> > > On Tue, Aug 31, 2010 at 2:33 PM, hong zhang <henryzhang62 at yahoo.com>
> > 
> > wrote:
> > > > Eric,
> > > > 
> > > > Do you know where I can download the most recent
> > 
> > BSP for PXA320?
> > 
> > > I'm afraid you have to contact Marvell's sales
> > 
> > representative for that.
> > 
> > > They do require an NDA for the extranet access. :-/
> > 
> > And everyone who saw that NDA, considering he's only a
> > little bit sane, would
> > bash his head to the wall until he'd fall unconscious ...
> > 
> > There are still some people who would do the board bringup
> > for free/some amount
> > of money btw. You can ask in the list.
> > 
> > What chipset does your wifi card utilize?
> > 
> > Cheers
> > 
> > > > --- On Tue, 8/31/10, Eric Miao <eric.y.miao at gmail.com>
> > 
> > wrote:
> > > >> From: Eric Miao <eric.y.miao at gmail.com>
> > > >> Subject: Re: PXA320 SDIO driver
> > > >> To: "hong zhang" <henryzhang62 at yahoo.com>
> > > >> Cc: linux-arm at lists.infradead.org
> > > >> Date: Tuesday, August 31, 2010, 12:48 AM
> > > >> On Tue, Aug 31, 2010 at 1:32 PM, hong
> > > >> zhang <henryzhang62 at yahoo.com>
> > > >> 
> > > >> wrote:
> > > >> > Eric,
> > > >> > 
> > > >> > 1. My kernel is 2.6.10 that has
> > > >> 
> > > >> drivers/mmc/host/pxamci.c too but no
> > > >> 
> > > >> > arch/arm/mach-pxa/pxa320.c.
> > > >> 
> > > >> That's way too old. I suggest you either use
> > 
> > the mainline
> > 
> > > >> version
> > > >> or the BSP from Marvell.
> > > >> 
> > > >> > 2. My wifi is from REDPINE wifi with
> > 
> > sdio interface.
> > 
> > > >> Not sure about the support status of this
> > 
> > wifi.
> > 
> > > >> > ---henry
> > > >> > 
> > > >> > 
> > > >> > --- On Mon, 8/30/10, Eric Miao <eric.y.miao at gmail.com>
> > > >> 
> > > >> wrote:
> > > >> >> From: Eric Miao <eric.y.miao at gmail.com>
> > > >> >> Subject: Re: PXA320 SDIO driver
> > > >> >> To: "hong zhang" <henryzhang62 at yahoo.com>
> > > >> >> Cc: linux-arm at lists.infradead.org
> > > >> >> Date: Monday, August 30, 2010, 8:47
> > 
> > PM
> > 
> > > >> >> On Tue, Aug 31, 2010 at 7:04 AM,
> > 
> > hong
> > 
> > > >> >> zhang <henryzhang62 at yahoo.com>
> > > >> >> 
> > > >> >> wrote:
> > > >> >> > List,
> > > >> >> > 
> > > >> >> > I look at arch/arm/mach-pxa
> > 
> > subdirectory and
> > 
> > > >> only see
> > > >> 
> > > >> >> em-x270.c has sdio related codes.
> > > >> >> 
> > > >> >> > Where should I look for PXA320
> > 
> > SDIO driver?
> > 
> > > >> >> Hi Hong,
> > > >> >> 
> > > >> >> The SDIO controller driver is
> > 
> > already there in
> > 
> > > >> >> drivers/mmc/host/pxamci.c.
> > > >> >> 
> > > >> >> The specific SDIO device driver
> > 
> > really depends on
> > 
> > > >> what you
> > > >> 
> > > >> >> are using.
> > > >> >> i.e. the SDIO driver for Marvell's
> > 
> > 88E8385/8686
> > 
> > > >> WiFi chip
> > > >> 
> > > >> >> can be found
> > > >> >> in
> > 
> > drivers/net/wireless/libertas/...
> > 
> > > >> >> > Any help will be appreciated!
> > > >> >> > 
> > > >> >> > 
> > > >> >> > ---henry
> > 
> > _______________________________________________
> > 
> > > >> >> > linux-arm mailing list
> > > >> >> > linux-arm at lists.infradead.org
> > > >> >> > http://lists.infradead.org/mailman/listinfo/linux-arm
> > 
> > _______________________________________________
> > 
> > > >> >> linux-arm mailing list
> > > >> >> linux-arm at lists.infradead.org
> > > >> >> http://lists.infradead.org/mailman/listinfo/linux-arm
> > 
> > _______________________________________________
> > 
> > > >> linux-arm mailing list
> > > >> linux-arm at lists.infradead.org
> > > >> http://lists.infradead.org/mailman/listinfo/linux-arm
> > > 
> > > _______________________________________________
> > > linux-arm mailing list
> > > linux-arm at lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/linux-arm
> > 
> > _______________________________________________
> > linux-arm mailing list
> > linux-arm at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm


From henryzhang62 at yahoo.com  Thu Sep  2 17:31:26 2010
From: henryzhang62 at yahoo.com (hong zhang)
Date: Thu, 2 Sep 2010 14:31:26 -0700 (PDT)
Subject: PXA320 SDIO driver
In-Reply-To: <201009020424.18053.marek.vasut@gmail.com>
Message-ID: <896455.14022.qm@web57904.mail.re3.yahoo.com>

Yes. Driver works with reference SDIO card on fedora 10.
Do you know which command can display SDIO/wifi device because lspci does not?

--- On Wed, 9/1/10, Marek Vasut <marek.vasut at gmail.com> wrote:

> From: Marek Vasut <marek.vasut at gmail.com>
> Subject: Re: PXA320 SDIO driver
> To: "hong zhang" <henryzhang62 at yahoo.com>
> Cc: "Eric Miao" <eric.y.miao at gmail.com>, linux-arm at lists.infradead.org
> Date: Wednesday, September 1, 2010, 9:24 PM
> Dne ?t 2. z??? 2010 03:56:46 hong
> zhang napsal(a):
> > Mark,
> > 
> > REDPINE chip.
> 
> It's their own in-house design? Or did they based the chip
> off some other chip?
> 
> Do they provide linux driver?
> 
> Cheers
> > 
> > ---henry
> > 
> > --- On Wed, 9/1/10, Marek Vasut <marek.vasut at gmail.com>
> wrote:
> > > From: Marek Vasut <marek.vasut at gmail.com>
> > > Subject: Re: PXA320 SDIO driver
> > > To: linux-arm at lists.infradead.org
> > > Cc: "hong zhang" <henryzhang62 at yahoo.com>,
> "Eric Miao"
> > > <eric.y.miao at gmail.com>
> Date: Wednesday, September 1, 2010, 3:16 PM
> > > Dne ?t 31. srpna 2010 08:55:44 Eric
> > > 
> > > Miao napsal(a):
> > > > On Tue, Aug 31, 2010 at 2:33 PM, hong zhang
> <henryzhang62 at yahoo.com>
> > > 
> > > wrote:
> > > > > Eric,
> > > > > 
> > > > > Do you know where I can download the
> most recent
> > > 
> > > BSP for PXA320?
> > > 
> > > > I'm afraid you have to contact Marvell's
> sales
> > > 
> > > representative for that.
> > > 
> > > > They do require an NDA for the extranet
> access. :-/
> > > 
> > > And everyone who saw that NDA, considering he's
> only a
> > > little bit sane, would
> > > bash his head to the wall until he'd fall
> unconscious ...
> > > 
> > > There are still some people who would do the
> board bringup
> > > for free/some amount
> > > of money btw. You can ask in the list.
> > > 
> > > What chipset does your wifi card utilize?
> > > 
> > > Cheers
> > > 
> > > > > --- On Tue, 8/31/10, Eric Miao <eric.y.miao at gmail.com>
> > > 
> > > wrote:
> > > > >> From: Eric Miao <eric.y.miao at gmail.com>
> > > > >> Subject: Re: PXA320 SDIO driver
> > > > >> To: "hong zhang" <henryzhang62 at yahoo.com>
> > > > >> Cc: linux-arm at lists.infradead.org
> > > > >> Date: Tuesday, August 31, 2010,
> 12:48 AM
> > > > >> On Tue, Aug 31, 2010 at 1:32 PM,
> hong
> > > > >> zhang <henryzhang62 at yahoo.com>
> > > > >> 
> > > > >> wrote:
> > > > >> > Eric,
> > > > >> > 
> > > > >> > 1. My kernel is 2.6.10 that
> has
> > > > >> 
> > > > >> drivers/mmc/host/pxamci.c too but
> no
> > > > >> 
> > > > >> > arch/arm/mach-pxa/pxa320.c.
> > > > >> 
> > > > >> That's way too old. I suggest you
> either use
> > > 
> > > the mainline
> > > 
> > > > >> version
> > > > >> or the BSP from Marvell.
> > > > >> 
> > > > >> > 2. My wifi is from REDPINE
> wifi with
> > > 
> > > sdio interface.
> > > 
> > > > >> Not sure about the support status
> of this
> > > 
> > > wifi.
> > > 
> > > > >> > ---henry
> > > > >> > 
> > > > >> > 
> > > > >> > --- On Mon, 8/30/10, Eric Miao
> <eric.y.miao at gmail.com>
> > > > >> 
> > > > >> wrote:
> > > > >> >> From: Eric Miao <eric.y.miao at gmail.com>
> > > > >> >> Subject: Re: PXA320 SDIO
> driver
> > > > >> >> To: "hong zhang" <henryzhang62 at yahoo.com>
> > > > >> >> Cc: linux-arm at lists.infradead.org
> > > > >> >> Date: Monday, August 30,
> 2010, 8:47
> > > 
> > > PM
> > > 
> > > > >> >> On Tue, Aug 31, 2010 at
> 7:04 AM,
> > > 
> > > hong
> > > 
> > > > >> >> zhang <henryzhang62 at yahoo.com>
> > > > >> >> 
> > > > >> >> wrote:
> > > > >> >> > List,
> > > > >> >> > 
> > > > >> >> > I look at
> arch/arm/mach-pxa
> > > 
> > > subdirectory and
> > > 
> > > > >> only see
> > > > >> 
> > > > >> >> em-x270.c has sdio related
> codes.
> > > > >> >> 
> > > > >> >> > Where should I look
> for PXA320
> > > 
> > > SDIO driver?
> > > 
> > > > >> >> Hi Hong,
> > > > >> >> 
> > > > >> >> The SDIO controller driver
> is
> > > 
> > > already there in
> > > 
> > > > >> >>
> drivers/mmc/host/pxamci.c.
> > > > >> >> 
> > > > >> >> The specific SDIO device
> driver
> > > 
> > > really depends on
> > > 
> > > > >> what you
> > > > >> 
> > > > >> >> are using.
> > > > >> >> i.e. the SDIO driver for
> Marvell's
> > > 
> > > 88E8385/8686
> > > 
> > > > >> WiFi chip
> > > > >> 
> > > > >> >> can be found
> > > > >> >> in
> > > 
> > > drivers/net/wireless/libertas/...
> > > 
> > > > >> >> > Any help will be
> appreciated!
> > > > >> >> > 
> > > > >> >> > 
> > > > >> >> > ---henry
> > > 
> > > _______________________________________________
> > > 
> > > > >> >> > linux-arm mailing
> list
> > > > >> >> > linux-arm at lists.infradead.org
> > > > >> >> > http://lists.infradead.org/mailman/listinfo/linux-arm
> > > 
> > > _______________________________________________
> > > 
> > > > >> >> linux-arm mailing list
> > > > >> >> linux-arm at lists.infradead.org
> > > > >> >> http://lists.infradead.org/mailman/listinfo/linux-arm
> > > 
> > > _______________________________________________
> > > 
> > > > >> linux-arm mailing list
> > > > >> linux-arm at lists.infradead.org
> > > > >> http://lists.infradead.org/mailman/listinfo/linux-arm
> > > > 
> > > >
> _______________________________________________
> > > > linux-arm mailing list
> > > > linux-arm at lists.infradead.org
> > > > http://lists.infradead.org/mailman/listinfo/linux-arm
> > > 
> > > _______________________________________________
> > > linux-arm mailing list
> > > linux-arm at lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/linux-arm
> 
> _______________________________________________
> linux-arm mailing list
> linux-arm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm
> 


      


From marek.vasut at gmail.com  Thu Sep  2 18:43:53 2010
From: marek.vasut at gmail.com (Marek Vasut)
Date: Fri, 3 Sep 2010 00:43:53 +0200
Subject: PXA320 SDIO driver
In-Reply-To: <896455.14022.qm@web57904.mail.re3.yahoo.com>
References: <896455.14022.qm@web57904.mail.re3.yahoo.com>
Message-ID: <201009030043.53126.marek.vasut@gmail.com>

Dne ?t 2. z??? 2010 23:31:26 hong zhang napsal(a):
> Yes. Driver works with reference SDIO card on fedora 10.
> Do you know which command can display SDIO/wifi device because lspci does
> not?
> 
Do they provide sources for the driver?

btw. can you show us output of the "dmesg" command a while after you insert the 
card?

> --- On Wed, 9/1/10, Marek Vasut <marek.vasut at gmail.com> wrote:
> > From: Marek Vasut <marek.vasut at gmail.com>
> > Subject: Re: PXA320 SDIO driver
> > To: "hong zhang" <henryzhang62 at yahoo.com>
> > Cc: "Eric Miao" <eric.y.miao at gmail.com>, linux-arm at lists.infradead.org
> > Date: Wednesday, September 1, 2010, 9:24 PM
> > Dne ?t 2. z??? 2010 03:56:46 hong
> > 
> > zhang napsal(a):
> > > Mark,
> > > 
> > > REDPINE chip.
> > 
> > It's their own in-house design? Or did they based the chip
> > off some other chip?
> > 
> > Do they provide linux driver?
> > 
> > Cheers
> > 
> > > ---henry
> > > 
> > > --- On Wed, 9/1/10, Marek Vasut <marek.vasut at gmail.com>
> > 
> > wrote:
> > > > From: Marek Vasut <marek.vasut at gmail.com>
> > > > Subject: Re: PXA320 SDIO driver
> > > > To: linux-arm at lists.infradead.org
> > > > Cc: "hong zhang" <henryzhang62 at yahoo.com>,
> > 
> > "Eric Miao"
> > 
> > > > <eric.y.miao at gmail.com>
> > 
> > Date: Wednesday, September 1, 2010, 3:16 PM
> > 
> > > > Dne ?t 31. srpna 2010 08:55:44 Eric
> > > > 
> > > > Miao napsal(a):
> > > > > On Tue, Aug 31, 2010 at 2:33 PM, hong zhang
> > 
> > <henryzhang62 at yahoo.com>
> > 
> > > > wrote:
> > > > > > Eric,
> > > > > > 
> > > > > > Do you know where I can download the
> > 
> > most recent
> > 
> > > > BSP for PXA320?
> > > > 
> > > > > I'm afraid you have to contact Marvell's
> > 
> > sales
> > 
> > > > representative for that.
> > > > 
> > > > > They do require an NDA for the extranet
> > 
> > access. :-/
> > 
> > > > And everyone who saw that NDA, considering he's
> > 
> > only a
> > 
> > > > little bit sane, would
> > > > bash his head to the wall until he'd fall
> > 
> > unconscious ...
> > 
> > > > There are still some people who would do the
> > 
> > board bringup
> > 
> > > > for free/some amount
> > > > of money btw. You can ask in the list.
> > > > 
> > > > What chipset does your wifi card utilize?
> > > > 
> > > > Cheers
> > > > 
> > > > > > --- On Tue, 8/31/10, Eric Miao <eric.y.miao at gmail.com>
> > > > 
> > > > wrote:
> > > > > >> From: Eric Miao <eric.y.miao at gmail.com>
> > > > > >> Subject: Re: PXA320 SDIO driver
> > > > > >> To: "hong zhang" <henryzhang62 at yahoo.com>
> > > > > >> Cc: linux-arm at lists.infradead.org
> > > > > >> Date: Tuesday, August 31, 2010,
> > 
> > 12:48 AM
> > 
> > > > > >> On Tue, Aug 31, 2010 at 1:32 PM,
> > 
> > hong
> > 
> > > > > >> zhang <henryzhang62 at yahoo.com>
> > > > > >> 
> > > > > >> wrote:
> > > > > >> > Eric,
> > > > > >> > 
> > > > > >> > 1. My kernel is 2.6.10 that
> > 
> > has
> > 
> > > > > >> drivers/mmc/host/pxamci.c too but
> > 
> > no
> > 
> > > > > >> > arch/arm/mach-pxa/pxa320.c.
> > > > > >> 
> > > > > >> That's way too old. I suggest you
> > 
> > either use
> > 
> > > > the mainline
> > > > 
> > > > > >> version
> > > > > >> or the BSP from Marvell.
> > > > > >> 
> > > > > >> > 2. My wifi is from REDPINE
> > 
> > wifi with
> > 
> > > > sdio interface.
> > > > 
> > > > > >> Not sure about the support status
> > 
> > of this
> > 
> > > > wifi.
> > > > 
> > > > > >> > ---henry
> > > > > >> > 
> > > > > >> > 
> > > > > >> > --- On Mon, 8/30/10, Eric Miao
> > 
> > <eric.y.miao at gmail.com>
> > 
> > > > > >> wrote:
> > > > > >> >> From: Eric Miao <eric.y.miao at gmail.com>
> > > > > >> >> Subject: Re: PXA320 SDIO
> > 
> > driver
> > 
> > > > > >> >> To: "hong zhang" <henryzhang62 at yahoo.com>
> > > > > >> >> Cc: linux-arm at lists.infradead.org
> > > > > >> >> Date: Monday, August 30,
> > 
> > 2010, 8:47
> > 
> > > > PM
> > > > 
> > > > > >> >> On Tue, Aug 31, 2010 at
> > 
> > 7:04 AM,
> > 
> > > > hong
> > > > 
> > > > > >> >> zhang <henryzhang62 at yahoo.com>
> > > > > >> >> 
> > > > > >> >> wrote:
> > > > > >> >> > List,
> > > > > >> >> > 
> > > > > >> >> > I look at
> > 
> > arch/arm/mach-pxa
> > 
> > > > subdirectory and
> > > > 
> > > > > >> only see
> > > > > >> 
> > > > > >> >> em-x270.c has sdio related
> > 
> > codes.
> > 
> > > > > >> >> > Where should I look
> > 
> > for PXA320
> > 
> > > > SDIO driver?
> > > > 
> > > > > >> >> Hi Hong,
> > > > > >> >> 
> > > > > >> >> The SDIO controller driver
> > 
> > is
> > 
> > > > already there in
> > 
> > drivers/mmc/host/pxamci.c.
> > 
> > > > > >> >> The specific SDIO device
> > 
> > driver
> > 
> > > > really depends on
> > > > 
> > > > > >> what you
> > > > > >> 
> > > > > >> >> are using.
> > > > > >> >> i.e. the SDIO driver for
> > 
> > Marvell's
> > 
> > > > 88E8385/8686
> > > > 
> > > > > >> WiFi chip
> > > > > >> 
> > > > > >> >> can be found
> > > > > >> >> in
> > > > 
> > > > drivers/net/wireless/libertas/...
> > > > 
> > > > > >> >> > Any help will be
> > 
> > appreciated!
> > 
> > > > > >> >> > ---henry
> > > > 
> > > > _______________________________________________
> > > > 
> > > > > >> >> > linux-arm mailing
> > 
> > list
> > 
> > > > > >> >> > linux-arm at lists.infradead.org
> > > > > >> >> > http://lists.infradead.org/mailman/listinfo/linux-arm
> > > > 
> > > > _______________________________________________
> > > > 
> > > > > >> >> linux-arm mailing list
> > > > > >> >> linux-arm at lists.infradead.org
> > > > > >> >> http://lists.infradead.org/mailman/listinfo/linux-arm
> > > > 
> > > > _______________________________________________
> > > > 
> > > > > >> linux-arm mailing list
> > > > > >> linux-arm at lists.infradead.org
> > > > > >> http://lists.infradead.org/mailman/listinfo/linux-arm
> > 
> > _______________________________________________
> > 
> > > > > linux-arm mailing list
> > > > > linux-arm at lists.infradead.org
> > > > > http://lists.infradead.org/mailman/listinfo/linux-arm
> > > > 
> > > > _______________________________________________
> > > > linux-arm mailing list
> > > > linux-arm at lists.infradead.org
> > > > http://lists.infradead.org/mailman/listinfo/linux-arm
> > 
> > _______________________________________________
> > linux-arm mailing list
> > linux-arm at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm


From henryzhang62 at yahoo.com  Fri Sep  3 18:25:41 2010
From: henryzhang62 at yahoo.com (hong zhang)
Date: Fri, 3 Sep 2010 15:25:41 -0700 (PDT)
Subject: PXA320 SDIO driver
In-Reply-To: <201009030043.53126.marek.vasut@gmail.com>
Message-ID: <802560.42775.qm@web57901.mail.re3.yahoo.com>

Marek,

Linux has SDIO stack. vendor provides wifi driver with SDIO interface like PCI interview.

My redpine wifi chip based custom SDIO card be detected in 2.6.30 but not in 2.6.18.
Redpine reference SDIO card works well in 2.6.18.

Where should I take a look in SDIO stack that invoke probe function?

---henry


      


From marek.vasut at gmail.com  Fri Sep  3 19:14:11 2010
From: marek.vasut at gmail.com (Marek Vasut)
Date: Sat, 4 Sep 2010 01:14:11 +0200
Subject: PXA320 SDIO driver
In-Reply-To: <802560.42775.qm@web57901.mail.re3.yahoo.com>
References: <802560.42775.qm@web57901.mail.re3.yahoo.com>
Message-ID: <201009040114.12095.marek.vasut@gmail.com>

Dne So 4. z??? 2010 00:25:41 hong zhang napsal(a):
> Marek,
> 
> Linux has SDIO stack. vendor provides wifi driver with SDIO interface like
> PCI interview.

Yea I know ... is the driver source available somewhere?
> 
> My redpine wifi chip based custom SDIO card be detected in 2.6.30 but not
> in 2.6.18. Redpine reference SDIO card works well in 2.6.18.

Is it really redpine chip or something rebranded (like marvell chip)?
> 
> Where should I take a look in SDIO stack that invoke probe function?

Probe function of what ?
> 
> ---henry


From mitja at lxnav.com  Tue Sep 14 08:57:09 2010
From: mitja at lxnav.com (=?iso-8859-2?Q?Mitja_=A9pes?=)
Date: Tue, 14 Sep 2010 14:57:09 +0200
Subject: SD card write problem on TX51 (i.MX51)
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAHwW0WbJwyhNsG/gnYbiZGrCgAAAEAAAAALCrAyVXLVHhN3sX8D8wW4BAAAAAA==@lxnav.com>

Hi,

I'm having trouble using SD card on Karo TX51 (i.mx515). I have an error
while writing to the SD card and no file changes are written to the SD.
The error is presented on the console as:
	mmc1: Timeout waiting for hardware interrupt
	mmcblk1: error -110 transferring data, sector 25938, nr 1, card
status 0x900
	end_request: I/O error, dev mmcblk1, sector 25938
	Buffer I/O error on device mmcblk1, logical block 25938
	lost page write due to I/O error on mmcblk1
The same error is present on evaluation board.
Reading from the SD seems to work.although when transferring big files I
periodically get an error like above.
I'm guessing it's just trying to update file access times on the SD and that
triggers the "write error".
I'm using kernel 2.6.31.

Could someone please help me and point me in the right direction on how to
solve this problem?

Thank you for your replies.

Mitja



From w.sang at pengutronix.de  Tue Sep 14 09:35:06 2010
From: w.sang at pengutronix.de (Wolfram Sang)
Date: Tue, 14 Sep 2010 15:35:06 +0200
Subject: SD card write problem on TX51 (i.MX51)
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAHwW0WbJwyhNsG/gnYbiZGrCgAAAEAAAAALCrAyVXLVHhN3sX8D8wW4BAAAAAA==@lxnav.com>
References: <!&!AAAAAAAAAAAYAAAAAAAAAHwW0WbJwyhNsG/gnYbiZGrCgAAAEAAAAALCrAyVXLVHhN3sX8D8wW4BAAAAAA==@lxnav.com>
Message-ID: <20100914133506.GD2629@pengutronix.de>

On Tue, Sep 14, 2010 at 02:57:09PM +0200, Mitja ?pes wrote:
> Hi,
> 
> I'm having trouble using SD card on Karo TX51 (i.mx515). I have an error
> while writing to the SD card and no file changes are written to the SD.
> The error is presented on the console as:
> 	mmc1: Timeout waiting for hardware interrupt
> 	mmcblk1: error -110 transferring data, sector 25938, nr 1, card
> status 0x900
> 	end_request: I/O error, dev mmcblk1, sector 25938
> 	Buffer I/O error on device mmcblk1, logical block 25938
> 	lost page write due to I/O error on mmcblk1
> The same error is present on evaluation board.
> Reading from the SD seems to work.although when transferring big files I
> periodically get an error like above.
> I'm guessing it's just trying to update file access times on the SD and that
> triggers the "write error".
> I'm using kernel 2.6.31.

There is no mmc-driver for that platform in the official 2.6.31, you
probably have a custom version. However...

> Could someone please help me and point me in the right direction on how to
> solve this problem?

...there is currently effort to bring a mmc-driver upstream. Follow this
list and you will soon find branches/patches with the current version.
Testers are always welcome :)

Kind regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm/attachments/20100914/fe092b1f/attachment.sig>

From fredpoint at gmail.com  Sat Sep 25 05:55:47 2010
From: fredpoint at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Point?=)
Date: Sat, 25 Sep 2010 11:55:47 +0200
Subject: Low limit for memory mapping
Message-ID: <AANLkTin=dKuq8GRzVpnFK0Cz2SZQ5k=CPe-o9vRsaFz_@mail.gmail.com>

Hi all,

I tried to mmap with the MAP_FIXED flags set to some addresses
starting at 0x1000 and mmap always return EPERM.

However when I can read from this document
(http://www.arm.linux.org.uk/developer/memory.txt):

00001000        TASK_SIZE-1     User space mappings
                               Per-thread mappings are placed here via
                               the mmap() system call.

But I can only map memory above 0x9000 just after where the _text is
mapped. Could someone point me out why I can't use the addresses
between 0X1000 and 0x8000 ?

I can't find any answer neither from the linux kernel source (but I'm
sure it's in it ;) ) nor from this mailing list.

Thanks

Fred.


From fredpoint at gmail.com  Sat Sep 25 06:15:56 2010
From: fredpoint at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Point?=)
Date: Sat, 25 Sep 2010 12:15:56 +0200
Subject: Memory mapping low limit
Message-ID: <AANLkTi=aK2fzYGVtR9TkDLi8-kzcTxS5XxG_QubuFL_F@mail.gmail.com>

Hi all,

I tried to mmap with the MAP_FIXED flags set to some addresses
starting at 0x1000 and mmap always return EPERM.

However when I can read from this document
(http://www.arm.linux.org.uk/developer/memory.txt):

00001000 ? ? ? ?TASK_SIZE-1 ? ? User space mappings
? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Per-thread mappings are placed here via
? ? ? ? ? ? ? ? ? ? ? ? ? ? ?the mmap() system call.

But I can only map memory above 0x9000 just after where the _text is
mapped. Could someone point me out why I can't use the addresses
between 0X1000 and 0x8000 ?

I can't find any answer neither from the linux kernel source (but I'm
sure it's in it ;) ) nor from this mailing list.

Thanks

Fred.


From linux at arm.linux.org.uk  Sat Sep 25 06:33:22 2010
From: linux at arm.linux.org.uk (Russell King - ARM Linux)
Date: Sat, 25 Sep 2010 11:33:22 +0100
Subject: Low limit for memory mapping
In-Reply-To: <AANLkTin=dKuq8GRzVpnFK0Cz2SZQ5k=CPe-o9vRsaFz_@mail.gmail.com>
References: <AANLkTin=dKuq8GRzVpnFK0Cz2SZQ5k=CPe-o9vRsaFz_@mail.gmail.com>
Message-ID: <20100925103322.GA2052@n2100.arm.linux.org.uk>

On Sat, Sep 25, 2010 at 11:55:47AM +0200, Fr?d?ric Point wrote:
> Hi all,
> 
> I tried to mmap with the MAP_FIXED flags set to some addresses
> starting at 0x1000 and mmap always return EPERM.

No idea - it should return EINVAL if it's unhappy with the address.
What does strace say when you run your program via strace?


From gilles.chanteperdrix at xenomai.org  Sat Sep 25 07:01:24 2010
From: gilles.chanteperdrix at xenomai.org (Gilles Chanteperdrix)
Date: Sat, 25 Sep 2010 13:01:24 +0200
Subject: Low limit for memory mapping
In-Reply-To: <AANLkTin=dKuq8GRzVpnFK0Cz2SZQ5k=CPe-o9vRsaFz_@mail.gmail.com>
References: <AANLkTin=dKuq8GRzVpnFK0Cz2SZQ5k=CPe-o9vRsaFz_@mail.gmail.com>
Message-ID: <4C9DD684.8070609@xenomai.org>

Fr?d?ric Point wrote:
> Hi all,
> 
> I tried to mmap with the MAP_FIXED flags set to some addresses
> starting at 0x1000 and mmap always return EPERM.
> 
> However when I can read from this document
> (http://www.arm.linux.org.uk/developer/memory.txt):
> 
> 00001000        TASK_SIZE-1     User space mappings
>                                Per-thread mappings are placed here via
>                                the mmap() system call.
> 
> But I can only map memory above 0x9000 just after where the _text is
> mapped. Could someone point me out why I can't use the addresses
> between 0X1000 and 0x8000 ?

Maybe you need to tweak /proc/sys/vm/mmap_min_addr ?

-- 
                                                                Gilles.



From pratyush.linux at gmail.com  Wed Sep  1 03:38:18 2010
From: pratyush.linux at gmail.com (Pratyush Anand)
Date: Wed, 01 Sep 2010 07:38:18 -0000
Subject: PCI master abort with USB3.0 card
Message-ID: <AANLkTi=CdAYrU6M8y2JYZRUv07SermQe7bWaZm7EcohA@mail.gmail.com>

Hello Amit,



We are using USB3.0 controller chip from NEC (D720200F1).

Arm processor is cortex-A9.



You can see the pcie implementation for my platform in this patch

http://lists.infradead.org/pipermail/linux-arm-kernel/2010-August/024364.html



Regards

Pratysuh

> Hi,
> Can you please share the USB3.0 controller chip or the PCIe card
manufacturer's name? Also, which ARM processor are you using?
> Thanks,
> - Amit
>
> On Tue, 31 Aug 2010 12:47:26 +0530 (IST) Pratyush Anand <
anand_pratyush at xxxxxxxxxxx> wrote:
>
>> Hello All,
>> I am using a PCIE base usb3.0 card on ARM based platform. Linux
>> version is 2.6.32.
>> Support of PCIE for this platform has been added by me.
>> This usb3.0 card works well , if I connect it to host intel
>> PC(fedora) having same linux kernel version.
>> But , with my board I have some issue.
>> I am able to detect the card.
>> If I connect a mass storage device to the card , it is also detected.
>> If I copy a small file from mass storage to root file system , it is
>> copied well.
>> But If I copy a big file(say 1MB) and do sync or umount operation , it
>> fails. If I try to see pci configuration register of this card then I
>> found that "Master abort received " bit is set.
>> Can anyone suggest a pointer to look into it.
>> Regards>
>> Pratyush
>> At the console i see following error:
>>
>> ------------------------------------------
>> root at xxxxxxxxxxxx:~# mount /dev/sda1 /mnt/ root at xxxxxxxxxxxx:~# cp 1MB
>> /mnt/ root at xxxxxxxxxxxx:~# umount /mnt/
>> INFO: task scsi_eh_0:482 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. scsi_eh_0     D c02c0708     0   482      2 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
>> (schedule_timeout+0x20/0x1b8)
>> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
>> (wait_for_common+0xe0/0x178)
>>  r7:7fffffff r6:cf9dc3ac r5:cf892080 r4:cf9dc3b0 [<c02c025c>]
>> (wait_for_common+0x0/0x178) from [<c02c0464>]
>> (wait_for_completion+0x18/0x1c)
>> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c020bcfc>]
>> (command_abort+0x94/0x9c)
>> [<c020bc68>] (command_abort+0x0/0x9c) from [<c019f8fc>]
>> (__scsi_try_to_abort_cmd+0x2c/0x30)
>>  r7:cf9d2000 r6:cf9d3f84 r5:cf9dc000 r4:cfacf320 [<c019f8d0>]
>> (__scsi_try_to_abort_cmd+0x0/0x30) from [<c01a12f0>]
>> (scsi_error_handler+0x12c/0x358)
>> [<c01a11c4>] (scsi_error_handler+0x0/0x358) from [<c0051150>]
>> (kthread+0x88/0x90)
>>  r7:c01a11c4 r6:cf9dc000 r5:cf867bb8 r4:cf9d3fbc [<c00510c8>]
>> (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)  r7:00000000
>> r6:00000000 r5:00000000 r4:00000000
>> INFO: task usb-storage:483 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. usb-storage   D c02c0708     0   483      2 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
>> (schedule_timeout+0x20/0x1b8)
>> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
>> (wait_for_common+0xe0/0x178)
>>  r7:7fffffff r6:cf9dc364 r5:cf892700 r4:cf9dc368 [<c02c025c>]
>> (wait_for_common+0x0/0x178) from [<c02c0464>]
>> (wait_for_completion+0x18/0x1c)
>> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c01f1c40>]
>> (usb_sg_wait+0x148/0x154)
>> [<c01f1af8>] (usb_sg_wait+0x0/0x154) from [<c020c748>]
>> (usb_stor_bulk_transfer_sglist+0xbc/0x110)
>> [<c020c68c>] (usb_stor_bulk_transfer_sglist+0x0/0x110) from
>> [<c020c7cc>] (usb_stor_bulk_srb+0x30/0x48) [<c020c79c>]
>> (usb_stor_bulk_srb+0x0/0x48) from [<c020ccfc>]
>> (usb_stor_Bulk_transport+0x110/0x2ac)
>>  r4:ffc1300f
>> [<c020cbec>] (usb_stor_Bulk_transport+0x0/0x2ac) from [<c020cec0>]
>> (usb_stor_invoke_transport+0x28/0x314)
>> [<c020ce98>] (usb_stor_invoke_transport+0x0/0x314) from [<c020becc>]
>> (usb_stor_transparent_scsi_command+0x10/0x14)
>>  r8:00000000 r7:c020de84 r6:cf9dc000 r5:cf9dc2bc r4:cf9f1fbc
>> [<c020bebc>] (usb_stor_transparent_scsi_command+0x0/0x14) from
>> [<c020dfd8>] (usb_stor_control_thread+0x154/0x21c)
>> [<c020de84>] (usb_stor_control_thread+0x0/0x21c) from [<c0051150>]
>> (kthread+0x88/0x90)
>>  r6:cf9dc2bc r5:cf867c10 r4:cf9f1fbc
>> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
>> r7:00000000 r6:00000000 r5:00000000 r4:00000000
>> INFO: task umount:1413 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. umount        D c02c0708     0  1413   1407 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c00afb5c>]
>> (bdi_sched_wait+0x10/0x18) [<c00afb4c>] (bdi_sched_wait+0x0/0x18) from
>> [<c02c0d0c>] (__wait_on_bit+0x64/0xac) [<c02c0ca8>]
>> (__wait_on_bit+0x0/0xac) from [<c02c0dd4>]
>> (out_of_line_wait_on_bit+0x80/0x8c)
>> [<c02c0d54>] (out_of_line_wait_on_bit+0x0/0x8c) from [<c00afbf4>]
>> (sync_inodes_sb+0x90/0x15c)
>> [<c00afb64>] (sync_inodes_sb+0x0/0x15c) from [<c00b3c78>]
>> (__sync_filesystem+0x38/0x64)
>>  r8:00000000 r7:cfb9d580 r6:c02c8724 r5:00000001 r4:cfac7c00
>> [<c00b3c40>] (__sync_filesystem+0x0/0x64) from [<c00b3e88>]
>> (sync_filesystem+0x54/0x5c)
>>  r5:cfad2000 r4:cfac7c00
>> [<c00b3e34>] (sync_filesystem+0x0/0x5c) from [<c0095ea8>]
>> (generic_shutdown_super+0x38/0x118)
>>  r5:cfad2000 r4:cfac7c00
>> [<c0095e70>] (generic_shutdown_super+0x0/0x118) from [<c0095fa8>]
>> (kill_block_super+0x20/0x38)
>>  r7:cfb9d580 r6:cfb9d580 r5:00000003 r4:cf50a000 [<c0095f88>]
>> (kill_block_super+0x0/0x38) from [<c00962d8>]
>> (deactivate_super+0x50/0x68)
>>  r5:c03a9b48 r4:cfac7c00
>> [<c0096288>] (deactivate_super+0x0/0x68) from [<c00aa51c>]
>> (mntput_no_expire+0x70/0xb0)
>>  r5:cfb9d580 r4:cfac7c00
>> [<c00aa4ac>] (mntput_no_expire+0x0/0xb0) from [<c00aaaf4>]
>> (sys_umount+0x2c0/0x2f8)
>>  r5:cfb9d598 r4:cfb9d578
>> [<c00aa834>] (sys_umount+0x0/0x2f8) from [<c0028e40>]
>> (ret_fast_syscall+0x0/0x2c)
>> INFO: task flush-8:0:1414 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. flush-8:0     D c02c0708     0  1414      2 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0888>]
>> (io_schedule+0x44/0x70) [<c02c0844>] (io_schedule+0x0/0x70) from
>> [<c00b6458>] (sync_buffer+0x4c/0x54) r5:c0604248 r4:cfb07d9c
>> [<c00b640c>] (sync_buffer+0x0/0x54) from [<c02c0bd4>]
>> (__wait_on_bit_lock+0x64/0xac)
>> [<c02c0b70>] (__wait_on_bit_lock+0x0/0xac) from [<c02c0c9c>]
>> (out_of_line_wait_on_bit_lock+0x80/0x8c)
>> [<c02c0c1c>] (out_of_line_wait_on_bit_lock+0x0/0x8c) from [<c00b6710>]
>> (__lock_buffer+0x3c/0x44) [<c00b66d4>] (__lock_buffer+0x0/0x44) from
>> [<c00b96d0>]
>> (sync_dirty_buffer+0x60/0x144)
>> [<c00b9670>] (sync_dirty_buffer+0x0/0x144) from [<c0105f48>]
>> (fat_write_inode+0x1e4/0x218)
>>  r5:00000000 r4:ce882160
>> [<c0105d64>] (fat_write_inode+0x0/0x218) from [<c00af820>]
>> (writeback_single_inode+0x10c/0x21c)
>> [<c00af714>] (writeback_single_inode+0x0/0x21c) from [<c00b0168>]
>> (writeback_inodes_wb+0x390/0x43c)
>> [<c00afdd8>] (writeback_inodes_wb+0x0/0x43c) from [<c00b034c>]
>> (wb_writeback+0x138/0x1b8)
>> [<c00b0214>] (wb_writeback+0x0/0x1b8) from [<c00b0530>]
>> (wb_do_writeback+0x68/0x1a0)
>> [<c00b04c8>] (wb_do_writeback+0x0/0x1a0) from [<c00b0698>]
>> (bdi_writeback_task+0x30/0xc0)
>> [<c00b0668>] (bdi_writeback_task+0x0/0xc0) from [<c007b414>]
>> (bdi_start_fn+0x78/0xd8)
>>  r7:c007b39c r6:cf99daa8 r5:cf99dad8 r4:cf99da38 [<c007b39c>]
>> (bdi_start_fn+0x0/0xd8) from [<c0051150>]
>> (kthread+0x88/0x90) r7:c007b39c r6:cf99daa8 r5:cf897ef8 r4:cfb07fbc
>> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
>> r7:00000000 r6:00000000 r5:00000000 r4:00000000
>> INFO: task scsi_eh_0:482 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. scsi_eh_0     D c02c0708     0   482      2 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
>> (schedule_timeout+0x20/0x1b8)
>> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
>> (wait_for_common+0xe0/0x178)
>>  r7:7fffffff r6:cf9dc3ac r5:cf892080 r4:cf9dc3b0 [<c02c025c>]
>> (wait_for_common+0x0/0x178) from [<c02c0464>]
>> (wait_for_completion+0x18/0x1c)
>> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c020bcfc>]
>> (command_abort+0x94/0x9c)
>> [<c020bc68>] (command_abort+0x0/0x9c) from [<c019f8fc>]
>> (__scsi_try_to_abort_cmd+0x2c/0x30)
>>  r7:cf9d2000 r6:cf9d3f84 r5:cf9dc000 r4:cfacf320 [<c019f8d0>]
>> (__scsi_try_to_abort_cmd+0x0/0x30) from [<c01a12f0>]
>> (scsi_error_handler+0x12c/0x358)
>> [<c01a11c4>] (scsi_error_handler+0x0/0x358) from [<c0051150>]
>> (kthread+0x88/0x90)
>>  r7:c01a11c4 r6:cf9dc000 r5:cf867bb8 r4:cf9d3fbc [<c00510c8>]
>> (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)  r7:00000000
>> r6:00000000 r5:00000000 r4:00000000
>> INFO: task usb-storage:483 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. usb-storage   D c02c0708     0   483      2 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
>> (schedule_timeout+0x20/0x1b8)
>> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
>> (wait_for_common+0xe0/0x178)
>>  r7:7fffffff r6:cf9dc364 r5:cf892700 r4:cf9dc368 [<c02c025c>]
>> (wait_for_common+0x0/0x178) from [<c02c0464>]
>> (wait_for_completion+0x18/0x1c)
>> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c01f1c40>]
>> (usb_sg_wait+0x148/0x154)
>> [<c01f1af8>] (usb_sg_wait+0x0/0x154) from [<c020c748>]
>> (usb_stor_bulk_transfer_sglist+0xbc/0x110)
>> [<c020c68c>] (usb_stor_bulk_transfer_sglist+0x0/0x110) from
>> [<c020c7cc>] (usb_stor_bulk_srb+0x30/0x48) [<c020c79c>]
>> (usb_stor_bulk_srb+0x0/0x48) from [<c020ccfc>]
>> (usb_stor_Bulk_transport+0x110/0x2ac)
>>  r4:ffc1300f
>> [<c020cbec>] (usb_stor_Bulk_transport+0x0/0x2ac) from [<c020cec0>]
>> (usb_stor_invoke_transport+0x28/0x314)
>> [<c020ce98>] (usb_stor_invoke_transport+0x0/0x314) from [<c020becc>]
>> (usb_stor_transparent_scsi_command+0x10/0x14)
>>  r8:00000000 r7:c020de84 r6:cf9dc000 r5:cf9dc2bc r4:cf9f1fbc
>> [<c020bebc>] (usb_stor_transparent_scsi_command+0x0/0x14) from
>> [<c020dfd8>] (usb_stor_control_thread+0x154/0x21c)
>> [<c020de84>] (usb_stor_control_thread+0x0/0x21c) from [<c0051150>]
>> (kthread+0x88/0x90)
>>  r6:cf9dc2bc r5:cf867c10 r4:cf9f1fbc
>> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
>> r7:00000000 r6:00000000 r5:00000000 r4:00000000
>> INFO: task umount:1413 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. umount        D c02c0708     0  1413   1407 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c00afb5c>]
>> (bdi_sched_wait+0x10/0x18) [<c00afb4c>] (bdi_sched_wait+0x0/0x18) from
>> [<c02c0d0c>] (__wait_on_bit+0x64/0xac) [<c02c0ca8>]
>> (__wait_on_bit+0x0/0xac) from [<c02c0dd4>]
>> (out_of_line_wait_on_bit+0x80/0x8c)
>> [<c02c0d54>] (out_of_line_wait_on_bit+0x0/0x8c) from [<c00afbf4>]
>> (sync_inodes_sb+0x90/0x15c)
>> [<c00afb64>] (sync_inodes_sb+0x0/0x15c) from [<c00b3c78>]
>> (__sync_filesystem+0x38/0x64)
>>  r8:00000000 r7:cfb9d580 r6:c02c8724 r5:00000001 r4:cfac7c00
>> [<c00b3c40>] (__sync_filesystem+0x0/0x64) from [<c00b3e88>]
>> (sync_filesystem+0x54/0x5c)
>>  r5:cfad2000 r4:cfac7c00
>> [<c00b3e34>] (sync_filesystem+0x0/0x5c) from [<c0095ea8>]
>> (generic_shutdown_super+0x38/0x118)
>>  r5:cfad2000 r4:cfac7c00
>> [<c0095e70>] (generic_shutdown_super+0x0/0x118) from [<c0095fa8>]
>> (kill_block_super+0x20/0x38)
>>  r7:cfb9d580 r6:cfb9d580 r5:00000003 r4:cf50a000 [<c0095f88>]
>> (kill_block_super+0x0/0x38) from [<c00962d8>]
>> (deactivate_super+0x50/0x68)
>>  r5:c03a9b48 r4:cfac7c00
>> [<c0096288>] (deactivate_super+0x0/0x68) from [<c00aa51c>]
>> (mntput_no_expire+0x70/0xb0)
>>  r5:cfb9d580 r4:cfac7c00
>> [<c00aa4ac>] (mntput_no_expire+0x0/0xb0) from [<c00aaaf4>]
>> (sys_umount+0x2c0/0x2f8)
>>  r5:cfb9d598 r4:cfb9d578
>> [<c00aa834>] (sys_umount+0x0/0x2f8) from [<c0028e40>]
>> (ret_fast_syscall+0x0/0x2c)
>> INFO: task flush-8:0:1414 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. flush-8:0     D c02c0708     0  1414      2 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0888>]
>> (io_schedule+0x44/0x70) [<c02c0844>] (io_schedule+0x0/0x70) from
>> [<c00b6458>] (sync_buffer+0x4c/0x54) r5:c0604248 r4:cfb07d9c
>> [<c00b640c>] (sync_buffer+0x0/0x54) from [<c02c0bd4>]
>> (__wait_on_bit_lock+0x64/0xac)
>> [<c02c0b70>] (__wait_on_bit_lock+0x0/0xac) from [<c02c0c9c>]
>> (out_of_line_wait_on_bit_lock+0x80/0x8c)
>> [<c02c0c1c>] (out_of_line_wait_on_bit_lock+0x0/0x8c) from [<c00b6710>]
>> (__lock_buffer+0x3c/0x44) [<c00b66d4>] (__lock_buffer+0x0/0x44) from
>> [<c00b96d0>]
>> (sync_dirty_buffer+0x60/0x144)
>> [<c00b9670>] (sync_dirty_buffer+0x0/0x144) from [<c0105f48>]
>> (fat_write_inode+0x1e4/0x218)
>>  r5:00000000 r4:ce882160
>> [<c0105d64>] (fat_write_inode+0x0/0x218) from [<c00af820>]
>> (writeback_single_inode+0x10c/0x21c)
>> [<c00af714>] (writeback_single_inode+0x0/0x21c) from [<c00b0168>]
>> (writeback_inodes_wb+0x390/0x43c)
>> [<c00afdd8>] (writeback_inodes_wb+0x0/0x43c) from [<c00b034c>]
>> (wb_writeback+0x138/0x1b8)
>> [<c00b0214>] (wb_writeback+0x0/0x1b8) from [<c00b0530>]
>> (wb_do_writeback+0x68/0x1a0)
>> [<c00b04c8>] (wb_do_writeback+0x0/0x1a0) from [<c00b0698>]
>> (bdi_writeback_task+0x30/0xc0)
>> [<c00b0668>] (bdi_writeback_task+0x0/0xc0) from [<c007b414>]
>> (bdi_start_fn+0x78/0xd8)
>>  r7:c007b39c r6:cf99daa8 r5:cf99dad8 r4:cf99da38 [<c007b39c>]
>> (bdi_start_fn+0x0/0xd8) from [<c0051150>]
>> (kthread+0x88/0x90) r7:c007b39c r6:cf99daa8 r5:cf897ef8 r4:cfb07fbc
>> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
>> r7:00000000 r6:00000000 r5:00000000 r4:00000000
>> INFO: task scsi_eh_0:482 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. scsi_eh_0     D c02c0708     0   482      2 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
>> (schedule_timeout+0x20/0x1b8)
>> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
>> (wait_for_common+0xe0/0x178)
>>  r7:7fffffff r6:cf9dc3ac r5:cf892080 r4:cf9dc3b0 [<c02c025c>]
>> (wait_for_common+0x0/0x178) from [<c02c0464>]
>> (wait_for_completion+0x18/0x1c)
>> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c020bcfc>]
>> (command_abort+0x94/0x9c)
>> [<c020bc68>] (command_abort+0x0/0x9c) from [<c019f8fc>]
>> (__scsi_try_to_abort_cmd+0x2c/0x30)
>>  r7:cf9d2000 r6:cf9d3f84 r5:cf9dc000 r4:cfacf320 [<c019f8d0>]
>> (__scsi_try_to_abort_cmd+0x0/0x30) from [<c01a12f0>]
>> (scsi_error_handler+0x12c/0x358)
>> [<c01a11c4>] (scsi_error_handler+0x0/0x358) from [<c0051150>]
>> (kthread+0x88/0x90)
>>  r7:c01a11c4 r6:cf9dc000 r5:cf867bb8 r4:cf9d3fbc [<c00510c8>]
>> (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)  r7:00000000
>> r6:00000000 r5:00000000 r4:00000000
>> INFO: task usb-storage:483 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
>> message. usb-storage   D c02c0708     0   483      2 0x00000000
>> Backtrace:
>> [<c02c0468>] (schedule+0x0/0x2dc) from [<c02c0954>]
>> (schedule_timeout+0x20/0x1b8)
>> [<c02c0934>] (schedule_timeout+0x0/0x1b8) from [<c02c033c>]
>> (wait_for_common+0xe0/0x178)
>>  r7:7fffffff r6:cf9dc364 r5:cf892700 r4:cf9dc368 [<c02c025c>]
>> (wait_for_common+0x0/0x178) from [<c02c0464>]
>> (wait_for_completion+0x18/0x1c)
>> [<c02c044c>] (wait_for_completion+0x0/0x1c) from [<c01f1c40>]
>> (usb_sg_wait+0x148/0x154)
>> [<c01f1af8>] (usb_sg_wait+0x0/0x154) from [<c020c748>]
>> (usb_stor_bulk_transfer_sglist+0xbc/0x110)
>> [<c020c68c>] (usb_stor_bulk_transfer_sglist+0x0/0x110) from
>> [<c020c7cc>] (usb_stor_bulk_srb+0x30/0x48) [<c020c79c>]
>> (usb_stor_bulk_srb+0x0/0x48) from [<c020ccfc>]
>> (usb_stor_Bulk_transport+0x110/0x2ac)
>>  r4:ffc1300f
>> [<c020cbec>] (usb_stor_Bulk_transport+0x0/0x2ac) from [<c020cec0>]
>> (usb_stor_invoke_transport+0x28/0x314)
>> [<c020ce98>] (usb_stor_invoke_transport+0x0/0x314) from [<c020becc>]
>> (usb_stor_transparent_scsi_command+0x10/0x14)
>>  r8:00000000 r7:c020de84 r6:cf9dc000 r5:cf9dc2bc r4:cf9f1fbc
>> [<c020bebc>] (usb_stor_transparent_scsi_command+0x0/0x14) from
>> [<c020dfd8>] (usb_stor_control_thread+0x154/0x21c)
>> [<c020de84>] (usb_stor_control_thread+0x0/0x21c) from [<c0051150>]
>> (kthread+0x88/0x90)
>>  r6:cf9dc2bc r5:cf867c10 r4:cf9f1fbc
>> [<c00510c8>] (kthread+0x0/0x90) from [<c003fb30>] (do_exit+0x0/0x5c4)
>> r7:00000000 r6:00000000 r5:00000000 r4:00000000
>> --------------------------------
>>
>>
>>
>>
>> _______________________________________________
>> linux-arm mailing list
>> linux-arm at xxxxxxxxxxxxxxxxxxx
>> http://lists.infradead.org/mailman/listinfo/linux-arm
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm/attachments/20100901/d5133368/attachment-0001.html>

