From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Kevin Fenzi <kevin-linux-kernel@scrye.com>
Cc: linux-kernel@vger.kernel.org, pavel@ucw.cz
Subject: Re: FYI: my current bigdiff
Date: Fri, 10 Sep 2004 16:46:01 -0600 [thread overview]
Message-ID: <200409101646.01558.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20040910041320.DF700E7504@voldemort.scrye.com>
On Thursday 09 September 2004 10:13 pm, Kevin Fenzi wrote:
> First suspend worked.
> First resume came back, but all kinds of problems with my network,
> with my usb, and with sound.
> ...
> After booting with the pci=routeirq as suggested wireless and usb
> played nice on suspend resume again.
Yes, I've had a couple other reports of this, but haven't made any
progress on tracking it down yet. (The other reports were from
vanilla -mm kernels, so I don't think it's related to Pavel's patch.)
I'm completely ignorant about how swsusp works; I guess this is my
chance to learn. "pci=routeirq" just causes us to do all the PCI
ACPI IRQ routing at boot-time, before the drivers start up. This
happens in pci_acpi_init(), which is a subsys_initcall that is run
at initial boot-time, but (I assume) not during a resume.
- Can you confirm that your USB and prism drivers were loaded
and working fine before the suspend?
- Could you post the whole dmesg log, including the part from
boot to suspend, and also the part after resume? I'd like
to see these both with and without "pci=routeirq" to see if
there's some meaningful difference.
- Can you capture the contents of /proc/interrupts before the
suspend?
Thanks for the problem report.
next prev parent reply other threads:[~2004-09-10 22:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 13:44 Pavel Machek
2004-09-10 4:13 ` Kevin Fenzi
2004-09-10 9:44 ` Pavel Machek
2004-09-10 17:27 ` Kevin Fenzi
2004-09-10 22:46 ` Bjorn Helgaas [this message]
2004-09-11 16:41 ` Stefan Seyfried
2004-09-11 18:55 ` Kevin Fenzi
2004-09-11 18:50 ` Kevin Fenzi
2004-09-13 22:06 ` Bjorn Helgaas
2004-09-12 8:54 ` Stefan Schweizer
2004-09-12 9:23 ` Stefan Seyfried
2004-09-12 9:32 ` Stefan Schweizer
2004-09-12 11:39 ` Stefan Seyfried
2004-09-12 21:03 ` 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=200409101646.01558.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=kevin-linux-kernel@scrye.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®