Kernel Panic with atmelwlandriver 2.1.2.2

Andre Küster <xsd12-S0/[email protected]>
Newsgroups gmane.linux.drivers.atmel-wlan
Message-ID <[email protected]>
Hi,

after trying out a Netgear MA311 (which works perfectly, but not with my AP)
and an ADM8211-WL-200P Fiberline PCI-Card (does not work at all) I returned
to my old USB-Wlan-Adapter WL-100UP, wich is an Atmel Device
(http://www.fiberlineeurope.de/Preislisten/fiberline_produkte/wireless_lan/WL100U_P_D.htm)

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]


While I am writing this, I could watch to a live kernel panic ;)
and the following happens: the usb-Device seemed to disconnect from the 
usb-bus and during reconnect the
crash happens. But, I often saw disconnects of my usb-device, followed 
by reconnects, and after that all worked
fine. Maybe the high activity makes the kernel crashing.. I have no 
idea, and I dont know much about
kernelspace, but I`d like to help debugging, if anyone can tell me how ;)


Greetings,
           Andre.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.