On Thu, Jul 24, 2008 at 5:37 PM, Herton Ronaldo Krzesinski <herton@xxxxxxxxxxxxxxx> wrote: <sniped> > For me it works with or without the patch, may be there is some condition that > triggers the bug that I'm not hitting. But I still have the same problem that > I previously reported about power management, but the bug isn't on that > commit and doesn't have to do with power management, later I found that an > ifconfig <interface> down + ifconfig <interface> up works too, it's something > on userspace that triggers the bug (shortly after I modprobe the module, udev > calls automatically scripts to configure the interface, if I disable this in > udev and run commands manually interface works here, I'll see if I catch this > other problem, may be a race in initialization code somewhere). Some kind of race condition is quite likely. I think I have seen two instances of dhclient being launched by udevd quite routinely; and I seems to notice that I have to do ifconfig up, iwconfig etc in fairly quick succession and in some specific order to get it to work, and sometimes killing off udevd launched dhclient and do my own. I notice that dhclient seems to want to ifconfig the interface down if it can't get an ip address (this seems extra to me - there are occasions when I want to have a bare interface without address up?). So what's the verdict so far? I am tracking fedora 9 koji test kernels mostly, and something between kernel-2.6.25.11-92.fc9 and kernel-2.6.25.11-93.fc9 broke rtl8187. I just checked out the source rpm itself, and the difference is just in the wireless area, and supposedly one of http://marc.info/?l=linux-wireless&m=121606436000705&w=2 . I think this is what most agreed - i.e. nobody is getting much success with latest wireless with rtl8187? Both the power management hook and the tx seq no removal are among those. the iwconfig power off doesn't do it for me (it seems to default to off anyway?), but I had one success with the tx seq fix having quite substantial traffic - 50MB? - going through before I reboot or otherwise lose the connectivity in some non-problematic way and didn't get it back ever. The journey continues... Hin-Tak -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
