Eric Lavarde wrote:
> On 12/12/11 03:29, Jonathan Nieder wrote:
>> Does suspend-to-disk ("echo
>> disk>/sys/power/state") work fine in general?
>
> No idea in general, but I made some tests.
Thanks for this, and sorry for the slow response.
> First, it kind of worked: after restarting the computer, I got error
> messages in dmesg like the following:
> [ 569.260555] PM: Image restored successfully.
> [ 569.260556] Restarting tasks ... done.
> [ 569.260643] PM: Basic memory bitmaps freed
> [ 569.260646] video LNXVIDEO:00: Restoring backlight state
> [ 569.336385] zd1211rw 1-1.4:1.0: firmware version 4725
> [ 569.376318] zd1211rw 1-1.4:1.0: zd1211b chip 0ace:1215 v4810 high 00-02-72 AL2230_RF pa0 g--NS
> [ 569.394922] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 570.265915] I2C timeout
> [ 570.265921] IRS 00000001
[...]
> [... hundreds of line of this type ...]
Ok, sounds like nothing good.
This error message comes from the ddb_i2c_cmd() function in the
ddbridge driver. I don't think it's supposed to fail like that. :)
Ralph, Oliver, any hints for debugging this? The above is with a
v3.1-based kernel. More details are below, at
<http://bugs.debian.org/650081>, and in messages after the first one
at <http://bugs.debian.org/562008>.
Thanks,
Jonathan
> [ 676.092300] tda18212: i2c_write error
> [ 677.089780] I2C timeout
> [ 677.090203] IRS 00000001
> [ 677.090607] stv0367: i2c_write error
> [ 677.090737] c_release
> [ 677.091408] DDBridge 0000:03:00.0: PCI INT A disabled
>
> And VDR was frozen for perhaps one minute, then it restarted itself, and
> then everything was fine. Only WLAN was still not working, unplug/plug the
> USB stick did make it work again.
>
> Then I modified my test script to set the wake-up time and disk > state but
> then my computer froze (see attached picture).
> After reboot, I tried again, shutting off nodm (for vdr-sxfe) and vdr before
> calling my test script. And the computer woke up!
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
