Re: HEADSUP: Sleep queues added to kernel, so be careful.

From: Craig Rodrigues (rodrigc_at_crodrigues.org)
Date: 02/29/04

  • Next message: Vincent Poy: "Re: HEADSUP: Sleep queues added to kernel, so be careful." 
    Date: Sat, 28 Feb 2004 21:17:54 -0500
To: Vincent Poy <vince@oahu.WURLDLINK.NET>

    On Sat, Feb 28, 2004 at 03:08:19PM -1000, Vincent Poy wrote:
    > I wonder if changing the "WARNS?=" back to "WARNS= 0" will
    > actually fix the problem.

    I doubt that this is a Makefile problem.
    I think it is more likely that one of the changes
    to /usr/src/sys/netinet/ip_divert.c is
    causing the problem. 

    -- 
Craig Rodrigues        
http://crodrigues.org
rodrigc@crodrigues.org
_______________________________________________
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"
  • Next message: Vincent Poy: "Re: HEADSUP: Sleep queues added to kernel, so be careful."

    Relevant Pages

    • 4.10-RELEASE Installation Locks Up
      ... Is there anything I can do to fix this problem? ... How likely is it that the less-than-perfect IDE cable is causing this problem? ... - Dave V. ... To unsubscribe, ...
      (freebsd-questions)
    • Re[2]: portsdb core dump
      ... *This message was transferred with a trial version of CommuniGatePro* ... >he has found the lines causing the problem. ... >and fix it:). ... To unsubscribe, ...
      (freebsd-questions)
    • [Fwd: Cron <operator@ekg> /usr/libexec/save-entropy]
      ... Can anybody indicate to me what is causing the attached email and how to ... fix it? ... Tom Veldhouse ... To unsubscribe, ...
      (freebsd-stable)
    • Re: Cant mount partition on slave drive
      ... >> It also does not show up in dmesg. ... What could be causing this? ... >> I do to fix it? ... To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org ...
      (Debian-User)
    • Re: C# & Microsoft
      ... a native image that was causing the problem, and those are nearly impossible to find, much less fix. ... It was a VisualC.dll native image that was causing the problem, and oddly enough, that is not a managed DLL, and shouldn't have been loaded at all. ... I believe it was related to an install of an early beta of the WinFX SDK that I did around December. ...
      (microsoft.public.dotnet.languages.csharp)