ACS ACR122U not working: pn533_usb 1-1:1.0: NFC: Couldn't poweron...

cmmps · 2018-05-15 15:56:14

Dear all

I'm trying to connect a ACS ACR122U card reader but it's not working and I find the following trace with "dmesg":

[   44.100275] usb 1-1: new full-speed USB device number 9 using xhci_hcd
[   44.244419] usb 1-1: New USB device found, idVendor=072f, idProduct=2200
[   44.244434] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   44.244443] usb 1-1: Product: ACR122U PICC Interface
[   44.244451] usb 1-1: Manufacturer: ACS
[   44.287396] nfc: nfc_init: NFC Core ver 0.1
[   44.287414] NET: Registered protocol family 39
[   44.291974] ------------[ cut here ]------------
[   44.291975] transfer buffer not dma capable
[   44.292009] WARNING: CPU: 3 PID: 1054 at drivers/usb/core/hcd.c:1584 usb_hcd_map_urb_for_dma+0x413/0x570 [usbcore]
[   44.292010] Modules linked in: pn533_usb(+) pn533 nfc ccm rfcomm bnep snd_hda_codec_hdmi joydev btusb btrtl mousedev btbcm btintel bluetooth intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel hid_generic snd_hda_codec_realtek ecdh_generic snd_hda_codec_generic kvm usbhid hid snd_soc_skl snd_soc_skl_ipc irqbypass crct10dif_pclmul snd_hda_ext_core crc32_pclmul snd_soc_sst_dsp ghash_clmulni_intel pcbc snd_soc_sst_ipc snd_soc_acpi uvcvideo snd_soc_core videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev rtsx_usb_ms aesni_intel memstick aes_x86_64 media crypto_simd glue_helper cryptd snd_compress ac97_bus snd_pcm_dmaengine intel_cstate arc4 iTCO_wdt iTCO_vendor_support ppdev nls_iso8859_1 nls_cp437 vfat fat iwlmvm mac80211 i915 intel_uncore snd_hda_intel iwlwifi
[   44.292050]  intel_rapl_perf input_leds snd_hda_codec psmouse intel_wmi_thunderbolt pcspkr e1000e snd_hda_core tpm_crb snd_hwdep cfg80211 snd_pcm ptp wmi_bmof pps_core snd_timer snd soundcore i2c_i801 toshiba_acpi shpchp sparse_keymap mei_me parport_pc tpm_tis tpm_tis_core tpm mei intel_gtt industrialio toshiba_bluetooth intel_pch_thermal rfkill battery parport rtc_cmos rng_core ac evdev mac_hid vboxnetflt(O) vboxnetadp(O) vboxpci(O) vboxdrv(O) sg crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 fscrypto rtsx_usb_sdmmc mmc_core rtsx_usb sr_mod sd_mod cdrom ahci libahci serio_raw atkbd libps2 xhci_pci libata xhci_hcd crc32c_intel usbcore scsi_mod usb_common i8042 serio nouveau led_class mxm_wmi wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm
[   44.292100]  agpgart
[   44.292104] CPU: 3 PID: 1054 Comm: systemd-udevd Tainted: G           O     4.16.8-1-ARCH #1
[   44.292105] Hardware name: TOSHIBA SATELLITE PRO A50-C/SATELLITE PRO A50-C, BIOS Version 7.50   09/26/2016
[   44.292114] RIP: 0010:usb_hcd_map_urb_for_dma+0x413/0x570 [usbcore]
[   44.292116] RSP: 0018:ffffb316c29179f8 EFLAGS: 00010282
[   44.292118] RAX: 0000000000000000 RBX: ffff992de363f3c0 RCX: 0000000000000001
[   44.292119] RDX: 0000000080000001 RSI: ffffffff91e7072c RDI: 00000000ffffffff
[   44.292121] RBP: ffff992e1435a000 R08: 0000000000000030 R09: 000000000000038f
[   44.292122] R10: 0000000000000000 R11: 0000000000000001 R12: 00000000014000c0
[   44.292124] R13: 00000000fffffff5 R14: ffff992dac8d6298 R15: 00000000c0410980
[   44.292126] FS:  00007f0fd1d73d40(0000) GS:ffff992e26d80000(0000) knlGS:0000000000000000
[   44.292127] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   44.292129] CR2: 0000555e633ac000 CR3: 00000003faf56001 CR4: 00000000003606e0
[   44.292130] Call Trace:
[   44.292141]  usb_hcd_submit_urb+0x38d/0xb20 [usbcore]
[   44.292146]  ? idr_alloc_u32+0xbc/0xe0
[   44.292150]  ? preempt_count_add+0x68/0xa0
[   44.292153]  ? __kmalloc+0x19e/0x220
[   44.292158]  pn533_usb_probe+0x397/0x4d0 [pn533_usb]
[   44.292168]  usb_probe_interface+0xe4/0x2f0 [usbcore]
[   44.292174]  driver_probe_device+0x2b9/0x460
[   44.292177]  ? __driver_attach+0xb6/0xe0
[   44.292180]  ? driver_probe_device+0x460/0x460
[   44.292182]  ? bus_for_each_dev+0x76/0xc0
[   44.292185]  ? bus_add_driver+0x152/0x230
[   44.292188]  ? driver_register+0x6b/0xb0
[   44.292198]  ? usb_register_driver+0x7a/0x130 [usbcore]
[   44.292201]  ? 0xffffffffc0ea9000
[   44.292204]  ? do_one_initcall+0x48/0x13b
[   44.292207]  ? free_unref_page_commit+0x6a/0x100
[   44.292209]  ? kmem_cache_alloc_trace+0xdc/0x1c0
[   44.292212]  ? do_init_module+0x5a/0x210
[   44.292214]  ? load_module+0x247a/0x29f0
[   44.292218]  ? SyS_init_module+0x139/0x180
[   44.292219]  ? SyS_init_module+0x139/0x180
[   44.292222]  ? do_syscall_64+0x74/0x190
[   44.292225]  ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[   44.292227] Code: 49 39 c9 73 30 80 3d 7d b5 02 00 00 41 bd f5 ff ff ff 0f 85 57 ff ff ff 48 c7 c7 88 5d 54 c0 c6 05 63 b5 02 00 01 e8 97 c5 b4 d0 <0f> 0b 8b 53 64 e9 3a ff ff ff 65 48 8b 0c 25 00 5c 01 00 48 8b 
[   44.292257] ---[ end trace 3d47789f60474aad ]---
[   44.292260] usb 1-1: NFC: Reader power on cmd error -11
[   44.292263] pn533_usb 1-1:1.0: NFC: Couldn't poweron the reader (error -11)
[   44.292269] pn533_usb: probe of 1-1:1.0 failed with error -11
[   44.292283] usbcore: registered new interface driver pn533_usb

