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
>
> 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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
-
To unsubscribe from this list: send the
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
-
To unsubscribe from this list: send the
18 matches
Mail list logo
