tcp_sack_output: Computed sack hole not the same as cached value
From: Daniel Eriksson (daniel_k_eriksson_at_telia.com)
Date: 06/30/05
- Previous message: Suleiman Souhlal: "Re: Acquiring lockmgr lock "ufs" with non-sleepable locks"
- Next in thread: Mohan Srinivasan: "Re: tcp_sack_output: Computed sack hole not the same as cached value"
- Reply: Mohan Srinivasan: "Re: tcp_sack_output: Computed sack hole not the same as cached value"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 30 Jun 2005 19:00:38 +0200 To: <freebsd-current@freebsd.org>
With latest CURRENT (2005.06.30.12.00.00) I get a ton of these messages
on the console. 50-100 per minute and that's when load is light. With
the old kernel (2005.06.23.00.30.00) no such messages show up.
tcp_sack_output: Computed sack hole not the same as cached value
This is on an SMP machine. On my UP server I saw no messages, but I only
had the two machines (one UP and one SMP) running the new kernel for a
few minutes.
/Daniel Eriksson
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Suleiman Souhlal: "Re: Acquiring lockmgr lock "ufs" with non-sleepable locks"
- Next in thread: Mohan Srinivasan: "Re: tcp_sack_output: Computed sack hole not the same as cached value"
- Reply: Mohan Srinivasan: "Re: tcp_sack_output: Computed sack hole not the same as cached value"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
