Bug#472180: Bug #472180: Xprt hogging CPU

2008-04-30 Thread Drew Parsons
Here is the top of a gprof analysis.

I'm wondering if the Xkb references indicate that it is the problem.  I
can hypothesise that some changes in the general Xserver code touched
upon Xkb, expecting the DDX to initialise it appropriately.  Since
Xprint does not use Xkb, it doesn't handle it in any explicit way.
Could Xkb be spinning, waiting for the Xprint DDX to tell it to go away
and stop being annoying?  This Xkb hypothesis is corroborated by
https://bugs.freedesktop.org/show_bug.cgi?id=13063


Function/Method Count Total (s)% Self (s) Total
ms/call Self ms/call
Dispatch1   0.150 68.200  0.030
150.000   30.000
WaitForSomething 14445610.060 27.300  0.060
0.0000.000
__i686.get_pc_thunk.bx  0   0.060 27.300  0.060
0.0000.000
FlushIfCriticalOutputPending 14445610.060 27.300  0.060
0.0000.000
XkbRF_LoadRules 1   0.010 4.500   0.000
10.0000.000
XkbInitKeyboardDeviceStruct 1   0.010 4.500   0.000
10.0000.000
XkbDDXNamesFromRules1   0.010 4.500   0.000
10.0000.000
GetInputLine 8330.010 4.500   0.010
0.0100.010
CoreKeyboardProc3   0.010 4.500   0.000
3.3300.000
InitAndStartDevices 1   0.010 2.300   0.000
5.0000.000
EnableDevice4   0.000 1.500   0.000
0.8300.000
CloseDownDevices1   0.000 1.500   0.000
3.3300.000
CloseDevice 4   0.000 1.500   0.000
0.8300.000
ActivateDevice  4   0.000 1.500   0.000
0.8300.000
InitCoreDevices 1   0.000 0.800   0.000
1.6700.000



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#472180: Xprt hogging CPU.

2008-03-26 Thread Gavin Bravery
Not 100% sure that I do...!
Think it's one of those things that ends up auto-installing.

That said, I haven't tried using my printer with it turned off.

So, when I said requests, what I actually meant is servicing the Xprt
process...
No requests are actually being made to Xprt

Gavin

-Original Message-
From: Julien Cristau [mailto:[EMAIL PROTECTED] 
Sent: 22 March 2008 15:34
To: Gavin Bravery; [EMAIL PROTECTED]
Subject: Re: Bug#472180: Xprt hogging CPU.

severity 472180 grave
kthxbye

On Sat, Mar 22, 2008 at 14:33:04 +, Gavin Bravery wrote:

 On starting the xprint service, the CPU climbs to 100% and sits there.
 Most of the time is being spent processing the Xprt requests.
 
I'm curious: why do you use xprint? :)

Cheers,
Julien




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#472180: Xprt hogging CPU.

2008-03-22 Thread Julien Cristau
severity 472180 grave
kthxbye

On Sat, Mar 22, 2008 at 14:33:04 +, Gavin Bravery wrote:

 On starting the xprint service, the CPU climbs to 100% and sits there.
 Most of the time is being spent processing the Xprt requests.
 
I'm curious: why do you use xprint? :)

Cheers,
Julien



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: Re: Bug#472180: Xprt hogging CPU.

2008-03-22 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 472180 grave
Bug#472180: Xprt hogging CPU.
Severity set to `grave' from `serious'

 kthxbye
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#472180: Xprt hogging CPU.

2008-03-22 Thread Gavin Bravery
Package: xprint
Version: 2:1.4.99.901-1
Severity: serious

--- Please enter the report below this line. ---
On starting the xprint service, the CPU climbs to 100% and sits there.
Most of the time is being spent processing the Xprt requests.

An strace on the process shows repeated messages like this:
clock_gettime(CLOCK_MONOTONIC, {129271, 124564461}) = 0
select(256, [0 1], NULL, NULL, {0, 0})  = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {129271, 124730486}) = 0
select(256, [0 1], NULL, NULL, {0, 0})  = 0 (Timeout)

The only way to return the system to useability was to kill the process
off.


--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.24-1-686

Debian Release: lenny/sid
  500 unstableweb-proxy.sdmz.jagsiacs.co.uk 
  500 latest  web-proxy.sdmz.jagsiacs.co.uk 
  400 experimentalweb-proxy.sdmz.jagsiacs.co.uk 
  200 testing web-proxy.sdmz.jagsiacs.co.uk 
  100 stable  web-proxy.sdmz.jagsiacs.co.uk 

--- Package information. ---
Depends  (Version) | Installed
==-+-=
libc6   (= 2.7-1) | 2.7-9
libfreetype6(= 2.3.5) | 2.3.5-1+b1
libx11-6   | 2:1.1.4-1
libxau6| 1:1.0.3-2
libxdmcp6  | 1:1.0.2-2
libxfont1 (= 1:1.2.9) | 1:1.3.2-1
xprint-common  | 2:1.4.99.901-1
zlib1g | 1:1.2.3.3.dfsg-11




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]