linux-kernel - Re: 3.5-rc5: radeon acceleration regression on Transmeta system

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.SOC.1.00.1207111340360.12880@math.ut.ee>
Date:	Wed, 11 Jul 2012 13:43:55 +0300 (EEST)
From:	Meelis Roos <mroos@...ux.ee>
To:	valdis.kletnieks@...edu
cc:	Dave Airlie <airlied@...il.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	dri-devel@...ts.freedesktop.org
Subject: Re: 3.5-rc5: radeon acceleration regression on Transmeta system

> > It's actually more complicated than that. Old kernel images started
> > misbehaving from around 2.6.35-rc5 and any kernel older than that was
> > OK. When I recompiled the older kernels with squeeze gcc (migh have been
> > lenny gcc before, or different answers to make oldconfig), anything from
> > current git down to 2.6.33 is broken with radeon.modeset=1 and works (I
> 
> What releases of GCC were those?  I'm chasing an issue where compiling
> with 4.7.[01] breaks but 4.6.2 is OK, wondering if we're chasing the same thing.

I do not remember when I upgraded from lenny to squeeze. It the previous 
gcc was lenny's, it was gcc version 4.3.2 (Debian 4.3.2-1.1). The gcc in 
current stable (squeeze) is gcc version 4.4.5 (Debian 4.4.5-8). Since 
the old laptop is somewhat slow for following unstable, I have not tried 
any newer gcc version on that machine, and it has been compiling its own 
kernels for stress-testing purposes.

So it's probably not related to gcc 4.6->4.7 changes.

-- 
Meelis Roos (mroos@...ux.ee)
--
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/