I have turned off Bluetooth, why are there interrupts about bluetooth hostwake?

I found that the computer can’t balance the interrupts well, especially. It is when the temperature is high.

cat /proc/interrupts

391: 53517210 0 0 0 0 0 0 tegra-gpio 192 Edge bluetooth hostwake

Hi,

Could you share your usecase here? Sounds like a problem that would affect system.

I use xavier to run a Location algorithm for PCL.

During the use of packet loss, I found that the first cpu is always full when the situation occurs, then I found that the interrupt is very high, and the interrupt only occurs in the first CPU.

I found xavier not irqbalace, I compiled and installed with source code about irqbalance.
Something changed, but when I tried again, I found the problem with Bluetooth.

I did the following to turn off Bluetooth:
sudo systemctl mask bluetooth.service
sudo apt-get remove indicator-bluetooth

When I am ready, the Bluetooth interrupt rises again.

Hi,

There is no bluetooth hardware on xavier so I don’t know why you have bluetooth hostwake here.

Is this pure devkit w/o any peripheral on device?

Xavier has two peripheral,One is the velodyne, the other is connected to the switch.

Does velodyne have a bluetooth function?

NO

What is the interface of velodyne and that switch…?
Are they both on xavier devkit?

Are you able to share the method to reproduce this problem?

Run a cpu-type calculation program, the above problem may occur when the cpu temperature reaches 60 degrees or more.

Temperature is viewed by command ./tegrastats

I am not sure what will happen because the situation on the spot is more complicated.

Thanks. We will try to repro it on our side.

We tried to run some cpu stress test and push the temperature to 70C. Unfortunately, we didn’t repro your issue.
The interrupt from bluetooth hostwake is always 0.

It looks like there are something else that causes the problem. Could you try to narrow down it?

Thank you!
Back to the company, I will continue to test, and notify you if there are new discoveries.

Thank you!
Back to the company, I will continue to test, and notify you if there are new discoveries.

[quote]

I did the following to turn off Bluetooth:
sudo systemctl mask bluetooth.service
sudo apt-get remove indicator-bluetooth
/quote]

This doesn’t turn off the kernel level drivers.

Assuming that bluetooth is loaded as a module (and not compiled statically into the kernel) you can ensure that bluetooth doesn’t do anything by masking the module in, for example, /etc/modprobe.d/blacklist.conf

I have added Bluetooth to the blacklist before.

for example, /etc/modprobe.d/blacklist.conf
add

disable bluetooth

blacklist bluetooth

Here is my data today
391: 999830569 0 0 0 0 0 0 0 tegra-gpio 192 Edge bluetooth hostwake

How do you resolved this problem?
I met the same problem with my xavier. Almost each time power on the xavier, run cat /proc/interrupts , the interrupt times of “tegra-gpio bluetooth hostwake” added more and more faster. and the hi load of cpu0 grows up to 100% in about 10 minutes.

Run the command:modprobe -r bluedroid_pm, the bluetooth hostwake interrupt can be removed.

Thanks, it works.

Hi,

I notice only some forum users are able to hit this issue.

To debug, could you try to restore the driver back and modify the pinmux setting of TEGRA194_MAIN_GPIO(Y, 0) with Int PU enabled?

You need to download the pinmux spreadsheet from download center and search for PY.00. Modify the init state to PU and generate new pinmux cfg.

Our developer also wants to know below result from you when you hit the error.

->dump of register GPIO_Y_ENABLE_CONFIG_00_0 ( 0x02212200)

Please kindly share the result.