Bug 903423 - systemd-udevd and systemd-joutnal: excessive cpu use when trying to connect Smanung GT-S6102 phone via usb
Summary: systemd-udevd and systemd-joutnal: excessive cpu use when trying to connect S...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-24 00:02 UTC by DAKSH
Modified: 2013-01-25 11:30 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-25 11:30:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
The Screenshot of Top and CPU usage (527.71 KB, image/png)
2013-01-24 00:02 UTC, DAKSH 		no flags Details
View All

Description DAKSH 2013-01-24 00:02:46 UTC 
Created attachment 686368 [details]
The Screenshot of Top and CPU usage

Description of problem: I tried to connect my phone (Samsung Y-Duos) Model No:GT-S6102 Android Version:2.3.6 via usb utilities from my phone. When I'm tapping on Connect storage to PC I found my both CPU using all most 100%. And my phone's memory card not mounting in my fedora 18. I never had this problem in Fedora 17 before.


Version-Release number of selected component (if applicable):
systemd 197
+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ

How reproducible:


Steps to Reproduce:
1. Have  No Idea
2.
3.
  
Actual results:
High Cpu usage and 

Expected results:
Mount the phone storage (Memory Card)

Additional info:
I am attaching an screenshot of top as well. If you need any other Details I will post them. But please let me know how to get them because I don't know very much commands
Comment 1 Michal Schmidt 2013-01-24 13:45:13 UTC 
Please attach the output of these two commands run as root:
dmesg
journactl -ab
Comment 2 Michal Schmidt 2013-01-24 13:46:31 UTC 
(In reply to comment #1)
> journactl -ab

Sorry, typo. The correct command is:
journalctl -ab
Comment 3 DAKSH 2013-01-24 20:32:08 UTC 
last night GDM was not working so I did linux rescue 
chroot /mnt/sysimage

Since the problem has resolved. You can close the bug. Thank you for your help.
Note You need to log in before you can comment on or make changes to this bug.