+++ This bug was initially created as a clone of Bug #3480 +++ Description of problem: When launching rpmdrake from drakconf in the usual GUI way the system slows to a crawl immediately after the "Please Wait - Finding installed Packages" dialogue. Top shows X taking around 90% CPU and the cursor whirling graphic visibly slows. The GUI eventually fills with package info after about 10 mins. Closing rpmdrake restores normal service. Starting rpmdrake directly from a root terminal works correctly. Version-Release number of selected component (if applicable): How reproducible: Always - also just tested in a *clean* installation of mga2 Alpha1 fully updated and the same issue is there. I first noticed this on Nov 23 at 13:28:31 and commented on #dev :- <barjac> rpmdrake broken today - anyone else? etc.. but no one responded. This was just after updates that day which included some drakxtools updates:- [baz@jackodesktop ~]$ rpm -qa --last | grep drak harddrake-13.70.1-1.mga2 Wed 23 Nov 2011 10:09:00 GMT harddrake-ui-13.70.1-1.mga2 Wed 23 Nov 2011 10:08:57 GMT drakxtools-13.70.1-1.mga2 Wed 23 Nov 2011 10:08:54 GMT drakxtools-curses-13.70.1-1.mga2 Wed 23 Nov 2011 10:08:51 GMT drakxtools-backend-13.70.1-1.mga2 Wed 23 Nov 2011 10:08:47 GMT ****************************************************************************** Cloned this bug, because the Barry still has the same issue, but his bug was closed as a duplicate of a solved one, so the problem should have disappeared. ******************************************************************************** from https://bugs.mageia.org/show_bug.cgi?id=2775#c18: I have just tested this in a clean LXDE installation of i586 Cauldron Beta, fully updated. After opening rpmdrake via mcc using all GUI from the task bar icon the problem is still there. I booted this installation over 30 mins ago, and went almost immediately into rpmdrake to test. It's still sat there with the cpu at 95% and no package menu displayed. Here's the state of play :- [baz@jackodesktop ~]$ rpm -q rpmdrake rpmdrake-5.30-1.mga2 [baz@jackodesktop ~]$ top top - 18:37:11 up 4 min, 1 user, load average: 1.01, 0.85, 0.40 Tasks: 101 total, 2 running, 98 sleeping, 0 stopped, 1 zombie Cpu(s): 95.7%us, 3.3%sy, 0.0%ni, 1.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 1030124k total, 409268k used, 620856k free, 19292k buffers Swap: 4095468k total, 0k used, 4095468k free, 168732k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1368 root 20 0 69124 14m 8904 R 93.6 1.4 2:37.94 X 1941 root 20 0 99.3m 78m 16m S 2.0 7.8 0:10.76 rpmdrake 1982 baz 20 0 211m 12m 9.9m S 1.3 1.2 0:00.37 lxterminal 28 root 20 0 0 0 0 S 0.3 0.0 0:00.30 kworker/0:2 283 root 20 0 0 0 0 S 0.3 0.0 0:00.25 kworker/0:3 852 root 20 0 5864 1248 1052 S 0.3 0.1 0:00.05 hald-addon-inpu 1854 baz 20 0 51224 32m 11m S 0.3 3.2 0:01.73 net_applet 1 root 20 0 5372 3372 1868 S 0.0 0.3 0:00.72 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:00.07 ksoftirqd/0 4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0 5 root 20 0 0 0 0 S 0.0 0.0 0:00.21 kworker/u:0 6 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0 7 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 cpuset 8 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper 9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs 10 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns *************************************************************************** https://bugs.mageia.org/show_bug.cgi?id=2775#c19 Created attachment 1740 [details] sample of strace of X during hang A few seconds of strace output of X pid *************************************************************************** https://bugs.mageia.org/show_bug.cgi?id=2775#c20 Created attachment 1741 [details] A sample of strace of rpmdrake during hang A few seconds of strace out put of rpmdrake pid **************************************************************************** https://bugs.mageia.org/show_bug.cgi?id=2775#c21 I just discovered that collapsing and re-opening the mcc window by clicking it's taskbar item twice clears the hang and the rpmdrake left panel immediately fills. Thierry - if there is anything else that I can supply in relation to this please ask as this really needs fixing before mga2 release. This i586 test system seems to exhibit the problem about 50% of the time and while it's hung I can still run Firefox, top, strace etc. ****************************************************************************** https://bugs.mageia.org/show_bug.cgi?id=2775#c22 I have just clean installed Beta 2 x86_64 full KDE and the issue is still there. Rpmdrake is useless like this. Increasing to high priority - but really it should be release blocker.
Assignee: bugsquad => thierry.vignaudSource RPM: Suspect drakxtools rev. 171084 => rpmdrake
Severity: normal => major
Created attachment 1791 [details] output of lshw Thanks Marja I really can't understand why this is only apparently affecting me. Admittedly this is fairly old hardware, but certainly adequate and I would imagine quite common, but maybe not among developers/testers. I suspect that if not fixed it could cause issues when mga2 is launched. To summarise:- AMD single core 2.2GHz Athlon with 1GB ram. Nvidia FX5600u graphics card using nouveau (as upstream driver no longer supports our X-server version). 2 x 1TB WD (green) HDs using SilImage PCI controller card (sata-sil) as onboard nvidia SATA controllers don't perform well with sata-nv. SB Audigy2 sound card. Attached full lshw output.
(In reply to comment #1) > Created attachment 1791 [details] > output of lshw > > Thanks Marja > I really can't understand why this is only apparently affecting me. > Admittedly this is fairly old hardware, but certainly adequate and I would > imagine quite common, but maybe not among developers/testers. Maybe a lot of testers prefer to update from the console with, e.g., urpmi --auto-update ? And maybe we have less testers than we think.... I know of some people that they stopped using cauldron altogether, and, tbh, I do still have "cauldrons", but I don't really use them atm. I'll try to use one on a daily basis again. I just tried updating from MCC in cauldron on an old ThinkPad R50e, and for me it worked fine. Do you always use the same mirror? (Not that I have any indication that a mirror is to blame, just curious because I've had a lot of issues with a mirror close to me, including an issue that nearly froze my konsole twice) > I suspect that if not fixed it could cause issues when mga2 is launched. > > To summarise:- > AMD single core 2.2GHz Athlon with 1GB ram. > Nvidia FX5600u graphics card using nouveau (as upstream driver no longer > supports our X-server version). > 2 x 1TB WD (green) HDs using SilImage PCI controller card (sata-sil) as onboard > nvidia SATA controllers don't perform well with sata-nv. > SB Audigy2 sound card. > > Attached full lshw output.
(In reply to comment #2) > (In reply to comment #1) > Maybe a lot of testers prefer to update from the console with, e.g., urpmi > --auto-update ? > Well yes - I currently have no other option :/ > And maybe we have less testers than we think.... I know of some people that > they stopped using cauldron altogether, and, tbh, I do still have "cauldrons", > but I don't really use them atm. I'll try to use one on a daily basis again. > Yes I try to use it all the time - but it can be be real pain when things are breaking and stopping the job in hand. > I just tried updating from MCC in cauldron on an old ThinkPad R50e, and for me > it worked fine. > > Do you always use the same mirror? (Not that I have any indication that a > mirror is to blame, just curious because I've had a lot of issues with a mirror > close to me, including an issue that nearly froze my konsole twice) I have my own mirror on the same machine, but I can switch instantly to a remote one. It's just the same whichever I use. In fact I just switched to $MIRRORLIST and tried to use rpmdrake and it's been sat there for at least 10 mins with X at 93% and no package menu. After closing rpmdrake with the X button and starting it again (from mcc as before) it just opened perfectly without delay. So frustrating !
Been doing some more tests. After the "Please wait finding available packages" dialog box closes then normally a "Please wait listing packages" message appears in the lower left status area. The hang occurs before this status message is written to the screen, and if it does not appear almost immediately after the "Please wait..." dialog box, then it never does. I just ran it 3 times - the first two hung and the third opened correctly. These tests were in rapid succession and nothing changed as regards running programs between them.
Frustrating indeed! :/ Does it make any difference which DE you use?
My wag would be a problem with the nouveau driver. Try switching to the vesa driver, and see if that fixes this problem.
CC: (none) => davidwhodgins
(In reply to comment #5) > Frustrating indeed! :/ > > Does it make any difference which DE you use? Yes - now you mention it, I can't reproduce it with ICEWM using nouveau, however:- (In reply to comment #6) > My wag would be a problem with the nouveau driver. Try > switching to the vesa driver, and see if that fixes this > problem. Switching to nv in KDE I can no longer reproduce. I will continue testing after reverting to nouveau again tomorrow to be sure that I can still reproduce it ;) It was around November when the X11-server package was updated and I was forced to use nouveau so it could be related.
This bug report is unreadable with lot of unrelated stuff. We shouldn't have cloned bug #3480 but reopen bug #2775 instead...
Summary: X uses 90% cpu when rpmdrake is run from drakconf => X uses 90% cpu when rpmdrake is run from drakconf with nouveau
> This bug report is unreadable with lot of unrelated stuff. I'm not surprised :( > We shouldn't have cloned bug #3480 but reopen bug #2775 instead... I give up... https://bugs.mageia.org/show_bug.cgi?id=2775#c25 https://bugs.mageia.org/show_bug.cgi?id=2775#c28(In reply to comment #8)
Sorry, I though you'd opened a bug before. OK then it should have been a new bug created from scratch, maybe copying your comments on other bugs.
Didn't you know my real name was "Catch-22" :-) ?
;) Let's stay here shall we? OK this does seem to be nouveau related. I have re-tested using ICEWM with nouveau and this time I did manage to reproduce the problem. So to summarise, Using nouveau I can always reproduce it (about 50% of the time) With nv I can't reproduce it.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
(In reply to comment #13) > Hi, > > This bug was filed against cauldron, but we do not have cauldron at the moment. > > Please report whether this bug is still valid for Mageia 2. > > Thanks :) > > Cheers, > marja The mother board died on the machine in question, so problem solved ;) Since no one else seems to have suffered from this and no further testing is possible I am closing as old.
Status: NEW => RESOLVEDResolution: (none) => OLD