Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

opensc-notify.exe(from OpenSC 0.20.0-rc2) - Win10( ver1809) - too high processor load #1874

Closed
mti-sk opened this issue Nov 27, 2019 · 3 comments · Fixed by #1923
Closed

opensc-notify.exe(from OpenSC 0.20.0-rc2) - Win10( ver1809) - too high processor load #1874

mti-sk opened this issue Nov 27, 2019 · 3 comments · Fixed by #1923

Comments

@mti-sk
Copy link

mti-sk commented Nov 27, 2019

Problem Description

Too high processor load on win10 enterprise (ver 1809, build 17763.805 ) by opensc-notify.exe without activity. Still, continuous 30%.
My CPU: Intel Core i5 - 5300U 2,3GHz

Proposed Resolution

I don't know if the opensc-notify process can be disabled in the opensc.conf configuration. That would be temporary help.

Steps to reproduce

Only install OpenSC-0.20.0-rc2 version.

Logs

obrazek
@frankmorgner
Copy link
Member

Could you send a debug output log OpenSC? Most likely, there is some unhandled error:

OpenSC/src/tools/opensc-notify.c

Lines 82 to 90 in ce71b17

if (r < 0) {
if (r == SC_ERROR_NO_READERS_FOUND) {
/* No readers available, PnP notification not supported */
Sleep(200);
} else {
error_count++;
}
continue;
}

Please check if the problem persists after attaching a reader (empty or with card).

@mti-sk
Copy link
Author

mti-sk commented Jan 2, 2020

Solved in OpenSC-0.20.0 release

@mti-sk mti-sk closed this as completed Jan 2, 2020
@frankmorgner
Copy link
Member

The issue still persists, see #1903 for a more detailed analysis

frankmorgner added a commit to frankmorgner/OpenSC that referenced this issue Jan 13, 2020
@frankmorgner
opensc-notify: handle reader insertion/removal events
f0c7597 
- If readers are attatched, the new reader is probed for a card to check
if a notification needs to be sent
- removal of readers are not notified to the user, we assume that PC/SC
sends the correct card removal event
- The list of readers to be monitored is adjusted once a reader (dis)appears
- On macOS, without PnP notification, we always check for new/removed
readers with SCardListReaders

fixes OpenSC#1874
@frankmorgner frankmorgner mentioned this issue Jan 30, 2020
Merged
3 tasks
frankmorgner added a commit to frankmorgner/OpenSC that referenced this issue Mar 21, 2020
@frankmorgner
opensc-notify: handle reader insertion/removal events
673d5d2 
- If readers are attatched, the new reader is probed for a card to check
if a notification needs to be sent
- removal of readers are not notified to the user, we assume that PC/SC
sends the correct card removal event
- The list of readers to be monitored is adjusted once a reader (dis)appears
- On macOS, without PnP notification, we always check for new/removed
readers with SCardListReaders

fixes OpenSC#1874
frankmorgner added a commit to frankmorgner/OpenSC that referenced this issue Mar 21, 2020
@frankmorgner
opensc-notify: handle reader insertion/removal events
ed84e61 
- If readers are attatched, the new reader is probed for a card to check
if a notification needs to be sent
- removal of readers are not notified to the user, we assume that PC/SC
sends the correct card removal event
- The list of readers to be monitored is adjusted once a reader (dis)appears
- On macOS, without PnP notification, we always check for new/removed
readers with SCardListReaders

fixes OpenSC#1874
frankmorgner added a commit to frankmorgner/OpenSC that referenced this issue Mar 27, 2020
@frankmorgner
opensc-notify: handle reader insertion/removal events
584067a 
- If readers are attatched, the new reader is probed for a card to check
if a notification needs to be sent
- removal of readers are not notified to the user, we assume that PC/SC
sends the correct card removal event
- The list of readers to be monitored is adjusted once a reader (dis)appears
- On macOS, without PnP notification, we always check for new/removed
readers with SCardListReaders
- fixes interrupt handling in opensc-notify on Unix

fixes OpenSC#1874
frankmorgner added a commit to frankmorgner/OpenSC that referenced this issue Mar 27, 2020
@frankmorgner
opensc-notify: handle reader insertion/removal events
0803735 
- If readers are attatched, the new reader is probed for a card to check
if a notification needs to be sent
- removal of readers are not notified to the user, we assume that PC/SC
sends the correct card removal event
- The list of readers to be monitored is adjusted once a reader (dis)appears
- On macOS, without PnP notification, we always check for new/removed
readers with SCardListReaders
- fixes interrupt handling in opensc-notify on Unix

fixes OpenSC#1874
frankmorgner added a commit to frankmorgner/OpenSC that referenced this issue Mar 27, 2020
@frankmorgner
opensc-notify: handle reader insertion/removal events
d6c75e3 
- If readers are attatched, the new reader is probed for a card to check
if a notification needs to be sent
- removal of readers are not notified to the user, we assume that PC/SC
sends the correct card removal event
- The list of readers to be monitored is adjusted once a reader (dis)appears
- On macOS, without PnP notification, we always check for new/removed
readers with SCardListReaders
- fixes interrupt handling in opensc-notify on Unix

fixes OpenSC#1874
frankmorgner added a commit to frankmorgner/OpenSC that referenced this issue Mar 28, 2020
@frankmorgner
opensc-notify: handle reader insertion/removal events
2901a2d 
- If readers are attatched, the new reader is probed for a card to check
if a notification needs to be sent
- removal of readers are not notified to the user, we assume that PC/SC
sends the correct card removal event
- The list of readers to be monitored is adjusted once a reader (dis)appears
- On macOS, without PnP notification, we always check for new/removed
readers with SCardListReaders
- fixes interrupt handling in opensc-notify on Unix

fixes OpenSC#1874
frankmorgner added a commit that referenced this issue Apr 6, 2020
@frankmorgner
opensc-notify: handle reader insertion/removal events
2c26b73 
- If readers are attatched, the new reader is probed for a card to check
if a notification needs to be sent
- removal of readers are not notified to the user, we assume that PC/SC
sends the correct card removal event
- The list of readers to be monitored is adjusted once a reader (dis)appears
- On macOS, without PnP notification, we always check for new/removed
readers with SCardListReaders
- fixes interrupt handling in opensc-notify on Unix

fixes #1874
@jozsefd jozsefd mentioned this issue May 17, 2021
Closed
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

opensc-notify: handle reader insertion/removal events frankmorgner/OpenSC
2 participants
@frankmorgner @mti-sk