Actually, looks like it might still be preempt...
Kernel BUG at kernel/rt.c:2193
invalid operand: 0000 [1] PREEMPT
CPU 0
Modules linked in: rt2500pci rt2x00core ieee80211 ieee80211_crypt
yenta_socket rsrc_nonstatic pcmcia pcmcia_core firmware_class 8139too
mii usbhid ohci_hcd psmouse usbcore
Pid: 8320, comm: ifconfig Not tainted 2.6.15-rc7-rt1 #1
RIP: 0010:[<ffffffff80144bb2>] <ffffffff80144bb2>{rt_downgrade_write+0}
RSP: 0018:ffff810028b01cf0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff810028a96a68 RCX: ffff8100288e6200
RDX: ffff810028b00000 RSI: 000000000000000b RDI: ffff810028a96a68
RBP: ffff810028a96ac8 R08: 0000000000000006 R09: 0000000000000282
R10: ffff81002df4d300 R11: ffff81002b6e5ec0 R12: 00000000000003ff
R13: ffff810028a96a68 R14: 0000000000000000 R15: 0000000000000000
FS: 00002aaaaade3b00(0000) GS:ffffffff803fc800(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002aaaaacb864c CR3: 00000000289b1000 CR4: 00000000000006e0
Process ifconfig (pid: 8320, threadinfo ffff810028b00000, task
ffff810028a987c0)Stack: ffffffff880700a6 ffff810028a96ac8
ffff810028a96624 ffff810028a96b88
ffffffff88071c91 ffff81002df4d300 ffff810028a96a68 0000000000000000
0000000000000000 ffff810028a96ac8
Call Trace:<ffffffff880700a6>{:rt2x00core:rt2x00_update_config+69}
<ffffffff88071c91>{:rt2x00core:rt2x00_start_scan+773}
<ffffffff88072cbe>{:rt2x00core:rt2x00_link_up+103}
<ffffffff88075c81>{:rt2x00core:rt2x00_open+120}
<ffffffff80293153>{dev_open+51} <ffffffff80294119>{dev_change_flags+88}
<ffffffff802c8b23>{devinet_ioctl+645} <ffffffff802c9c3e>{inet_ioctl+124}
<ffffffff8028aee4>{sock_ioctl+0} <ffffffff8028b0b9>{sock_ioctl+469}
<ffffffff8017ec41>{do_ioctl+41} <ffffffff8017eefb>{vfs_ioctl+628}
<ffffffff8017ef65>{sys_ioctl+89} <ffffffff8010e812>{system_call+126}
Code: 0f 0b 68 ed 6c 2f 80 c2 91 08 c3 0f ae f0 31 c0 48 83 7f 20
RIP <ffffffff80144bb2>{rt_downgrade_write+0} RSP <ffff810028b01cf0>
Is this an issue with realtime or the driver?
