qc timeout on a marvell 88F6282 board

DISCUSSION Richard Kang 2 participants 11 messages Jun 29, 2011 – Jul 12, 2011 1 message not in the archive libata

Share & tools

Richard Kang

author

2011-06-29 09:12 UTC #0 lore raw

Hello.

I have a sil3132 pci-e card and a DB-88F6282-A-BP(Marvell development board based on Arm9).
I compiled sata_sil24 driver as a module with a cross-compiler.

But, when loading the driver, qc timeout error was occurred during ata_read_dev_id.
What is wrong, IRQ or DMA ?

I have 2.6.31.8

libata version 3.00 loaded.
bus: 'pci': add driver sata_sil24
bus: 'pci': driver_probe_device: matched device 0000:01:01.0 with driver sata_sil24
bus: 'pci': really_probe: probing driver sata_sil24 with device 0000:01:01.0
sil24_init_one: @@@ ENTER
sata_sil24 0000:01:01.0: version 1.1
(arch/arm/mm/ioremap.c) __arm_ioremap: phys_addr=e8084000 (arch/arm/mm/ioremap.c) __arm_ioremap_pfn: addr=e0a22000 (arch/arm/mm/ioremap.c) __arm_ioremap: phys_addr=e8080000 (arch/arm/mm/ioremap.c) __arm_ioremap_pfn: addr=e0a28000
ata_host_alloc: ### ENTER: max_ports=2
ata_port_alloc: ENTER
(libata-core.c) ata_link_init
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
ata_port_alloc: LEAVE
ata_port_alloc: ENTER
(libata-core.c) ata_link_init
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
ata_port_alloc: LEAVE
ata_host_alloc: ### LEAVE
sil24_init_one: DMA_MASK_64 rc=0
sil24_init_controller: === ENTER : sil24_init_controller
sil24_init_controller: host_base=e0a22000 HOST_CTRL(0x40)=81000000
sil24_init_controller: === LEAVE: HOST_CTRL=1000003
sil24_init_one: @@@ LEAVE
sil24_port_start: ENTER ap=d1898000 ata4294967295
sil24_port_start: kernel va=ffc08000 cb_dma=118a0000
sil24_port_start: LEAVE
__ata_port_freeze: ENTER: ap=d1898000
__ata_port_freeze: LEAVE: ata4294967295 port frozen
sil24_port_start: ENTER ap=d1630000 ata4294967295
sil24_port_start: kernel va=ffc27000 cb_dma=11800000
sil24_port_start: LEAVE
__ata_port_freeze: ENTER: ap=d1630000
__ata_port_freeze: LEAVE: ata4294967295 port frozen
sil24_interrupt: ***** ENTER: sil24_interrupt
sil24_interrupt: host_base=e0a22000 HOST_IRQ_STAT=0
sil24_interrupt: ***** LEAVE
(libata-core.c) ata_host_register *ENTER*
scsi2 : sata_sil24
device: 'host2': device_add
bus: 'scsi': add device host2
device: 'host2': device_add
scsi3 : sata_sil24
device: 'host3': device_add
bus: 'scsi': add device host3
device: 'host3': device_add
ata1: SATA max UDMA/100 host m128@0xe8084000 port 0xe8080000 irq 10
ata2: SATA max UDMA/100 host m128@0xe8084000 port 0xe8082000 irq 10 (libata-core.c) ata_host_register *LEAVE*
driver: '0000:01:01.0': driver_bound: bound to device 'sata_sil24'
bus: 'pci': really_probe: bound device 0000:01:01.0 to driver sata_sil24
ata_port_schedule_eh: port EH scheduled
ata_scsi_error: ENTER
(libata-eh.c) ata_scsi_error
ata_port_flush_task: ENTER
ata1: ata_port_flush_task: EXIT
sil24_error_handler: ENTER
sil24_init_port: +++ ENTER port_base=e0a28000
sil24_init_port: +++ LEAVE
ata_eh_link_autopsy: ENTER
ata_eh_recover: ENTER
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
__ata_port_freeze: ENTER: ap=d1898000
__ata_port_freeze: LEAVE: ata1 port frozen
sil24_softreset: ENTER
sil24_init_port: +++ ENTER port_base=e0a28000
sil24_init_port: +++ LEAVE
sil24_softreset: call -> sil24_exec_polled_cmd:
sil24_exec_polled_cmd: ENTER: irq_enabled=0
(libata-core.c) ata_tf_to_fis: 27 0f 00 00
sil24_exec_polled_cmd: LEAVE: PORT_IRQ_STAT=b40000 rc=0
sil24_softreset: call -> sil24_read_tf
sil24_read_tf: ENTER: tag=0
(libata-core.c) ata_tf_from_fis
sil24_read_tf: LEAVE: 27 0f 50 01 01 00 00 00 [01]
ata_dev_classify: found ATA device by sig
sil24_softreset: EXIT, class=1
sil24_thaw: ENTER
sil24_thaw: LEAVE: irq_enabled=8d3
ata_eh_thaw_port: ata1 port thawed
ata_std_postreset: ENTER
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata_std_postreset: EXIT
ata_eh_revalidate_and_attach: ENTER
ata1.00: ata_dev_read_id: ENTER
(libata-core.c) ata_dev_read_id
ata_do_dev_read_id: (libata-core.c) call -> ata_exec_internal
ata_exec_internal_sg: (libata-core.c) ENTER
ata_sg_setup: ENTER, ata1
ata_sg_setup: qc->sg=d15cfd2c
ata_sg_setup: 1 sg elements mapped
sil24_qc_prep: cb=ffc08000 sil24(qc->tag)=0
sil24_qc_prep: cmd_block[0]=ffc08000 cmd_block[1]=ffc09000 cmd_block[2]=ffc0a000
sil24_qc_prep: pp=d122a6f8 prb=ffc08000 sge=ffc08020 (libata-core.c) ata_tf_to_fis: 27 80 ec 00
sil24_fill_sg: ENTER: sge=ffc08020
sil24_fill_sg: sg_dma_addr=0x11899578 -> cpu_to_le64=0x11899578 -> cpu_to_le32=0x11899578
sil24_fill_sg: LEAVE
sil24_qc_issue: (sata_sil24.c) ENTER:
sil24_qc_issue: (sata_sil24.c) LEAVE:
ata_exec_internal_sg: (libata-core.c) call -> wait_for_completion_timeout rc=0
ata_port_flush_task: ENTER
ata1: ata_port_flush_task: EXIT
(libata-core.c) ata_qc_complete
(sata_sil24.c) sil24_qc_fill_rtf
sil24_read_tf: ENTER: tag=0
(libata-core.c) ata_tf_from_fis
sil24_read_tf: LEAVE: 00 00 8a 11 00 00 00 00 [00]
ata_sg_clean: unmapping 1 sg elements
(libata-core.c) ata_qc_complete_internal: waiting=d15cfcdc __ata_port_freeze: ENTER: ap=d1898000
__ata_port_freeze: LEAVE: ata1 port frozen
ata1.00: qc timeout (cmd 0xec)
(sata_sil24.c) sil24_post_internal_cmd: qc->flag=10010
sil24_init_port: +++ ENTER port_base=e0a28000
__ata_port_freeze: ENTER: ap=d1898000
__ata_port_freeze: LEAVE: ata1 port frozen
(sata_sil24.c) sil24_post_internal_cmd <- ata_eh_freeze_port
ata_exec_internal_sg: (libata-core.c) LEAVE: err_mask=4 (libata-core.c) ata_dev_read_id <- ata_do_dev_read_id: err_mask=4 ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata_eh_revalidate_and_attach: EXIT rc=-5
__ata_port_freeze: ENTER: ap=d1898000
__ata_port_freeze: LEAVE: ata1 port frozen
ata1: controller in dubious state, performing PORT_RST
sil24_softreset: ENTER
sil24_init_port: +++ ENTER port_base=e0a28000
sil24_init_port: +++ LEAVE
sil24_softreset: call -> sil24_exec_polled_cmd:
sil24_exec_polled_cmd: ENTER: irq_enabled=0
(libata-core.c) ata_tf_to_fis: 27 0f 00 00
sil24_exec_polled_cmd: LEAVE: PORT_IRQ_STAT=b40000 rc=0
sil24_softreset: call -> sil24_read_tf
sil24_read_tf: ENTER: tag=0
(libata-core.c) ata_tf_from_fis
sil24_read_tf: LEAVE: 27 0f 50 01 01 00 00 00 [01]
ata_dev_classify: found ATA device by sig
sil24_softreset: EXIT, class=1
sil24_thaw: ENTER
sil24_thaw: LEAVE: irq_enabled=8d3
ata_eh_thaw_port: ata1 port thawed
ata_std_postreset: ENTER
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata_std_postreset: EXIT
ata_eh_revalidate_and_attach: ENTER
ata1.00: ata_dev_read_id: ENTER
(libata-core.c) ata_dev_read_id
ata_do_dev_read_id: (libata-core.c) call -> ata_exec_internal
ata_exec_internal_sg: (libata-core.c) ENTER
ata_sg_setup: ENTER, ata1
ata_sg_setup: qc->sg=d15cfd2c
ata_sg_setup: 1 sg elements mapped
sil24_qc_prep: cb=ffc08000 sil24(qc->tag)=0
sil24_qc_prep: cmd_block[0]=ffc08000 cmd_block[1]=ffc09000 cmd_block[2]=ffc0a000
sil24_qc_prep: pp=d122a6f8 prb=ffc08000 sge=ffc08020 (libata-core.c) ata_tf_to_fis: 27 80 ec 00
sil24_fill_sg: ENTER: sge=ffc08020
sil24_fill_sg: sg_dma_addr=0x11899578 -> cpu_to_le64=0x11899578 -> cpu_to_le32=0x11899578
sil24_fill_sg: LEAVE
sil24_qc_issue: (sata_sil24.c) ENTER:
sil24_qc_issue: (sata_sil24.c) LEAVE:
ata_exec_internal_sg: (libata-core.c) call -> wait_for_completion_timeout rc=0
ata_port_flush_task: ENTER
ata1: ata_port_flush_task: EXIT
(libata-core.c) ata_qc_complete
(sata_sil24.c) sil24_qc_fill_rtf
sil24_read_tf: ENTER: tag=0
(libata-core.c) ata_tf_from_fis
sil24_read_tf: LEAVE: 00 00 8a 11 00 00 00 00 [00]
ata_sg_clean: unmapping 1 sg elements
(libata-core.c) ata_qc_complete_internal: waiting=d15cfcdc __ata_port_freeze: ENTER: ap=d1898000
__ata_port_freeze: LEAVE: ata1 port frozen
ata1.00: qc timeout (cmd 0xec)
(sata_sil24.c) sil24_post_internal_cmd: qc->flag=10010
sil24_init_port: +++ ENTER port_base=e0a28000
__ata_port_freeze: ENTER: ap=d1898000
__ata_port_freeze: LEAVE: ata1 port frozen
(sata_sil24.c) sil24_post_internal_cmd <- ata_eh_freeze_port
ata_exec_internal_sg: (libata-core.c) LEAVE: err_mask=4 (libata-core.c) ata_dev_read_id <- ata_do_dev_read_id: err_mask=4 ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata_eh_revalidate_and_attach: EXIT rc=-5
ata1: limiting SATA link speed to 1.5 Gbps
__ata_port_freeze: ENTER: ap=d1898000
__ata_port_freeze: LEAVE: ata1 port frozen
ata1: controller in dubious state, performing PORT_RST

