From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: stefandoesinger-RbZlAiThDcE@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: pci device resume too early?
Date: Wed, 28 Jul 2004 22:59:24 +0100 [thread overview]
Message-ID: <1091051965.4300.1.camel@tyrosine> (raw)
In-Reply-To: <200407282118.52624.stefandoesinger-RbZlAiThDcE@public.gmane.org>
On Wed, 2004-07-28 at 21:18 +0200, Stefan Dösinger wrote:
> Can you try if this helps your yenta?
Hmm. Sadly not. If pci_restore_state is called on my yenta, every other
character of the next printk is missing and then the machine hangs. I'm
at something of a loss as to why it does this...
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&op=click
next prev parent reply other threads:[~2004-07-28 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 17:53 pci device resume too early? Stefan Dösinger
[not found] ` <200407281953.39159.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-07-28 18:14 ` Matthew Garrett
[not found] ` <1091038485.15464.9.camel-myFlNLNQP+Q@public.gmane.org>
2004-07-28 19:18 ` Stefan Dösinger
[not found] ` <200407282118.52624.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-07-28 21:06 ` Luca
[not found] ` <20040728210602.GA26087-sTXFmx6KbOnUXq0IF5SVAZ4oGUkBHcCu@public.gmane.org>
2004-07-29 15:04 ` Stefan Dösinger
2004-08-04 18:47 ` Stefan Dösinger
2004-07-28 21:59 ` Matthew Garrett [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-29 0:48 Li, Shaohua
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=1091051965.4300.1.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=stefandoesinger-RbZlAiThDcE@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