Does the kernel panic with led=0? Can you provide the kernel EIP and back trace
info when panic? reproduceable?

Settings to NEEDSMOREDATA till we get some more data.

Knowing the model of Acer might be useful too.

Sorry for the late, but my connection went down for long time.
The laptop is:
ACER TM804LMi
My distro is: Slackware 10.0
Kernel 2.6.11.7
The bug is always reproducible on my laptop. On startup IPW2200 is loaded. If I
remove the module and reload it with parameter led=1, it seems work fine. Then I
try to remove and kernel panic happens. I make the same steps with parameter
mode, to set Monitor mode. It work fine and when I remove the module, everything
go well.

I haven't too much pratice with debug message under linux, but if someone tell
me how, I might send every message that appear when kernel panic happen, like
EIP value, etc...

(Sorry for my English)
After folliwing steps, the kernel DON'T panic:
1) rmmod ipw2200
2) modprobe ipw2200 led=0
3) rmmod ipw2200

When the kernel panic, it prints some back trace information to the console. If
the back trace message can fit in the screen, you will see a line begin with
"EIP: " followed by a function name or address. Will you provide that back trace
log during panic?

Well, fist lines that appear are:
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing EIP:
*pde = 00000000
Oops: 0002 [#1]
PREEMPT
Modules linked in: ...
CPU: 0
EIP: 0060:[<c01296b2>] Not tainted VLI
EFLAGS: 00010002 (2.6.11.7)
EIP is at __queue_work+0x42/0xa0

(In reply to comment #7)
> Well, fist lines that appear are:
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> printing EIP:
> *pde = 00000000
> Oops: 0002 [#1]
> PREEMPT
> Modules linked in: ...
> CPU: 0
> EIP: 0060:[<c01296b2>] Not tainted VLI
> EFLAGS: 00010002 (2.6.11.7)
> EIP is at __queue_work+0x42/0xa0

Umm, may I get more?

Same to me. (Debian, vanila kernel 2.6.11.11)
This is all that i get after i try rmmod ipw2200 (if i modprobed it with led=1)


ipw2200: failed to send SSID command
Jun 11 19:50:05 lyonesse kernel: ipw2200: failed to send SSID command
Unable to handle kernel paging request at virtual address 08048034
 printing eip:
*pde = 1d853067
*pte = 1dede025
OOps: 003 [#1]
PREEMPT
Modules linked in: firmware_class ieee80211 ieee80211_crypt rfcomm l2cap
bluetooth i915 drm psmouse e1000 yenta_socket rsrc_nonstatic pcmcia_core
snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd
snd_page_alloc ehci_hcd uhci_hcd usbstore intel_agp agpgart ppp..... slhc
CPU:    0
EIP:    0060:[<c012a522>]  Not tainted VLI
EFLAGS: 00010002   (2.6.11.11-i4x40)
EIP is at __queue_work+0x42/0xa0
eax: de9a41c0  ebx: c0456000  ecx: da421278  edx: 00000003
esi: 08048034  edi: da421274  ebp: 00000282  esp: c0457f10
ds: 007b  es: 007b  ss: 0068
Process swapper (pid: 0, threadinfo=c0456000 task=c03c0b20)
Stack: c01236d2 c0456000 00000101 da421274 c012a5f0 c012a606 de9a41c0 da421274
       c01238b2 da421274 c01417c0 00000000 00000000 c0456000 c0457f48 c0457f48
       00000000 00000001 c048eea8 0000000a c15d9000 c011f52b c048eea8 00000046
Call Trace:
 [<c01236d2>] update_process_times+0x32/0x110
 [<c012a5f0>] delayed_work_timer_fn+0x0/0x20
 [<c012a606>] delayed_work_timer_fn+0x16/0x20
 [<c01238b2>] run_timer_softirq+0xe2/0x200
 [<c01417c0>] handle_IRQ_event+0x30/0x70
 [<c011f52b>] __do_softirq+0x7b/0x90
 [<c011f566>] do_softirq+0x26/0x30
 [<c011f635>] irq_exit+0x35/0x40
 [<c01054fe>] do_IRQ+0x1e/0x30
 [<c0103a8e>] common_interrupt+0x1a/0x20
 [<c0288dd1>] acpi_processor_idle+0x122/0x25e
 [<c01010f0>] cpu_idle+0x50/0x60
 [<c04587fe>] start_kernel+0x14e/0x170
 [<c04583a0>] unknown_bootoption+0x0/0x1e0
Code: 89 6c 24 10 9c 5d fa bb 00 e0 ff ff 21 e3 ff 43 14 89 47 14 8d 50 08 8b 72
04 89 57 04 8d 4f 04 89 4a 04 ba 03 00 00 00 89 71 04 <89> 0e b9 01 00 00 00 ff
40 04 83 c0 10 c7 04 24 00 00 00 00 e8
 <0>Kernel panic - not syncing: Fatal exception in interrupt


that's all.
my hardware is ibm thinkpad x40.

Created an attachment (id=421) [details]
fix patch

Mark as fixed. Thanks for reporting.

Hi Peitro, Josef:
Is the kernel panic gone in 1.0.4 or later versions?

Yes, bug is gone. Thanks for fix

Marking as verified, based on previous comment.