After bypassing the macros for i915 driver in suspend resume code,  cpr 
works fine now
on my Intel Atom platform. with Alarm as well as Wake button. 
powerbutton donot seems
to work for cpr, please see below for ACPI Error.
It makes sense to work one of WAKE or PWR buttons.

Oct 27 14:58:07 lippert genunix: [ID 535284 kern.notice] System is being 
suspended
Oct 27 14:58:09 lippert genunix: [ID 228648 kern.info] ata_set_feature: 
(0x2,0x0) failed
Oct 27 14:58:09 lippert ata: [ID 745855 kern.warning] WARNING: 
/pci at 0,0/pci-ide at 1f,1/ide at 0 unable to ena
ble write cache targ=1
Oct 27 14:58:09 lippert acpica: [ID 335148 kern.notice] ACPI Error 
(evxfevnt-0292): Could not enable Pow
erButton event [20060721] <<<<
Oct 27 14:58:09 lippert genunix: [ID 228648 kern.info] ata_set_feature: 
(0x2,0x0) failed
Oct 27 14:58:09 lippert ata: [ID 745855 kern.warning] WARNING: 
/pci at 0,0/pci-ide at 1f,1/ide at 0 unable to ena
ble write cache targ=1
Oct 27 14:58:46 lippert gnome-session[1093]: [ID 702911 daemon.warning] 
WARNING: Could not ask power man
ager to suspend: Did not receive a reply. Possible causes include: the 
remote application did not send a
 reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network con
nection was broken.
Oct 27 14:58:48 lippert genunix: [ID 583038 kern.notice] System has been 
resumed.


Thanks,
Venu.


