From: Lion Vollnhals <webmaster@schiggl.de>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swsusp: properly suspend and resume *all* devices
Date: Wed, 05 Jan 2005 16:57:36 +0100 [thread overview]
Message-ID: <41DC0E70.4000005@schiggl.de> (raw)
In-Reply-To: <20050104214315.GB1520@elf.ucw.cz>
>>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 (as I
>>assume from the hung machine and blinking CAPS LOCK), which didn't happen
>>previously (2.6.9, 2.6.8.1, ...). I also see lots of
>>
>>drivers/usb/input/hid-core.c: input irq status -84 received
>>
>>until I do a 'rmmod uhci_hcd; modprobe uhci_hcd'. This used to happen with 2.6.9
>>as well, but the system would recover after about 20 messages or so like this
>>after a resume.
>>
>>Any suggestions about where to look to track this down?
>
>
> Check if 3c59x has suspend/resume support. If not, add it.
>
> Panic... we really need to know why it panicked. VESAFB does not
> support blanking, just switch to VESAFB and you should be able to see
> the messages.
> Pavel
I have a problem with net-devices, ne2000 in particular, in 2.6.9 and
2.6.10, too. After a resume the ne2000-device doesn't work anymore. I
have to restart it using the initscripts.
How do I add suspend/resume support (to ISA devices, like my ne2000)?
Can you point me to some information/tutorial?
Lion Vollnhals
next prev parent reply other threads:[~2005-01-05 16:04 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 ` 2.6.10 suspend/resume bustage (was Re: [PATCH] swsusp: properly suspend and resume *all* devices) Martin Lucina
2005-01-04 21:43 ` [PATCH] swsusp: properly suspend and resume *all* devices Pavel Machek
2005-01-05 15:57 ` Lion Vollnhals [this message]
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=41DC0E70.4000005@schiggl.de \
--to=webmaster@schiggl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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).