From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: yenta_socket: no PCI interrupts after resume if intel-agp loaded on HP 1105
Date: Tue, 07 Jun 2005 12:56:33 +0100 [thread overview]
Message-ID: <1118145393.6648.232.camel@tyrosine> (raw)
If I boot a kernel without any modules loaded and then load intel-agp, I
can successfully suspend and resume this machine via ACPI. However, the
b44 module is then unable to determine its MAC address correctly, and
ipw2100 claims that it can't find a device. yenta_socket gives
Yenta : Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:06.0, mfunc 0x00001000, devctl 0x66
Yenta TI: socket 0000:02:06.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:02:06.0 falling back to parallel PCI interrupts
Yenta TI: socket 0000:02:06.0 no PCI interrupts. Fish. Please report.
The only output from the AGP driver is:
agpgart: Detected an Intel 855PM Chipset.
agpgart: AGP aperture is 32M @ 0xe2000000
If I have all of these drivers loaded at suspend, resume fails. Without
intel-agp, I can suspend and resume happily (well, X won't start after
resume, but that's potentially an entirely separate issue)
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
reply other threads:[~2005-06-07 11:56 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=1118145393.6648.232.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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