From owner-freebsd-stable@FreeBSD.ORG Fri Apr 8 08:29:52 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3862E16A4CE for ; Fri, 8 Apr 2005 08:29:52 +0000 (GMT) Received: from ferengi.borderworlds.dk (ferengi.borderworlds.dk [80.166.152.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id A112143D58 for ; Fri, 8 Apr 2005 08:29:51 +0000 (GMT) (envelope-from xi@borderworlds.dk) Received: from borg.borderworlds.dk (localhost [127.0.0.1]) by ferengi.borderworlds.dk (Postfix) with ESMTP id D4578B806; Fri, 8 Apr 2005 10:29:49 +0200 (CEST) Received: by borg.borderworlds.dk (Postfix, from userid 1001) id AFB0211418; Fri, 8 Apr 2005 10:29:49 +0200 (CEST) Sender: xi@borderworlds.dk To: Doug White References: <867jjlrpz9.fsf@borg.borderworlds.dk> <20050402150904.M1503@carver.gumbysoft.com> <86fyy59lfm.fsf@borg.borderworlds.dk> <20050407230159.D57391@carver.gumbysoft.com> From: Christian Laursen Date: 08 Apr 2005 10:29:49 +0200 In-Reply-To: <20050407230159.D57391@carver.gumbysoft.com> Message-ID: <867jjdllhe.fsf@borg.borderworlds.dk> Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-stable@freebsd.org Subject: Re: 5.4-PRERELEASE pccard problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2005 08:29:52 -0000 Doug White writes: > On Tue, 5 Apr 2005, Christian Laursen wrote: > > > Doug White writes: > > > > > On Sat, 2 Apr 2005, Christian Laursen wrote: > > > > > > > After upgrading to 5.4-PRERELEASE as of yesterday, I now have a problem > > > > with my wireless card that has worked fine before. > > > > I now suspect that my wireless card might be going bad. Could a faulty card > > cause a panic like that? > > Certainly could if it is causing random memory corruption. It now seems that the card is not faulty. I tried another card and got the same panic. :( -- Christian Laursen