[lkml]   [2006]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectHZ != 1000 causes problem with serial device shown by git-bisect
I am having a problem when using PPP over a particular PCMCIA based serial device and have
pinned the problem down using git-bisect to this particular commit that was made between and 2.6.13:

59121003721a8fad11ee72e646fd9d3076b5679c is first bad commit
diff-tree 59121003721a8fad11ee72e646fd9d3076b5679c (from
Author: Christoph Lameter <>
Date: Thu Jun 23 00:08:25 2005 -0700

[PATCH] i386: Selectable Frequency of the Timer Interrupt

Make the timer frequency selectable. The timer interrupt may cause bus
and memory contention in large NUMA systems since the interrupt occurs
on each processor HZ times per second.

The problem that I am seeing can be reproduced by attempting to send large packets via a
PPP interface on the modem, e.g. "ping -s 1000".

With this patch, the value of HZ was changed from the previously "hardcoded" 1000 to be
configurable with the default being 250. My ping packet size problem goes away if I
select 1000 as the new value. I do need to be able to run with HZ = 250 (actually 100 is
better for my situation).

It looks to me like the git-bisect did not really get me down to the core problem which is
that there is something is the system that isn't happy with HZ == 250.

I have also tried a number of other kernels and the problem exists all the way to
but is fixed in 2.6.16, so I am going to git-bisect to 2.6.16, but I thought I
would get this message out now in case someone has an inkling of what the problem is.

Please cc me on any responses. Russell I copied you directly since I think you may be in
the best position to understand the problem.

Greg Lee

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-03-28 01:50    [W:0.865 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site