Thank you,

saeed bishara

2011-07-03 12:52 UTC #1 lore raw

2011/6/29 Richard Kang <[email protected]>:

Quoted 9 lines

Hello.
I have a sil3132 pci-e card and a DB-88F6282-A-BP(Marvell development board based on Arm9).
I compiled sata_sil24 driver as a module with a cross-compiler.
But, when loading the driver, qc timeout error was occurred during ata_read_dev_id.
What is wrong, IRQ or DMA ?

looks to me this is DMA issue, can you force pio mode? you can do that by adding "libata.dma=0" to the kernel command line.
saeed

Quoted 1 line

I have 2.6.31.8

Richard Kang

author

2011-07-05 08:27 UTC #2 lore raw

Quoted 8 lines

2011/6/29 Richard Kang<[email protected]>:
Quoted 6 lines
Hello.
I have a sil3132 pci-e card and a DB-88F6282-A-BP(Marvell development board based on Arm9).
I compiled sata_sil24 driver as a module with a cross-compiler.

Quoted 8 lines

Quoted 3 lines
But, when loading the driver, qc timeout error was occurred during ata_read_dev_id.
What is wrong, IRQ or DMA ?
looks to me this is DMA issue, can you force pio mode? you can do that by adding "libata.dma=0" to the kernel command line.
saeed
Quoted 1 line
I have 2.6.31.8

