From: Martin Lucina <mato@kotelna.sk>
To: linux-kernel@vger.kernel.org
Subject: 2.6.10 suspend/resume bustage (was Re: [PATCH] swsusp: properly suspend and resume *all* devices)
Date: Tue, 4 Jan 2005 10:30:11 +0000 (UTC) [thread overview]
Message-ID: <loom.20050104T112419-883@post.gmane.org> (raw)
In-Reply-To: loom.20050104T093741-631@post.gmane.org
> Obviously, I don't get the APIC errors, but everything else is the same, random
> devices fail and need to be reloaded (3c59x and uhci-hcd in particular), plus
> the system appears to panic somewhere along the way to resume occasionally
...[panic] and suspend, as I just found out.
I just tried pci=routeirq here, doesn't help.
Another thing I'm seeing sometimes on resume is that the last key pressed on the
keyboard appears to be "stuck". This laptop has a function to ask for a password
on powerup/resume, which presumably is done by the BIOS while in SMM. Since the
last key pressed is ENTER, and I tend to resume into X with an XTerm window
focused, I see the ENTER keypress being repeated for ever, until I hit ENTER
again.
I haven't seen this in any other kernel version, so I'm just mentioning it here
in case it might be relevant.
-mato
next prev parent reply other threads:[~2005-01-04 10:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 14:47 2.6.10: e100 network broken after swsusp/resume John M Flinchbaugh
2004-12-28 21:25 ` Håkan Lindqvist
2005-01-01 23:41 ` Eduard Bloch
2005-01-01 17:23 ` Pavel Machek
2005-01-01 22:17 ` John M Flinchbaugh
2005-01-01 22:52 ` Pavel Machek
2005-01-01 23:14 ` Matthew Garrett
2005-01-02 3:46 ` Barry K. Nathan
2005-01-02 5:57 ` Barry K. Nathan
2005-01-02 18:42 ` John M Flinchbaugh
2005-01-02 20:09 ` Håkan Lindqvist
2005-01-03 5:10 ` Barry K. Nathan
2005-01-03 8:31 ` Barry K. Nathan
2005-01-03 8:53 ` Pavel Machek
2005-01-03 8:47 ` Pavel Machek
2005-01-03 10:14 ` Barry K. Nathan
2005-01-03 15:05 ` [PATCH] swsusp: properly suspend and resume *all* devices Barry K. Nathan
2005-01-03 17:08 ` Pavel Machek
2005-01-03 18:33 ` Pavel Machek
2005-01-04 5:15 ` Barry K. Nathan
2005-01-04 5:18 ` Barry K. Nathan
2005-01-04 8:44 ` Martin Lucina
2005-01-04 10:30 ` Martin Lucina [this message]
2005-01-04 21:43 ` Pavel Machek
2005-01-05 15:57 ` Lion Vollnhals
2005-01-06 22:29 ` Pavel Machek
2005-01-07 13:47 ` Takashi Iwai
2005-01-07 13:54 ` Pavel Machek
2005-01-07 14:48 ` Dmitry Torokhov
2005-01-07 15:35 ` Vojtech Pavlik
2005-01-07 15:59 ` Lion Vollnhals
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=loom.20050104T112419-883@post.gmane.org \
--to=mato@kotelna.sk \
--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).