This message contains a list of some regressions from 2.6.23 which have been

reported since 2.6.24-rc1 was released and for which there are no fixes in the

mainline that I know of.  If any of them have been fixed already, please let me

know.
If you know of any other unresolved regressions from 2.6.23, please let me know

either and I'll add them to the list.
Subject		: Settings to /proc/sys/net/ipv[46]/conf/all are not propagated. via sysctl too

Submitter	: Serge van den Boom <svdb+linux-kernel-bugs@stack.nl>

References	: http://bugzilla.kernel.org/show_bug.cgi?id=9224

Handled-By	: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Subject		: linux-2.6.23-git3: Many sysfs-related warnings in dmesg

Submitter	: "Rafael J. Wysocki" <rjw@sisk.pl>

References	: http://lkml.org/lkml/2007/10/13/204

		  http://lkml.org/lkml/2007/10/26/317

		  http://bugzilla.kernel.org/show_bug.cgi?id=9244

Handled-By	: Greg KH <gregkh@suse.de>

		  Kay Sievers <kay.sievers@vrfy.org>

Patch		: http://lkml.org/lkml/2007/10/26/359
Subject		: On 2.6.24-rc1-gc9927c2b BUG: unable to handle kernel paging request at virtual address 3d15b925

Submitter	: Giacomo Catenazzi <cate@cateee.net>

References	: http://lkml.org/lkml/2007/10/24/487

		  http://bugzilla.kernel.org/show_bug.cgi?id=9246
Subject		: Potential regression in -git15: can't resume stopped root shell?

Submitter	: Theodore Tso <tytso@mit.edu>

References	: http://lkml.org/lkml/2007/10/20/114

		  http://bugzilla.kernel.org/show_bug.cgi?id=9247
Subject		: 2.6.24-rc1 fails with lockup and BUG:

Submitter	: Romano Giannetti <romanol@upcomillas.es>

References	: http://lkml.org/lkml/2007/10/24/232

		  http://bugzilla.kernel.org/show_bug.cgi?id=9248

Handled-By	: Ingo Molnar <mingo@elte.hu>

		  Peter Zijlstra <a.p.zijlstra@chello.nl>

		  Stephen Hemminger <shemminger@linux-foundation.org>

Patch		: http://lkml.org/lkml/2007/10/26/382
Subject		: irq 21: nobody cared 2.6.24-rc1

Submit...
[ message continues ]

From: "Rafael J. Wysocki" <rjw@sisk.pl>
I am to understand, from a reply from Herbert Xu, that this issue has

existed a long time, definitely since before 2.6.22, therefore it

doesn't belong on the regression list.
The bug reporter says something that drives me a little batty, which

is probably what got this onto the regression list.  He says "2.6.22

(not sure)" as the most recent kernel where the problem didn't occur.
People should list no version at all if they don't know, otherwise

we'll just get more bogons on the regression list.

-

I'm fairly sure that this originates with 2.6.21 as it looks very similar to

http://bugzilla.kernel.org/show_bug.cgi?id=8519

which I filed at that time and which I traced to 8030f54499925d07.
I've never been convinced that that change was correct, but as it now "works

for me" due to changes in the Debian default configuration files, I decided

to not follow up.
Of course, not honoring 'all' is more obviously a bug than not honoring

'default' for existing interfaces.
I've added a comment to #8519.
Hope this helps,

Frans Pop

-

I have removed it from the list.
Thanks,

Rafael

-

2.6.23 did not have pata_acpi. Its also not clear this is a bug in

pata_acpi as opposed to pata_ali which knows about the ALi quirks. The

ACPI and ATA specs sort of disagree here so I'll be trying to fix it

anyway.
-

OK, but please let me keep that on the list.  It may cause some people to

experience problems that were not present before functionality-wise.

-