Dear saeed,

I excuted libata.dma=0 through "$modprobe libata dma=0" Then I excuted "$modprobe sata_sil24"

But, result is same as before.
I think sata_sil24 supports only dma not pio, right?

Thank you.

saeed bishara

2011-07-05 10:11 UTC #3 lore raw

Quoted 19 lines · Richard Kang

Quoted 9 lines
2011/6/29 Richard Kang<[email protected]>:
Quoted 7 lines
Hello.
I have a sil3132 pci-e card and a DB-88F6282-A-BP(Marvell development board based on Arm9).
I compiled sata_sil24 driver as a module with a cross-compiler.
Quoted 9 lines
Quoted 3 lines
But, when loading the driver, qc timeout error was occurred during ata_read_dev_id.
What is wrong, IRQ or DMA ?
looks to me this is DMA issue, can you force pio mode? you can do that by adding "libata.dma=0" to the kernel command line.
saeed
Quoted 1 line
I have 2.6.31.8

Quoted 7 lines

Dear saeed,
I excuted libata.dma=0 through "$modprobe libata dma=0" Then I excuted "$modprobe sata_sil24"
But, result is same as before.
I think sata_sil24 supports only dma not pio, right?

I don't think so.
can you check if interrupts working fine?
you can test that by loading the driver without any connected disk, then check if the controller raises any interrupt from /proc/interrupts when plugging a disk,
saeed

