From: Alex Raimondi <mailinglist@miromico.ch>
To: kernel@avr32linux.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Segfault in fbcmap.c => Compiler bug?
Date: Thu, 11 Dec 2008 11:25:27 +0100 [thread overview]
Message-ID: <4940EA97.8020308@miromico.ch> (raw)
In-Reply-To: <4940D8C0.9060709@miromico.ch>
Just for the records:
Removing the atmel precompiled toolchain and switching over to buildroot toolchain (same gcc version)
completely solved the problem.
Alex
>
>> On Thu, 11 Dec 2008 09:23:59 +0100
>> Alex Raimondi <mailinglist@miromico.ch> wrote:
>>
>> Hi Alex,
>>
>>> I am using latest atmel avr32 kernel (2.6.27) form
>>> git://git.kernel.org/pub/scm/linux/kernel/git/hskinnemoen/avr32-2.6.git.
>>> I am on it's master branch. I added a few patches specific to our own
>>> board (hammerhead).
>>>
>> Which toolchain are you using? If you have grabbed it from atmel.com
>> you have to download Buildroot for AVR32 [1] and build your own
>> toolchain. The toolchain on atmel.com is broken.
>
> I have both. AV32 toolchain from atmel is installed via apt-get. I have builroot 2.2.1 which
> generated a toolchain, as well.
>
> but kernel compilation is done using apt-get toolchain.
>
> So, your suggestion is to remove the atmel stuff completely and use only buildroot toolchain?
>
> Thx,
>
> Alex
>
>>> When compiling with support for atmel_lcdfb the kernel segfaults at
>>> module probe.
>>>
>>> This is the segfault output:
>>>
>>> **********************************
>>> alg: No test for stdrng (krng)
>>> io scheduler noop registered
>>> io scheduler cfq registered (default)
>>> atmel_lcdfb atmel_lcdfb.0: 225KiB frame buffer at 13940000 (mapped at
>>> b3940000) Unable to handle kernel NULL pointer dereference at virtual
>> Does indeed look like a known GCC bug.
>>
>> <snipp> rest of kernel dump and debugging>
>>
>> 1: www.atmel.no/buildroot
>>
>
> _______________________________________________
> Kernel mailing list
> Kernel@avr32linux.org
> http://duppen.flaskehals.net/cgi-bin/mailman/listinfo/kernel
next prev parent reply other threads:[~2008-12-11 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 8:23 Segfault in fbcmap.c => Compiler bug? Alex Raimondi
2008-12-11 8:29 ` Hans-Christian Egtvedt
2008-12-11 9:09 ` Alex Raimondi
2008-12-11 9:26 ` Hans-Christian Egtvedt
2008-12-11 10:25 ` Alex Raimondi [this message]
2008-12-11 10:06 ` Haavard Skinnemoen
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=4940EA97.8020308@miromico.ch \
--to=mailinglist@miromico.ch \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@vger.kernel.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