From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pavel Machek <pavel@ucw.cz>, lkml <linux-kernel@vger.kernel.org>,
spock@gentoo.org
Subject: Re: [BUG] at drivers/char/vt.c:3332 do_blank_screen() on resume
Date: Wed, 28 Feb 2007 14:10:00 +0200 [thread overview]
Message-ID: <200702281410.04196.caglar@pardus.org.tr> (raw)
In-Reply-To: <200702221552.14491.caglar@pardus.org.tr>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
22 Şub 2007 Per tarihinde, S.Çağlar Onur şunları yazmıştı:
> 22 Şub 2007 Per tarihinde, Antonino A. Daplas şunları yazmıştı:
> > Ah, and you have fb_splash too. That's why the tracing was not what I
> > expected it to be.
> >
> > Try using video=vesafb:noblank to disable hardware blanking and find out
> > if you can still reproduce the oops.
>
> I'll try and also will try to reproduce with vanilla one.
Sorry for long delay, here are some more test results;
* using video=vesafb:noblank _sometimes_ causes hard freezes on resume, and
_sometimes_ X can't start properly (it enters a weird "switch vt1 - wait for
some seconds - switch vt7" loop and after ~10 minutes X starts magically!)
whenever this happens system starts to become really unresponsive and dmesg
and Xorg's logs shows nothing strange :(. I will try an older kernel with
noblank to see its related or not.
* If system resumes normally with noblank (it can sometimes :)), dmesg shows
no error at all, X starts normally and system works well.
* I cannot reproduce that BUG with _vanilla one_ but please note that i cannot
easily reproduce that with patched one also (it occurs only once for ~20
suspend2disk/resume cycle)
I'll try to test more and trying to reproduce, if i can find anything else
i'll knock your door again :)
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-02-28 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 6:38 S.Çağlar Onur
2007-02-15 10:40 ` Pavel Machek
2007-02-15 10:56 ` Andrew Morton
2007-02-15 11:00 ` S.Çağlar Onur
2007-02-21 23:43 ` Antonino A. Daplas
2007-02-22 12:53 ` S.Çağlar Onur
2007-02-22 13:41 ` Antonino A. Daplas
2007-02-22 13:52 ` S.Çağlar Onur
2007-02-28 12:10 ` S.Çağlar Onur [this message]
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=200702281410.04196.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=spock@gentoo.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
Powered by JetHome