Thread: [Ndiswrapper-general] Re: oops
Status: Beta
Brought to you by:
pgiri
From: Giridhar P. <gi...@lm...> - 2004-07-30 14:50:52
|
Are you ejecting the card after bringing the interface down or without doing so? No, right thing to do is to call NdisPnpEventNotify indicating 'surprise removal' if you are ejecting without bringing the interface down. flush_schedule_work was always there; in fact, I removed an extraneous (spurious?) one from ndis_remove_one. -- Giri |
From: Giridhar P. <gi...@lm...> - 2004-07-30 15:20:14
|
On Fri, 30 Jul 2004 17:03:47 +0200, Cristiano De Michele <dem...@na...> said: >> Are you ejecting the card after bringing the interface down or >> without doing so? Cristiano> in that case it should work without problems, because Cristiano> ndis_remove_one() gets called not from a BH (interrupt Cristiano> context) on 2.4.x kernels... I am not sure what to make of what you wrote. Are you ejecting before bringing down the interface or after bringing down the interface? What BH context are you talking about? Can you enable DEBUG and give trace? I thought you are a seasoned user and know how to help us. >> No, right thing to do is to call NdisPnpEventNotify indicating >> 'surprise removal' if you are ejecting without bringing the >> interface down. Cristiano> but flush_scheduled_work() will be called anyway...or Cristiano> not? Is flush.. a problem? If so why is it a problem? Can you give details? -- Giri |
From: Cristiano De M. <dem...@na...> - 2005-01-08 20:16:53
Attachments:
kern.log.gz
ksymoops.output.gz
|
Hi Giri, unfortunately it's a while I'm trying to use ndiswrapper without success :(, what follows is about latest ndiswrapper from CVS, but it's the same since several revisions... as I insert ndiswrapper module doing: modprobe ndiswrapper I get errors attached (ksymoops output and kern.log) I remind you I have a usr805410 pcmcia card and a usr808054 AP and I'm using latest firmware (1.64) and latest driver (6.0b15) from USrobotics, many thanks, Cristiano -- Cristiano De Michele, Ph.D. E-mail: cri...@ph... Department of Physics Tel. : +39064457131 University of Rome "La Sapienza" Fax : +39064463158 Piazzale Aldo Moro 2 I-00185 Roma - Italy ------ "Shoot for the moon. Even if you miss, you'll land among the stars." |
From: Giridhar P. <gi...@lm...> - 2005-01-08 21:24:11
|
On Sat, 08 Jan 2005 21:16:27 +0100, Cristiano De Michele <dem...@na...> said: Cristiano> while I'm trying to use ndiswrapper without success :(, Cristiano> what follows is about latest ndiswrapper from CVS, but Cristiano> it's the same since several revisions... as I insert Cristiano> ndiswrapper module doing: You seem to be using Windows 98 driver, not Windows XP driver. As Installation document says, you are supposed to use Windows XP driver. For this card, 6.0b15 driver from USR works well, as does wg311v2 from Netgear. -- Giri |
From: Cristiano De M. <dem...@na...> - 2005-01-09 02:40:48
Attachments:
kern.log.gz
ksymoops.output.gz
|
On Sat, 2005-01-08 at 16:24 -0500, Giridhar Pemmasani wrote: > On Sat, 08 Jan 2005 21:16:27 +0100, Cristiano De Michele <dem...@na...> said: > > Cristiano> while I'm trying to use ndiswrapper without success :(, > Cristiano> what follows is about latest ndiswrapper from CVS, but > Cristiano> it's the same since several revisions... as I insert > Cristiano> ndiswrapper module doing: > > You seem to be using Windows 98 driver, not Windows XP driver. As > Installation document says, you are supposed to use Windows XP > driver. > > For this card, 6.0b15 driver from USR works well, as does wg311v2 from > Netgear. Giri, you were right, there was something messed up somewhere here... I reinstalled windows driver (6.0b15) on win XP and I got bin and sys files from it, then I re-installed them through ndiswrapper and now it works. Anyway as I do: modprobe -r ndiswrapper I get oops attached... my kernel is 2.4.28, many thanks, C. -- Cristiano De Michele, Ph.D. E-mail: cri...@ph... Department of Physics Tel. : +39064457131 University of Rome "La Sapienza" Fax : +39064463158 Piazzale Aldo Moro 2 I-00185 Roma - Italy ------ "Shoot for the moon. Even if you miss, you'll land among the stars." |
From: Giridhar P. <gi...@lm...> - 2005-01-09 08:54:54
|
On Sun, 09 Jan 2005 03:40:29 +0100, Cristiano De Michele <dem...@na...> said: Cristiano> Giri, you were right, there was something messed up Cristiano> somewhere here... I reinstalled windows driver Cristiano> (6.0b15) on win XP and I got bin and sys files from it, Cristiano> then I re-installed them through ndiswrapper and now it Cristiano> works. Anyway as I do: Cristiano> modprobe -r ndiswrapper Cristiano> I get oops attached... my kernel is 2.4.28, Something is messed up all right - I see traces of driverloader in the oops you attached. You should know that if you mess up this bad, you get to keep the pieces. As I said, this driver works fine with the chipset/card. Since you don't mention which version of ndiswrapper you are using (instead of attaching bits and pieces of information, use ndiswrapper-buginfo that is expressly created for the purpose of supplying useful information), I should remind you that until 1.0rc1, removing module in 2.4 kernels sometimes crashes kernel. -- Giri |
From: Adrian Irving-B. <wis...@wi...> - 2005-01-09 15:52:30
|
On Sun, Jan 09, 2005 at 03:54:52AM -0500, Giridhar Pemmasani wrote: > . . . I should remind you that until 1.0rc1, > removing module in 2.4 kernels sometimes crashes kernel. What's the status of this in 2.6? I still do a 'sync' before I rmmod, and still rmmod before I depart =66rom an AP's radius, because of the various oopses and panics. I use a USB one. Is this a 2.6 thing, an ndiswrapper thing, or a Windows driver thing? |
From: Giridhar P. <gi...@lm...> - 2005-01-09 18:47:17
|
On Sun, 9 Jan 2005 10:52:03 -0500, Adrian Irving-Beer <wis...@wi...> said: Adrian> I depart from an AP's radius, because of the various Adrian> oopses and panics. I use a USB one. Is this a 2.6 thing, Adrian> an ndiswrapper thing, or a Windows driver thing? Possibly ndiswrapper. I am not familiar with USB layer. May be Jan Kiszka can comment on it. I should've mentioned that when I commented that rmmod works, I was talking about PCI/PCMCIA cards (whatever I have). I occasionally try a prism54 USB dongle, but my testing with it is to see if anything other than USB layer is broken. -- Giri |
From: Jan K. <jan...@we...> - 2005-01-10 21:24:21
Attachments:
smime.p7s
|
Giridhar Pemmasani wrote: > On Sun, 9 Jan 2005 10:52:03 -0500, Adrian Irving-Beer <wis...@wi...> said: > > Adrian> I depart from an AP's radius, because of the various > Adrian> oopses and panics. I use a USB one. Is this a 2.6 thing, > Adrian> an ndiswrapper thing, or a Windows driver thing? > > Possibly ndiswrapper. I am not familiar with USB layer. May be Jan > Kiszka can comment on it. I should've mentioned that when I commented > that rmmod works, I was talking about PCI/PCMCIA cards (whatever I > have). I occasionally try a prism54 USB dongle, but my testing with it > is to see if anything other than USB layer is broken. > I'm not up-to-date with testing latest ndiswrapper against my WUSB54G dongle (prism54), but at least with 0.12 on kernel 2.6.8.1 it showed no unloading problems. However, if something crashes, I would also suspect that there is an issue with ndiswrapper - otherwise your Windows would also crash when you unplug your device (check if you use the latest Windows driver). Try to collect a crash dump of the kernel when unloading the driver. Jan |
From: Adrian Irving-B. <wis...@wi...> - 2005-01-11 01:25:47
|
On Mon, Jan 10, 2005 at 10:24:08PM +0100, Jan Kiszka wrote: > However, if something crashes, I would also suspect that there is an > issue with ndiswrapper - otherwise your Windows would also crash > when you unplug your device (check if you use the latest Windows > driver). I'll do said latest-driver check, sure. I'm reluctant to go poking around on someone else's computer to test the actual driver on a Windows machine, but it may come to that. I do have two different USB devices. The one I currently use (Netgear) has worked since I bought it, and the other (D-Link) has been slowly gaining functionality as ndiswrapper matures. The Netgear has always suffered freezes. Not when the device is unplugged (although that used to cause an infinite message loop, and may still), but rather, when I lose association for too long, change APs, or rmmod. I'll try the other sometime. If I can actually get an oops rather than a panic, I'll record that. It's difficult for me to get a panic dump; I can try recording it visually, but otherwise, I'll have to recompile my kernel for statically-loaded serial-over-USB support. :) (Certainly recompiling allows me to try other tricks, like turning off preempt.) |