On 11/07/07 23:16, Andi Kleen wrote:
> I just checked with today's gcc 4.2 (070711) freshly compiled and from a
> quick inspection
> the code looks correct again. So perhaps it has been already fixed?
It has indeed been fixed. I tracked the bug down to gcc svn revision 126418
(20070706) and t
* Linus Torvalds ([EMAIL PROTECTED]) wrote:
> But yeah, if Debian/sid is just using random compiler snapshots of the
> day, I htink we can just bury this as "pointless".
Err, debian/sid *isn't* defaulting to gcc-4.2 yet, but it is made
available to people who want to install it and play with it.
Andi Kleen <[EMAIL PROTECTED]> writes:
>> I don't think this is worth even trying to fix. This is terminal compiler
>> breakage. Make a bug-report to the gcc people, the inline asm stuff has
>> been totally buggered by that compiler version.
>>
>> If it mis-compiled that part, it probably misco
On Wed, Jul 11, 2007 at 03:37:41PM -0700, Linus Torvalds wrote:
>
>
> On Thu, 12 Jul 2007, Andi Kleen wrote:
> >
> > I just checked with today's gcc 4.2 (070711) freshly compiled and from a
> > quick inspection
> > the code looks correct again. So perhaps it has been already fixed?
>
> Did yo
On Thu, 12 Jul 2007, Andi Kleen wrote:
>
> I just checked with today's gcc 4.2 (070711) freshly compiled and from a
> quick inspection
> the code looks correct again. So perhaps it has been already fixed?
Did you see the breakage with the original compiler? It might be some
config setup or s
> I don't think this is worth even trying to fix. This is terminal compiler
> breakage. Make a bug-report to the gcc people, the inline asm stuff has
> been totally buggered by that compiler version.
>
> If it mis-compiled that part, it probably miscompiled a lot of other
> things too.
I just
On Wed, 11 Jul 2007, Martin Orr wrote:
> On 11/07/07 19:01, Linus Torvalds wrote:
> > Can you do
> >
> > make arch/x86_64/kernel/signal.s
> >
> > with both compilers, and post the results somewhere? It's probably going
>
> OK, they are at:
> http://www.srcf.ucam.org/~mpo25/2007/linux-sig
On 11/07/07 19:01, Linus Torvalds wrote:
> Can you do
>
> make arch/x86_64/kernel/signal.s
>
> with both compilers, and post the results somewhere? It's probably going
> to be so large, and have so many trivial differences (register allocation
> etc) that it will be hard-to-impossible to
On Wed, 11 Jul 2007, Martin Orr wrote:
>
> I have done this. The file is arch/x86_64/kernel/signal.c: if I compile
> this with gcc 20070627 then everything works, if I compile it with gcc
> 20070707 then udevsettle hangs. This is independent of the gcc version used
> to compile the rest of the
O#n 11/07/07 14:10, Andi Kleen wrote:
> Stefano Rivoir <[EMAIL PROTECTED]> writes:
>> Linus Torvalds wrote:
>>> On Tue, 10 Jul 2007, Stefano Rivoir wrote:
>> Ok, the guilty bit is gcc: in my box, compiling kernel with gcc 4.2.x
>> (which is installed on my debian/sid) turns into a hang (in init,
>>
On Wed, Jul 11, 2007 at 08:38:23AM +0200, Stefano Rivoir wrote:
> Probably it's something I had to know before... but the light lit when
> gcc crashed when compiling 2.6.22-git1...
If gcc crashed when compiling 2.6.22-git1, and it didn't crash using
2.6.22, it would be really good idea to git bis
Stephen Frost wrote:
* Linus Torvalds ([EMAIL PROTECTED]) wrote:
I'm hoping your Debian/sid gcc version is some very experimental
known-buggy one, and not something that people _expect_ to be solid and
work well?
No such luck. :( Debian's close to moving to gcc-4.2 as the default
compiler in
Martin Orr wrote:
On 11/07/07 06:38, Stefano Rivoir wrote:
Linus Torvalds wrote:
On Tue, 10 Jul 2007, Stefano Rivoir wrote:
2.6.22 hangs at boot on my box. Here attached a original dmesg from 2.6.21,
and a copy of it where it stops on 2.6.22 (I can't attach the original 2.6.22
dmesg because it
On 11/07/07 06:38, Stefano Rivoir wrote:
> Linus Torvalds wrote:
> > On Tue, 10 Jul 2007, Stefano Rivoir wrote:
> >> 2.6.22 hangs at boot on my box. Here attached a original dmesg from 2.6.21,
> >> and a copy of it where it stops on 2.6.22 (I can't attach the original
> >> 2.6.22
> >> dmesg becaus
Stefano Rivoir <[EMAIL PROTECTED]> writes:
> Linus Torvalds wrote:
> > On Tue, 10 Jul 2007, Stefano Rivoir wrote:
> >> 2.6.22 hangs at boot on my box. Here attached a original dmesg from 2.6.21,
> >> and a copy of it where it stops on 2.6.22 (I can't attach the original
> >> 2.6.22
> >> dmesg bec
* Linus Torvalds ([EMAIL PROTECTED]) wrote:
> I'm hoping your Debian/sid gcc version is some very experimental
> known-buggy one, and not something that people _expect_ to be solid and
> work well?
No such luck. :( Debian's close to moving to gcc-4.2 as the default
compiler in sid. We've rebui
Adrian Bunk wrote:
>> > http://kernelnewbies.org/Linux_2_6_22
> But when you anyway publish release notes for your subsystem, also
> pasting them to the Wiki shouldn't be much extra work.
I will do so from now on. Until now I was too lazy to create an account
there.
--
Stefan Richter
-=-
On Wed, 11 Jul 2007, Stefano Rivoir wrote:
>
> Ok, the guilty bit is gcc: in my box, compiling kernel with gcc 4.2.x (which
> is installed on my debian/sid) turns into a hang (in init, seemingly, maybe
> not even in kernel itself), while gcc-4.1 is allright.
>
> Probably it's something I had to
Linus Torvalds wrote:
On Tue, 10 Jul 2007, Stefano Rivoir wrote:
2.6.22 hangs at boot on my box. Here attached a original dmesg from 2.6.21,
and a copy of it where it stops on 2.6.22 (I can't attach the original 2.6.22
dmesg because it's not logged to disk yet); it actually stops right after
'i
On Wed, 11 Jul 2007 01:12:53 +0200, Stefan Richter said:
> Adrian Bunk wrote:
> > On Tue, Jul 10, 2007 at 03:39:51PM -0400, [EMAIL PROTECTED] wrote:
> >> What the Rest Of The World could probably use is if some kind soul were to
> >> go
> >> through and build a .21->.22 document that lists all the
On Wed, 11 Jul 2007, Adrian Bunk wrote:
On Tue, Jul 10, 2007 at 03:39:51PM -0400, [EMAIL PROTECTED] wrote:
On Sun, 08 Jul 2007 16:52:52 PDT, Linus Torvalds said:
The full changelog since 2.6.21 also got uploaded, but quite frankly, I
wonder if anybody uses those things? I've been uploading th
On Wed, Jul 11, 2007 at 01:12:53AM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> > On Tue, Jul 10, 2007 at 03:39:51PM -0400, [EMAIL PROTECTED] wrote:
> >> What the Rest Of The World could probably use is if some kind soul were to
> >> go
> >> through and build a .21->.22 document that lists
Adrian Bunk wrote:
> On Tue, Jul 10, 2007 at 03:39:51PM -0400, [EMAIL PROTECTED] wrote:
>> What the Rest Of The World could probably use is if some kind soul were to go
>> through and build a .21->.22 document that lists all the *userspace visible*
>> changes
> Already available:
> http://kernel
On Tue, Jul 10, 2007 at 03:39:51PM -0400, [EMAIL PROTECTED] wrote:
> On Sun, 08 Jul 2007 16:52:52 PDT, Linus Torvalds said:
>
> > The full changelog since 2.6.21 also got uploaded, but quite frankly, I
> > wonder if anybody uses those things? I've been uploading them for non-git
> > users, but I
On Sun, 08 Jul 2007 16:52:52 PDT, Linus Torvalds said:
> The full changelog since 2.6.21 also got uploaded, but quite frankly, I
> wonder if anybody uses those things? I've been uploading them for non-git
> users, but I have a suspicion that any people who want that kind of
> detail have long s
On 07/09/2007 06:14 AM, Alan Cox wrote:
> Are the shortlogs useful - yes .. they catch what appear to be mistakes
>
> Specifically: What happened to the aacraid ioctl security fix ? Did someone
> decide it
> wasn't needed or did it get lost somewhere on the way ?
>
> While this looks scary the o
Linus Torvalds wrote:
> On Tue, 10 Jul 2007, Stefano Rivoir wrote:
>> 2.6.22 hangs at boot on my box. Here attached a original dmesg from 2.6.21,
>> and a copy of it where it stops on 2.6.22
...
>The next thing that you got on 2.6.21 after the point it hangs was
>apparently
>
> ..
On Tue, 10 Jul 2007, Stefano Rivoir wrote:
>
> 2.6.22 hangs at boot on my box. Here attached a original dmesg from 2.6.21,
> and a copy of it where it stops on 2.6.22 (I can't attach the original 2.6.22
> dmesg because it's not logged to disk yet); it actually stops right after
> 'init' launches
On Tue, 10 Jul 2007 09:17:18 +0200 Stefano Rivoir <[EMAIL PROTECTED]> wrote:
> Linus Torvalds wrote:
> > It's out there now (or at least in the process of mirroring out - if you
> > don't see everything, give it a bit of time).
>
> Hi all.
>
> 2.6.22 hangs at boot on my box. Here attached a ori
Hi all,
I'm looking for a volunteer who is willing to maintain the list of
known regressions in 2.6.22
http://kernelnewbies.org/known_regressions_2622
Anyone interested?
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
-
To unsubscribe from this list: send the line "unsubscribe linu
On Jul 9 2007 12:30, Jan Engelhardt wrote:
>
>The rc-to-rc shortlog is usually helpful. That way, I can see whether a
>particular fix that I am interested in/involved with has already been
>merged - or not and its needs some reminder. And the 2.6.x -> 2.6.y-rc1
>shortlog for seeing whether patches
Hi,
On Jul 8 2007 16:52, Linus Torvalds wrote:
>
>So this is also a heads-up that I'm considering skipping the ChangeLog
>files in the future - the full release ones are so big as to not be very
>easily readable (the full ChangeLog from 2.6.21 is ove ra hundred thousand
>lines, and weighs in at
Are the shortlogs useful - yes .. they catch what appear to be mistakes
Specifically: What happened to the aacraid ioctl security fix ? Did someone
decide it
wasn't needed or did it get lost somewhere on the way ?
While this looks scary the only obvious exploit cases are where the user can
open
On Monday 09 July 2007, Phil Oester wrote:
> On Sun, Jul 08, 2007 at 04:52:52PM -0700, Linus Torvalds wrote:
> > Anybody? Should I make just the shortlogs available instead (I don't save
> > those, but I post those for the later -rc's - usually the -rc1 and -rc2's
> > are too big for the mailing li
On Sun, Jul 08, 2007 at 04:52:52PM -0700, Linus Torvalds wrote:
> Anybody? Should I make just the shortlogs available instead (I don't save
> those, but I post those for the later -rc's - usually the -rc1 and -rc2's
> are too big for the mailing list, but they are still a lot smaller and
> more
On Sun, Jul 08, 2007 at 04:52:52PM -0700, Linus Torvalds wrote:
> Anybody? Should I make just the shortlogs available instead (I don't save
> those, but I post those for the later -rc's - usually the -rc1 and -rc2's
> are too big for the mailing list, but they are still a lot smaller and
> more
On 09/07/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
[snip]
The shortlog (appended) is fairly self-explanatory and the diffstat (at
the very end) also gives a fairly good picture of where the changes are.
I've always felt that these "shortlog since last -rc for a full
release" were a bit poin
It's out there now (or at least in the process of mirroring out - if you
don't see everything, give it a bit of time).
Not a whole lot of changes since -rc7: some small architecture changes
(ppc, mips, blackfin), and most of those are defconfig updates. Various
driver fixes: new PCI ID's along
38 matches
Mail list logo