I've searched the net and found some people referring to kernel issues on a Fedora forum: https://bugzilla.redhat.com/show_bug.cgi?id=1436866
It seems the problem was solver after a kernel update but in the meantime someone else got the same error on 4.13.5.
There is also a link to a patch but I'm not going to try any patch without knowing if they can produce any problems with Arch.

My installation is up-to-date, thus running kernel version 4.16.8-1-ARCH.

Any suggestions on how can I get this working?

Kind regards,
Carlos Santos

loqs · 2018-05-15 16:44:06

The patch linked in the bug report is already applied to 4.16.8 https://git.kernel.org/pub/scm/linux/ke … 6dda807d5e
The backtrace for the issue it is fixing does not match the one you posted.
Edit:
Please post the full dmesg. Has the device worked with previous kernels?

Last edited by loqs (2018-05-15 17:42:50)

cmmps · 2018-05-16 12:02:32

Hi
It's the first time I'm using this device.
The full dmesg is huge, so I used pastebin:
https://pastebin.com/ck4sZuUY

Thanks in advance,
Carlos

loqs · 2018-05-16 14:30:17

https://www.kernel.org/doc/html/latest/ … -bugs.html
I recommend you report this to the linux-usb@vger.kernel.org mailing list after removing the virtual box modules to produce an untainted dmesg.

[    3.220874] vboxdrv: loading out-of-tree module taints kernel.

cmmps · 2018-05-16 14:37:30

Thank you loqs. I'm going to do that.

Arch Linux

#1 2018-05-15 15:56:14

ACS ACR122U not working: pn533_usb 1-1:1.0: NFC: Couldn't poweron...

#2 2018-05-15 16:44:06

Re: ACS ACR122U not working: pn533_usb 1-1:1.0: NFC: Couldn't poweron...

#3 2018-05-16 12:02:32

Re: ACS ACR122U not working: pn533_usb 1-1:1.0: NFC: Couldn't poweron...

#4 2018-05-16 14:30:17

Re: ACS ACR122U not working: pn533_usb 1-1:1.0: NFC: Couldn't poweron...

#5 2018-05-16 14:37:30

Re: ACS ACR122U not working: pn533_usb 1-1:1.0: NFC: Couldn't poweron...

Board footer