atom feed16 messages in org.freebsd.freebsd-currentRe: AP#1 Failed! panic y/n?
FromSent OnAttachments
Patrick LamaiziereAug 19, 2009 6:00 am 
Rink SpringerAug 19, 2009 6:20 am 
Ed SchoutenAug 19, 2009 7:17 am 
pluknetAug 19, 2009 7:36 am 
Ed SchoutenAug 19, 2009 7:41 am 
pluknetAug 19, 2009 7:55 am 
Patrick LamaiziereAug 19, 2009 8:07 am 
Ed SchoutenAug 19, 2009 8:09 am 
Patrick LamaiziereAug 19, 2009 10:16 am 
Patrick LamaiziereAug 19, 2009 10:19 am 
John BaldwinAug 19, 2009 10:51 am 
Jung-uk KimAug 19, 2009 11:17 am 
Jung-uk KimAug 19, 2009 11:48 am 
Ed SchoutenAug 19, 2009 11:54 pm 
pluknetAug 20, 2009 2:09 am 
pluknetAug 20, 2009 2:11 am 
Subject:Re: AP#1 Failed! panic y/n?
From:Patrick Lamaiziere (patf@davenulle.org)
Date:Aug 19, 2009 8:07:04 am
List:org.freebsd.freebsd-current

Le Wed, 19 Aug 2009 16:18:15 +0200, Ed Schouten <ed@80386.nl> a écrit :

* Patrick Lamaiziere <patf@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)

MacBookPro3,1

with dmidecode: Handle 0x0011, DMI type 1, 27 bytes System Information Manufacturer: Apple Inc. Product Name: MacBookPro3,1 Version: 1.0 Serial Number: W88080NBXAH UUID: 9CFE245E-D0C8-BD45-A79F-54EA5FBD3D97 Wake-up Type: Power Switch SKU Number: System SKU# Family: MacBook Pro

I'll have to re-add this device string to machdep.c to make it work again.

Thanks, the problem is quite reproductible here, so I can test anything and any idea if it can help.

Regards.