public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jules Villard <jvillard@ens-lyon.fr>,
	linux-kernel@vger.org, Andrew Morton <akpm@osdl.org>,
	Dave Airlie <airlied@linux.ie>
Subject: Re: Suspend to {mem,disk} broken in 2.6.15-rc6/rc7 on my T42
Date: Tue, 27 Dec 2005 11:00:18 +1100	[thread overview]
Message-ID: <1135641618.4780.3.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0512261545460.14098@g5.osdl.org>

On Mon, 2005-12-26 at 15:55 -0800, Linus Torvalds wrote:
> 
> On Mon, 26 Dec 2005, Jules Villard wrote:
> > 
> > Please find my .config and the lspci output attached (my graphic card
> > is a AGP plugged ATI Radeon Mobility 7500 and I use the "radeon"
> > driver from xorg).
> 
> Ok, from the sysrq-T stuff it _looks_ like X is just busy-looping in user 
> space. So it's probably some disagreement between radeonfb and X.org
> 
> The fact that everything was ok in -rc5 would imply that it's likely one 
> of the radeon aperture size issue patches.
> 
> > Investigating a bit further, I found out that resume is quite innocent
> > about all this: what hangs X is switching from a vt to X.
> 
> I'm cc'ing BenH and DaveA, but in the meantime, while waiting for the 
> professionals, can you try to revert the two attachments (revert "diff-1" 
> first, try that, and revert "diff-2" after that if it didn't start 
> working after the first revert).

Also, does it work if you don't use radeonfb ? radeonfb shouldn't touch
MC_AGP_LOCATION and the DRM change only affects that, so I'm a bit
surprised.

Ben.


  reply	other threads:[~2005-12-27  1:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 19:45 Suspend to {mem,disk} broken in 2.6.15-rc6/rc7 on my T42 Jules Villard
     [not found] ` <Pine.LNX.4.64.0512261201360.14098@g5.osdl.org>
2005-12-26 21:23   ` Jules Villard
2005-12-27  2:58     ` Marc Koschewski
2005-12-27  3:02       ` Marc Koschewski
2005-12-26 23:55 ` Linus Torvalds
2005-12-27  0:00   ` Benjamin Herrenschmidt [this message]
2005-12-27  1:20     ` Jules Villard
2005-12-27  1:27       ` Benjamin Herrenschmidt
2005-12-27 12:55         ` Jules Villard
2005-12-27 23:26           ` Benjamin Herrenschmidt
2005-12-28  6:16           ` Benjamin Herrenschmidt
2005-12-28 21:49             ` Linus Torvalds
2005-12-28 23:14               ` Benjamin Herrenschmidt
2005-12-27  1:19   ` Jules Villard
2005-12-27  1:27     ` Benjamin Herrenschmidt
2005-12-27  1:49   ` Benjamin Herrenschmidt
2005-12-27 12:14     ` Jules Villard

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=1135641618.4780.3.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=airlied@linux.ie \
    --cc=akpm@osdl.org \
    --cc=jvillard@ens-lyon.fr \
    --cc=linux-kernel@vger.org \
    --cc=torvalds@osdl.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