From owner-freebsd-mobile Mon Jun 10 19:13:14 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 52AA537B40B for ; Mon, 10 Jun 2002 19:13:10 -0700 (PDT) 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 g5B2D9Y97985; Mon, 10 Jun 2002 20:13:09 -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 g5B2D7G25243; Mon, 10 Jun 2002 20:13:08 -0600 (MDT) (envelope-from imp@village.org) Date: Mon, 10 Jun 2002 20:12:54 -0600 (MDT) Message-Id: <20020610.201254.54547046.imp@village.org> To: parv@subdimension.com Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: is lockup "normal" after "/usr/sbin/pccardd -v" on freebsd-stable-2002.05.02? From: "M. Warner Losh" In-Reply-To: <20020610031101.GA3523@moo.holy.cow> References: <20020512215313.GA350@moo.holy.cow> <20020512.202107.81051391.imp@village.org> <20020610031101.GA3523@moo.holy.cow> 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-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message: <20020610031101.GA3523@moo.holy.cow> parv writes: : in message <20020512.202107.81051391.imp@village.org>, : wrote M. Warner Losh thusly... : > : > In message: <20020512215313.GA350@moo.holy.cow> : > parv writes: : > : i tried w/ value of 1 but there is still same lockup w/ : > : "/usr/sbin/pccardd -v". : > : > Interesting. Can you live with the problem until June 7th and then : > drop me some email so that I can properly devote the time it will take : > to diagnost this problem? : : (jun. 9 2002) hi warner, this is a reminder about the above problem. OK. I'll start pulling together the hardware necessary to try to recreate this problem. I think I know what it might be, due to some research I've done over the past year on and off and have never had the time to explore. Since I have only limited access to a machine that I think will provoke the problem, I have to plan my access to it carefully. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message