All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 22 Feb 2007 15:52:11 +0200	[thread overview]
Message-ID: <200702221552.14491.caglar@pardus.org.tr> (raw)
In-Reply-To: <1172151671.4306.13.camel@daplas>

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

Hi;

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.

> After grepping for change_console, all callers of change_console and
> complete_change_console are acquiring the console semaphore, so I really
> don't know what's going on here...
>
> Since you are using a non-vanilla kernel, can you just do
> a grep change_console of the kernel source and see if you can find a
> caller that missed doing an acquire_console_sem().

fbsplash and vesafb-tng has no change_console call and patched one seems same 
with vanilla one.

[caglar@zangetsu][~/svk/playground/caglar/kernel/kernel/files/gentoo]> grep 
change_console fbsplash-0.9.2-r5.patch
[caglar@zangetsu][~/svk/playground/caglar/kernel/kernel/files/gentoo]> grep 
change_console vesafb-tng-1.0-rc2.patch
[caglar@zangetsu][~/svk/playground/caglar/kernel/kernel/files/gentoo]>

zangetsu linux-2.6.20 # grep change_console *  -r
drivers/char/vt_ioctl.c:static void complete_change_console(struct vc_data 
*vc);
drivers/char/vt_ioctl.c:                                
complete_change_console(vc_cons[newvt].d);
drivers/char/vt_ioctl.c:static void complete_change_console(struct vc_data 
*vc)
drivers/char/vt_ioctl.c:         * clean up (similar to logic employed in 
change_console())
drivers/char/vt_ioctl.c:void change_console(struct vc_data *new_vc)
drivers/char/vt_ioctl.c:        complete_change_console(new_vc);
drivers/char/vt.c:                      
change_console(vc_cons[want_console].d);
include/linux/vt_kern.h:void change_console(struct vc_data *new_vc);

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 --]

  reply	other threads:[~2007-02-22 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09  6:38 [BUG] at drivers/char/vt.c:3332 do_blank_screen() on resume 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 [this message]
2007-02-28 12:10               ` S.Çağlar Onur
2007-02-15 10:58 S.Çağlar Onur

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=200702221552.14491.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.