« Return to Thread: BUG: warning at lib/kref.c:32/kref_get() on with 0.16.4 on 2.6.18-6-686
Re: BUG: warning at lib/kref.c:32/kref_get() on with 0.16.4 on 2.6.18-6-686
by Nicolas Boullis
::
Rate this Message:
Hi,
On Fri, Aug 22, 2008 at 11:45:01AM -0500, Munir Nassar wrote:
> I have built the em8300 modules from lenny (0.16.4) on a debian etch
> system, linux-2.6.18-6-686 kernel.
>
> when i load the resulting em8300 and adv717x modules i get:
>
> em8300: EM8300 8300 (rev 2) bus: 1, devfn: 72, irq: 11, memory: 0xe6000000.
> em8300: mapped-memory at 0xf8e80000
> em8300: using MTRR
> em8300_main.o: Chip revision: 2
> BUG: warning at lib/kref.c:32/kref_get()
> [<c01b8887>] kref_get+0x24/0x2d
> [<c01b7eee>] kobject_get+0xf/0x13
> [<c018f1f3>] sysfs_create_link+0xa2/0xf3
> [<f8b87408>] em8300_i2c_reg+0x28d/0x2c9 [em8300]
> [<c01b87e2>] kobject_uevent+0x397/0x3b9
> [<f89b60d9>] i2c_attach_client+0x62/0xd2 [i2c_core]
> [<f89fd0d8>] eeprom_detect+0xaa/0x131 [eeprom]
> [<f89b5859>] i2c_probe_address+0x8d/0x99 [i2c_core]
> [<f89b599c>] i2c_probe+0x137/0x144 [i2c_core]
> [<f89fd02e>] eeprom_detect+0x0/0x131 [eeprom]
> [<f89fd02e>] eeprom_detect+0x0/0x131 [eeprom]
> [<f89b5eaa>] i2c_add_adapter+0x161/0x191 [i2c_core]
> [<c0210ee8>] __driver_attach+0x0/0x5d
> [<f8b86a44>] em8300_probe+0x285/0x354 [em8300]
> [<c01c1c14>] pci_device_probe+0x36/0x57
> [<c0210e49>] driver_probe_device+0x42/0x8b
> [<c0210f20>] __driver_attach+0x38/0x5d
> [<c021096a>] bus_for_each_dev+0x33/0x55
> [<c0210db3>] driver_attach+0x11/0x13
> [<c0210ee8>] __driver_attach+0x0/0x5d
> [<c0210683>] bus_add_driver+0x64/0xfd
> [<c01c1d50>] __pci_register_driver+0x47/0x63
> [<f8b2d086>] em8300_init+0x86/0xb8 [em8300]
> [<c01358f9>] sys_init_module+0x16c3/0x1846
> [<c0102c11>] sysenter_past_esp+0x56/0x79
(snip almost the same message again)
That sounds strange, and there certainly is here a bug to investigate...
Latest versions of the em8300 drivers are meant to support "recent" 2.4
and all 2.6 releases of linux.
As far as I understand it, this only is a warning. Is there any problem
besides this horrible (and somewhat frightening) message?
As far as I understand it, the kobj for the i2c slave chip (either
EEPROM or video encoder) is not completely initialized when
em8300_i2c_reg is called. It *might* be possible to change the adv717x
and bt865 drivers, but the problem also affects the eeprom driver, which
I don't control... I can't find a simple (read "not overly complex") way
to solve this problem... :-(
> Additionally unlike what is reported on
> http://dxr3.sourceforge.net/howto.html#detboard this is a Creative Labs
> DXR3 but uses the adv717x driver.
The online docs are somewhat incomplete and outdated. Volunteers are
welcome.
Cheers,
Nicolas
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel
On Fri, Aug 22, 2008 at 11:45:01AM -0500, Munir Nassar wrote:
> I have built the em8300 modules from lenny (0.16.4) on a debian etch
> system, linux-2.6.18-6-686 kernel.
>
> when i load the resulting em8300 and adv717x modules i get:
>
> em8300: EM8300 8300 (rev 2) bus: 1, devfn: 72, irq: 11, memory: 0xe6000000.
> em8300: mapped-memory at 0xf8e80000
> em8300: using MTRR
> em8300_main.o: Chip revision: 2
> BUG: warning at lib/kref.c:32/kref_get()
> [<c01b8887>] kref_get+0x24/0x2d
> [<c01b7eee>] kobject_get+0xf/0x13
> [<c018f1f3>] sysfs_create_link+0xa2/0xf3
> [<f8b87408>] em8300_i2c_reg+0x28d/0x2c9 [em8300]
> [<c01b87e2>] kobject_uevent+0x397/0x3b9
> [<f89b60d9>] i2c_attach_client+0x62/0xd2 [i2c_core]
> [<f89fd0d8>] eeprom_detect+0xaa/0x131 [eeprom]
> [<f89b5859>] i2c_probe_address+0x8d/0x99 [i2c_core]
> [<f89b599c>] i2c_probe+0x137/0x144 [i2c_core]
> [<f89fd02e>] eeprom_detect+0x0/0x131 [eeprom]
> [<f89fd02e>] eeprom_detect+0x0/0x131 [eeprom]
> [<f89b5eaa>] i2c_add_adapter+0x161/0x191 [i2c_core]
> [<c0210ee8>] __driver_attach+0x0/0x5d
> [<f8b86a44>] em8300_probe+0x285/0x354 [em8300]
> [<c01c1c14>] pci_device_probe+0x36/0x57
> [<c0210e49>] driver_probe_device+0x42/0x8b
> [<c0210f20>] __driver_attach+0x38/0x5d
> [<c021096a>] bus_for_each_dev+0x33/0x55
> [<c0210db3>] driver_attach+0x11/0x13
> [<c0210ee8>] __driver_attach+0x0/0x5d
> [<c0210683>] bus_add_driver+0x64/0xfd
> [<c01c1d50>] __pci_register_driver+0x47/0x63
> [<f8b2d086>] em8300_init+0x86/0xb8 [em8300]
> [<c01358f9>] sys_init_module+0x16c3/0x1846
> [<c0102c11>] sysenter_past_esp+0x56/0x79
(snip almost the same message again)
That sounds strange, and there certainly is here a bug to investigate...
Latest versions of the em8300 drivers are meant to support "recent" 2.4
and all 2.6 releases of linux.
As far as I understand it, this only is a warning. Is there any problem
besides this horrible (and somewhat frightening) message?
As far as I understand it, the kobj for the i2c slave chip (either
EEPROM or video encoder) is not completely initialized when
em8300_i2c_reg is called. It *might* be possible to change the adv717x
and bt865 drivers, but the problem also affects the eeprom driver, which
I don't control... I can't find a simple (read "not overly complex") way
to solve this problem... :-(
> Additionally unlike what is reported on
> http://dxr3.sourceforge.net/howto.html#detboard this is a Creative Labs
> DXR3 but uses the adv717x driver.
The online docs are somewhat incomplete and outdated. Volunteers are
welcome.
Cheers,
Nicolas
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel
« Return to Thread: BUG: warning at lib/kref.c:32/kref_get() on with 0.16.4 on 2.6.18-6-686
| Free embeddable forum powered by Nabble | Forum Help |
