From: Ondrej Zary <linux@rainbow-software.org>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: linux-fbdev@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Compiled tridentfb hangs but distribution kernel works fine
Date: Thu, 11 Dec 2014 23:07:44 +0000 [thread overview]
Message-ID: <201412120007.45242.linux@rainbow-software.org> (raw)
In-Reply-To: <1418195704.5312.31.camel@marge.simpson.net>
On Wednesday 10 December 2014 08:15:04 Mike Galbraith wrote:
> On Tue, 2014-12-09 at 22:33 +0100, Ondrej Zary wrote:
> > Hello,
> > I'm doing some work on tridentfb driver but encountered a weird problem.
> >
> > When I compile custom kernel with tridentfb, it hangs with Blade3D card
> > (ID 0x9880) in blade_image_blit(). The screen is blank with some
> > artifacts and machine does not respond to ping or keyboard. However, it
> > can be rebooted by Alt+SysRq+B. It works fine with other cards (3DImage
> > 9750 and CyberBlade XP) with no blit implementation. Commenting out
> > contents of blade_image_blit() function makes the hang go away (nothing
> > useful on the screen, of course).
> >
> > The weird thing is that the Blade3D card works fine when I load Debian
> > kernels! Debian 3.16-0.bpo.3-686-pae works fine but when I compile 3.16
> > kernel, it hangs.
> >
> > Any ideas?
>
> I'd start by looking for what Debian changed in source and/or config.
Seems that the problem appears only of CONFIG_CC_OPTIMIZE_FOR_SIZE is enabled.
Really weird.
--
Ondrej Zary
prev parent reply other threads:[~2014-12-11 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 21:33 Compiled tridentfb hangs but distribution kernel works fine Ondrej Zary
2014-12-10 7:15 ` Mike Galbraith
2014-12-11 23:07 ` Ondrej Zary [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=201412120007.45242.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=umgwanakikbuti@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;
as well as URLs for NNTP newsgroup(s).