Hello, All; I recently CVSUP'd from 5.4 to 6.0BETA1. I used the instructions in UPDATING to build/install world and used GENERIC unmodified to build the kernel. The whole procedure went without a single hitch. My question concerns the meaning of a debug message which appears when I remove my Wi-Fi card (which by the way works fine...I'm using it to send this mail). Here's the output from "dmesg" when I insert the card (just for reference); wi0: <SMC SMC2532W-B EliteConnect Wireless Adapter> at port 0x100-0x13f irq 11 function 0 config 1 on pccard1 wi0: using RF:PRISM2.5 MAC:ISL3873 wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) wi0: Ethernet address: 00:04:e2:80:34:be When I remove the card I get the following; taskqueue_drain with the following non-sleepable locks held: exclusive sleep mutex wi0 (network driver) r = 0 (0xc2416afc) locked @ /usr/src/sys/dev/wi/if_wi.c:845 KDB: stack backtrace: kdb_backtrace(1,c1af9250,c1af9000,c1989b80,d44bfc2c) at kdb_backtrace+0x29 witness_warn(5,0,c0854d21,c1af9000,c1af9000) at witness_warn+0x18e taskqueue_drain(c1989b80,c1af9250,c1af9000,c1af9000,c1af9000) at taskqueue_drain+0x1a if_detach(c1af9000,c1af9000) at if_detach+0x1a ether_ifdetach(c1af9000,0,c2416000,d44bfc94,c05debfc) at ether_ifdetach+0x28 ieee80211_ifdetach(c2416004,c1af9000,c1af9000,0,c1c51880) at ieee80211_ifdetach+0x50 wi_detach(c1c51880) at wi_detach+0x64 device_detach(c1c51880) at device_detach+0x70 pccard_detach_card(c1aaa600) at pccard_detach_card+0x41 exca_removal(c1a6e804) at exca_removal+0x46 cbb_removal(c1a6e800) at cbb_removal+0x2c cbb_event_thread(c1a6e800,d44bfd38,c1a6e800,c0579df0,0) at cbb_event_thread+0x9a fork_exit(c0579df0,c1a6e800,d44bfd38) at fork_exit+0xa0 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd44bfd6c, ebp = 0 --- wi0: detached I don't read debug messages yet, and am wondering if this is a problem, is it just because WITNESS and INVARIANTS are enabled, or if it's normal but never seen in a non-debug kernel. I get a similar message when I shutdown, having to do mostly with ACPI, but since that's been buggy on this machine (Dell Latitude C600), I almost expected that. Thanks in advance-- Patrick Bowen