Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Oct 2009 19:36:12 +0200
From:      Christian Schmidt <schmidt_chr@gmx.net>
To:        Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Boot issues with a Dell Inspiron 530 and 8.0 RC1
Message-ID:  <309b65830910071036h77276ee2jb2a9c7e82fe7ba9d@mail.gmail.com>
In-Reply-To: <1254842240.23831.22.camel@buffy.york.ac.uk>
References:  <309b65830910060054g16a099abxb8e203a46aa9e89c@mail.gmail.com>  <1254842240.23831.22.camel@buffy.york.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 6, 2009 at 17:17, Gavin Atkinson
<gavin.atkinson@ury.york.ac.uk> wrote:
> On Tue, 2009-10-06 at 09:54 +0200, Christian Schmidt wrote:
>> Hello list,
>>
>> 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
[...]
> There are a couple of things that might be worth trying. =C2=A0Firstly, t=
ry
> playing with any USB-related options in the BIOS (especially "legacy
> emulation" or similar.

Okay, I had a look at that one but the BIOS does not feature a lot of
options concerning USB. There was nothing about legacy emulation or
anything remotely similar, so that was a dead-end.

> Secondly, try editing src/sys/amd64/amd64/machdep.c
> (or /sys/i386/i386/machdep.c if you are using i386), search for
> "MacBook", and adding the output of the command
> "kenv smbios.system.product"
> to the list of strings compared.

I tried that (with the help of some of the kind people from
bsdforen.de ;-)) but that didn't fix the issue at all. Rebooting
resulted in panic. Oddly enough, a complete poweroff and reboot from
the old kernel worked well enough. Like I said: a cold-boot increases
the chances significantly while a reboot is almost always bound to
fail.

> This may not make any difference, or may even make things worse (so keep
> your backup kernel ready:) but it's worth a try.

Well, it didn't immolate my machine so I'm fine. ;-)

Thanks,
Christian


--=20
Todays mistakes are tomorrows catastrophes.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?309b65830910071036h77276ee2jb2a9c7e82fe7ba9d>