From owner-freebsd-current Thu Oct 15 13:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21958 for freebsd-current-outgoing; Thu, 15 Oct 1998 13:11:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from plethora.techv.net ([205.210.170.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21950 for ; Thu, 15 Oct 1998 13:11:28 -0700 (PDT) (envelope-from darin@slovitt.net) Received: from localhost (darin@localhost) by plethora.techv.net (8.8.8/8.8.8) with ESMTP id QAA06515; Thu, 15 Oct 1998 16:10:59 -0400 (EDT) Date: Thu, 15 Oct 1998 16:10:59 -0400 (EDT) From: Darin Slovitt X-Sender: darin@plethora.techv.net To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: Limits Problems ... In-Reply-To: <199810152010.NAA01067@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Oct 1998, Mike Smith wrote: > This is a known bug in 3.0, most commonly affecting laptop users. We > haven't been able to track down the exact cause of it. It's quite interesting that something like this isn't considered a little more important. In my case, it's on a PII 333MHz machine. The only reason why I decided to install current was because I had a 3COM 905B NIC, currently unsupported via RELEASE. Update: the problem seems to be gone ... all I did was recompile the KERNEL using GENERIC and change absolutly nothing. Seems a little disconserning that customizing the KERNEL actually introduces nasty side effects, much like this one. Ohwell, I'll just keep using GENERIC =) -- TTYS :-) Darin Slovitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message