Thread: [Ndiswrapper-general] strange problems
Status: Beta
Brought to you by:
pgiri
From: Razvan U. <ra...@it...> - 2006-04-17 12:47:32
|
Hi all, I'm trying for 2 weeks now and I cannot make it work, but let me explain first my environment: - Stripped version of gentoo linux for use on small embedded systems - ndiswrapper 1.13 - kernel 2.4.33 - wireless card: ubiqity/nl2511/artheros nl5211 I can load ndiswrapper with the proper driver for each card, i can see my wlan0 interfaces and can use iwconfig to setup various parameters. I raise my wlan0 interface: ifconfig wlan0 192.168.0.10 I can see in iwevent that it links to other cards in ad-hoc mode BUT here come my problem: when I try to ping any host from wlan0 network system crashes with: -------------------------------------------------------------------------------- kernel BUG at slab.c:1134! invalid operand: 0000 CPU: 0 EIP: 0010:[<c0131c04>] Not tainted EFLAGS: 00010202 eax: 000001f0 ebx: 000001f0 ecx: c10b3bc8 edx: 00000007 esi: 00000000 edi: c10b3bb8 ebp: 00000007 esp: c2be3b60 ds: 0018 es: 0018 ss: 0018 Process ping (pid: 1452, stackpage=c2be3000) Stack: c10b3bc8 c10b3bc8 c10b3bc0 c10b3bb8 00000246 000001f0 c0131f0e c10b3bb8 000001f0 c2be3b00 c3b07960 c11fa140 c2bd2262 c48ad651 c10b3bb8 000001f0 00000020 00000002 c2be3b00 c3b07960 c11fa140 00000000 c48a4e8a c2bd2262 Call Trace: [<c0131f0e>] [<c48ad651>] [<c48a4e8a>] [<c48b2d0d>] [<c48b34be>] [<c01df4f4>] [<c01d46bd>] [<c020e11e>] [<c01da001>] [<c01daa17>] [<c01ef60c>] [<c01ef510>] [<c01ddc55>] [<c01ee072>] [<c01ef510>] [<c01ef500>] [<c01ef50b>] [<c01ddc55>] [<c01eedf9>] [<c01ef500>] [<c020b89a>] [<c020b5d0>] [<c0213d83>] [<c01cd18d>] [<c01ce538>] [<c012d100>] [<c0128b1a>] [<c0128d6d>] [<c018cbb6>] [<c01ce982>] [<c01089d3>] Code: 0f 0b 6e 04 c3 07 23 c0 8d 74 26 00 89 d8 c7 04 24 01 00 00 <0>Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing ------------------------------------------------------------------------------------ The thing is that on devel machine using the same kernel and same drivers everything works like expected, so what can cause this problem ? Tested on i686, wrap boards and i586/c3/eden platforms, I get the same behavior on all of them. If anyone can help me, I have more information for debugging if needed. Thanks. |
From: Giridhar P. <gi...@lm...> - 2006-04-17 17:44:55
|
On Mon, 17 Apr 2006 15:46:43 +0300, Razvan Udrea <ra...@it...> said: Razvan> kernel BUG at slab.c:1134! Debug trace (see wiki entry Bugs) would help. Do you have enough space on the system for you to compile with debug support? If the system can't handle large debug trace generated, you can compile with debug but enable debug right before ping. You may want to test with standard system (not embedded) with 2.4.33 kernel with debug trace and submit the trace. You may also want to try 1.14. 2.4 kernels are not well supported with USB: 2.4 kernels and Windows drivers differ in how interrupt URBs are submitted to usb core (2.6 kernels and Windows do the same). -- Giri |
From: Razvan U. <ra...@it...> - 2006-04-17 18:21:33
|
I'll try that. Also I'm pretty sure it's not USB related because I have the same behavior with ndiswrapper compiled without USB support. Giridhar Pemmasani wrote: > On Mon, 17 Apr 2006 15:46:43 +0300, Razvan Udrea <ra...@it...> said: > > Razvan> kernel BUG at slab.c:1134! > > Debug trace (see wiki entry Bugs) would help. Do you have enough space > on the system for you to compile with debug support? If the system > can't handle large debug trace generated, you can compile with debug > but enable debug right before ping. You may want to test with standard > system (not embedded) with 2.4.33 kernel with debug trace and submit > the trace. You may also want to try 1.14. > > 2.4 kernels are not well supported with USB: 2.4 kernels and Windows > drivers differ in how interrupt URBs are submitted to usb core (2.6 > kernels and Windows do the same). > > |
From: Giridhar P. <gi...@lm...> - 2006-04-17 22:21:53
|
On Mon, 17 Apr 2006 21:22:16 +0300, Razvan Udrea <ra...@it...> said: Razvan> I'll try that. Also I'm pretty sure it's not USB related Razvan> because I have the same behavior with ndiswrapper compiled Razvan> without USB support. Oops, I think I read ubiquity atheors as atheors's usb device. Don't worry about my comments about usb then. Send debug trace. I have used ar5211 driver for a belkin device (I don't remember which): blkwgn (Belkin,06/01/2005,4.1.2.56). I haven't had any problems with it. You may want to try that. -- Giri |
From: Razvan U. <ra...@it...> - 2006-04-19 08:51:34
|
Hi, I managed to found the problem, it was preempt option in kernel even it was stated on wiki I never consider till now to remove it from kernel. I hope devel will fix this problem though because I really need preempt on my kernel, I am running mostly on VIA boards based on C3 and Nehemiah proc and they work much better with preempt enabled. Giridhar Pemmasani wrote: > On Mon, 17 Apr 2006 21:22:16 +0300, Razvan Udrea <ra...@it...> said: > > Razvan> I'll try that. Also I'm pretty sure it's not USB related > Razvan> because I have the same behavior with ndiswrapper compiled > Razvan> without USB support. > > Oops, I think I read ubiquity atheors as atheors's usb device. Don't > worry about my comments about usb then. Send debug trace. I have used > ar5211 driver for a belkin device (I don't remember which): > blkwgn (Belkin,06/01/2005,4.1.2.56). I haven't had any problems with > it. You may want to try that. > |
From: Giridhar P. <gi...@lm...> - 2006-04-19 11:47:49
|
On Wed, 19 Apr 2006 11:51:02 +0300, Razvan Udrea <ra...@it...> said: Razvan> I managed to found the problem, it was preempt option in Sigh. I asked for trace that shows what the problem is. Recent versions of ndiswrapper should work with preempt and/or smp. I have always used preempt with the driver I mentioned without any issues. Razvan> though because I really need preempt on my kernel, I am Razvan> running mostly on VIA boards based on C3 and Nehemiah proc Razvan> and they work much better with preempt enabled. I don't have that processor. Nor do I know which Windows driver you use. I understand if you can't collect debug trace on embedded processor. But you stated you can reproduce the problem on i686. Why can't you submit debug trace running on those? Unless you give information as stated in wiki entry Bugs, this issue can not be fixed. -- Giri |
From: Razvan U. <ra...@it...> - 2006-04-19 13:30:40
|
Yeah I know that, but my procs are so slow, after I enable debug I can't give any command at all, I tried making a bash script even, with no luck so far. I'll keep trying and when I have a trace i will send it along with wireless driver . Giridhar Pemmasani wrote: > On Wed, 19 Apr 2006 11:51:02 +0300, Razvan Udrea <ra...@it...> said: > > Razvan> I managed to found the problem, it was preempt option in > > Sigh. I asked for trace that shows what the problem is. Recent > versions of ndiswrapper should work with preempt and/or smp. I have > always used preempt with the driver I mentioned without any > issues. > > Razvan> though because I really need preempt on my kernel, I am > Razvan> running mostly on VIA boards based on C3 and Nehemiah proc > Razvan> and they work much better with preempt enabled. > > I don't have that processor. Nor do I know which Windows driver you > use. I understand if you can't collect debug trace on embedded > processor. But you stated you can reproduce the problem on i686. Why > can't you submit debug trace running on those? Unless you give > information as stated in wiki entry Bugs, this issue can not be fixed. > |
From: Jim C. <jim...@gm...> - 2006-04-19 14:10:06
|
Razvan Udrea wrote: > Yeah I know that, but my procs are so slow, after I enable debug I > can't give any command at all, I tried making a bash script even, with > no luck so far. > I'll keep trying and when I have a trace i will send it along with > wireless driver . > > Is relay-fs an option for you, or for ndiswrapper in general ? Ive never messed with it, but its supposed to be very fast and low overhead, good for large amounts of data/logging etc. > Giridhar Pemmasani wrote: >> On Wed, 19 Apr 2006 11:51:02 +0300, Razvan Udrea <ra...@it...> >> said: >> >> Razvan> I managed to found the problem, it was preempt option in >> >> Sigh. I asked for trace that shows what the problem is. Recent >> versions of ndiswrapper should work with preempt and/or smp. I have >> always used preempt with the driver I mentioned without any >> issues. >> >> Razvan> though because I really need preempt on my kernel, I am >> Razvan> running mostly on VIA boards based on C3 and Nehemiah proc >> Razvan> and they work much better with preempt enabled. >> >> I don't have that processor. Nor do I know which Windows driver you >> use. I understand if you can't collect debug trace on embedded >> processor. But you stated you can reproduce the problem on i686. Why >> can't you submit debug trace running on those? Unless you give >> information as stated in wiki entry Bugs, this issue can not be fixed. >> |
From: Razvan U. <ra...@it...> - 2006-04-19 14:35:38
|
I'll take a look, but I don't think it will solve out my CPU time problem when debugging. Jim Cromie wrote: > Razvan Udrea wrote: >> Yeah I know that, but my procs are so slow, after I enable debug I >> can't give any command at all, I tried making a bash script even, >> with no luck so far. >> I'll keep trying and when I have a trace i will send it along with >> wireless driver . >> >> > > Is relay-fs an option for you, or for ndiswrapper in general ? > Ive never messed with it, but its supposed to be very fast and low > overhead, > good for large amounts of data/logging etc. > > >> Giridhar Pemmasani wrote: >>> On Wed, 19 Apr 2006 11:51:02 +0300, Razvan Udrea <ra...@it...> >>> said: >>> >>> Razvan> I managed to found the problem, it was preempt option in >>> >>> Sigh. I asked for trace that shows what the problem is. Recent >>> versions of ndiswrapper should work with preempt and/or smp. I have >>> always used preempt with the driver I mentioned without any >>> issues. >>> >>> Razvan> though because I really need preempt on my kernel, I am >>> Razvan> running mostly on VIA boards based on C3 and Nehemiah proc >>> Razvan> and they work much better with preempt enabled. >>> >>> I don't have that processor. Nor do I know which Windows driver you >>> use. I understand if you can't collect debug trace on embedded >>> processor. But you stated you can reproduce the problem on i686. Why >>> can't you submit debug trace running on those? Unless you give >>> information as stated in wiki entry Bugs, this issue can not be fixed. >>> |
From: Giridhar P. <gi...@lm...> - 2006-04-19 15:20:16
|
On Wed, 19 Apr 2006 17:35:56 +0300, Razvan Udrea <ra...@it...> said: Razvan> I'll take a look, but I don't think it will solve out my CPU Razvan> time problem when debugging. As mentioned before, enable debug right before pinging (or whatever causes crash); this limits the amount of debug trace drastically. If indeed you are doing this, clarify it - you are giving information as though you are paying very dearly for it. Also try latest svn instead of 1.13. And the Windows driver I mentioned before. -- Giri |
From: razvan <ra...@it...> - 2006-04-20 07:46:42
|
> As mentioned before, enable debug right before pinging (or whatever > causes crash); this limits the amount of debug trace drastically. If > indeed you are doing this, clarify it - you are giving information as > though you are paying very dearly for it. I am doing just like that, load driver with debug 0 and and I execute the following script: echo 6 > /proc/net/ndiswrapper/debug delay 1 ifconfig wlan0 192.168.0.10 up ping -c1 192.168.0.1 << at this point system should crash >> echo 0 > /proc/net/ndiswrapper/debug But it never reaches the point to ping, I only see debug messages. I even let it run for 15 minutes, maybe it found some CPU time to execute those 2 instructions. PS. Tests are currently made on Soekris Wrap boards (266Mhz CPU) and console is spawned via serial line, the only way to get it. > Also try latest svn instead of 1.13. And the Windows driver I > mentioned before. > > -- > Giri > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general Razvan Udrea Ituner Networks Corp. http://www.ituner.com |
From: Jim C. <jim...@gm...> - 2006-04-20 11:08:56
|
razvan wrote: >> As mentioned before, enable debug right before pinging (or whatever >> causes crash); this limits the amount of debug trace drastically. If >> indeed you are doing this, clarify it - you are giving information as >> though you are paying very dearly for it. >> > I am doing just like that, load driver with debug 0 and and I execute the following script: > > echo 6 > /proc/net/ndiswrapper/debug > delay 1 > ifconfig wlan0 192.168.0.10 up > ping -c1 192.168.0.1 << at this point system should crash >> > echo 0 > /proc/net/ndiswrapper/debug > > But it never reaches the point to ping, I only see debug messages. I even let it run for 15 minutes, maybe it found > some CPU time to execute those 2 instructions. > > PS. Tests are currently made on Soekris Wrap boards (266Mhz CPU) and console is spawned via serial line, the only way > to get it. > Do you mean PC-Engines ? Yes http://linuxdevices.com/products/PD9671326815.html I have a soekris net-4801 ( its where Im using ndiswrapper ), with an inexpensive belkin pci card. your board Geode SC-1100 based, so, try adding idle=poll to kernel boot-line, That geode (maybe others) has a buggy TSC; (it stops, or slows dramatically, when processor executes halt insn, which is done in the scheduler) Without it, recent kernels take a long time to boot - or Ive become more aware of it - and timestamped printks wont show the pause/hang points - so looking after the fact shows nothing. 17rc1-mm3 has new timekeeping code which detects the buggy TSC, and switches to the PIT the switch is prevented by idle=poll, which is consistent with the theory. I agree this 'theory' isnt airtight - but by the time shell scripts are running, the scheduler is too. So its not like saying that the dinosaur bones were beamed down here by aliens, (who also can alter the physics of radioactive decay ;) btw, I mount NFS-root from my laptop, across ethernet. sure beats serial-only. you might also try ramping your debug level up from 2 - 6 on consecutive boots. If you can only get to 4, its still better than nothing, and possibly even useful to Giri. |
From: Giridhar P. <gi...@lm...> - 2006-04-19 15:24:52
|
BTW, are you aware of madwifi project? Did you try that? If you did, why are you not using it? Just curious. -- Giri |
From: razvan <ra...@it...> - 2006-04-20 07:50:39
|
Yeah I know about it, it works perfectly, but it is only for Atheros based chipsets, and I got some other wireless cards that are not atheros based so it does not cover all my wireless cards. On Wed, 19 Apr 2006 11:24:49 -0400, Giridhar Pemmasani wrote > BTW, are you aware of madwifi project? Did you try that? If you did, > why are you not using it? Just curious. > > -- > Giri > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general Razvan Udrea Ituner Networks Corp. http://www.ituner.com |
From: Razvan U. <ra...@it...> - 2006-04-27 13:24:15
Attachments:
ndiswrapper.log.tgz
|
Hi, Sorry I've resent it with log file archived. First of all, current release 1.15 does not compile on 2.4 kernels with USB enabled: ---------------------------------------------------- cc -DEXPORT_SYMTAB -DMODVERSIONS -include /lib/modules/2.4.33-imedia/build/include/linux/modversions.h -DUSB_DRIVER_OWNER -freg-struct-return -DDRIVER_VERSION=\"1.15\" -DLINUX -D__KERNEL__ -DMODULE -I/lib/modules/2.4.33-imedia/build/include -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strict-aliasing -pipe -O2 -mpreferred-stack-boundary=2 -c -o pnp.o pnp.c pnp.c: In function `wrap_pnp_start_usb_device': pnp.c:679: warning: implicit declaration of function `usb_set_intfdata' pnp.c:679: error: `intf' undeclared (first use in this function) pnp.c:679: error: (Each undeclared identifier is reported only once pnp.c:679: error: for each function it appears in.) pnp.c:680: warning: return makes pointer from integer without a cast make[1]: *** [pnp.o] Error 1 make[1]: Leaving directory `/extra/kernel/kernel-modules/ndiswrapper/ndiswrapper-1.15/driver' make: *** [all] Error 2 ---------------------------------------------------- Anyway, I managed to overcome this issue and get back to my previous problem. Only with debug 3 enabled, anything bigger will bring my wrap box to its knees. Hope information will be useful. I attached the log file. If needed the steps I followed: 1. load driver 2. enabled debug 3. raising wlan0 interface with 192.168.0.100 4. pinging something on interface networks 192.168.0.1 Razvan Udrea. |
From: Giridhar P. <gi...@lm...> - 2006-04-27 16:51:47
|
I mentioned this before. You should either send me Windows driver you are using or use the driver I recommended (blkwgn 06/01/2005,4.1.2.56 from belkin). Also, send me kernel/slab.c file from your kernel sources, which may give a hint about the problem. -- Giri |
From: Giridhar P. <gi...@lm...> - 2006-04-27 16:57:50
|
BTW, latest svn should compile with 2.4 kernels with USB enabled. -- Giri |