[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#429394: marked as done (linux-image-2.6.18-4-686-bigmem: STIME of ps output for a process is not constant)

Your message dated Wed, 16 Sep 2009 19:36:27 +0200
with message-id <20090916173627.GA27426@inutil.org>
and subject line Re: linux-image-2.6.18-4-686-bigmem: STIME of ps output for a process is not constant
has caused the Debian Bug report #429394,
regarding linux-image-2.6.18-4-686-bigmem: STIME of ps output for a process is not constant
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
429394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429394
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-4-686-bigmem
Version: 2.6.18.dfsg.1-12etch2
Severity: normal


STIME of a process jumps back and forward:

Look at this output:

# ps -afe |grep spamd
root     28063     1  0 21:55 ?        00:00:00 /usr/sbin/spamd
--max-children 30 --username=spamd -i -A 195.251.123.232 -x -d
--pidfile=/var/run/spamd.pid
spamd    28080 28063  0 21:55 ?        00:00:00 spamd child
spamd    28081 28063  0 21:55 ?        00:00:00 spamd child
root     28206 27204  0 21:56 pts/1    00:00:00 grep spamd

# ps -afe |grep spamd
root     28063     1  0 21:55 ?        00:00:00 /usr/sbin/spamd
--max-children 30 --username=spamd -i -A 195.251.123.232 -x -d
--pidfile=/var/run/spamd.pid
spamd    28080 28063  0 21:56 ?        00:00:00 spamd child
spamd    28081 28063  0 21:56 ?        00:00:00 spamd child
root     28215 27204  0 21:56 pts/1    00:00:00 grep spamd

# ps -afe |grep spamd
root     28063     1  0 21:55 ?        00:00:00 /usr/sbin/spamd
--max-children 30 --username=spamd -i -A 195.251.123.232 -x -d
--pidfile=/var/run/spamd.pid
spamd    28080 28063  0 21:55 ?        00:00:00 spamd child
spamd    28081 28063  0 21:55 ?        00:00:00 spamd child
root     28224 27204  0 21:56 pts/1    00:00:00 grep spamd

hydra# ps -afe |grep spamd
root     28063     1  0 21:55 ?        00:00:00 /usr/sbin/spamd
--max-children 30 --username=spamd -i -A 195.251.123.232 -x -d
--pidfile=/var/run/spamd.pid
spamd    28080 28063  0 21:56 ?        00:00:00 spamd child
spamd    28081 28063  0 21:56 ?        00:00:00 spamd child
root     28445 27204  0 21:59 pts/1    00:00:00 grep spamd

hydra# ps -afe |grep spamd
root     28063     1  0 21:55 ?        00:00:00 /usr/sbin/spamd
--max-children 30 --username=spamd -i -A 195.251.123.232 -x -d
--pidfile=/var/run/spamd.pid
spamd    28080 28063  0 21:56 ?        00:00:00 spamd child
spamd    28081 28063  0 21:56 ?        00:00:00 spamd child
root     28447 27204  0 21:59 pts/1    00:00:00 grep spamd

hydra# ps -afe |grep spamd
root     28063     1  0 21:55 ?        00:00:00 /usr/sbin/spamd
--max-children 30 --username=spamd -i -A 195.251.123.232 -x -d
--pidfile=/var/run/spamd.pid
spamd    28080 28063  0 21:55 ?        00:00:00 spamd child
spamd    28081 28063  0 21:55 ?        00:00:00 spamd child
root     28449 27204  0 21:59 pts/1    00:00:00 grep spamd

As you can see from the 'grep' pid, all of them are one after another. Watch
the STIME of spamd processes. Some times it says 21:55 and others 21:56. 

Other processes don't do this.

Hardware is:
IBM X-Series
2 Xeon 3.6GHz with hyperthreading enabled
4GB of memory

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686-bigmem
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)

Versions of packages linux-image-2.6.18-4-686-bigmem depends on:
ii  coreutils                     5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0]         1.5.11     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85g      tools for generating an initramfs
ii  module-init-tools             3.3-pre4-2 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-4-686-bigmem recommends:
ii  libc6-i686                  2.3.6.ds1-13 GNU C Library: Shared libraries [i

-- debconf-show failed

--- End Message ---
--- Begin Message --- 
On Wed, Sep 16, 2009 at 01:51:54PM +0300, Stefanos Harhalakis wrote:
> Hello and sorry for the long-delay. Kmail removed the 'to-do' flag of this 
> mail after a crash and i forgotten it.
> 
> On Friday 14 August 2009, Moritz Muehlenhoff wrote:
> > On Tue, Dec 16, 2008 at 02:04:45AM +0200, Stefanos Harhalakis wrote:
> > > On Monday 15 December 2008, Moritz Muehlenhoff wrote:
> > > > Does this error still occur with more recent kernel versions?
> > > >
> > > > If you're running Etch, could you try to reproduce this bug
> > > > with the 2.6.24 based kernel added in 4.0r4?
> > > > http://packages.qa.debian.org/l/linux-2.6.24.html
> > >
> > > I'm sorry but I don't know of a way to reproduce this on-demand, even on
> > > the same machine with the same kernel. I know that this is an ugly bug
> > > report but I can only report further similar problems or perhaps try to
> > > automate this in a way.
> > >
> > > To make this harder, ps shows the date instead of the time a process
> > > started when there are more than 24h passed and thus I cannot test it
> > > with other processes. This is a server machine that I cannot reboot for
> > > testing.
> > 
> > Has this error re-occured in the mean time?
> 
> I cannot reproduce it (I never could) and I haven't noticed it again. Since 
> AFAIK there are a lot of changes in kernel timming code since 2.6.18, I 
> suggest you close this bug and I'll re-report it if I see it again.

Thanks, for the feedback. Closing the bug, then.

Cheers,
       Moritz

--- End Message ---
Reply to: