Was the original issue fixed with the latest ndiswrapper? I don't want
to close out a bug if it still remains...
Thanks,
Richard Seguin
--
linux kernel socket deadlock (ndiswrapper?)
https://bugs.launchpad.net/bugs/227033
You received this bug notification because you are a member of Ubuntu
The issue was not solved by any version of ndiswrapper (also, the latest
in Hardy is newer than 1.52). I tried running ndiswrapper with a higher
debug setting, but because of the seeming randomness of the bug, the log
files filled and caused problems before the ndiswrapper bug manifested
itself,
This bug should possibly be closed - I wanted to move to 64-bit, where a
(possibly different) bug was causing a kernel panic for me (but
definitely related to the wireless card), so I've bought a more Linux-
compatible device, using neither ndiswrapper nor a Marvell chipset.
--
linux kernel
Did you try the debug parameter of ndiswrapper?
Also the output of 'ndiswrapper -v' and 'ndiswrapper -l' would be interesting.
Also, your problem might have been fixed in ndiswrapper 1.51:
http://sourceforge.net/project/shownotes.php?release_id=562382group_id=93482
Perhaps somewhere you can find
I'll give the latest ndiswrapper a try and report back when I can tell
if the bug still exists or not. Thanks =)
--
linux kernel socket deadlock (ndiswrapper?)
https://bugs.launchpad.net/bugs/227033
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: lspci -vvnn
http://launchpadlibrarian.net/14234248/lspci-vvnn.log
** Description changed:
The occurrence of this bug is seemingly random, but happens to me on
average once a day (but twice while writing this). Effectively, all of
my TCP connections do nothing, and
** Attachment added: dmesg
http://launchpadlibrarian.net/14234235/dmesg.log
--
linux kernel socket deadlock (ndiswrapper?)
https://bugs.launchpad.net/bugs/227033
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Marked incomplete pending more information...
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
linux kernel socket deadlock (ndiswrapper?)
https://bugs.launchpad.net/bugs/227033
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Is this a laptop or a desktop?
* Does this happen on a clean boot? (booting from scratch,
I haven't noticed any particular correlation between events and the bug
occurring, so there are no steps I know of which will definitely
reproduce this bug. I'll keep an eye out for any common factors.
This is a desktop machine, and as far as I can tell I've only had this
problem since using
Thank you for your help
--
linux kernel socket deadlock (ndiswrapper?)
https://bugs.launchpad.net/bugs/227033
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
11 matches
Mail list logo
