Bug 21776

Summary:	NFC: Reader power on cmd error -11
Product:	Mageia	Reporter:	Thomas Bigot <thomas.bigot>
Component:	RPM Packages	Assignee:	Kernel and Drivers maintainers <kernel>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, pterjan
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	https://bugzilla.redhat.com/show_bug.cgi?id=1436866
Whiteboard:
Source RPM:	kernel-4.12.14-1.mga7.src.rpm	CVE:
Status comment:

Description Thomas Bigot 2017-09-28 11:20:28 CEST

Description of problem:
Using usb NFC Reader
Product: ACR122U PICC Interface
Manufacturer: ACS

I get these messages:
kernel: usb 1-1: new full-speed USB device number 15 using xhci_hcd
kernel: usb 1-1: New USB device found, idVendor=072f, idProduct=2200
kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 1-1: Product: ACR122U PICC Interface
kernel: usb 1-1: Manufacturer: ACS
kernel: usb 1-1: NFC: Reader power on cmd error -11
kernel: pn533_usb 1-1:1.0: NFC: Couldn't poweron the reader (error -11)
kernel: pn533_usb: probe of 1-1:1.0 failed with error -11


Version-Release number of selected component (if applicable):
4.12.14-1.mga7


How reproducible:
always


Steps to Reproduce:
1. plug usb reader
2. read the messages above in journal


NB: patches are available on redhat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1436866

Marja Van Waes 2017-09-28 23:51:42 CEST

Assignee: bugsquad => kernel
CC: (none) => marja11

Comment 1 Thomas Bigot 2017-10-03 13:43:14 CEST

Having a look to the Mageia kernel source, it seems that the patch is already applied to 4.12.14-1.mga7.

Comment 2 Pascal Terjan 2017-10-03 13:51:24 CEST

The patch was applied upstream in 4.12-rc1 so yes it's already included

CC: (none) => pterjan

Comment 3 Thomas Bigot 2017-10-03 14:20:25 CEST

It is not clear to me which patch did the trick and solved the problem at Fedora side.

Comment 4 Pascal Terjan 2017-10-03 14:24:39 CEST

The patch was for the bug when sending acks, there may be another problem which causes the failure in your case

Comment 5 Pascal Terjan 2017-10-03 14:52:12 CEST

Also, I have a ACR122U reader somewhere at home but I am not sure if I can find it soon.

Comment 6 Thomas Bigot 2018-07-17 16:36:59 CEST

Solved with recent kernel (I don’t know exactly which one).

Status: NEW => RESOLVED
Resolution: (none) => FIXED