From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthias Hentges <mailinglisten@hentges.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines
Date: Sun, 21 Nov 2004 09:27:17 +1100 [thread overview]
Message-ID: <1100989638.3796.9.camel@gaston> (raw)
In-Reply-To: <1100937706.3497.11.camel@mhcln03>
On Sat, 2004-11-20 at 09:01 +0100, Matthias Hentges wrote:
> Am Samstag, den 20.11.2004, 18:34 +1100 schrieb Benjamin Herrenschmidt:
> > On Sat, 2004-11-20 at 04:36 +0100, Matthias Hentges wrote:
> > > Am Samstag, den 20.11.2004, 02:43 +0000 schrieb Matthew Garrett:
> > > > Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> > > >
>
> [...]
>
> > > Trying to resume with radeonfb or X (DRI or fglrx) causes the machine
> > > to freeze upon a resume.
> >
> > At what point does it freeze ? Is the display back before the freeze ?
>
> Sadly the video *never* comes back and stays dark no matter what I try:
> - boot-radeon (int10 POST call) doesn't work. Either it segfaults or
> it hangs the machine
> - Any combination of radeontool light on|off doesn't help (no freeze,
> sometimes it
> can't read the cards mem address??)
> - The int10 radeon patch for X11 doesn't help (freeze)
> - radeonfb and / or X (either patched w/ int10 or not) freeze the
> machine
>
> I'm running out of ideas with this darn thing.
> Since the serial port doesn't come back from S3 either, even a serial
> console is of no help.
>
> I have attached the output of lspci -vvv before and after resuming from
> S3
> The latter shows lots of "[disabled]" entries. Is that of any use?
Difficult to say at this point, the [disabled] thing are easy fixed with
a pci_enable_device(). Unfortunately, on some machines, the firmware
sort-of expects the kenrel driver to reboot the card from scratch...
Ben.
next prev parent reply other threads:[~2004-11-20 22:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 21:05 pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines Matthias Hentges
2004-11-19 11:55 ` Pavel Machek
2004-11-19 13:56 ` Matthias Hentges
2004-11-19 23:06 ` Benjamin Herrenschmidt
2004-11-20 2:43 ` Matthew Garrett
2004-11-20 3:36 ` Matthias Hentges
2004-11-20 7:34 ` Benjamin Herrenschmidt
2004-11-20 8:01 ` Matthias Hentges
2004-11-20 22:27 ` Benjamin Herrenschmidt [this message]
2004-11-21 8:50 ` Matthias Hentges
2004-11-21 21:39 ` Benjamin Herrenschmidt
2004-11-22 4:34 ` Matthias Hentges
2004-11-22 4:52 ` Benjamin Herrenschmidt
2004-11-20 7:33 ` Benjamin Herrenschmidt
2004-11-20 22:29 ` Pavel Machek
2004-11-19 11:56 ` 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=1100989638.3796.9.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailinglisten@hentges.net \
/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;
as well as URLs for NNTP newsgroup(s).