* Re: 2.6.1-mm4
[not found] ` <20040119224219.65991501.rusty@rustcorp.com.au.suse.lists.linux.kernel>
@ 2004-01-19 12:40 ` Andi Kleen
2004-01-21 4:06 ` 2.6.1-mm4 Rusty Russell
0 siblings, 1 reply; 68+ messages in thread
From: Andi Kleen @ 2004-01-19 12:40 UTC (permalink / raw)
To: Rusty Russell; +Cc: linux-kernel, akpm
Rusty Russell <rusty@rustcorp.com.au> writes:
> Migrating to module_param() is the Right Thing here IMHO, which actually
> takes the damn address,
The main problem is that module_parm renames the boot time arguments and
makes them long and hard to remember. E.g. the new argument needed to
make the mouse work on KVMs is mindboogling, could be nearly a Windows
registry entry.
-Andi
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-19 12:40 ` 2.6.1-mm4 Andi Kleen
@ 2004-01-21 4:06 ` Rusty Russell
2004-01-21 4:56 ` 2.6.1-mm4 Valdis.Kletnieks
` (2 more replies)
0 siblings, 3 replies; 68+ messages in thread
From: Rusty Russell @ 2004-01-21 4:06 UTC (permalink / raw)
To: Andi Kleen; +Cc: linux-kernel, akpm, Vojtech Pavlik
In message <p73r7xwglgn.fsf@verdi.suse.de> you write:
> Rusty Russell <rusty@rustcorp.com.au> writes:
>
> > Migrating to module_param() is the Right Thing here IMHO, which actually
> > takes the damn address,
>
> The main problem is that module_parm renames the boot time arguments and
> makes them long and hard to remember.
Um, if the module name is neat, and the parameter name is neat, the
combination of the two with a "." between them will be nest.
> E.g. the new argument needed to make the mouse work on KVMs is
> mindboogling, could be nearly a Windows registry entry.
I have no idea what you are talking about. 8(
Please explain,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 4:06 ` 2.6.1-mm4 Rusty Russell
@ 2004-01-21 4:56 ` Valdis.Kletnieks
2004-01-21 8:40 ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:23 ` mouse configuration in 2.6.1 Andi Kleen
2 siblings, 0 replies; 68+ messages in thread
From: Valdis.Kletnieks @ 2004-01-21 4:56 UTC (permalink / raw)
To: Rusty Russell; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
On Wed, 21 Jan 2004 15:06:57 +1100, Rusty Russell said:
> > E.g. the new argument needed to make the mouse work on KVMs is
> > mindboogling, could be nearly a Windows registry entry.
>
> I have no idea what you are talking about. 8(
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs
That's the name of a registry entry. I don't think iwe're quite THAT bad. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 4:06 ` 2.6.1-mm4 Rusty Russell
2004-01-21 4:56 ` 2.6.1-mm4 Valdis.Kletnieks
@ 2004-01-21 8:40 ` Vojtech Pavlik
2004-01-21 12:27 ` 2.6.1-mm4 Andi Kleen
2004-01-21 12:23 ` mouse configuration in 2.6.1 Andi Kleen
2 siblings, 1 reply; 68+ messages in thread
From: Vojtech Pavlik @ 2004-01-21 8:40 UTC (permalink / raw)
To: Rusty Russell; +Cc: Andi Kleen, linux-kernel, akpm
On Wed, Jan 21, 2004 at 03:06:57PM +1100, Rusty Russell wrote:
> In message <p73r7xwglgn.fsf@verdi.suse.de> you write:
> > Rusty Russell <rusty@rustcorp.com.au> writes:
> >
> > > Migrating to module_param() is the Right Thing here IMHO, which actually
> > > takes the damn address,
> >
> > The main problem is that module_parm renames the boot time arguments and
> > makes them long and hard to remember.
>
> Um, if the module name is neat, and the parameter name is neat, the
> combination of the two with a "." between them will be nest.
>
> > E.g. the new argument needed to make the mouse work on KVMs is
> > mindboogling, could be nearly a Windows registry entry.
>
> I have no idea what you are talking about. 8(
Inbetween the module changes and the input changes there was a
situation, where you'd have to pass
psmouse.psmouse_maxproto=imps2
as a kernel argument. This should (I hope so, I have to check) be fixed
now.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 68+ messages in thread
* mouse configuration in 2.6.1
2004-01-21 4:06 ` 2.6.1-mm4 Rusty Russell
2004-01-21 4:56 ` 2.6.1-mm4 Valdis.Kletnieks
2004-01-21 8:40 ` 2.6.1-mm4 Vojtech Pavlik
@ 2004-01-21 12:23 ` Andi Kleen
2004-01-21 12:31 ` Marcos D. Marado Torres
` (2 more replies)
2 siblings, 3 replies; 68+ messages in thread
From: Andi Kleen @ 2004-01-21 12:23 UTC (permalink / raw)
To: Rusty Russell; +Cc: linux-kernel, akpm, vojtech
On Wed, 21 Jan 2004 15:06:57 +1100
Rusty Russell <rusty@rustcorp.com.au> wrote:
> In message <p73r7xwglgn.fsf@verdi.suse.de> you write:
> > Rusty Russell <rusty@rustcorp.com.au> writes:
> >
> > > Migrating to module_param() is the Right Thing here IMHO, which actually
> > > takes the damn address,
> >
> > The main problem is that module_parm renames the boot time arguments and
> > makes them long and hard to remember.
>
> Um, if the module name is neat, and the parameter name is neat, the
> combination of the two with a "." between them will be nest.
Unfortunately we have lots of non neat module names and many previous boot
time arguments note their subsystem which adds even more redundancy.
And you're suggesting people to move to module_parm now in the stable
series leads to renaming of module parameters, which breaks previously
working configurations in often subtle ways. Maybe that's acceptable
in a unstable development kernel, but I don't think it is in 2.6.
How about adding a "setup option alias" table and require that everybody
changing an existing __setup to module_parm adds an alias there?
> > E.g. the new argument needed to make the mouse work on KVMs is
> > mindboogling, could be nearly a Windows registry entry.
>
> I have no idea what you are talking about. 8(
psmouse_base.psmouse_noext
(brought to you by the department of redundancy department)
The "new" and "improved" version is apparently:
psmouse_base.psmouse_proto=bare
which is even worse.
And 2.6.0 -> 2.6.1 silently changing to that without any documentation anywhere,
silently breaking my mouse. And debugging it requires a lot of reboots
because we have regressed to Windows state where every mouse setting change
requires a reboot :-/
Sorry Rusty. You are probably the wrong target for the flame, but a combination
of probably well intended changes including module_parm brought a total usability
disaster here.
-Andi
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 8:40 ` 2.6.1-mm4 Vojtech Pavlik
@ 2004-01-21 12:27 ` Andi Kleen
2004-01-21 12:34 ` 2.6.1-mm4 Vojtech Pavlik
0 siblings, 1 reply; 68+ messages in thread
From: Andi Kleen @ 2004-01-21 12:27 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: rusty, linux-kernel, akpm
On Wed, 21 Jan 2004 09:40:09 +0100
Vojtech Pavlik <vojtech@suse.cz> wrote:
>
> Inbetween the module changes and the input changes there was a
> situation, where you'd have to pass
>
> psmouse.psmouse_maxproto=imps2
>
> as a kernel argument. This should (I hope so, I have to check) be fixed
> now.
No, 2.6.1 requires it.
And worst is that you have to reboot to change mouse settings at all.
That just doesn't make any sense. Can you please add an runtime sysfs
interface for this?
-Andi
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: mouse configuration in 2.6.1
2004-01-21 12:23 ` mouse configuration in 2.6.1 Andi Kleen
@ 2004-01-21 12:31 ` Marcos D. Marado Torres
2004-01-21 12:42 ` Andi Kleen
2004-01-21 12:32 ` Vojtech Pavlik
2004-01-22 1:14 ` Rusty Russell
2 siblings, 1 reply; 68+ messages in thread
From: Marcos D. Marado Torres @ 2004-01-21 12:31 UTC (permalink / raw)
To: Andi Kleen; +Cc: Rusty Russell, linux-kernel, akpm, vojtech
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 21 Jan 2004, Andi Kleen wrote:
> On Wed, 21 Jan 2004 15:06:57 +1100
> Rusty Russell <rusty@rustcorp.com.au> wrote:
>
> > In message <p73r7xwglgn.fsf@verdi.suse.de> you write:
> > > Rusty Russell <rusty@rustcorp.com.au> writes:
> > >
> > > > Migrating to module_param() is the Right Thing here IMHO, which actually
> > > > takes the damn address,
> > >
> > > The main problem is that module_parm renames the boot time arguments and
> > > makes them long and hard to remember.
> >
> > Um, if the module name is neat, and the parameter name is neat, the
> > combination of the two with a "." between them will be nest.
>
> Unfortunately we have lots of non neat module names and many previous boot
> time arguments note their subsystem which adds even more redundancy.
>
> And you're suggesting people to move to module_parm now in the stable
> series leads to renaming of module parameters, which breaks previously
> working configurations in often subtle ways. Maybe that's acceptable
> in a unstable development kernel, but I don't think it is in 2.6.
>
> How about adding a "setup option alias" table and require that everybody
> changing an existing __setup to module_parm adds an alias there?
>
> > > E.g. the new argument needed to make the mouse work on KVMs is
> > > mindboogling, could be nearly a Windows registry entry.
> >
> > I have no idea what you are talking about. 8(
>
> psmouse_base.psmouse_noext
>
> (brought to you by the department of redundancy department)
>
> The "new" and "improved" version is apparently:
>
> psmouse_base.psmouse_proto=bare
Actually it's psmouse.proto=bare
> which is even worse.
>
> And 2.6.0 -> 2.6.1 silently changing to that without any documentation anywhere,
> silently breaking my mouse. And debugging it requires a lot of reboots
> because we have regressed to Windows state where every mouse setting change
> requires a reboot :-/
>
> Sorry Rusty. You are probably the wrong target for the flame, but a combination
> of probably well intended changes including module_parm brought a total usability
> disaster here.
>
> -Andi
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
- --
==================================================
Marcos Daniel Marado Torres AKA Mind Booster Noori
/"\ http://student.dei.uc.pt/~marado
\ / marado@student.dei.uc.pt
X ASCII Ribbon Campaign
/ \ against HTML e-mail and Micro$oft attachments
==================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFADnEbmNlq8m+oD34RAmatAKCBEpHzK1KzpmOQ6T8fveaL5j6bJgCeP+AA
N57BBoKD2an9Cg3ifJVYvh0=
=ikyB
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: mouse configuration in 2.6.1
2004-01-21 12:23 ` mouse configuration in 2.6.1 Andi Kleen
2004-01-21 12:31 ` Marcos D. Marado Torres
@ 2004-01-21 12:32 ` Vojtech Pavlik
2004-01-22 1:14 ` Rusty Russell
2 siblings, 0 replies; 68+ messages in thread
From: Vojtech Pavlik @ 2004-01-21 12:32 UTC (permalink / raw)
To: Andi Kleen; +Cc: Rusty Russell, linux-kernel, akpm
On Wed, Jan 21, 2004 at 01:23:37PM +0100, Andi Kleen wrote:
> (brought to you by the department of redundancy department)
>
> The "new" and "improved" version is apparently:
>
> psmouse_base.psmouse_proto=bare
2.6.2 will have it as:
psmouse.proto=bare
which isn't that bad.
> And 2.6.0 -> 2.6.1 silently changing to that without any documentation
> anywhere, silently breaking my mouse. And debugging it requires a lot
> of reboots because we have regressed to Windows state where every
> mouse setting change requires a reboot :-/
>
> Sorry Rusty. You are probably the wrong target for the flame, but a
> combination of probably well intended changes including module_parm
> brought a total usability disaster here.
Keep prepared for yet another silent change (documentation _is_ getting
updated, though). And I'll don my asbestos overall ...
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 12:27 ` 2.6.1-mm4 Andi Kleen
@ 2004-01-21 12:34 ` Vojtech Pavlik
2004-01-21 12:46 ` 2.6.1-mm4 Andi Kleen
2004-01-21 12:53 ` 2.6.1-mm4 Dmitry Torokhov
0 siblings, 2 replies; 68+ messages in thread
From: Vojtech Pavlik @ 2004-01-21 12:34 UTC (permalink / raw)
To: Andi Kleen; +Cc: rusty, linux-kernel, akpm
On Wed, Jan 21, 2004 at 01:27:44PM +0100, Andi Kleen wrote:
> On Wed, 21 Jan 2004 09:40:09 +0100
> Vojtech Pavlik <vojtech@suse.cz> wrote:
>
> >
> > Inbetween the module changes and the input changes there was a
> > situation, where you'd have to pass
> >
> > psmouse.psmouse_maxproto=imps2
> >
> > as a kernel argument. This should (I hope so, I have to check) be fixed
> > now.
>
> No, 2.6.1 requires it.
>
> And worst is that you have to reboot to change mouse settings at all.
> That just doesn't make any sense. Can you please add an runtime sysfs
> interface for this?
It's planned, though not easy to implement at all. I don't think I'll be
able to get this into 2.6.2. For now you can enable EMBEDDED, compile
psmouse as a module, and just rmmod/insmod it with new parameters.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: mouse configuration in 2.6.1
2004-01-21 12:31 ` Marcos D. Marado Torres
@ 2004-01-21 12:42 ` Andi Kleen
2004-01-21 12:53 ` Marcos D. Marado Torres
2004-01-21 13:09 ` Dmitry Torokhov
0 siblings, 2 replies; 68+ messages in thread
From: Andi Kleen @ 2004-01-21 12:42 UTC (permalink / raw)
To: Marcos D. Marado Torres; +Cc: rusty, linux-kernel, akpm, vojtech
On Wed, 21 Jan 2004 12:31:21 +0000 (WET)
"Marcos D. Marado Torres" <marado@student.dei.uc.pt> wrote:
> apparently:
> >
> > psmouse_base.psmouse_proto=bare
>
> Actually it's psmouse.proto=bare
In 2.6.1 it is definitely psmouse_base.psmouse_proto=bare
-Andi
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 12:34 ` 2.6.1-mm4 Vojtech Pavlik
@ 2004-01-21 12:46 ` Andi Kleen
2004-01-21 13:13 ` 2.6.1-mm4 Vojtech Pavlik
2004-01-22 1:31 ` 2.6.1-mm4 Rusty Russell
2004-01-21 12:53 ` 2.6.1-mm4 Dmitry Torokhov
1 sibling, 2 replies; 68+ messages in thread
From: Andi Kleen @ 2004-01-21 12:46 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: rusty, linux-kernel, akpm
On Wed, 21 Jan 2004 13:34:54 +0100
Vojtech Pavlik <vojtech@suse.cz> wrote:
> On Wed, Jan 21, 2004 at 01:27:44PM +0100, Andi Kleen wrote:
> > On Wed, 21 Jan 2004 09:40:09 +0100
> > Vojtech Pavlik <vojtech@suse.cz> wrote:
> >
> > >
> > > Inbetween the module changes and the input changes there was a
> > > situation, where you'd have to pass
> > >
> > > psmouse.psmouse_maxproto=imps2
> > >
> > > as a kernel argument. This should (I hope so, I have to check) be fixed
> > > now.
> >
> > No, 2.6.1 requires it.
> >
> > And worst is that you have to reboot to change mouse settings at all.
> > That just doesn't make any sense. Can you please add an runtime sysfs
> > interface for this?
>
> It's planned, though not easy to implement at all. I don't think I'll be
> able to get this into 2.6.2. For now you can enable EMBEDDED, compile
> psmouse as a module, and just rmmod/insmod it with new parameters.
Really. I don't want a modular mouse driver, just a mouse that keeps working
over kernel releases without me requiring tracking undocumented changes
every release. Thanks for the warning that you renamed it again, at least
that will save some reboots next time.
Could you perhaps readd the old __setup that at least the old version
keeps working? After that you can rename it again as often as you
want as long as the old alias keeps working ;-)
As for the implementation of doing it at runtime - i took a look at it
but got scared by sysfs livetime rules and the lack of callbacks in module_parm.
I think the easiest way would be to just poll the value: make it a module_parm with the
w bit enabled, add a second set of state variables and every time you access
the mouse you compare the module_parm variables and the shadow variables and change
the mouse setting if they differ. Not pretty, but would probably work without
too much sysfs black magic.
-Andi
>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: mouse configuration in 2.6.1
2004-01-21 12:42 ` Andi Kleen
@ 2004-01-21 12:53 ` Marcos D. Marado Torres
2004-01-21 13:02 ` Andi Kleen
2004-01-21 13:09 ` Dmitry Torokhov
1 sibling, 1 reply; 68+ messages in thread
From: Marcos D. Marado Torres @ 2004-01-21 12:53 UTC (permalink / raw)
To: Andi Kleen; +Cc: rusty, linux-kernel, akpm, vojtech
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 21 Jan 2004, Andi Kleen wrote:
> On Wed, 21 Jan 2004 12:31:21 +0000 (WET)
> "Marcos D. Marado Torres" <marado@student.dei.uc.pt> wrote:
>
> > apparently:
> > >
> > > psmouse_base.psmouse_proto=bare
> >
> > Actually it's psmouse.proto=bare
>
> In 2.6.1 it is definitely psmouse_base.psmouse_proto=bare
Do you have it compiled as a module?
> -Andi
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
- --
==================================================
Marcos Daniel Marado Torres AKA Mind Booster Noori
/"\ http://student.dei.uc.pt/~marado
\ / marado@student.dei.uc.pt
X ASCII Ribbon Campaign
/ \ against HTML e-mail and Micro$oft attachments
==================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFADnY7mNlq8m+oD34RAjSgAKDfYlvGpTiBTnlr8NXWbfpWcyAV5wCfafMb
aihlrtCkWQNtIXI4EuhERos=
=oxw2
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 12:34 ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:46 ` 2.6.1-mm4 Andi Kleen
@ 2004-01-21 12:53 ` Dmitry Torokhov
1 sibling, 0 replies; 68+ messages in thread
From: Dmitry Torokhov @ 2004-01-21 12:53 UTC (permalink / raw)
To: Vojtech Pavlik, Andi Kleen; +Cc: rusty, linux-kernel, akpm
On Wednesday 21 January 2004 07:34 am, Vojtech Pavlik wrote:
> On Wed, Jan 21, 2004 at 01:27:44PM +0100, Andi Kleen wrote:
> > On Wed, 21 Jan 2004 09:40:09 +0100
> >
> > Vojtech Pavlik <vojtech@suse.cz> wrote:
> > > Inbetween the module changes and the input changes there was a
> > > situation, where you'd have to pass
> > >
> > > psmouse.psmouse_maxproto=imps2
> > >
> > > as a kernel argument. This should (I hope so, I have to check) be
> > > fixed now.
> >
> > No, 2.6.1 requires it.
> >
> > And worst is that you have to reboot to change mouse settings at all.
> > That just doesn't make any sense. Can you please add an runtime sysfs
> > interface for this?
>
> It's planned, though not easy to implement at all. I don't think I'll
> be able to get this into 2.6.2. For now you can enable EMBEDDED,
> compile psmouse as a module, and just rmmod/insmod it with new
> parameters.
No, it's just mousedev that is always built-in, psmouse can be compiled
as a module (and that's the reason the whole naming mess happened - I use
it as a module and haven't noticed the necessity of the prefixes when
converted to the module_param()).
--
Dmitry
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: mouse configuration in 2.6.1
2004-01-21 12:53 ` Marcos D. Marado Torres
@ 2004-01-21 13:02 ` Andi Kleen
2004-01-21 13:06 ` Marcos D. Marado Torres
0 siblings, 1 reply; 68+ messages in thread
From: Andi Kleen @ 2004-01-21 13:02 UTC (permalink / raw)
To: Marcos D. Marado Torres; +Cc: rusty, linux-kernel, akpm, vojtech
On Wed, 21 Jan 2004 12:53:12 +0000 (WET)
"Marcos D. Marado Torres" <marado@student.dei.uc.pt> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, 21 Jan 2004, Andi Kleen wrote:
>
> > On Wed, 21 Jan 2004 12:31:21 +0000 (WET)
> > "Marcos D. Marado Torres" <marado@student.dei.uc.pt> wrote:
> >
> > > apparently:
> > > >
> > > > psmouse_base.psmouse_proto=bare
> > >
> > > Actually it's psmouse.proto=bare
> >
> > In 2.6.1 it is definitely psmouse_base.psmouse_proto=bare
>
> Do you have it compiled as a module?
No of course not. For a module it would be psmouse_proto=bare
-Andi
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: mouse configuration in 2.6.1
2004-01-21 13:02 ` Andi Kleen
@ 2004-01-21 13:06 ` Marcos D. Marado Torres
0 siblings, 0 replies; 68+ messages in thread
From: Marcos D. Marado Torres @ 2004-01-21 13:06 UTC (permalink / raw)
To: Andi Kleen; +Cc: rusty, linux-kernel, akpm, vojtech
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 21 Jan 2004, Andi Kleen wrote:
> On Wed, 21 Jan 2004 12:53:12 +0000 (WET)
> "Marcos D. Marado Torres" <marado@student.dei.uc.pt> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Wed, 21 Jan 2004, Andi Kleen wrote:
> >
> > > On Wed, 21 Jan 2004 12:31:21 +0000 (WET)
> > > "Marcos D. Marado Torres" <marado@student.dei.uc.pt> wrote:
> > >
> > > > apparently:
> > > > >
> > > > > psmouse_base.psmouse_proto=bare
> > > >
> > > > Actually it's psmouse.proto=bare
> > >
> > > In 2.6.1 it is definitely psmouse_base.psmouse_proto=bare
> >
> > Do you have it compiled as a module?
>
> No of course not. For a module it would be psmouse_proto=bare
>
> -Andi
>
Oh, I'm sorry, I was talking about 2.6.2-rc1.
Starting in 2.6.1-mm* and now in 2.6.2-rc1 you just have to pass
psmouse.proto=bare .
- --
==================================================
Marcos Daniel Marado Torres AKA Mind Booster Noori
/"\ http://student.dei.uc.pt/~marado
\ / marado@student.dei.uc.pt
X ASCII Ribbon Campaign
/ \ against HTML e-mail and Micro$oft attachments
==================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFADnlOmNlq8m+oD34RAgdPAKDeeGMpZOq2ObzIEVHyzUb8ovBarACfdIk0
owGg+aqr2clAfXNod323y9c=
=6PbO
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: mouse configuration in 2.6.1
2004-01-21 12:42 ` Andi Kleen
2004-01-21 12:53 ` Marcos D. Marado Torres
@ 2004-01-21 13:09 ` Dmitry Torokhov
1 sibling, 0 replies; 68+ messages in thread
From: Dmitry Torokhov @ 2004-01-21 13:09 UTC (permalink / raw)
To: Andi Kleen, Marcos D. Marado Torres; +Cc: rusty, linux-kernel, akpm, vojtech
On Wednesday 21 January 2004 07:42 am, Andi Kleen wrote:
> On Wed, 21 Jan 2004 12:31:21 +0000 (WET)
>
> "Marcos D. Marado Torres" <marado@student.dei.uc.pt> wrote:
> > apparently:
> > > psmouse_base.psmouse_proto=bare
> >
> > Actually it's psmouse.proto=bare
>
> In 2.6.1 it is definitely psmouse_base.psmouse_proto=bare
>
You really should see psmouse.psmouse_proto=bare in 2.6.1 (and it's
changed to psmouse.proto=bare in 2.6.2-rc1):
make KBUILD_MODULES=1 -f scripts/Makefile.build obj=drivers/input/mouse
gcc -Wp,-MD,drivers/input/mouse/.psmouse-base.o.d -nostdinc -iwithprefix
include -D__KERNEL__ -Iinclude -D__KERNEL__ -Iinclude
-Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=pentium3
-Iinclude/asm-i386/mach-default -O2
-DMODULE -DKBUILD_BASENAME=psmouse_base -DKBUILD_MODNAME=psmouse
-c -o drivers/input/mouse/.tmp_psmouse-base.o
drivers/input/mouse/psmouse-base.c
As you can see KBUILD_MODNAME is just psmouse and module_param() uses it
as a prefix.
--
Dmitry
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 12:46 ` 2.6.1-mm4 Andi Kleen
@ 2004-01-21 13:13 ` Vojtech Pavlik
2004-01-22 1:31 ` 2.6.1-mm4 Rusty Russell
1 sibling, 0 replies; 68+ messages in thread
From: Vojtech Pavlik @ 2004-01-21 13:13 UTC (permalink / raw)
To: Andi Kleen; +Cc: rusty, linux-kernel, akpm
On Wed, Jan 21, 2004 at 01:46:57PM +0100, Andi Kleen wrote:
> As for the implementation of doing it at runtime - i took a look at it
> but got scared by sysfs livetime rules and the lack of callbacks in module_parm.
> I think the easiest way would be to just poll the value: make it a module_parm with the
> w bit enabled, add a second set of state variables and every time you access
> the mouse you compare the module_parm variables and the shadow variables and change
> the mouse setting if they differ. Not pretty, but would probably work without
> too much sysfs black magic.
The second problem (after the sysfs magic) is that I'd have to
completely reinitialize the mouse as well, down to the features of the
mouse changing (for example no wheel anymore).
So, it's planned, but don't expect it in 2.6.2.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: mouse configuration in 2.6.1
2004-01-21 12:23 ` mouse configuration in 2.6.1 Andi Kleen
2004-01-21 12:31 ` Marcos D. Marado Torres
2004-01-21 12:32 ` Vojtech Pavlik
@ 2004-01-22 1:14 ` Rusty Russell
2 siblings, 0 replies; 68+ messages in thread
From: Rusty Russell @ 2004-01-22 1:14 UTC (permalink / raw)
To: Andi Kleen; +Cc: linux-kernel, akpm, vojtech
In message <20040121132337.7f8d3c79.ak@suse.de> you write:
> Unfortunately we have lots of non neat module names and many previous boot
> time arguments note their subsystem which adds even more redundancy.
>
> And you're suggesting people to move to module_parm now in the stable
> series leads to renaming of module parameters, which breaks previously
> working configurations in often subtle ways. Maybe that's acceptable
> in a unstable development kernel, but I don't think it is in 2.6.
I think we're getting a little confused here.
I'm saying that people should start using module_param instead of
MODULE_PARM in new code, or code being reworked. This adds a boot
param where there was none before.
I'm explicitly not advocating replacing __setup() for existing code.
> And 2.6.0 -> 2.6.1 silently changing to that without any
> documentation anywhere, silently breaking my mouse.
That's bad. I would have left the old __setup under #ifdef
CONFIG_OBSOLETE_MODPARM (or something where it can eventually go
away). And maybe a printk warning about using the old name.
> Sorry Rusty. You are probably the wrong target for the flame, but a
> combination of probably well intended changes including module_parm
> brought a total usability disaster here.
Perhaps I am the wrong target, but I'm glad you brought it up.
I thought that changing __setup to module_param() would have obvious
effects, and authors would make their own call on that.
FYI: __setup and module_param() *CAN* be freely mixed, unlike
MODULE_PARM and module_param().
Hope that clarifies,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 12:46 ` 2.6.1-mm4 Andi Kleen
2004-01-21 13:13 ` 2.6.1-mm4 Vojtech Pavlik
@ 2004-01-22 1:31 ` Rusty Russell
1 sibling, 0 replies; 68+ messages in thread
From: Rusty Russell @ 2004-01-22 1:31 UTC (permalink / raw)
To: Andi Kleen; +Cc: Vojtech Pavlik, linux-kernel, akpm
In message <20040121134657.6cd27cbd.ak@suse.de> you write:
> As for the implementation of doing it at runtime - i took a look at
> it but got scared by sysfs livetime rules and the lack of callbacks
> in module_parm.
FYI module_parm is just a convenience wrapper around
module_param_call(name, set, get, arg, perm)
Where get and set are the callbacks:
/* Returns 0, or -errno. arg is in kp->arg. */
typedef int (*param_set_fn)(const char *val, struct kernel_param *kp);
/* Returns length written or -errno. Buffer is 4k (ie. be short!) */
typedef int (*param_get_fn)(char *buffer, struct kernel_param *kp);
With these the implementation should be fairly neat.
Hope that clarifies,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-02-12 13:15 ` 2.6.1-mm4 Prakash K. Cheemplavam
@ 2004-02-12 16:11 ` Prakash K. Cheemplavam
0 siblings, 0 replies; 68+ messages in thread
From: Prakash K. Cheemplavam @ 2004-02-12 16:11 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: linux-kernel
Prakash K. Cheemplavam wrote:
> Valdis.Kletnieks@vt.edu wrote:
>
>> On Thu, 12 Feb 2004 08:30:54 +0100, "Prakash K. Cheemplavam" said:
>>
>>
>>> Well, I don't know whether my system actually locks up, it is like it
>>> seems the log gets flooded (when I wait long enough) but I cannot do
>>> anything with the system at that point, ie it seems like frozen.
>>
>>
>>
>> I don't think anybody's going to be able to shoot that bug report
>> without more
>> info. "seems like frozen" doesn't give us much to go on. Does the
>> machine
>> still ping/ssh/etc on the net? Is it totally locked up? Any disk
>> activity
>> lights left on/flickering, indicating life? Can you get a serial
>> console or
>> kgdb-ethernet or something to see if there's an oops/panic?
>
>
> Hmm, I'll test those bk-snapshots and when it locks up, I'll try to
So, I tried 2.6.2-rc1-bk1 and it locks up. How can I find out which
patches it incorporated, so that I can filter out that bugger? (more see
down, this time it was type 2)
I dunno about kgdb-ethernet (but I'll see whether I'll understand it)
nor do I have a serial console.
> Maybe it is a nforce2 issue then. I think it is ACPI specific. I'll also
> try compiling latest kernel without ACPI and report back.
I tried 2.6.3-rc1-mm1 without ACPI and it lock up up (type 1). I now can
tell about two type of lock-up (maybe due to the same cause):
1) complete freeze, nothing possible, not able to read machine from
network, must use reset button
2) freeze, but only mouse movement (nothing reacts though, keyboard
neither) is possibel and log is flooded with error I posted, I can still
reach machine via network and do a gracefull shutdown (killing X wasn't
passible)
Prakash
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-02-12 8:46 ` 2.6.1-mm4 Valdis.Kletnieks
@ 2004-02-12 13:15 ` Prakash K. Cheemplavam
2004-02-12 16:11 ` 2.6.1-mm4 Prakash K. Cheemplavam
0 siblings, 1 reply; 68+ messages in thread
From: Prakash K. Cheemplavam @ 2004-02-12 13:15 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: linux-kernel
Valdis.Kletnieks@vt.edu wrote:
> On Thu, 12 Feb 2004 08:30:54 +0100, "Prakash K. Cheemplavam" said:
>
>
>>Well, I don't know whether my system actually locks up, it is like it
>>seems the log gets flooded (when I wait long enough) but I cannot do
>>anything with the system at that point, ie it seems like frozen.
>
>
> I don't think anybody's going to be able to shoot that bug report without more
> info. "seems like frozen" doesn't give us much to go on. Does the machine
> still ping/ssh/etc on the net? Is it totally locked up? Any disk activity
> lights left on/flickering, indicating life? Can you get a serial console or
> kgdb-ethernet or something to see if there's an oops/panic?
Hmm, I'll test those bk-snapshots and when it locks up, I'll try to
access the pc form another machine. As I said it seems (when I wait long
enough, within the first minute nothing in the log survives the reboot,
probably due to reiserfs journalling) the log writes the oops I posted
in the first message infinite times.
> Well, the 53.36 drivers are rock-solid on my Dell laptop with a GeForce4 440Go
> and the 2.6.3-rc1-mm1 kernel. There very well may be bugs in there, but
> they're not ones I can replicate or diagnose...
Maybe it is a nforce2 issue then. I think it is ACPI specific. I'll also
try compiling latest kernel without ACPI and report back.
Thanx,
Prakash
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-02-12 7:30 ` 2.6.1-mm4 Prakash K. Cheemplavam
@ 2004-02-12 8:46 ` Valdis.Kletnieks
2004-02-12 13:15 ` 2.6.1-mm4 Prakash K. Cheemplavam
0 siblings, 1 reply; 68+ messages in thread
From: Valdis.Kletnieks @ 2004-02-12 8:46 UTC (permalink / raw)
To: Prakash K. Cheemplavam; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
On Thu, 12 Feb 2004 08:30:54 +0100, "Prakash K. Cheemplavam" said:
> Well, I don't know whether my system actually locks up, it is like it
> seems the log gets flooded (when I wait long enough) but I cannot do
> anything with the system at that point, ie it seems like frozen.
I don't think anybody's going to be able to shoot that bug report without more
info. "seems like frozen" doesn't give us much to go on. Does the machine
still ping/ssh/etc on the net? Is it totally locked up? Any disk activity
lights left on/flickering, indicating life? Can you get a serial console or
kgdb-ethernet or something to see if there's an oops/panic?
> Furthermore I am using latest 53.36 drivers and I am not the only one
> having this problem if I look into nvnews forums. As I said this is a
> problem which came with something changed in the newer kernels. 2.6.1
> (and 2.6.2-rc1) works OK for me, 2.6.2-rc2 and later not.
Well, the 53.36 drivers are rock-solid on my Dell laptop with a GeForce4 440Go
and the 2.6.3-rc1-mm1 kernel. There very well may be bugs in there, but
they're not ones I can replicate or diagnose...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-02-12 5:52 ` 2.6.1-mm4 Valdis.Kletnieks
@ 2004-02-12 7:30 ` Prakash K. Cheemplavam
2004-02-12 8:46 ` 2.6.1-mm4 Valdis.Kletnieks
0 siblings, 1 reply; 68+ messages in thread
From: Prakash K. Cheemplavam @ 2004-02-12 7:30 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: linux-kernel
Valdis.Kletnieks@vt.edu wrote:
> On Wed, 11 Feb 2004 23:22:36 +0100, "Prakash K. Cheemplavam" said:
>
>
>>>If this is the NVidia graphics driver, it's been doing it at least since 2.
>
> 5.6something,
>
>>>at least that I've seen. It's basically calling pci_find_slot in an interr
>
> upt context,
>
>>>which ends up calling pci_find_subsys which complains about it. One possib
>
> le
>
>>>solution would be for the code to be changed to call pci_find_slot during m
>
> odule
>
>>>initialization and save the return value, and use that instead. Yes, I kno
>
> w this
>
>>>prevents hotplugging. Who hotplugs graphics cards? ;)
>>
>>Could you advise me how to make a dirty hack to get this going? Once
>>again I am back to 2.6.1-rc1 kernel, which seems to be the last one
>>stable for me. 2.6.3-rc1-mm1 locked up quite fast..
>
>
> 1) 'badness in pci_find_subsys' is a warning only. If your system is
> locking up, there's something else at issue, probably.
>
> 2) NVidia released the 5336 level of drivers, which apparently have been
> fixed to support 2.6 without the warning being triggered.
Well, I don't know whether my system actually locks up, it is like it
seems the log gets flooded (when I wait long enough) but I cannot do
anything with the system at that point, ie it seems like frozen.
Furthermore I am using latest 53.36 drivers and I am not the only one
having this problem if I look into nvnews forums. As I said this is a
problem which came with something changed in the newer kernels. 2.6.1
(and 2.6.2-rc1) works OK for me, 2.6.2-rc2 and later not.
Prakash
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-02-11 22:22 ` 2.6.1-mm4 Prakash K. Cheemplavam
@ 2004-02-12 5:52 ` Valdis.Kletnieks
2004-02-12 7:30 ` 2.6.1-mm4 Prakash K. Cheemplavam
0 siblings, 1 reply; 68+ messages in thread
From: Valdis.Kletnieks @ 2004-02-12 5:52 UTC (permalink / raw)
To: Prakash K. Cheemplavam; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On Wed, 11 Feb 2004 23:22:36 +0100, "Prakash K. Cheemplavam" said:
> > If this is the NVidia graphics driver, it's been doing it at least since 2.
5.6something,
> > at least that I've seen. It's basically calling pci_find_slot in an interr
upt context,
> > which ends up calling pci_find_subsys which complains about it. One possib
le
> > solution would be for the code to be changed to call pci_find_slot during m
odule
> > initialization and save the return value, and use that instead. Yes, I kno
w this
> > prevents hotplugging. Who hotplugs graphics cards? ;)
>
> Could you advise me how to make a dirty hack to get this going? Once
> again I am back to 2.6.1-rc1 kernel, which seems to be the last one
> stable for me. 2.6.3-rc1-mm1 locked up quite fast..
1) 'badness in pci_find_subsys' is a warning only. If your system is
locking up, there's something else at issue, probably.
2) NVidia released the 5336 level of drivers, which apparently have been
fixed to support 2.6 without the warning being triggered.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 19:20 ` 2.6.1-mm4 Valdis.Kletnieks
@ 2004-02-11 22:22 ` Prakash K. Cheemplavam
2004-02-12 5:52 ` 2.6.1-mm4 Valdis.Kletnieks
0 siblings, 1 reply; 68+ messages in thread
From: Prakash K. Cheemplavam @ 2004-02-11 22:22 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: linux-kernel
Valdis.Kletnieks@vt.edu wrote:
> On Wed, 21 Jan 2004 19:46:32 +0100, "Prakash K. Cheemplavam" said:
>
>>Ok, here is the stack backtrace:
>>
>>I hope it helps, otherwise I could try compiling in frame-pointers. (I
>>used another logger to get this...)
>>
>>Is it nvidia driver doing something bad (which earlier kernels didn't do)?
>>
>>Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
>>drivers/pci/search.c:132
>>Jan 21 19:25:39 tachyon Call Trace:
>>Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
>>Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
>>Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
>
>
> If this is the NVidia graphics driver, it's been doing it at least since 2.5.6something,
> at least that I've seen. It's basically calling pci_find_slot in an interrupt context,
> which ends up calling pci_find_subsys which complains about it. One possible
> solution would be for the code to be changed to call pci_find_slot during module
> initialization and save the return value, and use that instead. Yes, I know this
> prevents hotplugging. Who hotplugs graphics cards? ;)
Could you advise me how to make a dirty hack to get this going? Once
again I am back to 2.6.1-rc1 kernel, which seems to be the last one
stable for me. 2.6.3-rc1-mm1 locked up quite fast..
Perhaps it would also help to test the snapshots between rc1 and rc2 to
find out which patch borked for me... I see 6 bk versions. Are these
just incremental patches?
Prakash
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-21 18:46 ` 2.6.1-mm4 Prakash K. Cheemplavam
(?)
@ 2004-01-21 19:20 ` Valdis.Kletnieks
2004-02-11 22:22 ` 2.6.1-mm4 Prakash K. Cheemplavam
-1 siblings, 1 reply; 68+ messages in thread
From: Valdis.Kletnieks @ 2004-01-21 19:20 UTC (permalink / raw)
To: Prakash K. Cheemplavam; +Cc: Andrew Morton, linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Wed, 21 Jan 2004 19:46:32 +0100, "Prakash K. Cheemplavam" said:
> Ok, here is the stack backtrace:
>
> I hope it helps, otherwise I could try compiling in frame-pointers. (I
> used another logger to get this...)
>
> Is it nvidia driver doing something bad (which earlier kernels didn't do)?
>
> Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
> drivers/pci/search.c:132
> Jan 21 19:25:39 tachyon Call Trace:
> Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
> Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
> Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
If this is the NVidia graphics driver, it's been doing it at least since 2.5.6something,
at least that I've seen. It's basically calling pci_find_slot in an interrupt context,
which ends up calling pci_find_subsys which complains about it. One possible
solution would be for the code to be changed to call pci_find_slot during module
initialization and save the return value, and use that instead. Yes, I know this
prevents hotplugging. Who hotplugs graphics cards? ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 9:34 ` 2.6.1-mm4 Prakash K. Cheemplavam
@ 2004-01-21 18:46 ` Prakash K. Cheemplavam
-1 siblings, 0 replies; 68+ messages in thread
From: Prakash K. Cheemplavam @ 2004-01-21 18:46 UTC (permalink / raw)
To: Prakash K. Cheemplavam; +Cc: Andrew Morton, linux-kernel, linux-mm
Ok, here is the stack backtrace:
I hope it helps, otherwise I could try compiling in frame-pointers. (I
used another logger to get this...)
Is it nvidia driver doing something bad (which earlier kernels didn't do)?
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa10ffb5>] _nv000816rm+0x2f5/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa077c9d>] _nv003795rm+0x4d9/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<fa0964ff>] _nv001613rm+0x6f/0x7c [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa07a8fd>] _nv003797rm+0xa9/0x128 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e7341>] _nv001490rm+0x55/0xe4 [nvidia]
Jan 21 19:25:39 tachyon [<fa10fff4>] _nv000816rm+0x334/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa077c9d>] _nv003795rm+0x4d9/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa10ffb5>] _nv000816rm+0x2f5/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa077eae>] _nv003795rm+0x6ea/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<fa0964ff>] _nv001613rm+0x6f/0x7c [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa07a8fd>] _nv003797rm+0xa9/0x128 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e7341>] _nv001490rm+0x55/0xe4 [nvidia]
Jan 21 19:25:39 tachyon [<fa10fff4>] _nv000816rm+0x334/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa077eae>] _nv003795rm+0x6ea/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa10ffb5>] _nv000816rm+0x2f5/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa07802b>] _nv003795rm+0x867/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<fa0964ff>] _nv001613rm+0x6f/0x7c [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa07a8fd>] _nv003797rm+0xa9/0x128 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e7341>] _nv001490rm+0x55/0xe4 [nvidia]
Jan 21 19:25:39 tachyon [<fa10fff4>] _nv000816rm+0x334/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa07802b>] _nv003795rm+0x867/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
@ 2004-01-21 18:46 ` Prakash K. Cheemplavam
0 siblings, 0 replies; 68+ messages in thread
From: Prakash K. Cheemplavam @ 2004-01-21 18:46 UTC (permalink / raw)
To: Prakash K. Cheemplavam; +Cc: Andrew Morton, linux-kernel, linux-mm
Ok, here is the stack backtrace:
I hope it helps, otherwise I could try compiling in frame-pointers. (I
used another logger to get this...)
Is it nvidia driver doing something bad (which earlier kernels didn't do)?
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa10ffb5>] _nv000816rm+0x2f5/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa077c9d>] _nv003795rm+0x4d9/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<fa0964ff>] _nv001613rm+0x6f/0x7c [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa07a8fd>] _nv003797rm+0xa9/0x128 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e7341>] _nv001490rm+0x55/0xe4 [nvidia]
Jan 21 19:25:39 tachyon [<fa10fff4>] _nv000816rm+0x334/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa077c9d>] _nv003795rm+0x4d9/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa10ffb5>] _nv000816rm+0x2f5/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa077eae>] _nv003795rm+0x6ea/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<fa0964ff>] _nv001613rm+0x6f/0x7c [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa07a8fd>] _nv003797rm+0xa9/0x128 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e7341>] _nv001490rm+0x55/0xe4 [nvidia]
Jan 21 19:25:39 tachyon [<fa10fff4>] _nv000816rm+0x334/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa077eae>] _nv003795rm+0x6ea/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa10ffb5>] _nv000816rm+0x2f5/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa07802b>] _nv003795rm+0x867/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
Jan 21 19:25:39 tachyon Badness in pci_find_subsys at
drivers/pci/search.c:132
Jan 21 19:25:39 tachyon Call Trace:
Jan 21 19:25:39 tachyon [<c027a7f8>] pci_find_subsys+0xe8/0xf0
Jan 21 19:25:39 tachyon [<c027a82f>] pci_find_device+0x2f/0x40
Jan 21 19:25:39 tachyon [<c027a6e8>] pci_find_slot+0x28/0x50
Jan 21 19:25:39 tachyon [<f9faf9f9>] os_pci_init_handle+0x35/0x62 [nvidia]
Jan 21 19:25:39 tachyon [<fa0964ff>] _nv001613rm+0x6f/0x7c [nvidia]
Jan 21 19:25:39 tachyon [<f9fc978f>] _nv001243rm+0x1f/0x24 [nvidia]
Jan 21 19:25:39 tachyon [<fa07a8fd>] _nv003797rm+0xa9/0x128 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e7341>] _nv001490rm+0x55/0xe4 [nvidia]
Jan 21 19:25:39 tachyon [<fa10fff4>] _nv000816rm+0x334/0x384 [nvidia]
Jan 21 19:25:39 tachyon [<fa0787cc>] _nv003801rm+0xd8/0x100 [nvidia]
Jan 21 19:25:39 tachyon [<fa10faef>] _nv000809rm+0x2f/0x34 [nvidia]
Jan 21 19:25:39 tachyon [<fa0795f0>] _nv003816rm+0xf0/0x104 [nvidia]
Jan 21 19:25:39 tachyon [<fa07802b>] _nv003795rm+0x867/0xaec [nvidia]
Jan 21 19:25:39 tachyon [<f9fe2197>] _nv004046rm+0x3a3/0x3b0 [nvidia]
Jan 21 19:25:39 tachyon [<fa0e3a47>] _nv001476rm+0x277/0x45c [nvidia]
Jan 21 19:25:39 tachyon [<f9fcc2ca>] _nv000896rm+0x4a/0x64 [nvidia]
Jan 21 19:25:39 tachyon [<f9fcdae4>] rm_isr_bh+0xc/0x10 [nvidia]
Jan 21 19:25:39 tachyon [<f9facd93>] nv_kern_isr_bh+0x11/0x15 [nvidia]
Jan 21 19:25:39 tachyon [<c0126576>] tasklet_action+0x46/0x70
Jan 21 19:25:39 tachyon [<c0126390>] do_softirq+0x90/0xa0
Jan 21 19:25:39 tachyon [<c010cced>] do_IRQ+0xfd/0x130
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c03f77d4>] common_interrupt+0x18/0x20
Jan 21 19:25:39 tachyon [<c0107000>] rest_init+0x0/0x60
Jan 21 19:25:39 tachyon [<c0109053>] default_idle+0x23/0x30
Jan 21 19:25:39 tachyon [<c01090bc>] cpu_idle+0x2c/0x40
Jan 21 19:25:39 tachyon [<c05026dc>] start_kernel+0x17c/0x1b0
Jan 21 19:25:39 tachyon [<c0502430>] unknown_bootoption+0x0/0x100
Jan 21 19:25:39 tachyon
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-20 0:57 ` 2.6.1-mm4 Andrew Morton
@ 2004-01-20 2:13 ` Thomas Molina
-1 siblings, 0 replies; 68+ messages in thread
From: Thomas Molina @ 2004-01-20 2:13 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
On Mon, 19 Jan 2004, Andrew Morton wrote:
> > Cannot open master raw device '/dev/rawctl' (No such device)
>
> Do you have
>
> alias char-major-162 raw
>
> in /etc/modprobe.conf?
I added that and got the same message on the next reboot. I don't get
this on the 2.4 RedHat kernel. I will have to do a bk pull for 2.6 since
I have been running mm kernels exclusively lately.
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
@ 2004-01-20 2:13 ` Thomas Molina
0 siblings, 0 replies; 68+ messages in thread
From: Thomas Molina @ 2004-01-20 2:13 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
On Mon, 19 Jan 2004, Andrew Morton wrote:
> > Cannot open master raw device '/dev/rawctl' (No such device)
>
> Do you have
>
> alias char-major-162 raw
>
> in /etc/modprobe.conf?
I added that and got the same message on the next reboot. I don't get
this on the 2.4 RedHat kernel. I will have to do a bk pull for 2.6 since
I have been running mm kernels exclusively lately.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-20 0:26 ` 2.6.1-mm4 Thomas Molina
@ 2004-01-20 0:57 ` Andrew Morton
-1 siblings, 0 replies; 68+ messages in thread
From: Andrew Morton @ 2004-01-20 0:57 UTC (permalink / raw)
To: Thomas Molina; +Cc: linux-kernel, linux-mm
Thomas Molina <tmolina@cablespeed.com> wrote:
>
> Rusty,
>
> I updated mm4 with the patch you sent in response to my shutdown oops
> report and haven't received a repeat oops in six reboots. Hopefully this
> cures my problem. I previously couldn't reproduce the oops every single
> reboot.
>
> I do have a couple of other anomalies to report though.
>
> First is this snippet from my bootup log:
>
> Cannot open master raw device '/dev/rawctl' (No such device)
Do you have
alias char-major-162 raw
in /etc/modprobe.conf?
> WARNING: /lib/modules/2.6.1-mm4a/kernel/fs/nfsd/nfsd.ko needs unknown
> symbol dnotify_parent
>
Yup, this is fixed and it's all merged up.
diff -puN fs/dnotify.c~nfsd-04-add-dnotify-events-fix fs/dnotify.c
--- 25/fs/dnotify.c~nfsd-04-add-dnotify-events-fix 2004-01-16 08:42:25.000000000 -0800
+++ 25-akpm/fs/dnotify.c 2004-01-16 08:42:45.000000000 -0800
@@ -165,6 +165,7 @@ void dnotify_parent(struct dentry *dentr
spin_unlock(&dentry->d_lock);
}
}
+EXPORT_SYMBOL_GPL(dnotify_parent);
static int __init dnotify_init(void)
{
_
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
@ 2004-01-20 0:57 ` Andrew Morton
0 siblings, 0 replies; 68+ messages in thread
From: Andrew Morton @ 2004-01-20 0:57 UTC (permalink / raw)
To: Thomas Molina; +Cc: linux-kernel, linux-mm
Thomas Molina <tmolina@cablespeed.com> wrote:
>
> Rusty,
>
> I updated mm4 with the patch you sent in response to my shutdown oops
> report and haven't received a repeat oops in six reboots. Hopefully this
> cures my problem. I previously couldn't reproduce the oops every single
> reboot.
>
> I do have a couple of other anomalies to report though.
>
> First is this snippet from my bootup log:
>
> Cannot open master raw device '/dev/rawctl' (No such device)
Do you have
alias char-major-162 raw
in /etc/modprobe.conf?
> WARNING: /lib/modules/2.6.1-mm4a/kernel/fs/nfsd/nfsd.ko needs unknown
> symbol dnotify_parent
>
Yup, this is fixed and it's all merged up.
diff -puN fs/dnotify.c~nfsd-04-add-dnotify-events-fix fs/dnotify.c
--- 25/fs/dnotify.c~nfsd-04-add-dnotify-events-fix 2004-01-16 08:42:25.000000000 -0800
+++ 25-akpm/fs/dnotify.c 2004-01-16 08:42:45.000000000 -0800
@@ -165,6 +165,7 @@ void dnotify_parent(struct dentry *dentr
spin_unlock(&dentry->d_lock);
}
}
+EXPORT_SYMBOL_GPL(dnotify_parent);
static int __init dnotify_init(void)
{
_
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
@ 2004-01-20 0:26 ` Thomas Molina
-1 siblings, 0 replies; 68+ messages in thread
From: Thomas Molina @ 2004-01-20 0:26 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Rusty,
I updated mm4 with the patch you sent in response to my shutdown oops
report and haven't received a repeat oops in six reboots. Hopefully this
cures my problem. I previously couldn't reproduce the oops every single
reboot.
I do have a couple of other anomalies to report though.
First is this snippet from my bootup log:
Cannot open master raw device '/dev/rawctl' (No such device)
/: clean, 192622/1196032 files, 969619/2390842 blocks
[ OK ]
cat: /sys//devices/pci0000:00/0000:00:07.2/usb1/bNumConfigurations: No
such file or directory
/etc/hotplug/usb.agent: line 144: [: too many arguments
Remounting root filesystem in read-write mode: [ OK ]
Activating swap partitions: [ OK ]
Finding module dependencies: [ OK ]
Second is that I receive the following error while compiling mm4:
Kernel: arch/i386/boot/bzImage is ready
sh /usr/local/kernel/linux-2.6.0/arch/i386/boot/install.sh 2.6.1-mm4a
arch/i386/boot/bzImage System.map ""
WARNING: /lib/modules/2.6.1-mm4a/kernel/fs/nfsd/nfsd.ko needs unknown
symbol dnotify_parent
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
@ 2004-01-20 0:26 ` Thomas Molina
0 siblings, 0 replies; 68+ messages in thread
From: Thomas Molina @ 2004-01-20 0:26 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Rusty,
I updated mm4 with the patch you sent in response to my shutdown oops
report and haven't received a repeat oops in six reboots. Hopefully this
cures my problem. I previously couldn't reproduce the oops every single
reboot.
I do have a couple of other anomalies to report though.
First is this snippet from my bootup log:
Cannot open master raw device '/dev/rawctl' (No such device)
/: clean, 192622/1196032 files, 969619/2390842 blocks
[ OK ]
cat: /sys//devices/pci0000:00/0000:00:07.2/usb1/bNumConfigurations: No
such file or directory
/etc/hotplug/usb.agent: line 144: [: too many arguments
Remounting root filesystem in read-write mode: [ OK ]
Activating swap partitions: [ OK ]
Finding module dependencies: [ OK ]
Second is that I receive the following error while compiling mm4:
Kernel: arch/i386/boot/bzImage is ready
sh /usr/local/kernel/linux-2.6.0/arch/i386/boot/install.sh 2.6.1-mm4a
arch/i386/boot/bzImage System.map ""
WARNING: /lib/modules/2.6.1-mm4a/kernel/fs/nfsd/nfsd.ko needs unknown
symbol dnotify_parent
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
@ 2004-01-19 11:46 ` Luiz Fernando Capitulino
-1 siblings, 0 replies; 68+ messages in thread
From: Luiz Fernando Capitulino @ 2004-01-19 11:46 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Hi Andrew,
Em Sex, 2004-01-16 às 04:59, Andrew Morton escreveu:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
I got this today, after an '# shutdown -r now':
EFLAGS: 00010082
EIP is at __tasklet_schedule+0x35/0x50
eax: c48d0000 ebx: 00000046 ecx: 0000009d edx: c7fb99d0
esi: c201b9d0 edi: 00000000 ebp: c48d1ebc esp: c48d1eb8
ds: 007b es: 007b ss: 0068
Process rc (pid: 11596, threadinfo=c48d0000 task=c201b9d0)
Stack: 00000000 c48d1ee8 c0117c34 00000000 00000000 0e5fb9c6 03acf444 27263b42
0000ea8d c76029d0 c48d0000 00000000 c48d1f00 c011742d 00000000 00000000
01200011 c76029d0 c48d1f4c c011a81d 00000000 01200011 bffff614 00000000
Call Trace:
[<c0117c34>] scheduler_tick+0x564/0x580
[<c011742d>] sched_fork+0x7d/0x80
[<c011a81d>] copy_process+0x5dd/0x9e0
[<c011ac6d>] do_fork+0x4d/0x17a
[<c0125f3d>] sigprocmask+0x4d/0xc0
[<c0109af5>] sys_clone+0x45/0x50
[<c0301723>] syscall_call+0x7/0xb
Code: 3a 35 c0 89 10 83 0d 40 51 3f c0 20 a3 14 3a 35 c0 b8 00 e0 ff ff 21 e0 f7
40 14 00 ff ff 00 75 10 8b 15 60 52 3f c0 85 d2 74 06 <8b> 02 85 c0 75 05 53 9d
5b 5d c3 89 d0 e8 f9 84 ff ff eb f2 8d
--
Luiz Fernando N. Capitulino
<lcapitulino@prefeitura.sp.gov.br>
<http://www.telecentros.sp.gov.br>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
@ 2004-01-19 11:46 ` Luiz Fernando Capitulino
0 siblings, 0 replies; 68+ messages in thread
From: Luiz Fernando Capitulino @ 2004-01-19 11:46 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Hi Andrew,
Em Sex, 2004-01-16 as 04:59, Andrew Morton escreveu:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
I got this today, after an '# shutdown -r now':
EFLAGS: 00010082
EIP is at __tasklet_schedule+0x35/0x50
eax: c48d0000 ebx: 00000046 ecx: 0000009d edx: c7fb99d0
esi: c201b9d0 edi: 00000000 ebp: c48d1ebc esp: c48d1eb8
ds: 007b es: 007b ss: 0068
Process rc (pid: 11596, threadinfo=c48d0000 task=c201b9d0)
Stack: 00000000 c48d1ee8 c0117c34 00000000 00000000 0e5fb9c6 03acf444 27263b42
0000ea8d c76029d0 c48d0000 00000000 c48d1f00 c011742d 00000000 00000000
01200011 c76029d0 c48d1f4c c011a81d 00000000 01200011 bffff614 00000000
Call Trace:
[<c0117c34>] scheduler_tick+0x564/0x580
[<c011742d>] sched_fork+0x7d/0x80
[<c011a81d>] copy_process+0x5dd/0x9e0
[<c011ac6d>] do_fork+0x4d/0x17a
[<c0125f3d>] sigprocmask+0x4d/0xc0
[<c0109af5>] sys_clone+0x45/0x50
[<c0301723>] syscall_call+0x7/0xb
Code: 3a 35 c0 89 10 83 0d 40 51 3f c0 20 a3 14 3a 35 c0 b8 00 e0 ff ff 21 e0 f7
40 14 00 ff ff 00 75 10 8b 15 60 52 3f c0 85 d2 74 06 <8b> 02 85 c0 75 05 53 9d
5b 5d c3 89 d0 e8 f9 84 ff ff eb f2 8d
--
Luiz Fernando N. Capitulino
<lcapitulino@prefeitura.sp.gov.br>
<http://www.telecentros.sp.gov.br>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-18 8:17 ` 2.6.1-mm4 Andrew Morton
@ 2004-01-19 11:42 ` Rusty Russell
0 siblings, 0 replies; 68+ messages in thread
From: Rusty Russell @ 2004-01-19 11:42 UTC (permalink / raw)
To: Andrew Morton; +Cc: jamagallon, linux-kernel, netdev
On Sun, 18 Jan 2004 00:17:08 -0800
Andrew Morton <akpm@osdl.org> wrote:
> Presumably, recent gcc's remove the variable altogether and just expand the
> constant inline. When the central module code checks for the parameter's
> existence in the module's symbol table it errors out.
MODULE_PARM considered harmful.
Unfortunately, there's no easy way of fixing this, since MODULE_PARM()
is often used on variables which aren't declared yet 8(. (I tried this
in an early patch).
Migrating to module_param() is the Right Thing here IMHO, which actually
takes the damn address,
Rusty.
--
there are those who do and those who hang on and you don't see too
many doers quoting their contemporaries. -- Larry McVoy
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-17 18:52 ` 2.6.1-mm4 Andrew Morton
2004-01-19 7:16 ` 2.6.1-mm4 Rusty Russell
@ 2004-01-19 11:29 ` Rusty Russell
1 sibling, 0 replies; 68+ messages in thread
From: Rusty Russell @ 2004-01-19 11:29 UTC (permalink / raw)
To: Andrew Morton; +Cc: Hugh Dickins, tmolina, linux-kernel
In message <20040117105239.0b94f2b3.akpm@osdl.org> you write:
> Yes. ksoftirqd and the migration threads can now be killed off
> with `kill -9'.
Fix below.
Thanks,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
Name: Block Signals For Early Kthreads
Author: Rusty Russell
Status: Booted on 2.6.1-bk4
Depends: Hotcpu-New-Kthread/use-kthread-simple.patch.gz
D: Kthreads created at boot before "keventd" are spawned directly.
D: However, this means that they don't have all signals blocked, and
D: hence can be killed. The simplest solution is to always explicitly
D: block all signals in the kthread.
diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal .29870-linux-2.6.1-mm4/kernel/kthread.c .29870-linux-2.6.1-mm4.updated/kernel/kthread.c
--- .29870-linux-2.6.1-mm4/kernel/kthread.c 2004-01-19 18:12:53.000000000 +1100
+++ .29870-linux-2.6.1-mm4.updated/kernel/kthread.c 2004-01-19 21:45:53.000000000 +1100
@@ -32,12 +32,18 @@ static int kthread(void *_create)
struct kthread_create_info *create = _create;
int (*threadfn)(void *data);
void *data;
+ sigset_t blocked;
int ret = -EINTR;
/* Copy data: it's on keventd's stack */
threadfn = create->threadfn;
data = create->data;
+ /* Block and flush all signals (in case we're not from keventd). */
+ sigfillset(&blocked);
+ sigprocmask(SIG_BLOCK, &blocked, NULL);
+ flush_signals(current);
+
/* OK, tell user we're spawned, wait for stop or wakeup */
__set_current_state(TASK_INTERRUPTIBLE);
complete(&create->started);
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-17 18:52 ` 2.6.1-mm4 Andrew Morton
@ 2004-01-19 7:16 ` Rusty Russell
2004-01-19 11:29 ` 2.6.1-mm4 Rusty Russell
1 sibling, 0 replies; 68+ messages in thread
From: Rusty Russell @ 2004-01-19 7:16 UTC (permalink / raw)
To: Andrew Morton; +Cc: Hugh Dickins, tmolina, linux-kernel
In message <20040117105239.0b94f2b3.akpm@osdl.org> you write:
> Hugh Dickins <hugh@veritas.com> wrote:
> > I was getting something like that on reboot a few days ago, I think it
> > was with 2.6.1-mm2. I had to move on before debugging it fully, but
> > the impression I got (maybe vile calumny, sue me Rusty) was that the
> > new kthread_create for 2.6.1-mm's ksoftirqd was leaving it vulnerable
> > to shutdown kill, whereas other things (RCU in my traces) still needed
> > it around and assumed its task address still valid.
>
> Yes. ksoftirqd and the migration threads can now be killed off
> with `kill -9'.
"That shouldn't happen".
We block and flush all signals in workqueue.c. How is that kill -9
getting through?
It also implies that previously ksoftirqd and migration threads would
tight spin after kill -9, since they slept with TASK_INTERRUPTIBLE.
Will dig...
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-18 8:11 ` 2.6.1-mm4 J.A. Magallon
@ 2004-01-18 8:17 ` Andrew Morton
2004-01-19 11:42 ` 2.6.1-mm4 Rusty Russell
0 siblings, 1 reply; 68+ messages in thread
From: Andrew Morton @ 2004-01-18 8:17 UTC (permalink / raw)
To: J.A. Magallon; +Cc: linux-kernel, netdev
"J.A. Magallon" <jamagallon@able.es> wrote:
>
>
> On 01.18, Andrew Morton wrote:
> > "J.A. Magallon" <jamagallon@able.es> wrote:
> > >
> > > On 01.16, Andrew Morton wrote:
> > > >
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
> > > >
> > > >
> > >
> > > Net driver problem:
> > >
> > > werewolf:/etc# modprobe --verbose 3c59x
> > > insmod /lib/modules/2.6.1-jam4/kernel/drivers/net/3c59x.ko
> > > FATAL: Error inserting 3c59x (/lib/modules/2.6.1-jam4/kernel/drivers/net/3c59x.ko): Invalid argument
> >
> > hmm, cute.
> >
>
> Yes.
> It worked.
> I thought of this, but why this and not the other parameters ? Compiler bug ?
Presumably, recent gcc's remove the variable altogether and just expand the
constant inline. When the central module code checks for the parameter's
existence in the module's symbol table it errors out.
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-18 5:55 ` 2.6.1-mm4 Andrew Morton
@ 2004-01-18 8:11 ` J.A. Magallon
2004-01-18 8:17 ` 2.6.1-mm4 Andrew Morton
0 siblings, 1 reply; 68+ messages in thread
From: J.A. Magallon @ 2004-01-18 8:11 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, netdev
On 01.18, Andrew Morton wrote:
> "J.A. Magallon" <jamagallon@able.es> wrote:
> >
> > On 01.16, Andrew Morton wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
> > >
> > >
> >
> > Net driver problem:
> >
> > werewolf:/etc# modprobe --verbose 3c59x
> > insmod /lib/modules/2.6.1-jam4/kernel/drivers/net/3c59x.ko
> > FATAL: Error inserting 3c59x (/lib/modules/2.6.1-jam4/kernel/drivers/net/3c59x.ko): Invalid argument
>
> hmm, cute.
>
Yes.
It worked.
I thought of this, but why this and not the other parameters ? Compiler bug ?
Witches...
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrake Linux release 10.0 (Cooker) for i586
Linux 2.6.1-jam4 (gcc 3.3.2 (Mandrake Linux 10.0 3.3.2-4mdk))
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-18 0:12 ` 2.6.1-mm4 J.A. Magallon
@ 2004-01-18 5:55 ` Andrew Morton
2004-01-18 8:11 ` 2.6.1-mm4 J.A. Magallon
0 siblings, 1 reply; 68+ messages in thread
From: Andrew Morton @ 2004-01-18 5:55 UTC (permalink / raw)
To: J.A. Magallon; +Cc: linux-kernel, netdev
"J.A. Magallon" <jamagallon@able.es> wrote:
>
> On 01.16, Andrew Morton wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
> >
> >
>
> Net driver problem:
>
> werewolf:/etc# modprobe --verbose 3c59x
> insmod /lib/modules/2.6.1-jam4/kernel/drivers/net/3c59x.ko
> FATAL: Error inserting 3c59x (/lib/modules/2.6.1-jam4/kernel/drivers/net/3c59x.ko): Invalid argument
hmm, cute.
--- 25/drivers/net/3c59x.c~3c59x-modprobe-fix 2004-01-17 21:49:14.000000000 -0800
+++ 25-akpm/drivers/net/3c59x.c 2004-01-17 21:49:18.000000000 -0800
@@ -211,11 +211,11 @@
/* Set the copy breakpoint for the copy-only-tiny-frames scheme.
Setting to > 1512 effectively disables this feature. */
#ifndef __arm__
-static const int rx_copybreak = 200;
+static int rx_copybreak = 200;
#else
/* ARM systems perform better by disregarding the bus-master
transfer capability of these cards. -- rmk */
-static const int rx_copybreak = 1513;
+static int rx_copybreak = 1513;
#endif
/* Allow setting MTU to a larger size, bypassing the normal ethernet setup. */
static const int mtu = 1500;
_
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
` (9 preceding siblings ...)
(?)
@ 2004-01-18 0:12 ` J.A. Magallon
2004-01-18 5:55 ` 2.6.1-mm4 Andrew Morton
-1 siblings, 1 reply; 68+ messages in thread
From: J.A. Magallon @ 2004-01-18 0:12 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, netdev
On 01.16, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
>
>
Net driver problem:
werewolf:/etc# modprobe --verbose 3c59x
insmod /lib/modules/2.6.1-jam4/kernel/drivers/net/3c59x.ko
FATAL: Error inserting 3c59x (/lib/modules/2.6.1-jam4/kernel/drivers/net/3c59x.ko): Invalid argument
/var/messages:
Jan 18 01:03:00 werewolf kernel: 3c59x: falsely claims to have parameter rx_copybreak
Hardware:
00:12.0 Ethernet controller: 3Com Corporation 3c980-TX 10/100baseTX NIC [Python-T] (rev 78)
Subsystem: 3Com Corporation: Unknown device 1000
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at ec00 [size=128]
Memory at febfef80 (32-bit, non-prefetchable) [size=128]
Expansion ROM at feba0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
(if you answer from netdev, plz CC: me, I'm not subscribed. thanks)
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrake Linux release 10.0 (Cooker) for i586
Linux 2.6.1-jam4 (gcc 3.3.2 (Mandrake Linux 10.0 3.3.2-4mdk))
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-17 18:14 ` 2.6.1-mm4 Hugh Dickins
@ 2004-01-17 18:52 ` Andrew Morton
2004-01-19 7:16 ` 2.6.1-mm4 Rusty Russell
2004-01-19 11:29 ` 2.6.1-mm4 Rusty Russell
0 siblings, 2 replies; 68+ messages in thread
From: Andrew Morton @ 2004-01-17 18:52 UTC (permalink / raw)
To: Hugh Dickins; +Cc: tmolina, linux-kernel, rusty
Hugh Dickins <hugh@veritas.com> wrote:
>
> > Code: 0a 3c c0 89 10 83 0d 20 0a 3c c0 20 a3 00 0a 3c c0 b8 00 e0 ff ff 21
> > e0 f7 40 14 00 ff ff 00 75 15 8b 15 40 0b 3c c0 85 d2 74 0b <8b> 02 85 c0
> > 75 0a 90 8d 74 26 00 53 9d 5b 5d c3 89 d0 e8 b4 1a
> > <6>note: S01reboot[2352] exited with preempt_count 1
>
> I was getting something like that on reboot a few days ago, I think it
> was with 2.6.1-mm2. I had to move on before debugging it fully, but
> the impression I got (maybe vile calumny, sue me Rusty) was that the
> new kthread_create for 2.6.1-mm's ksoftirqd was leaving it vulnerable
> to shutdown kill, whereas other things (RCU in my traces) still needed
> it around and assumed its task address still valid.
Yes. ksoftirqd and the migration threads can now be killed off
with `kill -9'.
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-17 13:13 2.6.1-mm4 Thomas Molina
@ 2004-01-17 18:14 ` Hugh Dickins
2004-01-17 18:52 ` 2.6.1-mm4 Andrew Morton
0 siblings, 1 reply; 68+ messages in thread
From: Hugh Dickins @ 2004-01-17 18:14 UTC (permalink / raw)
To: Thomas Molina; +Cc: Kernel Mailing List, Rusty Russell, Andrew Morton
On Sat, 17 Jan 2004, Thomas Molina wrote:
> I issued a reboot command under -mm4 and received the following oops some
> time after the "Sending all processes the TERM signal" message. This
> message did not make it into syslog. Following this oops are one
> "sleeping function called from invalid context at
> include/linux/rwsem.h:43" and one "bad: scheduling while atomic!" message.
> Then I get the message "no more processes left in this runlevel", after
> which processing stops. Nothing further appears to happen, but I can
> still use <SHIFT><PAGE [UP|DOWN]> to scroll screen.
>
> I've typed this in by hand so there may be errors. This machine is a
> Presario 12XL325 laptop and does not have a serial port to use as a remote
> console. This oops is reproducable, but does not happen on every reboot.
>
> Unable to handle kernel paging request at virtual address c778c950
> printing eip:
> c0130555
> *pde = 0001a063
> *pte = 0778c000
> Oops: 0000 (#1]
> PREEMPT DEBUG_PAGEALLOC
> CPU: 0
> EIP: 0060:[<c0130555>] Not tainted VLI
> EFLAGS: 00010086
> EIP is at __tasklet_schedule+0x35/0x50
> eax: c6e9c000 ebx: 00000046 ecx: 00000186 edx: c778c950
> esi: 00000000 edi: c6eb6950 ebp: c6e9de74 esp: c6e9de70
> ds: 007b es: 007b ss: 0068
> Process S01reboot (pid: 3322, threadinfo=c6e9c000 task=c6eb6950)
> Stack: 00000000 c6e9dea8 c012267e 00000000 00000000 c2213fc4 c6e9dec0
> 13aaa68c
> 00895486 3f33cb49 00001640 00000000 c6e9c000 401610c8 c6e9dec0
> c012212c
> 00000000 00000000 c2117950 c6eb6fe0 c6e9df20 c0128880 00000000
> 01200011
> Call Trace:
> [<c012267e>] scheduler_tick+0x6e/0x6b0
> [<c012212c>] sched_fork+0xbc/0xe0
> [<c0128880>] copy_process+0x5e0/0xfe0
> [<c01292cd>] do_fork+0x4d/0x1c1
> [<c013bba7>] sigprocmask+0xf7/0x2a0
> [<c017b54a>] generic_file_llseek+0x3a/0xf0
> [<c017bc90>] sys_llseek+0xd0/0x100
> [<c0109cef>] sys_clone+0x3f/0x50
> [<c02ec24a>] sysenter_past_esp+0x43/0x65
>
> Code: 0a 3c c0 89 10 83 0d 20 0a 3c c0 20 a3 00 0a 3c c0 b8 00 e0 ff ff 21
> e0 f7 40 14 00 ff ff 00 75 15 8b 15 40 0b 3c c0 85 d2 74 0b <8b> 02 85 c0
> 75 0a 90 8d 74 26 00 53 9d 5b 5d c3 89 d0 e8 b4 1a
> <6>note: S01reboot[2352] exited with preempt_count 1
I was getting something like that on reboot a few days ago, I think it
was with 2.6.1-mm2. I had to move on before debugging it fully, but
the impression I got (maybe vile calumny, sue me Rusty) was that the
new kthread_create for 2.6.1-mm's ksoftirqd was leaving it vulnerable
to shutdown kill, whereas other things (RCU in my traces) still needed
it around and assumed its task address still valid.
Hope this helps instead of misleading,
Hugh
^ permalink raw reply [flat|nested] 68+ messages in thread
* 2.6.1-mm4
@ 2004-01-17 13:13 Thomas Molina
2004-01-17 18:14 ` 2.6.1-mm4 Hugh Dickins
0 siblings, 1 reply; 68+ messages in thread
From: Thomas Molina @ 2004-01-17 13:13 UTC (permalink / raw)
To: Kernel Mailing List; +Cc: Andrew Morton
I issued a reboot command under -mm4 and received the following oops some
time after the "Sending all processes the TERM signal" message. This
message did not make it into syslog. Following this oops are one
"sleeping function called from invalid context at
include/linux/rwsem.h:43" and one "bad: scheduling while atomic!" message.
Then I get the message "no more processes left in this runlevel", after
which processing stops. Nothing further appears to happen, but I can
still use <SHIFT><PAGE [UP|DOWN]> to scroll screen.
I've typed this in by hand so there may be errors. This machine is a
Presario 12XL325 laptop and does not have a serial port to use as a remote
console. This oops is reproducable, but does not happen on every reboot.
Unable to handle kernel paging request at virtual address c778c950
printing eip:
c0130555
*pde = 0001a063
*pte = 0778c000
Oops: 0000 (#1]
PREEMPT DEBUG_PAGEALLOC
CPU: 0
EIP: 0060:[<c0130555>] Not tainted VLI
EFLAGS: 00010086
EIP is at __tasklet_schedule+0x35/0x50
eax: c6e9c000 ebx: 00000046 ecx: 00000186 edx: c778c950
esi: 00000000 edi: c6eb6950 ebp: c6e9de74 esp: c6e9de70
ds: 007b es: 007b ss: 0068
Process S01reboot (pid: 3322, threadinfo=c6e9c000 task=c6eb6950)
Stack: 00000000 c6e9dea8 c012267e 00000000 00000000 c2213fc4 c6e9dec0
13aaa68c
00895486 3f33cb49 00001640 00000000 c6e9c000 401610c8 c6e9dec0
c012212c
00000000 00000000 c2117950 c6eb6fe0 c6e9df20 c0128880 00000000
01200011
Call Trace:
[<c012267e>] scheduler_tick+0x6e/0x6b0
[<c012212c>] sched_fork+0xbc/0xe0
[<c0128880>] copy_process+0x5e0/0xfe0
[<c01292cd>] do_fork+0x4d/0x1c1
[<c013bba7>] sigprocmask+0xf7/0x2a0
[<c017b54a>] generic_file_llseek+0x3a/0xf0
[<c017bc90>] sys_llseek+0xd0/0x100
[<c0109cef>] sys_clone+0x3f/0x50
[<c02ec24a>] sysenter_past_esp+0x43/0x65
Code: 0a 3c c0 89 10 83 0d 20 0a 3c c0 20 a3 00 0a 3c c0 b8 00 e0 ff ff 21
e0 f7 40 14 00 ff ff 00 75 15 8b 15 40 0b 3c c0 85 d2 74 0b <8b> 02 85 c0
75 0a 90 8d 74 26 00 53 9d 5b 5d c3 89 d0 e8 b4 1a
<6>note: S01reboot[2352] exited with preempt_count 1
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-17 4:05 ` 2.6.1-mm4 Dmitry Torokhov
@ 2004-01-17 4:22 ` Greg Fitzgerald
0 siblings, 0 replies; 68+ messages in thread
From: Greg Fitzgerald @ 2004-01-17 4:22 UTC (permalink / raw)
To: linux-kernel
Dmitry,
psmouse.proto=exps worked perfect. Thanks very much.
--Greg
On (01/16/04 23:05), Dmitry Torokhov wrote:
> To: Greg Fitzgerald <gregf@bigtimegeeks.com>, linux-kernel@vger.kernel.org
> From: Dmitry Torokhov <dtor_core@ameritech.net>
> Date: Fri, 16 Jan 2004 23:05:26 -0500
> Subject: Re: 2.6.1-mm4
>
> On Friday 16 January 2004 08:31 pm, Greg Fitzgerald wrote:
> > Hi,
> >
> > Just gave 2.6.1-mm4 a try hoping to fix my NFS problems. NFS seems
> > to be working better but now my mouse is not working properly. I have
> > psmouse.psmouse_proto=exps in my grub.conf.
> >
>
> Please change it to psmouse.proto=exps
>
> --
> Dmitry
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-17 1:31 ` 2.6.1-mm4 Greg Fitzgerald
2004-01-17 1:40 ` 2.6.1-mm4 Mike Fedyk
2004-01-17 2:24 ` 2.6.1-mm4 Mike Fedyk
@ 2004-01-17 4:05 ` Dmitry Torokhov
2004-01-17 4:22 ` 2.6.1-mm4 Greg Fitzgerald
2 siblings, 1 reply; 68+ messages in thread
From: Dmitry Torokhov @ 2004-01-17 4:05 UTC (permalink / raw)
To: Greg Fitzgerald, linux-kernel
On Friday 16 January 2004 08:31 pm, Greg Fitzgerald wrote:
> Hi,
>
> Just gave 2.6.1-mm4 a try hoping to fix my NFS problems. NFS seems
> to be working better but now my mouse is not working properly. I have
> psmouse.psmouse_proto=exps in my grub.conf.
>
Please change it to psmouse.proto=exps
--
Dmitry
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-17 1:31 ` 2.6.1-mm4 Greg Fitzgerald
2004-01-17 1:40 ` 2.6.1-mm4 Mike Fedyk
@ 2004-01-17 2:24 ` Mike Fedyk
2004-01-17 4:05 ` 2.6.1-mm4 Dmitry Torokhov
2 siblings, 0 replies; 68+ messages in thread
From: Mike Fedyk @ 2004-01-17 2:24 UTC (permalink / raw)
To: Greg Fitzgerald; +Cc: linux-kernel
On Fri, Jan 16, 2004 at 08:31:15PM -0500, Greg Fitzgerald wrote:
> Hi,
>
> Just gave 2.6.1-mm4 a try hoping to fix my NFS problems. NFS seems
> to be working better but now my mouse is not working properly. I have
> psmouse.psmouse_proto=exps in my grub.conf. Anyone have ideas? Thanks in advance.
Are you getting stale filehandle from a 2.6 nfs server?
I'm testing 2.6.1-bk2 + [1] to see if it fixes the trouble I've been having
with that. Maybe you can confirm...
Mike
1. http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/broken-out/nfsd-01-stale-filehandles-fixes.patch
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
@ 2004-01-17 2:22 ` Adrian Bunk
-1 siblings, 0 replies; 68+ messages in thread
From: Adrian Bunk @ 2004-01-17 2:22 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
On Thu, Jan 15, 2004 at 10:59:48PM -0800, Andrew Morton wrote:
>...
> - There's a patch here which changes the ia32 CPU type selection. Make
> sure you go in there and select the right CPU type(s), else the kernel
> won't compile. We might need to set a default here.
>...
Hi Andrew,
thanks for including my patch to give it further testing, and also
thanks for this suggestion.
The patch below lets all cpu options default to "y".
cu
Adrian
--- linux-2.6.1-mm4/arch/i386/Kconfig.old 2004-01-17 02:13:22.000000000 +0100
+++ linux-2.6.1-mm4/arch/i386/Kconfig 2004-01-17 02:14:51.000000000 +0100
@@ -147,11 +147,13 @@
config CPU_386
bool "386"
+ default y
help
Select this for a 386 series processor.
config CPU_486
bool "486"
+ default y
help
Select this for a 486 series processor, either Intel or one of the
compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX,
@@ -160,6 +162,7 @@
config CPU_586
bool "586/K5/5x86/6x86/6x86MX"
+ default y
help
Select this for a non-Intel 586 or 686 series processor such as
the AMD K5 or the Cyrix 6x86MX.
@@ -173,41 +176,48 @@
config CPU_586TSC
bool "Pentium-Classic"
+ default y
help
Select this for a Pentium Classic processor with the RDTSC (Read
Time Stamp Counter) instruction.
config CPU_586MMX
bool "Pentium-MMX"
+ default y
help
Select this for a Pentium with the MMX graphics/multimedia
extended instructions.
config CPU_686
bool "Pentium-Pro"
+ default y
help
Select this for Intel Pentium Pro chips.
config CPU_PENTIUMII
bool "Pentium-II/Celeron(pre-Coppermine)"
+ default y
help
Select this for Intel chips based on the Pentium-II and
pre-Coppermine Celeron core.
config CPU_PENTIUMIII
bool "Pentium-III/Celeron(Coppermine)/Pentium-III Xeon"
+ default y
help
Select this for Intel chips based on the Pentium-III and
Celeron-Coppermine core.
config CPU_PENTIUMM
bool "Pentium M"
+ default y
help
Select this for Intel Pentium M (not Pentium-4 M)
notebook chips.
config CPU_PENTIUM4
bool "Pentium-4/Celeron(P4-based)/Pentium-4 M/Xeon"
+ default y
help
Select this for Intel Pentium 4 chips. This includes
the Pentium 4, P4-based Celeron and Xeon, and
@@ -215,42 +225,50 @@
config CPU_K6
bool "K6/K6-II/K6-III"
+ default y
help
Select this for an AMD K6, K6-II or K6-III (aka K6-3D).
config CPU_K7
bool "Athlon/Duron/K7"
+ default y
help
Select this for an AMD Athlon K7-family processor.
config CPU_K8
bool "Opteron/Athlon64/Hammer/K8"
+ default y
help
Select this for an AMD Opteron or Athlon64 Hammer-family processor.
config CPU_CRUSOE
bool "Crusoe"
+ default y
help
Select this for a Transmeta Crusoe processor.
config CPU_WINCHIPC6
bool "Winchip-C6"
+ default y
help
Select this for an IDT Winchip C6 chip.
config CPU_WINCHIP2
bool "Winchip-2"
+ default y
help
Select this for an IDT Winchip-2.
config CPU_WINCHIP3D
bool "Winchip-2A/Winchip-3"
+ default y
help
Select this for an IDT Winchip-2A or 3 with 3dNow!
capabilities.
config CPU_CYRIXIII
bool "Cyrix III/VIA C3"
+ default y
help
Select this for a Cyrix III or VIA C3 chip.
@@ -259,6 +277,7 @@
config CPU_VIAC3_2
bool "VIA C3-2 (Nehemiah)"
+ default y
help
Select this for a VIA C3 "Nehemiah" (model 9 and above).
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
@ 2004-01-17 2:22 ` Adrian Bunk
0 siblings, 0 replies; 68+ messages in thread
From: Adrian Bunk @ 2004-01-17 2:22 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
On Thu, Jan 15, 2004 at 10:59:48PM -0800, Andrew Morton wrote:
>...
> - There's a patch here which changes the ia32 CPU type selection. Make
> sure you go in there and select the right CPU type(s), else the kernel
> won't compile. We might need to set a default here.
>...
Hi Andrew,
thanks for including my patch to give it further testing, and also
thanks for this suggestion.
The patch below lets all cpu options default to "y".
cu
Adrian
--- linux-2.6.1-mm4/arch/i386/Kconfig.old 2004-01-17 02:13:22.000000000 +0100
+++ linux-2.6.1-mm4/arch/i386/Kconfig 2004-01-17 02:14:51.000000000 +0100
@@ -147,11 +147,13 @@
config CPU_386
bool "386"
+ default y
help
Select this for a 386 series processor.
config CPU_486
bool "486"
+ default y
help
Select this for a 486 series processor, either Intel or one of the
compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX,
@@ -160,6 +162,7 @@
config CPU_586
bool "586/K5/5x86/6x86/6x86MX"
+ default y
help
Select this for a non-Intel 586 or 686 series processor such as
the AMD K5 or the Cyrix 6x86MX.
@@ -173,41 +176,48 @@
config CPU_586TSC
bool "Pentium-Classic"
+ default y
help
Select this for a Pentium Classic processor with the RDTSC (Read
Time Stamp Counter) instruction.
config CPU_586MMX
bool "Pentium-MMX"
+ default y
help
Select this for a Pentium with the MMX graphics/multimedia
extended instructions.
config CPU_686
bool "Pentium-Pro"
+ default y
help
Select this for Intel Pentium Pro chips.
config CPU_PENTIUMII
bool "Pentium-II/Celeron(pre-Coppermine)"
+ default y
help
Select this for Intel chips based on the Pentium-II and
pre-Coppermine Celeron core.
config CPU_PENTIUMIII
bool "Pentium-III/Celeron(Coppermine)/Pentium-III Xeon"
+ default y
help
Select this for Intel chips based on the Pentium-III and
Celeron-Coppermine core.
config CPU_PENTIUMM
bool "Pentium M"
+ default y
help
Select this for Intel Pentium M (not Pentium-4 M)
notebook chips.
config CPU_PENTIUM4
bool "Pentium-4/Celeron(P4-based)/Pentium-4 M/Xeon"
+ default y
help
Select this for Intel Pentium 4 chips. This includes
the Pentium 4, P4-based Celeron and Xeon, and
@@ -215,42 +225,50 @@
config CPU_K6
bool "K6/K6-II/K6-III"
+ default y
help
Select this for an AMD K6, K6-II or K6-III (aka K6-3D).
config CPU_K7
bool "Athlon/Duron/K7"
+ default y
help
Select this for an AMD Athlon K7-family processor.
config CPU_K8
bool "Opteron/Athlon64/Hammer/K8"
+ default y
help
Select this for an AMD Opteron or Athlon64 Hammer-family processor.
config CPU_CRUSOE
bool "Crusoe"
+ default y
help
Select this for a Transmeta Crusoe processor.
config CPU_WINCHIPC6
bool "Winchip-C6"
+ default y
help
Select this for an IDT Winchip C6 chip.
config CPU_WINCHIP2
bool "Winchip-2"
+ default y
help
Select this for an IDT Winchip-2.
config CPU_WINCHIP3D
bool "Winchip-2A/Winchip-3"
+ default y
help
Select this for an IDT Winchip-2A or 3 with 3dNow!
capabilities.
config CPU_CYRIXIII
bool "Cyrix III/VIA C3"
+ default y
help
Select this for a Cyrix III or VIA C3 chip.
@@ -259,6 +277,7 @@
config CPU_VIAC3_2
bool "VIA C3-2 (Nehemiah)"
+ default y
help
Select this for a VIA C3 "Nehemiah" (model 9 and above).
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-17 1:40 ` 2.6.1-mm4 Mike Fedyk
@ 2004-01-17 2:07 ` Greg Fitzgerald
0 siblings, 0 replies; 68+ messages in thread
From: Greg Fitzgerald @ 2004-01-17 2:07 UTC (permalink / raw)
To: Mike Fedyk; +Cc: linux-kernel
Mike,
Sorry about the bad description. I have a logitech MX500
mouse that uses the explorer protocol. When i boot -mm4 the
scroll wheel is broke. When you try to scroll with the mouse wheel
the cursor moves all around the screen instead of scrolling. This was fixed
in 2.6.0 by adding psmouse.psmouse_proto=exps to the end of my kernel line in
grub.conf. It also was working in 2.6.1. For some reason it won't in
2.6.1--m4 though. Thanks.
-Greg
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-17 1:31 ` 2.6.1-mm4 Greg Fitzgerald
@ 2004-01-17 1:40 ` Mike Fedyk
2004-01-17 2:07 ` 2.6.1-mm4 Greg Fitzgerald
2004-01-17 2:24 ` 2.6.1-mm4 Mike Fedyk
2004-01-17 4:05 ` 2.6.1-mm4 Dmitry Torokhov
2 siblings, 1 reply; 68+ messages in thread
From: Mike Fedyk @ 2004-01-17 1:40 UTC (permalink / raw)
To: Greg Fitzgerald; +Cc: linux-kernel
On Fri, Jan 16, 2004 at 08:31:15PM -0500, Greg Fitzgerald wrote:
> Hi,
>
> Just gave 2.6.1-mm4 a try hoping to fix my NFS problems. NFS seems
> to be working better but now my mouse is not working properly. I have
> psmouse.psmouse_proto=exps in my grub.conf. Anyone have ideas? Thanks in advance.
What does "properly" mean?
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
` (7 preceding siblings ...)
(?)
@ 2004-01-17 1:31 ` Greg Fitzgerald
2004-01-17 1:40 ` 2.6.1-mm4 Mike Fedyk
` (2 more replies)
-1 siblings, 3 replies; 68+ messages in thread
From: Greg Fitzgerald @ 2004-01-17 1:31 UTC (permalink / raw)
To: linux-kernel
Hi,
Just gave 2.6.1-mm4 a try hoping to fix my NFS problems. NFS seems
to be working better but now my mouse is not working properly. I have
psmouse.psmouse_proto=exps in my grub.conf. Anyone have ideas? Thanks in advance.
--Greg
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 17:03 ` 2.6.1-mm4 Andrew Morton
(?)
@ 2004-01-16 18:11 ` Fabian Fenaut
-1 siblings, 0 replies; 68+ messages in thread
From: Fabian Fenaut @ 2004-01-16 18:11 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Gerd Knorr
Andrew Morton wrote:
> Fabian Fenaut <fabian.fenaut@free.fr> wrote:
>
>>I got an error compiling -mm4 :
>>
>> [...]
>> CC [M] drivers/media/video/ir-kbd-gpio.o
>> drivers/media/video/ir-kbd-gpio.c:185: unknown field `name' specified in
>> initializer
>
> You must be using an elderly gcc.
2.95.4 from debian stable
> diff -puN drivers/media/video/ir-kbd-gpio.c~ir-kbd-gpio-build-fix drivers/media/video/ir-kbd-gpio.c
> --- 25/drivers/media/video/ir-kbd-gpio.c~ir-kbd-gpio-build-fix 2004-01-16 09:01:59.000000000 -0800
> +++ 25-akpm/drivers/media/video/ir-kbd-gpio.c 2004-01-16 09:02:17.000000000 -0800
> @@ -182,9 +182,11 @@ static int ir_probe(struct device *dev);
> static int ir_remove(struct device *dev);
>
> static struct bttv_sub_driver driver = {
> - .drv.name = DEVNAME,
> - .drv.probe = ir_probe,
> - .drv.remove = ir_remove,
> + .drv = {
> + .name = DEVNAME,
> + .probe = ir_probe,
> + .remove = ir_remove,
> + },
> .gpio_irq = ir_irq,
> };
it works, thanks.
Fabian
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
` (6 preceding siblings ...)
(?)
@ 2004-01-16 17:58 ` Thomas Schlichter
-1 siblings, 0 replies; 68+ messages in thread
From: Thomas Schlichter @ 2004-01-16 17:58 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
[-- Attachment #1.1: body text --]
[-- Type: text/plain, Size: 268 bytes --]
Hi Andrew,
the attached patch fixes a link error of the kernel module 'drivers/scsi/
pcmcia/aha152x_cs.ko' because of two module_init() and two module_exit()
functions. Now the module links but I did not test it further...
Best regards
Thomas Schlichter
[-- Attachment #1.2: fix-PCMCIA-aha152x.diff --]
[-- Type: text/x-diff, Size: 329 bytes --]
--- linux-2.6.1-mm4/drivers/scsi/aha152x.c.orig 2004-01-16 16:26:09.018919528 +0100
+++ linux-2.6.1-mm4/drivers/scsi/aha152x.c 2004-01-16 16:26:42.661805032 +0100
@@ -3914,5 +3914,7 @@
.use_clustering = DISABLE_CLUSTERING,
};
+#if !defined(PCMCIA)
module_init(aha152x_init);
module_exit(aha152x_exit);
+#endif
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
` (5 preceding siblings ...)
(?)
@ 2004-01-16 17:37 ` Thomas Schlichter
-1 siblings, 0 replies; 68+ messages in thread
From: Thomas Schlichter @ 2004-01-16 17:37 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
[-- Attachment #1.1: body text --]
[-- Type: text/plain, Size: 183 bytes --]
Hi,
the patch "PP4-bwqcam-RC1" includes a small typo which leads to the undefined
symbol 'strcnmp'. The attaches patch corrects this typo.
Best regards
Thomas Schlichter
[-- Attachment #1.2: fix-bw-qcam-typo.diff --]
[-- Type: text/x-diff, Size: 448 bytes --]
--- linux-2.6.1-mm4/drivers/media/video/bw-qcam.c.orig 2004-01-16 16:42:27.178216712 +0100
+++ linux-2.6.1-mm4/drivers/media/video/bw-qcam.c 2004-01-16 16:42:51.534513992 +0100
@@ -963,7 +963,7 @@
#ifdef MODULE
int n;
- if (parport[0] && strcnmp(parport[0], "auto", 4) != 0) {
+ if (parport[0] && strncmp(parport[0], "auto", 4) != 0) {
/* user gave parport parameters */
for(n=0; parport[n] && n<MAX_CAMS; n++){
char *ep;
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 13:45 ` 2.6.1-mm4 Ed Tomlinson
(?)
@ 2004-01-16 17:32 ` Thomas Schlichter
-1 siblings, 0 replies; 68+ messages in thread
From: Thomas Schlichter @ 2004-01-16 17:32 UTC (permalink / raw)
To: Ed Tomlinson, Andrew Morton; +Cc: linux-kernel, linux-mm
[-- Attachment #1.1: body text --]
[-- Type: text/plain, Size: 398 bytes --]
Hi,
Am Freitag, 16. Januar 2004 14:45 schrieb Ed Tomlinson:
> Hi Andrew,
>
> Doing a modules install with mm4 gets a nfsd.ko needs unknown symbol
> dnotify_parent
>
> Ideas?
> Ed Tomlinson
This came with the "nfsd-04-add-dnotify-events" patch. The patch attached to
this mail exports the symbol 'dnotify_parent' and fixes the problem for me...
Best regards
Thomas Schlichter
[-- Attachment #1.2: export-dnotify_parent.diff --]
[-- Type: text/x-diff, Size: 306 bytes --]
--- linux-2.6.1-mm4/fs/dnotify.c.orig 2004-01-16 17:46:40.844370408 +0100
+++ linux-2.6.1-mm4/fs/dnotify.c 2004-01-16 17:48:46.045336968 +0100
@@ -166,6 +166,8 @@
}
}
+EXPORT_SYMBOL(dnotify_parent);
+
static int __init dnotify_init(void)
{
dn_cache = kmem_cache_create("dnotify_cache",
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
[not found] ` <200401161449.i0GEnoAv026627@fire-1.osdl.org>
@ 2004-01-16 17:03 ` Andrew Morton
0 siblings, 0 replies; 68+ messages in thread
From: Andrew Morton @ 2004-01-16 17:03 UTC (permalink / raw)
To: Fabian Fenaut; +Cc: linux-kernel, linux-mm, Gerd Knorr
Fabian Fenaut <fabian.fenaut@free.fr> wrote:
>
> I got an error compiling -mm4 :
>
> [...]
> CC [M] drivers/media/video/ir-kbd-gpio.o
> drivers/media/video/ir-kbd-gpio.c:185: unknown field `name' specified in
> initializer
> drivers/media/video/ir-kbd-gpio.c:185: warning: missing braces around
> initializer
> drivers/media/video/ir-kbd-gpio.c:185: warning: (near initialization for
> `driver.drv')
> drivers/media/video/ir-kbd-gpio.c:186: unknown field `drv' specified in
> initializer
> drivers/media/video/ir-kbd-gpio.c:187: unknown field `drv' specified in
> initializer
> drivers/media/video/ir-kbd-gpio.c:188: unknown field `gpio_irq'
> specified in initializer
You must be using an elderly gcc.
diff -puN drivers/media/video/ir-kbd-gpio.c~ir-kbd-gpio-build-fix drivers/media/video/ir-kbd-gpio.c
--- 25/drivers/media/video/ir-kbd-gpio.c~ir-kbd-gpio-build-fix 2004-01-16 09:01:59.000000000 -0800
+++ 25-akpm/drivers/media/video/ir-kbd-gpio.c 2004-01-16 09:02:17.000000000 -0800
@@ -182,9 +182,11 @@ static int ir_probe(struct device *dev);
static int ir_remove(struct device *dev);
static struct bttv_sub_driver driver = {
- .drv.name = DEVNAME,
- .drv.probe = ir_probe,
- .drv.remove = ir_remove,
+ .drv = {
+ .name = DEVNAME,
+ .probe = ir_probe,
+ .remove = ir_remove,
+ },
.gpio_irq = ir_irq,
};
_
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
@ 2004-01-16 17:03 ` Andrew Morton
0 siblings, 0 replies; 68+ messages in thread
From: Andrew Morton @ 2004-01-16 17:03 UTC (permalink / raw)
To: Fabian Fenaut; +Cc: linux-kernel, linux-mm, Gerd Knorr
Fabian Fenaut <fabian.fenaut@free.fr> wrote:
>
> I got an error compiling -mm4 :
>
> [...]
> CC [M] drivers/media/video/ir-kbd-gpio.o
> drivers/media/video/ir-kbd-gpio.c:185: unknown field `name' specified in
> initializer
> drivers/media/video/ir-kbd-gpio.c:185: warning: missing braces around
> initializer
> drivers/media/video/ir-kbd-gpio.c:185: warning: (near initialization for
> `driver.drv')
> drivers/media/video/ir-kbd-gpio.c:186: unknown field `drv' specified in
> initializer
> drivers/media/video/ir-kbd-gpio.c:187: unknown field `drv' specified in
> initializer
> drivers/media/video/ir-kbd-gpio.c:188: unknown field `gpio_irq'
> specified in initializer
You must be using an elderly gcc.
diff -puN drivers/media/video/ir-kbd-gpio.c~ir-kbd-gpio-build-fix drivers/media/video/ir-kbd-gpio.c
--- 25/drivers/media/video/ir-kbd-gpio.c~ir-kbd-gpio-build-fix 2004-01-16 09:01:59.000000000 -0800
+++ 25-akpm/drivers/media/video/ir-kbd-gpio.c 2004-01-16 09:02:17.000000000 -0800
@@ -182,9 +182,11 @@ static int ir_probe(struct device *dev);
static int ir_remove(struct device *dev);
static struct bttv_sub_driver driver = {
- .drv.name = DEVNAME,
- .drv.probe = ir_probe,
- .drv.remove = ir_remove,
+ .drv = {
+ .name = DEVNAME,
+ .probe = ir_probe,
+ .remove = ir_remove,
+ },
.gpio_irq = ir_irq,
};
_
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
` (2 preceding siblings ...)
(?)
@ 2004-01-16 14:49 ` Fabian Fenaut
-1 siblings, 0 replies; 68+ messages in thread
From: Fabian Fenaut @ 2004-01-16 14:49 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Hi,
I got an error compiling -mm4 :
[...]
CC [M] drivers/media/video/ir-kbd-gpio.o
drivers/media/video/ir-kbd-gpio.c:185: unknown field `name' specified in
initializer
drivers/media/video/ir-kbd-gpio.c:185: warning: missing braces around
initializer
drivers/media/video/ir-kbd-gpio.c:185: warning: (near initialization for
`driver.drv')
drivers/media/video/ir-kbd-gpio.c:186: unknown field `drv' specified in
initializer
drivers/media/video/ir-kbd-gpio.c:187: unknown field `drv' specified in
initializer
drivers/media/video/ir-kbd-gpio.c:188: unknown field `gpio_irq'
specified in initializer
drivers/media/video/ir-kbd-gpio.c:188: warning: initialization from
incompatible pointer type
make[4]: *** [drivers/media/video/ir-kbd-gpio.o] Erreur 1
make[3]: *** [drivers/media/video] Erreur 2
make[2]: *** [drivers/media] Erreur 2
make[1]: *** [drivers] Erreur 2
make[1]: Leaving directory `/usr/src/linux-2.6.1'
make: *** [stamp-build] Erreur 2
Complete log : http://fabian.fenaut.free.fr/compile_error
.config : http://fabian.fenaut.free.fr/config-2.6.1-mm4
Any hint ?
Thank you
Fabian
Andrew Morton a écrit le 16.01.2004 07:59:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
` (3 preceding siblings ...)
(?)
@ 2004-01-16 14:49 ` Fabian Fenaut
-1 siblings, 0 replies; 68+ messages in thread
From: Fabian Fenaut @ 2004-01-16 14:49 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Hi,
I got an error compiling -mm4 :
[...]
CC [M] drivers/media/video/ir-kbd-gpio.o
drivers/media/video/ir-kbd-gpio.c:185: unknown field `name' specified in
initializer
drivers/media/video/ir-kbd-gpio.c:185: warning: missing braces around
initializer
drivers/media/video/ir-kbd-gpio.c:185: warning: (near initialization for
`driver.drv')
drivers/media/video/ir-kbd-gpio.c:186: unknown field `drv' specified in
initializer
drivers/media/video/ir-kbd-gpio.c:187: unknown field `drv' specified in
initializer
drivers/media/video/ir-kbd-gpio.c:188: unknown field `gpio_irq'
specified in initializer
drivers/media/video/ir-kbd-gpio.c:188: warning: initialization from
incompatible pointer type
make[4]: *** [drivers/media/video/ir-kbd-gpio.o] Erreur 1
make[3]: *** [drivers/media/video] Erreur 2
make[2]: *** [drivers/media] Erreur 2
make[1]: *** [drivers] Erreur 2
make[1]: Leaving directory `/usr/src/linux-2.6.1'
make: *** [stamp-build] Erreur 2
Complete log : http://fabian.fenaut.free.fr/compile_error
.config : http://fabian.fenaut.free.fr/config-2.6.1-mm4
Any hint ?
Thank you
Fabian
Andrew Morton a ecrit le 16.01.2004 07:59:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
@ 2004-01-16 13:45 ` Ed Tomlinson
-1 siblings, 0 replies; 68+ messages in thread
From: Ed Tomlinson @ 2004-01-16 13:45 UTC (permalink / raw)
To: linux-kernel, linux-mm; +Cc: Andrew Morton
On January 16, 2004 01:59 am, Andrew Morton wrote:
> - There's a patch here which changes the ia32 CPU type selection. Make
> sure you go in there and select the right CPU type(s), else the kernel
> won't compile. We might need to set a default here.
>
> - Kernel NFS server update
>
> - MD update
>
> - V4L update
>
> - A string of fixes against the parport, paride and associated drivers
>
> - Update to the latest UML
>
> - Patches to support gcc-3.4 on ia32. There is more to do here - more
> warnings need to be fixed and the exception tables need to be sorted. I
> didn't add the `-Winline' patch because it's way too noisy at present.
Hi Andrew,
Doing a modules install with mm4 gets a nfsd.ko needs unknown symbol dnotify_parent
Ideas?
Ed Tomlinson
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
@ 2004-01-16 13:45 ` Ed Tomlinson
0 siblings, 0 replies; 68+ messages in thread
From: Ed Tomlinson @ 2004-01-16 13:45 UTC (permalink / raw)
To: linux-kernel, linux-mm; +Cc: Andrew Morton
On January 16, 2004 01:59 am, Andrew Morton wrote:
> - There's a patch here which changes the ia32 CPU type selection. Make
> sure you go in there and select the right CPU type(s), else the kernel
> won't compile. We might need to set a default here.
>
> - Kernel NFS server update
>
> - MD update
>
> - V4L update
>
> - A string of fixes against the parport, paride and associated drivers
>
> - Update to the latest UML
>
> - Patches to support gcc-3.4 on ia32. There is more to do here - more
> warnings need to be fixed and the exception tables need to be sorted. I
> didn't add the `-Winline' patch because it's way too noisy at present.
Hi Andrew,
Doing a modules install with mm4 gets a nfsd.ko needs unknown symbol dnotify_parent
Ideas?
Ed Tomlinson
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
@ 2004-01-16 9:34 ` Prakash K. Cheemplavam
-1 siblings, 0 replies; 68+ messages in thread
From: Prakash K. Cheemplavam @ 2004-01-16 9:34 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Hi,
I just gave it a try and the locking-up issue went worse with this
kernel. Now even without APIC the kernel locks up quite fast on my
nforce2. Very easy method (for me) was to copy a large file from CD-ROM
(at least now mounting CDs works again, in contrast to mm2) to HD and
machine locks-up. Sorry, no stack backtrace yet and no log entry, but
I'll try to do what I can.
Prakash
^ permalink raw reply [flat|nested] 68+ messages in thread
* Re: 2.6.1-mm4
@ 2004-01-16 9:34 ` Prakash K. Cheemplavam
0 siblings, 0 replies; 68+ messages in thread
From: Prakash K. Cheemplavam @ 2004-01-16 9:34 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Hi,
I just gave it a try and the locking-up issue went worse with this
kernel. Now even without APIC the kernel locks up quite fast on my
nforce2. Very easy method (for me) was to copy a large file from CD-ROM
(at least now mounting CDs works again, in contrast to mm2) to HD and
machine locks-up. Sorry, no stack backtrace yet and no log entry, but
I'll try to do what I can.
Prakash
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
* 2.6.1-mm4
@ 2004-01-16 6:59 ` Andrew Morton
0 siblings, 0 replies; 68+ messages in thread
From: Andrew Morton @ 2004-01-16 6:59 UTC (permalink / raw)
To: linux-kernel, linux-mm
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
- There's a patch here which changes the ia32 CPU type selection. Make
sure you go in there and select the right CPU type(s), else the kernel
won't compile. We might need to set a default here.
- Kernel NFS server update
- MD update
- V4L update
- A string of fixes against the parport, paride and associated drivers
- Update to the latest UML
- Patches to support gcc-3.4 on ia32. There is more to do here - more
warnings need to be fixed and the exception tables need to be sorted. I
didn't add the `-Winline' patch because it's way too noisy at present.
Changes since 2.6.1-mm3:
linus.patch
Latest Linus tree
-scsi-rename-TIMEOUT.patch
-qla1280-update-2.patch
-qla1280-build-fix.patch
-sym-speed-fix.patch
-sym2-speed-selection-fix.patch
-aacraid-warning-fix.patch
-68k-359.patch
-68k-360.patch
-68k-365.patch
-68k-366.patch
-68k-378.patch
-68k-384.patch
-inia100-fix.patch
-mremap-dosemu-fix.patch
-symbios-build-fix.patch
Merged
-aic7xxx_old-proc-oops-fix.patch
-aic7xxx_old-oops-fix.patch
These broke.
+qla2xxx-build-fix.patch
Fix the new qlogic driver for older gcc's
-2.6.1-bk1-netdev4.patch
+netdev.patch
Recentish jgarzik tree
-keyboard-scancode-fix.patch
+keyboard-scancode-fixes.patch
+input-use-after-free-checks.patch
-input-print-screen-emulation-fix.patch
-input-use-after-free-checks.patch
+psmouse-timeout-parity-fixes.patch
More keyboard/mouse fixes
+acpi-frees-irq0.patch
ACPI fix.
-loop-bio-index-fix.patch
-loop-bio-clone.patch
-loop-recycle.patch
+loop-bio-handling-fix.patch
+loop-init-fix.patch
Go back to the loop patches which work.
+alsa-pnp-fix.patch
Fix PNP+ALSA combination
-sysfs_remove_dir-vs-dcache_readdir-race-fix.patch
This seems to be causing oopses
-sysfs-add-simple-class-device-support.patch
-sysfs-remove-tty-class-device-logic.patch
-sysfs-add-mem-device-support.patch
-sysfs-add-misc-class.patch
-vc-init-race-fix.patch
-sysfs-add-video-class.patch
-sysfs-add-oss-class.patch
-sysfs-add-alsa-class.patch
-sysfs-add-input-class-support.patch
+sysfs-class-01-simple.patch
+sysfs-class-02-input.patch
+sysfs-class-03-lp.patch
+sysfs-class-04-mem.patch
+sysfs-class-05-misc.patch
+sysfs-class-06-raw.patch
+sysfs-class-07-oss-sound.patch
+sysfs-class-08-alsa-sound.patch
+sysfs-class-09-cleanup-tty.patch
+sysfs-class-10-vc.patch
New sysfs simple-class support
+sched-clock-fixes.patch
+sched-build-fix.patch
+p4-clockmod-sibling-map-fix.patch
+sched-sync-rt-wakeup-fix.patch
CPU scheduler-related fixups
+eicon-buffer-allocation-fixes.patch
ISDN driver fix
-libata-update.patch
+2.6.1-bk2-libata1.patch
New libata update patch
+limit-hash-table-size-2.patch
Allow larger dentry+inode hashtable sizes on monster 64-bit boxen
+readahead-revert-lazy-readahead.patch
Revert a bit more of the recent readahead rework -it wasn't nice to NFS.
+better-i386-cpu-selection.patch
Finer-grained ia32 CPU type selection
+serial-02-fixups-fix.patch
+serial-02-fixes-fix-2.patch
+serial-03-fixups-fix.patch
+serial-03-fixups-fix-2.patch
Fix compile breakages
-increase-MAX_MP_BUSSES.patch
This is still under discussion
+remove-null-initialisers.patch
Small bss savings
+nuke-noisy-printks.patch
Less bootup messages
+ppc-cond_syscall-fix.patch
ppc32 build fix
+PP0-full_list-RC1.patch
+PP1-parport_locking-RC1.patch
+PP2-enumerate1-RC1.patch
+PP2-enumerate1-RC1-fix.patch
+PP3-parport_gsc-RC1.patch
+PP4-bwqcam-RC1.patch
+PP5-daisy-RC1.patch
+PI0-schedule_claimed-RC1.patch
+PI1-expansion-RC1.patch
+PI2-crapectomy-RC1.patch
+PI3-ps_ready-RC1.patch
+PI4-pd_busy-RC1.patch
+PI5-do_pd_io-RC1.patch
+PI6-bogus_requests-RC1.patch
+PI7-claim_reorder-RC1.patch
+PI8-do_pd_request1-RC1.patch
+PI9-run_fsm-RC1.patch
+PI10-action-RC1.patch
+PI11-disconnect-RC1.patch
+PI12-unclaim-RC1.patch
+PI13-run_fsm-loop-RC1.patch
+PI14-next_request-RC1.patch
+PI15-do_pd_io-gone-RC1.patch
+PI16-pd_claimed-RC1.patch
+PI17-connect-RC1.patch
+PI18-reorder-RC1.patch
+PI19-special1-RC1.patch
+PI20-gendisk_setup-RC1.patch
+PI21-present-RC1.patch
+PI22-pd_init_units-RC1.patch
+PI23-special2-RC1.patch
+PI24-paride64-RC1.patch
+IMM0-lindent-RC1.patch
+IMM1-references-RC1.patch
+IMM2-claim-RC1.patch
+IMM3-scsi_module-RC1.patch
+IMM4-imm_probe-RC1.patch
+IMM5-imm_wakeup-RC1.patch
+IMM6-imm_hostdata-RC1.patch
+IMM7-imm_attach-RC1.patch
+PPA0-ppa_lindent-RC1.patch
+PPA1-ppa_references-RC1.patch
+PPA2-ppa_claim-RC1.patch
+PPA3-ppa_scsi_module-RC1.patch
+PPA4-ppa_probe-RC1.patch
+PPA5-ppa_wakeup-RC1.patch
+PPA6-ppa_hostdata-RC1.patch
+PPA7-ppa_attach-RC1.patch
+PPA8-ppa_lock_fix-RC1.patch
parport/paride cleanups/fixes
+document-efi-zero-page-usage.patch
Documentation
+v4l-01-videodev-update.patch
+v4l-02-v4l2-update.patch
+v4l-03-video-buf-update.patch
+v4l-04-bttv-driver-update.patch
+v4l-05-infrared-remote-support.patch
+v4l-06-misc-i2c-fixes.patch
+v4l-07-tuner-update.patch
+v4l-08-bttv-IR-input-support.patch
+v4l-09-saa7134-update.patch
+v4l-10-conexant-2388x-driver.patch
V4L update
+request-origination-determination-fix.patch
Sanify the way in which we determine where a disk request came from
+ppc-module-skip-debug-sections.patch
ppc module loading fix/speedup
+MAINTAINERS-oprofile-update.patch
MAINTAINERS update
+md-01-set_disk_faulty-return-code-fix.patch
+md-02-rebuild-needs-yield.patch
+md-03-resync-interrupt-fix.patch
+md-04-typo-fix.patch
+md-05-recovery-fix.patch
+md-06-do_md_run-fix.patch
+md-07-superblock-writing-fixes.patch
+md-08-remove-disks-array.patch
+md-09-discard-mddev_map-array.patch
+md-10-use-bd_disk-private_data.patch
MD update
+nfsd-01-stale-filehandles-fixes.patch
+nfsd-02-failed-lookup-status-fix.patch
+nfsd-03-follow_up-fix.patch
+nfsd-04-add-dnotify-events.patch
+nfsd-05-SUN-NFSv2-hack.patch
+nfsd-06-SVCFH_fmt-is-extern.patch
kNFSD update
+ghash.patch
+tty_io-uml-fix.patch
+uml-update.patch
UML update
+proc_dma_open-simplification.patch
Code simplification
+rq_for_each_bio-fix.patch
Avoid possible problems with macro expansion
+remove-afs-strdup.patch
Remove dead code
+uninline-bitmap-functions.patch
+sock_put-inline-fix.patch
+add-noinline-attribute.patch
+use-funit-at-a-time.patch
+add-config-for-mregparm-3.patch
+add-config-for-mregparm-3-make-EXPERIMENTAL.patch
+add-module-magic-for-mregparm3.patch
+#add-W-inline.patch
+fix-x86_64-gcc-34-warnings.patch
+fix-more-gcc-34-warnings.patch
+gcc-34-string-fixes.patch
Patches to take advantage of gcc-3.4 features, and fixups for gcc-3.4.
All 620 patches:
linus.patch
mm.patch
add -mmN to EXTRAVERSION
qla2xxx-build-fix.patch
fix qla2xxx build for older gcc's
sh-merge.patch
SH Merge
sh-kyrofb-support.patch
kyrofb support
alsa-101.patch
ALSA 1.0.1
alsa-cmipci-joystick-fix.patch
netdev.patch
kgdb-ga.patch
kgdb stub for ia32 (George Anzinger's one)
kgdbL warning fix
kgdb buffer overflow fix
kgdbL warning fix
kgdb: CONFIG_DEBUG_INFO fix
x86_64 fixes
kgdb-doc-fix.patch
correct kgdb.txt Documentation link (against 2.6.1-rc1-mm2)
kgdboe-netpoll.patch
kgdb-over-ethernet via netpoll
kgdboe-non-ia32-build-fix.patch
kgdb-x86_64-support.patch
kgdb for x86_64 2.6 kernels
kgdb-x86_64-build-fix.patch
fix x86_64 build with CONFIG_KGDB=n
radeon-line-length-fix.patch
radeonfb line length fix
loop-fix-hardsect.patch
loop: fix hard sector size
loop-fd-leak-fix.patch
loop: fix file refcount leak
must-fix.patch
must fix lists update
must fix list update
mustfix update
must-fix-update-5.patch
must-fix update
modular-ide-is-broken.patch
document in must-fix that modular IDE is
RD1-open-mm.patch
RD2-release-mm.patch
RD3-presto_journal_close-mm.patch
RD4-f_mapping-mm.patch
RD5-f_mapping2-mm.patch
RD6-i_sem-mm.patch
RD7-f_mapping3-mm.patch
RD8-generic_osync_inode-mm.patch
RD9-bd_acquire-mm.patch
RD10-generic_write_checks-mm.patch
RD11-I_BDEV-mm.patch
cramfs-use-pagecache.patch
cramfs: use pagecache better
raw-driver-refcounting-fix.patch
raw.c refcounting fix
invalidate_inodes-speedup.patch
invalidate_inodes speedup
more invalidate_inodes speedup fixes
net-jiffy-normalisation-fix.patch
NET: Normalize jiffies reported to userspace, in neighbor management code
input-mousedev-remove-jitter.patch
Input: smooth out mouse jitter
input-mousedev-ps2-emulation-fix.patch
mousedev PS/@ emulation fix
input-01-i8042-suspend.patch
input: i8042 suspend
input-02-i8042-option-parsing.patch
input: i8042 option parsing
input-03-psmouse-option-parsing.patch
input: psmouse option parsing
input-04-atkbd-option-parsing.patch
input: atkbd option parsing
input-05-missing-module-licenses.patch
input: missing module licenses
input-06-Kconfig-Synaptics-help.patch
Kconfig Synaptics help
input-07-sis-aux-port.patch
input: SiS AUX port
input-11-98busmouse-compile-fix.patch
Fix compile error in 98busmouse.c module
input-12-mouse-drivers-use-module_param.patch
Convert mouse drivers to use module_param
input-13-tsdev-use-module_param.patch
Convert tsdev to use module_param
keyboard-scancode-fixes.patch
keyboard scancode fixes
input-use-after-free-checks.patch
input layer debug checks
synaptics-rate-switching.patch
Synaptics rate switching
psmouse-drop-timed-out-bytes.patch
psmouse: log and discard timed out bytes
psmouse-timeout-parity-fixes.patch
input: psmouse timeout&parity fixes
cpu_sibling_map-fix.patch
cpu_sibling_map fix
acpi-20031203.patch
acpi-20031203-fix.patch
acpi-frees-irq0.patch
acpi frees free irq0
cfq-4.patch
CFQ io scheduler
CFQ fixes
config_spinline.patch
uninline spinlocks for profiling accuracy.
ppc64-WARN_ON.patch
[ppc64] clean up WARN_ON backtrace
ppc64-IRQ_INPROGRESS.patch
[ppc64] revert IRQ_INPROGRESS change
ppc64-zImage_default.patch
[ppc64] Build the zImage by default
ppc64-biarch.patch
[ppc64] add automatic check for biarch compilers
ppc64-PT_FPSCR_fix.patch
[ppc64] ptrace.h PT_FPSCR fixup, from Will Schmidt
ppc64-writelogbuffer.patch
[ppc64] HvCall_writeLogBuffer called with too large of a buffer
ppc64-phandle.patch
[ppc64] support for ibm,phandle OF property, from Dave Engebretsen:
ppc64-of_traversal_api.patch
[ppc64] New Open Firmware device tree API, from Nathan Lynch
ppc64-of_traversal_api_2.patch
[PPC64] Change to new OF device tree API, from Nathan Lynch
ppc64-vty_node.patch
[ppc64] vty updates, from Hollis Blanchard
ppc64-hvc_console.patch
[ppc64] hvc_console can only handle vty nodes compatible with "hvterm1", from Hollis Blanchard
ppc64-device_is_compatible.patch
[ppc64] use device_is_compatible() instead of manual strcmp, from Hollis Blanchard
ppc64-smp_call_function.patch
[ppc64] Make IPI receivers survive a late arrival after the sender has given up waiting, from Olof Johansson
ppc64-device_tree_updates.patch
[ppc64] support for runtime updates of /proc/device-tree, from Nathan Lynch
ppc64-device_tree_updates_2.patch
[ppc64] base support for dynamic update of OF device, tree from Nathan Lynch
ppc64-trivial.patch
[ppc64] various trivial patches
ppc64-device_tree_updates_3.patch
[ppc64] Open Firmware device tree manipulation support, from Nathan Lynch
ppc64-ioremap_rework.patch
[ppc64] Mem-map I/O changes, from Mike Wolf
ppc64-rtas_flash.patch
[ppc64] extended flash changes, from Mike Wolf
ppc64-cputable.patch
[ppc64] cputable update, from Dave Engebretsen
ppc64-cputable_2.patch
[ppc64] cputable cleanup, from Dave Engebretsen:
ppc64-remove_MAX_PROCESSORS.patch
[ppc64] iSeries fixups, from Stephen Rothwel
ppc64-rtas_functions.patch
[ppc64] Add some rtas calls, from John Rose
ppc64-rtas_rename.patch
[ppc64] rename the rtas event classes to avoid namespace collisions, from John Rose
ppc64-stupidnumabug.patch
[ppc64] fix sign extension bug in NUMA code
ppc64-devinit_fixes.patch
[ppc64] Add exports and change some __init to __devinit for dynamic OF and pci hotplug, from John Rose and Linda Xie
ppc64-syscall6.patch
[ppc64] Add _syscall6, from Olaf Hering
ppc64-sched_clock.patch
[ppc64] fix sched_clock, from Paul Mackerras:
ppc64-compat_update.patch
[ppc64] compat layer update, from Paul Mackerras, Olaf Hering and myself
ppc64-sys_rtas.patch
[ppc64] add rtas syscall, from John Rose
ppc64-sharedproc.patch
[ppc64] shared processor support, from Dave Engebretsen
ppc64-logical_cpu.patch
[ppc46] SMT processor support and logical cpu numbering, from Dave Engebretsen
ppc64-UP_cleanup.patch
[ppc64] UP compile fixes, from Paul Mackerras
ppc64-add_vmx.patch
[ppc64] Add VMX registers to sigcontext, from Steve Munroe
ppc64-missing_sync.patch
[ppc64] one instruction fix for synchronization bug found during cpu DLPAR development, from Joel Schopp
ppc64-nvram_rewrite.patch
[ppc64] NVRAM error logging/buffering patch, from Jake Moilanen
ppc64-iseries_support.patch
[ppc64] preliminary iseries support, from Paul Mackerras
ppc64-hcall_constants.patch
[ppc64] Add additional hypervisor call constants, from Dave Boutcher
ppc64-iseries_cleanup.patch
[ppc64] iSeries fixes, from Stephen Rothwell
ppc64-device_tree_updates_fix.patch
[ppc64] fix a couple small OF device tree bugs which were overlooked, from Joel Schopp
ppc64-iseries_cleanup_2.patch
[ppc64] Tidy up various bits of the iSeries code. No significant code changes, from Stephen Rothwell
ppc64-remove-veth-proc.patch
[ppc64] Small cleanups to iSeries virtual ethernet driver, from Dave Gibson
ppc64-add_hcall.patch
[ppc64] add hcall interface
ppc64-addvio.patch
[ppc64] VIO support, from Dave Boutcher, Hollis Blanchard and Santiago Leon
ppc64-iseries_pci.patch
[ppc64] Get native PCI going on iSeries, from Paul Mackerras
ppc64-lparcfg.patch
[ppc64] add/forward port of lparcfg, from Will Schmidt
ppc64-surveillance.patch
[ppc64] Update the surveillance boot parameter to allow all valid settings of the surveillance timeout, from Nathan Fontenot
ppc64-power4fix.patch
[ppc64] fix POWER3 boot
ppc64-vmxsupport.patch
[ppc64] VMX (Altivec) support & signal32 rework, from Ben Herrenschmidt
ppc64-hash_page_race.patch
[ppc64] Fix {pte,pmd}_free vs. hash_page race by relaying actual deallocation with RCU, from Ben Herrenschmidt
ppc64-hash_page_rewrite.patch
[ppc64] __hash_page rewrite, from Ben Herrenschmidt
ppc64-mf_proc_cleanup.patch
[ppc64] Tidy up the mf_proc code, from Stephen Rothwell
ppc64-prom_panic.patch
[ppc64] prom_panic(), from Todd Inglett
ppc64-iseries_pci_2.patch
[ppc64] Check range of PCI memory and I/O accesses on iSeries, from Stephen Rothwell
ppc64-iseries_fixes.patch
[ppc64] Fix a compile error and a warning in the iSeries code, from Stephen Rothwell
ppc64-viopath_fix.patch
[ppc64] Use an atomic_t instead of a volatile unsigned long, from Stephen Rothwell
ppc64-makefile_fixes.patch
[ppc64] Makefile fixes
ppc64-vmlinux_lds.patch
[ppc64] vmlinux.lds fixes, from Alan Modra
ppc64-setup_cpu.patch
[ppc64] setup_cpu must be called on boot cpu
ppc64-epoll.patch
[ppc64] correct epoll syscall names
ppc64-compat_stat.patch
[ppc64] cp_compat_stat should copy nanosecond fields
ppc64-xmon_fixes.patch
[ppc64] xmon breakpoint and single step on LPAR fixes from John Rose
ppc64-rtas_delay.patch
[ppc64] Fixed rtas_extended_busy_delay_time() to calculate correct value, from John Rose
ppc64-bss_clear.patch
[ppc64] early BSS clear, from Ben Herrenschmidt
ppc64-vio-fixup.patch
[ppc64] vio fixup
ppc64-bar-0-fix.patch
Allow PCI BARs that start at 0
ppc64-reloc_hide.patch
ramdisk-leak-fix.patch
fix memory leak in ram disk
ramdisk-cleanup.patch
intel8x0-cleanup.patch
intel8x0 cleanups
pdflush-diag.patch
zap_page_range-debug.patch
zap_page_range() debug
asus-L5-fix.patch
Asus L5 framebuffer fix
jffs-use-daemonize.patch
get_user_pages-handle-VM_IO.patch
support-zillions-of-scsi-disks.patch
support many SCSI disks
pci_set_power_state-might-sleep.patch
CONFIG_STANDALONE-default-to-n.patch
Make CONFIG_STANDALONE default to N
extra-buffer-diags.patch
CONFIG_SYSFS.patch
From: Pat Mochel <mochel@osdl.org>
Subject: [PATCH] Add CONFIG_SYSFS
CONFIG_SYSFS-boot-from-disk-fix.patch
slab-leak-detector.patch
slab leak detector
loop-module-alias.patch
loop needs MODULE_ALIAS_BLOCK
loop-remove-blkdev-special-case.patch
loop-highmem.patch
remove useless highmem bounce from loop/cryptoloop
loop-bio-handling-fix.patch
loop: BIO handling fix
loop-init-fix.patch
loop.c doesn't fail init gracefully
acpi-pm-timer-3.patch
ACPI PM timer version 3
as-regression-fix.patch
Fix IO scheduler regression
as-request-poisoning.patch
AS: request poisoning
as-request-poisoning-fix.patch
AS: request poisining fix
as-fix-all-known-bugs.patch
AS fixes
as-new-process-estimation.patch
AS: new process estimation
as-cooperative-thinktime.patch
AS: thinktime improvement
as-tuning.patch
AS tuning
scale-nr_requests.patch
scale nr_requests with TCQ depth
truncate_inode_pages-check.patch
local_bh_enable-warning-fix.patch
pnp-fix-2.patch
PnP Fixes #2
pnp-fix-3.patch
PnP Fixes #3
alsa-pnp-fix.patch
ALSA pnp fix
alpha-stack-dump.patch
invalidate_mmap_range-non-gpl-export.patch
mark invalidate_mmap_range() as EXPORT_SYMBOL
ppc-export-consistent_sync_page.patch
PPC32: Export consistent_sync_page.
ppc-use-EXPORT_SYMBOL_NOVERS.patch
PPC32: Change all EXPORT_SYMBOL_NOVERS to EXPORT_SYMBOL in ppc_ksyms.c
ppc-CONFIG_PPC_STD_MMU-fix.patch
PPC32: Select arch/ppc/kernel/head.S on CONFIG_PPC_STD_MMU.
ppc-IBM-MPC-header-cleanups.patch
PPC32: Minor cleanups to IBM4xx and MPC82xx headers.
percpu-gcc-34-warning-fix.patch
fix gcc-3.4 warning in percpu code
nr_requests-oops-fix.patch
Fix oops when modifying /sys/block/dm-0/queue/nr_requests
netfilter_bridge-compile-fix.patch
atapi-mo-support.patch
ATAPI MO drive support
mt-ranier-support.patch
mt rainier support
atapi-mo-support-update.patch
ATAPI MO support update
cdrom_open fix
ppp_async-locking-fix.patch
Make ppp_async callable from hard interrupt
make-try_to_free_pages-walk-zonelist.patch
make try_to_free_pages walk zonelist
make-try_to_free_pages-walk-zonelist-fix.patch
zone scanning fix
remove-CardServices-from-pcmcia-net-drivers.patch
CardServices() removal from pcmcia net drivers
remove-CardServices-from-ide-cs.patch
From: Arjan van de Ven <arjanv@redhat.com>
Subject: Re: [PATCH 1/10] CardServices() removal from pcmcia net drivers
remove-CardServices-from-drivers-net-wireless.patch
remove CardServices() from drivers/net/wireless
remove-CardServices-from-drivers-serial.patch
Remvoe CardServices() from drivers/serial
remove-CardServices-from-drivers-serial-fix.patch
serial_cs CardServices removal fix
remove-CardServices-from-axnet_cs.patch
remvoe CardServices from axnet_cs
remove-CardServices-final.patch
final CardServices() removal patches
CardServices-compatibility-layer.patch
CardServices compatibility layer
sysfs-class-01-simple.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add class_simple support [01/10]
sysfs-class-02-input.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for input devices [02/10]
sysfs-class-03-lp.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add class support for lp devices [03/10]
sysfs-class-04-mem.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for mem devices [04/10]
sysfs-class-05-misc.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for misc devices [05/10]
sysfs-class-06-raw.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for raw devices [06/10]
sysfs-class-07-oss-sound.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for OSS sound devices [07/10]
sysfs-class-08-alsa-sound.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for ALSA sound devices [08/10]
sysfs-class-09-cleanup-tty.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] clean up sysfs class support for tty devices [09/10]
sysfs-class-10-vc.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for vc devices [10/10]
tridentfb-non-flatpanel-fix.patch
fix for tridentfb.c usage on CRTs.
CONFIG_EPOLL-file_struct-members.patch
CONFIG_EPOLL=n space reduction
epoll-oneshot-support.patch
One-shot support for epoll
kill_fasync-speedup.patch
kill_fasync speedup
o21-sched.patch
O21 for interactivity 2.6.0
sched-clock-2.6.0-A1.patch
Relax synchronization of sched_clock()
sched-can-migrate-2.6.0-A2.patch
can_migrate_task cleanup
sched-cleanup-2.6.0-A2.patch
CPU scheduler cleanup
sched-style-2.6.0-A5.patch
sched.c style cleanups
make-for_each_cpu-iterator-more-friendly.patch
Make for_each_cpu() Iterator More Friendly
make-for_each_cpu-iterator-more-friendly-fix.patch
Fix alpha build failure
make-for_each_cpu-iterator-more-friendly-fix-fix.patch
use-for_each_cpu-in-right-places.patch
Use for_each_cpu() Where It's Meant To Be
for_each_cpu-oprofile-fix.patch
for_each_cpu oprofile fix
for_each_cpu-oprofile-fix-2.patch
sched-find_busiest_node-resolution-fix.patch
sched: improved resolution in find_busiest_node
sched-domains.patch
sched: scheduler domain support
sched-clock-fixes.patch
fix sched_clock()
sched-build-fix.patch
sched: fix for NR_CPUS > BITS_PER_LONG
sched-sibling-map-to-cpumask.patch
sched: cpu_sibling_map to cpu_mask
p4-clockmod-sibling-map-fix.patch
p4-clockmod sibling_map fix
sched-domains-i386-ht.patch
sched: implement domains for i386 HT
acpi-numa-printk-level-fixes.patch
ACPI NUMA quiet printk and cleanup
sched-sync-rt-wakeup-fix.patch
sched: fix sync wakeups of RT tasks
decrypt-CONFIG_PDC202XX_FORCE-help.patch
Change cryptic description and help for CONFIG_PDC202XX_FORCE
ide-siimage-seagate.patch
ide-siimage-stack-fix.patch
ide-siimage-sil3114.patch
ide-pdc_old-pio-fix.patch
ide-pdc_old-udma66-fix.patch
ide-pdc_old-66mhz_clock-fix.patch
ide-pdc_new-proc.patch
fa311-mac-address-fix.patch
wrong mac address with netgear FA311 ethernet card
kernel-locking-doc-end-tags-fix.patch
Missing end tags in kernel-locking kerneldoc
rcupdate-c99-initialisers.patch
C99 change to rcupdate.h
68k-339.patch
M68k floppy selection
68k-340.patch
M68k head console
68k-341.patch
M68k head unused
68k-342.patch
M68k head comments
68k-343.patch
M68k head pic
68k-344.patch
M68k head white space
68k-345.patch
M68k cache mode
68k-346.patch
M68k RMW accesses
68k-347.patch
Atari Hades PCI C99
68k-348.patch
Amiga sound C99
68k-349.patch
BVME6000 RTC C99
68k-350.patch
M68k symbol exports
68k-351.patch
M68k math emu C99
68k-352.patch
MVME16x RTC C99
68k-353.patch
Q40 interrupts C99
68k-354.patch
Sun-3 ID PROM C99
68k-355.patch
Mac ADB IOP fix
68k-361.patch
Macfb setup
68k-364.patch
Mac ADB
68k-367.patch
Amiga Gayle IDE cleanup
68k-368.patch
Amiga Gayle E-Matrix 530 IDE
68k-369.patch
Zorro sysfs/driver model
68k-374.patch
Amiga debug fix
68k-375.patch
Mac II VIA
68k-377.patch
M68k asm/system.h
68k-379.patch
Amiga core C99
68k-380.patch
M68k has no VGA/MDA
68k-381.patch
M68k thread
68k-382.patch
M68k thread_info
68k-383.patch
M68k extern inline
68k-385.patch
Cirrusfb extern inline
68k-386.patch
Genrtc warning
68k-387.patch
M68k Documentation
68k-390.patch
Amiga Buddha/CatWeasel IDE
printk_ratelimit.patch
generalise net_ratelimit (printk_ratelimit)
printk_ratelimit-fix.patch
parintk_ratelimit fix
freevxfs-MODULE_ALIAS.patch
MODULE_ALIAS for freevxfs
trident-cleanup-indentation-D1-2.6.0.patch
reindent trident OSS sound driver
trident-sound-driver-fixes.patch
trident OSS sound driver fixes
trident-cleanup-2.patch
trident: use pr_debug instead of home-brewed TRDBG
compound-page-page_count-fix.patch
fix page counting for compound pages
MAINTAINERS-lanana-update.patch
MAINTAINERS update
devfs-joystick-fix.patch
fix devfs names for joystick
s3-sleep-remove-debug-code.patch
s3 sleep: Kill obsolete debugging code
swsusp-doc-updates.patch
swsusp/sleep documentation update
watchdog-updates.patch
Watchdog patches
watchdog-updates-2.patch
Watchdog patches (part 2)
ext2_new_inode-cleanup.patch
ext2_new_inode nanocleanup
ext2-s_next_generation-fix.patch
ext2: s_next_generation locking
ext3-s_next_generation-fix.patch
ext3: s_next_generation fixes
alt-arrow-console-switch-fix.patch
Fix Alt-arrow console switch droppage
alt-arrow-console-switch-fix-2.patch
Alt-arrow console switch #2
ia32-remove-SIMNOW.patch
Remove x86_64 leftover SIMNOW code
softcursor-fix.patch
Fix softcursor
ext2-debug-build-fix.patch
ext2: fix build when EXT2_DEBUG is set
efi-inline-fixes.patch
Fix weird placement of inline
do_timer_gettime-cleanup.patch
do_timer_gettime() cleanup
set_cpus_allowed-locking-fix.patch
set_cpus_allowed locking
fix set_cpus_allowed locking even more
rmmod-race-fix.patch
module removal race fix
remove-hpet-intel-check.patch
Remove Intel check in i386 HPET code
devfs-d_revalidate-oops-fix.patch
devfs d_revalidate race/oops fix
laptop-mode-2.patch
laptop-mode for 2.6, version 6
laptop-mode-doc-update.patch
Documentation/laptop-mode.txt
laptop-mode-2-doc-updates.patch
laptop-mode documentation updates
ali-m1533-hang-fix.patch
ALI M1533 audio hang fix
start_this_handle-retval-fix.patch
jbd: start_this_handle() return value fix
remove-eicon-isdn-driver.patch
remove old Eicon isdn driver
eicon-memory-access-size-fix.patch
Eicon isdn driver hardware access fix
eicon-buffer-allocation-fixes.patch
Eicon isdn driver alloc buffer size fix
do_no_page-leak-fix.patch
do_no_page leak fix
vt-locking-fixes-2.patch
VT locking patch #2
pid_max-fix.patch
Bug when setting pid_max > 32k
allow-SGI-IOC4-chipset-support.patch
allow SGI IOC4 chipset support
oss-dmabuf-deadlock-fix.patch
OSS dmabuf deadlock fix
workqueue-cleanup.patch
Remove redundant code in workqueue.c
2.6.1-bk2-libata1.patch
tridentfb-documentation-fix.patch
tridentfb documentation fix
proc_pid_lookup-speedup.patch
Optimize proc_pid_lookup
bio_endio-clarifications.patch
clarify meaning of bio fields in the end_io function
rtc-leak-fixes.patch
2.6.1 RTC leaks.
simplify-node-zone-fields-3.patch
Simplify node/zone field in page->flags
radeonfb-pdi-id-addition.patch
Identify RADEON Yd in radeonfb
mpt-fusion-update.patch
MPT Fusion driver 3.00.00 update
use-soft-float.patch
Use -msoft-float
DRM-cvs-update.patch
DRM cvs update
sis-DRM-floating-point-removal.patch
Remove float from sis DRM
drm-include-fix.patch
raid6-20040107.patch
RAID-6
raid6-readahead-fix.patch
RAID-6 readahead fix
kthread-primitive.patch
kthread primitive
use-kthread-primitives.patch
Use kthread primitives
alpha-module-relocation-overflow-fix.patch
Relocation overflow with modules on Alpha
ppc32-of-bootwrapper-support.patch
ppc32: OF bootwrapper support
lsi-megaraid-pci-id.patch
LSI Logic MegaRAID3 PCI ID
ide-pci-modules-fix.patch
fix issues with loading PCI IDE drivers as modules
use-diff-dash-p.patch
Fix Documentation/SubmittingPatches to use -p
use-kconfig-range-for-NR_CPUS.patch
Kconfig: use range for NR_CPUS
sysfs-pin-kobject.patch
sysfs: pin kobjects to fix use-after-free crashes
bio-documentation-update.patch
bio documentation update
limit-hash-table-sizes.patch
Subject: Limit hash table size
limit-hash-table-size-2.patch
hash table size limiting: huge 64-bit fixes
add-SIOCSIFNAME-compat-ioctl.patch
Add SIOCSIFNAME compat ioctl
disable-G400-DRM-on-x86_64.patch
Disable G400 DRM driver on x86-64
x86_64-merge.patch
x86-64 merge for 2.6.1
init-zone-priorities.patch
vmscan: initialize zone->{prev,temp}_priority
readahead-partial-backout.patch
radahead part-backout
readahead-revert-lazy-readahead.patch
readaheadL revert lazy readahead
menuconfig-exit-code-fix.patch
kconfig: fix menuconfig exit code
slab-poison-hex-dumping.patch
slab: hexdump for check_poison
p4-clockmod-cpu-detection-fix.patch
fix up CPU detection in p4-clockmod
suspend-resume-for-PIT.patch
suspend/resume support for PIT
truncated-module-check-2.patch
check for truncated modules
alpha-prefetch_spinlock-fix.patch
Alpha: make prefetch_spinlock() a no-op on UP
proc-pid-maps-gate-fixes.patch
Fix statically declare FIXMAPs
tmpfs-readdir-atime-fix.patch
tmpfs readdir does not update dir atime
blockdev-bd_private.patch
Add bdev private field
ext3-journal-mode-fix.patch
pentium-m-support.patch
add Pentium M and Pentium-4 M options
old-gcc-supports-k6.patch
gcc 2.95 supports -march=k6 (no need for check_gcc)
amd-elan-is-a-different-subarch.patch
AMD Elan is a different subarch
better-i386-cpu-selection.patch
better i386 CPU selection
efi-conditional-cleanup.patch
Arrange for EFI-related code to be compiled away
gcc-3_4-needs-attribute_used.patch
make gcc 3.4 compilation work
serial-01-fixups.patch
Serial fixups (mostly tested)
serial-02-fixups.patch
serial fixups (untested)
serial-02-fixups-fix.patch
serial-02 fixes
serial-02-fixes-fix-2.patch
serial-02 fixes
serial-03-fixups.patch
more serial driver fixups
serial-03-fixups-fix.patch
serial-03 fixes
serial-03-fixups-fix-2.patch
serial-03 fixes
BUG-to-BUG_ON.patch
if ... BUG() -> BUG_ON()
sysrq_key_table_key2index-fix.patch
sysrq_key_table_key2index() fixlets
set_scheduler-fix.patch
setscheduler fix
usr-isapnp-modem-support.patch
isapnp modem addition
ia32-MSI-vector-handling-fix.patch
ia32 MSI vector handling fix
load_elf_interp-error-case-fix.patch
fix error case in binfmt_elf.c:load_elf_interp
remove-null-initialisers.patch
remove null-ilizers
nuke-noisy-printks.patch
quiet down SMP boot messages
ppc-cond_syscall-fix.patch
ppc cond_syscall fix
PP0-full_list-RC1.patch
parport fixes [1/5]
PP1-parport_locking-RC1.patch
parport fixes [2/5]
PP2-enumerate1-RC1.patch
parport fixes [3/5]
PP2-enumerate1-RC1-fix.patch
PP3-parport_gsc-RC1.patch
parport fixes [4/5]
PP4-bwqcam-RC1.patch
parport fixes [5/5]
PP5-daisy-RC1.patch
parport fixes [2/5]
PI0-schedule_claimed-RC1.patch
paride cleanups and fixes [1/24]
PI1-expansion-RC1.patch
paride cleanups and fixes [2/24]
PI2-crapectomy-RC1.patch
paride cleanups and fixes [3/24]
PI3-ps_ready-RC1.patch
paride cleanups and fixes [4/24]
PI4-pd_busy-RC1.patch
paride cleanups and fixes [5/24]
PI5-do_pd_io-RC1.patch
paride cleanups and fixes [6/24]
PI6-bogus_requests-RC1.patch
paride cleanups and fixes [7/24]
PI7-claim_reorder-RC1.patch
paride cleanups and fixes [8/24]
PI8-do_pd_request1-RC1.patch
paride cleanups and fixes [9/24]
PI9-run_fsm-RC1.patch
paride cleanups and fixes [10/24]
PI10-action-RC1.patch
paride cleanups and fixes [2/24]
PI11-disconnect-RC1.patch
paride cleanups and fixes [12/24]
PI12-unclaim-RC1.patch
paride cleanups and fixes [13/24]
PI13-run_fsm-loop-RC1.patch
paride cleanups and fixes [14/24]
PI14-next_request-RC1.patch
paride cleanups and fixes [15/24]
PI15-do_pd_io-gone-RC1.patch
paride cleanups and fixes [16/24]
PI16-pd_claimed-RC1.patch
paride cleanups and fixes [17/24]
PI17-connect-RC1.patch
paride cleanups and fixes [18/24]
PI18-reorder-RC1.patch
paride cleanups and fixes [19/24]
PI19-special1-RC1.patch
paride cleanups and fixes [20/24]
PI20-gendisk_setup-RC1.patch
paride cleanups and fixes [21/24]
PI21-present-RC1.patch
paride cleanups and fixes [22/24]
PI22-pd_init_units-RC1.patch
paride cleanups and fixes [23/24]
PI23-special2-RC1.patch
paride cleanups and fixes [24/24]
PI24-paride64-RC1.patch
paride cleanups and fixes [25/24]
IMM0-lindent-RC1.patch
drivers/scsi/imm.c cleanups and fixes [1/8]
IMM1-references-RC1.patch
drivers/scsi/imm.c cleanups and fixes [2/8]
IMM2-claim-RC1.patch
drivers/scsi/imm.c cleanups and fixes [3/8]
IMM3-scsi_module-RC1.patch
drivers/scsi/imm.c cleanups and fixes [4/8]
IMM4-imm_probe-RC1.patch
drivers/scsi/imm.c cleanups and fixes [5/8]
IMM5-imm_wakeup-RC1.patch
drivers/scsi/imm.c cleanups and fixes [6/8]
IMM6-imm_hostdata-RC1.patch
drivers/scsi/imm.c cleanups and fixes [7/8]
IMM7-imm_attach-RC1.patch
drivers/scsi/imm.c cleanups and fixes [8/8]
PPA0-ppa_lindent-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [1/9]
PPA1-ppa_references-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [2/9]
PPA2-ppa_claim-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [3/9]
PPA3-ppa_scsi_module-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [4/9]
PPA4-ppa_probe-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [5/9]
PPA5-ppa_wakeup-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [6/9]
PPA6-ppa_hostdata-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [7/9]
PPA7-ppa_attach-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [8/9]
PPA8-ppa_lock_fix-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [9/9]
selinux-01-resource-limit-control.patch
selinux: Add resource limit control
selinux-02-netif-controls.patch
selinux: add netif controls
selinux-03-node-controls.patch
selinux: Add node controls
selinux-04-node_bind-control.patch
selinux: Add node_bind control
selinux-05-socket_has_perm-cleanup.patch
selinux: socket_has_perm cleanup
selinux-06-SO_PEERSEC-getpeersec.patch
selinux: Add SO_PEERSEC socket option and getpeersec LSM hook.
selinux-07-add-dname-to-audit-output.patch
selinux: Add dname to audit output when a path cannot be generated.
selinux-makefile-cleanup.patch
selinux: Makefile cleanup
selinux-improve-skb-audit-logging.patch
selinux: improve skb audit logging
selinux-SEND_MSG-RECV_MSG-controls.patch
Add SEND_MSG and RECV_MSG controls
nfs-fix-bogus-setattr-calls.patch
NFS: fix bogus setattr calls
nfs-optimise-COMMIT-calls.patch
nfs: Optimize away unnecessary NFSv3 COMMIT calls.
nfs-open-intent-fix.patch
nfs: Fix an open intent bug
nfs-readonly-mounts-fix.patch
nfs: Fix readonly mounts
nfs-client-deadlock-fix.patch
nfs: Fix a possible client deadlock
nfs-rpc-debug-oops-fix.patch
nfs: Fix an Oops in the RPC debug code...
nfs-01-rpc_pipe_timeout.patch
NFSv4/RPCSEC_GSS: userland upcall timeouts
nfs-02-auth_gss.patch
RPCSEC_GSS: More fixes to the upcall mechanism.
nfs-03-pipe_close.patch
RPCSEC_GSS: detect daemon death
nfs-04-fix_nfs4client.patch
NFSv4: oops fix
nfs-05-fix_idmap.patch
NFSv4: client name fixes
nfs-06-fix_idmap2.patch
NFSv4: Bugfixes and cleanups client name to uid mapper.
nfs-07-gss_krb5.patch
RPCSEC_GSS: Make it safe to share crypto tfms among multiple threads.
nfs-08-gss_missingkfree.patch
RPCSEC_GSS: Oops. Major memory leak here.
nfs-09-memleaks.patch
RPCSEC_GSS: Fix two more memory leaks found by the stanford checker.
nfs-10-refleaks.patch
RPCSEC_GSS: Fix yet more memory leaks.
nfs-11-krb5_cleanup.patch
RPCSEC_GSS: krb5 cleanups
nfs-12-gss_nokmalloc.patch
RPCSEC_GSS: memory allocation fixes
nfs-13-krb5_integ.patch
RPCSEC_GSS: Client-side only support for rpcsec_gss integrity protection.
nfs-14-clnt_seqno_to_req.patch
RPCSEC_GSS: gss sequence number history fixes
nfs-15-encode_pages_tail.patch
XDR: page encoding fix
nfs-16-rpc_clones.patch
RPC: transport sharing
nfs-17-rpc_clone2.patch
NFSv4/RPCSEC_GSS: use RPC cloning
nfs-18-renew_xdr.patch
NFSv4: make RENEW a standalone RPC call
nfs-19-renewd.patch
NFSv4: make lease renewal daemon per-server
nfs-20-fsinfo_xdr.patch
NFSv4: Split the code for retrieving static server information out of the GETATTR compound.
nfs-21-setclientid_xdr.patch
NFSv4: Make SETCLIENTID and SETCLIENTID_CONFIRM standalone operations
nfs-22-errno.patch
NFSv4: errno fixes
nfs-23-open_reclaim.patch
NFSv4: Preparation for the server reboot recovery code.
nfs-24-state_recovery.patch
NFSv4: Basic code for recovering file OPEN state after a server reboot.
nfs-25-soft.patch
RPC/NFSv4: Allow lease RENEW calls to be soft
nfs-26-sock_disconnect.patch
RPC: TCP timeout fixes
nfs-27-atomic_open.patch
NFSv4: Atomic open()
nfs-28-open_owner.patch
NFSv4: Share open_owner structs
nfs-29-fix_idmap3.patch
NFSv4: fix multi-partition mount oops
nfs_idmap-warning-fix.patch
nfs-30-lock.patch
NFSv4: Add support for POSIX file locking.
nfs-old-gcc-fix.patch
NFS: fix for older gcc's
nfs-31-attr.patch
NFSv2/v3/v4: New attribute revalidation code
m68knommu-module-support.patch
allow for building module support for m68knommu architecture
m68knommu-module-support-2.patch
add module support for m68knommu architecture
m68knommu-sched_clock.patch
sched_clock() for m68knommu architectures
m68knommu-include-fix.patch
m68knommu include fix
m68knommu-cpustats-fix.patch
fix cpu stats in m68knommu entry.S
m68knommu-types-cleanup.patch
use m68k/types.h for m68knommu
m68knommu-find_extend_vma.patch
implement find_extend_vma() for nommu
s390-01-base.patch
s390: general update
s390-02-common-io-layer.patch
s390: common i/o layer
s390-03-console-driver.patch
s390: console driver.
s390-04-dasd-driver.patch
s390: dasd driver
s390-05-tape-driver.patch
s390: tape driver.
s390-06-network-drivers.patch
s390: network drivers
s390-07-zfcp-host-adapter.patch
s390: zfcp host adapter
s390-07-zfcp-host-adapter-update.patch
zfcp host adapter patch cleanup
s390-08-new-3270-driver.patch
s390: new 3270 driver.
s390-09-32-bit-emulation-fixes.patch
s390: 32 bit emulation fixes.
s390-10-32-bit-ioctl-emulation-fixes.patch
s390: 32 bit ioctl emulation fixes.
s390-11-tlb-flush-optimisation.patch
s390: tlb flush optimization.
s390-12-dirty-referenced-bits.patch
s390: physical dirty/referenced bits.
s390-13-tlb-flush-race-fix.patch
s390: tlb flush race.
s390-14-rmap-optimisation.patch
s390: rmap optimization.
s390-14-rmap-optimisation-2.patch
rmap page refcounting simplification
s390-15-superfluous-flush_tlb_range-calls.patch
s390: superflous flush_tlb_range calls.
s390-16-follow_page-lockup-fix.patch
s390: endless loop in follow_page.
const-fixes.patch
const vs. __attribute__((const)) confusion
sn01.patch
sn: Some hwgraph code clean up
sn03.patch
sn: copyright update
sn05.patch
sn: namespace cleanup: ioerror_dump->sn_ioerror_dump
sn06.patch
sn: kill big endian stuff
sn07.patch
sn: kill $Id$
sn08.patch
sn: remove unused enum
sn09.patch
From: Pat Gefre <pfg@sgi.com>
Subject: Re: [PATCH] Updating our sn code in 2.6] - Patch 009
sn10.patch
sn: Kill nag.h
sn11.patch
sn: Kill the arcs/*.h files
sn12.patch
sn: Delete invent.h
sn13.patch
sn: General code clean up of sn/io/io.c
sn14.patch
sn: machvec/pci.c clean up
sn15.patch
sn: General clean up of xbow.c
sn16.patch
sn: Remove the bridge and xbridge code - everything not PIC
sn17.patch
sn: Fix the last patch - missed an IS_PIC_SOFT and needed the CG definition
sn18.patch
sn: Fix the last patch - missed an IS_PIC_SOFT and needed the CG definition
sn19.patch
sn: New code for Opus and CGbrick
sn20.patch
sn: klgraph.c clean up
sn21.patch
sn: More klgraph.c clean up
sn22.patch
sn: General module.c clean up
sn23.patch
sn: shubio.c cleanup
sn24.patch
sn: General xtalk.c clean up
sn25.patch
sn: irq clean up and update
sn26.patch
sn: code pruning - a couple of adds due to the clean up
sn27.patch
sn: Fix a couple of compiler warnings
sn28.patch
sn: hcl.c clean up for init failures and OOM
sn29.patch
sn: Some small bte code clean ups
sn30.patch
sn: Moved code out of pciio and into its own file - snia_if.c and renamed the functions
sn31.patch
sn: A few small clean ups
sn32.patch
sn: Some more minor clean up
sn33.patch
sn: Remove __ASSEMBLY__ tags from shubio.h
sn34.patch
sn: Small check for invalid node in shub ioctl function
sn35.patch
sn: More code clean up - this time ioconfig_bus.c
sn36.patch
sn: Code changes for interrupt redirect
sn37.patch
sn: Forget to check in the _reg file
sn38.patch
sn: Merged 2 files into another (sgi_io_sim and irix_io_init into sgi_io_init)
sn39.patch
sn: Support for the LCD
sn40.patch
sn: Missed an include file in the last patch
sn41.patch
sn: One less panic
sn42.patch
sn: SAL interface clean up
sn43.patch
sn: Fixes for shuberror.c
sn44.patch
sn: Need a bigger max compact node value
sn45.patch
sn: Use numionodes
sn46.patch
sn: Change the definition and usage of iio_itte - make it an array
sn47.patch
sn: Debug clean up in pcibr_dvr.c
sn48.patch
sn: New pci provider interfaces
sn49.patch
sn: Fix IIO_ITTE_DISABLE() args
sn50.patch
sn: Added a missed opus mod and oom mod
sn51.patch
sn: Added cbrick_type_get_nasid() function
sn52.patch
sn: Clean up the bit twiddle macros in pcibr_config.c
sn53.patch
sn: Fixed an oom in pci_bus_cvlink.c
sn54.patch
sn: Remove the pcibr_wrap... functions
sn55.patch
sn: printk cleanup
sn56.patch
sn: pci dma cleanup
sn57.patch
sn: Make pcibr debug variables static
sn58.patch
sn: Include file clean up in pcibr_hints.c
sn59.patch
sn: Added call to pcireg_intr_status_get
sn60.patch
sn: More code clean up = mostly pcibr_slot.c
sn61.patch
sn: pcibr_rrb.c cleanup
sn62.patch
sn: Minor code clean up of pcibr_error.c
sn63.patch
sn: sn_pci_fixup() clean up or is it fix up ???
sn65.patch
sn: Remove irix_io_init - replace with sgi_master_io_infr_init
sn66.patch
sn: Don't call init_hcl from the fixup code
sn67.patch
sn: Error devenable not used - delete defs
sn68.patch
sn: Delete unused code in pcibr_slot.c
sn69.patch
sn: Delete unused pciio.c code (???_host???_[sg]et)
sn70.patch
sn: Minor clean up for ml_iograph.c
sn71.patch
sn: Simulator check in pci_bus_cvlink.c
sn73.patch
sn: Mostly printk clean up and remove some dead code
sn74.patch
sn: A little re-formatting
sn75.patch
sn: cleanups and error checking
document-efi-zero-page-usage.patch
Document EFI zero-page usage
v4l-01-videodev-update.patch
[v4l] videodev update
v4l-02-v4l2-update.patch
[v4l] v4l2 update
v4l-03-video-buf-update.patch
[v4l] video-buf update
v4l-04-bttv-driver-update.patch
[v4l] bttv driver update
v4l-05-infrared-remote-support.patch
[v4l] add infrared remote support
v4l-06-misc-i2c-fixes.patch
[v4l] misc i2c fixes
v4l-07-tuner-update.patch
[v4l] tuner update
v4l-08-bttv-IR-input-support.patch
[v4l] add bttv IR input support.
v4l-09-saa7134-update.patch
[v4l] saa7134 driver update
v4l-10-conexant-2388x-driver.patch
[v4l] add conexant 2388x driver.
request-origination-determination-fix.patch
Use request_list as indicator that req originated from ll_rw_blk
ppc-module-skip-debug-sections.patch
modules: skip debug sections
MAINTAINERS-oprofile-update.patch
update OProfile maintainer
md-01-set_disk_faulty-return-code-fix.patch
md: fix return code in set_disk_faulty()
md-02-rebuild-needs-yield.patch
md: Don't allow raid5 rebuild to swamp raid5 stripe cache
md-03-resync-interrupt-fix.patch
md: Make sure an interrupted resync doesn't seem to have completed.
md-04-typo-fix.patch
md: Fix typo in comment
md-05-recovery-fix.patch
md: Make sure md recovery happens appropriately.
md-06-do_md_run-fix.patch
md: Don't do_md_stop and array when do_md_run fails.
md-07-superblock-writing-fixes.patch
md: Small fixes for timely writing of md superblocks.
md-08-remove-disks-array.patch
md: Remove the 'disks' array from md which holds the gendisk structures.
md-09-discard-mddev_map-array.patch
md: Discard the mddev_map array.
md-10-use-bd_disk-private_data.patch
md: Use bd_disk->private data instead of bd_inode->u.generic_ip
nfsd-01-stale-filehandles-fixes.patch
kNFSd: Fix problem with stale filehandles.
nfsd-02-failed-lookup-status-fix.patch
kNFSd: Convert error status for failed lookup("..") properly.
nfsd-03-follow_up-fix.patch
kNFSd: Fix incorrect call for follow_up
nfsd-04-add-dnotify-events.patch
kNFSd: Make sure dnotify events happen for NFS read and write.
nfsd-05-SUN-NFSv2-hack.patch
kNFSd: Honour SUN NFSv2 hack for "set times to server time.
nfsd-06-SVCFH_fmt-is-extern.patch
kNFSd: Move SVCFH_fmt from being 'inline' to being 'extern'.
ghash.patch
ghash.h from 2.4
tty_io-uml-fix.patch
uml: make tty_init callable from UML functions
uml-update.patch
UML update
proc_dma_open-simplification.patch
cleanup single_open usage in dma.c
rq_for_each_bio-fix.patch
rq_for_each_bio fix
remove-afs-strdup.patch
remove spurious strdup
list_del-debug.patch
list_del debug check
print-build-options-on-oops.patch
show_task-free-stack-fix.patch
show_task() fix and cleanup
oops-dump-preceding-code.patch
i386 oops output: dump preceding code
lockmeter.patch
uninline-bitmap-functions.patch
uninline bitmap functions
sock_put-inline-fix.patch
add-noinline-attribute.patch
Add noinline attribute
use-funit-at-a-time.patch
Use -funit-at-a-time when possible
add-config-for-mregparm-3.patch
Add CONFIG for -mregparm=3
add-config-for-mregparm-3-make-EXPERIMENTAL.patch
add-module-magic-for-mregparm3.patch
Add -mregparm info to module versioning
fix-x86_64-gcc-34-warnings.patch
Fix gcc 3.4 warnings in x86-64
fix-more-gcc-34-warnings.patch
Fix more gcc 3.4 warnings
gcc-34-string-fixes.patch
string fixes for gcc 3.4
4g-2.6.0-test2-mm2-A5.patch
4G/4G split patch
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g/4g usercopy atomicity fix
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g/4g usercopy atomicity fix
4G/4G preempt on vstack
4G/4G: even number of kmap types
4g4g: fix __get_user in slab
4g4g: Remove extra .data.idt section definition
4g/4g linker error (overlapping sections)
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g4g: show_registers() fix
4g/4g usercopy atomicity fix
4g4g: debug flags fix
4g4g: Fix wrong asm-offsets entry
cyclone time fixmap fix
4G/4G preempt on vstack
4G/4G: even number of kmap types
4g4g: fix __get_user in slab
4g4g: Remove extra .data.idt section definition
4g/4g linker error (overlapping sections)
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g4g: show_registers() fix
4g/4g usercopy atomicity fix
4g4g: debug flags fix
4g4g: Fix wrong asm-offsets entry
cyclone time fixmap fix
use direct_copy_{to,from}_user for kernel access in mm/usercopy.c
4G/4G might_sleep warning fix
4g/4g pagetable accounting fix
Fix 4G/4G and WP test lockup
4G/4G KERNEL_DS usercopy again
Fix 4G/4G X11/vm86 oops
Fix 4G/4G athlon triplefault
4g4g SEP fix
Fix 4G/4G split fix for pre-pentiumII machines
4g4g-locked-userspace-copy.patch
Do a locked user-space copy for 4g/4g
4g4g-acpi-low-mappings-fix.patch
4g/4g PAE ACPI low mappings fix
ppc-fixes.patch
make mm4 compile on ppc
O_DIRECT-race-fixes-rollup.patch
DIO fixes forward port and AIO-DIO fix
O_DIRECT race fixes comments
O_DRIECT race fixes fix fix fix
DIO locking rework
O_DIRECT XFS fix
dio-aio-fixes.patch
direct-io AIO fixes
dio-aio fix fix
aio-fallback-bio_count-race-fix-2.patch
AIO+DIO bio_count race fix
aio-sysctl-parms.patch
aio sysctl parms
^ permalink raw reply [flat|nested] 68+ messages in thread
* 2.6.1-mm4
@ 2004-01-16 6:59 ` Andrew Morton
0 siblings, 0 replies; 68+ messages in thread
From: Andrew Morton @ 2004-01-16 6:59 UTC (permalink / raw)
To: linux-kernel, linux-mm
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/
- There's a patch here which changes the ia32 CPU type selection. Make
sure you go in there and select the right CPU type(s), else the kernel
won't compile. We might need to set a default here.
- Kernel NFS server update
- MD update
- V4L update
- A string of fixes against the parport, paride and associated drivers
- Update to the latest UML
- Patches to support gcc-3.4 on ia32. There is more to do here - more
warnings need to be fixed and the exception tables need to be sorted. I
didn't add the `-Winline' patch because it's way too noisy at present.
Changes since 2.6.1-mm3:
linus.patch
Latest Linus tree
-scsi-rename-TIMEOUT.patch
-qla1280-update-2.patch
-qla1280-build-fix.patch
-sym-speed-fix.patch
-sym2-speed-selection-fix.patch
-aacraid-warning-fix.patch
-68k-359.patch
-68k-360.patch
-68k-365.patch
-68k-366.patch
-68k-378.patch
-68k-384.patch
-inia100-fix.patch
-mremap-dosemu-fix.patch
-symbios-build-fix.patch
Merged
-aic7xxx_old-proc-oops-fix.patch
-aic7xxx_old-oops-fix.patch
These broke.
+qla2xxx-build-fix.patch
Fix the new qlogic driver for older gcc's
-2.6.1-bk1-netdev4.patch
+netdev.patch
Recentish jgarzik tree
-keyboard-scancode-fix.patch
+keyboard-scancode-fixes.patch
+input-use-after-free-checks.patch
-input-print-screen-emulation-fix.patch
-input-use-after-free-checks.patch
+psmouse-timeout-parity-fixes.patch
More keyboard/mouse fixes
+acpi-frees-irq0.patch
ACPI fix.
-loop-bio-index-fix.patch
-loop-bio-clone.patch
-loop-recycle.patch
+loop-bio-handling-fix.patch
+loop-init-fix.patch
Go back to the loop patches which work.
+alsa-pnp-fix.patch
Fix PNP+ALSA combination
-sysfs_remove_dir-vs-dcache_readdir-race-fix.patch
This seems to be causing oopses
-sysfs-add-simple-class-device-support.patch
-sysfs-remove-tty-class-device-logic.patch
-sysfs-add-mem-device-support.patch
-sysfs-add-misc-class.patch
-vc-init-race-fix.patch
-sysfs-add-video-class.patch
-sysfs-add-oss-class.patch
-sysfs-add-alsa-class.patch
-sysfs-add-input-class-support.patch
+sysfs-class-01-simple.patch
+sysfs-class-02-input.patch
+sysfs-class-03-lp.patch
+sysfs-class-04-mem.patch
+sysfs-class-05-misc.patch
+sysfs-class-06-raw.patch
+sysfs-class-07-oss-sound.patch
+sysfs-class-08-alsa-sound.patch
+sysfs-class-09-cleanup-tty.patch
+sysfs-class-10-vc.patch
New sysfs simple-class support
+sched-clock-fixes.patch
+sched-build-fix.patch
+p4-clockmod-sibling-map-fix.patch
+sched-sync-rt-wakeup-fix.patch
CPU scheduler-related fixups
+eicon-buffer-allocation-fixes.patch
ISDN driver fix
-libata-update.patch
+2.6.1-bk2-libata1.patch
New libata update patch
+limit-hash-table-size-2.patch
Allow larger dentry+inode hashtable sizes on monster 64-bit boxen
+readahead-revert-lazy-readahead.patch
Revert a bit more of the recent readahead rework -it wasn't nice to NFS.
+better-i386-cpu-selection.patch
Finer-grained ia32 CPU type selection
+serial-02-fixups-fix.patch
+serial-02-fixes-fix-2.patch
+serial-03-fixups-fix.patch
+serial-03-fixups-fix-2.patch
Fix compile breakages
-increase-MAX_MP_BUSSES.patch
This is still under discussion
+remove-null-initialisers.patch
Small bss savings
+nuke-noisy-printks.patch
Less bootup messages
+ppc-cond_syscall-fix.patch
ppc32 build fix
+PP0-full_list-RC1.patch
+PP1-parport_locking-RC1.patch
+PP2-enumerate1-RC1.patch
+PP2-enumerate1-RC1-fix.patch
+PP3-parport_gsc-RC1.patch
+PP4-bwqcam-RC1.patch
+PP5-daisy-RC1.patch
+PI0-schedule_claimed-RC1.patch
+PI1-expansion-RC1.patch
+PI2-crapectomy-RC1.patch
+PI3-ps_ready-RC1.patch
+PI4-pd_busy-RC1.patch
+PI5-do_pd_io-RC1.patch
+PI6-bogus_requests-RC1.patch
+PI7-claim_reorder-RC1.patch
+PI8-do_pd_request1-RC1.patch
+PI9-run_fsm-RC1.patch
+PI10-action-RC1.patch
+PI11-disconnect-RC1.patch
+PI12-unclaim-RC1.patch
+PI13-run_fsm-loop-RC1.patch
+PI14-next_request-RC1.patch
+PI15-do_pd_io-gone-RC1.patch
+PI16-pd_claimed-RC1.patch
+PI17-connect-RC1.patch
+PI18-reorder-RC1.patch
+PI19-special1-RC1.patch
+PI20-gendisk_setup-RC1.patch
+PI21-present-RC1.patch
+PI22-pd_init_units-RC1.patch
+PI23-special2-RC1.patch
+PI24-paride64-RC1.patch
+IMM0-lindent-RC1.patch
+IMM1-references-RC1.patch
+IMM2-claim-RC1.patch
+IMM3-scsi_module-RC1.patch
+IMM4-imm_probe-RC1.patch
+IMM5-imm_wakeup-RC1.patch
+IMM6-imm_hostdata-RC1.patch
+IMM7-imm_attach-RC1.patch
+PPA0-ppa_lindent-RC1.patch
+PPA1-ppa_references-RC1.patch
+PPA2-ppa_claim-RC1.patch
+PPA3-ppa_scsi_module-RC1.patch
+PPA4-ppa_probe-RC1.patch
+PPA5-ppa_wakeup-RC1.patch
+PPA6-ppa_hostdata-RC1.patch
+PPA7-ppa_attach-RC1.patch
+PPA8-ppa_lock_fix-RC1.patch
parport/paride cleanups/fixes
+document-efi-zero-page-usage.patch
Documentation
+v4l-01-videodev-update.patch
+v4l-02-v4l2-update.patch
+v4l-03-video-buf-update.patch
+v4l-04-bttv-driver-update.patch
+v4l-05-infrared-remote-support.patch
+v4l-06-misc-i2c-fixes.patch
+v4l-07-tuner-update.patch
+v4l-08-bttv-IR-input-support.patch
+v4l-09-saa7134-update.patch
+v4l-10-conexant-2388x-driver.patch
V4L update
+request-origination-determination-fix.patch
Sanify the way in which we determine where a disk request came from
+ppc-module-skip-debug-sections.patch
ppc module loading fix/speedup
+MAINTAINERS-oprofile-update.patch
MAINTAINERS update
+md-01-set_disk_faulty-return-code-fix.patch
+md-02-rebuild-needs-yield.patch
+md-03-resync-interrupt-fix.patch
+md-04-typo-fix.patch
+md-05-recovery-fix.patch
+md-06-do_md_run-fix.patch
+md-07-superblock-writing-fixes.patch
+md-08-remove-disks-array.patch
+md-09-discard-mddev_map-array.patch
+md-10-use-bd_disk-private_data.patch
MD update
+nfsd-01-stale-filehandles-fixes.patch
+nfsd-02-failed-lookup-status-fix.patch
+nfsd-03-follow_up-fix.patch
+nfsd-04-add-dnotify-events.patch
+nfsd-05-SUN-NFSv2-hack.patch
+nfsd-06-SVCFH_fmt-is-extern.patch
kNFSD update
+ghash.patch
+tty_io-uml-fix.patch
+uml-update.patch
UML update
+proc_dma_open-simplification.patch
Code simplification
+rq_for_each_bio-fix.patch
Avoid possible problems with macro expansion
+remove-afs-strdup.patch
Remove dead code
+uninline-bitmap-functions.patch
+sock_put-inline-fix.patch
+add-noinline-attribute.patch
+use-funit-at-a-time.patch
+add-config-for-mregparm-3.patch
+add-config-for-mregparm-3-make-EXPERIMENTAL.patch
+add-module-magic-for-mregparm3.patch
+#add-W-inline.patch
+fix-x86_64-gcc-34-warnings.patch
+fix-more-gcc-34-warnings.patch
+gcc-34-string-fixes.patch
Patches to take advantage of gcc-3.4 features, and fixups for gcc-3.4.
All 620 patches:
linus.patch
mm.patch
add -mmN to EXTRAVERSION
qla2xxx-build-fix.patch
fix qla2xxx build for older gcc's
sh-merge.patch
SH Merge
sh-kyrofb-support.patch
kyrofb support
alsa-101.patch
ALSA 1.0.1
alsa-cmipci-joystick-fix.patch
netdev.patch
kgdb-ga.patch
kgdb stub for ia32 (George Anzinger's one)
kgdbL warning fix
kgdb buffer overflow fix
kgdbL warning fix
kgdb: CONFIG_DEBUG_INFO fix
x86_64 fixes
kgdb-doc-fix.patch
correct kgdb.txt Documentation link (against 2.6.1-rc1-mm2)
kgdboe-netpoll.patch
kgdb-over-ethernet via netpoll
kgdboe-non-ia32-build-fix.patch
kgdb-x86_64-support.patch
kgdb for x86_64 2.6 kernels
kgdb-x86_64-build-fix.patch
fix x86_64 build with CONFIG_KGDB=n
radeon-line-length-fix.patch
radeonfb line length fix
loop-fix-hardsect.patch
loop: fix hard sector size
loop-fd-leak-fix.patch
loop: fix file refcount leak
must-fix.patch
must fix lists update
must fix list update
mustfix update
must-fix-update-5.patch
must-fix update
modular-ide-is-broken.patch
document in must-fix that modular IDE is
RD1-open-mm.patch
RD2-release-mm.patch
RD3-presto_journal_close-mm.patch
RD4-f_mapping-mm.patch
RD5-f_mapping2-mm.patch
RD6-i_sem-mm.patch
RD7-f_mapping3-mm.patch
RD8-generic_osync_inode-mm.patch
RD9-bd_acquire-mm.patch
RD10-generic_write_checks-mm.patch
RD11-I_BDEV-mm.patch
cramfs-use-pagecache.patch
cramfs: use pagecache better
raw-driver-refcounting-fix.patch
raw.c refcounting fix
invalidate_inodes-speedup.patch
invalidate_inodes speedup
more invalidate_inodes speedup fixes
net-jiffy-normalisation-fix.patch
NET: Normalize jiffies reported to userspace, in neighbor management code
input-mousedev-remove-jitter.patch
Input: smooth out mouse jitter
input-mousedev-ps2-emulation-fix.patch
mousedev PS/@ emulation fix
input-01-i8042-suspend.patch
input: i8042 suspend
input-02-i8042-option-parsing.patch
input: i8042 option parsing
input-03-psmouse-option-parsing.patch
input: psmouse option parsing
input-04-atkbd-option-parsing.patch
input: atkbd option parsing
input-05-missing-module-licenses.patch
input: missing module licenses
input-06-Kconfig-Synaptics-help.patch
Kconfig Synaptics help
input-07-sis-aux-port.patch
input: SiS AUX port
input-11-98busmouse-compile-fix.patch
Fix compile error in 98busmouse.c module
input-12-mouse-drivers-use-module_param.patch
Convert mouse drivers to use module_param
input-13-tsdev-use-module_param.patch
Convert tsdev to use module_param
keyboard-scancode-fixes.patch
keyboard scancode fixes
input-use-after-free-checks.patch
input layer debug checks
synaptics-rate-switching.patch
Synaptics rate switching
psmouse-drop-timed-out-bytes.patch
psmouse: log and discard timed out bytes
psmouse-timeout-parity-fixes.patch
input: psmouse timeout&parity fixes
cpu_sibling_map-fix.patch
cpu_sibling_map fix
acpi-20031203.patch
acpi-20031203-fix.patch
acpi-frees-irq0.patch
acpi frees free irq0
cfq-4.patch
CFQ io scheduler
CFQ fixes
config_spinline.patch
uninline spinlocks for profiling accuracy.
ppc64-WARN_ON.patch
[ppc64] clean up WARN_ON backtrace
ppc64-IRQ_INPROGRESS.patch
[ppc64] revert IRQ_INPROGRESS change
ppc64-zImage_default.patch
[ppc64] Build the zImage by default
ppc64-biarch.patch
[ppc64] add automatic check for biarch compilers
ppc64-PT_FPSCR_fix.patch
[ppc64] ptrace.h PT_FPSCR fixup, from Will Schmidt
ppc64-writelogbuffer.patch
[ppc64] HvCall_writeLogBuffer called with too large of a buffer
ppc64-phandle.patch
[ppc64] support for ibm,phandle OF property, from Dave Engebretsen:
ppc64-of_traversal_api.patch
[ppc64] New Open Firmware device tree API, from Nathan Lynch
ppc64-of_traversal_api_2.patch
[PPC64] Change to new OF device tree API, from Nathan Lynch
ppc64-vty_node.patch
[ppc64] vty updates, from Hollis Blanchard
ppc64-hvc_console.patch
[ppc64] hvc_console can only handle vty nodes compatible with "hvterm1", from Hollis Blanchard
ppc64-device_is_compatible.patch
[ppc64] use device_is_compatible() instead of manual strcmp, from Hollis Blanchard
ppc64-smp_call_function.patch
[ppc64] Make IPI receivers survive a late arrival after the sender has given up waiting, from Olof Johansson
ppc64-device_tree_updates.patch
[ppc64] support for runtime updates of /proc/device-tree, from Nathan Lynch
ppc64-device_tree_updates_2.patch
[ppc64] base support for dynamic update of OF device, tree from Nathan Lynch
ppc64-trivial.patch
[ppc64] various trivial patches
ppc64-device_tree_updates_3.patch
[ppc64] Open Firmware device tree manipulation support, from Nathan Lynch
ppc64-ioremap_rework.patch
[ppc64] Mem-map I/O changes, from Mike Wolf
ppc64-rtas_flash.patch
[ppc64] extended flash changes, from Mike Wolf
ppc64-cputable.patch
[ppc64] cputable update, from Dave Engebretsen
ppc64-cputable_2.patch
[ppc64] cputable cleanup, from Dave Engebretsen:
ppc64-remove_MAX_PROCESSORS.patch
[ppc64] iSeries fixups, from Stephen Rothwel
ppc64-rtas_functions.patch
[ppc64] Add some rtas calls, from John Rose
ppc64-rtas_rename.patch
[ppc64] rename the rtas event classes to avoid namespace collisions, from John Rose
ppc64-stupidnumabug.patch
[ppc64] fix sign extension bug in NUMA code
ppc64-devinit_fixes.patch
[ppc64] Add exports and change some __init to __devinit for dynamic OF and pci hotplug, from John Rose and Linda Xie
ppc64-syscall6.patch
[ppc64] Add _syscall6, from Olaf Hering
ppc64-sched_clock.patch
[ppc64] fix sched_clock, from Paul Mackerras:
ppc64-compat_update.patch
[ppc64] compat layer update, from Paul Mackerras, Olaf Hering and myself
ppc64-sys_rtas.patch
[ppc64] add rtas syscall, from John Rose
ppc64-sharedproc.patch
[ppc64] shared processor support, from Dave Engebretsen
ppc64-logical_cpu.patch
[ppc46] SMT processor support and logical cpu numbering, from Dave Engebretsen
ppc64-UP_cleanup.patch
[ppc64] UP compile fixes, from Paul Mackerras
ppc64-add_vmx.patch
[ppc64] Add VMX registers to sigcontext, from Steve Munroe
ppc64-missing_sync.patch
[ppc64] one instruction fix for synchronization bug found during cpu DLPAR development, from Joel Schopp
ppc64-nvram_rewrite.patch
[ppc64] NVRAM error logging/buffering patch, from Jake Moilanen
ppc64-iseries_support.patch
[ppc64] preliminary iseries support, from Paul Mackerras
ppc64-hcall_constants.patch
[ppc64] Add additional hypervisor call constants, from Dave Boutcher
ppc64-iseries_cleanup.patch
[ppc64] iSeries fixes, from Stephen Rothwell
ppc64-device_tree_updates_fix.patch
[ppc64] fix a couple small OF device tree bugs which were overlooked, from Joel Schopp
ppc64-iseries_cleanup_2.patch
[ppc64] Tidy up various bits of the iSeries code. No significant code changes, from Stephen Rothwell
ppc64-remove-veth-proc.patch
[ppc64] Small cleanups to iSeries virtual ethernet driver, from Dave Gibson
ppc64-add_hcall.patch
[ppc64] add hcall interface
ppc64-addvio.patch
[ppc64] VIO support, from Dave Boutcher, Hollis Blanchard and Santiago Leon
ppc64-iseries_pci.patch
[ppc64] Get native PCI going on iSeries, from Paul Mackerras
ppc64-lparcfg.patch
[ppc64] add/forward port of lparcfg, from Will Schmidt
ppc64-surveillance.patch
[ppc64] Update the surveillance boot parameter to allow all valid settings of the surveillance timeout, from Nathan Fontenot
ppc64-power4fix.patch
[ppc64] fix POWER3 boot
ppc64-vmxsupport.patch
[ppc64] VMX (Altivec) support & signal32 rework, from Ben Herrenschmidt
ppc64-hash_page_race.patch
[ppc64] Fix {pte,pmd}_free vs. hash_page race by relaying actual deallocation with RCU, from Ben Herrenschmidt
ppc64-hash_page_rewrite.patch
[ppc64] __hash_page rewrite, from Ben Herrenschmidt
ppc64-mf_proc_cleanup.patch
[ppc64] Tidy up the mf_proc code, from Stephen Rothwell
ppc64-prom_panic.patch
[ppc64] prom_panic(), from Todd Inglett
ppc64-iseries_pci_2.patch
[ppc64] Check range of PCI memory and I/O accesses on iSeries, from Stephen Rothwell
ppc64-iseries_fixes.patch
[ppc64] Fix a compile error and a warning in the iSeries code, from Stephen Rothwell
ppc64-viopath_fix.patch
[ppc64] Use an atomic_t instead of a volatile unsigned long, from Stephen Rothwell
ppc64-makefile_fixes.patch
[ppc64] Makefile fixes
ppc64-vmlinux_lds.patch
[ppc64] vmlinux.lds fixes, from Alan Modra
ppc64-setup_cpu.patch
[ppc64] setup_cpu must be called on boot cpu
ppc64-epoll.patch
[ppc64] correct epoll syscall names
ppc64-compat_stat.patch
[ppc64] cp_compat_stat should copy nanosecond fields
ppc64-xmon_fixes.patch
[ppc64] xmon breakpoint and single step on LPAR fixes from John Rose
ppc64-rtas_delay.patch
[ppc64] Fixed rtas_extended_busy_delay_time() to calculate correct value, from John Rose
ppc64-bss_clear.patch
[ppc64] early BSS clear, from Ben Herrenschmidt
ppc64-vio-fixup.patch
[ppc64] vio fixup
ppc64-bar-0-fix.patch
Allow PCI BARs that start at 0
ppc64-reloc_hide.patch
ramdisk-leak-fix.patch
fix memory leak in ram disk
ramdisk-cleanup.patch
intel8x0-cleanup.patch
intel8x0 cleanups
pdflush-diag.patch
zap_page_range-debug.patch
zap_page_range() debug
asus-L5-fix.patch
Asus L5 framebuffer fix
jffs-use-daemonize.patch
get_user_pages-handle-VM_IO.patch
support-zillions-of-scsi-disks.patch
support many SCSI disks
pci_set_power_state-might-sleep.patch
CONFIG_STANDALONE-default-to-n.patch
Make CONFIG_STANDALONE default to N
extra-buffer-diags.patch
CONFIG_SYSFS.patch
From: Pat Mochel <mochel@osdl.org>
Subject: [PATCH] Add CONFIG_SYSFS
CONFIG_SYSFS-boot-from-disk-fix.patch
slab-leak-detector.patch
slab leak detector
loop-module-alias.patch
loop needs MODULE_ALIAS_BLOCK
loop-remove-blkdev-special-case.patch
loop-highmem.patch
remove useless highmem bounce from loop/cryptoloop
loop-bio-handling-fix.patch
loop: BIO handling fix
loop-init-fix.patch
loop.c doesn't fail init gracefully
acpi-pm-timer-3.patch
ACPI PM timer version 3
as-regression-fix.patch
Fix IO scheduler regression
as-request-poisoning.patch
AS: request poisoning
as-request-poisoning-fix.patch
AS: request poisining fix
as-fix-all-known-bugs.patch
AS fixes
as-new-process-estimation.patch
AS: new process estimation
as-cooperative-thinktime.patch
AS: thinktime improvement
as-tuning.patch
AS tuning
scale-nr_requests.patch
scale nr_requests with TCQ depth
truncate_inode_pages-check.patch
local_bh_enable-warning-fix.patch
pnp-fix-2.patch
PnP Fixes #2
pnp-fix-3.patch
PnP Fixes #3
alsa-pnp-fix.patch
ALSA pnp fix
alpha-stack-dump.patch
invalidate_mmap_range-non-gpl-export.patch
mark invalidate_mmap_range() as EXPORT_SYMBOL
ppc-export-consistent_sync_page.patch
PPC32: Export consistent_sync_page.
ppc-use-EXPORT_SYMBOL_NOVERS.patch
PPC32: Change all EXPORT_SYMBOL_NOVERS to EXPORT_SYMBOL in ppc_ksyms.c
ppc-CONFIG_PPC_STD_MMU-fix.patch
PPC32: Select arch/ppc/kernel/head.S on CONFIG_PPC_STD_MMU.
ppc-IBM-MPC-header-cleanups.patch
PPC32: Minor cleanups to IBM4xx and MPC82xx headers.
percpu-gcc-34-warning-fix.patch
fix gcc-3.4 warning in percpu code
nr_requests-oops-fix.patch
Fix oops when modifying /sys/block/dm-0/queue/nr_requests
netfilter_bridge-compile-fix.patch
atapi-mo-support.patch
ATAPI MO drive support
mt-ranier-support.patch
mt rainier support
atapi-mo-support-update.patch
ATAPI MO support update
cdrom_open fix
ppp_async-locking-fix.patch
Make ppp_async callable from hard interrupt
make-try_to_free_pages-walk-zonelist.patch
make try_to_free_pages walk zonelist
make-try_to_free_pages-walk-zonelist-fix.patch
zone scanning fix
remove-CardServices-from-pcmcia-net-drivers.patch
CardServices() removal from pcmcia net drivers
remove-CardServices-from-ide-cs.patch
From: Arjan van de Ven <arjanv@redhat.com>
Subject: Re: [PATCH 1/10] CardServices() removal from pcmcia net drivers
remove-CardServices-from-drivers-net-wireless.patch
remove CardServices() from drivers/net/wireless
remove-CardServices-from-drivers-serial.patch
Remvoe CardServices() from drivers/serial
remove-CardServices-from-drivers-serial-fix.patch
serial_cs CardServices removal fix
remove-CardServices-from-axnet_cs.patch
remvoe CardServices from axnet_cs
remove-CardServices-final.patch
final CardServices() removal patches
CardServices-compatibility-layer.patch
CardServices compatibility layer
sysfs-class-01-simple.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add class_simple support [01/10]
sysfs-class-02-input.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for input devices [02/10]
sysfs-class-03-lp.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add class support for lp devices [03/10]
sysfs-class-04-mem.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for mem devices [04/10]
sysfs-class-05-misc.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for misc devices [05/10]
sysfs-class-06-raw.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for raw devices [06/10]
sysfs-class-07-oss-sound.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for OSS sound devices [07/10]
sysfs-class-08-alsa-sound.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for ALSA sound devices [08/10]
sysfs-class-09-cleanup-tty.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] clean up sysfs class support for tty devices [09/10]
sysfs-class-10-vc.patch
From: Greg KH <greg@kroah.com>
Subject: [PATCH] add sysfs class support for vc devices [10/10]
tridentfb-non-flatpanel-fix.patch
fix for tridentfb.c usage on CRTs.
CONFIG_EPOLL-file_struct-members.patch
CONFIG_EPOLL=n space reduction
epoll-oneshot-support.patch
One-shot support for epoll
kill_fasync-speedup.patch
kill_fasync speedup
o21-sched.patch
O21 for interactivity 2.6.0
sched-clock-2.6.0-A1.patch
Relax synchronization of sched_clock()
sched-can-migrate-2.6.0-A2.patch
can_migrate_task cleanup
sched-cleanup-2.6.0-A2.patch
CPU scheduler cleanup
sched-style-2.6.0-A5.patch
sched.c style cleanups
make-for_each_cpu-iterator-more-friendly.patch
Make for_each_cpu() Iterator More Friendly
make-for_each_cpu-iterator-more-friendly-fix.patch
Fix alpha build failure
make-for_each_cpu-iterator-more-friendly-fix-fix.patch
use-for_each_cpu-in-right-places.patch
Use for_each_cpu() Where It's Meant To Be
for_each_cpu-oprofile-fix.patch
for_each_cpu oprofile fix
for_each_cpu-oprofile-fix-2.patch
sched-find_busiest_node-resolution-fix.patch
sched: improved resolution in find_busiest_node
sched-domains.patch
sched: scheduler domain support
sched-clock-fixes.patch
fix sched_clock()
sched-build-fix.patch
sched: fix for NR_CPUS > BITS_PER_LONG
sched-sibling-map-to-cpumask.patch
sched: cpu_sibling_map to cpu_mask
p4-clockmod-sibling-map-fix.patch
p4-clockmod sibling_map fix
sched-domains-i386-ht.patch
sched: implement domains for i386 HT
acpi-numa-printk-level-fixes.patch
ACPI NUMA quiet printk and cleanup
sched-sync-rt-wakeup-fix.patch
sched: fix sync wakeups of RT tasks
decrypt-CONFIG_PDC202XX_FORCE-help.patch
Change cryptic description and help for CONFIG_PDC202XX_FORCE
ide-siimage-seagate.patch
ide-siimage-stack-fix.patch
ide-siimage-sil3114.patch
ide-pdc_old-pio-fix.patch
ide-pdc_old-udma66-fix.patch
ide-pdc_old-66mhz_clock-fix.patch
ide-pdc_new-proc.patch
fa311-mac-address-fix.patch
wrong mac address with netgear FA311 ethernet card
kernel-locking-doc-end-tags-fix.patch
Missing end tags in kernel-locking kerneldoc
rcupdate-c99-initialisers.patch
C99 change to rcupdate.h
68k-339.patch
M68k floppy selection
68k-340.patch
M68k head console
68k-341.patch
M68k head unused
68k-342.patch
M68k head comments
68k-343.patch
M68k head pic
68k-344.patch
M68k head white space
68k-345.patch
M68k cache mode
68k-346.patch
M68k RMW accesses
68k-347.patch
Atari Hades PCI C99
68k-348.patch
Amiga sound C99
68k-349.patch
BVME6000 RTC C99
68k-350.patch
M68k symbol exports
68k-351.patch
M68k math emu C99
68k-352.patch
MVME16x RTC C99
68k-353.patch
Q40 interrupts C99
68k-354.patch
Sun-3 ID PROM C99
68k-355.patch
Mac ADB IOP fix
68k-361.patch
Macfb setup
68k-364.patch
Mac ADB
68k-367.patch
Amiga Gayle IDE cleanup
68k-368.patch
Amiga Gayle E-Matrix 530 IDE
68k-369.patch
Zorro sysfs/driver model
68k-374.patch
Amiga debug fix
68k-375.patch
Mac II VIA
68k-377.patch
M68k asm/system.h
68k-379.patch
Amiga core C99
68k-380.patch
M68k has no VGA/MDA
68k-381.patch
M68k thread
68k-382.patch
M68k thread_info
68k-383.patch
M68k extern inline
68k-385.patch
Cirrusfb extern inline
68k-386.patch
Genrtc warning
68k-387.patch
M68k Documentation
68k-390.patch
Amiga Buddha/CatWeasel IDE
printk_ratelimit.patch
generalise net_ratelimit (printk_ratelimit)
printk_ratelimit-fix.patch
parintk_ratelimit fix
freevxfs-MODULE_ALIAS.patch
MODULE_ALIAS for freevxfs
trident-cleanup-indentation-D1-2.6.0.patch
reindent trident OSS sound driver
trident-sound-driver-fixes.patch
trident OSS sound driver fixes
trident-cleanup-2.patch
trident: use pr_debug instead of home-brewed TRDBG
compound-page-page_count-fix.patch
fix page counting for compound pages
MAINTAINERS-lanana-update.patch
MAINTAINERS update
devfs-joystick-fix.patch
fix devfs names for joystick
s3-sleep-remove-debug-code.patch
s3 sleep: Kill obsolete debugging code
swsusp-doc-updates.patch
swsusp/sleep documentation update
watchdog-updates.patch
Watchdog patches
watchdog-updates-2.patch
Watchdog patches (part 2)
ext2_new_inode-cleanup.patch
ext2_new_inode nanocleanup
ext2-s_next_generation-fix.patch
ext2: s_next_generation locking
ext3-s_next_generation-fix.patch
ext3: s_next_generation fixes
alt-arrow-console-switch-fix.patch
Fix Alt-arrow console switch droppage
alt-arrow-console-switch-fix-2.patch
Alt-arrow console switch #2
ia32-remove-SIMNOW.patch
Remove x86_64 leftover SIMNOW code
softcursor-fix.patch
Fix softcursor
ext2-debug-build-fix.patch
ext2: fix build when EXT2_DEBUG is set
efi-inline-fixes.patch
Fix weird placement of inline
do_timer_gettime-cleanup.patch
do_timer_gettime() cleanup
set_cpus_allowed-locking-fix.patch
set_cpus_allowed locking
fix set_cpus_allowed locking even more
rmmod-race-fix.patch
module removal race fix
remove-hpet-intel-check.patch
Remove Intel check in i386 HPET code
devfs-d_revalidate-oops-fix.patch
devfs d_revalidate race/oops fix
laptop-mode-2.patch
laptop-mode for 2.6, version 6
laptop-mode-doc-update.patch
Documentation/laptop-mode.txt
laptop-mode-2-doc-updates.patch
laptop-mode documentation updates
ali-m1533-hang-fix.patch
ALI M1533 audio hang fix
start_this_handle-retval-fix.patch
jbd: start_this_handle() return value fix
remove-eicon-isdn-driver.patch
remove old Eicon isdn driver
eicon-memory-access-size-fix.patch
Eicon isdn driver hardware access fix
eicon-buffer-allocation-fixes.patch
Eicon isdn driver alloc buffer size fix
do_no_page-leak-fix.patch
do_no_page leak fix
vt-locking-fixes-2.patch
VT locking patch #2
pid_max-fix.patch
Bug when setting pid_max > 32k
allow-SGI-IOC4-chipset-support.patch
allow SGI IOC4 chipset support
oss-dmabuf-deadlock-fix.patch
OSS dmabuf deadlock fix
workqueue-cleanup.patch
Remove redundant code in workqueue.c
2.6.1-bk2-libata1.patch
tridentfb-documentation-fix.patch
tridentfb documentation fix
proc_pid_lookup-speedup.patch
Optimize proc_pid_lookup
bio_endio-clarifications.patch
clarify meaning of bio fields in the end_io function
rtc-leak-fixes.patch
2.6.1 RTC leaks.
simplify-node-zone-fields-3.patch
Simplify node/zone field in page->flags
radeonfb-pdi-id-addition.patch
Identify RADEON Yd in radeonfb
mpt-fusion-update.patch
MPT Fusion driver 3.00.00 update
use-soft-float.patch
Use -msoft-float
DRM-cvs-update.patch
DRM cvs update
sis-DRM-floating-point-removal.patch
Remove float from sis DRM
drm-include-fix.patch
raid6-20040107.patch
RAID-6
raid6-readahead-fix.patch
RAID-6 readahead fix
kthread-primitive.patch
kthread primitive
use-kthread-primitives.patch
Use kthread primitives
alpha-module-relocation-overflow-fix.patch
Relocation overflow with modules on Alpha
ppc32-of-bootwrapper-support.patch
ppc32: OF bootwrapper support
lsi-megaraid-pci-id.patch
LSI Logic MegaRAID3 PCI ID
ide-pci-modules-fix.patch
fix issues with loading PCI IDE drivers as modules
use-diff-dash-p.patch
Fix Documentation/SubmittingPatches to use -p
use-kconfig-range-for-NR_CPUS.patch
Kconfig: use range for NR_CPUS
sysfs-pin-kobject.patch
sysfs: pin kobjects to fix use-after-free crashes
bio-documentation-update.patch
bio documentation update
limit-hash-table-sizes.patch
Subject: Limit hash table size
limit-hash-table-size-2.patch
hash table size limiting: huge 64-bit fixes
add-SIOCSIFNAME-compat-ioctl.patch
Add SIOCSIFNAME compat ioctl
disable-G400-DRM-on-x86_64.patch
Disable G400 DRM driver on x86-64
x86_64-merge.patch
x86-64 merge for 2.6.1
init-zone-priorities.patch
vmscan: initialize zone->{prev,temp}_priority
readahead-partial-backout.patch
radahead part-backout
readahead-revert-lazy-readahead.patch
readaheadL revert lazy readahead
menuconfig-exit-code-fix.patch
kconfig: fix menuconfig exit code
slab-poison-hex-dumping.patch
slab: hexdump for check_poison
p4-clockmod-cpu-detection-fix.patch
fix up CPU detection in p4-clockmod
suspend-resume-for-PIT.patch
suspend/resume support for PIT
truncated-module-check-2.patch
check for truncated modules
alpha-prefetch_spinlock-fix.patch
Alpha: make prefetch_spinlock() a no-op on UP
proc-pid-maps-gate-fixes.patch
Fix statically declare FIXMAPs
tmpfs-readdir-atime-fix.patch
tmpfs readdir does not update dir atime
blockdev-bd_private.patch
Add bdev private field
ext3-journal-mode-fix.patch
pentium-m-support.patch
add Pentium M and Pentium-4 M options
old-gcc-supports-k6.patch
gcc 2.95 supports -march=k6 (no need for check_gcc)
amd-elan-is-a-different-subarch.patch
AMD Elan is a different subarch
better-i386-cpu-selection.patch
better i386 CPU selection
efi-conditional-cleanup.patch
Arrange for EFI-related code to be compiled away
gcc-3_4-needs-attribute_used.patch
make gcc 3.4 compilation work
serial-01-fixups.patch
Serial fixups (mostly tested)
serial-02-fixups.patch
serial fixups (untested)
serial-02-fixups-fix.patch
serial-02 fixes
serial-02-fixes-fix-2.patch
serial-02 fixes
serial-03-fixups.patch
more serial driver fixups
serial-03-fixups-fix.patch
serial-03 fixes
serial-03-fixups-fix-2.patch
serial-03 fixes
BUG-to-BUG_ON.patch
if ... BUG() -> BUG_ON()
sysrq_key_table_key2index-fix.patch
sysrq_key_table_key2index() fixlets
set_scheduler-fix.patch
setscheduler fix
usr-isapnp-modem-support.patch
isapnp modem addition
ia32-MSI-vector-handling-fix.patch
ia32 MSI vector handling fix
load_elf_interp-error-case-fix.patch
fix error case in binfmt_elf.c:load_elf_interp
remove-null-initialisers.patch
remove null-ilizers
nuke-noisy-printks.patch
quiet down SMP boot messages
ppc-cond_syscall-fix.patch
ppc cond_syscall fix
PP0-full_list-RC1.patch
parport fixes [1/5]
PP1-parport_locking-RC1.patch
parport fixes [2/5]
PP2-enumerate1-RC1.patch
parport fixes [3/5]
PP2-enumerate1-RC1-fix.patch
PP3-parport_gsc-RC1.patch
parport fixes [4/5]
PP4-bwqcam-RC1.patch
parport fixes [5/5]
PP5-daisy-RC1.patch
parport fixes [2/5]
PI0-schedule_claimed-RC1.patch
paride cleanups and fixes [1/24]
PI1-expansion-RC1.patch
paride cleanups and fixes [2/24]
PI2-crapectomy-RC1.patch
paride cleanups and fixes [3/24]
PI3-ps_ready-RC1.patch
paride cleanups and fixes [4/24]
PI4-pd_busy-RC1.patch
paride cleanups and fixes [5/24]
PI5-do_pd_io-RC1.patch
paride cleanups and fixes [6/24]
PI6-bogus_requests-RC1.patch
paride cleanups and fixes [7/24]
PI7-claim_reorder-RC1.patch
paride cleanups and fixes [8/24]
PI8-do_pd_request1-RC1.patch
paride cleanups and fixes [9/24]
PI9-run_fsm-RC1.patch
paride cleanups and fixes [10/24]
PI10-action-RC1.patch
paride cleanups and fixes [2/24]
PI11-disconnect-RC1.patch
paride cleanups and fixes [12/24]
PI12-unclaim-RC1.patch
paride cleanups and fixes [13/24]
PI13-run_fsm-loop-RC1.patch
paride cleanups and fixes [14/24]
PI14-next_request-RC1.patch
paride cleanups and fixes [15/24]
PI15-do_pd_io-gone-RC1.patch
paride cleanups and fixes [16/24]
PI16-pd_claimed-RC1.patch
paride cleanups and fixes [17/24]
PI17-connect-RC1.patch
paride cleanups and fixes [18/24]
PI18-reorder-RC1.patch
paride cleanups and fixes [19/24]
PI19-special1-RC1.patch
paride cleanups and fixes [20/24]
PI20-gendisk_setup-RC1.patch
paride cleanups and fixes [21/24]
PI21-present-RC1.patch
paride cleanups and fixes [22/24]
PI22-pd_init_units-RC1.patch
paride cleanups and fixes [23/24]
PI23-special2-RC1.patch
paride cleanups and fixes [24/24]
PI24-paride64-RC1.patch
paride cleanups and fixes [25/24]
IMM0-lindent-RC1.patch
drivers/scsi/imm.c cleanups and fixes [1/8]
IMM1-references-RC1.patch
drivers/scsi/imm.c cleanups and fixes [2/8]
IMM2-claim-RC1.patch
drivers/scsi/imm.c cleanups and fixes [3/8]
IMM3-scsi_module-RC1.patch
drivers/scsi/imm.c cleanups and fixes [4/8]
IMM4-imm_probe-RC1.patch
drivers/scsi/imm.c cleanups and fixes [5/8]
IMM5-imm_wakeup-RC1.patch
drivers/scsi/imm.c cleanups and fixes [6/8]
IMM6-imm_hostdata-RC1.patch
drivers/scsi/imm.c cleanups and fixes [7/8]
IMM7-imm_attach-RC1.patch
drivers/scsi/imm.c cleanups and fixes [8/8]
PPA0-ppa_lindent-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [1/9]
PPA1-ppa_references-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [2/9]
PPA2-ppa_claim-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [3/9]
PPA3-ppa_scsi_module-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [4/9]
PPA4-ppa_probe-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [5/9]
PPA5-ppa_wakeup-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [6/9]
PPA6-ppa_hostdata-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [7/9]
PPA7-ppa_attach-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [8/9]
PPA8-ppa_lock_fix-RC1.patch
drivers/scsi/ppa.c cleanups and fixes [9/9]
selinux-01-resource-limit-control.patch
selinux: Add resource limit control
selinux-02-netif-controls.patch
selinux: add netif controls
selinux-03-node-controls.patch
selinux: Add node controls
selinux-04-node_bind-control.patch
selinux: Add node_bind control
selinux-05-socket_has_perm-cleanup.patch
selinux: socket_has_perm cleanup
selinux-06-SO_PEERSEC-getpeersec.patch
selinux: Add SO_PEERSEC socket option and getpeersec LSM hook.
selinux-07-add-dname-to-audit-output.patch
selinux: Add dname to audit output when a path cannot be generated.
selinux-makefile-cleanup.patch
selinux: Makefile cleanup
selinux-improve-skb-audit-logging.patch
selinux: improve skb audit logging
selinux-SEND_MSG-RECV_MSG-controls.patch
Add SEND_MSG and RECV_MSG controls
nfs-fix-bogus-setattr-calls.patch
NFS: fix bogus setattr calls
nfs-optimise-COMMIT-calls.patch
nfs: Optimize away unnecessary NFSv3 COMMIT calls.
nfs-open-intent-fix.patch
nfs: Fix an open intent bug
nfs-readonly-mounts-fix.patch
nfs: Fix readonly mounts
nfs-client-deadlock-fix.patch
nfs: Fix a possible client deadlock
nfs-rpc-debug-oops-fix.patch
nfs: Fix an Oops in the RPC debug code...
nfs-01-rpc_pipe_timeout.patch
NFSv4/RPCSEC_GSS: userland upcall timeouts
nfs-02-auth_gss.patch
RPCSEC_GSS: More fixes to the upcall mechanism.
nfs-03-pipe_close.patch
RPCSEC_GSS: detect daemon death
nfs-04-fix_nfs4client.patch
NFSv4: oops fix
nfs-05-fix_idmap.patch
NFSv4: client name fixes
nfs-06-fix_idmap2.patch
NFSv4: Bugfixes and cleanups client name to uid mapper.
nfs-07-gss_krb5.patch
RPCSEC_GSS: Make it safe to share crypto tfms among multiple threads.
nfs-08-gss_missingkfree.patch
RPCSEC_GSS: Oops. Major memory leak here.
nfs-09-memleaks.patch
RPCSEC_GSS: Fix two more memory leaks found by the stanford checker.
nfs-10-refleaks.patch
RPCSEC_GSS: Fix yet more memory leaks.
nfs-11-krb5_cleanup.patch
RPCSEC_GSS: krb5 cleanups
nfs-12-gss_nokmalloc.patch
RPCSEC_GSS: memory allocation fixes
nfs-13-krb5_integ.patch
RPCSEC_GSS: Client-side only support for rpcsec_gss integrity protection.
nfs-14-clnt_seqno_to_req.patch
RPCSEC_GSS: gss sequence number history fixes
nfs-15-encode_pages_tail.patch
XDR: page encoding fix
nfs-16-rpc_clones.patch
RPC: transport sharing
nfs-17-rpc_clone2.patch
NFSv4/RPCSEC_GSS: use RPC cloning
nfs-18-renew_xdr.patch
NFSv4: make RENEW a standalone RPC call
nfs-19-renewd.patch
NFSv4: make lease renewal daemon per-server
nfs-20-fsinfo_xdr.patch
NFSv4: Split the code for retrieving static server information out of the GETATTR compound.
nfs-21-setclientid_xdr.patch
NFSv4: Make SETCLIENTID and SETCLIENTID_CONFIRM standalone operations
nfs-22-errno.patch
NFSv4: errno fixes
nfs-23-open_reclaim.patch
NFSv4: Preparation for the server reboot recovery code.
nfs-24-state_recovery.patch
NFSv4: Basic code for recovering file OPEN state after a server reboot.
nfs-25-soft.patch
RPC/NFSv4: Allow lease RENEW calls to be soft
nfs-26-sock_disconnect.patch
RPC: TCP timeout fixes
nfs-27-atomic_open.patch
NFSv4: Atomic open()
nfs-28-open_owner.patch
NFSv4: Share open_owner structs
nfs-29-fix_idmap3.patch
NFSv4: fix multi-partition mount oops
nfs_idmap-warning-fix.patch
nfs-30-lock.patch
NFSv4: Add support for POSIX file locking.
nfs-old-gcc-fix.patch
NFS: fix for older gcc's
nfs-31-attr.patch
NFSv2/v3/v4: New attribute revalidation code
m68knommu-module-support.patch
allow for building module support for m68knommu architecture
m68knommu-module-support-2.patch
add module support for m68knommu architecture
m68knommu-sched_clock.patch
sched_clock() for m68knommu architectures
m68knommu-include-fix.patch
m68knommu include fix
m68knommu-cpustats-fix.patch
fix cpu stats in m68knommu entry.S
m68knommu-types-cleanup.patch
use m68k/types.h for m68knommu
m68knommu-find_extend_vma.patch
implement find_extend_vma() for nommu
s390-01-base.patch
s390: general update
s390-02-common-io-layer.patch
s390: common i/o layer
s390-03-console-driver.patch
s390: console driver.
s390-04-dasd-driver.patch
s390: dasd driver
s390-05-tape-driver.patch
s390: tape driver.
s390-06-network-drivers.patch
s390: network drivers
s390-07-zfcp-host-adapter.patch
s390: zfcp host adapter
s390-07-zfcp-host-adapter-update.patch
zfcp host adapter patch cleanup
s390-08-new-3270-driver.patch
s390: new 3270 driver.
s390-09-32-bit-emulation-fixes.patch
s390: 32 bit emulation fixes.
s390-10-32-bit-ioctl-emulation-fixes.patch
s390: 32 bit ioctl emulation fixes.
s390-11-tlb-flush-optimisation.patch
s390: tlb flush optimization.
s390-12-dirty-referenced-bits.patch
s390: physical dirty/referenced bits.
s390-13-tlb-flush-race-fix.patch
s390: tlb flush race.
s390-14-rmap-optimisation.patch
s390: rmap optimization.
s390-14-rmap-optimisation-2.patch
rmap page refcounting simplification
s390-15-superfluous-flush_tlb_range-calls.patch
s390: superflous flush_tlb_range calls.
s390-16-follow_page-lockup-fix.patch
s390: endless loop in follow_page.
const-fixes.patch
const vs. __attribute__((const)) confusion
sn01.patch
sn: Some hwgraph code clean up
sn03.patch
sn: copyright update
sn05.patch
sn: namespace cleanup: ioerror_dump->sn_ioerror_dump
sn06.patch
sn: kill big endian stuff
sn07.patch
sn: kill $Id$
sn08.patch
sn: remove unused enum
sn09.patch
From: Pat Gefre <pfg@sgi.com>
Subject: Re: [PATCH] Updating our sn code in 2.6] - Patch 009
sn10.patch
sn: Kill nag.h
sn11.patch
sn: Kill the arcs/*.h files
sn12.patch
sn: Delete invent.h
sn13.patch
sn: General code clean up of sn/io/io.c
sn14.patch
sn: machvec/pci.c clean up
sn15.patch
sn: General clean up of xbow.c
sn16.patch
sn: Remove the bridge and xbridge code - everything not PIC
sn17.patch
sn: Fix the last patch - missed an IS_PIC_SOFT and needed the CG definition
sn18.patch
sn: Fix the last patch - missed an IS_PIC_SOFT and needed the CG definition
sn19.patch
sn: New code for Opus and CGbrick
sn20.patch
sn: klgraph.c clean up
sn21.patch
sn: More klgraph.c clean up
sn22.patch
sn: General module.c clean up
sn23.patch
sn: shubio.c cleanup
sn24.patch
sn: General xtalk.c clean up
sn25.patch
sn: irq clean up and update
sn26.patch
sn: code pruning - a couple of adds due to the clean up
sn27.patch
sn: Fix a couple of compiler warnings
sn28.patch
sn: hcl.c clean up for init failures and OOM
sn29.patch
sn: Some small bte code clean ups
sn30.patch
sn: Moved code out of pciio and into its own file - snia_if.c and renamed the functions
sn31.patch
sn: A few small clean ups
sn32.patch
sn: Some more minor clean up
sn33.patch
sn: Remove __ASSEMBLY__ tags from shubio.h
sn34.patch
sn: Small check for invalid node in shub ioctl function
sn35.patch
sn: More code clean up - this time ioconfig_bus.c
sn36.patch
sn: Code changes for interrupt redirect
sn37.patch
sn: Forget to check in the _reg file
sn38.patch
sn: Merged 2 files into another (sgi_io_sim and irix_io_init into sgi_io_init)
sn39.patch
sn: Support for the LCD
sn40.patch
sn: Missed an include file in the last patch
sn41.patch
sn: One less panic
sn42.patch
sn: SAL interface clean up
sn43.patch
sn: Fixes for shuberror.c
sn44.patch
sn: Need a bigger max compact node value
sn45.patch
sn: Use numionodes
sn46.patch
sn: Change the definition and usage of iio_itte - make it an array
sn47.patch
sn: Debug clean up in pcibr_dvr.c
sn48.patch
sn: New pci provider interfaces
sn49.patch
sn: Fix IIO_ITTE_DISABLE() args
sn50.patch
sn: Added a missed opus mod and oom mod
sn51.patch
sn: Added cbrick_type_get_nasid() function
sn52.patch
sn: Clean up the bit twiddle macros in pcibr_config.c
sn53.patch
sn: Fixed an oom in pci_bus_cvlink.c
sn54.patch
sn: Remove the pcibr_wrap... functions
sn55.patch
sn: printk cleanup
sn56.patch
sn: pci dma cleanup
sn57.patch
sn: Make pcibr debug variables static
sn58.patch
sn: Include file clean up in pcibr_hints.c
sn59.patch
sn: Added call to pcireg_intr_status_get
sn60.patch
sn: More code clean up = mostly pcibr_slot.c
sn61.patch
sn: pcibr_rrb.c cleanup
sn62.patch
sn: Minor code clean up of pcibr_error.c
sn63.patch
sn: sn_pci_fixup() clean up or is it fix up ???
sn65.patch
sn: Remove irix_io_init - replace with sgi_master_io_infr_init
sn66.patch
sn: Don't call init_hcl from the fixup code
sn67.patch
sn: Error devenable not used - delete defs
sn68.patch
sn: Delete unused code in pcibr_slot.c
sn69.patch
sn: Delete unused pciio.c code (???_host???_[sg]et)
sn70.patch
sn: Minor clean up for ml_iograph.c
sn71.patch
sn: Simulator check in pci_bus_cvlink.c
sn73.patch
sn: Mostly printk clean up and remove some dead code
sn74.patch
sn: A little re-formatting
sn75.patch
sn: cleanups and error checking
document-efi-zero-page-usage.patch
Document EFI zero-page usage
v4l-01-videodev-update.patch
[v4l] videodev update
v4l-02-v4l2-update.patch
[v4l] v4l2 update
v4l-03-video-buf-update.patch
[v4l] video-buf update
v4l-04-bttv-driver-update.patch
[v4l] bttv driver update
v4l-05-infrared-remote-support.patch
[v4l] add infrared remote support
v4l-06-misc-i2c-fixes.patch
[v4l] misc i2c fixes
v4l-07-tuner-update.patch
[v4l] tuner update
v4l-08-bttv-IR-input-support.patch
[v4l] add bttv IR input support.
v4l-09-saa7134-update.patch
[v4l] saa7134 driver update
v4l-10-conexant-2388x-driver.patch
[v4l] add conexant 2388x driver.
request-origination-determination-fix.patch
Use request_list as indicator that req originated from ll_rw_blk
ppc-module-skip-debug-sections.patch
modules: skip debug sections
MAINTAINERS-oprofile-update.patch
update OProfile maintainer
md-01-set_disk_faulty-return-code-fix.patch
md: fix return code in set_disk_faulty()
md-02-rebuild-needs-yield.patch
md: Don't allow raid5 rebuild to swamp raid5 stripe cache
md-03-resync-interrupt-fix.patch
md: Make sure an interrupted resync doesn't seem to have completed.
md-04-typo-fix.patch
md: Fix typo in comment
md-05-recovery-fix.patch
md: Make sure md recovery happens appropriately.
md-06-do_md_run-fix.patch
md: Don't do_md_stop and array when do_md_run fails.
md-07-superblock-writing-fixes.patch
md: Small fixes for timely writing of md superblocks.
md-08-remove-disks-array.patch
md: Remove the 'disks' array from md which holds the gendisk structures.
md-09-discard-mddev_map-array.patch
md: Discard the mddev_map array.
md-10-use-bd_disk-private_data.patch
md: Use bd_disk->private data instead of bd_inode->u.generic_ip
nfsd-01-stale-filehandles-fixes.patch
kNFSd: Fix problem with stale filehandles.
nfsd-02-failed-lookup-status-fix.patch
kNFSd: Convert error status for failed lookup("..") properly.
nfsd-03-follow_up-fix.patch
kNFSd: Fix incorrect call for follow_up
nfsd-04-add-dnotify-events.patch
kNFSd: Make sure dnotify events happen for NFS read and write.
nfsd-05-SUN-NFSv2-hack.patch
kNFSd: Honour SUN NFSv2 hack for "set times to server time.
nfsd-06-SVCFH_fmt-is-extern.patch
kNFSd: Move SVCFH_fmt from being 'inline' to being 'extern'.
ghash.patch
ghash.h from 2.4
tty_io-uml-fix.patch
uml: make tty_init callable from UML functions
uml-update.patch
UML update
proc_dma_open-simplification.patch
cleanup single_open usage in dma.c
rq_for_each_bio-fix.patch
rq_for_each_bio fix
remove-afs-strdup.patch
remove spurious strdup
list_del-debug.patch
list_del debug check
print-build-options-on-oops.patch
show_task-free-stack-fix.patch
show_task() fix and cleanup
oops-dump-preceding-code.patch
i386 oops output: dump preceding code
lockmeter.patch
uninline-bitmap-functions.patch
uninline bitmap functions
sock_put-inline-fix.patch
add-noinline-attribute.patch
Add noinline attribute
use-funit-at-a-time.patch
Use -funit-at-a-time when possible
add-config-for-mregparm-3.patch
Add CONFIG for -mregparm=3
add-config-for-mregparm-3-make-EXPERIMENTAL.patch
add-module-magic-for-mregparm3.patch
Add -mregparm info to module versioning
fix-x86_64-gcc-34-warnings.patch
Fix gcc 3.4 warnings in x86-64
fix-more-gcc-34-warnings.patch
Fix more gcc 3.4 warnings
gcc-34-string-fixes.patch
string fixes for gcc 3.4
4g-2.6.0-test2-mm2-A5.patch
4G/4G split patch
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g/4g usercopy atomicity fix
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g/4g usercopy atomicity fix
4G/4G preempt on vstack
4G/4G: even number of kmap types
4g4g: fix __get_user in slab
4g4g: Remove extra .data.idt section definition
4g/4g linker error (overlapping sections)
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g4g: show_registers() fix
4g/4g usercopy atomicity fix
4g4g: debug flags fix
4g4g: Fix wrong asm-offsets entry
cyclone time fixmap fix
4G/4G preempt on vstack
4G/4G: even number of kmap types
4g4g: fix __get_user in slab
4g4g: Remove extra .data.idt section definition
4g/4g linker error (overlapping sections)
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g4g: show_registers() fix
4g/4g usercopy atomicity fix
4g4g: debug flags fix
4g4g: Fix wrong asm-offsets entry
cyclone time fixmap fix
use direct_copy_{to,from}_user for kernel access in mm/usercopy.c
4G/4G might_sleep warning fix
4g/4g pagetable accounting fix
Fix 4G/4G and WP test lockup
4G/4G KERNEL_DS usercopy again
Fix 4G/4G X11/vm86 oops
Fix 4G/4G athlon triplefault
4g4g SEP fix
Fix 4G/4G split fix for pre-pentiumII machines
4g4g-locked-userspace-copy.patch
Do a locked user-space copy for 4g/4g
4g4g-acpi-low-mappings-fix.patch
4g/4g PAE ACPI low mappings fix
ppc-fixes.patch
make mm4 compile on ppc
O_DIRECT-race-fixes-rollup.patch
DIO fixes forward port and AIO-DIO fix
O_DIRECT race fixes comments
O_DRIECT race fixes fix fix fix
DIO locking rework
O_DIRECT XFS fix
dio-aio-fixes.patch
direct-io AIO fixes
dio-aio fix fix
aio-fallback-bio_count-race-fix-2.patch
AIO+DIO bio_count race fix
aio-sysctl-parms.patch
aio sysctl parms
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 68+ messages in thread
end of thread, other threads:[~2004-02-12 16:11 UTC | newest]
Thread overview: 68+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20040115225948.6b994a48.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20040118001217.GE3125@werewolf.able.es.suse.lists.linux.kernel>
[not found] ` <20040117215535.0e4674b8.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20040118081128.GA3153@werewolf.able.es.suse.lists.linux.kernel>
[not found] ` <20040118001708.09291455.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20040119224219.65991501.rusty@rustcorp.com.au.suse.lists.linux.kernel>
2004-01-19 12:40 ` 2.6.1-mm4 Andi Kleen
2004-01-21 4:06 ` 2.6.1-mm4 Rusty Russell
2004-01-21 4:56 ` 2.6.1-mm4 Valdis.Kletnieks
2004-01-21 8:40 ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:27 ` 2.6.1-mm4 Andi Kleen
2004-01-21 12:34 ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:46 ` 2.6.1-mm4 Andi Kleen
2004-01-21 13:13 ` 2.6.1-mm4 Vojtech Pavlik
2004-01-22 1:31 ` 2.6.1-mm4 Rusty Russell
2004-01-21 12:53 ` 2.6.1-mm4 Dmitry Torokhov
2004-01-21 12:23 ` mouse configuration in 2.6.1 Andi Kleen
2004-01-21 12:31 ` Marcos D. Marado Torres
2004-01-21 12:42 ` Andi Kleen
2004-01-21 12:53 ` Marcos D. Marado Torres
2004-01-21 13:02 ` Andi Kleen
2004-01-21 13:06 ` Marcos D. Marado Torres
2004-01-21 13:09 ` Dmitry Torokhov
2004-01-21 12:32 ` Vojtech Pavlik
2004-01-22 1:14 ` Rusty Russell
2004-01-17 13:13 2.6.1-mm4 Thomas Molina
2004-01-17 18:14 ` 2.6.1-mm4 Hugh Dickins
2004-01-17 18:52 ` 2.6.1-mm4 Andrew Morton
2004-01-19 7:16 ` 2.6.1-mm4 Rusty Russell
2004-01-19 11:29 ` 2.6.1-mm4 Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 6:59 2.6.1-mm4 Andrew Morton
2004-01-16 6:59 ` 2.6.1-mm4 Andrew Morton
2004-01-16 9:34 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-16 9:34 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-21 18:46 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-21 18:46 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-21 19:20 ` 2.6.1-mm4 Valdis.Kletnieks
2004-02-11 22:22 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-02-12 5:52 ` 2.6.1-mm4 Valdis.Kletnieks
2004-02-12 7:30 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-02-12 8:46 ` 2.6.1-mm4 Valdis.Kletnieks
2004-02-12 13:15 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-02-12 16:11 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-16 13:45 ` 2.6.1-mm4 Ed Tomlinson
2004-01-16 13:45 ` 2.6.1-mm4 Ed Tomlinson
2004-01-16 17:32 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 14:49 ` 2.6.1-mm4 Fabian Fenaut
2004-01-16 14:49 ` 2.6.1-mm4 Fabian Fenaut
[not found] ` <200401161449.i0GEnoAv026627@fire-1.osdl.org>
2004-01-16 17:03 ` 2.6.1-mm4 Andrew Morton
2004-01-16 17:03 ` 2.6.1-mm4 Andrew Morton
2004-01-16 18:11 ` 2.6.1-mm4 Fabian Fenaut
2004-01-16 17:37 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 17:58 ` 2.6.1-mm4 Thomas Schlichter
2004-01-17 1:31 ` 2.6.1-mm4 Greg Fitzgerald
2004-01-17 1:40 ` 2.6.1-mm4 Mike Fedyk
2004-01-17 2:07 ` 2.6.1-mm4 Greg Fitzgerald
2004-01-17 2:24 ` 2.6.1-mm4 Mike Fedyk
2004-01-17 4:05 ` 2.6.1-mm4 Dmitry Torokhov
2004-01-17 4:22 ` 2.6.1-mm4 Greg Fitzgerald
2004-01-17 2:22 ` 2.6.1-mm4 Adrian Bunk
2004-01-17 2:22 ` 2.6.1-mm4 Adrian Bunk
2004-01-18 0:12 ` 2.6.1-mm4 J.A. Magallon
2004-01-18 5:55 ` 2.6.1-mm4 Andrew Morton
2004-01-18 8:11 ` 2.6.1-mm4 J.A. Magallon
2004-01-18 8:17 ` 2.6.1-mm4 Andrew Morton
2004-01-19 11:42 ` 2.6.1-mm4 Rusty Russell
2004-01-19 11:46 ` 2.6.1-mm4 Luiz Fernando Capitulino
2004-01-19 11:46 ` 2.6.1-mm4 Luiz Fernando Capitulino
2004-01-20 0:26 ` 2.6.1-mm4 Thomas Molina
2004-01-20 0:26 ` 2.6.1-mm4 Thomas Molina
2004-01-20 0:57 ` 2.6.1-mm4 Andrew Morton
2004-01-20 0:57 ` 2.6.1-mm4 Andrew Morton
2004-01-20 2:13 ` 2.6.1-mm4 Thomas Molina
2004-01-20 2:13 ` 2.6.1-mm4 Thomas Molina
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.