>-----Original Message----- >From: Pavel Machek [mailto:pavel at ucw.cz] >Sent: Friday, September 29, 2006 3:15 PM >To: Pallipadi, Venkatesh >Cc: Dave Jones; Louis Garcia; linux-pm at lists.osdl.org >Subject: Re: [linux-pm] suspending to disk on FC6 not working > >Hi! > >> > > Could not power down device &q->lock: error -22 >> > > Some devices failed to power down, aborting suspend >> > >> >Ok, I'm not quite sure how we got into this state. Venkatesh, >> >any ideas ? >> >acpi-cpufreq got quite a few changes between .17 and .18, >including the >> >two large 'P-state coordination' change. >> > >> >Louis, I'm attaching two smaller changes that went into .18. >> >Can you apply those with -R, and see if either of those makes >> >a difference? >> >> cpufreq_cpu_data[] = NULL; only happens when acpi_cpufreq driver init >> fails; >> Looks like acpi_cpufreq driver init is failing at some point in this >> case and the driver is staying loaded after that failure. >That in turn >> seems similar to one other bug I saw recently. > >Uh, if acpi_cpufreq is built-in... you can't unload it when init >fails, so you need to handle that somehow...? > Sorry. I meant unregistering with cpufreq. When acpi-cpufreq fails, it should be unregistered from cpufreq and either cpufreq should look for some other driver that may work or cpufreq should mark that there is no driver registered. I am looking at the acpi-cpufreq changes that might have resulted in this and havent found anything yet... Thanks, Venki
