Re: Could not suspend device [VIA UHCI USB controller]: error -22

[Pavel Machek <pavel@ucw.cz>]

Hi!

> >>Also, "suspend to mem" does just nothing, -- the same as "suspend to disk"
> >>(but for disk, it never worked at all as stated above).
> > 
> > 
> > Can you quote exact messages? Suspend to mem should not have problems
> > without 4MB pages, as it does not do any pagetables related magic. If
> > it does include same check, it is bug and should be easy to fix.
> 
> Hmm.. There's no messages, no at all.
> 
>  echo mem > /sys/power/state
> 
> does exactly nothing.  When writing 'suspend' to that file, the
>system

I think you mean 'standby'?

> at least tries to do something (now with 2.6.15-rc4 it completes the
> syspend procedure; but it wakes up again in a secound or two), with all
> the messages et al, but not 'mem' or 'disk' - no messages at all.

You are hitting something else than missing 4MB pages:

static inline int
arch_prepare_suspend(void)
{
        /* If you want to make non-PSE machine work, turn off paging
           in swsusp_arch_suspend. swsusp_pg_dir should have identity
mapping, so
           it could work...  */
        if (!cpu_has_pse) {
                printk(KERN_ERR "PSE is required for swsusp.\n");
                return -EPERM;
        }
        return 0;
}

...so just insert printks into the code to find out what is going on...

								Pavel
-- 
Thanks, Sharp!