From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Ingo Molnar <mingo@elte.hu>
Cc: Daniel Walker <dwalker@mvista.com>,
linux-kernel@vger.kernel.org, planetccrma@ccrma.Stanford.EDU,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PlanetCCRMA] Re: 2.6.22.6 + rt9: suspend/hibernate not working
Date: Thu, 06 Sep 2007 16:30:03 -0700 [thread overview]
Message-ID: <1189121403.10587.24.camel@cmn3.stanford.edu> (raw)
In-Reply-To: <1189108535.10587.11.camel@cmn3.stanford.edu>
[-- Attachment #1: Type: text/plain, Size: 2765 bytes --]
On Thu, 2007-09-06 at 12:55 -0700, Fernando Lopez-Lezcano wrote:
> On Thu, 2007-09-06 at 11:42 -0700, Fernando Lopez-Lezcano wrote:
> > On Tue, 2007-09-04 at 17:15 -0700, Daniel Walker wrote:
> > > On Tue, 2007-09-04 at 17:12 -0700, Fernando Lopez-Lezcano wrote:
> > > > Hi Ingo... I'm getting reports from some of my Planet CCRMA users (which
> > > > I confirmed) that the latest rt kernel I released has broken suspend
> > > > (tested on fc6 & fc7, stock Fedora kernel works fine - the rt
> > > > configuration files are virtual clones as far as possible of the
> > > > standard Fedora kernel config files).
> > > >
> > > > I don't know where to start debugging this. When suspend is initiated it
> > > > freezes with a "Stopping tasks ... " message in the text console - a
> > > > hard power cycle is the only way to get the machine back to normal.
> > > >
> > > > kernel/power/process.c seems to contain that string in the
> > > > freeze_processes function so it looks like the freezer is not freezing
> > > > tasks as no "done" message is ever printed.
> > > >
> > > > What could we do to help?
> > >
> > > If you have high resolution timers enabled you could try disabling it,
> > > and see if the problem persists .
> >
> > The problem is still there ("Stopping tasks ... " and nothing
> > afterwards).
>
> Looks like it was a known problem (sorry about the noise), see:
> http://lkml.org/lkml/2007/8/25/117
>
> It does fix the problem here as well.
> Ingo: is this still the right fix for 2.6.22.6 + rt9?
I'm seeing this while going into suspend:
...
Disabling non-boot CPUs ...
Breaking affinity for irq 218
CPU 1 is now offline
SMP alternatives: switching to UP code
BUG: sleeping function called from invalid context pm-suspend(3676) at
kernel/rtmutex.c:636
in_atomic():0 [00000000], irqs_disabled():1
[<c061c13d>] __rt_spin_lock+0x21/0x3d
[<c0461b2c>] free_pages_bulk+0x28/0x188
[<c042653d>] migration_call+0x3a5/0x3be
[<c0461cd4>] __drain_pages+0x48/0x69
[<c0461d0a>] page_alloc_cpu_notify+0x15/0x2b
[<c061e083>] notifier_call_chain+0x2a/0x47
[<c0435fe8>] raw_notifier_call_chain+0x17/0x1a
[<c0446869>] _cpu_down+0x17a/0x238
[<c042b4e5>] printk+0x1f/0x92
[<c0446ad0>] disable_nonboot_cpus+0x4e/0xd2
[<c044b673>] enter_state+0x116/0x1d6
[<c044b831>] state_store+0xc9/0xe0
[<c044b768>] state_store+0x0/0xe0
[<c04b44cf>] subsys_attr_store+0x27/0x2b
[<c04b45db>] sysfs_write_file+0x9a/0xbd
[<c04b4541>] sysfs_write_file+0x0/0xbd
[<c047bc97>] vfs_write+0xa8/0x15a
[<c047c2c0>] sys_write+0x41/0x67
[<c0404ef6>] syscall_call+0x7/0xb
=======================
CPU1 is down
PM: Entering mem sleep
thinkpad_acpi thinkpad_acpi: LATE suspend
...
I'm attaching the whole compressed dmesg output to put it in context.
-- Fernando
[-- Attachment #2: dmesg.1.bz2 --]
[-- Type: application/x-bzip, Size: 11077 bytes --]
next prev parent reply other threads:[~2007-09-06 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 0:12 Fernando Lopez-Lezcano
2007-09-05 0:15 ` Daniel Walker
2007-09-06 18:42 ` Fernando Lopez-Lezcano
2007-09-06 19:55 ` Fernando Lopez-Lezcano
2007-09-06 23:30 ` Fernando Lopez-Lezcano [this message]
2007-09-06 3:38 ` Pavel Machek
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=1189121403.10587.24.camel@cmn3.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=planetccrma@ccrma.Stanford.EDU \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®