Bug 127752
Summary: | Thinkpad X24 laptop HD grinds until unresponsive | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alex Deucher <agd5f> |
Component: | rpm | Assignee: | Dave Jones <davej> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | barryn, mattdm, pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-04 13:27:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alex Deucher
2004-07-13 13:31:48 UTC
Keep a terminal window open and running "top". Then when it starts grinding, keep the window in view. By the time it's unresponsive, note down what the top several processes are. (I have several specific ideas about what might be causing this, but knowing the output of "top" would seriously help me narrow this down.) Also, you may want to try booting with "elevator=as" and see if that helps responsiveness. (It could also make the situation worse not better, but it's worth trying.) Last time this happened I sshed in and ran top, as I recall the big 3 were rpmq (?), X, and top. I can check again tonight to be sure. I'll also try the elevator=as option. it's definitely rpmq: top - 00:05:18 up 1:13, 2 users, load average: 11.40, 6.52, 2.85 Tasks: 80 total, 2 running, 78 sleeping, 0 stopped, 0 zombie Cpu(s): 0.3% us, 3.3% sy, 0.7% ni, 0.0% id, 95.3% wa, 0.3% hi, 0.0% si Mem: 256600k total, 253988k used, 2612k free, 160k buffers Swap: 718192k total, 299812k used, 418380k free, 7976k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3724 root 34 19 445m 192m 7168 D 3.3 77.0 0:20.27 rpmq 9 root 15 0 0 0 0 D 1.0 0.0 0:01.18 kswapd0 2913 alex 17 0 20252 2424 17m S 0.3 0.9 0:05.72 battstat-applet 1 root 16 0 2800 68 1316 S 0.0 0.0 0:05.10 init 2 root 34 19 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0 3 root 5 -10 0 0 0 S 0.0 0.0 0:00.09 events/0 4 root 5 -10 0 0 0 S 0.0 0.0 0:00.00 kblockd/0 6 root 5 -10 0 0 0 S 0.0 0.0 0:00.01 khelper 5 root 15 0 0 0 0 S 0.0 0.0 0:00.00 khubd 10 root 11 -10 0 0 0 S 0.0 0.0 0:00.00 aio/0 114 root 19 0 0 0 0 S 0.0 0.0 0:00.00 kseriod 153 root 15 0 0 0 0 S 0.0 0.0 0:00.09 kjournald 1115 root 15 0 0 0 0 S 0.0 0.0 0:00.03 kjournald 1377 root 15 0 2688 168 1232 S 0.0 0.1 0:00.00 cpuspeed 1576 root 16 0 2920 4 1236 S 0.0 0.0 0:00.00 netplugd 1586 root 15 0 2064 72 1296 S 0.0 0.0 0:00.02 syslogd 1590 root 16 0 1872 4 1244 S 0.0 0.0 0:00.00 klogd it stay consistently at the top and occasionally spikes to 20-30% CPU. 3724 root 34 19 497m 193m 7168 D 2.3 77.3 0:26.14 rpmq 9 root 15 0 0 0 0 D 0.7 0.0 0:01.68 kswapd0 3745 alex 16 0 8800 284 6836 R 0.3 0.1 0:00.13 sshd 3777 alex 16 0 2756 820 1620 R 0.3 0.3 0:00.67 top 3724 root 35 19 477m 122m 7168 R 53.2 48.8 0:27.75 rpmq 3777 alex 16 0 2756 820 1620 R 0.3 0.3 0:00.68 top 1 root 16 0 2800 68 1316 S 0.0 0.0 0:05.10 init 2 root 34 19 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0 3724 root 35 19 477m 193m 7168 D 3.0 77.1 0:28.34 rpmq 2913 alex 16 0 20252 2484 17m S 0.7 1.0 0:05.93 battstat-applet 3777 alex 16 0 2756 820 1620 R 0.7 0.3 0:00.74 top 3 root 5 -10 0 0 0 S 0.3 0.0 0:00.10 events/0 etc. I haven't gotten a chance to try the elevator=as option. What is rpmq? "kill -9"ing the rpmq process (plain kill doesn't work) returns the computer to a useable state. What is rpmq and why does it go nuts on my computer? (Sorry I didn't respond earlier, I've been busy) rpmq is what performs rpm queries (e.g. when you run "rpm -q name-of-package" or "rpm -qa" or whatever) There's a cron script at /etc/cron.daily/rpm that, once a day, lists all of the packages installed on your computer, sorts the list, and writes it to a log file. (BTW, after you kill -9 it, it would be a good idea to reboot in case the RPM locks are left in a bad state. If you don't, rpm or anything that updates/installs/removes/queries packages could freeze up later.) You could try "chmod a-x /etc/cron.daily/rpm" to disable the script. I'm not sure that's really a fix per se, but at least your computer will be usable for now. re-assigning to rpm component. Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. Closing per previous comment. |