lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 11 Dec 2008 11:25:27 +0100
From:	Alex Raimondi <mailinglist@...omico.ch>
To:	kernel@...32linux.org
CC:	linux-kernel@...r.kernel.org
Subject: Re: Segfault in fbcmap.c => Compiler bug?

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@...omico.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@...32linux.org
> http://duppen.flaskehals.net/cgi-bin/mailman/listinfo/kernel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