linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Brice Figureau <brice@tincell.com>
Cc: "Linuxppc-Dev@Lists.            " "Linuxppc. Org"
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: ibook2r2 & strange freeze.
Date: 26 Apr 2003 23:01:18 +0200	[thread overview]
Message-ID: <1051390877.1824.44.camel@gaston> (raw)
In-Reply-To: <E31EF083-7828-11D7-9243-0003939D5F18@tincell.com>


> The pc was in fbcon_radeon_bmove, so even if it's a fbcon problem, the
> crash is happening into the radeonfb module...
> video=ofonly works fine because it does not use fbcon_radeon_bmove I
> guess...

Well... The only way I see fbcon_radeon_bmove crash this way
would be because of a corrupt struct display.

> > So there is probably some memory corruption going on... I'm comparing
> > other bits of ben8 and ben9 now and see nothing relevants. The changes
> > where in the cache flush affecting cpufreq and sleep, and radeonfb...
> Since the crash occurs in the scoll, if there is a problem with the
> font (corrupted font or something) the scroll computation might be
> wrong, and thus fbcon_radeon_bmove might copy some memory from/to a bad
> area.

I don't think so. But try commenting out setting of the font in the
init scripts and let me know if that helps.

> Unfortunately those bugs are the most difficult to find and fix.
> What I could do is disable some part of the -ben9 patch in favor of the
> -ben8 version, until I find in which part it happens.

Can you try the xmon tricks I told you so I get a disassembly
(only copy the first 2 or 3 lines) and the register dump ?

I'm not sure anything in -ben9 compared to -ben8 explains the
problem if using -ben8's radeonfb in -ben9 still dies. I think
something get corrupt in struct display, it would be useful to
figure out what.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-04-26 21:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 15:27 ibook2r2 & strange freeze Brice Figureau
2003-04-25 17:43 ` Benjamin Herrenschmidt
2003-04-25 17:50   ` Benjamin Herrenschmidt
2003-04-25 20:05     ` Brice Figureau
2003-04-25 23:00     ` Brice Figureau
2003-04-26 10:33       ` Benjamin Herrenschmidt
2003-04-26 20:22         ` Brice Figureau
2003-04-26 20:35           ` Benjamin Herrenschmidt
2003-04-26 20:51             ` Brice Figureau
2003-04-26 21:01               ` Benjamin Herrenschmidt [this message]
2003-04-26 22:08                 ` Brice Figureau
2003-04-26 22:13                   ` Benjamin Herrenschmidt
2003-04-26 22:32                     ` Brice Figureau
2003-04-26 22:40                       ` Benjamin Herrenschmidt
2003-04-26 22:51                         ` Brice Figureau
2003-04-26 23:14                           ` Benjamin Herrenschmidt
2003-04-27 12:39                             ` Brice Figureau
2003-04-25 20:12 ` Remco Treffkorn
2003-04-25 22:55   ` Brice Figureau
2003-04-26  7:08   ` Mich Lanners

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=1051390877.1824.44.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=brice@tincell.com \
    --cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).