From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 16:10:47 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 055811065670 for ; Fri, 16 Oct 2009 16:10:47 +0000 (UTC) (envelope-from christian@nertenher.de) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id 9B40C8FC0C for ; Fri, 16 Oct 2009 16:10:46 +0000 (UTC) Received: by fxm6 with SMTP id 6so2520541fxm.43 for ; Fri, 16 Oct 2009 09:10:45 -0700 (PDT) MIME-Version: 1.0 Sender: christian@nertenher.de Received: by 10.223.57.22 with SMTP id a22mr298741fah.4.1255709445268; Fri, 16 Oct 2009 09:10:45 -0700 (PDT) In-Reply-To: <20091015183338.37FBB1CC44@ptavv.es.net> References: <309b65830910150235w59857e83r23887193c36561f0@mail.gmail.com> <20091015183338.37FBB1CC44@ptavv.es.net> From: Christian Schmidt Date: Fri, 16 Oct 2009 18:10:25 +0200 X-Google-Sender-Auth: ed3a6019c60500e6 Message-ID: <309b65830910160910v5081b098tfec440db48bb08a8@mail.gmail.com> To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: john hood , freebsd-current@freebsd.org Subject: Re: Boot issues with a Dell Inspiron 530 and 8.0 RC1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 16:10:47 -0000 On Thu, Oct 15, 2009 at 20:33, Kevin Oberman wrote: >> From: Christian Schmidt >> Date: Thu, 15 Oct 2009 11:35:11 +0200 >> Sender: owner-freebsd-current@freebsd.org >> >> On Tue, Oct 13, 2009 at 18:12, Christian Schmidt w= rote: >> > On Mon, Oct 12, 2009 at 07:21, john hood wrote: >> >> Christian Schmidt wrote: >> > [...] >> >>> I am seeing a strange issue with my Dell Inspiron 530 with 8.0 RC1-p= 1 >> >>> at around 50-75% percent of all boots. It all boils down to GENERIC >> >>> throwing the following: >> >>> >> >>> AP #1 (PHY #1) failed! >> >>> panic y/n? [y] panic: bye-bye >> >>> cpuid =3D 0 >> > [...] >> >> We have 3 of these machines. >> >> >> >> In my experience, keyboard activity triggers the problem. =C2=A0If I = boot the >> >> machine without any keyboard presses/releases between the time the lo= ader >> >> starts the kernel and some time later, definitely by the time the USB >> >> keyboard driver attaches, then I don't get this problem. =C2=A0This i= ncludes any >> >> key-up (and maybe key repeat) events you may generate after typing a = key at >> >> the boot menu, or after typing enter at the OK prompt, or pressing a = key to >> >> bypass the autoboot timeout that counts down by seconds. >> >> >> >> If you let the machine start from cold without touching the keyboard,= what >> >> happens? >> > >> > That is a very interesting point you are making. Indeed, it never >> > occured to me that I am usually hammering down on F1 and 1 to boot >> > faster (yeah yeah, I know ;-)). I let the machine boot through without >> > that a couple of times and it seemed to have worked for about a 100% >> > of those cases. I will keep testing but I think we have a hot >> > contender. :-) >> > >> >> Okay, after testing that for a couple of days I can confirm that it >> never-ever happens when I leave the keyboard alone during the >> boot-phase. As a workaround, I can live with not touching the >> keyboard. Nethertheless, this seems to be a bug that deserves fixing, >> isn't it? > > FWIW, I've seen this at least as far back as V5 and I think I have seen > it on V4. I have no idea if it happened in V3. That was too long ago. > > IT would be nice to see this fixed, but I think we have all lived with > it for a long time and most have either learned not to type stuff before > the device probes have ended or they have never happened to trigger it. > > In my case, it seems like it is OK to type after the keyboard probe is > completed. Okay, I'll take that as the closing statement. :-) Now that I know what the problem is I can just work around it. Thanks for the useful hints! Cheers, Christian