On Fri, Jul 20, 2007 at 06:32:21PM +0200, Michal Piotrowski wrote:
> Hi Greg,
>
> This looks like a sysfs bug
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/broken-out-2007-07-20-00-22/00003.jpg
>
> l *kernel_param_sysfs_setup+0x75
> 0xc13c0894 is in kernel_param_sysfs_setup (kernel/params.c:570).
> 565 mk->mod = THIS_MODULE;
> 566 kobj_set_kset_s(mk, module_subsys);
> 567 kobject_set_name(&mk->kobj, name);
> 568 kobject_init(&mk->kobj);
> 569 ret = kobject_add(&mk->kobj);
> 570 BUG_ON(ret < 0);
> 571 param_sysfs_setup(mk, kparam, num_params, name_skip);
> 572 kobject_uevent(&mk->kobj, KOBJ_ADD);
> 573 }
> 574
>
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/broken-out-2007-07-20-00-22/mm-config
What kernel version is this happening on? The -mm tree? Can you try
Linus's tree instead?
It looks like there was some needed information right before the first
stack dump, showing exactly what kobject was trying to be added that was
already present. Odds are this is a kernel parameter with the same name
as a duplicate one within the same module, but the trick is going to be
trying to figure out what module is causing this.
So it's not a sysfs bug, but rather a driver issue that this is
catching.
Does that make sense?
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
