From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Tero Roponen <teanropo@jyu.fi>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: tty-related oops in latest kernel(s)?
Date: Thu, 31 May 2007 07:17:27 +0800 [thread overview]
Message-ID: <1180567047.4570.18.camel@daplas> (raw)
In-Reply-To: <Pine.LNX.4.64.0705301857370.29485@jalava.cc.jyu.fi>
On Wed, 2007-05-30 at 19:01 +0300, Tero Roponen wrote:
> On Wed, 30 May 2007, Andrew Morton wrote:
>
> > On Wed, 30 May 2007 15:02:49 +0300 (EEST) Tero Roponen <teanropo@jyu.fi> wrote:
> >
> > > On Wed, 30 May 2007, Pekka Enberg wrote:
> > >
> > > > On 5/30/07, Tero Roponen <teanropo@jyu.fi> wrote:
>
> after some trial and error I found a simple way to trigger the
> corruption:
>
BTW, that was impressive. You exposed a long-standing bug in neofb,
thanks.
And just FYI, you can also trigger it by doing fbset -depth 24.
Tony
prev parent reply other threads:[~2007-05-30 23:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 9:06 tty-related oops in latest kernel(s)? Tero Roponen
2007-05-28 7:22 ` Pekka Enberg
2007-05-28 7:47 ` Pekka Enberg
2007-05-28 8:08 ` Tero Roponen
2007-05-28 9:34 ` Pekka Enberg
2007-05-29 16:04 ` Tero Roponen
2007-05-29 18:57 ` Pekka Enberg
2007-05-30 3:43 ` Tero Roponen
2007-05-30 3:57 ` Tero Roponen
2007-05-30 5:54 ` Pekka Enberg
2007-05-30 5:59 ` Pekka Enberg
2007-05-30 6:00 ` Tero Roponen
2007-05-30 12:02 ` Tero Roponen
2007-05-30 15:39 ` Andrew Morton
2007-05-30 16:01 ` Tero Roponen
2007-05-30 16:09 ` Andrew Morton
2007-05-30 18:04 ` Alexey Dobriyan
2007-05-30 23:14 ` Antonino A. Daplas
2007-05-30 23:18 ` David Miller
2007-05-30 23:28 ` Antonino A. Daplas
2007-05-31 7:17 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2007-05-31 9:04 ` Antonino A. Daplas
2007-05-30 18:13 ` Pekka Enberg
2007-05-30 18:27 ` Tero Roponen
2007-05-30 22:14 ` Antonino A. Daplas
2007-05-30 23:17 ` Antonino A. Daplas [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=1180567047.4570.18.camel@daplas \
--to=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=teanropo@jyu.fi \
/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