From: "Adrian McMenamin" <adrianmcmenamin@gmail.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: "Adrian McMenamin" <lkmladrian@gmail.com>,
linux-kernel@vger.kernel.org, lethal@users.sourceforge.net
Subject: Re: Problems with framebuffer in 2.6.22-git17
Date: Fri, 27 Jul 2007 20:47:21 +0100 [thread overview]
Message-ID: <92a12cdb0707271247s727993b8i33999a9652b2ca20@mail.gmail.com> (raw)
In-Reply-To: <1185406433.5046.23.camel@daplas>
On 26/07/07, Antonino A. Daplas <adaplas@gmail.com> wrote:
>
> I'm also confused. Can you change the color depth to 32 bpp ('fbset
> -depth 32')? I'm thinking of a possible pseudo_palette overrun.
>
The code behaves in exactly the same way with the bit depth set to 32
and without the patch reversion (ie forces a reboot).
With the parch reverted there is a flicker of output on the screen
before a reboot is forced (it will boot with 16bpp though the colour
is a bit iffy)
With the patch reverted and 24bpp, it oopses before freezing (with two
odd looking boot logos on the screen):
[ 1.485628] Console: switching to colour frame buffer device 80x30
[ 1.553925] Unable to handle kernel paging request at virtual
address 55ff5504
[ 1.562351] pc = 8c0033a0
[ 1.565402] Unable to handle kernel paging request at virtual
address 0c1e8688
[ 1.573784] pc = 8c00b9e2
[ 1.576833] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.585205] pc = 8c00b9e2
[ 1.588258] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.596641] pc = 8c00b9e2
[ 1.599688] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.608069] pc = 8c00b9e2
[ 1.611117] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.619488] pc = 8c00b9e2
[ 1.622549] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.630927] pc = 8c00b9e2
[ 1.633979] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.642370] pc = 8c00b9e2
[ 1.645421] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.653793] pc = 8c00b9e2
[ 1.656854] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.665226] pc = 8c00b9e2
[ 1.668273] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.676664] pc = 8c00b9e2
[ 1.679715] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.688086] pc = 8c00b9e2
[ 1.691191] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.699557] pc = 8c00b9e2
[ 1.702603] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.710988] pc = 8c00b9e2
[ 1.714036] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.722408] pc = 8c00b9e2
[ 1.725468] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.733837] pc = 8c00b9e2
[ 1.736884] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.745270] pc = 8c00b9e2
[ 1.748314] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.756696] pc = 8c00b9e2
[ 1.759745] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.768111] pc = 8c00b9e2
[ 1.771155] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.779538] pc = 8c00b9e2
[ 1.782584] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.790997] pc = 8c00b9e2
[ 1.794045] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.802452] pc = 8c00b9e2
[ 1.805500] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.813888] pc = 8c00b9e2
[ 1.816937] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.825326] pc = 8c00b9e2
[ 1.828378] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.836753] pc = 8c00b9e2
[ 1.839846] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.848215] pc = 8c00b9e2
[ 1.851263] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.859649] pc = 8c00b9e2
[ 1.862695] Unable to handle kernel paging request at virtual
address 0c1e81ec
[ 1.871066] pc = 8c00b9e2
In short all versions of the driver seem to be broken in some way, but
it won't boot at all unless the patch is reverted
next prev parent reply other threads:[~2007-07-27 19:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 18:41 Adrian McMenamin
2007-07-22 21:02 ` Adrian McMenamin
2007-07-22 23:22 ` Antonino A. Daplas
[not found] ` <8b67d60707231324k28f3cd45p287418fd77feaf00@mail.gmail.com>
2007-07-23 20:35 ` Adrian McMenamin
2007-07-23 21:06 ` Paul Mundt
2007-07-24 21:45 ` Adrian McMenamin
2007-07-25 23:33 ` Antonino A. Daplas
2007-07-27 19:47 ` Adrian McMenamin [this message]
2007-07-27 20:18 ` Adrian McMenamin
2007-07-27 21:31 ` Antonino A. Daplas
2007-07-27 22:25 ` Adrian McMenamin
2007-07-27 23:22 ` Antonino A. Daplas
2007-07-28 0:32 ` Adrian McMenamin
2007-07-28 0:52 ` Antonino A. Daplas
2007-07-28 1:06 ` Adrian McMenamin
2007-07-28 2:14 ` Antonino A. Daplas
2007-07-28 2:18 ` Antonino A. Daplas
2007-07-27 21:43 ` 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=92a12cdb0707271247s727993b8i33999a9652b2ca20@mail.gmail.com \
--to=adrianmcmenamin@gmail.com \
--cc=adaplas@gmail.com \
--cc=lethal@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkmladrian@gmail.com \
/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®