Messages in this thread | | | Subject | Re: pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines | From | Benjamin Herrenschmidt <> | Date | Sun, 21 Nov 2004 09:27:17 +1100 |
| |
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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |