Return to Answer

As per my comments on the question (I'll provide a link, since you didn't) [Note all comments on the question have since been deleted, and the question itself edited to remove the "research" link under discussion, but it is included here below], in the original context that research is on the same level as this:

• https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=142481 This does indeed include the phrase "lock up" and and bluetooth apparently turns out to be the culprit, but what's interesting about it is bluetooth was not mentioned in that person's initial report of an issue. It's mentioned in the solution and what's more, exactly how to disable it is also mentioned. So if you already found a solution in the first link of your research, why are you asking about it?

• https://github.com/raspberrypi/linux Nothing to do with any of this but may indeed be indicative of my google chrome browser history since I'm there at least a few times a week. However, it is also perhaps because of #3...

• https://github.com/raspberrypi/linux/issues/1360 Is indeed again a connection between "rpi3 lockup" and "bluetooth", but there's another common connection to the first hit: The use of PS3 controllers! Since they were posted a week apart, and the person who posted #1 found their solution the next day, very likely it was because of this. But you do not mention PS3 controllers in your question...

• Raspbian migration from Raspberry Pi 2 to Raspberry Pi 3 A question from here where the solution appears to have nothing to do with bluetooth or wifi.

• http://www.runeaudio.com/forum/the-raspberry-pi-3-t3256-80.html Completely tangential.

As per my comments on the question (I'll provide a link, since you didn't) [Note all comments on the question have since been deleted, and the question itself edited to remove the "research" link under discussion, but it is included here below], in the original context that research is on the same level as this:

• https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=142481 This does indeed include the phrase "lock up" and and bluetooth apparently turns out to be the culprit, but what's interesting about it is bluetooth was not mentioned in that person's initial report of an issue. It's mentioned in the solution and what's more, exactly how to disable it is also mentioned. So if you already found a solution in the first link of your research, why are you asking about it?

• https://github.com/raspberrypi/linux Nothing to do with any of this but may indeed be indicative of my google chrome browser history since I'm there at least a few times a week. However, it is also perhaps because of #3...

• https://github.com/raspberrypi/linux/issues/1360 Is indeed again a connection between "rpi3 lockup" and "bluetooth", but there's another common connection to the first hit: The use of PS3 controllers! Since they were posted a week apart, and the person who posted #1 found their solution the next day, very likely it was because of this. But you do not mention PS3 controllers in your question...

• Raspbian migration from Raspberry Pi 2 to Raspberry Pi 3 A question from here where the solution appears to have nothing to do with bluetooth or wifi.

• http://www.runeaudio.com/forum/the-raspberry-pi-3-t3256-80.html Completely tangential.

As per my comments on the question (I'll provide a link, since you didn't), that "research" is on the same level as this:

As per my comments on the question (I'll provide a link, since you didn't) [Note all comments on the question have since been deleted, and the question itself edited to remove the "research" link under discussion, but it is included here below], in the original context that research is on the same level as this:

In any case it does not explain, if you genuinely "visited the relevant links", you would not link to them directly. Unless that would complicate your question...further evidence that the link, like this question, was an intentional rhetorical ploy.

Your misinterpretation is then born out in further comments on the question -- which, again, you presumably did not link to because you are trying to paint a different picture than the background reality presents.

In any case it does not explain, if you genuinely "visited the relevant links", why you would not link to them directly. Unless, of course, if that would complicate your claim...further evidence that the link, like this question, was an intentional rhetorical ploy.

Your misinterpretation is then born out in further comments on the question -- which, again, you presumably did not link to because you are trying to paint a different picture than the background reality presents and you know it. I.e. You are playing games. Please play them somewhere else in the future.