Dear Andrew, dear developers!
Since 2.6.12-rc1-mmX I cannot get suspend2ram working again as it was
with 2.6.11-mm4 with the same .config.
I suspends fine, but never resumes. No CapsLock, no sysrq, no network is
working. Nothing in the log files. Is there anything which may cause
these troubles when compiled into the kernel and not loaded as module?
(as it was with my usb stuff until 2.6.11-mm2, after this I had to stop
hotplug, before I could go with usb running).
On a side node: Once suspend2ram couldn't stop all tasks, in fact
cpufreq, although it was stopped with /etc/init.d/cpufreqd stop, was
mentioned in syslog as not being able to be stopped, and after this
halfway through suspend, my touchpad (synaptics) and kbd wasn't working
anymore. After resume the touchpad is somehow behaving strange.
THe touchpad is not working at all, the keyboard seems to react to some
events (Sysrq is working, but normal typing not, nor power button/acpi
stuff).
In the syslog I find:
vmunix: psmouse.c: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 4 bytes away.
vmunix: psmouse.c: TouchPad at isa0060/serio1/input0 lot sync at byte 1
I would be happy to test some stuff to get S2R back to work!
Thanks a lot and all the best
Norbert
-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at> Universit? di Siena
sip:[email protected] +43 (0) 59966-690018
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
HARBLEDOWN (vb.)
To manoeuvre a double mattress down a winding staircase.
--- Douglas Adams, The Meaning of Liff
Hi!
> Since 2.6.12-rc1-mmX I cannot get suspend2ram working again as it was
> with 2.6.11-mm4 with the same .config.
>
> I suspends fine, but never resumes. No CapsLock, no sysrq, no network is
> working. Nothing in the log files. Is there anything which may cause
> these troubles when compiled into the kernel and not loaded as module?
> (as it was with my usb stuff until 2.6.11-mm2, after this I had to stop
> hotplug, before I could go with usb running).
Try suspend2disk, first, and try suspend2ram with minimal kernel
config.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
Same issue here.
Suspend-to-ram works perfectly fine with kernel 2.6.12-rc1-mm1, in
mm2,3 and mm4 it is broken.
It suspends properly but does not resume. Just a blackscreen and no
reaction on keypress/usb plug-in/network/power button.
regards,
Stefan
On Fre, 01 Apr 2005, Pavel Machek wrote:
> > I suspends fine, but never resumes. No CapsLock, no sysrq, no network is
> > working. Nothing in the log files. Is there anything which may cause
> > these troubles when compiled into the kernel and not loaded as module?
> > (as it was with my usb stuff until 2.6.11-mm2, after this I had to stop
> > hotplug, before I could go with usb running).
>
> Try suspend2disk, first, and try suspend2ram with minimal kernel
> config.
suspend2disk runs without any problem, even with X running.
it is only suspend2ram which stopped working after 2.6.11-mm4 (at least
in 2.6.12-rc1-mm3,4).
Concerning tests with minimal kernel config: I guess since it *was*
working there should not be a change necessary -- but well, from
2.6.11-mm2 to 2.6.11-mm4 I had to stop hotplug/usb to get ot working, so
maybe now I have to stop all the other things. Grrrr. This is not what I
want!
Isn't there a different way?
Best wishes
Norbert
-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at> Universit? di Siena
sip:[email protected] +43 (0) 59966-690018
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
DORRIDGE (n.)
Technical term for one of the lame excuses written in very small print
on the side of packets of food or washing powder to explain why
there's hardly anything inside. Examples include 'Contents may have
settled in transit' and 'To keep each biscuit fresh they have been
individually wrapped in silver paper and cellophane and separated with
corrugated lining, a cardboard flap, and heavy industrial tyres'.
--- Douglas Adams, The Meaning of Liff
Hi!
> it is only suspend2ram which stopped working after 2.6.11-mm4 (at least
> in 2.6.12-rc1-mm3,4).
>
> Concerning tests with minimal kernel config: I guess since it *was*
> working there should not be a change necessary -- but well, from
> 2.6.11-mm2 to 2.6.11-mm4 I had to stop hotplug/usb to get ot working, so
> maybe now I have to stop all the other things. Grrrr. This is not what I
> want!
>
> Isn't there a different way?
I'd like to fix the problem, but first I need to know where the
problem is. If it works with minimal config, I know that it is one of
drivers you deselected.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
Hi Pavel!
On Mon, 04 Apr 2005, Pavel Machek wrote:
> I'd like to fix the problem, but first I need to know where the
> problem is. If it works with minimal config, I know that it is one of
> drivers you deselected.
It's b44. It *was* working with b44 insmod-ed and up and running, but
now as soon as b44-eth0 is ifup-ed while suspending, the resume freezes.
If I do a ifdown eth0 before suspending, it works.
Best wishes
Norbert
-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at> Universit? di Siena
sip:[email protected] +43 (0) 59966-690018
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
PUDSEY (n.)
The curious-shaped flat wads of dough left on a kitchen table after
someone has been cutting scones out of it.
--- Douglas Adams, The Meaning of Liff
On Po 04-04-05 10:16:00, Norbert Preining wrote:
> Hi Pavel!
>
> On Mon, 04 Apr 2005, Pavel Machek wrote:
> > I'd like to fix the problem, but first I need to know where the
> > problem is. If it works with minimal config, I know that it is one of
> > drivers you deselected.
>
> It's b44. It *was* working with b44 insmod-ed and up and running, but
> now as soon as b44-eth0 is ifup-ed while suspending, the resume freezes.
> If I do a ifdown eth0 before suspending, it works.
Does this one help?
Pavel
--- clean/drivers/net/b44.c 2005-04-05 10:55:16.000000000 +0200
+++ linux/drivers/net/b44.c 2005-04-05 10:56:33.000000000 +0200
@@ -1927,6 +1927,8 @@
b44_free_rings(bp);
spin_unlock_irq(&bp->lock);
+
+ free_irq(dev->irq, dev);
return 0;
}
@@ -1940,6 +1942,9 @@
if (!netif_running(dev))
return 0;
+ if (request_irq(dev->irq, b44_interrupt, SA_SHIRQ, dev->name, dev))
+ printk(KERN_ERR PFX "%s: request_irq failed\n", dev->name);
+
spin_lock_irq(&bp->lock);
b44_init_rings(bp);
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
On Die, 05 Apr 2005, Pavel Machek wrote:
> > It's b44. It *was* working with b44 insmod-ed and up and running, but
> > now as soon as b44-eth0 is ifup-ed while suspending, the resume freezes.
> > If I do a ifdown eth0 before suspending, it works.
>
> Does this one help?
I compiled it into 2.6.12-rc2-mm1, and first wanted to try it with
module removed etc, but 2.6.12-rc2-mm1 not even freezes after resuming,
but immediately reboots!
So, more to track down. I will recreate my 2.6.12-rc1-mm4 tree, and try
your fix. Then I will try to find out *why* the hell 2.6.12-rc2-mm1 is
not resuming at all. Any ideas?
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining AT logic DOT at> Universit? di Siena
sip:[email protected] +43 (0) 59966-690018
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
QUENBY (n.)
A stubborn spot on a window which you spend twenty minutes trying to
clean off before discovering it's on the other side of the glass.
--- Douglas Adams, The Meaning of Liff
On Die, 05 Apr 2005, Pavel Machek wrote:
> > It's b44. It *was* working with b44 insmod-ed and up and running, but
> > now as soon as b44-eth0 is ifup-ed while suspending, the resume freezes.
> > If I do a ifdown eth0 before suspending, it works.
>
> Does this one help?
With 2.6.12-rc1-mm4 it did help. For 2.6.12-rc2-mm1 see previous email.
Thanks.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining AT logic DOT at> Universit? di Siena
sip:[email protected] +43 (0) 59966-690018
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
KITMURVY (n.)
Man who owns all the latest sporting gadgetry and clothing (gold
trolley, tee cosies, ventilated shoes, Gary Player- autographed
tracksuit top, American navy cap, mirror sunglasses) but is still only
on his second gold lesson.
--- Douglas Adams, The Meaning of Liff
Hi!
> Same issue here.
>
> Suspend-to-ram works perfectly fine with kernel 2.6.12-rc1-mm1, in
> mm2,3 and mm4 it is broken.
>
> It suspends properly but does not resume. Just a blackscreen and no
> reaction on keypress/usb plug-in/network/power button.
>
Same way to debug it, then.... try minimal drivers.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
>
> Same way to debug it, then.... try minimal drivers.
Yes, the lifer of a kernel debugger is hard...
Pavel, one question (maybe stupid, I am not at all an expert). Wouldn't be
possible to add a printk when invoking and returning from suspend/resume
methods of drivers, telling if they are specific or generic on? Maybe with
the help of the serial console could be an aid to detect wich drivers are
failing in that case. It could have helped the ALPS case, methinks.
Obviously, under a "kernel hacking" config. I'd love to be able to make it
myself, but I do not know where to start...
Romano
--
Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain)
Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569
Hi,
On Tuesday, 5 of April 2005 17:01, Romano Giannetti wrote:
> >
> > Same way to debug it, then.... try minimal drivers.
>
> Yes, the lifer of a kernel debugger is hard...
>
> Pavel, one question (maybe stupid, I am not at all an expert). Wouldn't be
> possible to add a printk when invoking and returning from suspend/resume
> methods of drivers, telling if they are specific or generic on? Maybe with
> the help of the serial console could be an aid to detect wich drivers are
> failing in that case.
The serial sonsole itself is disabled during suspend/resume, so you have to
hack the serial driver's suspend/resume routines to get any output on it
at that time. :-)
Anyway, if you want to put some debug printks somewhere, IMO a good place
to start is in resume_device() in drivers/base/power/resume.c or
in suspend_device() in drivers/base/power/suspend.c (actually, there already
is one, you only need to enable it).
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"