id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,blockedby,blocking,platform 5532,Complete system freeze when using atheroswifi with an SMP system.,jstressman,colin,"I was getting a number of complete system locks while trying to install the BeZillaBrowser package, or just in general after a variable amount of time (sometimes immediately when reaching the desktop, or maybe after 10 minutes etc). So I began testing and removed the atheroswifi driver. This ""fixed the problem"" and I ran the computer for about an hour with no problems. So then I restored the driver and did some research into whether or not anyone had had any problems with the BSD drivers themselves, where I found that this seemed to be a known LOR (lock order reversal) problem and the email recommended to disable SMP as a workaround until the problem was fixed. http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2009-10/msg00495.html So I disabled SMP and was able to surf the net, chat, etc... for 17 hours with no problems before I rebooted the system myself. I re-enabled SMP for testing a bit ago and was able to freeze the system completely within less than 2 minutes of using the internet. This is a hard freeze where the system instantly becomes completely unresponsive. No keyboard shortcuts work etc. (No alt+sysreq+d for KDL, no ctrl+alt+del etc) You have to press the power button on the computer itself to shut off the machine. Here are some of the other links I was looking at that may be related: http://sources.zabbadoz.net/freebsd/lor.html http://sources.zabbadoz.net/freebsd/lor/42.html http://sources.zabbadoz.net/freebsd/lor/224.html http://sources.zabbadoz.net/freebsd/lor/170.html http://sources.zabbadoz.net/freebsd/lor/59.html I'm also attaching the output of listdev, and a few copies of the syslog from before the crash. (this is nightly build r35693 gcc4hybrid) ",bug,closed,normal,R1/beta2,Drivers/Network/atheroswifi,R1/Development,fixed,,,,,x86