You are not logged in.
In the interests of battery life, I never bothered getting the Bluetooth card in my laptop up-and-running until yesterday, when I decided it would be interesting to set up blueproximity (run commands, e.g. lock screen, based on whether a device is in range). To set this up, I installed bluez and started the bluetooth service. I configured blueproximity and messed around with it for an hour or so without problems, and then I rebooted to see how it would interact with logging in (would I get locked out immediately, etc.). It worked fine, so I wandered off, only to return to a kernel panic. My tired self neglected to take a photo of the error messages, but the word bluetooth was mentioned several times, and the only other recent change was switching to Firefox nightly, which didn't seem related. I repeated the scenario several more times, including once after a 24-hour delay, and it would consistently give up after 30-40 minutes of normal usage. (After the 24-hour delay, which included sleep, the screen just blanked instead of printing anything helpful.)
I've since taken bluetooth out of my rc.conf, and my machine has successfully run from boot for 2.5 hours, so I strongly suspect bluez and something (the kernel?) are not pleased with each other. I should also note that my machine doesn't ventilate super-well and tends to run hot, so there could be something going on there as well.
I'm running standard latest packages of everything; specifically, uname -a gives "Linux laptop618 3.4.4-2-ARCH #1 SMP PREEMPT Sun Jun 24 18:59:47 CEST 2012 x86_64 GNU/Linux".
Any suggestions on further things to look into? I can live without bluetooth, of course, but I would feel lame just giving up (this is a fancy way of saying that I'm actually just too lazy to remember to hit my lock screen key combo...).
Offline