| Summary: | X uses 90% cpu when rpmdrake is run from drakconf with nouveau | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marja Van Waes <marja11> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | davidwhodgins, marja11, zen25000 |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpmdrake | CVE: | |
| Status comment: | |||
| Bug Depends on: | 3480 | ||
| Bug Blocks: | |||
| Attachments: | output of lshw | ||
|
Description
Marja Van Waes
2012-03-17 22:07:05 CET
Marja Van Waes
2012-03-17 22:08:52 CET
Assignee:
bugsquad =>
thierry.vignaud
Marja Van Waes
2012-03-17 22:09:29 CET
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 =>
RESOLVED |