pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

Post by Matthias H » Sat, 20 Nov 2004 23:10:06


Am Freitag, den 19.11.2004, 12:55 +0100 schrieb Pavel Machek:

Heh, well no. Video is as dead as it can get :\ No known trick revives
it after a resume . But at least the machine doesn't freeze after S3.



Of course it is :) It's more a proof--concept that pci-resume is
indeed causing the problem. I have no idea how to debug this any
further. In the meantime this patch works for me.


Sorry, that's beyond my abilities. That's why I'm posting here. I'm not
even sure that it's the radeon which is acting up here.
--
Matthias Hentges
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4 -> No files, no URL's

My OS: Debian SID. Geek by Nature, Linux by Choice

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

Post by Benjamin H » Sun, 21 Nov 2004 08:20:11


Have you tried with radeonfb in your kernel config ?

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/

 
 
 

pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

Post by Matthias H » Sun, 21 Nov 2004 13:00:11

Am Samstag, den 20.11.2004, 02:43 +0000 schrieb Matthew Garrett:


Trying to resume with radeonfb or X (DRI or fglrx) causes the machine
to freeze upon a resume.
--
Matthias Hentges
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4 -> No files, no URL's

My OS: Debian SID. Geek by Nature, Linux by Choice

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

Post by Benjamin H » Sun, 21 Nov 2004 16:40:07


Bullshit...

Well... In an ideal world, the video chip would come up all back by
itself and nobody would have to care... unfortunately we aren't in an
ideal world.

With the way video cards are evolving, we'll soon have no choice but
have a kernel driver bring the chip back. Userspace has nothing to do
with that, and userspace & kernel aren't fighting over it.

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

Post by Benjamin H » Sun, 21 Nov 2004 16:40:08


At what point does it freeze ? Is the display back before the freeze ?

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

Post by Matthias H » Sun, 21 Nov 2004 17:10:08


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
Am Samstag, den 20.11.2004, 18:34 +1100 schrieb Benjamin Herrenschmidt:



[...]


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?

Thanks
--
Matthias Hentges
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4 -> No files, no URL's

My OS: Debian SID. Geek by Nature, Linux by Choice
 
 
 

pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

Post by Benjamin H » Mon, 22 Nov 2004 07:30:19


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 XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

Post by Benjamin H » Tue, 23 Nov 2004 06:50:07


That "update only what changed" makes little sense ... can you send me
the lspci state of the Intel bridge before you try to resume it ? I
suspect our pci_restore_state() should be smarter, that is check if
something changed (a BAR), if yes, switch mem/io off, restore the BARs,
then switch mem/io back on...

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines

Post by Benjamin H » Tue, 23 Nov 2004 14:00:19


Ok, it's clearly visible that your CPU->AGP bridge isn't properly
restored. I can't tell if the "default" resume code is enough tho, but
it's fairly probably that this isn't the only problem, and that the
video chip itself isn't restored neither...

I don't think the default resume code is to blame here, though the CPU
to AGP bridge may need some special restore code restoring more than
just it's config space (very probable even). I suspect there is some
ACPI trickery here that should be happening and isn't but my knowledge
of ACPI isn't that great.

Once the config space is resumed, I suppose doing a soft-boot of the
card with the BIOS would work, but then, that means preventing anything
from actually touching the video card until that happens...

Ben.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/