From: Matthew Garrett <mjg59@srcf.ucam.org>
To: linux-kernel@vger.kernel.org
Subject: yenta_socket dies on rewriting configuration registers
Date: Sat, 03 Jul 2004 16:58:16 +0100 [thread overview]
Message-ID: <1088870296.3733.29.camel@tyrosine> (raw)
Running 2.6.7 on a Thinkpad 240X, if I allow the PCI registers on my
cardbus bridge to be rewritten after ACPI resume, the system dies with
slightly strange symptoms. Every other character of kernel messages is
written, with blank spaces in between. After a few lines of message, the
system stops. If I do a resume with an unpatched kernel, it appears to
get through to thawing processes before hanging - if I put debug
statements in the resume path, it hangs within device_resume. I get this
behaviour even if the yenta_socket driver is not loaded due to the
generic 2.6.7 resume code. Commenting out both calls to
pci_restore_state (from the driver itself and from the generic PCI code)
results in suspend working correctly. The bridge is a Texas Instruments
PCI1211.
The driver works correctly with my Thinkpad X40, which has a Ricoh
RL5c476 II
--
Matthew Garrett | mjg59@srcf.ucam.org
reply other threads:[~2004-07-03 15:58 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=1088870296.3733.29.camel@tyrosine \
--to=mjg59@srcf.ucam.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