Re: [PATCH] Fix 2.6.21 rfcomm lockups (2.6.21 regression)

2007-03-05 Thread Jiri Kosina
On Sun, 4 Mar 2007, Mark Lord wrote: > This patch prevents total system lockup when using rfcomm devices. I acknowledge that this patch fixes lockup for me too. When debugging this, I also came across a different bug (spotted by lockdep). Is the patch below applicable? From: Jiri Kosina

Re: [PATCH] Fix 2.6.21 rfcomm lockups (2.6.21 regression)

2007-03-05 Thread Cornelia Huck
On Sun, 04 Mar 2007 13:26:49 -0500, Mark Lord <[EMAIL PROTECTED]> wrote: > The simplest fix for this bug is to prevent sysfs_move_dir() > from self-deadlocking when (old_parent == new_parent). > > This patch prevents total system lockup when using rfcomm devices. > > Signed-off-by: Mark Lord

Re: [PATCH] Fix 2.6.21 rfcomm lockups (2.6.21 regression)

2007-03-05 Thread Cornelia Huck
On Sun, 04 Mar 2007 13:26:49 -0500, Mark Lord [EMAIL PROTECTED] wrote: The simplest fix for this bug is to prevent sysfs_move_dir() from self-deadlocking when (old_parent == new_parent). This patch prevents total system lockup when using rfcomm devices. Signed-off-by: Mark Lord [EMAIL

Re: [PATCH] Fix 2.6.21 rfcomm lockups (2.6.21 regression)

2007-03-05 Thread Jiri Kosina
On Sun, 4 Mar 2007, Mark Lord wrote: This patch prevents total system lockup when using rfcomm devices. I acknowledge that this patch fixes lockup for me too. When debugging this, I also came across a different bug (spotted by lockdep). Is the patch below applicable? From: Jiri Kosina

[PATCH] Fix 2.6.21 rfcomm lockups (2.6.21 regression)

2007-03-04 Thread Mark Lord
Mark Lord wrote: Any attempt to open/use a bluetooth rfcomm device locks up scheduling completely on my machine. Interrupts (ping, alt-sysrq) seem to be alive, but nothing else. This was working fine in 2.6.20, broken now in 2.6.21-rc2-git* Further info: Reverting this change (below) fixes

[PATCH] Fix 2.6.21 rfcomm lockups (2.6.21 regression)

2007-03-04 Thread Mark Lord
Mark Lord wrote: Any attempt to open/use a bluetooth rfcomm device locks up scheduling completely on my machine. Interrupts (ping, alt-sysrq) seem to be alive, but nothing else. This was working fine in 2.6.20, broken now in 2.6.21-rc2-git* Further info: Reverting this change (below) fixes