Bug 92341 - ipp process at 100% processor
ipp process at 100% processor
Status: CLOSED DUPLICATE of bug 97958
Product: Red Hat Linux
Classification: Retired
Component: cups (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2003-06-05 06:36 EDT by Paul D. Mitcheson
Modified: 2007-04-18 12:54 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:53:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul D. Mitcheson 2003-06-05 06:36:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823

Description of problem:
Every so often, and IPP process is running on my print server, taking up 100%
processor time.

The process seems to have no function and I can just kill it, but it slows down

Unfortunatelty I have no more information.  It jseems to occur once every few days.

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

How reproducible:
Couldn't Reproduce

Steps to Reproduce:
don't know how to reproduce other than just let people print for a couple of days.

Additional info:

this is an entry in the cups error log for a recent process which causd this error:

I [04/Jun/2003:18:53:17 +0100] Started backend /usr/lib/cups/backend/ipp (PID
4831) for job 933.

when I killed it I got this:

E [05/Jun/2003:11:26:05 +0100] PID 4831 crashed on signal 9!
Comment 1 Tim Waugh 2003-06-06 06:42:02 EDT
Next time you see it happening, please try finding out what it's up to using strace:

strace -p {pid}

Comment 2 Tim Waugh 2003-06-28 06:49:15 EDT

*** This bug has been marked as a duplicate of 97958 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:53:27 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.