Re: [DSCAPE] rate_control needs some form of reference counting

2006-08-01 Thread Jiri Benc
On Tue, 1 Aug 2006 17:16:32 +0200, Karol Lewandowski wrote: > Without that ieee80211_register_hw was returning value from previous > check: I missed that. Thanks for spotting this. > This fixes that oops. Problem remains, though. I suppose that oops > would happen anyway if someone would do: >

Re: [DSCAPE] rate_control needs some form of reference counting

2006-08-01 Thread Karol Lewandowski
On Tue, Aug 01, 2006 at 04:10:23PM +0200, Jiri Benc wrote: > On Sat, 29 Jul 2006 23:56:45 +0200, Karol Lewandowski wrote: > The fix is not easy. In fact, it's as hard as to fix it by implementing > a feature that allows to use different rate control algorithm for each > device. Given the fact the

Re: [DSCAPE] rate_control needs some form of reference counting

2006-08-01 Thread Jiri Benc
On Sat, 29 Jul 2006 23:56:45 +0200, Karol Lewandowski wrote: > I'm getting reproductible oops when removing rt2500pci module > (which uses devicescape ieee802.11 stack): Thanks for the report and nice description how to reproduce the problem. The fix is not easy. In fact, it's as hard as to fix i

[DSCAPE] rate_control needs some form of reference counting

2006-07-29 Thread Karol Lewandowski
Hi, I'm getting reproductible oops when removing rt2500pci module (which uses devicescape ieee802.11 stack): # modprobe rt2500pci Loading module: rt2500pci - CVS (N/A) by http://rt2x00.serialmonkey.com. ACPI: PCI Interrupt :03:00.0[A] -> GSI 21 (level, low) -> IRQ 18 wmaster0: Failed to s