[Prism54-devel] [Bug 46] New: trying to mount a NFS share wireless causes kernel crash

[bugzilla-daemon@mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=46

           Summary: trying to mount a NFS share wireless causes kernel crash
           Product: prim54
           Version: 1.0.2.2
          Platform: ia32
        OS/Version: Linux 2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Kernel patches
        AssignedTo: prism54-devel@prism54.org
        ReportedBy: johnzbesko@alum.mit.edu


I have been successful in connecting a Netgear WG511 to a Netgear router 
WGR614v2 using the 2.6.1 Mandrake 9.2 kernel source. I've added "route"s to 
connect the WLAN to the rest of my wired LAN. I can ssh into my server, 
192.168.1.251, from my laptop, 192.168.0.249.

However, when I attempt to mount a NFS share, things go screwy- the laptop hard 
freezes and the router is affected in that it seems to stop broadcasting- the 
RJ-ports still work, but the radio transmission goes dead. I've discovered that 
power-cycling the router will get it working again. In Windows XP, I am able to 
map/connect to Samba and Win2K and WinME shares.

Anyhow, one of the times I tried to NFS mount, I got the following error 
message:

kernel bug at 3rdparty/prism54/isl_ioctl.c:306
invalid operand: 0000[#1]
CPU: 0
EIP: 0060:[<C0292c85>] not tainted VLI
EFLAGS: 000010046
EIP is at prism54_mib_init+0x5d5/0x1100

eax: 00000000 ebx:d515f200 ecx:00000000 edx:d515f848
eis:00000296 edi:00000293 ebp:ddeddf6c esp:ddedddcc
ds:007b es:007b ss:0068

Then a stack dump, which I didn't write down. Then,

Call Trace:
free_task
schedule
copy_files
default_wake_function
default_wake_function
soft_cursor
schedule
__wake_up_common
worker_thread
prism54_mib_init
default_wake_function
worker_thread
kernel_thread_helper

I tried to write down the error message as best I could. I hope this helps. 
BTW, it also seems that when the laptop goes to "sleep", i.e. has been inactive 
for a while, the connection is lost and won't come back!



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.