From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>,
Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: swsusp: kill crash when too much memory is free
Date: Sat, 11 Sep 2004 21:22:24 +0200 [thread overview]
Message-ID: <200409112122.24194.rjw@sisk.pl> (raw)
In-Reply-To: <200409111150.28457.rjw@sisk.pl>
On Saturday 11 of September 2004 11:50, Rafael J. Wysocki wrote:
> On Saturday 11 of September 2004 00:29, Pavel Machek wrote:
[- snip -]
>
> However, I think the problem is with the hardware, not with the driver: if
the
> sound driver is unloaded before suspend and loaded again after resume, the
> box behaves as though it were loaded all the time (ie IRQ #5 goes mad). Are
> there any boot options that may help get around this?
Some good news here. :-)
If the kernel is booted with pci=routeirq and nmi_watchdog=0, almost all of
the problems that I had with swsusp "magically" disappear.
One issue that remains is a USB-related crash (trace available at:
http://www.sisk.pl/kernel/040911/swsusp-usb-trace.log), which does not
prevent the box from waking up (as you can see in the trace), but requires
the ohci_hcd module to be reloaded. I have got rid of it by compiling the
USB drivers into the kernel.
The second remaining "thing" is that the network interface on eth0 (sk98lin)
does not come up properly after resume and I have to restart networking to
make it work, but this is a non-issue.
Thanks a lot for your help, and if I can do something for you (like testing
new code etc.), please let me know.
Greets,
RJW
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next prev parent reply other threads:[~2004-09-11 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 15:42 swsusp: kill crash when too much memory is free Pavel Machek
2004-09-09 22:01 ` Rafael J. Wysocki
2004-09-10 9:40 ` Pavel Machek
2004-09-10 10:45 ` Rafael J. Wysocki
2004-09-10 17:26 ` Rafael J. Wysocki
2004-09-10 22:29 ` Pavel Machek
2004-09-11 9:50 ` Rafael J. Wysocki
2004-09-11 19:22 ` Rafael J. Wysocki [this message]
2004-09-11 21:59 ` Rafael J. Wysocki
2004-09-12 10:32 ` swsusp (2.6.9-rc1-mm4 + bigdiff): Unable to handle kernel paging request Rafael J. Wysocki
2004-09-12 20:42 ` swsusp: kill crash when too much memory is free Pavel Machek
2004-09-12 21:16 ` Rafael J. Wysocki
2004-09-12 21:40 ` Stefan Seyfried
2004-09-12 22:23 ` Rafael J. Wysocki
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=200409112122.24194.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=pavel@ucw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.