On Sun, Sep 11, 2011 at 10:10 AM, Bill Allaire <open...@bogoflop.com> wrote:
> TP-Link (TLWN812N 300Mbps) USB device. What I found really surprising was
> that unplugging the device locked up the OS.
>
> Due to message:
> Sep 7 15:19:08 geeky /bsd: athn0 at uhub0
> Sep 7 15:19:08 geeky /bsd: port 1 "ATHEROS UB95" rev 2.00/2.02 addr 3
> Sep 7 15:19:08 geeky /bsd: athn0: failed loadfirmware of file
> athn-ar7010-11 (error 2)
> Sep 7 15:19:08 geeky /bsd: athn0: could not load firmware
>
> I downloaded athn-firmware-1.1.tgz and extracted those files into
> /etc/firmware. That file contained:
> firmware/athn-ar7010
> firmware/athn-ar7010-11
> firmware/athn-ar9271
>
>
> That led to the following when plugged in:
>
> Sep 11 10:30:05 geeky /bsd: port 1 "ATHEROS UB95" rev 2.00/2.02 addr 3
> Sep 11 10:30:07 geeky /bsd: athn0: bad ROM checksum 0x2c17
> Sep 11 10:30:07 geeky /bsd: athn0: could not read ROM
> Sep 11 10:30:07 geeky /bsd: athn0: could not attach chip
>
>
> When unplugged:
>
> uvm_fault(0xd0a31aa0, 0x0, 0, 3) -> e
> kernel: page fault trap, code=0
> Stopped at ieee80211_ifdetach+0x3e: movl %edx,0(%eax)
> ddb{1}> (lost keyboard response at this point)
You in X-Windows, I assume.
> I did try setting "sysctl ddb.console=1" before unplugging the device again
> but:
> sysctl: ddb.console: Operation not permitted
You can't change that setting at run time. You need to set it in your
/etc/sysctl.conf file and reboot the system.
> I'm not sure how else I can get a trace, ps, show registers, etc...
Try your experiment either from the console or set up a serial console
for the machine.
--patrick
