Bug 248855 - kernel 2.6.22.1.27.fc7 in updates-testing cpu allway on top
Summary: kernel 2.6.22.1.27.fc7 in updates-testing cpu allway on top
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 7
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-19 09:30 UTC by dominique
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-07-19 18:06:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description dominique 2007-07-19 09:30:00 UTC 
Description of problem:
automount on top with kernel 2.6.22.1.27.fc7

Version-Release number of selected component (if applicable):


How reproducible:
NO I disinstall this kernel

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
I want to test the new kernel 2.6.22.1.27.fc7 in updates-testing and when I boot
my cpu are on the top
If I do top in console I saw automount on top with 40% cpu usage
When I keep console and I do a new top in a console it is top who are in top
with 80% cpu usage...
I don't know if it is a new bug...
Comment 1 dominique 2007-07-19 15:53:07 UTC 
I re-install kernel 2.6.22.1.27.fc7 and now my cpu is 40% usage
with the commande top I see is automount in use for 35%
I do a killall automount and and my fedora is good
But I think it is not natunal that automount is on after boot
With kernel 2.6.21-1 it is not the case...
Comment 2 Chuck Ebbert 2007-07-19 18:06:20 UTC 
autofs-5.0.1-18 has been released to fix this.

[https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=247711]
Note You need to log in before you can comment on or make changes to this bug.