[Ndiswrapper-general] Crashes with smc2802w-v2

[Andreas J K. <and...@fr...>]

Hi,

I can reproduce kernel crashes and freezes with this setup:

Hardware      SMP (Dual Intel Celeron (Mendocino) stepping 05)
Card          scm2802w v2
Kernel        2.6.9 (also seen with 2.6.10 and 2.4.29-pre3)
ndiswrapper   current CVS (after check-in '2004-12-27 09:57  pgiri')
gcc           2.95.4


/etc/ndiswrapper/2802w:
total 400
lrwxr-xr-x    1 root     root           47 Dec 26 10:21 1260:3890.conf -> /etc/ndiswrapper/2802w/1260:3890:1113:EE03.conf
-rw-r--r--    1 root     root          455 Dec 26 10:21 1260:3890:1113:EE03.conf
-rw-------    1 root     root        11196 Dec 26 10:21 2802w.inf
-rw-r--r--    1 root     root       387435 Dec 26 10:21 2802w.sys

Connection is running ad-hoc, no accesspoint involved. The card I'm
communicating with is an ATMEL, in case this might matter.

I've added lkcd to the otherwise vanilla 2.6.9 kernel. This allows me
to generate arbitrary numbers of these crashes. The recipe is to
produce some traffic on the connection. If I only have a ping running,
the box seems to work OK, but as soon as I start some traffic, e.g an
X application, we quickly have the kernel dying. If I do not use the
card at all, then the machine runs absolutely reliably. Unfortunately
I have no clue how to interprete the dump directory.

See the three traces of the three crashes I've collected so far below.
What jumps into my eye is that all three traces contain 'schedule+1408
[0xc02c7430]'.

Please let me know if I can provide more data for deeper insight.

	================================================================
	STACK TRACE FOR TASK: 0xf7f2cb10(events/1)
	
	Sl      SP      Function [IP]
	 0 [0xf7f37f24] schedule+1408 [0xc02c7430]
	 1 [0xf7f37f30] send_packets+105 [0xf8989c61]
	 2 [0xf7f37f50] xmit_worker+43 [0xf8989d6f]
	 3 [0xf7f37f74] worker_thread+435 [0xc0123543]
	 4 [0xf7f37fcc] kthread+122 [0xc0126d66]
	 5 [0xf7f37ff0] kernel_thread_helper+5 [0xc0102355]
	================================================================

	================================================================
	STACK TRACE FOR TASK: 0xf60b06d0(spamassassin)
	
	Sl      SP      Function [IP]
	 0 [0xee1a7f6c] schedule+1408 [0xc02c7430]
	 1 [0xee1a7f88] __do_softirq+106 [0xc0119b4a]
	 2 [0xee1a7fa8] do_softirq+40 [0xc0119bdc]
	 3 [0xee1a7fb0] smp_apic_timer_interrupt+249 [0xc010d51d]
	 4 [0xee1a7fc0] apic_timer_interrupt+26 [0xc01047a2]
	================================================================
	
	================================================================
	STACK TRACE FOR TASK: 0xf7f2d070(events/0)
	
	Sl      SP      Function [IP]
	 0 [0xf7f35f24] schedule+1408 [0xc02c7430]
	 1 [0xf7f35f60] ndis_irq_bh+57 [0xf8984d25]
	 2 [0xf7f35f74] worker_thread+435 [0xc0123543]
	 3 [0xf7f35fcc] kthread+122 [0xc0126d66]
	 4 [0xf7f35ff0] kernel_thread_helper+5 [0xc0102355]
	================================================================


-- 
andreas