[ATrpms-users] 2.6.20.3 & ieee80211-1.2.16 & ipw3945-1.2.0 broken? (fwd: fc6 problem with the ieee8011 module)

Thu Mar 29 14:12:46 CEST 2007

I got the following report from an ATrpms user. If he removes the
1.2.16 ieee80211 module and drops to the in-kernel 1.1.13 the messages
disappear.

The ipw3945 packages are built against ieee80211 1.2.16 headers, though.

----- Forwarded message from Brian Millett <bmillett at gmail.com> -----

From: Brian Millett <bmillett at gmail.com>
Subject: [ATrpms-users] fc6 problem with the ieee8011 module
To: ATrpms user list <atrpms-users at ATrpms.net>
Date: Thu, 29 Mar 2007 05:52:26 -0500
Envelope-to: Axel.Thimm at atrpms.net
Delivery-date: Thu, 29 Mar 2007 12:53:25 +0200

Hello,
  I'm running a fc6 laptop with the ipw3945 & ieee8011 modules from
atrpms. With the start of kernel-2.6.20-1.2925.fc6, I started to get
kernel messages with the message comming from the ipw3945 stack:

__BEGIN__
Mar 24 22:05:19 dufus kernel: ipw3945: Error sending ADD_STA: time out
after 500ms.
Mar 24 22:05:19 dufus kernel: invalid opcode: 0000 [#1]
Mar 24 22:05:19 dufus kernel: SMP
Mar 24 22:05:19 dufus kernel: last sysfs file: /class/net/eth0/carrier
Mar 24 22:05:19 dufus kernel: Modules linked in: ipt_LOG xt_tcpudp
nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink xt_multiport
iptable_filter ip_tables x_tables vfat fat nfsd exportfs lockd nfs_acl
autofs4 hidp rfcomm l2cap bluetooth vmnet(P)(U) vmmon(P)(U) sunrpc
cpufreq_ondemand video sbs i2c_ec dock button battery asus_acpi
backlight ac parport_pc lp parport snd_hda_intel snd_hda_codec
snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device
snd_pcm_oss joydev snd_mixer_oss nvidia(P)(U) sr_mod snd_pcm cdrom
snd_timer snd iTCO_wdt tg3 soundcore iTCO_vendor_support snd_page_alloc
ipw3945(F)(U) serio_raw ohci1394 pcspkr i2c_i801 ieee1394 i2c_core
ide_cs ieee80211(F)(U) ieee80211_crypt(F)(U) sg dm_snapshot dm_zero
dm_mirror dm_mod ata_piix libata sd_mod scsi_mod ext3 jbd ehci_hcd
ohci_hcd uhci_hcd
Mar 24 22:05:19 dufus kernel: CPU:    0
Mar 24 22:05:19 dufus kernel: EIP:    0060:[<c0434847>]    Tainted: PF
   VLI
Mar 24 22:05:19 dufus kernel: EFLAGS: 00010206   (2.6.20-1.2933.fc6 #1)
Mar 24 22:05:19 dufus kernel: EIP is at run_workqueue+0x8a/0x125
Mar 24 22:05:19 dufus kernel: eax: f6c54d4c   ebx: f6c56258   ecx:
00000018   edx: 00000018
Mar 24 22:05:19 dufus kernel: esi: f77929c0   edi: 00000246   ebp:
f6c56254   esp: f72c6f6c
Mar 24 22:05:19 dufus kernel: ds: 007b   es: 007b   ss: 0068
Mar 24 22:05:19 dufus kernel: Process ipw3945/0 (pid: 1484, ti=f72c6000
task=f72cc2f0 task.ti=f72c6000)
Mar 24 22:05:19 dufus kernel: Stack: 00000000 00000282 f7030d34 c061ffaf
f8f489d4 f77929c0 f7030d34 f72c6fbc
Mar 24 22:05:19 dufus kernel:        00000000 c04351b4 00000001 00000000
00000001 00010000 00000000 00000000
Mar 24 22:05:19 dufus kernel:        f72cc2f0 c04226ab 00100100 00200200
ffffffff ffffffff f77929c0 c04350bb
Mar 24 22:05:19 dufus kernel: Call Trace:
Mar 24 22:05:19 dufus kernel:  [<c061ffaf>] _spin_lock_irqsave+0x9/0xd
Mar 24 22:05:19 dufus kernel:  [<f8f489d4>] ipw_bg_disassociate+0x0/0x31
[ipw3945]
Mar 24 22:05:19 dufus kernel:  [<c04351b4>] worker_thread+0xf9/0x124
Mar 24 22:05:19 dufus kernel:  [<c04226ab>] default_wake_function+0x0/0xc
Mar 24 22:05:19 dufus kernel:  [<c04350bb>] worker_thread+0x0/0x124
Mar 24 22:05:19 dufus kernel:  [<c04377c7>] kthread+0xb0/0xd9
Mar 24 22:05:19 dufus kernel:  [<c0437717>] kthread+0x0/0xd9
Mar 24 22:05:19 dufus kernel:  [<c0404b33>] kernel_thread_helper+0x7/0x10
Mar 24 22:05:19 dufus kernel:  =======================
Mar 24 22:05:19 dufus kernel: Code: e8 9f b7 1e 00 8b 43 fc 83 e0 fc 39
f0 74 04 0f 0b eb fe 8b 43 fc a8 02 75 06 f0 0f ba 73 fc 00 89 e8 ff 54
24 10 89 e0 25 00 f0 <ff> ff 8b 48 14 f7 c1 ff ff ff ef 74 48 65 a1 08
00 00 00 8b 90
Mar 24 22:05:19 dufus kernel: EIP: [<c0434847>] run_workqueue+0x8a/0x125
SS:ESP 0068:f72c6f6c
__END__

I've read that the ieee80211 in the 2.6.20 kernel is compatible with the
ipw3945 drivers, so I forced a removal of the
ieee80211-kmdl-2.6.20-1.2933.fc6-1.2.16-17.fc6.at and still have the
ipw3945-kmdl-2.6.20-1.2933.fc6-1.2.0-18.2.fc6.at module.  Since I did
that, I have not had any messages and all is running fine.

Is the ieee8011 necessary anymore?  If not, can the dependency be
removed?  I know that that would make it not backward compatible.

Thanks.
-- 
Brian Millett - [ Markab Ambassador, "The Long Dark"]
"The forces of darkness do not move openly. They work through others.
Use others. When the darkness was defeated long ago, they scattered, hid
 themselves away in secret places, and waited. Now, the dark hand is
 reaching out and recalling them from their sleep."

_______________________________________________
atrpms-users mailing list
atrpms-users at atrpms.net
http://lists.atrpms.net/mailman/listinfo/atrpms-users

----- End forwarded message -----

-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20070329/b47f8f24/attachment.bin 