From: Felix Homann <fexpop@onlinehome.de>
To: linux-kernel@vger.kernel.org
Subject: Regressions w.r.t. suspend behaviour in recent kernel versions
Date: Fri, 24 Aug 2007 14:42:55 +0200 [thread overview]
Message-ID: <46CED24F.1020400@onlinehome.de> (raw)
Hi,
I've been experiencing several problems with s2ram/s2disk with recent
kernels (mostly starting with 2.6.19):
1. s2disk won't work without the nolapic kernel option.
I didn't have to use that option with kernels < 2.6.19. I only found out
that I need this option with the kind help from Rafael Wysocki.
Unfortunately, using the nolapic option raises new problems as I'm
getting these warnings at boot time (with kernel 2.6.23-rc2):
++++++++++++++++++++++++++++++++++++
Aug 9 00:22:13 jawaka kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Aug 9 00:22:13 jawaka kernel: WARNING: at kernel/irq/resend.c:70
check_irq_resend()
Aug 9 00:22:13 jawaka kernel: [<c014afab>] check_irq_resend+0xab/0xc0
Aug 9 00:22:13 jawaka kernel: [<c014ab99>] enable_irq+0xc9/0xd0
Aug 9 00:22:13 jawaka kernel: [<c026ab54>]
ide_config_drive_speed+0x164/0x380
Aug 9 00:22:13 jawaka kernel: [<c0266162>] piix_tune_chipset+0x1f2/0x3d0
Aug 9 00:22:13 jawaka kernel: [<c0270bfb>] ide_tune_dma+0x3b/0x50
Aug 9 00:22:13 jawaka kernel: [<c0265eec>]
piix_config_drive_xfer_rate+0xc/0x40
Aug 9 00:22:13 jawaka kernel: [<c026fbfe>] ide_set_dma+0xe/0x40
Aug 9 00:22:13 jawaka kernel: [<c0266c2d>] set_using_dma+0x8d/0xe0
Aug 9 00:22:13 jawaka kernel: [<c0266ba0>] set_using_dma+0x0/0xe0
Aug 9 00:22:13 jawaka kernel: [<c026797c>] generic_ide_ioctl+0xdc/0x430
Aug 9 00:22:13 jawaka kernel: [<c0273722>] idedisk_ioctl+0xf2/0x120
Aug 9 00:22:13 jawaka kernel: [<c01eb900>] blk_end_sync_rq+0x0/0x30
Aug 9 00:22:13 jawaka kernel: [<c0273672>] idedisk_ioctl+0x42/0x120
Aug 9 00:22:13 jawaka kernel: [<c0273630>] idedisk_ioctl+0x0/0x120
Aug 9 00:22:13 jawaka kernel: [<c01ee194>] blkdev_driver_ioctl+0x54/0x60
Aug 9 00:22:13 jawaka kernel: [<c01ee538>] blkdev_ioctl+0x358/0x7b0
Aug 9 00:22:13 jawaka kernel: [<c02faefb>] _read_unlock_irq+0x1b/0x20
Aug 9 00:22:13 jawaka kernel: [<c0157e7f>] __do_fault+0x15f/0x340
Aug 9 00:22:13 jawaka kernel: [<c0157e23>] __do_fault+0x103/0x340
Aug 9 00:22:13 jawaka kernel: [<c0157e88>] __do_fault+0x168/0x340
Aug 9 00:22:13 jawaka kernel: [<c01160bb>] do_page_fault+0x18b/0x6b0
Aug 9 00:22:13 jawaka kernel: [<c0115ff7>] do_page_fault+0xc7/0x6b0
Aug 9 00:22:13 jawaka kernel: [<c0134384>] up_read+0x14/0x30
Aug 9 00:22:13 jawaka kernel: [<c0190388>] block_ioctl+0x18/0x20
Aug 9 00:22:13 jawaka kernel: [<c0190370>] block_ioctl+0x0/0x20
Aug 9 00:22:13 jawaka kernel: [<c0176e8f>] do_ioctl+0x1f/0x70
Aug 9 00:22:13 jawaka kernel: [<c0176f3c>] vfs_ioctl+0x5c/0x260
Aug 9 00:22:13 jawaka kernel: [<c01771b2>] sys_ioctl+0x72/0x90
Aug 9 00:22:13 jawaka kernel: [<c01040de>] syscall_call+0x7/0xb
Aug 9 00:22:13 jawaka kernel: =======================
Aug 9 00:22:13 jawaka kernel: Linux agpgart interface v0.102
+++++++++++++++++++++++++++++++++
Without the nolapic option the kernel will panic when trying to suspend
to disk. Here are the last lines of the kernel output:
EIP: [<c01127fd> lapic_nmi_suspend+0x1d/0x30 ss:ESP 0068:c1ae3ec8
Kernel panic - not syncing: Attempted to kill init!
Rafael advised me to post directly to the LKML on this issue and so I do.
You can follow the whole discussion with Rafael here:
http://sourceforge.net/mailarchive/forum.php?thread_name=46A9A9A8.2070209%40onlinehome.de&forum_name=suspend-devel
http://sourceforge.net/mailarchive/forum.php?thread_name=200708062038.41452.rjw%40sisk.pl&forum_name=suspend-devel
2. s2ram won't work with kernels > 2.6.18 if the fglrx module is loaded.
Please, don't stone me for using the fglrx driver, without it I couldn't
suspend at all. Unfortunately, I'm stuck to kernel 2.6.18 at the
moment since it's the last kernel that would suspend to ram with the
fglrx module loaded. With more recent kernels the system will hang with
"Suspending console(s)".
3. Even with the 2.6.18 kernel sound won't work after suspending to ram.
I don't know when this started, but I know that this has not been an
issue in the past.
Please, let me know what additional information you might need.
Kind regards,
Felix
next reply other threads:[~2007-08-24 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 12:42 Felix Homann [this message]
2007-09-05 16:36 ` Regressions w.r.t. suspend behaviour in recent kernel versions Andrew Morton
2007-09-05 22:51 ` Felix Homann
2007-09-06 1:01 ` Andrew Morton
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=46CED24F.1020400@onlinehome.de \
--to=fexpop@onlinehome.de \
--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