Date: Thu, 20 Aug 2009 13:11:58 +0400 From: pluknet <pluknet@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: Ed Schouten <ed@80386.nl>, freebsd-current@freebsd.org, Patrick Lamaiziere <patfbsd@davenulle.org>, FreeBSD Current <current@freebsd.org> Subject: Re: AP#1 Failed! panic y/n? Message-ID: <a31046fc0908200211x5d2ecd66gc86ff284d017862a@mail.gmail.com> In-Reply-To: <200908191351.49892.jhb@freebsd.org> References: <20090819150045.0e01640a@baby-jane.lamaiziere.net> <20090819141815.GU1292@hoeg.nl> <a31046fc0908190737j2a985d18xe877aa9618ab5802@mail.gmail.com> <200908191351.49892.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/8/19 John Baldwin <jhb@freebsd.org>: > On Wednesday 19 August 2009 10:37:21 am pluknet wrote: >> 2009/8/19 Ed Schouten <ed@80386.nl>: >> > * Patrick Lamaiziere <patfbsd@davenulle.org> wrote: >> >> From time to time, I see this at boot-time on my laptop (a Macbook >> >> pro model 3,1). I'm not sure but it seems related if an USB device is >> >> plugged in one plug (strange because the internal keyboard and the >> >> touchpad are USB devices) >> > >> > So what does smbios.system.product say? (Escape to the loader prompt a= nd >> > run `show' or whatever it's called) >> >> I'm not Patrik, but I saw this on two Intel boxes running on 6.2. >> =A0smbios.system.product=3D"S5000PAL". I didn't try the later releases o= n them. > > Look for a BIOS update. =A0Your issue may be different than the MacBook i= ssue. > I know of some boxes of this sort where the hangs were resolved by a BIOS > update that included newer micrcode for certain CPUs. > Ok. Thank you for this information, John. --=20 wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0908200211x5d2ecd66gc86ff284d017862a>