From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 09:35:33 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 D2039106566C for ; Thu, 15 Oct 2009 09:35:33 +0000 (UTC) (envelope-from christian@nertenher.de) Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mx1.freebsd.org (Postfix) with ESMTP id 71F298FC1D for ; Thu, 15 Oct 2009 09:35:32 +0000 (UTC) Received: by fxm22 with SMTP id 22so829383fxm.36 for ; Thu, 15 Oct 2009 02:35:32 -0700 (PDT) MIME-Version: 1.0 Sender: christian@nertenher.de Received: by 10.223.75.136 with SMTP id y8mr2130292faj.69.1255599332198; Thu, 15 Oct 2009 02:35:32 -0700 (PDT) In-Reply-To: <309b65830910130912u7fd303e9kffa1b248188b9194@mail.gmail.com> References: <309b65830910060054g16a099abxb8e203a46aa9e89c@mail.gmail.com> <4AD2BCD9.2090904@sandstorm.net> <309b65830910130912u7fd303e9kffa1b248188b9194@mail.gmail.com> From: Christian Schmidt Date: Thu, 15 Oct 2009 11:35:11 +0200 X-Google-Sender-Auth: 0abffa4795f7d462 Message-ID: <309b65830910150235w59857e83r23887193c36561f0@mail.gmail.com> To: john hood , freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: 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: Thu, 15 Oct 2009 09:35:33 -0000 On Tue, Oct 13, 2009 at 18:12, Christian Schmidt wrot= e: > 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-p1 >>> 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 boo= t the >> machine without any keyboard presses/releases between the time the loade= r >> 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 incl= udes 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, wh= at >> 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? Thank you for your help. :-) Christian