* Re: 2.6.6-mm2
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
@ 2004-05-13 10:45 ` Christoph Hellwig
2004-05-13 10:51 ` 2.6.6-mm2 Andrew Morton
2004-05-13 10:53 ` 2.6.6-mm2, usb ehci warnings/error? Prakash K. Cheemplavam
` (7 subsequent siblings)
8 siblings, 1 reply; 54+ messages in thread
From: Christoph Hellwig @ 2004-05-13 10:45 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
> +hugetlb_shm_group-sysctl-gid-0-fix.patch
>
> Don't make gid 0 special for hugetlb shm.
As Oracle has agreed on fixing their DB to use hugetlbfs could we
please stop doctoring around on this broken patch and revert it.
Except for for you I've seen no one defending it, not even the Intel
folks that submitted it..
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 10:45 ` 2.6.6-mm2 Christoph Hellwig
@ 2004-05-13 10:51 ` Andrew Morton
2004-05-13 11:12 ` 2.6.6-mm2 Christoph Hellwig
` (2 more replies)
0 siblings, 3 replies; 54+ messages in thread
From: Andrew Morton @ 2004-05-13 10:51 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: linux-kernel
Christoph Hellwig <hch@infradead.org> wrote:
>
> > +hugetlb_shm_group-sysctl-gid-0-fix.patch
> >
> > Don't make gid 0 special for hugetlb shm.
>
> As Oracle has agreed on fixing their DB to use hugetlbfs could we
> please stop doctoring around on this broken patch and revert it.
Once I'm convinced that kernel.org kernels will be able to run applications
which vendor kernels will run, sure.
We're nowhere near that, and your continual whining gets us no closer.
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 10:51 ` 2.6.6-mm2 Andrew Morton
@ 2004-05-13 11:12 ` Christoph Hellwig
2004-05-13 11:25 ` 2.6.6-mm2 Andrew Morton
2004-05-14 7:30 ` 2.6.6-mm2 Ian Kent
2004-05-13 14:15 ` 2.6.6-mm2 Adrian Bunk
2004-05-13 19:18 ` 2.6.6-mm2 Chris Wright
2 siblings, 2 replies; 54+ messages in thread
From: Christoph Hellwig @ 2004-05-13 11:12 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Thu, May 13, 2004 at 03:51:34AM -0700, Andrew Morton wrote:
> Once I'm convinced that kernel.org kernels will be able to run applications
> which vendor kernels will run, sure.
>
> We're nowhere near that, and your continual whining gets us no closer.
Sorry, but this argumentation is utter bullshit.
If $VENDORKERNEL/freebsd/sco/windows2000 runs $APP and we don't, what
does this mean? Right, exactly nothing. Follwoing that path of argumentation
we could also merge the almost 1000 patches from SuSE's tree because you
can be pretty sure some IHV or ISV relies on it.
I've talked to three persons at Oracle and neither likes it at all, in
fact en Oracle employee is working on doing quota for hugetlbfs which
fixes this properly. Merging some horrible hacks that completly change
the authorization model (for a special case, that is) in the middle of
stable series doesn't get us anywhere, except into a horrible unmaintable
mess.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 11:12 ` 2.6.6-mm2 Christoph Hellwig
@ 2004-05-13 11:25 ` Andrew Morton
2004-05-13 13:18 ` 2.6.6-mm2 Adrian Bunk
2004-05-14 7:30 ` 2.6.6-mm2 Ian Kent
1 sibling, 1 reply; 54+ messages in thread
From: Andrew Morton @ 2004-05-13 11:25 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: linux-kernel
Christoph Hellwig <hch@infradead.org> wrote:
>
> On Thu, May 13, 2004 at 03:51:34AM -0700, Andrew Morton wrote:
> > Once I'm convinced that kernel.org kernels will be able to run applications
> > which vendor kernels will run, sure.
> >
> > We're nowhere near that, and your continual whining gets us no closer.
>
> Sorry, but this argumentation is utter bullshit.
Wim explained that any application changes now won't be widely deployed for
another year. During that period the ability to run existing Oracle setups
requires that hugepage allocation be available to unprivileged
applications.
> If $VENDORKERNEL/freebsd/sco/windows2000 runs $APP and we don't, what
> does this mean? Right, exactly nothing.
It means that if people install a kernel.org machine on their database
server, the database *just won't work*. This is not good for those users,
for the kernel developers or for Linux's reputation in general.
It's worth a very small, extremely easily maintainable patch to fix all
this up.
And this is not just any old application.
> I've talked to three persons at Oracle and neither likes it at all, in
> fact en Oracle employee is working on doing quota for hugetlbfs which
> fixes this properly.
One year.
> Merging some horrible hacks that completly change
> the authorization model (for a special case, that is)
If you need to exaggerate this much to make your point, it isn't a very
good point.
> in the middle of
> stable series doesn't get us anywhere, except into a horrible unmaintable
> mess.
Here's your "horrible unmaintainable mess":
diff -puN fs/hugetlbfs/inode.c~hugetlb_shm_group-sysctl-patch fs/hugetlbfs/inode.c
--- 25/fs/hugetlbfs/inode.c~hugetlb_shm_group-sysctl-patch 2004-05-10 04:48:58.627456560 -0700
+++ 25-akpm/fs/hugetlbfs/inode.c 2004-05-10 04:48:58.640454584 -0700
@@ -43,6 +43,8 @@ static struct backing_dev_info hugetlbfs
.memory_backed = 1, /* Does not contribute to dirty memory */
};
+int sysctl_hugetlb_shm_group;
+
static int hugetlbfs_file_mmap(struct file *file, struct vm_area_struct *vma)
{
struct inode *inode = file->f_dentry->d_inode;
@@ -718,6 +720,12 @@ static unsigned long hugetlbfs_counter(v
return ret;
}
+static int can_do_hugetlb_shm(void)
+{
+ return likely(capable(CAP_IPC_LOCK) ||
+ in_group_p(sysctl_hugetlb_shm_group));
+}
+
struct file *hugetlb_zero_setup(size_t size)
{
int error;
@@ -727,7 +735,7 @@ struct file *hugetlb_zero_setup(size_t s
struct qstr quick_string;
char buf[16];
- if (!capable(CAP_IPC_LOCK))
+ if (!can_do_hugetlb_shm())
return ERR_PTR(-EPERM);
if (!is_hugepage_mem_enough(size))
diff -puN include/linux/hugetlb.h~hugetlb_shm_group-sysctl-patch include/linux/hugetlb.h
--- 25/include/linux/hugetlb.h~hugetlb_shm_group-sysctl-patch 2004-05-10 04:48:58.628456408 -0700
+++ 25-akpm/include/linux/hugetlb.h 2004-05-10 04:48:58.641454432 -0700
@@ -32,6 +32,7 @@ void free_huge_page(struct page *);
extern unsigned long max_huge_pages;
extern const unsigned long hugetlb_zero, hugetlb_infinity;
+extern int sysctl_hugetlb_shm_group;
static inline void
mark_mm_hugetlb(struct mm_struct *mm, struct vm_area_struct *vma)
diff -puN include/linux/sysctl.h~hugetlb_shm_group-sysctl-patch include/linux/sysctl.h
--- 25/include/linux/sysctl.h~hugetlb_shm_group-sysctl-patch 2004-05-10 04:48:58.630456104 -0700
+++ 25-akpm/include/linux/sysctl.h 2004-05-10 04:48:58.643454128 -0700
@@ -163,6 +163,7 @@ enum
VM_MAX_MAP_COUNT=22, /* int: Maximum number of mmaps/address-space */
VM_LAPTOP_MODE=23, /* vm laptop mode */
VM_BLOCK_DUMP=24, /* block dump mode */
+ VM_HUGETLB_GROUP=25, /* permitted hugetlb group */
};
diff -puN kernel/sysctl.c~hugetlb_shm_group-sysctl-patch kernel/sysctl.c
--- 25/kernel/sysctl.c~hugetlb_shm_group-sysctl-patch 2004-05-10 04:48:58.632455800 -0700
+++ 25-akpm/kernel/sysctl.c 2004-05-10 04:48:58.645453824 -0700
@@ -738,6 +738,14 @@ static ctl_table vm_table[] = {
.extra1 = (void *)&hugetlb_zero,
.extra2 = (void *)&hugetlb_infinity,
},
+ {
+ .ctl_name = VM_HUGETLB_GROUP,
+ .procname = "hugetlb_shm_group",
+ .data = &sysctl_hugetlb_shm_group,
+ .maxlen = sizeof(gid_t),
+ .mode = 0644,
+ .proc_handler = &proc_dointvec,
+ },
#endif
{
.ctl_name = VM_LOWER_ZONE_PROTECTION,
_
Please, spare me the hyperbole.
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 11:25 ` 2.6.6-mm2 Andrew Morton
@ 2004-05-13 13:18 ` Adrian Bunk
2004-05-13 13:39 ` 2.6.6-mm2 Chris Mason
0 siblings, 1 reply; 54+ messages in thread
From: Adrian Bunk @ 2004-05-13 13:18 UTC (permalink / raw)
To: Andrew Morton; +Cc: Christoph Hellwig, linux-kernel
On Thu, May 13, 2004 at 04:25:40AM -0700, Andrew Morton wrote:
>...
> Wim explained that any application changes now won't be widely deployed for
> another year. During that period the ability to run existing Oracle setups
> requires that hugepage allocation be available to unprivileged
> applications.
>...
> It means that if people install a kernel.org machine on their database
> server, the database *just won't work*. This is not good for those users,
> for the kernel developers or for Linux's reputation in general.
>...
That sounds silly when talking about Oracle.
Oracle says:
Which Kernels are supported?
Oracle does not support modified or recompiled kernels. Recompiled
kernels are not supported with or without source modifications.
I doubt there are many "existing Oracle setups" that will risk to lose
all Oracle support by installing a different kernel.
And AFAIK Oracle currently supports not a single distribution that ships
with kernel 2.6.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 13:18 ` 2.6.6-mm2 Adrian Bunk
@ 2004-05-13 13:39 ` Chris Mason
2004-05-13 14:09 ` 2.6.6-mm2 Adrian Bunk
0 siblings, 1 reply; 54+ messages in thread
From: Chris Mason @ 2004-05-13 13:39 UTC (permalink / raw)
To: Adrian Bunk; +Cc: Andrew Morton, Christoph Hellwig, linux-kernel
On Thu, 2004-05-13 at 09:18, Adrian Bunk wrote:
> On Thu, May 13, 2004 at 04:25:40AM -0700, Andrew Morton wrote:
> >...
> > Wim explained that any application changes now won't be widely deployed for
> > another year. During that period the ability to run existing Oracle setups
> > requires that hugepage allocation be available to unprivileged
> > applications.
> >...
> > It means that if people install a kernel.org machine on their database
> > server, the database *just won't work*. This is not good for those users,
> > for the kernel developers or for Linux's reputation in general.
> >...
>
> That sounds silly when talking about Oracle.
>
> Oracle says:
> Which Kernels are supported?
>
> Oracle does not support modified or recompiled kernels. Recompiled
> kernels are not supported with or without source modifications.
>
>
> I doubt there are many "existing Oracle setups" that will risk to lose
> all Oracle support by installing a different kernel.
>
No, I doubt so as well. Then again, why force them into a vendor
kernel? At the very least, it would be nice to be able to benchmark
vanilla against the vendors.
> And AFAIK Oracle currently supports not a single distribution that ships
> with kernel 2.6.
Keep in mind that just because oracle isn't certified on a kernel today,
that doesn't make Andrew's statements wrong.
-chris
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 13:39 ` 2.6.6-mm2 Chris Mason
@ 2004-05-13 14:09 ` Adrian Bunk
2004-05-17 20:52 ` 2.6.6-mm2 Bill Davidsen
0 siblings, 1 reply; 54+ messages in thread
From: Adrian Bunk @ 2004-05-13 14:09 UTC (permalink / raw)
To: Chris Mason; +Cc: Andrew Morton, Christoph Hellwig, linux-kernel
On Thu, May 13, 2004 at 09:39:32AM -0400, Chris Mason wrote:
> On Thu, 2004-05-13 at 09:18, Adrian Bunk wrote:
> > On Thu, May 13, 2004 at 04:25:40AM -0700, Andrew Morton wrote:
> > >...
> > > Wim explained that any application changes now won't be widely deployed for
> > > another year. During that period the ability to run existing Oracle setups
> > > requires that hugepage allocation be available to unprivileged
> > > applications.
> > >...
> > > It means that if people install a kernel.org machine on their database
> > > server, the database *just won't work*. This is not good for those users,
> > > for the kernel developers or for Linux's reputation in general.
> > >...
> >
> > That sounds silly when talking about Oracle.
> >
> > Oracle says:
> > Which Kernels are supported?
> >
> > Oracle does not support modified or recompiled kernels. Recompiled
> > kernels are not supported with or without source modifications.
> >
> >
> > I doubt there are many "existing Oracle setups" that will risk to lose
> > all Oracle support by installing a different kernel.
> >
> No, I doubt so as well. Then again, why force them into a vendor
> kernel? At the very least, it would be nice to be able to benchmark
> vanilla against the vendors.
>...
I think I recall times when code contributions to the kernel were only
judged by their quality and not by the needs of some non-free apps or
what vendors did.
Either my memory is wrong, or these times are gone now...
> -chris
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 14:09 ` 2.6.6-mm2 Adrian Bunk
@ 2004-05-17 20:52 ` Bill Davidsen
0 siblings, 0 replies; 54+ messages in thread
From: Bill Davidsen @ 2004-05-17 20:52 UTC (permalink / raw)
To: linux-kernel
Adrian Bunk wrote:
> On Thu, May 13, 2004 at 09:39:32AM -0400, Chris Mason wrote:
>
>>On Thu, 2004-05-13 at 09:18, Adrian Bunk wrote:
>>
>>>On Thu, May 13, 2004 at 04:25:40AM -0700, Andrew Morton wrote:
>>>
>>>>...
>>>>Wim explained that any application changes now won't be widely deployed for
>>>>another year. During that period the ability to run existing Oracle setups
>>>>requires that hugepage allocation be available to unprivileged
>>>>applications.
>>>>...
>>>>It means that if people install a kernel.org machine on their database
>>>>server, the database *just won't work*. This is not good for those users,
>>>>for the kernel developers or for Linux's reputation in general.
>>>>...
>>>
>>>That sounds silly when talking about Oracle.
>>>
>>>Oracle says:
>>> Which Kernels are supported?
>>>
>>> Oracle does not support modified or recompiled kernels. Recompiled
>>> kernels are not supported with or without source modifications.
>>>
>>>
>>>I doubt there are many "existing Oracle setups" that will risk to lose
>>>all Oracle support by installing a different kernel.
>>>
>>
>>No, I doubt so as well. Then again, why force them into a vendor
>>kernel? At the very least, it would be nice to be able to benchmark
>>vanilla against the vendors.
>>...
>
>
> I think I recall times when code contributions to the kernel were only
> judged by their quality and not by the needs of some non-free apps or
> what vendors did.
>
> Either my memory is wrong, or these times are gone now...
I don't see that "quality" and "what vendors did" are mutually
exclusive. What I don't see is why you think that having a capability
control this is a bad thing. It would seem to be exactly the type of
thing capabilities address, giving a selected bit of permission to a
trusted application.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 11:12 ` 2.6.6-mm2 Christoph Hellwig
2004-05-13 11:25 ` 2.6.6-mm2 Andrew Morton
@ 2004-05-14 7:30 ` Ian Kent
1 sibling, 0 replies; 54+ messages in thread
From: Ian Kent @ 2004-05-14 7:30 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Andrew Morton, linux-kernel
On Thu, 13 May 2004, Christoph Hellwig wrote:
> On Thu, May 13, 2004 at 03:51:34AM -0700, Andrew Morton wrote:
> > Once I'm convinced that kernel.org kernels will be able to run applications
> > which vendor kernels will run, sure.
> >
> > We're nowhere near that, and your continual whining gets us no closer.
>
> Sorry, but this argumentation is utter bullshit.
Excuse me for interrupting.
Surely the main concern is the place where this runs not the kernel
developer or application developer.
I know it's not a good situation, it never has been, but sites often
aren't able to upgrade to new versions of kernels or products, in anything
like short order, for all sorts of reasons.
Ian
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 10:51 ` 2.6.6-mm2 Andrew Morton
2004-05-13 11:12 ` 2.6.6-mm2 Christoph Hellwig
@ 2004-05-13 14:15 ` Adrian Bunk
2004-05-13 19:18 ` 2.6.6-mm2 Chris Wright
2 siblings, 0 replies; 54+ messages in thread
From: Adrian Bunk @ 2004-05-13 14:15 UTC (permalink / raw)
To: Andrew Morton; +Cc: Christoph Hellwig, linux-kernel
On Thu, May 13, 2004 at 03:51:34AM -0700, Andrew Morton wrote:
> Christoph Hellwig <hch@infradead.org> wrote:
> >
> > > +hugetlb_shm_group-sysctl-gid-0-fix.patch
> > >
> > > Don't make gid 0 special for hugetlb shm.
> >
> > As Oracle has agreed on fixing their DB to use hugetlbfs could we
> > please stop doctoring around on this broken patch and revert it.
>
> Once I'm convinced that kernel.org kernels will be able to run applications
> which vendor kernels will run, sure.
>...
Vendor 2.4 kernels support the "old" EVMS application.
Despite this fact, the code was rejected by Linus during 2.5.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 10:51 ` 2.6.6-mm2 Andrew Morton
2004-05-13 11:12 ` 2.6.6-mm2 Christoph Hellwig
2004-05-13 14:15 ` 2.6.6-mm2 Adrian Bunk
@ 2004-05-13 19:18 ` Chris Wright
2004-05-13 19:29 ` 2.6.6-mm2 Andrew Morton
2004-05-13 19:38 ` 2.6.6-mm2 Andrew Morton
2 siblings, 2 replies; 54+ messages in thread
From: Chris Wright @ 2004-05-13 19:18 UTC (permalink / raw)
To: Andrew Morton; +Cc: Christoph Hellwig, linux-kernel
* Andrew Morton (akpm@osdl.org) wrote:
> Christoph Hellwig <hch@infradead.org> wrote:
> >
> > > +hugetlb_shm_group-sysctl-gid-0-fix.patch
> > >
> > > Don't make gid 0 special for hugetlb shm.
> >
> > As Oracle has agreed on fixing their DB to use hugetlbfs could we
> > please stop doctoring around on this broken patch and revert it.
>
> Once I'm convinced that kernel.org kernels will be able to run applications
> which vendor kernels will run, sure.
What about something that's just simple and generic? This is similar to
Andrea's disable_cap_mlock patch and the disabling capabilities patch
that wli produced back in that thread. It would remove the hack, and
buy us some time to find better solutions. Downside of course (as all
of these have) is reduced security value.
Against -mm2, thoughts?
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
--- linux-2.6.6-mm2/security/capability.c 2004-05-13 11:19:44.000000000 -0700
+++ linux-2.6.6-mm2-cap_mask_disable/security/capability.c 2004-05-13 12:01:04.167511552 -0700
@@ -24,12 +24,24 @@
#include <linux/ptrace.h>
#include <linux/moduleparam.h>
+static int capability_mask;
+module_param_named(mask, capability_mask, int, 0);
+MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
+
+static int capability_capable(struct task_struct *task, int cap)
+{
+ if (CAP_TO_MASK(cap) & capability_mask)
+ return 0;
+ else
+ return cap_capable(task, cap);
+}
+
static struct security_operations capability_ops = {
.ptrace = cap_ptrace,
.capget = cap_capget,
.capset_check = cap_capset_check,
.capset_set = cap_capset_set,
- .capable = cap_capable,
+ .capable = capability_capable,
.netlink_send = cap_netlink_send,
.netlink_recv = cap_netlink_recv,
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 19:18 ` 2.6.6-mm2 Chris Wright
@ 2004-05-13 19:29 ` Andrew Morton
2004-05-13 19:35 ` 2.6.6-mm2 Chris Wright
2004-05-13 19:38 ` 2.6.6-mm2 Andrew Morton
1 sibling, 1 reply; 54+ messages in thread
From: Andrew Morton @ 2004-05-13 19:29 UTC (permalink / raw)
To: Chris Wright; +Cc: hch, linux-kernel, Andrea Arcangeli
Chris Wright <chrisw@osdl.org> wrote:
>
> * Andrew Morton (akpm@osdl.org) wrote:
> > Christoph Hellwig <hch@infradead.org> wrote:
> > >
> > > > +hugetlb_shm_group-sysctl-gid-0-fix.patch
> > > >
> > > > Don't make gid 0 special for hugetlb shm.
> > >
> > > As Oracle has agreed on fixing their DB to use hugetlbfs could we
> > > please stop doctoring around on this broken patch and revert it.
> >
> > Once I'm convinced that kernel.org kernels will be able to run applications
> > which vendor kernels will run, sure.
>
> What about something that's just simple and generic? This is similar to
> Andrea's disable_cap_mlock patch and the disabling capabilities patch
> that wli produced back in that thread. It would remove the hack, and
> buy us some time to find better solutions. Downside of course (as all
> of these have) is reduced security value.
-ENODOCCO.
I assume one does
modprobe capability mask=32768
and this squashes CAP_IPC_LOCK system-wide?
> Against -mm2, thoughts?
Seems feasible, thanks. It replaces /proc/sys/vm/disable-mlock.
What does Andrea think?
>
> thanks,
> -chris
> --
> Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
>
>
> --- linux-2.6.6-mm2/security/capability.c 2004-05-13 11:19:44.000000000 -0700
> +++ linux-2.6.6-mm2-cap_mask_disable/security/capability.c 2004-05-13 12:01:04.167511552 -0700
> @@ -24,12 +24,24 @@
> #include <linux/ptrace.h>
> #include <linux/moduleparam.h>
>
> +static int capability_mask;
> +module_param_named(mask, capability_mask, int, 0);
> +MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
> +
> +static int capability_capable(struct task_struct *task, int cap)
> +{
> + if (CAP_TO_MASK(cap) & capability_mask)
> + return 0;
> + else
> + return cap_capable(task, cap);
> +}
> +
> static struct security_operations capability_ops = {
> .ptrace = cap_ptrace,
> .capget = cap_capget,
> .capset_check = cap_capset_check,
> .capset_set = cap_capset_set,
> - .capable = cap_capable,
> + .capable = capability_capable,
> .netlink_send = cap_netlink_send,
> .netlink_recv = cap_netlink_recv,
>
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 19:29 ` 2.6.6-mm2 Andrew Morton
@ 2004-05-13 19:35 ` Chris Wright
0 siblings, 0 replies; 54+ messages in thread
From: Chris Wright @ 2004-05-13 19:35 UTC (permalink / raw)
To: Andrew Morton; +Cc: Chris Wright, hch, linux-kernel, Andrea Arcangeli
* Andrew Morton (akpm@osdl.org) wrote:
> Chris Wright <chrisw@osdl.org> wrote:
> > What about something that's just simple and generic? This is similar to
> > Andrea's disable_cap_mlock patch and the disabling capabilities patch
> > that wli produced back in that thread. It would remove the hack, and
> > buy us some time to find better solutions. Downside of course (as all
> > of these have) is reduced security value.
>
> -ENODOCCO.
Oops, I assumed the MODULE_PARAM_DESC was self-explanatory for a first
pass, sorry about that.
> I assume one does
>
> modprobe capability mask=32768
>
> and this squashes CAP_IPC_LOCK system-wide?
Yes, although I think you picked off the wrong bit ;-) (and I prefer hex)
modprobe capability mask=0x4000
or if CONFIG_SECURITY_MODULE=y, then boot param:
capability.mask=0x4000
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 19:18 ` 2.6.6-mm2 Chris Wright
2004-05-13 19:29 ` 2.6.6-mm2 Andrew Morton
@ 2004-05-13 19:38 ` Andrew Morton
2004-05-13 19:42 ` 2.6.6-mm2 Chris Wright
2004-05-14 19:06 ` 2.6.6-mm2 Kevin O'Connor
1 sibling, 2 replies; 54+ messages in thread
From: Andrew Morton @ 2004-05-13 19:38 UTC (permalink / raw)
To: Chris Wright; +Cc: hch, linux-kernel, Andrea Arcangeli
Chris Wright <chrisw@osdl.org> wrote:
>
>
> +static int capability_mask;
> +module_param_named(mask, capability_mask, int, 0);
> +MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
Is there a way to make this tunable at runtime, btw?
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 19:38 ` 2.6.6-mm2 Andrew Morton
@ 2004-05-13 19:42 ` Chris Wright
2004-05-14 19:14 ` 2.6.6-mm2 Andrea Arcangeli
2004-05-14 19:06 ` 2.6.6-mm2 Kevin O'Connor
1 sibling, 1 reply; 54+ messages in thread
From: Chris Wright @ 2004-05-13 19:42 UTC (permalink / raw)
To: Andrew Morton; +Cc: Chris Wright, hch, linux-kernel, Andrea Arcangeli
* Andrew Morton (akpm@osdl.org) wrote:
> Chris Wright <chrisw@osdl.org> wrote:
> >
> >
> > +static int capability_mask;
> > +module_param_named(mask, capability_mask, int, 0);
> > +MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
>
> Is there a way to make this tunable at runtime, btw?
Yeah, it'd require sysctl or similar, and further reduces the security,
unless you only allow bit clearing or something.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 19:42 ` 2.6.6-mm2 Chris Wright
@ 2004-05-14 19:14 ` Andrea Arcangeli
2004-05-14 20:58 ` 2.6.6-mm2 Chris Wright
0 siblings, 1 reply; 54+ messages in thread
From: Andrea Arcangeli @ 2004-05-14 19:14 UTC (permalink / raw)
To: Chris Wright; +Cc: Andrew Morton, hch, linux-kernel
On Thu, May 13, 2004 at 12:42:49PM -0700, Chris Wright wrote:
> * Andrew Morton (akpm@osdl.org) wrote:
> > Chris Wright <chrisw@osdl.org> wrote:
> > >
> > >
> > > +static int capability_mask;
> > > +module_param_named(mask, capability_mask, int, 0);
> > > +MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
> >
> > Is there a way to make this tunable at runtime, btw?
>
> Yeah, it'd require sysctl or similar, and further reduces the security,
> unless you only allow bit clearing or something.
the runtime switch would be more confortable, the config is:
ONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_SECURITY_CAPABILITIES_BOOTPARAM=y
CONFIG_SECURITY_ROOTPLUG=m
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
# CONFIG_SECURITY_SELINUX_MLS is not set
if the runtime switch needs sysctl then probably we can stay with
disable_cap_mlock or mlock_group (I prefer disable_cap_mlock because
having more sysctl doesn't make it more secure, if you can exploit
disable_cap_mlock you can exploit hugetlbfs_group and you can exploit
mlock_group too). It's an hack and the simplest hack is
disable_cap_mlock and it is more "featured" than the group that is only
available to one group of users at once.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-14 19:14 ` 2.6.6-mm2 Andrea Arcangeli
@ 2004-05-14 20:58 ` Chris Wright
2004-05-15 2:43 ` 2.6.6-mm2 Andrea Arcangeli
0 siblings, 1 reply; 54+ messages in thread
From: Chris Wright @ 2004-05-14 20:58 UTC (permalink / raw)
To: Andrea Arcangeli; +Cc: Chris Wright, Andrew Morton, hch, linux-kernel
* Andrea Arcangeli (andrea@suse.de) wrote:
> On Thu, May 13, 2004 at 12:42:49PM -0700, Chris Wright wrote:
> > * Andrew Morton (akpm@osdl.org) wrote:
> > > Chris Wright <chrisw@osdl.org> wrote:
> > > > +static int capability_mask;
> > > > +module_param_named(mask, capability_mask, int, 0);
> > > > +MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
> > >
> > > Is there a way to make this tunable at runtime, btw?
> >
> > Yeah, it'd require sysctl or similar, and further reduces the security,
> > unless you only allow bit clearing or something.
>
> the runtime switch would be more confortable, the config is:
>
> ONFIG_SECURITY=y
> CONFIG_SECURITY_NETWORK=y
> CONFIG_SECURITY_CAPABILITIES=y
> CONFIG_SECURITY_CAPABILITIES_BOOTPARAM=y
So you already prepare for a capability bootparam.
> CONFIG_SECURITY_ROOTPLUG=m
> CONFIG_SECURITY_SELINUX=y
> CONFIG_SECURITY_SELINUX_BOOTPARAM=y
> CONFIG_SECURITY_SELINUX_DEVELOP=y
> # CONFIG_SECURITY_SELINUX_MLS is not set
>
> if the runtime switch needs sysctl then probably we can stay with
> disable_cap_mlock or mlock_group (I prefer disable_cap_mlock because
> having more sysctl doesn't make it more secure, if you can exploit
> disable_cap_mlock you can exploit hugetlbfs_group and you can exploit
> mlock_group too). It's an hack and the simplest hack is
Well it's just basic security issue. The disable_cap_mlock has less
runtime risk because it's only exposing a single capability. The ability
to mask off capability checks as boot/module load time (not compilation
time) is more flexible, and doesn't have to touch any extra code (which
gives the feel of cleaner hack), and is runtime safe (unless you care
a lot about setting up oracle, then re-enabling the CAP_IPC_LOCK checks
to minimized risk exposure). You could give the module_param some 0644
access, but now uid == 0 or CAP_DAC_OVERRIDE could freely change the
mask during runtime. So, to my thinking, you'd want to control with
sysctl that only allows bit clearing.
> disable_cap_mlock and it is more "featured" than the group that is only
> available to one group of users at once.
Question of audience...machine running oracle, or machine with users
that want safe gpg. In fact, they probably aren't same machine, and I
bet in both cases a single group would work. Well, anyway for gpg we
only want rlimits, and this work is already done...
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-14 20:58 ` 2.6.6-mm2 Chris Wright
@ 2004-05-15 2:43 ` Andrea Arcangeli
2004-05-15 7:43 ` 2.6.6-mm2 Hugh Dickins
0 siblings, 1 reply; 54+ messages in thread
From: Andrea Arcangeli @ 2004-05-15 2:43 UTC (permalink / raw)
To: Chris Wright; +Cc: Andrew Morton, hch, linux-kernel
On Fri, May 14, 2004 at 01:58:49PM -0700, Chris Wright wrote:
> gives the feel of cleaner hack), and is runtime safe (unless you care
what makes no sense to me is the "cleaner hack" approch. Since this is a
dirty hack anyways, trying to make it cleaner seems quite pointless, we
should keep it simple and localized instead, so it can be deleted with
minimal effort. Having more than 1 hack (i.e. more than 1 sysctl) for
this as well seems pointless. Dealing with the groups as well seems
overkill and not needed.
The question is is if what you are proposing could be a long term
solution or not. If it cannot be a long term solution, then going with
a single disable_cap_mlock simplest of all hack is the best from my
point of view.
> that want safe gpg. In fact, they probably aren't same machine, and I
they can or cannot be in the same machine, but the big question is if
the gpg user is "locally" trusted too or not. But this isn't just about
gpg. I had to put remap_file_pages under mlock too, not because of the
paging, paging of nonlinear VMAs works fine, but the truncate of the
nonlinear vmas doesn't work yet correctly. This will be eventually fixed
but in the short term I had to keep it under remap_file_pages under
mlock since you can mlock memory with remap_file_pages+truncate.
So if one group uses uml and the other group uses oracle, the group
approch won't work, only disable_cap_mlock will work. I can very well
imagine uml being run as nobody.nogroup or as wwwrun.www.
> [..] Well, anyway for gpg we only want rlimits, and this work is
> already done...
correct.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 19:38 ` 2.6.6-mm2 Andrew Morton
2004-05-13 19:42 ` 2.6.6-mm2 Chris Wright
@ 2004-05-14 19:06 ` Kevin O'Connor
2004-05-14 19:36 ` 2.6.6-mm2 Chris Wright
2004-05-14 19:42 ` 2.6.6-mm2 Kevin O'Connor
1 sibling, 2 replies; 54+ messages in thread
From: Kevin O'Connor @ 2004-05-14 19:06 UTC (permalink / raw)
To: Andrew Morton; +Cc: Chris Wright, hch, linux-kernel, Andrea Arcangeli
On Thu, May 13, 2004 at 12:38:09PM -0700, Andrew Morton wrote:
> Chris Wright <chrisw@osdl.org> wrote:
> >
> >
> > +static int capability_mask;
> > +module_param_named(mask, capability_mask, int, 0);
> > +MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
>
> Is there a way to make this tunable at runtime, btw?
I thought that was what the fourth argument to module_param_named was for..
/* This is the fundamental function for registering boot/module
parameters. perm sets the visibility in driverfs: 000 means it's
not there, read bits mean it's readable, write bits mean it's
writable. */
#define __module_param_call(prefix, name, set, get, arg, perm) \
Did I miss something?
-Kevin
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-14 19:06 ` 2.6.6-mm2 Kevin O'Connor
@ 2004-05-14 19:36 ` Chris Wright
2004-05-14 19:42 ` 2.6.6-mm2 Kevin O'Connor
1 sibling, 0 replies; 54+ messages in thread
From: Chris Wright @ 2004-05-14 19:36 UTC (permalink / raw)
To: Kevin O'Connor
Cc: Andrew Morton, Chris Wright, hch, linux-kernel, Andrea Arcangeli
* Kevin O'Connor (kevin@koconnor.net) wrote:
> On Thu, May 13, 2004 at 12:38:09PM -0700, Andrew Morton wrote:
> > Chris Wright <chrisw@osdl.org> wrote:
> > >
> > >
> > > +static int capability_mask;
> > > +module_param_named(mask, capability_mask, int, 0);
> > > +MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
> >
> > Is there a way to make this tunable at runtime, btw?
>
> I thought that was what the fourth argument to module_param_named was for..
>
>
> /* This is the fundamental function for registering boot/module
> parameters. perm sets the visibility in driverfs: 000 means it's
> not there, read bits mean it's readable, write bits mean it's
> writable. */
> #define __module_param_call(prefix, name, set, get, arg, perm) \
>
> Did I miss something?
No, that's right, but I didn't think it was safe enough, because it
doesn't let you register your own function to manage how the variable is
set. For example, only clearing set bits.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-14 19:06 ` 2.6.6-mm2 Kevin O'Connor
2004-05-14 19:36 ` 2.6.6-mm2 Chris Wright
@ 2004-05-14 19:42 ` Kevin O'Connor
1 sibling, 0 replies; 54+ messages in thread
From: Kevin O'Connor @ 2004-05-14 19:42 UTC (permalink / raw)
To: Andrew Morton; +Cc: Chris Wright, hch, linux-kernel, Andrea Arcangeli
This is a reply to my own message.
On Fri, May 14, 2004 at 03:06:42PM -0400, Kevin O'Connor wrote:
> On Thu, May 13, 2004 at 12:38:09PM -0700, Andrew Morton wrote:
> > > +MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
> >
> > Is there a way to make this tunable at runtime, btw?
>
> I thought that was what the fourth argument to module_param_named was for..
[...]
> Did I miss something?
It would significantly limit the usefulness of capabilities if root could
arbitrarily clear them. I think I answered my own question.
Sorry for the traffic,
-Kevin
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2, usb ehci warnings/error?
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
2004-05-13 10:45 ` 2.6.6-mm2 Christoph Hellwig
@ 2004-05-13 10:53 ` Prakash K. Cheemplavam
2004-05-13 12:11 ` 2.6.6-mm-rc3-mm2 USB 2.0 after suspend issue Ari Pollak
2004-05-13 12:14 ` 2.6.6-mm2 Matt H.
` (6 subsequent siblings)
8 siblings, 1 reply; 54+ messages in thread
From: Prakash K. Cheemplavam @ 2004-05-13 10:53 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Please look at the end of dmesg output.
There appear lines like
usb usb2: string descriptor 0 read error: -108
bug or feature? They weren't there with 2.6.6-mm1. I have no usb2.0
stuff to actually test. My usb1 stuff seems to work though.
Prakash
My dmesg (start is gone..part of it comes from log.)
May 13 12:46:06 tachyon 00003fff3000 - 0000000040000000 (ACPI data)
May 13 12:46:06 tachyon BIOS-e820: 00000000fec00000 - 00000000fec01000
(reserved)
May 13 12:46:06 tachyon BIOS-e820: 00000000fee00000 - 00000000fee01000
(reserved)
May 13 12:46:06 tachyon BIOS-e820: 00000000ffff0000 - 0000000100000000
(reserved)
May 13 12:46:06 tachyon 127MB HIGHMEM available.
May 13 12:46:06 tachyon 896MB LOWMEM available.
May 13 12:46:06 tachyon On node 0 totalpages: 262128
May 13 12:46:06 tachyon DMA zone: 4096 pages, LIFO batch:1
May 13 12:46:06 tachyon Normal zone: 225280 pages, LIFO batch:16
May 13 12:46:06 tachyon HighMem zone: 32752 pages, LIFO batch:7
May 13 12:46:06 tachyon DMI 2.2 present.
May 13 12:46:06 tachyon ACPI: RSDP (v000 Nvidia
) @ 0x000f6ba0
May 13 12:46:06 tachyon ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD
0x00000000) @ 0x3fff3000
May 13 12:46:06 tachyon ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD
0x00000000) @ 0x3fff3040
ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff79c0
ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:8 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] global_irq_base[0x0])
IOAPIC[0]: Assigned apic_id 2
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: BIOS IRQ0 pin2 override ignored.
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Built 1 zonelists
Initializing CPU#0
Kernel command line: root=/dev/sda7 quiet elevator=cfq hdg=none
idle=halt acpi_skip_timer_override
ide_setup: hdg=none
using halt in idle threads.
CPU 0 irqstacks, hard=c0478000 soft=c0477000
PID hash table entries: 4096 (order 12: 32768 bytes)
Detected 2205.243 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Memory: 1035476k/1048512k available (2425k kernel code, 12128k reserved,
952k data, 144k init, 131008k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 4358.14 BogoMIPS
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23
not connected.
..TIMER: vector=0x31 pin1=0 pin2=-1
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2204.0682 MHz.
..... host bus clock speed is 400.0851 MHz.
NET: Registered protocol family 16
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: nForce2 C1 Halt Disconnect fixup
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [APC1] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs *17), disabled.
ACPI: PCI Interrupt Link [APC3] (IRQs *18)
ACPI: PCI Interrupt Link [APC4] (IRQs *19)
ACPI: PCI Interrupt Link [APCE] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs *23)
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
ACPI: PCI Interrupt Link [APCS] enabled at IRQ 23
00:00:01[A] -> 2-23 -> IRQ 23 level high
ACPI: PCI Interrupt Link [APCF] enabled at IRQ 22
00:00:02[A] -> 2-22 -> IRQ 22 level high
ACPI: PCI Interrupt Link [APCG] enabled at IRQ 21
00:00:02[B] -> 2-21 -> IRQ 21 level high
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 20
00:00:02[C] -> 2-20 -> IRQ 20 level high
ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
ACPI: PCI Interrupt Link [APCI] enabled at IRQ 21
ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 20
ACPI: PCI Interrupt Link [APCK] enabled at IRQ 22
ACPI: PCI Interrupt Link [APCM] enabled at IRQ 21
ACPI: PCI Interrupt Link [AP3C] enabled at IRQ 20
ACPI: PCI Interrupt Link [APCZ] enabled at IRQ 22
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
00:01:06[A] -> 2-18 -> IRQ 18 level high
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
00:01:06[B] -> 2-19 -> IRQ 19 level high
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
00:01:06[C] -> 2-16 -> IRQ 16 level high
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
00:01:06[D] -> 2-17 -> IRQ 17 level high
number of MP IRQ sources: 16.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
....... : Delivery Type: 0
....... : LTS : 0
.... register #01: 00170011
....... : max redirection entries: 0017
....... : PRQ implemented: 0
....... : IO APIC version: 0011
.... register #02: 00000000
....... : arbitration: 00
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 001 01 0 0 0 0 0 1 1 31
01 001 01 0 0 0 0 0 1 1 39
02 001 01 0 0 0 0 0 1 1 41
03 001 01 0 0 0 0 0 1 1 49
04 001 01 0 0 0 0 0 1 1 51
05 001 01 0 0 0 0 0 1 1 59
06 001 01 0 0 0 0 0 1 1 61
07 001 01 0 0 0 0 0 1 1 69
08 001 01 0 0 0 0 0 1 1 71
09 001 01 0 1 0 0 0 1 1 79
0a 001 01 0 0 0 0 0 1 1 81
0b 001 01 0 0 0 0 0 1 1 89
0c 001 01 0 0 0 0 0 1 1 91
0d 001 01 0 0 0 0 0 1 1 99
0e 001 01 0 0 0 0 0 1 1 A1
0f 001 01 0 0 0 0 0 1 1 A9
10 001 01 1 1 0 0 0 1 1 E1
11 001 01 1 1 0 0 0 1 1 E9
12 001 01 1 1 0 0 0 1 1 D1
13 001 01 1 1 0 0 0 1 1 D9
14 001 01 1 1 0 0 0 1 1 C9
15 001 01 1 1 0 0 0 1 1 C1
16 001 01 1 1 0 0 0 1 1 B9
17 001 01 1 1 0 0 0 1 1 B1
IRQ to pin mappings:
IRQ0 -> 0:0
IRQ1 -> 0:1
IRQ2 -> 0:2
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ10 -> 0:10
IRQ11 -> 0:11
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ16 -> 0:16
IRQ17 -> 0:17
IRQ18 -> 0:18
IRQ19 -> 0:19
IRQ20 -> 0:20
IRQ21 -> 0:21
IRQ22 -> 0:22
IRQ23 -> 0:23
.................................... done.
PCI: Using ACPI for IRQ routing
Machine check exception polling timer started.
IA-32 Microcode Update Driver: v1.13 <tigran@veritas.com>
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NTFS driver 2.1.10 [Flags: R/W].
udf: registering filesystem
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.4
ACPI: Power Button (FF) [PWRF]
ACPI: Fan [FAN] (on)
ACPI: Processor [CPU0] (supports C1)
ACPI: Thermal Zone [THRM] (52 C)
Real Time Clock Driver v1.12
Non-volatile memory driver v1.2
Using cfq io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.25.
PCI: Setting latency timer of device 0000:00:04.0 to 64
eth0: forcedeth.c: subsystem: 0147b:1c00 bound to 0000:00:04.0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: _NEC DV-5800A, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: NU DVDRW DDW-081, ATAPI CD/DVD-ROM drive
hdd: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdc: ATAPI 40X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
ide-floppy driver 0.99.newide
hdd: No disk in drive
hdd: 98304kB, 32/64/96 CHS, 4096 kBps, 512 sector size, 2941 rpm
libata version 1.02 loaded.
sata_sil version 0.54
ata1: SATA max UDMA/100 cmd 0xF8817080 ctl 0xF881708A bmdma 0xF8817000
irq 18
ata2: SATA max UDMA/100 cmd 0xF88170C0 ctl 0xF88170CA bmdma 0xF8817008
irq 18
ata1: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c69 86:3c01 87:4003
88:203f
ata1: dev 0 ATA, max UDMA/100, 312581808 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
Vendor: ATA Model: SAMSUNG SP1614N Rev: 1.02
Type: Direct-Access ANSI SCSI revision: 05
ata1: dev 0 max request 32MB (lba48)
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write through
sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
I2O Core - (C) Copyright 1999 Red Hat Software
I2O: Event thread created as pid 155
i2o: Checking for PCI I2O controllers...
I2O configuration manager v 0.04.
(C) Copyright 1999 Red Hat Software
i2c /dev entries driver
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x5000
i2c_adapter i2c-2: nForce2 SMBus adapter at 0x5100
Advanced Linux Sound Architecture Driver Version 1.0.4 (Tue Mar 30
08:19:30 2004 UTC).
PCI: Setting latency timer of device 0000:00:06.0 to 64
intel8x0_measure_ac97_clock: measured 49394 usecs
intel8x0: clocking to 47419
ALSA device list:
#0: NVidia nForce2 at 0xcc081000, irq 20
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S0 S3 S4 S5)
ReiserFS: sda7: found reiserfs format "3.6" with standard journal
ReiserFS: sda7: using ordered data mode
ReiserFS: sda7: journal params: device sda7, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: sda7: checking transaction log (sda7)
ReiserFS: sda7: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 144k freed
NTFS volume version 3.1.
NTFS-fs error (device sda2): ntfs_check_logfile(): The two restart pages
in $LogFile do not match.
NTFS-fs warning (device sda2): load_system_files(): Failed to load
$LogFile. Will not be able to remount read-write. Mount in Windows.
NTFS volume version 3.1.
NTFS-fs error (device sda6): ntfs_check_logfile(): The two restart pages
in $LogFile do not match.
NTFS-fs warning (device sda6): load_system_files(): Failed to load
$LogFile. Will not be able to remount read-write. Mount in Windows.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ohci_hcd 0000:00:02.0: nVidia Corporation nForce2 USB Controller
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: irq 22, pci mem f88fc000
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
ohci_hcd 0000:00:02.1: nVidia Corporation nForce2 USB Controller (#2)
PCI: Setting latency timer of device 0000:00:02.1 to 64
ohci_hcd 0000:00:02.1: irq 21, pci mem f88fe000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ehci_hcd 0000:00:02.2: nVidia Corporation nForce2 USB Controller
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: irq 20, pci mem f8909000
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 6 ports detected
hub 1-0:1.0: hub_port_status failed (err = -108)
hub 1-0:1.0: connect-debounce failed, port 1 disabled
hub 1-0:1.0: cannot disable port 1 (err = -108)
hub 1-0:1.0: hub_port_status failed (err = -108)
hub 1-0:1.0: hub_port_status failed (err = -108)
hub 1-0:1.0: hub_hub_status failed (err = -108)
hub 1-0:1.0: get_hub_status failed
ohci_hcd 0000:00:02.0: remote wakeup
usb 1-1: new full speed USB device using address 2
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0
alt 1 proto 2 vid 0x03F0 pid 0x1004
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb usb2: string descriptor 0 read error: -108
usb 1-2: new full speed USB device using address 3
usb 1-2: USB disconnect, address 3
^ permalink raw reply [flat|nested] 54+ messages in thread* 2.6.6-mm-rc3-mm2 USB 2.0 after suspend issue
2004-05-13 10:53 ` 2.6.6-mm2, usb ehci warnings/error? Prakash K. Cheemplavam
@ 2004-05-13 12:11 ` Ari Pollak
0 siblings, 0 replies; 54+ messages in thread
From: Ari Pollak @ 2004-05-13 12:11 UTC (permalink / raw)
To: linux-kernel
That reminds me, I seem to be having problems with EHCI in 2.6.6-rc3-mm2
after a resume. With this: "0000:00:1d.7 USB Controller: Intel Corp.
82801DB (ICH4) USB2 EHCI Controller (rev 01)" if I suspend & resume with
APM, then plug in a USB 2.0 device, it won't work at all until I "rmmod
ehci_hcd; modprobe ehci_hcd". I'd imagine it has something to do with
these messages:
uhci_hcd 0000:00:1d.1: suspend_hc
ehci_hcd 0000:00:1d.7: suspend D0 --> D3
ehci_hcd 0000:00:1d.7: No PM capability
uhci_hcd 0000:00:1d.2: suspend D4 --> D3
uhci_hcd 0000:00:1d.2: suspend_hc
uhci_hcd 0000:00:1d.1: suspend D4 --> D3
uhci_hcd 0000:00:1d.1: suspend_hc
uhci_hcd 0000:00:1d.0: suspend D4 --> D3
uhci_hcd 0000:00:1d.0: suspend_hc
uhci_hcd 0000:00:1d.0: resume from state D4
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.1: resume from state D4
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.2: resume from state D4
PCI: Setting latency timer of device 0000:00:1d.2 to 64
ehci_hcd 0000:00:1d.7: resume from state D0
ehci_hcd 0000:00:1d.7: can't resume, not suspended!
Granted, this isn't a huge problem because I can easily work around it
by reloading the ehci_hcd module. But it's still a little annoying. It
doesn't look like this has changed as of 2.6.6-mm2 either.
Prakash K. Cheemplavam wrote:
> Please look at the end of dmesg output.
>
> There appear lines like
>
> usb usb2: string descriptor 0 read error: -108
>
> bug or feature? They weren't there with 2.6.6-mm1. I have no usb2.0
> stuff to actually test. My usb1 stuff seems to work though.
>
> Prakash
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
2004-05-13 10:45 ` 2.6.6-mm2 Christoph Hellwig
2004-05-13 10:53 ` 2.6.6-mm2, usb ehci warnings/error? Prakash K. Cheemplavam
@ 2004-05-13 12:14 ` Matt H.
2004-05-13 18:24 ` 2.6.6-mm2 Andrew Morton
2004-05-13 12:54 ` i810 AGP fails to initialise (was Re: 2.6.6-mm2) Sean Neakums
` (5 subsequent siblings)
8 siblings, 1 reply; 54+ messages in thread
From: Matt H. @ 2004-05-13 12:14 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Just attempted to compile 2.6.6-mm2 and got this error
CC [M] drivers/usb/core/driverfs.o
CC [M] drivers/usb/core/hcd-pci.o
LD [M] drivers/usb/core/usbcore.o
LD drivers/usb/host/built-in.o
CC [M] drivers/usb/host/ehci-hcd.o
CC [M] drivers/usb/host/ohci-hcd.o
In file included from drivers/usb/host/ohci-hcd.c:129:
drivers/usb/host/ohci-hub.c: In function `ohci_rh_resume':
drivers/usb/host/ohci-hub.c:313: error: `hcd' undeclared (first use in this
function)
drivers/usb/host/ohci-hub.c:313: error: (Each undeclared identifier is
reported only once
drivers/usb/host/ohci-hub.c:313: error: for each function it appears in.)
drivers/usb/host/ohci-hub.c:313: warning: unused variable `ohci'
make[3]: *** [drivers/usb/host/ohci-hcd.o] Error 1
make[2]: *** [drivers/usb/host] Error 2
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2
Matt H.
On Thursday 13 May 2004 3:27 am, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6-m
>m2/
>
>
> - Lots of VM changes - fixes from Andrea and generally moving things closer
> to the -aa tree.
>
> - The x86_64 gcc-3.3.3 shipped with SuSE 9.1 miscompiles the post-2.6.6 CPU
> scheduler changes, resulting in lockups after several minutes of heavy
> load. Hence this kernel refuses to build on gcc-3.3.x. Please use
> gcc-3.4.0 if you're on x86_64.
>
> - Rediscovered and hopefully fixed the page double-freeing bug which was
> identified in August 2002 (!). I decided it wasn't real, but it is.
>
> - arch updates, rlimits for rt-signals and posix message queues, tons of
> other stuff.
>
>
>
> Changes since 2.6.6-mm1:
>
>
> linus.patch
> bk-acpi.patch
> bk-agpgart.patch
> bk-alsa.patch
> bk-cifs.patch
> bk-cpufreq.patch
> bk-driver-core.patch
> bk-i2c.patch
> bk-input.patch
> bk-netdev.patch
> bk-ntfs.patch
> bk-net-drivers.patch
> bk-pci.patch
> bk-pcmcia.patch
> bk-scsi.patch
> bk-serial.patch
> bk-usb.patch
>
> External trees. (bk-pci is currently in disgrace due to BK conflicts.
> This is an old version).
>
> -fix-deadlock-in-journalled-quota.patch
> -mips-update.patch
> -mips-fix-mips-26-fb-setup.patch
> -mips-simplify-expression.patch
> -mips-newport-driver-fixes.patch
> -mips-remove-video_type_sni_rm.patch
> -mips-gbe-video-driver.patch
> -mips-add-missing-ip22-zilog-bit.patch
> -mips-64-bit-mips-needs-compat-stuff.patch
> -mips-remove-dz-driver.patch
> -mips-sgiwd93-26-fixes-and-crapectomy.patch
> -ppc64-extra-barrier-in-i-o-operations.patch
> -sched-run_list-cleanup.patch
> -sched-find_busiest_node-resolution-fix.patch
> -sched-domains.patch
> -sched-domain-debugging.patch
> -sched-domain-balancing-improvements.patch
> -sched-sibling-map-to-cpumask.patch
> -sched-domains-i386-ht.patch
> -sched-no-drop-balance.patch
> -sched-directed-migration.patch
> -sched-group-power.patch
> -sched-domains-use-cpu_possible_map.patch
> -sched-smt-nice-handling.patch
> -sched-local-load.patch
> -sched-process-migration-speedup.patch
> -sched-trivial.patch
> -sched-hotplug-cpu-sched_balance_exec-fix.patch
> -sched-wakebalance-fixes.patch
> -sched-imbalance-fix.patch
> -sched-altix-tune1.patch
> -sched-fix-activelb.patch
> -sched-ppc64-sched-domain-support.patch
> -sched-ppc64-sched-domain-support-fix.patch
> -sched-domain-setup-lock.patch
> -sched-minor-cleanups.patch
> -sched-inline-removals.patch
> -sched-enqueue_task_head.patch
> -sched-more-sync-wakeups.patch
> -sched-boot-fix.patch
> -sched-cleanups.patch
> -sched-damp-passive-balance.patch
> -sched-cpu-load-cleanup.patch
> -sched-balance-context.patch
> -sched-less-idle.patch
> -sched-wake_up-speedup.patch
> -sched-smt-domain-race.patch
> -sched-move-migrate_all_tasks-to-cpu_dead-handling.patch
> -sched-sys_sched_getaffinity_lock_cpu_hotplug.patch
> -sched-kthread_stop_race_fix.patch
> -x86_64-convert-sibling-map-to-masks.patch
> -sched-x86_64-sched-domains-support.patch
> -fixes-in-32-bit-ioctl-emulation-code.patch
> -nmi_watchdog-local-apic-fix.patch
> -nmi-1-hz-2.patch
> -ext3-bogus-enospc-fix.patch
> -sched-in_sched_functions.patch
> -sysfs-d_fsdata-race-fix-2.patch
> -ext3-error-handling-fixes.patch
> -re-open-descriptors-closed-on-exec-by-selinux-to.patch
> -cyclades-maintainers-update.patch
> -laptop-mode-mutt-noatime-doc-update.patch
> -as-increase-batch-expiry.patch
> -consolidate-sys32_readv-and-sys32_writev.patch
> -consolidate-do_execve32.patch
> -consolidate-sys32_select.patch
> -consolidate-sys32_nfsservctl.patch
> -ppc64-uninline-__pte_free_tlb.patch
> -es7000-subarch-update-2.patch
> -kernel_ppc8xx_misc.patch
> -remove-bootsect_helper-and-a-comment-fix-iii.patch
> -remove-bootsect_helper-on-x86_64-and-pc98.patch
> -remove-some-unused-variables-in-s2io.patch
> -new-version-of-early-cpu-detect.patch
> -shrink_slab-handle-GFP_NOFS.patch
> -shrink_slab-handle-GFP_NOFS-fix.patch
> -fix-3c59xc-to-allow-3c905c-100bt-fd.patch
> -use-dos_extended_partition.patch
> -reiserfs-commit-default-fix.patch
> -reiserfs-acl-mknod.patch
> -reiserfs-xattrs-04.patch
> -reiserfs-acl-02.patch
> -reiserfs-trusted-02.patch
> -reiserfs-selinux-02.patch
> -reiserfs-xattr-locking-02.patch
> -reiserfs-quota.patch
> -reiserfs-permission.patch
> -reiserfs-warning.patch
> -mptfusion-depends-on-scsi.patch
> -radeon-fb-screen-corruption-fix.patch
> -8139too-suspend-fix.patch
> -find_user-locking.patch
> -improve-laptop-modes-block_dump-output.patch
> -com90xx_message.patch
> -parport_doc_arg.patch
> -kernel-api-docs.patch
> -allow-architectures-to-reenable-interrupts-on-contended-spinlocks.patch
> -un-inline-spinlocks-on-ppc64.patch
> -only-print-tainted-message-once.patch
> -blk_start_queue-use-kblockd.patch
> -edd-follow-sysfs-convention-module_version-remove-dead-scsi-symlink.patch
> -cmpci-update.patch
> -dentry-and-inode-cache-hash-algorithm-performance-changes.patch
> -fix-mtd-suspend-resume.patch
> -remove-blk_queue_bounce-messages.patch
> -fix-deadlock-in-__create_workqueue-2.patch
> -throttle-p4-thermal-warnings.patch
> -i82365c-warning-fix.patch
> -worker_thread-race-fix.patch
> -kernel-syscalls-retval-fix.patch
> -remove-errno-refs.patch
> -warn-when-smp_call_function-is-called-with-interrupts-disabled.patch
> -initio-ini-9x00u-uw-error-handling-in-26.patch
> -fixup-68360-module-refcounting.patch
> -intermezzo-stack-reduction.patch
> -lance-racal-interlan-fix.patch
> -gcc-340-fixes-for-266-rc3-x86_64-kernel.patch
> -ppc64-use-generic-ipc-syscall-translation.patch
> -ramdisk-size-warning-fix.patch
> -cyclades-cleanups.patch
> -jiffies-to-clockt-fix_a1.patch
> -readahead-private.patch
> -introduce-asm--8253pith.patch
> -use-pit_tick_rate-in-spkrc.patch
> -use-clock_tick_rate.patch
> -265-es7000-subarch-update-for-generic-arch.patch
> -new-i2c-video-decoder-calls.patch
> -new-i2c-video-decoder-calls-saa7111.patch
> -get_thread_area-macros.patch
> -update-documentation-mdtxt.patch
> -bfs-filesystem-read-past-the-end-of-dir.patch
> -simplify-mqueue_inode_info-messages-allocation.patch
> -swsusp-documentation-updates.patch
> -cache-queue_congestion_on-off_threshold.patch
> -report-size-of-printk-buffer-selinux-interface.patch
> -fix-race-on-tty-close.patch
> -force-ide-cache-flush-on-shutdown-flush.patch
> -force-ide-cache-flush-on-shutdown-flush-fix.patch
> -as-iosched-cleanups.patch
> -pcmcia-tcicc-warning-fix.patch
> -lindent-on-arch-i386-kernel-cpuidc.patch
> -fix-media-dsbr100c-unused-variable.patch
> -fix-warning-in-intermezzo-journalc.patch
> -fix-wrong-var-used-in-hotplug-shpchp_ctrlc.patch
> -hugepage-add_to_page_cache-fix.patch
> -hugetlb_shm_group-sysctl-patch.patch
> -cpqarray-update-for-26.patch
> -i8042-shutdown-fix.patch
> -kill-useless-mod_incdec_use_count-in-sound-oss-msndc.patch
> -kill-mod_incdec_use_count-gunk-in-arch-cris-arch-v10-drivers-pcf8563c.patc
>h -fix-mod_incdec_use_count-gunk-in-arch-um-drivers-net_kernc.patch
> -drivers-video-mod_inc_use_count-fixes.patch
> -fix-mod_inc_use_count-usage-in-mtd.patch
> -remove-mod_inc_use_count-usage-in-arch-um-drivers-harddog_kernc.patch
> -minor-rcu-optimization.patch
> -binfmt-use-core_initcall.patch
> -usermodehelper_init-use-core_initcall.patch
> -export-con_set_default_unimap.patch
> -crystal-cs4235-mixer-fix.patch
> -remove-kernel-22-code-from-drivers-net-hamradio-dmasccc-fwd.patch
> -telephony-ixjh-remove-kernel-22-ifdefs-fwd.patch
> -fix-some-typos-in-sound-docs.patch
> -make-tags-for-selinux.patch
> -remove-intermezzo.patch
> -ppc-termio-fix.patch
> -fix-__down-tainting-kernel-with-config_modversions=y.patch
>
> Merged
>
> +page_count-fixups.patch
>
> Remove all(?) open-coded references to page->count.
>
> +page-freeing-race-fix.patch
>
> Fix race between page_cache_release() and vmscan.c functions. Hopefully
> fixes the page double-free in bug 1403.
>
> +arch-atomic_add_negative.patch
>
> Implement atomic_add_negative() on lots of architectures. (needed by the
> above)
>
> +arch-atomic_inc_and_test.patch
>
> Implement atomic_inc_and_test() on lots of architectures. (needed by the
> above)
>
> +x86_64-doesnt-like-gcc-333.patch
>
> Some flavours of gcc-3.3.3 compile x86_64 kernels incorrectly.
>
> +yield_irq.patch
>
> Small bug in sched_yield()
>
> +MSEC_TO_JIFFIES-fixups.patch
> +msec_to_jiffies-fixups-speedup.patch
>
> MSECS_TO_JIFFIES fixes
>
> +revert-process-migration-speedup.patch
>
> Revert small ia64-only CPU scheduler patch.
>
> +vm-accounting-fix.patch
>
> Fix VMA merging
>
> +system-state-splitup.patch
>
> Make system_state more meaningful. So IDE flushing doesn't spin the disk
> down across reboots. (This enables the IDE change - this kernel does not
> actually implement the IDE change).
>
> +kexec-reserve-syscall-slot.patch
>
> Reserve a syscall slot for kexec.
>
> +do_mounts_rd-malloc-fix.patch
>
> Fix a warning.
>
> +acpi-procfs-fix.patch
>
> Fix ACPI procfs handling
>
> +writeback_inodes-fix.patch
>
> Fix race in writeback.
>
> +rename-rmap_lock.patch
>
> Rename rmap_lock() to page_map_lock().
>
> +rmap-5-swap_unplug-page-revert.patch
>
> Revert pre-2.6.6 swap unplugging changes.
>
> +blk_run_page.patch
> +blk_run_page-swap-fixup.patch
> +blk_run_page-sync_buffer-revert.patch
>
> Generalise the per-address-space blockdev unplugging code.
>
> +rmap-7-object-based-rmap-sync_page-fix.patch
>
> Fix rmap-7-object-based-rmap.patch for the above.
>
> +swap-speedups-and-fix.patch
>
> Simplify, speedup and fix the swapdev unplugging code.
>
> +try_to_unmap_cluster-comment.patch
>
> Add a comment
>
> -i_shared_lock.patch
> +i_mmap_lock.patch
>
> Rename i_shared_lock to i_mmap_lock
>
> +unmap_mapping_range-comment.patch
>
> Add another comment.
>
> +rmap-19-arch-prio_tree-parisc.patch
> +rmap-20-i_mmap_shared-into-i_mmap-parisc.patch
> +rmap-22-flush_dcache_mmap_lock-parisc.patch
>
> Recent parisc changes broke Hugh's patches. He fixed them up.
>
> +rmap-33-install_arg_page-vma.patch
>
> anon_vma preparation work.
>
> +ppc64-uninline-__pte_free_tlb.patch
> +export-clear_pages-on-ppc32.patch
> +ppc32-fix-__flush_dcache_icache_phys-for-book-e.patch
> +ppc32-fix-copy-prefetch-on-non-coherent-ppcs.patch
> +ppc32-add-book-e--ppc44x-specific-exception-support.patch
> +ppc32-add-book-e--ppc44x-specific-exception-support-2.patch
> +ppc32-new-ocp-core-support-updated.patch
> +ppc32-bubinga-405ep-for-new-ocp.patch
> +ppc32-ppc44x-lib-support.patch
> +ppc32-ibm-ppc4xx-specific-ocp-support.patch
> +ppc32-4xx-core-fixes-and-440gx-pic-support.patch
> +ppc32-update-4xx-defconfigs.patch
> +ppc32-ppc40x-ports-for-new-ocp.patch
> +ppc32-ppc44x-ports-for-new-ocp.patch
>
> PPCxx stuff
>
> -CONFIG_STANDALONE-default-to-n.patch
>
> Dropped, seems unneeded.
>
> -Move-saved_command_line-to-init-mainc.patch
> -Move-saved_command_line-to-init-mainc-warnings.patch
>
> Dropped, was causing x86_64 grief.
>
> +sched-loadup-roundup.patch
> +sched-activate-tslt.patch
>
> CPU scheduler work.
>
> -nfs-O_DIRECT-fixes.patch
>
> Dropped - was not up to date.
>
> +autofs4-compat-ioctls.patch
>
> Missing autofs4 compat ioctls.
>
> -psmouse-fix-mouse-hotplugging.patch
>
> Dropped, it broke things.
>
> +i2o-64-bit-fixes.patch
>
> Fix the i2o patches for 64-bit.
>
> +invalid-notify_changesymlink-in-nfsd-fix.patch
>
> NFSD fix
>
> +sysfs-backing-store-sysfs_rename_dir-fix.patch
>
> Fix oops in the sysfs-backing-store patches
>
> +hugetlb_shm_group-sysctl-gid-0-fix.patch
>
> Don't make gid 0 special for hugetlb shm.
>
> -idr-overflow-fixes-fix.patch
> -idr-overflow-fixes-2.patch
>
> Folded into idr-overflow-fixes.patch
>
> +idr-remove-counter.patch
>
> Remove that funny 8-bit counter from the MSB's of idr_get_new()'s return
> value.
>
> -timers-signals-rlimits.patch
> -timers-signals-rlimits-setuid-fix.patch
> -timers-signals-rlimits-fix.patch
> -timers-signals-rlimits-rename-stuff.patch
> +rlim-add-rlimit-entry-for-controlling-queued-signals.patch
> +rlim-add-sigpending-field-to-user_struct.patch
> +rlim-pass-task_struct-in-send_signal.patch
> +rlim-add-simple-get_uid-helper.patch
> +rlim-enforce-rlimits-on-queued-signals.patch
> +rlim-remove-unused-queued_signals-global-accounting.patch
> +rlim-add-rlimit-entry-for-posix-mqueue-allocation.patch
> +rlim-add-mq_bytes-to-user_struct.patch
> +rlim-add-mq_attr_ok-helper.patch
> +rlim-enforce-rlimits-for-posix-mqueue-allocation.patch
> +rlim-adjust-default-mqueue-sizes.patch
>
> Reworked rlimits for signals and posix message queues.
>
> +slabify-iocontext-request_queue.patch
> +slabify-iocontext-request_queue-SLAB_PANIC.patch
>
> Add some slab caches for the block layer
>
> +show-last-kernel-image-symbol-in-proc-kallsyms.patch
>
> Fix /proc/kallsyms output
>
> +raid-locking-fix.patch
>
> Fix illegal sleep in RAID
>
> +include-aliases-in-kallsyms.patch
>
> Enhance kallsyms
>
> +make-buildcheck.patch
> +make-buildcheck-license-fix.patch
>
> Add reference_discarded.pl to the build system.
>
> +efivars-fix.patch
>
> Fix oops with efivars enabled but not avaialble.
>
> +serial-fifo-size-is-ignored.patch
>
> Serial driver fix
>
> +expose-backing-dev-max-read-ahead.patch
>
> Expose the per-disk readahead tunable in /sys/block/hda/queue
>
> +ib700wdt-fix.patch
> +ib700wdt-fix-2.patch
>
> Watchdog driver fixes
>
> +laptop-doc-bugfix.patch
>
> Documentation fix
>
> +create_workqueue-locking-bogon.patch
>
> workqueue locking fixlet
>
> +problem-with-aladdincard-entry-in-parport_pc.patch
>
> parport fix
>
> +seeky-readahead-speedups.patch
>
> readahead speedups (I hope - haven't benched it)
>
> +watchdog-timer-for-intel-ixp4xx-cpus.patch
>
> New watchdog driver
>
> +i810_audio-fixes-from-herbert-xu.patch
>
> Audio driver fixes
>
> +ide-diskc-revert-to-previous-24-way-of-handling-flush-cache-commands.patch
>
> More IDE disk flushing fun
>
> +update-laptop-mode-control-script-with-xfs_hz=100.patch
>
> Documentation fix
>
> +del_singleshot_timer_sync.patch
> +del_singleshot_timer_sync-tweaks.patch
>
> Faster version of del_timer_sync()
>
> +really-ptrace-single-step-2.patch
>
> Fix ptracing across int $80.
>
> +dquot_release-oops-workaround.patch
>
> Hopefully hackily fix the dquot oops, until Jan fixes it for real
>
> +h8-300-update-1-9-bitopsh-add-find_next_bit.patch
> +h8-300-update-2-9-ldscripts-fix.patch
> +h8-300-update-3-9-pic-support.patch
> +h8-300-update-4-9-preempt-support.patch
> +h8-300-update-5-9-sci-driver-fix.patch
> +h8-300-update-6-9-ne-driver.patch
> +h8-300-update-7-9-kconfig.patch
> +h8-300-update-8-9-delete-headers.patch
> +h8-300-update-9-9-more-cleanup.patch
>
> H8/300 updates
>
> +calculate-ngroups_per_block-from-page_size.patch
>
> Fix nasty ia64-affecting NGROUPS_MAX bug
>
> +pci-debug-compile-fix-in-sis_router_probe.patch
>
> Compile fix
>
> +remove-empty-build-of-capabilityo.patch
>
> Don't compile an empty file.
>
> +minor-cleanups-in-capabilityc.patch
>
> capability.c tidy up
>
> +add-disable-param-to-capabilities-module.patch
>
> Add a "disable=1" option to the capabilities module.
>
> +fix-linux-doc-errors.patch
>
> Fix kerneldoc generation
>
> +fix-block-layer-ioctl-bug.patch
>
> Handle strange blockdev ioctl return values.
>
> +fix-crash-on-modprobe-ohci1394.patch
>
> Fix a firewire problem
>
> +x86_64-has-buggy-ffs-implementation.patch
>
> Fix x86_64 ffs() implementation
>
> +make-reiserfs-not-to-crash-on-oom.patch
>
> reiserfs error path handling fix
>
> +implement-print_modules.patch
>
> Provide an implementation of print_modules()
>
> +m68k-print_modules.patch
>
> Use it in m68k
>
> +fix-endianess-in-modpost-when-cross-compiling-for-sparc-on-i386.patch
>
> Fix cross-compilation
>
> +fix-cyclades-compile-with-pci.patch
> +fix-tlanc-for-pci.patch
> +fix-aic7xxx_oldc-for-pci.patch
>
> CONFIG_PCI=n build fixes
>
> +powernow-k8-buggy-bios-override-for-266.patch
>
> Work around a BIOS bug
>
> +x86_64-msr-warning-fix.patch
>
> Fix a compile warning
>
> +abs-cleanup.patch
>
> Fix problems with abs(). (I'll probably drop this, in favour of simply
> nuking abs() althogether).
>
>
>
>
>
>
>
> All 334 patches:
>
>
> linus.patch
>
> page_count-fixups.patch
> Make users of page->count use the provided macros
>
> page-freeing-race-fix.patch
> Fix page double-freeing race
>
> arch-atomic_add_negative.patch
> Implement atomic_add_negative() on various architectures
>
> arch-atomic_inc_and_test.patch
> Implement atomic_inc_and_test() on various architectures
>
> x86_64-doesnt-like-gcc-333.patch
> x86_64 doesn't like gcc-3.3.3
>
> yield_irq.patch
> sched: add missing local_irq_enable()
>
> MSEC_TO_JIFFIES-fixups.patch
> MSEC_TO_JIFFIES consolidation
>
> msec_to_jiffies-fixups-speedup.patch
> MSEC_TO_JIFFIES speedup
>
> revert-process-migration-speedup.patch
> revert the process-migration-speedup patch
>
> vm-accounting-fix.patch
> VM accounting fix
>
> system-state-splitup.patch
> system_state splitup
>
> kexec-reserve-syscall-slot.patch
> reserve a syscall slot for kexec
>
> do_mounts_rd-malloc-fix.patch
> do_mounts_rd-malloc-fix
>
> bk-acpi.patch
>
> bk-agpgart.patch
>
> bk-alsa.patch
>
> bk-cifs.patch
>
> bk-cpufreq.patch
>
> bk-driver-core.patch
>
> bk-i2c.patch
>
> bk-input.patch
>
> bk-netdev.patch
>
> bk-ntfs.patch
>
> bk-net-drivers.patch
>
> bk-pci.patch
>
> bk-pcmcia.patch
>
> bk-scsi.patch
>
> bk-serial.patch
>
> bk-usb.patch
>
> mm.patch
> add -mmN to EXTRAVERSION
>
> frame-pointer-based-stack-dumps.patch
> x86: stack dumps using frame pointers
>
> fealnx-bogon-fix.patch
> fealnx.c spinlock fix
>
> bk-driver-core-module-fix.patch
> bk-driver-core-module-fix
>
> acpi-procfs-fix.patch
> acpi procfs fix
>
> writeback_inodes-fix.patch
> Fix writeback_inodes-vs-umount race
>
> 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
> correct kgdb.txt Documentation link (against 2.6.1-rc1-mm2)
> kgdb: fix for recent gcc
> kgdb warning fixes
> THREAD_SIZE fixes for kgdb
>
> kgdb-in-sched_functions.patch
>
> kgdboe-netpoll.patch
> kgdb-over-ethernet via netpoll
> kgdboe: fix configuration of MAC address
>
> kgdb-x86_64-support.patch
> kgdb-x86_64-support.patch for 2.6.2-rc1-mm3
> kgdb-x86_64-warning-fixes
>
> kgdb-in-sched_functions-x86_64.patch
>
> wakefunc.patch
> filtered wakeups
>
> wakeup.patch
> filtered wakeups: wakeup enhancements
>
> filtered_page.patch
> filtered wakeups: apply to pagecache functions
>
> filtered_buffer.patch
> filtered wakeups: apply to buffer_head functions
>
> rename-rmap_lock.patch
> rename rmap_lock to page_map_lock
>
> rmap-5-swap_unplug-page-revert.patch
> rmap-5-swap_unplug-page-revert
>
> blk_run_page.patch
> Add blk_run_page()
>
> blk_run_page-swap-fixup.patch
> blk_run_page-swap-fixup
>
> blk_run_page-sync_buffer-revert.patch
> blk_run_page-sync_buffer-revert
>
> rmap-7-object-based-rmap.patch
> rmap 7 object-based rmap
>
> rmap-7-object-based-rmap-sync_page-fix.patch
> rmap-7-object-based-rmap-sync_page-fix
>
> swap-speedups-and-fix.patch
> swap speedups and fix
>
> ia64-rmap-build-fix.patch
> ia64 rmap build fix
>
> rmap-8-unmap-nonlinear.patch
> rmap 8 unmap nonlinear
>
> try_to_unmap_cluster-comment.patch
> try_to_unmap_cluster-comment
>
> slab-panic.patch
> slab: consolidate panic code
>
> rmap-9-remove-pte_chains.patch
> rmap 9 remove pte_chains
>
> rmap-9-page_add_anon_rmap-bug-fix.patch
> page_add_anon_rmap BUG fix
>
> rmap-10-add-anonmm-rmap.patch
> rmap 10 add anonmm rmap
>
> rmap-anonhd-locking-fix.patch
> rmap anonhd locking fix
>
> rmap-11-mremap-moves.patch
> rmap 11 mremap moves
>
> rmap-12-pgtable-remove-rmap.patch
> rmap 12 pgtable remove rmap
>
> rmap-13-include-asm-deletions.patch
> rmap 13 include/asm deletions
>
> i_mmap_lock.patch
> Convert i_shared_sem back to a spinlock
> i_mmap_lock fix 1
> i_mmap_lock fix 2
> i_mmap_lock mremap fix
>
> rmap-14-i_shared_lock-fixes.patch
> rmap 14: i_shared_lock fixes
>
> numa-api-x86_64.patch
> numa api: -64 support
> numa api: Bitmap bugfix
>
> numa-api-i386.patch
> numa api: Add i386 support
>
> numa-api-ia64.patch
> numa api: Add IA64 support
>
> numa-api-core.patch
> numa api: Core NUMA API code
> numa api: docs and policy_vma() locking fix
> numa-api-core-tweaks
> Some fixes for NUMA API
> From: Matthew Dobson <colpatch@us.ibm.com>
> Subject: [PATCH] include/linux/gfp.h cleanup for NUMA API
> numa-api-core bitmap_clear fixes
>
> mpol-in-copy_vma.patch
> mpol in copy_vma
>
> numa-api-core-slab-panic.patch
> numa-api-core-slab-panic
>
> numa-api-statistics-2.patch
> Re-add NUMA API statistics
>
> numa-api-vma-policy-hooks.patch
> numa api: Add VMA hooks for policy
> numa-api-vma-policy-hooks fix
>
> numa-api-shared-memory-support.patch
> numa api: Add shared memory support
> numa-api-shared-memory-support-tweaks
>
> small-numa-api-fixups.patch
> small numa api fixups
>
> small-numa-api-fixups-fix.patch
> small-numa-api-fixups-fix
>
> numa-api-statistics.patch
> numa api: Add statistics
>
> numa-api-anon-memory-policy.patch
> numa api: Add policy support to anonymous memory
>
> rmap-15-vma_adjust.patch
> rmap 15: vma_adjust
>
> rmap-16-pretend-prio_tree.patch
> rmap 16: pretend prio_tree
>
> rmap-17-real-prio_tree.patch
> rmap 17: real prio_tree
>
> rmap-18-i_mmap_nonlinear.patch
> rmap 18: i_mmap_nonlinear
>
> unmap_mapping_range-comment.patch
> unmap_mapping_range-comment
>
> rmap-19-arch-prio_tree.patch
> rmap 19: arch prio_tree
>
> rmap-19-arch-prio_tree-parisc.patch
> rmap-19-arch-prio_tree-parisc
>
> vm_area_struct-size-comment.patch
> vm_area_struct size comment
>
> rmapc-comment-style-fixups.patch
> rmap.c comment/style fixups
>
> rmap-20-i_mmap_shared-into-i_mmap.patch
> rmap 20 i_mmap_shared into i_mmap
>
> rmap-20-i_mmap_shared-into-i_mmap-parisc.patch
> rmap-20-i_mmap_shared-into-i_mmap-parisc
>
> rmap-21-try_to_unmap_one-mapcount.patch
> rmap 21 try_to_unmap_one mapcount
>
> rmap-22-flush_dcache_mmap_lock.patch
> rmap 22 flush_dcache_mmap_lock
>
> rmap-22-flush_dcache_mmap_lock-parisc.patch
> rmap-22-flush_dcache_mmap_lock-parisc
>
> rmap-23-empty-flush_dcache_mmap_lock.patch
> rmap 23 empty flush_dcache_mmap_lock
>
> rmap-24-no-rmap-fastcalls.patch
> rmap 24 no rmap fastcalls
>
> rmap-27-memset-0-vma.patch
> rmap 27 memset 0 vma
>
> rmap-28-remove_vm_struct.patch
> rmap 28 remove_vm_struct
>
> rmap-29-vm_reserved-safety.patch
> rmap 29 VM_RESERVED safety
>
> rmap-30-fix-bad-mapcount.patch
> rmap 30 fix bad mapcount
>
> rmap-31-unlikely-bad-memory.patch
> rmap 31 unlikely bad memory
>
> rmap-32-zap_pmd_range-wrap.patch
> rmap 32 zap_pmd_range wrap
>
> rmap-33-install_arg_page-vma.patch
> rmap 33 install_arg_page vma
>
> partial-prefetch-for-vma_prio_tree_next.patch
> partial prefetch for vma_prio_tree_next
>
> must-fix.patch
> must fix lists update
> must fix list update
> mustfix update
>
> must-fix-update-5.patch
> must-fix update
>
> ppc64-uninline-__pte_free_tlb.patch
> ppc64: uninline __pte_free_tlb()
>
> export-clear_pages-on-ppc32.patch
> export clear_pages on ppc32
>
> ppc32-fix-__flush_dcache_icache_phys-for-book-e.patch
> PPC32: Fix __flush_dcache_icache_phys() for Book E
>
> ppc32-fix-copy-prefetch-on-non-coherent-ppcs.patch
> PPC32: Fix copy prefetch on non coherent PPCs
>
> ppc32-add-book-e--ppc44x-specific-exception-support.patch
> PPC32: Add Book E / PPC44x specific exception support
>
> ppc32-add-book-e--ppc44x-specific-exception-support-2.patch
> PPC32: Add Book E / PPC44x specific exception support
>
> ppc32-new-ocp-core-support-updated.patch
> PPC32: New OCP core support (updated)
>
> ppc32-bubinga-405ep-for-new-ocp.patch
> PPC32: Bubinga/405EP for new OCP
>
> ppc32-ppc44x-lib-support.patch
> PPC32: PPC44x lib support
>
> ppc32-ibm-ppc4xx-specific-ocp-support.patch
> PPC32: IBM PPC4xx-specific OCP support
>
> ppc32-4xx-core-fixes-and-440gx-pic-support.patch
> PPC32: 4xx core fixes and 440gx PIC support
>
> ppc32-update-4xx-defconfigs.patch
> PPC32: Update 4xx defconfigs
>
> ppc32-ppc40x-ports-for-new-ocp.patch
> PPC32: PPC40x ports for new OCP
>
> ppc32-ppc44x-ports-for-new-ocp.patch
> PPC32: PPC44x ports for new OCP
>
> ppc64-reloc_hide.patch
>
> invalidate_inodes-speedup.patch
> invalidate_inodes speedup
> more invalidate_inodes speedup fixes
>
> config_spinline.patch
> uninline spinlocks for profiling accuracy.
>
> pdflush-diag.patch
>
> get_user_pages-handle-VM_IO.patch
> fix get_user_pages() against mappings of /dev/mem
>
> pci_set_power_state-might-sleep.patch
>
> slab-leak-detector.patch
> slab leak detector
> mm/slab.c warning in cache_alloc_debugcheck_after
>
> local_bh_enable-warning-fix.patch
>
> sched-loadup-roundup.patch
> sched: improved cpu_load rounding
>
> sched-activate-tslt.patch
> sched: fix scheduler for unsynched processor sched_clock
>
> schedstats.patch
> sched: scheduler statistics
>
> cond_resched-might-sleep.patch
> cond_resched() might sleep
>
> fa311-mac-address-fix.patch
> wrong mac address with netgear FA311 ethernet card
>
> pid_max-fix.patch
> Bug when setting pid_max > 32k
>
> use-soft-float.patch
> Use -msoft-float
>
> non-readable-binaries.patch
> Handle non-readable binfmt_misc executables
>
> binfmt_misc-credentials.patch
> binfmt_misc: improve calaulation of interpreter's credentials
>
> poll-select-longer-timeouts.patch
> poll()/select(): support longer timeouts
>
> poll-select-range-check-fix.patch
> poll()/select() range checking fix
>
> poll-select-handle-large-timeouts.patch
> poll()/select(): handle long timeouts
>
> add-a-slab-for-ethernet.patch
> Add a kmalloc slab for ethernet packets
>
> siimage-update.patch
> ide: update for siimage driver
>
> shm-do_munmap-check.patch
>
> stack-overflow-test-fix.patch
> Fix stack overflow test for non-8k stacks
>
> jbd-remove-livelock-avoidance.patch
> JBD: remove livelock avoidance code in journal_dirty_data()
>
> logitech-keyboard-fix.patch
> 2.6.5-rc2 keyboard breakage
>
> stack-reductions-nfsread.patch
> stack reductions: nfs read
>
> speed-up-sata.patch
> speed up SATA
>
> advansys-fix.patch
> advansys check_region() fix
>
> journal_add_journal_head-debug.patch
> journal_add_journal_head-debug
>
> list_del-debug.patch
> list_del debug check
>
> oops-dump-preceding-code.patch
> i386 oops output: dump preceding code
>
> lockmeter.patch
> lockmeter
> ia64 CONFIG_LOCKMETER fix
>
> cciss-logical-device-queues.patch
> cciss: per logical device queues
>
> sk98lin-buggy-vpd-workaround.patch
> net/sk98lin: correct buggy VPD in ASUS MB
>
> unplug-can-sleep.patch
> unplug functions can sleep
>
> firestream-warnings.patch
> firestream warnings
>
> ext3_rsv_cleanup.patch
> ext3 block reservation patch set -- ext3 preallocation cleanup
>
> ext3_rsv_base.patch
> ext3 block reservation patch set -- ext3 block reservation
> ext3 reservations: fix performance regression
> ext3 block reservation patch set -- mount and ioctl feature
> ext3 block reservation patch set -- dynamically increase reservation
> window
>
> ext3-reservation-default-on.patch
> ext3 reservation: default to on
>
> ext3-reservation-ifdef-cleanup-patch.patch
> ext3 reservation ifdef cleanup patch
>
> ext3-reservation-max-window-size-check-patch.patch
> ext3 reservation max window size check patch
>
> ext3-reservation-file-ioctl-fix.patch
> ext3 reservation file ioctl fix
>
> ext3-lazy-discard-reservation-window-patch.patch
> ext3 lazy discard reservation window patch
>
> ext3-discard-reservation-in-last-iput-fix-patch.patch
> ext3 discard reservation in last iput fix patch
>
> ext3-discard-reservation-in-last-iput-fix-patch-fix.patch
> Fix lazy reservation discard
>
> ext3-reservation-bad-inode-fix.patch
> ext3 reservations: bad_inode fix
>
> ext3_reservation_discard_race_fix.patch
> ext3 reservation discard race fix
>
> 0-autofs4-2.6.0-signal-20040405.patch
> autofs: dnotify + autofs may create signal/restart syscall loop
>
> add-omitted-autofs4-super-block-field.patch
> add omitted autofs4 super block field
>
> 1-autofs4-2.6.4-cleanup-20040405.patch
> autofs: printk cleanups
>
> 2-autofs4-2.6.4-fill_super-20040405.patch
>
> 3-autofs4-2.6.0-bkl-20040405.patch
> autofs: locking rework
>
> 4-autofs4-2.6.0-expire-20040405.patch
> autofs: expiry refcount fixes
>
> 4-autofs4-260-expire-20040405-fix.patch
> 4-autofs4-2.6.0-expire-20040405 locking fix
>
> 4-autofs4-260-expire-20040405-fix-fix.patch
> autofs expiry fix
>
> 4-autofs4-2.6.0-expire-20040405-may_umount_tree-cleanup.patch
> autofs4: may_umount_tree() cleanup
>
> 5-autofs4-2.6.0-readdir-20040405.patch
> autofs: readdir fixes
>
> umount-after-bad-chdir.patch
> fix umount after bad chdir
>
> autofs4-fix-handling-of-chdir-and-chroot.patch
> autofs4: fix handling of chdir and chroot
>
> 6-autofs4-2.6.0-may_umount-20040405.patch
> autofs: add ioctl to query unmountability
>
> 7-autofs4-2.6.0-extra-20040405.patch
> autofs: readdir futureproofing
>
> autofs-locking-fix.patch
> autofs locking fix
>
> autofs4-race-fix.patch
> autofs4 race fix
>
> autofs4-compat-ioctls.patch
> autofs compat ioctls
>
> clean-up-asm-pgalloch-include.patch
> Clean up asm/pgalloc.h include
>
> clean-up-asm-pgalloch-include-2.patch
> Clean up asm/pgalloc.h include
>
> clean-up-asm-pgalloch-include-3.patch
> Clean up asm/pgalloc.h include 3
>
> input-tsdev-fixes.patch
> tsdev.c fixes
>
> fix-scancode-keycode-scancode-conversion-for-265.patch
> Fix scancode->keycode->scancode conversion
>
> use-less-stack-in-ide_unregister.patch
> use less stack in ide_unregister
>
> fealnx-mac-address-and-other-issues.patch
> Fealnx. Mac address and other issues
>
> reiserfs-group-alloc-9.patch
> reiserfs: block allocator optimizations
>
> reiserfs-remove-debugging-warning-from-block-allocator.patch
> reiserfs: remove debugging warning from block allocator
>
> reiserfs-group-alloc-9-build-fix.patch
> reiserfs-group-alloc-9 build fix
>
> reiserfs-search_reada-5.patch
> reiserfs: btree readahead
>
> reiserfs-data-logging-support.patch
> reiserfs data logging support
>
> problems-with-atkbd_command--atkbd_interrupt-interaction.patch
> Problems with atkbd_command & atkbd_interrupt interaction
>
> mark-config_mac_serial-drivers-macintosh-macserialc-as-broken.patch
> Mark CONFIG_MAC_SERIAL (drivers/macintosh/macserial.c) as broken
>
> radeon-garbled-screen-fix.patch
> radeonfb: fix garbled screen
>
> neomagic-driver-update.patch
> Neomagic driver update.
>
> tridentfbc-warning-fix.patch
> video/tridentfb.c warning fix
>
> hgafbc-warning-fix.patch
> video/hgafb.c warning fix
>
> tdfxfbc-warning-fix.patch
> video/tdfxfb.c warning fix
>
> imsttfbc-warning-fix.patch
> video/imsttfb.c. warning fix
>
> fbdev-logo-handling-fix.patch
> fbdev: clean up logo handling
>
> fbdev-redundant-prows-calculation-removal.patch
> fbdev: remove redundant p->vrows calculation
>
> fbdev-remove-redundant-local.patch
> fbdev: remove redundant local
>
> fbdev-access_align-default.patch
> fbdev: set a default access_align value
>
> fix-null-ptr-dereference-in-pm2fb_probe-2.patch
> Fix NULL-ptr dereference in pm2fb_probe
>
> virtual-fbdev-updates.patch
> Virtual fbdev updates
>
> vesa-fbdev-update.patch
> Vesa Fbdev update
>
> vesa-fbdev-update-fix.patch
> Vesa Fbdev update fix
>
> sis-agp-updates.patch
> SIS AGP updates
>
> new-asiliant-framebuffer-driver.patch
> New Asiliant framebuffer driver.
>
> fbcon-and-unimap.patch
> Fix fbcon and unimap
>
> videodev-handle-class_register-failure.patch
> videodev: handle class_register() failure
>
> q40-fbdev-updates.patch
> Q40 fbdev updates.
>
> acpiphp_glue-oops-fix.patch
> acpiphp_glue.c oops fix
>
> clear_backing_dev_congested.patch
> clear_baking_dev_congested
>
> dpt_i2o.patch
> Fix dpt_i2o
>
> allow-i386-to-reenable-interrupts-on-lock-contention.patch
> Allow i386 to reenable interrupts on lock contention
>
> ia64-cpuhotplug-core_kernel_init.patch
> oa64 cpu hotplug: core kernel initialisation
>
> ia64-cpuhotplug-init_removal.patch
> ia64 cpu hotplug: init section fixes
>
> ia64-cpuhotplug-sysfs_ia64.patch
> ia64 cpu hotplug: sysfs additions
>
> ia64-cpuhotplug-irq_affinity_fix.patch
> ia64 cpu hotplug: IRQ affinity work
>
> ia64-cpuhotplug-palinfo.patch
> ia64 cpu hotplug: /proc rework
>
> ia64-cpu-hotplug-cpu_present-2.patch
> Revisited: ia64-cpu-hotplug-cpu_present.patch
>
> ia64-cpu-hotplug-cpu_present-2-fix.patch
> ia64-cpu-hotplug-cpu_present-2-fix
>
> ia64-cpuhotplug-hotcpu.patch
> ia64 cpu hotplug: core
>
> module-ref-counting-for-vt-console-drivers.patch
> Module ref counting for vt console drivers
>
> i2o-subsystem-fixing-and-cleanup-for-26-i2o-config-cleanpatch.patch
> I2O subsystem fixing and cleanup for 2.6 - i2o-config-clean.patch
>
> i2o-subsystem-fixing-and-cleanup-for-26-i2o-passthrupatch.patch
> I2O subsystem fixing and cleanup for 2.6 - i2o-passthru.patch
>
> i2o-64-bit-fixes.patch
> i2o: 64-bit fixes
>
> i2o-subsystem-fixing-and-cleanup-for-26-i2o_block-cleanuppatch.patch
> I2O subsystem fixing and cleanup for 2.6 - i2o_block-cleanup.patch
>
> i2o-subsystem-fixing-and-cleanup-for-26-i2o-64-bit-fixpatch.patch
> I2O subsystem fixing and cleanup for 2.6 - i2o-64-bit-fix.patch
>
> i2o-subsystem-fixing-and-cleanup-for-26-i2o-makefile-cleanuppatch.patch
> I2O subsystem fixing and cleanup for 2.6 - i2o-makefile-cleanup.patch
>
> make-4k-stacks-permanent.patch
> make 4k stacks permanent
>
> force-config_regparm-to-y.patch
> Force CONFIG_REGPARM to `y'
>
> ia64-remove-errno-refs.patch
> ia64-remove-errno-refs
>
> missing-closing-n-in-printk.patch
> missing closing n in printk
>
> invalid-notify_changesymlink-in-nfsd.patch
> Invalid notify_change(symlink, [ATTR_MODE]) in nfsd
>
> invalid-notify_changesymlink-in-nfsd-fix.patch
> Fix "Invalid notify_change(symlink, [ATTR_MODE]) in nfsd"
>
> fix-sysfs-symlinks.patch
> fix sysfs symlinks
>
> sysfs-backing-store-sysfs_rename_dir-fix.patch
> sysfs backing store negative dentry hashing fix
>
> sysfs-leaves-mount.patch
> sysfs backing store: sysfs_direct
>
> sysfs-leaves-dir.patch
> sysfs backing store: inode operations
>
> sysfs-leaves-file.patch
> sysfs backing store: sysfs operations
>
> sysfs-leaves-symlink.patch
> sysfs backing store: sysfs_create_link changes
>
> sysfs-leaves-bin.patch
> sysfs backing store: bin file attribute changes
>
> sysfs-leaves-misc.patch
> sysfs backing store: attribute groups
>
> die_386_graphic.patch
> ia32 oops diagnostic fix
>
> fix-net-tulip-winbond-840c-warning.patch
> fix net/tulip/winbond-840.c warning.
>
> hugetlb_shm_group-sysctl-gid-0-fix.patch
> hugetlb_shm_group-sysctl-gid-0-fix
>
> mlock_group-sysctl.patch
> mlock_group sysctl
>
> nfs_writepage_sync-stack-reduction.patch
> nfs_writepage_sync stack reduction
>
> nfs4-stack-reduction.patch
> nfs4 stack reduction
>
> idr-overflow-fixes.patch
> Fixes for idr code
> idr-overflow-fixes fix
> More fixes for idr code
> Fixes for POSIX timers
> timers-signals-rlimits-setuid-fix
> timers-signals-rlimits-fix
> timers-signals-rlimits-rename-stuff
> idr-overflow-fixes fix
> More fixes for idr code
>
> idr-remove-counter.patch
> idr: remove counter bits from id's
>
> rlim-add-rlimit-entry-for-controlling-queued-signals.patch
> RLIM: add rlimit entry for controlling queued signals
>
> rlim-add-sigpending-field-to-user_struct.patch
> RLIM: add sigpending field to user_struct
>
> rlim-pass-task_struct-in-send_signal.patch
> RLIM: pass task_struct in send_signal()
>
> rlim-add-simple-get_uid-helper.patch
> RLIM: add simple get_uid() helper
>
> rlim-enforce-rlimits-on-queued-signals.patch
> RLIM: enforce rlimits on queued signals
>
> rlim-remove-unused-queued_signals-global-accounting.patch
> RLIM: remove unused queued_signals global accounting
>
> rlim-add-rlimit-entry-for-posix-mqueue-allocation.patch
> RLIM: add rlimit entry for POSIX mqueue allocation
>
> rlim-add-mq_bytes-to-user_struct.patch
> RLIM: add mq_bytes to user_struct
>
> rlim-add-mq_attr_ok-helper.patch
> RLIM: add mq_attr_ok() helper
>
> rlim-enforce-rlimits-for-posix-mqueue-allocation.patch
> RLIM: enforce rlimits for POSIX mqueue allocation
>
> rlim-adjust-default-mqueue-sizes.patch
> RLIM: adjust default mqueue sizes
>
> call-might_sleep-in-tasklet_kill.patch
> Call might_sleep() in tasklet_kill
>
> d_flags-locking-fix.patch
> d_flags locking fixes
>
> d_vfs_flags-locking-fix.patch
> d_vfs_flags locking fix
>
> dentry-shrinkage.patch
> dentry shrinkage
>
> dentry-qstr-consolidation.patch
> dentry qstr consolidation
>
> dentry-qstr-consolidation-fix.patch
> dentry qstr consolidation fix
>
> dentry-d_bucket-fix.patch
> dentry d_bucket fix
>
> dentry-d_flags-consolidation.patch
> more dentry shrinkage
>
> dentry-layout-tweaks.patch
> dentry layout tweaks
>
> to-fix-i2o_proc-kernel-panic-on-access-of-proc-i2o-iop0-lct.patch
> Fix i2o_proc kernel panic on access of /proc/i2o/iop0/lct
>
> i2o_proc-module-owner-fix.patch
> i2o_proc module owner fix
>
> add-qsort-library-function.patch
> add qsort library function
>
> have-xfs-use-kernel-provided-qsort.patch
> Have XFS use kernel-provided qsort
>
> slabify-iocontext-request_queue.patch
> slabify iocontext + request_queue
>
> slabify-iocontext-request_queue-SLAB_PANIC.patch
> slabify-iocontext-request_queue: use SLAB_PANIC
>
> show-last-kernel-image-symbol-in-proc-kallsyms.patch
> show last kernel-image symbol in /proc/kallsyms
>
> raid-locking-fix.patch
> raid locking fix.
>
> include-aliases-in-kallsyms.patch
> Include Aliases in kallsyms
>
> make-buildcheck.patch
> make buildcheck
>
> make-buildcheck-license-fix.patch
> make buildcheck license fix
>
> efivars-fix.patch
> efivars: check that it's enabled
>
> serial-fifo-size-is-ignored.patch
> serial fifo size is ignored
>
> expose-backing-dev-max-read-ahead.patch
> expose backing dev max read-ahead
>
> ib700wdt-fix.patch
> ib700wdt watchdog driver fix
>
> ib700wdt-fix-2.patch
> ib700wdt watchdog driver fix #2
>
> laptop-doc-bugfix.patch
> laptop-mode documentation fix
>
> create_workqueue-locking-bogon.patch
> create_workqueue locking fix
>
> problem-with-aladdincard-entry-in-parport_pc.patch
> Fix AladdinCard entry in parport_pc
>
> seeky-readahead-speedups.patch
> speed up readahead for seeky loads
>
> watchdog-timer-for-intel-ixp4xx-cpus.patch
> Watchdog timer for Intel IXP4xx CPUs
>
> i810_audio-fixes-from-herbert-xu.patch
> i810_audio fixes from Herbert Xu
>
> ide-diskc-revert-to-previous-24-way-of-handling-flush-cache-commands.patch
> ide-disk.c: revert to previous (2.4) way of handling flush cache commands
>
> update-laptop-mode-control-script-with-xfs_hz=100.patch
> Update laptop mode control script with XFS_HZ=100
>
> del_singleshot_timer_sync.patch
> Add del_single_shot_timer()
>
> del_singleshot_timer_sync-tweaks.patch
> del_singleshot_timer_sync-tweaks
>
> really-ptrace-single-step-2.patch
> ptrace single-stepping fix
>
> dquot_release-oops-workaround.patch
> dquot_release oops workaround
>
> h8-300-update-1-9-bitopsh-add-find_next_bit.patch
> H8/300: bitops.h add find_next_bit
>
> h8-300-update-2-9-ldscripts-fix.patch
> H8/300: ldscripts fix
>
> h8-300-update-3-9-pic-support.patch
> H8/300: pic support
>
> h8-300-update-4-9-preempt-support.patch
> H8/300: preempt support
>
> h8-300-update-5-9-sci-driver-fix.patch
> H8/300: SCI driver fix
>
> h8-300-update-6-9-ne-driver.patch
> H8/300: ne driver
>
> h8-300-update-7-9-kconfig.patch
> H8/300: Kconfig
>
> h8-300-update-8-9-delete-headers.patch
> H8/300: delete headers
>
> h8-300-update-9-9-more-cleanup.patch
> H8/300: more cleanup
>
> calculate-ngroups_per_block-from-page_size.patch
> calculate NGROUPS_PER_BLOCK from PAGE_SIZE
>
> pci-debug-compile-fix-in-sis_router_probe.patch
> PCI debug compile fix in sis_router_probe()
>
> remove-empty-build-of-capabilityo.patch
> security: remove empty build of capability.o
>
> minor-cleanups-in-capabilityc.patch
> security: minor cleanups in capability.c
>
> add-disable-param-to-capabilities-module.patch
> security: add disable param to capabilities module
>
> fix-linux-doc-errors.patch
> fix linux doc errors
>
> fix-block-layer-ioctl-bug.patch
> fix block layer ioctl bug
>
> fix-crash-on-modprobe-ohci1394.patch
> fix crash on `modprobe ohci1394; modprobe -r ohci1394'
>
> x86_64-has-buggy-ffs-implementation.patch
> x86_64 has buggy ffs() implementation
>
> make-reiserfs-not-to-crash-on-oom.patch
> Fix reiserfs oom crash
>
> implement-print_modules.patch
> implement print_modules()
>
> m68k-print_modules.patch
> m68k: use print_modules()
>
> fix-endianess-in-modpost-when-cross-compiling-for-sparc-on-i386.patch
> Fix endianess in modpost when cross-compiling for sparc on i386
>
> fix-cyclades-compile-with-pci.patch
> fix cyclades compile with !PCI
>
> fix-tlanc-for-pci.patch
> fix tlan.c for !PCI
>
> fix-aic7xxx_oldc-for-pci.patch
> fix aic7xxx_old.c for !PCI
>
> powernow-k8-buggy-bios-override-for-266.patch
> Powernow-k8 buggy BIOS override for 2.6.6
>
> x86_64-msr-warning-fix.patch
> x86_64 msr.c warning fix
>
> abs-cleanup.patch
> abs() cleanup
>
>
> -
> 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/
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 12:14 ` 2.6.6-mm2 Matt H.
@ 2004-05-13 18:24 ` Andrew Morton
2004-05-13 22:40 ` 2.6.6-mm2 Greg KH
0 siblings, 1 reply; 54+ messages in thread
From: Andrew Morton @ 2004-05-13 18:24 UTC (permalink / raw)
To: lkml; +Cc: linux-kernel, Greg KH
"Matt H." <lkml@lpbproductions.com> wrote:
>
> Just attempted to compile 2.6.6-mm2 and got this error
>
> CC [M] drivers/usb/core/driverfs.o
> CC [M] drivers/usb/core/hcd-pci.o
> LD [M] drivers/usb/core/usbcore.o
> LD drivers/usb/host/built-in.o
> CC [M] drivers/usb/host/ehci-hcd.o
> CC [M] drivers/usb/host/ohci-hcd.o
> In file included from drivers/usb/host/ohci-hcd.c:129:
> drivers/usb/host/ohci-hub.c: In function `ohci_rh_resume':
> drivers/usb/host/ohci-hub.c:313: error: `hcd' undeclared (first use in this
> function)
hm, not sure what's happened there...
---
25-akpm/drivers/usb/host/ohci-hub.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/usb/host/ohci-hub.c~ohci-hub-build-fix drivers/usb/host/ohci-hub.c
--- 25/drivers/usb/host/ohci-hub.c~ohci-hub-build-fix 2004-05-13 11:23:48.588645576 -0700
+++ 25-akpm/drivers/usb/host/ohci-hub.c 2004-05-13 11:23:56.972371056 -0700
@@ -310,7 +310,7 @@ static void ohci_rh_resume (void *_hcd)
static void ohci_rh_resume (void *_hcd)
{
- struct ohci_hcd *ohci = hcd_to_ohci (hcd);
+ struct ohci_hcd *ohci = hcd_to_ohci (_hcd);
ohci_dbg(ohci, "rh_resume ??\n");
}
_
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 18:24 ` 2.6.6-mm2 Andrew Morton
@ 2004-05-13 22:40 ` Greg KH
0 siblings, 0 replies; 54+ messages in thread
From: Greg KH @ 2004-05-13 22:40 UTC (permalink / raw)
To: Andrew Morton; +Cc: lkml, linux-kernel
On Thu, May 13, 2004 at 11:24:47AM -0700, Andrew Morton wrote:
> "Matt H." <lkml@lpbproductions.com> wrote:
> >
> > Just attempted to compile 2.6.6-mm2 and got this error
> >
> > CC [M] drivers/usb/core/driverfs.o
> > CC [M] drivers/usb/core/hcd-pci.o
> > LD [M] drivers/usb/core/usbcore.o
> > LD drivers/usb/host/built-in.o
> > CC [M] drivers/usb/host/ehci-hcd.o
> > CC [M] drivers/usb/host/ohci-hcd.o
> > In file included from drivers/usb/host/ohci-hcd.c:129:
> > drivers/usb/host/ohci-hub.c: In function `ohci_rh_resume':
> > drivers/usb/host/ohci-hub.c:313: error: `hcd' undeclared (first use in this
> > function)
>
> hm, not sure what's happened there...
Oops, didn't check with CONFIG_PM disabled, sorry.
Applied, thanks.
greg k-h
^ permalink raw reply [flat|nested] 54+ messages in thread
* i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
` (2 preceding siblings ...)
2004-05-13 12:14 ` 2.6.6-mm2 Matt H.
@ 2004-05-13 12:54 ` Sean Neakums
2004-05-13 13:53 ` Dave Jones
2004-05-13 13:38 ` 2.6.6-mm2: EFI_VARS=m is broken Adrian Bunk
` (4 subsequent siblings)
8 siblings, 1 reply; 54+ messages in thread
From: Sean Neakums @ 2004-05-13 12:54 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Andrew Morton <akpm@osdl.org> writes:
> bk-agpgart.patch
>
With this patch applied, agpgart doesn't initialise on my Dell
OptiPlex GX110, causing drm to fail to initialise.
Linux agpgart interface v0.100 (c) Dave Jones
[drm:i810_probe] *ERROR* Cannot initialize the agpgart module.
Here are the messages from successful initialisation with the patch
reverted.
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel i810 E Chipset.
agpgart: Maximum main memory to use for agp memory: 320M
agpgart: detected 4MB dedicated video ram.
agpgart: AGP aperture is 64M @ 0xf8000000
[drm] Initialized i810 1.4.0 20030605 on minor 0: Intel Corp. 82810E DC-133 CGC [Chipset Graphics Controller]
Here is the lspci -vvvv output:
0000:00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03)
Subsystem: Dell Computer Corporation: Unknown device 00b4
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
0000:00:01.0 VGA compatible controller: Intel Corp. 82810E DC-133 CGC [Chipset Graphics Controller] (rev 03) (prog-if 00 [VGA])
Subsystem: Dell Computer Corporation: Unknown device 00b4
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 9
Region 0: Memory at f8000000 (32-bit, prefetchable)
Region 1: Memory at ff000000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fd000000-feffffff
Prefetchable memory behind bridge: fff00000-000fffff
BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
0000:00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC) (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
0000:00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02) (prog-if 80 [Master])
Subsystem: Intel Corp. 82801AA IDE
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 4: I/O ports at ffa0 [size=16]
0000:00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corp. 82801AA USB
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin D routed to IRQ 11
Region 4: I/O ports at ff80 [size=32]
0000:00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02)
Subsystem: Intel Corp. 82801AA SMBus
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 10
Region 4: I/O ports at dcd0 [size=16]
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801AA AC'97 Audio (rev 02)
Subsystem: Dell Computer Corporation: Unknown device 00b4
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin B routed to IRQ 10
Region 0: I/O ports at d800
Region 1: I/O ports at dc80 [size=64]
0000:01:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
Subsystem: Dell Computer Corporation: Unknown device 00b4
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2500ns min, 2500ns max), Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at e480 [size=fe000000]
Region 1: Memory at fdffe400 (32-bit, non-prefetchable) [size=128]
Expansion ROM at 00020000 [disabled]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-13 12:54 ` i810 AGP fails to initialise (was Re: 2.6.6-mm2) Sean Neakums
@ 2004-05-13 13:53 ` Dave Jones
2004-05-13 13:58 ` Andi Kleen
0 siblings, 1 reply; 54+ messages in thread
From: Dave Jones @ 2004-05-13 13:53 UTC (permalink / raw)
To: Andrew Morton, linux-kernel; +Cc: ak
On Thu, May 13, 2004 at 01:54:03PM +0100, Sean Neakums wrote:
> > bk-agpgart.patch
> With this patch applied, agpgart doesn't initialise on my Dell
> OptiPlex GX110, causing drm to fail to initialise.
>
> Linux agpgart interface v0.100 (c) Dave Jones
> [drm:i810_probe] *ERROR* Cannot initialize the agpgart module.
>
> Here are the messages from successful initialisation with the patch
> reverted.
>
> Linux agpgart interface v0.100 (c) Dave Jones
> agpgart: Detected an Intel i810 E Chipset.
> agpgart: Maximum main memory to use for agp memory: 320M
> agpgart: detected 4MB dedicated video ram.
> agpgart: AGP aperture is 64M @ 0xf8000000
> [drm] Initialized i810 1.4.0 20030605 on minor 0: Intel Corp. 82810E DC-133 CGC [Chipset Graphics Controller]
Damn, probably something trivially wrong in Andi's changes.
Andi?
Dave
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-13 13:53 ` Dave Jones
@ 2004-05-13 13:58 ` Andi Kleen
2004-05-13 14:02 ` Sean Neakums
0 siblings, 1 reply; 54+ messages in thread
From: Andi Kleen @ 2004-05-13 13:58 UTC (permalink / raw)
To: Dave Jones; +Cc: akpm, linux-kernel
On Thu, 13 May 2004 14:53:08 +0100
Dave Jones <davej@redhat.com> wrote:
>
> Damn, probably something trivially wrong in Andi's changes.
>
> Andi?
lspci and lspci -n of the failing system please.
-Andi
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-13 13:58 ` Andi Kleen
@ 2004-05-13 14:02 ` Sean Neakums
2004-05-13 15:41 ` Andi Kleen
0 siblings, 1 reply; 54+ messages in thread
From: Sean Neakums @ 2004-05-13 14:02 UTC (permalink / raw)
To: Andi Kleen; +Cc: Dave Jones, akpm, linux-kernel
Andi Kleen <ak@suse.de> writes:
> On Thu, 13 May 2004 14:53:08 +0100
> Dave Jones <davej@redhat.com> wrote:
>
>>
>> Damn, probably something trivially wrong in Andi's changes.
>>
>> Andi?
>
> lspci and lspci -n of the failing system please.
0000:00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03)
0000:00:01.0 VGA compatible controller: Intel Corp. 82810E DC-133 CGC [Chipset Graphics Controller] (rev 03)
0000:00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev 02)
0000:00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC) (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02)
0000:00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801AA AC'97 Audio (rev 02)
0000:01:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
0000:00:00.0 Class 0600: 8086:7124 (rev 03)
0000:00:01.0 Class 0300: 8086:7125 (rev 03)
0000:00:1e.0 Class 0604: 8086:2418 (rev 02)
0000:00:1f.0 Class 0601: 8086:2410 (rev 02)
0000:00:1f.1 Class 0101: 8086:2411 (rev 02)
0000:00:1f.2 Class 0c03: 8086:2412 (rev 02)
0000:00:1f.3 Class 0c05: 8086:2413 (rev 02)
0000:00:1f.5 Class 0401: 8086:2415 (rev 02)
0000:01:0c.0 Class 0200: 10b7:9200 (rev 78)
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-13 14:02 ` Sean Neakums
@ 2004-05-13 15:41 ` Andi Kleen
2004-05-14 3:47 ` Clemens Schwaighofer
2004-05-14 7:42 ` Sean Neakums
0 siblings, 2 replies; 54+ messages in thread
From: Andi Kleen @ 2004-05-13 15:41 UTC (permalink / raw)
To: Sean Neakums; +Cc: davej, akpm, linux-kernel
On Thu, 13 May 2004 15:02:25 +0100
Sean Neakums <sneakums@zork.net> wrote:
>
> 0000:00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03)
I don't see what could be wrong. The PCI table has this PCI ID:
#define PCI_DEVICE_ID_INTEL_82810E_MC 0x7124
...
#define ID(x) \
{ \
.class = (PCI_CLASS_BRIDGE_HOST << 8), \
.class_mask = ~0, \
.vendor = PCI_VENDOR_ID_INTEL, \
.device = x, \
.subvendor = PCI_ANY_ID, \
.subdevice = PCI_ANY_ID, \
}
...
ID(PCI_DEVICE_ID_INTEL_82810E_MC),
We also tested it on some other machines and it worked.
Does anyone else see a problem in the patches?
Sean, can you double check that when you compile the AGP driver as module
that the 7124 PCI ID appears in modinfo intel-agp ?
And does the module also refuse to load ?
-Andi
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-13 15:41 ` Andi Kleen
@ 2004-05-14 3:47 ` Clemens Schwaighofer
2004-05-14 7:42 ` Sean Neakums
1 sibling, 0 replies; 54+ messages in thread
From: Clemens Schwaighofer @ 2004-05-14 3:47 UTC (permalink / raw)
To: Andi Kleen; +Cc: davej, akpm, linux-kernel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andi Kleen wrote:
| On Thu, 13 May 2004 15:02:25 +0100
| Sean Neakums <sneakums@zork.net> wrote:
|
|>0000:00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics
Memory Controller Hub] (rev 03)
I have exact the same problem here, my i810 fails to init. I used exact
the same config like 2.6.6-mm1 which works fine.
X fails with: no /dev/agpgart
and in dmesg I find this:
i810fb: cannot acquire agp
...
Linux agpgart interface v0.100 (c) Dave Jones
[drm:i810_probe] *ERROR* Cannot initialize the agpgart module.
lspci:
0000:00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics
Memory Controller Hub] (rev 03)
0000:00:01.0 VGA compatible controller: Intel Corp. 82810E DC-133 CGC
[Chipset Graphics Controller] (rev 03)
0000:00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface
to PCI Bridge (rev 05)
0000:00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 05)
0000:00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 05)
0000:00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 05)
0000:00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 05)
0000:00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 05)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97
Audio (rev 05)
0000:01:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM
Ethernet Controller (rev 03)
lspci -n
0000:00:00.0 Class 0600: 8086:7124 (rev 03)
0000:00:01.0 Class 0300: 8086:7125 (rev 03)
0000:00:1e.0 Class 0604: 8086:244e (rev 05)
0000:00:1f.0 Class 0601: 8086:2440 (rev 05)
0000:00:1f.1 Class 0101: 8086:244b (rev 05)
0000:00:1f.2 Class 0c03: 8086:2442 (rev 05)
0000:00:1f.3 Class 0c05: 8086:2443 (rev 05)
0000:00:1f.4 Class 0c03: 8086:2444 (rev 05)
0000:00:1f.5 Class 0401: 8086:2445 (rev 05)
0000:01:08.0 Class 0200: 8086:2449 (rev 03)
- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
TEQUILA\Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.co.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFApEFBjBz/yQjBxz8RAtcyAKDjbuJMwyAFktes/KnCfbpPW3rt3QCcDM5a
DMrSA1kamtEp9i+4S5rQUyM=
=MAJF
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-13 15:41 ` Andi Kleen
2004-05-14 3:47 ` Clemens Schwaighofer
@ 2004-05-14 7:42 ` Sean Neakums
2004-05-15 9:52 ` Sean Neakums
1 sibling, 1 reply; 54+ messages in thread
From: Sean Neakums @ 2004-05-14 7:42 UTC (permalink / raw)
To: Andi Kleen; +Cc: davej, akpm, linux-kernel
Andi Kleen <ak@suse.de> writes:
> Sean, can you double check that when you compile the AGP driver as module
> that the 7124 PCI ID appears in modinfo intel-agp ?
> And does the module also refuse to load ?
I rebuilt with agpgart, intel-agp and i810 as modules, modprobed them,
and it works.
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel i810 E Chipset.
agpgart: Maximum main memory to use for agp memory: 320M
agpgart: detected 4MB dedicated video ram.
agpgart: AGP aperture is 64M @ 0xf8000000
[drm] Initialized i810 1.4.0 20030605 on minor 0: Intel Corp. 82810E DC-133 CGC [Chipset Graphics Controller]
Very odd.
Here is the modinfo output for intel-agp.
author: Dave Jones <davej@codemonkey.org.uk>
license: GPL and additional rights
vermagic: 2.6.6-mm2 preempt PENTIUMIII REGPARM 4KSTACKS gcc-3.4
depends: agpgart
alias: pci:v00008086d*sv*sd*bc06sc00i00*
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-14 7:42 ` Sean Neakums
@ 2004-05-15 9:52 ` Sean Neakums
2004-05-17 8:49 ` Sean Neakums
0 siblings, 1 reply; 54+ messages in thread
From: Sean Neakums @ 2004-05-15 9:52 UTC (permalink / raw)
To: Andi Kleen; +Cc: davej, akpm, linux-kernel
Sean Neakums <sneakums@zork.net> writes:
> Andi Kleen <ak@suse.de> writes:
>
>> Sean, can you double check that when you compile the AGP driver as module
>> that the 7124 PCI ID appears in modinfo intel-agp ?
>> And does the module also refuse to load ?
>
> I rebuilt with agpgart, intel-agp and i810 as modules, modprobed them,
> and it works.
I just realised that I probably forgot to reapply the patch before
doing this test. Will check Monday. Sorry about this.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-15 9:52 ` Sean Neakums
@ 2004-05-17 8:49 ` Sean Neakums
2004-05-17 10:01 ` Andi Kleen
0 siblings, 1 reply; 54+ messages in thread
From: Sean Neakums @ 2004-05-17 8:49 UTC (permalink / raw)
To: Andi Kleen; +Cc: davej, akpm, linux-kernel
Sean Neakums <sneakums@zork.net> writes:
> Sean Neakums <sneakums@zork.net> writes:
>
>> Andi Kleen <ak@suse.de> writes:
>>
>>> Sean, can you double check that when you compile the AGP driver as module
>>> that the 7124 PCI ID appears in modinfo intel-agp ?
>>> And does the module also refuse to load ?
>>
>> I rebuilt with agpgart, intel-agp and i810 as modules, modprobed them,
>> and it works.
>
> I just realised that I probably forgot to reapply the patch before
> doing this test. Will check Monday. Sorry about this.
Below is modinfo output. The module loads but doesn't initialise the
AGP.
author: Dave Jones <davej@codemonkey.org.uk>
license: GPL and additional rights
vermagic: 2.6.6-mm2 preempt PENTIUMIII REGPARM 4KSTACKS gcc-3.4
depends: agpgart
alias: pci:v00008086d00007180sv*sd*bc06sc00i00*
alias: pci:v00008086d00007190sv*sd*bc06sc00i00*
alias: pci:v00008086d000071A0sv*sd*bc06sc00i00*
alias: pci:v00008086d00007120sv*sd*bc06sc00i00*
alias: pci:v00008086d00007122sv*sd*bc06sc00i00*
alias: pci:v00008086d00007124sv*sd*bc06sc00i00*
alias: pci:v00008086d00001130sv*sd*bc06sc00i00*
alias: pci:v00008086d00002500sv*sd*bc06sc00i00*
alias: pci:v00008086d00002501sv*sd*bc06sc00i00*
alias: pci:v00008086d00003575sv*sd*bc06sc00i00*
alias: pci:v00008086d00001A21sv*sd*bc06sc00i00*
alias: pci:v00008086d00001A30sv*sd*bc06sc00i00*
alias: pci:v00008086d00002560sv*sd*bc06sc00i00*
alias: pci:v00008086d00002530sv*sd*bc06sc00i00*
alias: pci:v00008086d00003340sv*sd*bc06sc00i00*
alias: pci:v00008086d00003580sv*sd*bc06sc00i00*
alias: pci:v00008086d00002531sv*sd*bc06sc00i00*
alias: pci:v00008086d00002570sv*sd*bc06sc00i00*
alias: pci:v00008086d00002578sv*sd*bc06sc00i00*
alias: pci:v00008086d00002550sv*sd*bc06sc00i00*
alias: pci:v00008086d0000255Dsv*sd*bc06sc00i00*
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-17 8:49 ` Sean Neakums
@ 2004-05-17 10:01 ` Andi Kleen
2004-05-17 11:04 ` Sean Neakums
0 siblings, 1 reply; 54+ messages in thread
From: Andi Kleen @ 2004-05-17 10:01 UTC (permalink / raw)
To: Andi Kleen, davej, akpm, linux-kernel
On Mon, May 17, 2004 at 09:49:56AM +0100, Sean Neakums wrote:
> Sean Neakums <sneakums@zork.net> writes:
>
> > Sean Neakums <sneakums@zork.net> writes:
> >
> >> Andi Kleen <ak@suse.de> writes:
> >>
> >>> Sean, can you double check that when you compile the AGP driver as module
> >>> that the 7124 PCI ID appears in modinfo intel-agp ?
> >>> And does the module also refuse to load ?
> >>
> >> I rebuilt with agpgart, intel-agp and i810 as modules, modprobed them,
> >> and it works.
> >
> > I just realised that I probably forgot to reapply the patch before
> > doing this test. Will check Monday. Sorry about this.
>
> Below is modinfo output. The module loads but doesn't initialise the
> AGP.
Someone else reported that it worked modular at least. When you apply
the following patch what output do you get in the kernel log when you
load the module?
-Andi
--- linux-2.6.6-work/drivers/char/agp/intel-agp.c.~2~ 2004-05-10 20:59:24.000000000 +0200
+++ linux-2.6.6-work/drivers/char/agp/intel-agp.c 2004-05-17 11:56:01.000000000 +0200
@@ -1263,9 +1263,13 @@
u8 cap_ptr = 0;
struct resource *r;
+ printk("agp_intel_probe device %x\n", pdev->device);
+
cap_ptr = pci_find_capability(pdev, PCI_CAP_ID_AGP);
- if (!cap_ptr)
+ if (!cap_ptr) {
+ printk("no cap\n");
return -ENODEV;
+ }
bridge = agp_alloc_bridge();
if (!bridge)
@@ -1432,6 +1436,7 @@
pci_set_drvdata(pdev, bridge);
return agp_add_bridge(bridge);
fail:
+ printk("failure\n");
agp_put_bridge(bridge);
return -ENODEV;
}
@@ -1518,6 +1523,7 @@
return 0;
agp_initialised=1;
+ printk("agp_intel_init\n");
return pci_module_init(&agp_intel_pci_driver);
}
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-17 10:01 ` Andi Kleen
@ 2004-05-17 11:04 ` Sean Neakums
2004-05-17 11:46 ` Andi Kleen
0 siblings, 1 reply; 54+ messages in thread
From: Sean Neakums @ 2004-05-17 11:04 UTC (permalink / raw)
To: Andi Kleen; +Cc: davej, akpm, linux-kernel
Andi Kleen <ak@suse.de> writes:
> On Mon, May 17, 2004 at 09:49:56AM +0100, Sean Neakums wrote:
>> Sean Neakums <sneakums@zork.net> writes:
>>
>> > Sean Neakums <sneakums@zork.net> writes:
>> >
>> >> Andi Kleen <ak@suse.de> writes:
>> >>
>> >>> Sean, can you double check that when you compile the AGP driver as module
>> >>> that the 7124 PCI ID appears in modinfo intel-agp ?
>> >>> And does the module also refuse to load ?
>> >>
>> >> I rebuilt with agpgart, intel-agp and i810 as modules, modprobed them,
>> >> and it works.
>> >
>> > I just realised that I probably forgot to reapply the patch before
>> > doing this test. Will check Monday. Sorry about this.
>>
>> Below is modinfo output. The module loads but doesn't initialise the
>> AGP.
>
> Someone else reported that it worked modular at least. When you apply
> the following patch what output do you get in the kernel log when you
> load the module?
Linux agpgart interface v0.100 (c) Dave Jones
agp_intel_init
agp_intel_probe device 7124
no cap
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-17 11:04 ` Sean Neakums
@ 2004-05-17 11:46 ` Andi Kleen
2004-05-17 12:37 ` Sean Neakums
0 siblings, 1 reply; 54+ messages in thread
From: Andi Kleen @ 2004-05-17 11:46 UTC (permalink / raw)
To: Sean Neakums; +Cc: davej, akpm, linux-kernel
On Mon, 17 May 2004 12:04:36 +0100
Sean Neakums <sneakums@zork.net> wrote:
> Andi Kleen <ak@suse.de> writes:
>
> > On Mon, May 17, 2004 at 09:49:56AM +0100, Sean Neakums wrote:
> >> Sean Neakums <sneakums@zork.net> writes:
> >>
> >> > Sean Neakums <sneakums@zork.net> writes:
> >> >
> >> >> Andi Kleen <ak@suse.de> writes:
> >> >>
> >> >>> Sean, can you double check that when you compile the AGP driver as module
> >> >>> that the 7124 PCI ID appears in modinfo intel-agp ?
> >> >>> And does the module also refuse to load ?
> >> >>
> >> >> I rebuilt with agpgart, intel-agp and i810 as modules, modprobed them,
> >> >> and it works.
> >> >
> >> > I just realised that I probably forgot to reapply the patch before
> >> > doing this test. Will check Monday. Sorry about this.
> >>
> >> Below is modinfo output. The module loads but doesn't initialise the
> >> AGP.
> >
> > Someone else reported that it worked modular at least. When you apply
> > the following patch what output do you get in the kernel log when you
> > load the module?
>
> Linux agpgart interface v0.100 (c) Dave Jones
> agp_intel_init
> agp_intel_probe device 7124
> no cap
Thanks for testing.
Ok. This patch should fix it then. Revert the debug patch first.
Apparently some of the devices listed don't have a AGP capability. Maybe they're only AGPv1
compliant?
Dave, please apply.
-Andi
--- linux-2.6.6-work/drivers/char/agp/intel-agp.c.~3~ 2004-05-17 13:45:26.000000000 +0200
+++ linux-2.6.6-work/drivers/char/agp/intel-agp.c 2004-05-17 13:46:15.000000000 +0200
@@ -1264,8 +1264,6 @@
struct resource *r;
cap_ptr = pci_find_capability(pdev, PCI_CAP_ID_AGP);
- if (!cap_ptr)
- return -ENODEV;
bridge = agp_alloc_bridge();
if (!bridge)
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: i810 AGP fails to initialise (was Re: 2.6.6-mm2)
2004-05-17 11:46 ` Andi Kleen
@ 2004-05-17 12:37 ` Sean Neakums
0 siblings, 0 replies; 54+ messages in thread
From: Sean Neakums @ 2004-05-17 12:37 UTC (permalink / raw)
To: Andi Kleen; +Cc: davej, akpm, linux-kernel
Andi Kleen <ak@suse.de> writes:
> On Mon, 17 May 2004 12:04:36 +0100
> Sean Neakums <sneakums@zork.net> wrote:
>
>> Andi Kleen <ak@suse.de> writes:
>>
>> > On Mon, May 17, 2004 at 09:49:56AM +0100, Sean Neakums wrote:
>> >> Sean Neakums <sneakums@zork.net> writes:
>> >>
>> >> > Sean Neakums <sneakums@zork.net> writes:
>> >> >
>> >> >> Andi Kleen <ak@suse.de> writes:
>> >> >>
>> >> >>> Sean, can you double check that when you compile the AGP driver as module
>> >> >>> that the 7124 PCI ID appears in modinfo intel-agp ?
>> >> >>> And does the module also refuse to load ?
>> >> >>
>> >> >> I rebuilt with agpgart, intel-agp and i810 as modules, modprobed them,
>> >> >> and it works.
>> >> >
>> >> > I just realised that I probably forgot to reapply the patch before
>> >> > doing this test. Will check Monday. Sorry about this.
>> >>
>> >> Below is modinfo output. The module loads but doesn't initialise the
>> >> AGP.
>> >
>> > Someone else reported that it worked modular at least. When you apply
>> > the following patch what output do you get in the kernel log when you
>> > load the module?
>>
>> Linux agpgart interface v0.100 (c) Dave Jones
>> agp_intel_init
>> agp_intel_probe device 7124
>> no cap
>
> Thanks for testing.
>
> Ok. This patch should fix it then. Revert the debug patch first.
This did the trick. Also applied it to 2.6.6-mm3, built static, works
fine there also.
^ permalink raw reply [flat|nested] 54+ messages in thread
* 2.6.6-mm2: EFI_VARS=m is broken
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
` (3 preceding siblings ...)
2004-05-13 12:54 ` i810 AGP fails to initialise (was Re: 2.6.6-mm2) Sean Neakums
@ 2004-05-13 13:38 ` Adrian Bunk
2004-05-13 15:03 ` Matt Domsch
2004-05-13 13:42 ` 2.6.6-mm2 Paolo Ornati
` (3 subsequent siblings)
8 siblings, 1 reply; 54+ messages in thread
From: Adrian Bunk @ 2004-05-13 13:38 UTC (permalink / raw)
To: Andrew Morton, Randy.Dunlap, matthew.e.tolentino, Matt_Domsch
Cc: linux-kernel
On Thu, May 13, 2004 at 03:27:36AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.6-mm1:
>...
> +efivars-fix.patch
>
> Fix oops with efivars enabled but not avaialble.
>...
This patch broke EFI_VARS=m:
<-- snip -->
WARNING: /lib/modules/2.6.6-mm2/kernel/drivers/firmware/efivars.ko needs unknown symbol efi_enabled
<-- snip -->
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2: EFI_VARS=m is broken
2004-05-13 13:38 ` 2.6.6-mm2: EFI_VARS=m is broken Adrian Bunk
@ 2004-05-13 15:03 ` Matt Domsch
0 siblings, 0 replies; 54+ messages in thread
From: Matt Domsch @ 2004-05-13 15:03 UTC (permalink / raw)
To: Adrian Bunk
Cc: Andrew Morton, Randy.Dunlap, matthew.e.tolentino, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
On Thu, May 13, 2004 at 03:38:06PM +0200, Adrian Bunk wrote:
> On Thu, May 13, 2004 at 03:27:36AM -0700, Andrew Morton wrote:
> >...
> > Changes since 2.6.6-mm1:
> >...
> > +efivars-fix.patch
> >
> > Fix oops with efivars enabled but not avaialble.
>
> This patch broke EFI_VARS=m:
Duh. i386 needs to export efi_enabled. ia64 doesn't as it's a
#define in linux/efi.h. Matt T, are you working on EFI for x86_64
too? Patch below for i386.
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
Export efi_enabled to modules such as efivars. Only needed on i386 at
present, as ia64 has this as a #define in linux/efi.h, and EFI isn't
available for other arches.
===== arch/i386/kernel/setup.c 1.118 vs edited =====
--- 1.118/arch/i386/kernel/setup.c Wed Apr 28 02:09:40 2004
+++ edited/arch/i386/kernel/setup.c Thu May 13 09:58:01 2004
@@ -65,6 +65,7 @@
#ifdef CONFIG_EFI
int efi_enabled = 0;
+EXPORT_SYMBOL(efi_enabled);
#endif
/* cpu data as detected by the assembly code in head.S */
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
` (4 preceding siblings ...)
2004-05-13 13:38 ` 2.6.6-mm2: EFI_VARS=m is broken Adrian Bunk
@ 2004-05-13 13:42 ` Paolo Ornati
2004-05-13 14:01 ` 2.6.6-mm2: bk-driver-core-module-fix.patch no longer required Adrian Bunk
2004-05-13 15:07 ` 2.6.6-mm2 Lorenzo Allegrucci
` (2 subsequent siblings)
8 siblings, 1 reply; 54+ messages in thread
From: Paolo Ornati @ 2004-05-13 13:42 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Thursday 13 May 2004 12:27, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6
>-mm2/
CC kernel/module.o
kernel/module.c:730: error: redefinition of `add_attribute'
kernel/module.c:382: error: `add_attribute' previously defined here
kernel/module.c:382: warning: `add_attribute' defined but not used
make[1]: *** [kernel/module.o] Error 1
make: *** [kernel] Error 2
bye
--
Paolo Ornati
Linux v2.6.6
^ permalink raw reply [flat|nested] 54+ messages in thread* 2.6.6-mm2: bk-driver-core-module-fix.patch no longer required
2004-05-13 13:42 ` 2.6.6-mm2 Paolo Ornati
@ 2004-05-13 14:01 ` Adrian Bunk
2004-05-13 14:36 ` Paolo Ornati
0 siblings, 1 reply; 54+ messages in thread
From: Adrian Bunk @ 2004-05-13 14:01 UTC (permalink / raw)
To: Paolo Ornati; +Cc: Andrew Morton, linux-kernel
On Thu, May 13, 2004 at 03:42:23PM +0200, Paolo Ornati wrote:
> On Thursday 13 May 2004 12:27, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6
> >-mm2/
>
> CC kernel/module.o
> kernel/module.c:730: error: redefinition of `add_attribute'
> kernel/module.c:382: error: `add_attribute' previously defined here
> kernel/module.c:382: warning: `add_attribute' defined but not used
> make[1]: *** [kernel/module.o] Error 1
> make: *** [kernel] Error 2
bk-driver-core-module-fix.patch is no longer required (a different fix
is in bk-driver-core.patch).
Simply _revert_ the patch below.
> bye
>
> --
> Paolo Ornati
cu
Adrian
--- 25/kernel/module.c~bk-driver-core-module-fix 2004-05-10 04:47:54.697175440 -0700
+++ 25-akpm/kernel/module.c 2004-05-10 04:47:54.701174832 -0700
@@ -726,6 +726,12 @@ static inline int sysfs_unload_setup(str
{
return 0;
}
+
+static int add_attribute(struct module *mod, struct kernel_param *kp)
+{
+ return 0;
+}
+
#endif /* CONFIG_MODULE_UNLOAD */
#ifdef CONFIG_OBSOLETE_MODPARM
_
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2: bk-driver-core-module-fix.patch no longer required
2004-05-13 14:01 ` 2.6.6-mm2: bk-driver-core-module-fix.patch no longer required Adrian Bunk
@ 2004-05-13 14:36 ` Paolo Ornati
0 siblings, 0 replies; 54+ messages in thread
From: Paolo Ornati @ 2004-05-13 14:36 UTC (permalink / raw)
To: Adrian Bunk; +Cc: linux-kernel
On Thursday 13 May 2004 16:01, you wrote:
> On Thu, May 13, 2004 at 03:42:23PM +0200, Paolo Ornati wrote:
> >
> > CC kernel/module.o
> > kernel/module.c:730: error: redefinition of `add_attribute'
> > kernel/module.c:382: error: `add_attribute' previously defined here
> > kernel/module.c:382: warning: `add_attribute' defined but not used
> > make[1]: *** [kernel/module.o] Error 1
> > make: *** [kernel] Error 2
>
> bk-driver-core-module-fix.patch is no longer required (a different fix
> is in bk-driver-core.patch).
>
> Simply _revert_ the patch below.
OK
bye
--
Paolo Ornati
Linux v2.6.6
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
` (5 preceding siblings ...)
2004-05-13 13:42 ` 2.6.6-mm2 Paolo Ornati
@ 2004-05-13 15:07 ` Lorenzo Allegrucci
2004-05-13 18:55 ` 2.6.6-mm2 Andrew Morton
2004-05-14 17:48 ` 2.6.6-mm2 R. J. Wysocki
2004-05-14 23:56 ` 2.6.6-mm2 Joseph Fannin
8 siblings, 1 reply; 54+ messages in thread
From: Lorenzo Allegrucci @ 2004-05-13 15:07 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Thursday 13 May 2004 12:27, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6-m
>m2/
make[2]: *** No rule to make target `fs/xfs/support/qsort.s', needed by
`fs/xfs/support/qsort.o'. Stop.
make[1]: *** [fs/xfs] Error 2
make: *** [fs] Error 2
--
Lorenzo
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 15:07 ` 2.6.6-mm2 Lorenzo Allegrucci
@ 2004-05-13 18:55 ` Andrew Morton
2004-05-13 19:41 ` 2.6.6-mm2 Lorenzo Allegrucci
0 siblings, 1 reply; 54+ messages in thread
From: Andrew Morton @ 2004-05-13 18:55 UTC (permalink / raw)
To: Lorenzo Allegrucci; +Cc: linux-kernel
Lorenzo Allegrucci <l_allegrucci@despammed.com> wrote:
>
> On Thursday 13 May 2004 12:27, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6-m
> >m2/
>
> make[2]: *** No rule to make target `fs/xfs/support/qsort.s', needed by
> `fs/xfs/support/qsort.o'. Stop.
That's odd.
diff -puN fs/xfs/Makefile~have-xfs-use-kernel-provided-qsort-fix fs/xfs/Makefile
--- 25/fs/xfs/Makefile~have-xfs-use-kernel-provided-qsort-fix 2004-05-13 11:54:24.869488456 -0700
+++ 25-akpm/fs/xfs/Makefile 2004-05-13 11:54:28.218979256 -0700
@@ -142,7 +142,6 @@ xfs-y += $(addprefix linux/, \
xfs-y += $(addprefix support/, \
debug.o \
move.o \
- qsort.o \
uuid.o)
xfs-$(CONFIG_XFS_TRACE) += support/ktrace.o
_
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 18:55 ` 2.6.6-mm2 Andrew Morton
@ 2004-05-13 19:41 ` Lorenzo Allegrucci
0 siblings, 0 replies; 54+ messages in thread
From: Lorenzo Allegrucci @ 2004-05-13 19:41 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Thursday 13 May 2004 20:55, Andrew Morton wrote:
> Lorenzo Allegrucci <l_allegrucci@despammed.com> wrote:
> > On Thursday 13 May 2004 12:27, Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.
> > >6.6-m m2/
> >
> > make[2]: *** No rule to make target `fs/xfs/support/qsort.s', needed by
> > `fs/xfs/support/qsort.o'. Stop.
>
> That's odd.
>
> diff -puN fs/xfs/Makefile~have-xfs-use-kernel-provided-qsort-fix
> fs/xfs/Makefile ---
> 25/fs/xfs/Makefile~have-xfs-use-kernel-provided-qsort-fix 2004-05-13
> 11:54:24.869488456 -0700 +++ 25-akpm/fs/xfs/Makefile 2004-05-13
> 11:54:28.218979256 -0700
> @@ -142,7 +142,6 @@ xfs-y += $(addprefix linux/, \
> xfs-y += $(addprefix support/, \
> debug.o \
> move.o \
> - qsort.o \
> uuid.o)
>
> xfs-$(CONFIG_XFS_TRACE) += support/ktrace.o
>
> _
>
>
Fixed, thanks.
--
Lorenzo
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.6-mm2
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
` (6 preceding siblings ...)
2004-05-13 15:07 ` 2.6.6-mm2 Lorenzo Allegrucci
@ 2004-05-14 17:48 ` R. J. Wysocki
2004-05-14 17:47 ` 2.6.6-mm2 Christoph Hellwig
2004-05-14 23:56 ` 2.6.6-mm2 Joseph Fannin
8 siblings, 1 reply; 54+ messages in thread
From: R. J. Wysocki @ 2004-05-14 17:48 UTC (permalink / raw)
To: Andrew Morton, linux-kernel
On Thursday 13 of May 2004 12:27, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6-m
>m2/
>
>
> - Lots of VM changes - fixes from Andrea and generally moving things closer
> to the -aa tree.
>
> - The x86_64 gcc-3.3.3 shipped with SuSE 9.1 miscompiles the post-2.6.6 CPU
> scheduler changes, resulting in lockups after several minutes of heavy
> load. Hence this kernel refuses to build on gcc-3.3.x. Please use
> gcc-3.4.0 if you're on x86_64.
Oh well. And every distribution for x86_64 that I know ships with the
gcc-3.3.x (sigh).
Can you please tell me where I can get the gcc-3.4 in RPM for SuSE 9.0 or
FC2T3/AMD64? I've bad memories of trying to bulid the gcc myself from the
sources ...
Yours,
RJW
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: 2.6.6-mm2
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
` (7 preceding siblings ...)
2004-05-14 17:48 ` 2.6.6-mm2 R. J. Wysocki
@ 2004-05-14 23:56 ` Joseph Fannin
2004-05-14 23:58 ` 2.6.6-mm2 Chris Wright
8 siblings, 1 reply; 54+ messages in thread
From: Joseph Fannin @ 2004-05-14 23:56 UTC (permalink / raw)
To: Andrew Morton, Chris Wright; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On Thu, May 13, 2004 at 03:27:36AM -0700, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6-mm2/
> +rlim-add-rlimit-entry-for-posix-mqueue-allocation.patch
The above patch includes linux/mqueue.h from
arch/*/kernel/init_task.c for each arch. Building the kernel fails on
ppc because ppc doesn't have an init_task.c; the setting of
CONFIG_POSIX_MQUEUE doesn't matter. I added the include to
arch/ppc/kernel/process.c and the resulting kernel boots ok, but this
is probably not the correct place to put it.
cris and m68k don't have an init_task.c either.
--
Joseph Fannin
jhf@rivenstone.net
"Bull in pure form is rare; there is usually some contamination by data."
-- William G. Perry Jr.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 54+ messages in thread