Richard Kang

author

2011-07-06 06:43 UTC #4 lore raw

2011-07-05 오후 7:11, saeed bishara 쓴 글:

Quoted 21 lines · Richard Kang

Quoted 20 lines
Quoted 7 lines
2011/6/29 Richard Kang<[email protected]>:
Quoted 6 lines
Hello.
I have a sil3132 pci-e card and a DB-88F6282-A-BP(Marvell development board based on Arm9).
I compiled sata_sil24 driver as a module with a cross-compiler.
Quoted 8 lines
Quoted 3 lines
But, when loading the driver, qc timeout error was occurred during ata_read_dev_id.
What is wrong, IRQ or DMA ?
looks to me this is DMA issue, can you force pio mode? you can do that by adding "libata.dma=0" to the kernel command line.
saeed
Quoted 1 line
I have 2.6.31.8
Dear saeed,
I excuted libata.dma=0 through "$modprobe libata dma=0" Then I excuted "$modprobe sata_sil24"

Quoted 9 lines

Quoted 2 lines
But, result is same as before.
I think sata_sil24 supports only dma not pio, right?
I don't think so.
can you check if interrupts working fine?
you can test that by loading the driver without any connected disk, then check if the controller raises any interrupt from /proc/interrupts when plugging a disk,
saeed

Dear saeed,

As your instructions, I checked interrupt.
At first, I load a sata_sil24 driver without a disk. (I added the log.)

