From: Alan Jenkins <sourcejedi.lkml@googlemail.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: hugh.dickins@tiscali.co.uk, Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
pm list <linux-pm@lists.linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: s2disk hang update
Date: Sat, 2 Jan 2010 15:03:56 +0000 [thread overview]
Message-ID: <9b2b86521001020703v23152d0cy3ba2c08df88c0a79@mail.gmail.com> (raw)
Hi,
I've been suffering from s2disk hangs again. This time, the hangs
were always before the hibernation image was written out.
They're still frustratingly random. I just started trying to work out
whether doubling PAGES_FOR_IO makes them go away, but they went away
on their own again.
I did manage to capture a backtrace with debug info though. Here it
is for 2.6.33-rc2. (It has also happened on rc1). I was able to get
the line numbers (using gdb, e.g. "info line
*stop_machine_create+0x27"), having built the kernel with debug info.
[top of trace lost due to screen height]
? sync_page (filemap.c:183)
? wait_on_page_bit (filemap.c:506)
? wake_bit_function (wait.c:174)
? shrink_page_list (vmscan.c:696)
? __delayacct_blkio_end (delayacct.c:94)
? finish_wait (list.h:142)
? congestion_wait (backing-dev.c:761)
? shrink_inactive_list (vmscan.c:1193)
? scsi_request_fn (spinlock.h:306)
? blk_run_queue (blk-core.c:434)
? shrink_zone (vmscan.c:1484)
? do_try_to_free_pages (vmscan.c:1684)
? try_to_free_pages (vmscan.c:1848)
? isolate_pages_global (vmscan.c:980)
? __alloc_pages_nodemask (page_alloc.c:1702)
? __get_free_pages (page_alloc.c:1990)
? copy_process (fork.c:237)
? do_fork (fork.c:1443)
? rb_erase
? __switch_to
? kthread
? kernel_thread
? kthread
? kernel_thread_helper
? kthreadd
? kthreadd
? kernel_thread_helper
INFO: task s2disk:2174 blocked for more than 120 seconds
...
Call Trace:
? __switch_to
? schedule_timeout
? check_preempt_wakeup
? wait_for_common
? default_wake_function
? kthread_create:133
? worker_thread
? schedule
? create_workqueue_thread
? worker_thread
? __create_workqueue_key (workqueue.c:1006)
? stop_machine_create (stop_machine.c:121)
? disable_nonboot_cpus (cpu.c:370)
? hibernation_snapshot
? snapshot_ioctl
...
? sys_ioctl
Thanks for everything
Alan
next reply other threads:[~2010-01-02 15:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 15:03 Alan Jenkins [this message]
2010-01-02 20:38 ` Rafael J. Wysocki
2010-02-02 14:21 ` Alan Jenkins
2010-02-02 20:34 ` Rafael J. Wysocki
2010-02-03 11:14 ` Alan Jenkins
2010-02-09 16:36 ` Alan Jenkins
2010-02-15 23:08 ` Rafael J. Wysocki
2010-02-16 11:09 ` Alan Jenkins
2010-02-16 15:12 ` Alan Jenkins
2010-02-16 21:16 ` Rafael J. Wysocki
2010-02-17 11:27 ` Alan Jenkins
2010-02-17 19:58 ` Rafael J. Wysocki
2010-02-18 12:53 ` Alan Jenkins
2010-02-18 20:04 ` Rafael J. Wysocki
2010-02-19 11:48 ` Alan Jenkins
2010-02-21 20:47 ` Rafael J. Wysocki
2010-02-22 15:35 ` Alan Jenkins
2010-02-22 19:17 ` Rafael J. Wysocki
2010-02-23 14:24 ` Alan Jenkins
2010-02-23 21:13 ` Rafael J. Wysocki
2010-02-24 1:20 ` KAMEZAWA Hiroyuki
2010-02-24 20:19 ` Alan Jenkins
2010-02-24 20:36 ` Rafael J. Wysocki
2010-02-24 16:23 ` Alan Jenkins
2010-02-24 20:52 ` Rafael J. Wysocki
2010-02-25 13:10 ` Alan Jenkins
2010-02-25 20:04 ` Rafael J. Wysocki
2010-02-26 9:26 ` Alan Jenkins
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=9b2b86521001020703v23152d0cy3ba2c08df88c0a79@mail.gmail.com \
--to=sourcejedi.lkml@googlemail.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mel@csn.ul.ie \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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®