From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_VGACON_SOFT_SCROLLBACK crashes 2.6.17
Date: Thu, 22 Jun 2006 08:47:27 +0800 [thread overview]
Message-ID: <4499E89F.6030509@gmail.com> (raw)
In-Reply-To: <200606220005.32446.a1426z@gawab.com>
Al Boldi wrote:
> Antonino A. Daplas wrote:
>> Al Boldi wrote:
>>> Enabling CONFIG_VGACON_SOFT_SCROLLBACK causes random fatal system
>>> freezes.
>>>
>>> Especially, ping 10.1 -A easily causes a complete system hang during
>>> scroll.
>>>
>>> Is there an easy way to fix this, other than disabling the option?
>> I can't duplicate your problem. Did it ever work before?
>
> This option did not exist before 2.6.17.
I meant if you tried any of the -rc kernels.
Anyway, can you try the patch below. It's a debugging patch and
it will slow down the console.
If the system hang disappears, remove the line
while (i--);
in include/linux/vt_buffer.h. This line is introduced by
the patch below.
Let me know at what point it worked, or whether it worked at all.
>
>> Can you send me you kernel config?
>
> Attached below.
>
> BTW, is there any chance to patch your savagefb to support VIA/S3 UniChrome?
>
If someone posts a patch to lkml or fbdev-devel, why not? But a separate
driver is probably better as the 2 are very different.
Tony
diff --git a/include/linux/vt_buffer.h b/include/linux/vt_buffer.h
index 057db7d..e9b6064 100644
--- a/include/linux/vt_buffer.h
+++ b/include/linux/vt_buffer.h
@@ -20,11 +20,21 @@ #endif
#ifndef VT_BUF_HAVE_RW
#define scr_writew(val, addr) (*(addr) = (val))
-#define scr_readw(addr) (*(addr))
-#define scr_memcpyw(d, s, c) memcpy(d, s, c)
-#define scr_memmovew(d, s, c) memmove(d, s, c)
-#define VT_BUF_HAVE_MEMCPYW
-#define VT_BUF_HAVE_MEMMOVEW
+//#define scr_readw(addr) (*(addr))
+
+static inline u16 scr_readw(volatile const u16 *addr)
+{
+ int i = 10000;
+ u16 val = *addr;
+
+ while (i--);
+ return val;
+}
+
+//#define scr_memcpyw(d, s, c) memcpy(d, s, c)
+//#define scr_memmovew(d, s, c) memmove(d, s, c)
+#undef VT_BUF_HAVE_MEMCPYW
+#undef VT_BUF_HAVE_MEMMOVEW
#endif
#ifndef VT_BUF_HAVE_MEMSETW
next prev parent reply other threads:[~2006-06-22 0:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 14:15 CONFIG_VGACON_SOFT_SCROLLBACK crashes 2.6.17 Al Boldi
2006-06-21 15:18 ` Antonino A. Daplas
2006-06-21 21:05 ` Al Boldi
2006-06-22 0:47 ` Antonino A. Daplas [this message]
2006-06-22 6:32 ` Antonio Vargas
2006-06-22 10:37 ` Antonino A. Daplas
2006-06-22 17:36 ` Al Boldi
2006-06-22 18:08 ` Antonino A. Daplas
2006-06-23 13:25 ` Al Boldi
2006-06-23 14:38 ` Antonino A. Daplas
2006-06-22 19:19 ` Randy.Dunlap
2006-06-23 13:25 ` Al Boldi
[not found] <fa.RonUKQ4bRxV1BEEAvvcvwPKcfXM@ifi.uio.no>
[not found] ` <fa.xi8WlIQLoSpgs6byyFeCFmlTjCE@ifi.uio.no>
2006-06-22 14:24 ` Robert Hancock
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=4499E89F.6030509@gmail.com \
--to=adaplas@gmail.com \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.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.