--------------------------------------------------------------------------------
sil24_init_one: @@@ ENTER
(arch/arm/mm/ioremap.c) __arm_ioremap: phys_addr=e8084000 (arch/arm/mm/ioremap.c) __arm_ioremap_pfn: addr=e0a22000 (arch/arm/mm/ioremap.c) __arm_ioremap: phys_addr=e8080000 (arch/arm/mm/ioremap.c) __arm_ioremap_pfn: addr=e0a28000
ata_host_alloc: ### ENTER: max_ports=2
ata_port_alloc: ENTER
(libata-core.c) ata_link_init
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
ata_port_alloc: LEAVE
ata_port_alloc: ENTER
(libata-core.c) ata_link_init
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
ata_port_alloc: LEAVE
ata_host_alloc: ### LEAVE
sil24_init_one: DMA_MASK_64 rc=0
sil24_init_controller: === ENTER : sil24_init_controller
sil24_init_controller: host_base=e0a22000 HOST_CTRL(0x40)=81000000
sil24_init_controller: === LEAVE: HOST_CTRL=1000003
sil24_init_one: @@@ LEAVE
sil24_port_start: ENTER ap=d1668000 ata4294967295
sil24_port_start: kernel va=ffc08000 cb_dma=11800000
sil24_port_start: LEAVE
__ata_port_freeze: ENTER: ap=d1668000
__ata_port_freeze: LEAVE: ata4294967295 port frozen
sil24_port_start: ENTER ap=d164c000 ata4294967295
sil24_port_start: kernel va=ffc27000 cb_dma=117a0000
sil24_port_start: LEAVE
__ata_port_freeze: ENTER: ap=d164c000
__ata_port_freeze: LEAVE: ata4294967295 port frozen
sil24_interrupt: ***** ENTER: sil24_interrupt
sil24_interrupt: host_base=e0a22000 HOST_IRQ_STAT=0
sil24_interrupt: ***** LEAVE
(libata-core.c) ata_host_register *ENTER*
scsi2 : sata_sil24
scsi3 : sata_sil24
ata1: SATA max UDMA/100 host m128@0xe8084000 port 0xe8080000 irq 10
ata2: SATA max UDMA/100 host m128@0xe8084000 port 0xe8082000 irq 10 (libata-core.c) ata_host_register *LEAVE*
ata_port_schedule_eh: port EH scheduled
ata_scsi_error: ENTER
(libata-eh.c) ata_scsi_error
ata_port_flush_task: ENTER
sil24_error_handler: ENTER
sil24_init_port: +++ ENTER port_base=e0a28000
sil24_init_port: +++ LEAVE
ata_eh_link_autopsy: ENTER
ata_eh_recover: ENTER
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
__ata_port_freeze: ENTER: ap=d1668000
__ata_port_freeze: LEAVE: ata1 port frozen
sil24_thaw: ENTER
sil24_thaw: LEAVE: irq_enabled=8d3
ata_eh_thaw_port: ata1 port thawed
ata_std_postreset: ENTER
ata1: SATA link down (SStatus 0 SControl 0)
ata_std_postreset: EXIT
ata_eh_revalidate_and_attach: ENTER
ata_eh_recover: EXIT, rc=0
sil24_error_handler: LEAVE
ata_scsi_error: EXIT
ata_port_schedule_eh: port EH scheduled
ata_scsi_error: ENTER
(libata-eh.c) ata_scsi_error
ata_port_flush_task: ENTER
sil24_error_handler: ENTER
sil24_init_port: +++ ENTER port_base=e0a2a000
sil24_init_port: +++ LEAVE
ata_eh_link_autopsy: ENTER
ata_eh_recover: ENTER
ata_dev_init: (libata-core.c) ENTER
ata_dev_init: (libata-core.c) LEAVE
__ata_port_freeze: ENTER: ap=d164c000
__ata_port_freeze: LEAVE: ata2 port frozen
sil24_thaw: ENTER
sil24_thaw: LEAVE: irq_enabled=8d3
ata_eh_thaw_port: ata2 port thawed
ata_std_postreset: ENTER
ata2: SATA link down (SStatus 0 SControl 0)
ata_std_postreset: EXIT
ata_eh_revalidate_and_attach: ENTER
ata_eh_recover: EXIT, rc=0
sil24_error_handler: LEAVE
ata_scsi_error: EXIT
--------------------------------------------------------------------------------

