Hi,
2007/6/6, Christoph Lameter <[EMAIL PROTECTED]>:
Note that the corruption seems to have its cause in a decrement done at
offset 16 into the object pointing to the refcount in struct hci_dev. So
it looks like the refcount was decremented after the object was freed.
sysfs related?
I
On Tue, 5 Jun 2007, Andrew Morton wrote:
> Could perhaps be due to bluetooth-postpone-hci_dev-unregistration.patch,
> but I don't see how. (But that patch looks a bit dodgy wrt module
> unload so I think I'll drop it).
It is perfectly fine to drop this one, as the issue it was trying to solve
On Tue, 5 Jun 2007, Andrew Morton wrote:
Could perhaps be due to bluetooth-postpone-hci_dev-unregistration.patch,
but I don't see how. (But that patch looks a bit dodgy wrt module
unload so I think I'll drop it).
It is perfectly fine to drop this one, as the issue it was trying to solve
Hi,
2007/6/6, Christoph Lameter [EMAIL PROTECTED]:
Note that the corruption seems to have its cause in a decrement done at
offset 16 into the object pointing to the refcount in struct hci_dev. So
it looks like the refcount was decremented after the object was freed.
sysfs related?
I tested
Hi,
2007/6/6, Christoph Lameter <[EMAIL PROTECTED]>:
Note that the corruption seems to have its cause in a decrement done at
offset 16 into the object pointing to the refcount in struct hci_dev. So
it looks like the refcount was decremented after the object was freed.
sysfs related?
I noticed
Note that the corruption seems to have its cause in a decrement done at
offset 16 into the object pointing to the refcount in struct hci_dev. So
it looks like the refcount was decremented after the object was freed.
sysfs related?
-
To unsubscribe from this list: send the line "unsubscribe
On Wed, 6 Jun 2007 03:27:31 + "young dave" <[EMAIL PROTECTED]> wrote:
> Hi,
> > Are you able to reproduce this in 2.6.22-rc4?
>
> The bug seems doesn't exist in 2.6.22-rc4, I have tested it, the
> unpluging can't produce kernel bug message.
>
OK, thanks. I'll drop
Hi,
Are you able to reproduce this in 2.6.22-rc4?
The bug seems doesn't exist in 2.6.22-rc4, I have tested it, the
unpluging can't produce kernel bug message.
Regards
dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Hi,
Are you able to reproduce this in 2.6.22-rc4?
The kmalloc in dmesg is in skbuff.c:pskb_expand_head, I will try
2.6.22-rc4 ASAP.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Wed, 6 Jun 2007 01:56:01 + "young dave" <[EMAIL PROTECTED]> wrote:
> Hi,
> when I remove the usb bluetooth adapter , the kernel reporting bug:
>
> /* this two line is printk message I printed in net/bluetooth/hci_core.c */
>
> #before free dev: c3758430
> #after free dev
>
>
Hi,
when I remove the usb bluetooth adapter , the kernel reporting bug:
/* this two line is printk message I printed in net/bluetooth/hci_core.c */
#before free dev: c3758430
#after free dev
=
BUG kmalloc-1024: Poison
Hi,
when I remove the usb bluetooth adapter , the kernel reporting bug:
/* this two line is printk message I printed in net/bluetooth/hci_core.c */
#before free dev: c3758430
#after free dev
=
BUG kmalloc-1024: Poison
On Wed, 6 Jun 2007 01:56:01 + young dave [EMAIL PROTECTED] wrote:
Hi,
when I remove the usb bluetooth adapter , the kernel reporting bug:
/* this two line is printk message I printed in net/bluetooth/hci_core.c */
#before free dev: c3758430
#after free dev
Hi,
Are you able to reproduce this in 2.6.22-rc4?
The kmalloc in dmesg is in skbuff.c:pskb_expand_head, I will try
2.6.22-rc4 ASAP.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hi,
Are you able to reproduce this in 2.6.22-rc4?
The bug seems doesn't exist in 2.6.22-rc4, I have tested it, the
unpluging can't produce kernel bug message.
Regards
dave
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
On Wed, 6 Jun 2007 03:27:31 + young dave [EMAIL PROTECTED] wrote:
Hi,
Are you able to reproduce this in 2.6.22-rc4?
The bug seems doesn't exist in 2.6.22-rc4, I have tested it, the
unpluging can't produce kernel bug message.
OK, thanks. I'll drop
Note that the corruption seems to have its cause in a decrement done at
offset 16 into the object pointing to the refcount in struct hci_dev. So
it looks like the refcount was decremented after the object was freed.
sysfs related?
-
To unsubscribe from this list: send the line unsubscribe
Hi,
2007/6/6, Christoph Lameter [EMAIL PROTECTED]:
Note that the corruption seems to have its cause in a decrement done at
offset 16 into the object pointing to the refcount in struct hci_dev. So
it looks like the refcount was decremented after the object was freed.
sysfs related?
I noticed
18 matches
Mail list logo
