From: Matthias Hentges <mailinglisten@hentges.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines
Date: Mon, 22 Nov 2004 05:34:17 +0100 [thread overview]
Message-ID: <1101098057.4589.2.camel@mhcln03> (raw)
In-Reply-To: <1101073197.3796.72.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
Am Montag, den 22.11.2004, 08:39 +1100 schrieb Benjamin Herrenschmidt:
> That "update only what changed" makes little sense
Sorry, I was merely stating my observations.
> ... can you send me
> the lspci state of the Intel bridge before you try to resume it ? I
> suspect our pci_restore_state() should be smarter, that is check if
> something changed (a BAR), if yes, switch mem/io off, restore the BARs,
> then switch mem/io back on...
Attached.
Thanks!
--
Matthias Hentges
Cologne / Germany
[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4 -> No files, no URL's
My OS: Debian SID. Geek by Nature, Linux by Choice
[-- Attachment #2: dmesg.txt.gz --]
[-- Type: application/x-gzip, Size: 4589 bytes --]
[-- Attachment #3: kernel.config.gz --]
[-- Type: application/x-gzip, Size: 6322 bytes --]
[-- Attachment #4: lspci-vvvxxx_after_restoring_PCI.txt.gz --]
[-- Type: application/x-gzip, Size: 3424 bytes --]
[-- Attachment #5: lspci-vvvxxx_after_resuming.txt.gz --]
[-- Type: application/x-gzip, Size: 3384 bytes --]
[-- Attachment #6: lspci-vvvxxx_before_suspending.txt.gz --]
[-- Type: application/x-gzip, Size: 3468 bytes --]
[-- Attachment #7: proc_interrupts.txt --]
[-- Type: text/plain, Size: 406 bytes --]
CPU0
0: 411306 XT-PIC timer
1: 510 XT-PIC i8042
2: 0 XT-PIC cascade
4: 8 XT-PIC serial
5: 1385 XT-PIC eth0
9: 9 XT-PIC acpi
12: 803 XT-PIC i8042
14: 2036 XT-PIC ide0
15: 21 XT-PIC ide1
NMI: 0
ERR: 0
next prev parent reply other threads:[~2004-11-22 4:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 21:05 pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines Matthias Hentges
2004-11-19 11:55 ` Pavel Machek
2004-11-19 13:56 ` Matthias Hentges
2004-11-19 23:06 ` Benjamin Herrenschmidt
2004-11-20 2:43 ` Matthew Garrett
2004-11-20 3:36 ` Matthias Hentges
2004-11-20 7:34 ` Benjamin Herrenschmidt
2004-11-20 8:01 ` Matthias Hentges
2004-11-20 22:27 ` Benjamin Herrenschmidt
2004-11-21 8:50 ` Matthias Hentges
2004-11-21 21:39 ` Benjamin Herrenschmidt
2004-11-22 4:34 ` Matthias Hentges [this message]
2004-11-22 4:52 ` Benjamin Herrenschmidt
2004-11-20 7:33 ` Benjamin Herrenschmidt
2004-11-20 22:29 ` Pavel Machek
2004-11-19 11:56 ` Pavel Machek
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=1101098057.4589.2.camel@mhcln03 \
--to=mailinglisten@hentges.net \
--cc=benh@kernel.crashing.org \
--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).