edward.shu wrote:
>   I am afriad there are bunch of hardcoded check in i915 driver, like,
> IS_945GM(), IS_G33().  I  think we should fix these MACROs before the
> device alias is added.
>
> Venu Chis
>> -bash-3.2$ uname -achip SunOS lippert 5.11 snv_100 i86pc i386 i86pc
>>
>> -bash-3.2$ /usr/sbin/smbios | grep Wake
>>   Wake-Up Event: 0x6 (power switch)
>>
>> and the instrumented i915 I have installed on the
>> system is based on the following command on oct15(not
>> sure if it matters):
>>
>> wget
>> http://dlc.sun.com/osol/on/downloads/current/on-src.tar.bz2
>>
>> Please advise anything else I could try.
>>
>> Thanks,
>> Venu.
>> --- Randy Fishel <randy.fishel at sun.com> wrote:
>>
>>  
>>>   Can you remind us again what actual release you
>>> are using?
>>>
>>>   I can understand that a keypress might not wake
>>> the machine, but the power button should (especially if the alarm 
>>> does). There was a problem not too long ago with the backlite not
>>> turning on, but some of these issues are supposed to be fixed.  So 
>>> it will
>>> be useful to know where you are in the release path.
>>>
>>>     ---- Randy
>>>
>>>
>>> On Fri, 24 Oct 2008, Venu C wrote:
>>>
>>>    
>>>> Setting acpi_rtc-wake to 6sec, I noticed system
>>>>       
>>> being
>>>    
>>>> resumed in /var/adm/messages
>>>>  
>>>> 12:27:29 System is being suspended
>>>> 12:27:48 System has been resumed
>>>>
>>>> Is this because Display backlight doesnot turn on
>>>> after
>>>> resume?
>>>>
>>>> is there any known workaround for i915 driver or Intel (0x8086, 
>>>> 0x8108) graphics controller.
>>>>
>>>> without autowake up setting, I still dont see
>>>>       
>>> resume
>>>    
>>>> event logged on reset(after waitng a while)
>>>>
>>>> Thanks,
>>>> venu.
>>>>
>>>> --- Venu C <venu at ascentronics.com> wrote:
>>>>
>>>>      
>>>>> Now I tried to disable the iprb with the
>>>>>         
>>> suggested
>>>    
>>>>> method over rem_drv approach(the mail, where I
>>>>> informed the results before I receive this).
>>>>>
>>>>> uadmin 3 22 is working fine.
>>>>>
>>>>> uadmin 3 20:
>>>>>
>>>>>  - suspend is fine
>>>>>  - resume part is not working
>>>>>     . by pressing any key didnot resume      . In my platform I 
>>>>> have power, reset, wake
>>>>> buttons
>>>>>     . When I press Wake and Power buttons, I
>>>>>         
>>> dont
>>>    
>>>>> see
>>>>>       cpr resume.
>>>>>     . after few tries, and then power cycle
>>>>>         
>>> system
>>>    
>>>>>       boots normally
>>>>>
>>>>> Did I need to change any BIOS PowerManagement
>>>>> parameters? or anything else missing.
>>>>>
>>>>> Thanks,
>>>>> Venu.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --- Randy Fishel <randy.fishel at sun.com> wrote:
>>>>>
>>>>>        
>>>>>>   So it looks like you might have a
>>>>>>           
>>> framebuffer
>>>    
>>>>>> solution.  But IIRC, you are constrained by IPRB.  A next test
>>>>>>           
>>> would be
>>>    
>>>>>> to disable this driver from loading by adding:
>>>>>>
>>>>>>     -B disable-iprb=true
>>>>>>
>>>>>> to the grub $kernel line, and see if it will
>>>>>>           
>>> now
>>>    
>>>>>> suspend (try 'uadmin 3 22 first).  I would be interested in your
>>>>>>           
>>>>> results.
>>>>>        
>>>>>>     ---- Randy
>>>>>>
>>>>>>
>>>>>> On Thu, 23 Oct 2008, Venu C wrote:
>>>>>>
>>>>>>          
>>>>>>> edward,
>>>>>>>
>>>>>>>    I had instrumented the driver not to
>>>>>>>             
>>> check
>>>    
>>>>> the
>>>>>        
>>>>>>> pciidlist by drm_probe, the driver is
>>>>>>>             
>>>>> successfully
>>>>>        
>>>>>>> installed on ATOM platform.
>>>>>>>
>>>>>>> # prtconf -D | grep i915
>>>>>>>         display, instance #0 (driver name:
>>>>>>>             
>>> i915)
>>>    
>>>>>>> #
>>>>>>> # cat /etc/name_to_major | grep i915
>>>>>>> i915 99
>>>>>>> # uadmin 3 25 99
>>>>>>> #
>>>>>>> Oct 23 14:40:14 lippert genunix: [ID 535284
>>>>>>> kern.notice] System is being suspended
>>>>>>> Oct 23 14:40:18 lippert The system is back
>>>>>>>             
>>> where
>>>    
>>>>>> you
>>>>>>          
>>>>>>> left!
>>>>>>> Oct 23 14:40:18 lippert genunix: [ID 583038
>>>>>>> kern.notice] System has been resumed.
>>>>>>>
>>>>>>> I think (0x8086, 0x8108) also could be added
>>>>>>>             
>>>>> into
>>>>>        
>>>>>> the
>>>>>>          
>>>>>>> supported device list for i915.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Venu.
>>>>>>> --- "edward.shu" <Edward.Shu at Sun.COM> wrote:
>>>>>>>
>>>>>>>            
>>>>>>>> Venu C:
>>>>>>>>              
>>>>>>>>> Kerry,
>>>>>>>>>
>>>>>>>>>   is i915 is not supporting, is just
>>>>>>>>>                 
>>> because
>>>    
>>>>>> it is
>>>>>>          
>>>>>>>> not
>>>>>>>>              
>>>>>>>>> claiming the device. or the hardware
>>>>>>>>>                 
>>>>> interface
>>>>>        
>>>>>> to          
>>>>>>>>> graphic device (0x8086, 0x8108) is
>>>>>>>>>                 
>>> supported
>>>    
>>>>>> by
>>>>>>          
>>>>>>>> i915
>>>>>>>>              
>>>>>>>>> or
>>>>>>>>> it is not compatible to i915 supported
>>>>>>>>>                 
>>>>>> hardware.
>>>>>>          
>>>>>>>>> Since the generic vgatext, is claiming
>>>>>>>>>                 
>>> and
>>>    
>>>>>> device
>>>>>>          
>>>>>>>>> works
>>>>>>>>> fine. As a simple test, if I add a
>>>>>>>>>                 
>>> driver
>>>    
>>>>>> alias
>>>>>>          
>>>>>>>> for
>>>>>>>>              
>>>>>>>>> i915 "pci8086,8108" will it work?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Venu.
>>>>>>>>> --- Kerry Shu <Kerry.Shu at Sun.COM> wrote:
>>>>>>>>>                   
>>>>>>>> i915 was supposed to support all the Intel
>>>>>>>>               
>>>>>> graphics
>>>>>>          
>>>>>>>> chips for PC.
>>>>>>>> However,  we can not test  all of the
>>>>>>>>               
>>> hardware
>>>    
>>>>>>>> before the integration,
>>>>>>>> so some chip IDs may not be included in
>>>>>>>>               
>>> the
>>>    
>>>>>>>> supported list.   As to
>>>>>>>> "pci8086,8108",  is it a graphics chip
>>>>>>>>               
>>>>> embedded
>>>>>        
>>>>>> in
>>>>>>          
>>>>>>>> ATOM platform?
>>>>>>>> It may be different from Intel graphics
>>>>>>>>               
>>> for
>>>    
>>>>> PC.
>>>>>        
>>>>>>>>>                 
>>> _______________________________________________
>>>    
>>>>>>>>> driver-discuss mailing list
>>>>>>>>> driver-discuss at opensolaris.org
>>>>>>>>>
>>>>>>>>>                 
>> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>>   === message truncated ===
>>
>>
>> _______________________________________________
>> driver-discuss mailing list
>> driver-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>>   
>
>


Reply via email to