On 14/09/06, Michal Piotrowski <[email protected]> wrote:
On 14/09/06, Michal Piotrowski <[email protected]> wrote:
> On 14/09/06, David Chinner <[email protected]> wrote:
> >
> > What arch are you running on and what compiler are you using?
>
> gcc -v
> Using built-in specs.
> Target: i386-redhat-linux
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --enable-checking=release --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-libgcj-multifile
> --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> --enable-java-awt=gtk --disable-dssi
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> --with-cpu=generic --host=i386-redhat-linux
> Thread model: posix
> gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
>
> I'll build system with gcc 3.4
It's not a compiler issue.
Binary search should solve this mystery.
I was wrong - it's in vanilla tree
(http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg1).
cat hunt | head -n 3
origin.patch
BAD
libata-ignore-cfa-signature-while-sanity-checking-an-atapi-device.patch
I can reproduce this bug with all CONFIG_DEBUG_*=y.
(only
CONFIG_DEBUG_SYNCHRO_TEST=m
CONFIG_RCU_TORTURE_TEST=m
as modules)
I have checked memory
http://www.stardust.webpages.pl/files/crap/memtest.jpg and everything
seems to be fine.
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
