I took a look at logs, the DSDT from AcpiTables and the toshiba_{bluetooth,acpi} code, and seems your machine for some reason gets repeated bluetooth status events after rfkill blocks bluetooth through toshiba_acpi, at least it looks like what's happening.
You can install it with sudo dpkg -i linux-image-2.6.38-8-generic_2.6.38-8.41~lp750428r1_i386.deb
Reboot, do the same test, and attach the resulting dmesg here. Although your original test is with 2.6.35, the newer kernel doesn't have any relevant changes in toshiba_acpi or toshiba_bluetooth, but I'm curious to see also if behaviour is different with it.
I took a look at logs, the DSDT from AcpiTables and the toshiba_ {bluetooth, acpi} code, and seems your machine for some reason gets repeated bluetooth status events after rfkill blocks bluetooth through toshiba_acpi, at least it looks like what's happening.
I'm curious to see what status toshiba_bluetooth is getting, please test the kernel I uploaded at http:// people. canonical. com/~herton/ lp750428/
You can install it with sudo dpkg -i linux-image- 2.6.38- 8-generic_ 2.6.38- 8.41~lp750428r1 _i386.deb
Reboot, do the same test, and attach the resulting dmesg here. Although your original test is with 2.6.35, the newer kernel doesn't have any relevant changes in toshiba_acpi or toshiba_bluetooth, but I'm curious to see also if behaviour is different with it.