It seems no problem.
Then I plug a disk. Followings are debug msg of sil24_interrupt and contents of /proc/interrupts. An interrupt is occurred and no error.

--------------------------------------------------------------------------------
sil24_interrupt: ***** ENTER: sil24_interrupt
sil24_interrupt: host_base=e0a22000 HOST_IRQ_STAT=2 (sata_sil24.c) sil24_host_intr (sata_sil24.c) sil24_host_intr -> sil24_error_intr
ata_port_schedule_eh: port EH scheduled __ata_port_freeze: ENTER: ap=d164c000 __ata_port_freeze: LEAVE: ata2 port frozen
sil24_interrupt: ***** LEAVE
--------------------------------------------------------------------------------
sh-3.2# cat /proc/interrupts
CPU0

  1:      20689           -  kw_tick
 10:          1           -  sata_sil24
 11:       2901           -  mv_ethernet
 19:          0           -  ehci_hcd:usb1
 21:          0           -  mvSata
 22:          0           -  cesa
 28:       2145           -  mvsdio
 29:          0           -  mv64xxx_i2c
 33:        242           -  serial

Err: 0
--------------------------------------------------------------------------------

I can't find reason of not working. Please advise to me.

Thank you.

saeed bishara

2011-07-06 08:07 UTC #5 lore raw

Richard,

this board is supported by mainline kernel, can you try latest
version (3.0-rcX)?

Quoted 4 lines

I can't find reason of not working. Please advise to me.
Thank you.

A message that is not in the archive (sent off-list or not yet received): CAMAG_edjasMffHA2tozzBEUWf27BPvjF_=fOL_N9oktTyTradQ@mail.gmail.com

Richard Kang

author

2011-07-07 03:00 UTC #7 lore raw

2011-07-06 오후 5:16, saeed bishara 쓴 글:

Quoted 5 lines · saeed bishara

Quoted 4 lines
Richard,
this board is supported by mainline kernel, can you try latest
version (3.0-rcX)?

Quoted 8 lines

in order to do that, you need to build the kernel with "make kirkwood_defconfig",
then do the following from u-boot:
Marvell>>  setenv mainlineLinux yes
Marvell>>  setenv arcNumber 1680
Marvell>>  saveenv
Marvell>>  reset

Dear saeed,

I tried to build the kernel with "make kirkwood_defconfig". But, during "make uImage", some errors occurred.

Is it impossible to excute your (u-boot) commands with kernel image by "make mv_kw_defconfig" ?

Thank you.
------------------------------------------------------------------------------------------------------------
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
Generating include/asm-arm/mach-types.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-arm

  CC      kernel/bounds.s
  GEN     include/linux/bounds.h
  CC      arch/arm/kernel/asm-offsets.s
  GEN     include/asm/asm-offsets.h
  CALL    scripts/checksyscalls.sh

<stdin>:1351:2: warning: #warning syscall migrate_pages not implemented <stdin>:1407:2: warning: #warning syscall pselect6 not implemented <stdin>:1411:2: warning: #warning syscall ppoll not implemented <stdin>:1451:2: warning: #warning syscall epoll_pwait not implemented

  CC      scripts/mod/empty.o
  HOSTCC  scripts/mod/mk_elfconfig
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/file2alias.o
  HOSTCC  scripts/mod/modpost.o

scripts/mod/modpost.c: In function ‘get_markers’:
scripts/mod/modpost.c:1562:12: warning: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result scripts/mod/modpost.c: In function ‘add_marker’:
scripts/mod/modpost.c:1982:10: warning: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result

  HOSTCC  scripts/mod/sumversion.o
  HOSTLD  scripts/mod/modpost
  HOSTCC  scripts/kallsyms
