Red Hat Bugzilla – Bug 459311
Macbook Pro (4,1) + ndiswrapper + latest NetworkManager = CPU#0 stuck for 61s!
Last modified: 2008-08-18 10:01:42 EDT
Description of problem:
Connecting to a wireless network using the latest NetworkManager on Fedora 9 on my Macbook Pro (4,1). If I turn off NetworkManager, and use system-config-network, the computer doesn't freeze.
Version-Release number of selected component (if applicable):
[root@localhost tmp]# rpm -qa | grep NetworkManager
How reproducible: It happens every time, sometimes it is almost instant, sometimes it takes a bit longer, like a minute or two.
Steps to Reproduce:
1. NetworkManager connects to SID
2. Start 'surfing'
3. Machine freezes
Machine locks up.
Machine doesn't lock up. :-)
part of my message log is attached.
Created attachment 314425 [details]
scrubbed message log
@redhat.com? You really should know better.
There is absolutely nothing we can do about ndiswrapper. The Fedora kernel is not even capable of running with stability with ndiswrapper because you need 16KB stacks while Fedora kernel uses 4KB stacks for performance.
email@example.com you should read my post better. The problem is not ndiswrapper, it is NetworkManager, if the problem was ndiswrapper the dirvers wouldn't work even if I used system-config-network. So, instead of giving me attitude, why not just try to be helpful. If the bug won't be fixed, that's fine... just a shame that we have to keep shipping buggy software.
I want to go on record and say a couple of things here:
1. I want to apologize for the 'buggy software' remark, software is complex, and virtually always there's going to be bugs on them with that said.
2. It's really hard not to get mad with remarks like:
"@redhat.com? You really should know better."
Does everyone who work at red hat a kernel developer? It's very frustrating, because I know a lot of people in the Fedora community thrive to get people participating with the development with the OS with documentation, bug filing, packaging, development, etc...
Yet, I find myself asking if I will ever file a bug at bugzilla again due to the fact that I am expected to know the ins and outs of the operating system just because I work at redhat.com. Yes, I work there, yet that doesn't mean I know everything there is to know about the ins and outs of the operating system.
I will leave at that, I just hope that anyone who gets this email will be able to reflect upon how well are we treating Fedora users who are taking their personal time to contribute independent of where they work at.
If at any point your machine hangs or panics when using NetworkManager, that is a kernel or driver problem. It's not NetworkManager's problem. The kernel/driver should never panic or hang when asked to do anything. NM uses wpa_supplicant to drive the wifi card, and the supplicant does a lot of things differently than system-config-network/iwconfig do precisely becuase it's more capable. But that still means that if something panics or hangs, the kernel or driver are at fault here.
And because it's ndiswrapper, there's absolutely nothing we can do, because the driver is actually a closed-source Windows NDIS blob that we cannot fix :(
I feel your pain though, because there isn't a driver for the newer broadcom parts yet, and that sucks.
firstname.lastname@example.org, thank you for you explanation. sounds good.