Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hello Rainer,
On Thu, Mar 05, 2015 at 10:09:04PM +0100, Rainer Dorsch wrote:
> Hi Emil,
>
> sorry for the long silence, but I did not have physical access to the machine for which I
> reported the bug and I did not want to install new kernel from remote...
>
> I recompiled a recent kernel with PM_TRACE_RTC enabled, but still get no log data in
> pm-suspend.log:
>
> root@Silberkiste:~# uname -a
> Linux Silberkiste 4.0.0-rc2+ #1 SMP Thu Mar 5 01:01:25 CET 2015 x86_64 GNU/Linux
So the issue has not been resolved in the 4.0-rc2 kernel?
> root@Silberkiste:~# grep PM_TRACE_RTC /boot/config-4.0.0-rc2+
> CONFIG_PM_TRACE_RTC=y
> root@Silberkiste:~# head -4 /usr/lib/pm-utils/pm-functions
> #!/bin/sh
> # vim:noexpandtab
>
> export PM_DEBUG=true
> root@Silberkiste:~# cat /var/log/pm-suspend.log
> root@Silberkiste:~# ls -l /var/log/pm-suspend.log
> -rw-r--r-- 1 root root 0 Jan 3 15:52 /var/log/pm-suspend.log
> root@Silberkiste:~#
>
> I did
>
> 501 echo 1 > /sys/power/pm_trace
> 502 echo mem > /sys/power/state
>
> but this did not create any logs.
>
> Do you have any suggestions, what I might do wrong?
Sorry, the /var/log/pm-suspend.log is used by the pm-suspend script.
Try suspending with pm-suspend and post the log.
Then run the following and post the dmesg output after resuming.
echo 1 > /sys/power/pm_trace
echo mem > /sys/power/state
Also did you try to suspend after blacklisting the wifi modules?
I can take a look at it but note that it may require more skilled
upstream people to resolve this issue.
Best regards,
Emil Goode
>
> Thanks,
> Rainer
>
> On Sunday 04 January 2015 18:12:44 Emil Goode wrote:
> > Hello Rainer,
> >
> > On Sat, Jan 03, 2015 at 04:23:44PM +0100, Rainer Dorsch wrote:
> > > Hi Emil,
> > >
> > > I have only remote access to the system for the next few weeks and I feel
> > > somewhat uncomfortable to experiment with my self-compiled kernels on the
> > > system or changing networking configurations.
> > >
> > > So please apologize that I may need 3-4 weeks to test that.
> > >
> > > I assume you suggest to follow
> > >
> > > http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
> > >
> > > to enable PM_TRACE_RTC and rebuild the kernel, correct?
> >
> > Yes and you can clone this tree for testing upstream kernels.
> >
> > git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> >
> > Best regards,
> >
> > Emil Goode
> >
> > > On Tuesday 30 December 2014 12:40:53 Emil Goode wrote:
> > > > Hello Rainer,
> > > >
> > > > On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote:
> > > > > Hi Emil,
> > > > >
> > > > > Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode:
> > > > > > Hello Rainer,
> > > > > >
> > > > > > The below procedure would give more information:
> > > > > >
> > > > > > Add the following line to the top of the file
> > > > > > /usr/lib/pm-utils/pm-functions.
> > > > > >
> > > > > > export PM_DEBUG=true
> > > > > >
> > > > > > Then suspend with:
> > > > > >
> > > > > > echo 1 > /sys/power/pm_trace
> > > > > > echo mem > /sys/power/state
> > > > >
> > > > > Hmm....I do not have a pm_trace
> > > >
> > > > Ok, that is because PM_TRACE_RTC needs to be enabled in the kernel
> > > > config.
> > > >
> > > > Please be aware that when using pm_trace it will mess with your
> > > > machine's
> > > > real-time clock.
> > > >
> > > > > There is a similar bug report already for an older kernel, but that
> > > > > seems
> > > > > to be fixed (?)
> > > > >
> > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264
> > > >
> > > > The iwlagn module is for intel wireless and I believe you are using
> > > > broadcom.
> > > >
> > > > > > Post dmesg and the contents of /var/log/pm-suspend.log.
> > > > > >
> > > > > > Have you tried disabling the mac80211 module?
> > > > >
> > > > > Can you tell how I unload a module for suspend or if
> > > > >
> > > > > http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint-> > > > to-u
> > > > > nload-modules-at-suspend-to-disk also applies to systemd?
> > > >
> > > > I think you can temporarily blacklist modules as described here:
> > > >
> > > > https://wiki.debian.org/KernelModuleBlacklisting
> > > >
> > > > I would also try the latest upstream kernel, this might have been fixed.
> > > >
> > > > Best regards,
> > > >
> > > > Emil Goode
>
> --
> Rainer Dorsch
> http://bokomoko.de/
Reply to: