From: Pavel Machek <pavel@suse.cz>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, acpi-support@lists.sourceforge.net
Subject: Re: [2.5.75] S3 and S4
Date: Fri, 11 Jul 2003 22:45:06 +0200 [thread overview]
Message-ID: <20030711204506.GA169@elf.ucw.cz> (raw)
In-Reply-To: <20030711200053.GA402@elf.ucw.cz>
Hi!
> > Fixing swap signatures... <3>bad: scheduling while atomic!
> > Call Trace:
> > [<c012419e>] schedule+0x6ce/0x6e0
> > [<c02a219d>] generic_make_request+0x17d/0x210
> > [<c01272d0>] autoremove_wake_function+0x0/0x50
> > [<c012641e>] io_schedule+0xe/0x20
> > [<c0150522>] wait_on_page_bit+0xa2/0xd0
> > [<c01272d0>] autoremove_wake_function+0x0/0x50
> > [<c01272d0>] autoremove_wake_function+0x0/0x50
> > [<c017194b>] swap_readpage+0x5b/0x80
> > [<c0171a2a>] rw_swap_page_sync+0xba/0x110
> > [<c014d8be>] mark_swapfiles+0x7e/0x1b0
> > [<c014ea35>] do_magic_resume_2+0xe5/0x170
> > [<c011d410>] restore_processor_state+0x70/0x90
> > [<c011ff5f>] do_magic+0x11f/0x140
> > [<c014ef1d>] do_software_suspend+0x6d/0xa0
> > [<c023e3cc>] acpi_system_write_sleep+0x11b/0x132
> > [<c0177de0>] filp_open+0x60/0x70
> > [<c017952d>] vfs_write+0xad/0x120
> > [<c017963f>] sys_write+0x3f/0x60
> > [<c010b10f>] syscall_call+0x7/0xb
>
> Ahha, this looks like generic problem. I'll probably take a look...
It is not generic -- I can't reproduce it here. Perhaps its side
effect of your e100 problems? You have to debug...
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-07-11 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 19:36 [2.5.75] S3 and S4 Kronos
2003-07-11 20:00 ` Pavel Machek
2003-07-11 20:45 ` Pavel Machek [this message]
2003-07-11 20:48 ` Andrew Morton
2003-07-11 21:52 ` Pavel Machek
2003-07-11 21:53 ` Andrew Morton
2003-07-12 13:54 ` Pavel Machek
2003-07-12 16:45 ` [ACPI-sppt] " Kronos
2003-07-12 20:12 ` Pavel Machek
2003-07-17 19:09 ` Kronos
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=20030711204506.GA169@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=acpi-support@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).