linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, vandrove@vc.cvut.cz
Subject: Re: 2.5.67-mm1 cause framebuffer crash at bootup
Date: Wed, 9 Apr 2003 03:18:45 -0700	[thread overview]
Message-ID: <PAO-EX01DJb0LxA56iY0000151b@pao-ex01.pao.digeo.com> (raw)
Message-ID: <20030409031845.185d853f.akpm@digeo.com> (raw)
In-Reply-To: <3E93EB0E.4030609@aitel.hist.no>


Helge Hafting <helgehaf@aitel.hist.no> wrote:
>
> 2.5.67 works with framebuffer console, 2.5.67-mm1 dies before activating
> graphichs mode on two different machines:
> 
> smp with matroxfb, also using a patch that makes matroxfb work in 2.5
> up with radeonfb, also using patches that fixes the broken devfs in mm1.
> 
> I use devfs and preempt in both cases, and monolithic kernels without module
> support.
> 
> 2.5.67-mm1 works if I drop framebuffer support completely.
>
> Here is the printed backtrace for the radeon case, the matrox case was 
> similiar:

Well I tried to reproduce this with an

	nVidia Corporation NV17 [GeForce4 MX440] (rev a3)

and the screen came up in a strange mixture of penguins and obviously uninitialised
video RAM overlayed on top of text.  I can't read a thing.

But there is no oops.

The Cirrus drivers still do not compile, so scrub that test box.

We have some compilation scruffies:
drivers/video/aty/mach64_gx.c:194: warning: initialization from incompatible pointer type
drivers/video/aty/mach64_gx.c:486: warning: initialization from incompatible pointer type
drivers/video/aty/mach64_gx.c:602: warning: initialization from incompatible pointer type
drivers/video/aty/mach64_gx.c:726: warning: initialization from incompatible pointer type
drivers/video/aty/mach64_gx.c:873: warning: initialization from incompatible pointer type

Another machine here uses

	ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02)

and..... it oopses!   Backing out 

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.67/2.5.67-mm1/broken-out/earlier-keyboard-init.patch

prevents it oopsing.  Can you please try that?


Despite the lack of oopses, framebuffer support is sick on this machine also.
The LCD alternates between blackness and a strange smeary set of flickering
lines.


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

  parent reply	other threads:[~2003-04-09 10:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 11:22 2.5.67-mm1 Andrew Morton
2003-04-08 13:01 ` 2.5.67-mm1 William Lee Irwin III
2003-04-08 13:17 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 15:31   ` 2.5.67-mm1 Randy.Dunlap
2003-04-08 15:39     ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 16:14       ` 2.5.67-mm1 Randy.Dunlap
2003-04-08 16:18     ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 16:10   ` 2.5.67-mm1 Andrew Morton
2003-04-08 16:50     ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 14:08 ` 2.5.67-mm1 William Lee Irwin III
2003-04-08 16:43 ` 2.5.67-mm1 Helge Hafting
2003-04-09  9:42 ` 2.5.67-mm1 cause framebuffer crash at bootup Helge Hafting
     [not found]   ` <20030409030534.619f7fa0.akpm@digeo.com>
2003-04-09 10:05     ` Andrew Morton
     [not found]   ` <20030409031845.185d853f.akpm@digeo.com>
2003-04-09 10:18     ` Andrew Morton [this message]
2003-04-09 20:30       ` Randy.Dunlap
2003-05-28 11:14 ` 2.5.67-mm1 bootcrash, possibly IDE or RAID Helge Hafting
2003-05-28 11:13   ` William Lee Irwin III
2003-05-28 11:34     ` 2.5.70-mm1 " Helge Hafting
2003-05-28 11:35       ` William Lee Irwin III
2003-05-28 22:59         ` 2.5.70-mm1 bootcrash, possibly RAID-1 Helge Hafting
2003-05-28 23:18           ` Andrew Morton
2003-05-28 23:30           ` Paul E. Erkkila
2003-05-29  1:08             ` Neil Brown
2003-05-29  7:14               ` Zwane Mwaikambo
2003-05-29  7:32                 ` Zwane Mwaikambo
2003-05-30  1:59                   ` Neil Brown
2003-05-31 16:13                     ` Paul E. Erkkila
2003-05-29  4:27           ` Alain Toussaint
2003-05-29 13:22           ` John Stoffel
2003-04-09 12:24 2.5.67-mm1 cause framebuffer crash at bootup Petr Vandrovec

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=PAO-EX01DJb0LxA56iY0000151b@pao-ex01.pao.digeo.com \
    --to=akpm@digeo.com \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vandrove@vc.cvut.cz \
    /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