I have not had time to reply earlier, partially due to network problems
here. So here goes...

On Mon, Feb 21, 2005 at 03:02:49PM +0200, Tzafrir Cohen wrote:
> On Mon, Feb 21, 2005 at 02:07:18PM +0200, Nadav Har'El wrote:
> > On Mon, Feb 21, 2005, Tzafrir Cohen wrote about "system clock loops":
> > > The following is from the output of 'date' run from the same shell about
> > > 1 second apart:
> > > 
> > >   12:13:37
> > >   13:25:08
> > >   12:13:34
> > >...
> > > 
> > > Obviously anything that assumes a steady system clock misbehaves.
> > > 
> > > Any idea what else may play with the system clock?
> > > 
> > > Kernel is 2.6.8-2-686 (14), the current Debian-sarge kernel.

actually: 13

> > 
> > I have seen this sort of nonsense when using AFS or Kerberos, which try to
> > keep their own time, based on bad servers, and force their notion of time
> > on the computer.
> 
> Not here. The computer is an NFS server, though.
> 
> After many tinkerrings I rebotted the computer to see if it could make
> the problem go away. It has. For about an hour or so.
> 
> And again, when it goes to the "future" it seems to have the safe offset
> of ~ 71:31 (4291 seconds).

One reboot made the problem go away, but it got back after ~half an
hour. I noticed that uptime's report of the system clock (as well as
the first number in /proc/uptime) is coherent with the system clock as
reported by 'date' . So I think we can rule out glibc mis-reportings.

Then I decided to revert back to an older kernel (2.6.7-1-386, package
revision 2.6.7-2) and the problem has disappeared. The "problematic" 
kernel version was 2.6.8-2-686 (2.6.8-13)

I have only used the newer kernel for ~2 days, so I figure that the
kernel is the suspect here. I'm not sure what triggered it and I really
don't want to play with this system. In both cases one of the last
messages in the logs was the network adapter leaving promocious mode (me
running tcpdump in the course of new network setup).

Danny, Gilad, Nadav, Oron, Tzahi: thanks for the help. I still have no
idea what may cause such a loop.

Hardware details:
boole:~# lspci
0000:00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub 
Interface (rev 02)
0000:00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics 
Device (rev 02)
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 
(rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 
(rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 
(rev 02)
0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 
(rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI 
Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 
Storage Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 
02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) 
AC'97 Audio Controller (rev 02)
0000:03:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet 
Controller (rev 02)


boole:~# lsmod
Module                  Size  Used by
i830                   68516  2 
nfsd                  178432  8 
exportfs                6144  1 nfsd
lockd                  56520  2 nfsd
sunrpc                137060  2 nfsd,lockd
lp                     10436  0 
af_packet              20616  2 
ipv6                  221152  23 
e100                   30080  0 
eepro100               28300  0 
mii                     4864  2 e100,eepro100
snd_intel8x0           33068  0 
snd_ac97_codec         59268  1 snd_intel8x0
snd_pcm_oss            48168  0 
snd_mixer_oss          16640  1 snd_pcm_oss
snd_pcm                85412  2 snd_intel8x0,snd_pcm_oss
snd_timer              23172  1 snd_pcm
snd_page_alloc         11144  2 snd_intel8x0,snd_pcm
gameport                4736  1 snd_intel8x0
snd_mpu401_uart         7296  1 snd_intel8x0
snd_rawmidi            23232  1 snd_mpu401_uart
snd_seq_device          7944  1 snd_rawmidi
snd                    50148  9 
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore               9824  1 snd
pciehp                 84332  0 
shpchp                 87404  0 
pci_hotplug            30640  2 pciehp,shpchp
ehci_hcd               27780  0 
uhci_hcd               29200  0 
usbcore               100704  4 ehci_hcd,uhci_hcd
intel_mch_agp          10000  0 
intel_agp              17948  1 
agpgart                31272  4 intel_mch_agp,intel_agp
parport_pc             31552  1 
parport                37320  2 lp,parport_pc
floppy                 54996  0 
pcspkr                  3816  0 
nls_cp437               6016  1 
isofs                  32440  1 
loop                   14728  2 
evdev                   9088  0 
mousedev                9996  2 
tsdev                   7168  0 
capability              4872  0 
commoncap               7168  1 capability
psmouse                17800  0 
ide_cd                 38916  0 
cdrom                  35360  1 ide_cd
rtc                    12088  0 
reiserfs              205296  3 
ide_disk               16640  5 
ide_generic             1664  0 
piix                   12448  1 
ide_core              127448  4 ide_cd,ide_disk,ide_generic,piix
unix                   25776  250 
font                    8576  0 
vesafb                  6688  0 
cfbcopyarea             3840  1 vesafb
cfbimgblt               3200  1 vesafb
cfbfillrect             3712  1 vesafb


Note the anomality with the network adapter drivers: both e100 and 
eepro100 are loaded and both have a reference count of 0. We noticed the 
thing yesterday, tried to remove both and load just one.

dmesg now shows:

eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.
html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin 
<[EMAIL PROTECTED]
w.sw.com.sg> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:0D:60:68:17:98, IRQ 20.
  Board assembly 000000-000, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0xed626fe2).
e100: Intel(R) PRO/100 Network Driver, 3.0.18
e100: Copyright(c) 1999-2004 Intel Corporation


Logs from a previous boot:
Feb 20 10:33:58 boole kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker 
http://www.scyld.com/network/eepro100.html
Feb 20 10:33:58 boole kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified 
by Andrey V. Savochkin <[EMAIL PROTECTED]> and others
Feb 20 10:33:58 boole kernel: ACPI: PCI interrupt 0000:03:08.0[A] -> GSI 20 
(level, low) -> IRQ 217
Feb 20 10:33:58 boole kernel: eth0: OEM i82557/i82558 10/100 Ethernet, 
00:0D:60:68:17:98, IRQ 217.
Feb 20 10:33:58 boole kernel:   Board assembly 000000-000, Physical connectors 
present: RJ45
Feb 20 10:33:58 boole kernel:   Primary interface chip i82555 PHY #1.
Feb 20 10:33:58 boole kernel:   General self-test: passed.
Feb 20 10:33:58 boole kernel:   Serial sub-system self-test: passed.
Feb 20 10:33:58 boole kernel:   Internal registers self-test: passed.
Feb 20 10:33:58 boole kernel:   ROM checksum self-test: passed (0xed626fe2).
Feb 20 10:33:58 boole kernel: e100: Intel(R) PRO/100 Network Driver, 3.0.18
Feb 20 10:33:58 boole kernel: e100: Copyright(c) 1999-2004 Intel Corporation

-- 
Tzafrir Cohen         | New signature for new address and  |  VIM is
http://tzafrir.org.il | new homepage                       | a Mutt's  
[EMAIL PROTECTED] |                                    |  best
ICQ# 16849755         | Space reserved for other protocols | friend

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to