All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willi Mann <foss-ml@wm1.at>
To: linux-pm@lists.osdl.org
Subject: CONFIG_PM_VERBOSE causing system lockup
Date: Tue, 07 Sep 2010 11:23:45 +0200	[thread overview]
Message-ID: <i650b3$h98$1@dough.gmane.org> (raw)

Hi!

For trying to test my software suspend issue I reported a month ago with 
kernel 2.6.36-rc3, I enabled CONFIG_PM_VERBOSE. Unfortunately, this causes a 
complete system lockup when I execute

dpkg-reconfigure linux-image-2.6.36-rc3

I discovered this by accident. I guess other commands causing serious amount 
of hard disk access could trigger the same, but I didn't test. 

I logged the following via netconsole, but kernel messages are written to 
both /var/log/syslog and /var/log/kern.log too. (I could imagine that this 
causes the problem). They are also written to local console as I've set log 
level 8 for the console. The last page of the screen before it freezes only 
contains the messages from the log. I tried to issue SysRQ-commands, but 
that doesn't cause any reaction. 

http://wserver.wm1.at/~willi/linux/config_pm_verbose/suspend-hang2.log.gz

Any ideas how to solve this problem?

WM

                 reply	other threads:[~2010-09-07  9:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='i650b3$h98$1@dough.gmane.org' \
    --to=foss-ml@wm1.at \
    --cc=linux-pm@lists.osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.