Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Aug 2009 13:51:49 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-current@freebsd.org
Cc:        Ed Schouten <ed@80386.nl>, pluknet <pluknet@gmail.com>, Patrick Lamaiziere <patfbsd@davenulle.org>, FreeBSD Current <current@freebsd.org>
Subject:   Re: AP#1 Failed! panic y/n?
Message-ID:  <200908191351.49892.jhb@freebsd.org>
In-Reply-To: <a31046fc0908190737j2a985d18xe877aa9618ab5802@mail.gmail.com>
References:  <20090819150045.0e01640a@baby-jane.lamaiziere.net> <20090819141815.GU1292@hoeg.nl> <a31046fc0908190737j2a985d18xe877aa9618ab5802@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 and
> > run `show' or whatever it's called)
> 
> I'm not Patrik, but I saw this on two Intel boxes running on 6.2.
>  smbios.system.product="S5000PAL". I didn't try the later releases on them.

Look for a BIOS update.  Your issue may be different than the MacBook issue.  
I know of some boxes of this sort where the hangs were resolved by a BIOS 
update that included newer micrcode for certain CPUs.

-- 
John Baldwin



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