wpi and suspend/resume

Paul B Mahol onemda at gmail.com
Sat Dec 26 15:56:55 UTC 2009


On 12/26/09, Frank Staals <frank at fstaals.net> wrote:
> On 12/24/09 11:33, Paul B Mahol wrote:
>> <snip>
>> This is bug, it doesnt exits nicely if attach fail ...
>>
>> You could try, when unloading wpi module to unload another pci driver and
>> load
>> same one again while using
>>
>> hw.pci.do_power_nodriver="3"
>> hw.pci.do_power_resume="0"
>>
>> in loader.conf, maybe device doesnt get to D3 state in 'right way'.
>>
> I'm not sure I understand what you meant by that.  First I added the
> both hw.pci lines to /boot/loader.conf and rebooted. Then I tried the
> following two scenarios:
>
> 1: kldunload if_wpi
> 2: kldunload snd_hda
> 3: acpiconf -s3
> 4: resume
> 5: kldload snd_hda
> 6: kldload if_wpi
>
> However when I load if_wpi in step 6 it will not recognize the hardware.
>
> The other scenario:
>
> 1: kldunload if_wpi
> 2: kldunload snd_hda
> 3: kldload snd_hda
> 4: acpiconf -s3
> 5: kldload if_wpi
>
> This scenario again results in a panic when loading if_wpi in step 5.
> When loading if_wpi again the following message popped up in particular:
>
> wpi0: chip is in D3 power mode -- setting to d0
>
> Allthough when I checked the second scenario again without the hw.pci
> lines in /boot/loader.conf the this message also appears when
> re-enabling wpi.
>
> Is one of these scenarios what you had in mind ? Or can/should I try
> something else ?

I'm out of ideas :(

-- 
Paul B Mahol


More information about the freebsd-mobile mailing list