From: Tako Schotanus <quintesse@palacio-cristal.com>
To: linux-acpi@vger.kernel.org
Subject: PCI: Cannot allocate resource region messages on resume after hibernate
Date: Mon, 06 Feb 2006 16:41:09 +0100 [thread overview]
Message-ID: <43E76E15.9070601@palacio-cristal.com> (raw)
Hi,
I sent a similar message some days ago to the swsusp2 mailing list and
it's maintainer told me to try here.
What I wanted to know is if anybody knows what could be wrong if after
every suspend (either from KDE or from runlevel 3) the resume freezes
showing several lines of "PCI: Cannot allocate resource region" with
some numbers and a couple of other lines saying something about
"resource collisions".
They appear immediately after the kernel info but before the swsusp2
message about restoring the kernel. The system never wakes up though.
The strange thing is that after rebooting/resetting it again it _will_
continue resuming without errors..
The pci messages never appear during a "normal" boot sequence.
Does anybody have any idea what could be wrong? Or what information
should I provide to be able to figure this out?
Cheers,
-Tako
reply other threads:[~2006-02-06 15:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43E76E15.9070601@palacio-cristal.com \
--to=quintesse@palacio-cristal.com \
--cc=linux-acpi@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