scripts/kallsyms.c: In function ‘read_symbol’:
scripts/kallsyms.c:112:9: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result
  HOSTCC  scripts/conmakehash
  CC      init/main.o
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  CC      init/do_mounts.o
  LD      init/mounts.o
  CC      init/noinitramfs.o
  CC      init/calibrate.o
  LD      init/built-in.o
  LD      usr/built-in.o
  CC      arch/arm/kernel/compat.o
  CC      arch/arm/kernel/elf.o
  AS      arch/arm/kernel/entry-armv.o
  AS      arch/arm/kernel/entry-common.o
  CC      arch/arm/kernel/irq.o
  CC      arch/arm/kernel/process.o
  CC      arch/arm/kernel/ptrace.o
  CC      arch/arm/kernel/setup.o
  CC      arch/arm/kernel/signal.o
  CC      arch/arm/kernel/sys_arm.o
  CC      arch/arm/kernel/stacktrace.o
  CC      arch/arm/kernel/time.o
  CC      arch/arm/kernel/traps.o
  CC      arch/arm/kernel/armksyms.o
  CC      arch/arm/kernel/module.o
  CC      arch/arm/kernel/bios32.o
  CC      arch/arm/kernel/isa.o
  CC      arch/arm/kernel/kprobes.o
  CC      arch/arm/kernel/kprobes-decode.o
  CC      arch/arm/kernel/unwind.o
  CC      arch/arm/kernel/io.o
  AS      arch/arm/kernel/debug.o
  LD      arch/arm/kernel/built-in.o
  AS      arch/arm/kernel/head.o
  CC      arch/arm/kernel/init_task.o
  LDS     arch/arm/kernel/vmlinux.lds
  CC      arch/arm/mm/dma-mapping.o
  CC      arch/arm/mm/extable.o
  CC      arch/arm/mm/fault.o
  CC      arch/arm/mm/init.o
  CC      arch/arm/mm/iomap.o
  CC      arch/arm/mm/fault-armv.o
  CC      arch/arm/mm/flush.o
  CC      arch/arm/mm/ioremap.o
  CC      arch/arm/mm/mmap.o
  CC      arch/arm/mm/pgd.o
  CC      arch/arm/mm/mmu.o
arch/arm/mm/mmu.c: In function 'sanity_check_meminfo':
arch/arm/mm/mmu.c:690: warning: unused variable 'highmem'
  CC      arch/arm/mm/proc-syms.o
  CC      arch/arm/mm/alignment.o
  AS      arch/arm/mm/abort-ev5t.o
  CC      arch/arm/mm/copypage-feroceon.o

