-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Oct 3, 2007, at 09:37, SUNAGAWA Keiki wrote:

>> I thought I fixed this in 4.0 but I guess I was wrong.
>> On some newer *Books we accidentally power down when the adb driver
>> attaches. As far as I know this happens on machines which don't have
>> an ADB bus, so the PMU regards ADB commands as error and powers down.
>> The attached patch will prevent the adb driver from issuing any ADB
>> commands when the pmu node doesn't have an adb child. I've tested it
>> on a PowerMac G4 which doesn't have ADB but the PMU is similar enough
>> to the one used in newer PowerBooks although it doesn't power down on
>> every error and a PowerBook 3400c which does have ADB. On the G4 no
>> ADB commands are issued ( usually there would be a timeout message )
>> and on the PowerBook the normal ADB devices attach.
>>
>> Please test this on machines with or without ADB, if it fixes the
>> power down problem and doesn't have any funny side effects I'll
>> request pullup into 4.0
>
> Do you have a test kernel with the patch incorporated?

Sure:
ftp://ftp.netbsd.org/pub/NetBSD/misc/macallan/macppc/netbsd_4_generic

> BTW, my PowerBook G4 12" powered down when I hitted f2 key
> twice or more with the kernel 3.99.x or earlier, but 4.99.31
> works fine.  Not tested 4.0.x.

Sounds like something trying to control brightness on a PMU that  
doesn't support it - same thing, PMU thinks it got an invalid command  
and powers down.

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBRwQ+M8pnzkX8Yg2nAQKemwf/Yu4dKWGllI+scMxmeVJqZFmXYAPhVQ4f
9WG3BlpnJUvI98h5Ok7t8v+iEeE6+vSLA9dIj5Rq69vQ5lYYbu4t7QTJIieaKsK6
Y8AQptjhQisB/5S0rccmjiC6pQUeaCP9lstI+O9/KZDW3C/hsCrD77RVbY9SiMm0
SY0hNgyRxtRkh3O1aWdHDlGec7VmauoLeva9j0IPBuDFmzSeaZNN6mwjZNOs4yHo
U86OQ0+sT1rDCucc+k0+pSyWB1tmIKFTyPmbuVsPznKuoox8M/JxZ+THSViVc1zE
QvyrW0rJ84bAmYphq4dlxPgdS1AgE3/jZOWbX6Iz7gqUMHjeya2bBw==
=9D4H
-----END PGP SIGNATURE-----