From owner-freebsd-current Fri Jun 28 22: 0:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 462D737B400 for ; Fri, 28 Jun 2002 22:00:32 -0700 (PDT) Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4411C43E09 for ; Fri, 28 Jun 2002 22:00:31 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g5T50UY10629; Fri, 28 Jun 2002 23:00:30 -0600 (MDT) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g5T50RG69199; Fri, 28 Jun 2002 23:00:27 -0600 (MDT) (envelope-from imp@village.org) Date: Fri, 28 Jun 2002 22:59:51 -0600 (MDT) Message-Id: <20020628.225951.42144076.imp@village.org> To: gavin@ury.york.ac.uk Cc: current@FreeBSD.ORG Subject: Re: Laptop hangs with recent kernel From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: Gavin Atkinson writes: : I'm going to try backing out the recent pcmcia changes (as it has a topic : chipset) unless anyone can suggest anything else. However the hang is : random, so it may be hard to know if the back-out it fixes it. It is as good a place to start as any. I'd really like to know if it hurts you or helps you because so far it has helped all the laptops I've tried it on. i've noticed random panics in more recent kernels, but haven't been able to take a crash dump for reasons unknown. :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message