/tmp/ccyqzNzD.s: Assembler messages:
/tmp/ccyqzNzD.s:38: Error: selected processor does not support pld [lr,#32]' /tmp/ccyqzNzD.s:39: Error: selected processor does not support pld [lr,#64]' /tmp/ccyqzNzD.s:40: Error: selected processor does not support pld [lr,#96]' /tmp/ccyqzNzD.s:41: Error: selected processor does not support pld [lr,#128]' /tmp/ccyqzNzD.s:42: Error: selected processor does not support pld [lr,#160]' /tmp/ccyqzNzD.s:43: Error: selected processor does not support pld [lr,#192]' /tmp/ccyqzNzD.s:44: Error: selected processor does not support `pld [lr,#224]' make[1]: *** [arch/arm/mm/copypage-feroceon.o] Error 1
make: *** [arch/arm/mm] Error 2
------------------------------------------------------------------------------------------------------------

Richard Kang

author

2011-07-07 06:36 UTC #8 lore raw

In reply to saeed bishara

2011-07-06 오후 5:07, saeed bishara 쓴 글:

Quoted 4 lines

Richard,
this board is supported by mainline kernel, can you try latest
version (3.0-rcX)?

Quoted 9 lines

Quoted 4 lines
I can't find reason of not working. Please advise to me.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Dear saeed,

I tested sata_sil24 driver with 3.0.0-rc6.
At first booting, machine id was not supported in new kernel. And I replaced id(0x690) of DB-88F6281-BP with 0x20f. After changing machine id, booting was completed.

I loaded "libata dma=0" and "sata_sil24". But result was same to before. -> qc timeout(0xec)

Thank you.

saeed bishara

2011-07-07 06:44 UTC #9 lore raw

Quoted 19 lines · Richard Kang

2011-07-06 오후 5:07, saeed bishara 쓴 글:
Quoted 6 lines
Richard,
this board is supported by mainline kernel, can you try latest version (3.0-rcX)?
Quoted 1 line
Quoted 9 lines
Quoted 4 lines
I can't find reason of not working. Please advise to me.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Dear saeed,

Quoted 7 lines

I tested sata_sil24 driver with 3.0.0-rc6.
At first booting, machine id was not supported in new kernel. And I replaced id(0x690) of DB-88F6281-BP with 0x20f. After changing machine id, booting was completed.
I loaded "libata dma=0" and "sata_sil24". But result was same to before. -> qc timeout(0xec)

does this controller (sil24) works on different platfrom (PC)? have you tried different disk?

Quoted 3 lines

Thank you.

Richard Kang

author

2011-07-11 08:01 UTC #10 lore raw

2011-07-07 오후 3:44, saeed bishara 쓴 글:

Quoted 24 lines · Richard Kang

Quoted 16 lines
2011-07-06 오후 5:07, saeed bishara 쓴 글:
Quoted 4 lines
Richard,
this board is supported by mainline kernel, can you try latest
version (3.0-rcX)?
Quoted 9 lines
Quoted 4 lines
I can't find reason of not working. Please advise to me.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Dear saeed,
Quoted 7 lines
I tested sata_sil24 driver with 3.0.0-rc6.
At first booting, machine id was not supported in new kernel. And I replaced id(0x690) of DB-88F6281-BP with 0x20f. After changing machine id, booting was completed.
I loaded "libata dma=0" and "sata_sil24". But result was same to before. -> qc timeout(0xec)

Quoted 9 lines

does this controller (sil24) works on different platfrom (PC)? have you tried different disk?
Quoted 2 lines
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Dear saeed,

I tested this controller and this disk on a PC(ubuntu 10.10). The controller works well. I test disk I/O. No problem.

Thank you.

Richard Kang

author

2011-07-12 08:19 UTC #11 lore raw

In reply to saeed bishara

2011-07-07 오후 3:44, saeed bishara 쓴 글:

Quoted 24 lines · Richard Kang

Quoted 16 lines
2011-07-06 오후 5:07, saeed bishara 쓴 글:
Quoted 4 lines
Richard,
this board is supported by mainline kernel, can you try latest
version (3.0-rcX)?
Quoted 9 lines
Quoted 4 lines
I can't find reason of not working. Please advise to me.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Dear saeed,
Quoted 7 lines
I tested sata_sil24 driver with 3.0.0-rc6.
At first booting, machine id was not supported in new kernel. And I replaced id(0x690) of DB-88F6281-BP with 0x20f. After changing machine id, booting was completed.
I loaded "libata dma=0" and "sata_sil24". But result was same to before. -> qc timeout(0xec)

Quoted 9 lines

does this controller (sil24) works on different platfrom (PC)? have you tried different disk?
Quoted 2 lines
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Dear saeed,

I patched a board for pci_err_handling. The patch file is given from marvell. And I re-test a module of sata_sil24.

When I connect a disk to a Pex card(sil3132), Pex error is occurred. Following is error message.

-> PCI express error : irq - 45, Pex number: 1, Interrupt Cause Register value: 400

irq-45 is defined as IRQ_PEX1_ERR and the value of 0x400 means fatal error. This error is occurred after "sil24_qc_issue".
Function of sil24_qc_issue is to write dma addr to PORT_CMD_ACTIVATE address. Therefore, I think it is dma issue, right?

Now I am checking dma setting of a Dev-Board.

Thank you.