Suspicious about 2.4.18

Suspicious about 2.4.18

[Michael]

I'm not really a linux expert, so I can only be suspicious.

Masquerading of iptables 1.2.5 sudently idles when "iptables -L" shows 
everything is alright. A realoading of rc.firewall brings everything back to 
normal. That happened 7 days after a normal operation. I've now upgraded to 
1.2.6 and see what happens.

Also, crond doesn't seem to operate very precisely. It is sometimes seems 
idle for 30 minutes.

I know that these may be application-specific problems, but I was curious if 
there are any current kernel issues related to them so I can quit searching 
for another cure.

Thanks. Michael.

Re: Suspicious about 2.4.18

[Adam Johansson]

On Mon, 18 Mar 2002, Michael wrote:

> I'm not really a linux expert, so I can only be suspicious.

Neither am I but I after seeing strange cron-jobs being run in the
future according to the log,I upgraded to 2.4.19pre3 and all was ok
again.

> Masquerading of iptables 1.2.5 sudently idles when "iptables -L" shows
> everything is alright. A realoading of rc.firewall brings everything back to
> normal. That happened 7 days after a normal operation. I've now upgraded to
> 1.2.6 and see what happens.
>
> Also, crond doesn't seem to operate very precisely. It is sometimes seems
> idle for 30 minutes.

I tried running this small script under 2.4.18 and noticed very strange
outputs..

// --- start ---
#!/bin/tcsh
while (1)
  date
end
// --- end ---

./timescript > output

output gives me this;
Fri Mar 15 10:17:12 CET 2002
Fri Mar 15 10:17:12 CET 2002
Fri Mar 15 10:17:12 CET 2002
Fri Mar 15 10:17:12 CET 2002
Fri Mar 15 10:17:12 CET 2002
Fri Mar 15 10:17:12 CET 2002
Fri Mar 15 11:29:43 CET 2002
Fri Mar 15 11:29:43 CET 2002
Fri Mar 15 11:29:43 CET 2002
Fri Mar 15 10:17:13 CET 2002
Fri Mar 15 10:17:13 CET 2002
Fri Mar 15 10:17:13 CET 2002
Fri Mar 15 10:17:13 CET 2002
Fri Mar 15 10:17:13 CET 2002
Fri Mar 15 10:17:13 CET 2002


Which clearly shows that something is very very strange.
I've no idea where or why this happens but since upgrading to 2.4.19pre3
helped I assume that there is something in the kernel that is wrong.
I run SuSE7.2 with a vanilla 2.4.18 (now 2.4.19pre3).

> I know that these may be application-specific problems, but I was curious if
> there are any current kernel issues related to them so I can quit searching
> for another cure.
>
> Thanks. Michael.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Cheers! /Adam

-=-=-=-=-=-=-=-=-=-=-=-=-
Adam Johansson
Developer @ MadSci AB
Phone: +46 (0)18 606462
ICQ: 58187935
http://www.madsci.se
-=-=-=-=-=-=-=-=-=-=-=-=-

Re: Suspicious about 2.4.18

[Mike Fedyk]

On Mon, Mar 18, 2002 at 10:20:50AM +0100, Adam Johansson wrote:
> // --- start ---
> #!/bin/tcsh
> while (1)
>   date
> end
> // --- end ---
> 
> ./timescript > output
> 
> output gives me this;
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 11:29:43 CET 2002
> Fri Mar 15 11:29:43 CET 2002
> Fri Mar 15 11:29:43 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> 
> 
> Which clearly shows that something is very very strange.
> I've no idea where or why this happens but since upgrading to 2.4.19pre3
> helped I assume that there is something in the kernel that is wrong.
> I run SuSE7.2 with a vanilla 2.4.18 (now 2.4.19pre3).
> 

Can you try to reproduce with pre1 and pre2?

Re: Suspicious about 2.4.18

[Pierre Lombard]

On Mon, Mar 18, 2002 at 10:20:50AM +0100, Adam Johansson wrote:
> On Mon, 18 Mar 2002, Michael wrote:
> 
> > I'm not really a linux expert, so I can only be suspicious.
> 
> Neither am I but I after seeing strange cron-jobs being run in the
> future according to the log,I upgraded to 2.4.19pre3 and all was ok
> again.

Not sure it is quite relevant but...

I had such a weird behavior on my Abit KT7 (with VIA chipsets) based
system: the time often went wild when I started doing heavy I/O between
IDE0 and IDE1... and after that the system had to be restarted :/

The workaround below by Vojtech Pavlik has fixed this issue on my system:

  Re: [PATCH] VIA timer fix was removed?
  From: Vojtech Pavlik (vojtech@suse.cz)
  Date: Mon Nov 12 2001 - 16:58:32 EST

  http://www.uwsg.iu.edu/hypermail/linux/kernel/0111.1/0951.html

> > Masquerading of iptables 1.2.5 sudently idles when "iptables -L" shows
> > everything is alright. A realoading of rc.firewall brings everything back to
> > normal. That happened 7 days after a normal operation. I've now upgraded to
> > 1.2.6 and see what happens.
> >
> > Also, crond doesn't seem to operate very precisely. It is sometimes seems
> > idle for 30 minutes.
> 
> I tried running this small script under 2.4.18 and noticed very strange
> outputs..
> 
> // --- start ---
> #!/bin/tcsh
> while (1)
>   date
> end
> // --- end ---
> 
> ./timescript > output
> 
> output gives me this;
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 10:17:12 CET 2002
> Fri Mar 15 11:29:43 CET 2002
> Fri Mar 15 11:29:43 CET 2002
> Fri Mar 15 11:29:43 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> Fri Mar 15 10:17:13 CET 2002
> 
> 
> Which clearly shows that something is very very strange.
> I've no idea where or why this happens but since upgrading to 2.4.19pre3
> helped I assume that there is something in the kernel that is wrong.
> I run SuSE7.2 with a vanilla 2.4.18 (now 2.4.19pre3).
> 
> > I know that these may be application-specific problems, but I was curious if
> > there are any current kernel issues related to them so I can quit searching
> > for another cure.

-- 
Best regards,
  Pierre Lombard