This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.

You need to provide a working fdi file snippet for this to get fixed; see these
pages for how to do that

 http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-index.html

Hello Daniel,

do thinks work with "pm-suspend --quirk-old"? That should be the same
as "pm-suspend --quirk-dpms-suspend".

Thanks a lot,

Florian La Roche

It still works with "--quirk-old" and it also works with "--quirk-dpms-suspend".
The upstreamd quirk from git uses "--quirk-radeon-off" which does NOT work.

As it works with --quirk-old, there is something wrong with pm-utils as it
should do this automatically when no quirks are passed. Reassigning to pm-utils.

Clear Devel ACK as it's a regression.

Fix for pm-utils is available.

Thanks,

Read ya, Phil

Tried with pm-utils-0.99.3-6.el5.14.i386 but still the same behaviour.

After some debugging of the problem i found out that it steems from the newly
added FDI file for IBM laptops in hal:

https://bugzilla.redhat.com/show_bug.cgi?id=251496

If you take a look at the FDI file from comment #26 for IBM laptops there you
seen an entry for the X32 that looks like this:

      <!-- X32 -->
      <match key="system.hardware.version" string="ThinkPad X32">
        <merge key="power_management.quirk.radeon_off" type="bool">true</merge>
        <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
        <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
      </match>

which contains the radeon_off quirk but not the dpms_suspend quirk. And Daniel
already tested with his IBM X32 that --quirk-dpms-suspend works but
--quirk-radeon-off does not.

So 2 possible solutions are now available:

- Fix the X32 entry like this:

      <!-- X32 -->
      <match key="system.hardware.version" string="ThinkPad X32">
        <merge key="power_management.quirk.dpms_suspend" type="bool">true</merge>
        <merge key="power_management.quirk.radeon_off" type="bool">true</merge>
        <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
        <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
      </match>

- Remove the whole newly added FDI file.

The reason for the 2nd suggestion comes from an in-depth review of the new IBM
and Lenovo FDI files. It shows that a lot of the quirks for various models
deviate strongly from the original quirks that were used in RHEL-5 GA. As we've
now already found 1 model where the new quirks are not working properly this
seems to be a dangerous change for all IBM and Lenovo laptops despite the tests
that were done using those quirks.

Of course it's up to David to decide which fix to implement, so i'm leaving the
decision up to him.

Reassigning this bug to hal as it needs to be fixed there.

Read ya, Phil

If I am not completely mistaken, that quirk was not installed on my laptop when
testing. Where should it be?

Addint an FDI with dpms-suspend indeed works (I created my onwn one for daily work).

Here is the fdi-information that is installed:
/usr/share/hal/fdi/information/10freedesktop
/usr/share/hal/fdi/information/10freedesktop/10-camera-ptp.fdi
/usr/share/hal/fdi/information/10freedesktop/10-cd-dvd-burner.fdi
/usr/share/hal/fdi/information/10freedesktop/10-usb-card-readers.fdi
/usr/share/hal/fdi/information/10freedesktop/10-usb-music-players.fdi
/usr/share/hal/fdi/information/10freedesktop/10-usb-pda.fdi
/usr/share/hal/fdi/information/10freedesktop/10-usb-zip-drives.fdi
/usr/share/hal/fdi/information/10freedesktop/10-wireless-mice.fdi
/usr/share/hal/fdi/information/20thirdparty

Hal version on my test system:
hal-0.5.8.1-23.el5

According to bug 251496 it should not have the IBM FDI.

Hello Daniel.

Could you provide the output of

/sbin/lspci -mn

please? Something really strange is going on atm as you should be getting the
old behaviour with the latest version of pm-utils.

Thanks,

Read ya, Phil

Here ya go:

[root@scorp information]# lspci -nm
00:00.0 "0600" "8086" "3340" -r03 "1014" "0529"
00:01.0 "0604" "8086" "3341" -r03 "" ""
00:1d.0 "0c03" "8086" "24c2" -r01 "1014" "052d"
00:1d.1 "0c03" "8086" "24c4" -r01 "1014" "052d"
00:1d.2 "0c03" "8086" "24c7" -r01 "1014" "052d"
00:1d.7 "0c03" "8086" "24cd" -r01 -p20 "1014" "052e"
00:1e.0 "0604" "8086" "2448" -r81 "" ""
00:1f.0 "0601" "8086" "24cc" -r01 "" ""
00:1f.1 "0101" "8086" "24ca" -r01 -p8a "1014" "052d"
00:1f.3 "0c05" "8086" "24c3" -r01 "1014" "052d"
00:1f.5 "0401" "8086" "24c5" -r01 "1014" "0534"
00:1f.6 "0703" "8086" "24c6" -r01 "1014" "0559"
01:00.0 "0300" "1002" "4c59" "1014" "052f"
02:00.0 "0607" "1180" "0476" -raa "1014" "0532"
02:00.1 "0607" "1180" "0476" -raa "1014" "0532"
02:00.2 "0c00" "1180" "0552" -r02 -p10 "1014" "0533"
02:01.0 "0200" "8086" "101e" -r03 "1014" "0549"
02:02.0 "0280" "8086" "4220" -r05 "8086" "2711"

Now i'm really confused.

This should enable the same quirks as RHEL-5 GA and therefore expose the same
behaviour as using pm-suspend --quirk-old or for ATI cards pm-suspend
--quirk-dpms-suspend. I've just verified that this happens on 2 laptops here
with pm-utils-0.99.3-6.el5.12 or newer and a hal package without any
vendor/model specific fdi files (e.g. hal-0.5.8.1-23.el5).

I have 0 clue whats going on here at the moment and can't reproduce it on any
machine here.

The only way i could see whats going on is if i'd get access to that machine.

Read ya, Phil

Put patch from comment 24 into 0.5.8.1-25.el5

I tested this and it works.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2007-0632.html