Re: Kernel Panic with atmelwlandriver 2.1.2.2
Joerg Albert <[email protected]>
| Newsgroups | gmane.linux.drivers.atmel-wlan |
|---|---|
| Message-ID | <[email protected]> |
Hi Andre, On Wed, 23 Jul 2003, Andre Küster wrote: > after trying out a Netgear MA311 (which works perfectly, but not with my AP) What's the problem with your AP? Did you try both wlan-ng and host_ap? > and an ADM8211-WL-200P Fiberline PCI-Card (does not work at all) Strange, the WL-200X works here (the Cardbus card) with driver version 1.03, althrough I've tried ad-hoc mode only. > Since a while I try to get this device running stable, but it will not work. > I used Kernels 2.4.20, 2.4.21 and now 2.4.22pre7 and atmel-driver-version > 2.1.2.2. This is the first release, which is working over a longer > period and > crashes only happens under a few conditions. > > This are mainly firmware-upload-issues (I suppose), e.g. USB-Replug, > reboot without > "powering down" the usb-device and stuff... But the most annoying thing > are the crashes > under high load. The average "crash rate" during the download of an > 650mb cd-iso file > is 3 times, the kernel gets a NULL-Pointer-Reference and dies... > > Between the Kernel-Panic stuff I could read something about "process: > hotplug" > so maybe the usb-stuff is it, what produces the crash... > > Im am using the uhci.o Module for my MPV3-Via-USB-Controller, > for which lspci -v gave me that infos... > > 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 02) (prog-if 00 > [UHCI]) > Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- > Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- > Latency: 64, cache line size 08 > Interrupt: pin D routed to IRQ 10 > Region 4: I/O ports at e400 [size=32] No idea about the reason of the above problem, but could you try: a) another USB controller hardware (some PCI card)? b) an external hub and/or c) the Berlios OS driver (http://at76c503a.berlios.de/) /Jörg