From: Nigel Cunningham <ncunningham@cyclades.com>
To: mhf@berlios.de,
FrameBuffer Devel <linux-fbdev-devel@lists.sourceforge.net>
Cc: SoftwareSuspend Development
<softwaresuspend-devel@lists.berlios.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
pavel@suse.cz, akpm@osdl.org
Subject: Re: i810 BUG summary. Was Re: [SoftwareSuspend-devel] [Announce] 2.1.7 for 2.6.11-rc4
Date: Thu, 17 Feb 2005 15:39:25 +1100 [thread overview]
Message-ID: <1108615165.4471.13.camel@desktop.cunningham.myip.net.au> (raw)
In-Reply-To: <42141C01.nail5A31PHQ9L@berlios.de>
Hi Michael.
Perhaps this belongs with the framebuffer devel guys? I'll copy them
now. Antonio et al, have I called it right?
Regards,
Nigel
On Thu, 2005-02-17 at 15:22, mhf@berlios.de wrote:
> Hi Nigel!
>
> On Wednesday 16 February 2005 05:22, Nigel Cunningham wrote:
> > Hi Michael.
> >
> > On Tue, 2005-02-15 at 22:32, mhf@berlios.de wrote:
> > > - Removing intel-agp as well fixes the problem and X
> > > can be started alright after resume.
> >
> > Did you see Karol's patch? It looks like it should
> > improve your situation.
>
> It did :-)
>
> >
> > Did you get any joy out of the posting to LKML?
> >
>
> Yes, Andrew suggested privately thqt screen should come back
> as prior to S3 and Pavel sees the setfont issue as a bug.
>
> 2.6.11-rc4 i810 bugs:
>
> 1) Screen comes back in 25 line mode but scroll remains at
> last set linecount. (also on all other displays tested like
> savage or sis or via.
>
> 2) setfont dies on resume from S3.
>
> 3) A scroll problem in console mode with gentoo portage and
> likely othe apps which scroll lines of random length
>
> 4) With X wo DRM random colored bands flash over the screen
> when running some programs and shellscripts as if it would
> send the data bus instead of video data to the DAC. A
> swsusp2 cycles fixes it until the next S3 cycle.
>
> 5) Then DRM (20050211 snapshot) dies on resume.
>
> Guess it's time to find an i810 datasheet and go digging.
>
> Otherwise, No issues seen wrt swsusp 2.1.7 on 2.6.11-rc4.
>
> Good news is that S3 seems to be quite stable also when
> interleaved with swsusp2. There were no failures.
>
> Lastly, I'd like to see the ACPI alarm function work to do
> stress testing in a loop:
>
> 1) set alarm to current time + xx sec
> 2) enter S3 or S4/swsusp2
> 3) on resume triggered by alarm continue from step 1.
>
> Regards
> Michael
--
Nigel Cunningham
Software Engineer, Canberra, Australia
http://www.cyclades.com
Ph: +61 (2) 6292 8028 Mob: +61 (417) 100 574
next prev parent reply other threads:[~2005-02-17 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 4:22 mhf
2005-02-17 4:39 ` Nigel Cunningham [this message]
2005-02-17 12:09 ` [Linux-fbdev-devel] " Antonino A. Daplas
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=1108615165.4471.13.camel@desktop.cunningham.myip.net.au \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@berlios.de \
--cc=pavel@suse.cz \
--cc=softwaresuspend-devel@lists.berlios.de \
/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
all inboxes | Powered by JetHome®