On Thu, 2006-08-03 at 12:32 -0400, Theodore Tso wrote:
This only shows up with the real-time kernel where timer softirq's run
in their own processes, and a high priority process preempts the timer
softirq. I don't really consider this a networking bug, or even
driver bug, although it does seem unfortunate that Broadcom hardware
locks up and goes unresponsive if the OS doesn't tickle it every tenth
of a second or so. (Definitely a bad idea if the tg3 gets used on any
laptops, from a power usage perspective.) But that seems like a
(lame) hardware bug, not a driver bug....
There is some form of priority inheritance on the timer softirq. It said
in the patch header that the right fix was for the timer softirq to
change priorities. Which Real Time patch are you using? Or is the
current system not sufficient ?
Daniel