Date: Thu, 15 Oct 2009 11:35:11 +0200 From: Christian Schmidt <schmidt_chr@gmx.net> To: john hood <jh@sandstorm.net>, freebsd-current@freebsd.org Subject: Re: Boot issues with a Dell Inspiron 530 and 8.0 RC1 Message-ID: <309b65830910150235w59857e83r23887193c36561f0@mail.gmail.com> In-Reply-To: <309b65830910130912u7fd303e9kffa1b248188b9194@mail.gmail.com> References: <309b65830910060054g16a099abxb8e203a46aa9e89c@mail.gmail.com> <4AD2BCD9.2090904@sandstorm.net> <309b65830910130912u7fd303e9kffa1b248188b9194@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 13, 2009 at 18:12, Christian Schmidt <schmidt_chr@gmx.net> wrot= e: > On Mon, Oct 12, 2009 at 07:21, john hood <jh@sandstorm.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?309b65830910150235w59857e83r23887193c36561f0>