https://bugzilla.novell.com/show_bug.cgi?id=350014 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c2 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mhoppe@novell.com --- Comment #2 from Helmut Schaa 2008-01-11 04:29:31 MST --- Matthias, did you try iwlwifi already. Since 1.2.0 the driver is much more reliable (and survives suspend-resume-cycles much better then ipw). And if you want to try yet another release try 1.2.23 from buildservice at [1]. [1] http://download.opensuse.org/repositories/driver:/wireless:/10.3/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350014 User mhoppe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c4 --- Comment #4 from Matthias Boettger 2008-01-11 06:18:52 MST --- Ok I tested the releases from buildservice. iwl is working with suspend without any crashes (tested s2ram and s2disk around 20 times) ipw from buildservice crashed on s2ram But I can't use iwl for the folliwng reasons: - wifi led not working - information about bit rate missing - lower link quality: IWL=71/100, IPW=84/100 - slow speed: IWL=2,25MB/s, IPW=2,75MB/s - take long time to associate, ipw is much faster - short interupts during network session (e.g. ssh) - no adjustable power management found (the wifi card within T60 and X61 becomes very hot without it) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350014 User mhoppe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c6 --- Comment #6 from Matthias Boettger 2008-01-11 06:47:56 MST --- (In reply to comment #5 from Helmut Schaa)

...

- lower link quality: IWL=71/100, IPW=84/100

Hmm, never saw this before. Is this ever the case?

It is ever the case.

...

- take long time to associate, ipw is much faster

Only for hidden networks?

I tested currently only a broadcasted WPA network

...

- no adjustable power management found (the wifi card within T60 and X61 becomes very hot without it)

I'm not sure if the 3945 has it too, but with my 4965 I have /sys/bus/pci/drivers/iwl4965/xxx/power_level for adjusting the power management.

Currently I use iwpriv set_power with ipw. Setting this is possible for me but for other users? You see, iwl is not really useable at the moment if you need to work over wifi many hours per day, especially with the interuptions. I think I found the reason for the crashing ipw module. I forgot that I put the ipw module in the list of modules to unload during suspend. If I remove ipw3945 from there everything is working during suspend but after first suspend I don't have any wifi device in NetworkManager. I need to restart network. After 2nd suspend and restarting network I'm unable to see any wifi networks. iwlist scan is empty too. After unloading und loading ipw manually everything is working again. Finally the crash is only happen if the module will be unloaded during suspend but is neccessary to get wifi working automatically after resume. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350014 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c8 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ipw3945 module crash system on suspend |ipw3945 crash on unload --- Comment #8 from Helmut Schaa 2008-01-11 07:07:49 MST --- Adjusting summary. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350014 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c10 --- Comment #10 from Helmut Schaa 2008-01-11 07:39:19 MST --- So, using the buildservice-packages the crash is gone, right? ipw3945 and suspend is a mess right now and will most likely not get fixed due to iwlwifi. The only way to get ipw3945 working reliable with suspend is as you did: reloading the modules after resume :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350014 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c12 --- Comment #12 from Helmut Schaa 2008-01-11 08:19:41 MST --- (In reply to comment #11 from Matthias Boettger)

Yes the module did not crash and the system is responsible but I was unable to reboot or shutdown my system. I saw a modprobe -r ipw3945 in D state and the system hangs on D-BUS shutdown.

Uhhh, that might be due to an _evil_ patch by Joe which I put into the buildservice project. Are you willing to try another build? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350014 User mhoppe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c14 --- Comment #14 from Matthias Boettger 2008-01-11 09:01:18 MST --- I think it is not really a problem with ipw on suspend because normal unloads are working. It seems to be a 'bad timing' problem if ipw is unloaded with SUSPEND_MODULES= and DBUS/NetworkManager is shutting down the network links. So two processes tries to shutdown an interface same time or something like this. I think we should add one of the powermanagement guys. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350014 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c16 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mhoppe@novell.com | --- Comment #16 from Stefan Seyfried 2008-01-16 10:00:39 MST --- Yes, i'll try. If unloading the module from 50modules does crash the kernel because of networkmangler still accessing the device, maybe we should just pack something like Matthias' script into ipw3945-kmp (the correct way would be to fix the driver, but...) Personally, i'd leave out the sleep and the iwpriv call since IMHO this should go somewhere into modprobe.conf or a udev rule. And the script should get a much higher number (98ipwreload.sh) to make sure it is executed some time before NM is told to resume networking. It should go into /usr/lib/pm-utils/sleep.d/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350014 User mhoppe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c18 --- Comment #18 from Matthias Boettger 2008-01-25 03:00:24 MST --- We had now several crashes during resume with my workaround on T60p and X61. So it seems not solve the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350014 User cstender@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350014#c20 Christopher Stender changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|mhoppe@novell.com | --- Comment #20 from Christopher Stender 2008-01-25 12:25:36 MST --- Okay, I could reproduce it by my one (after ~20 tests): Jan 25 19:59:50 tank dhclient: caught deadly SIGTERM Jan 25 19:59:50 tank dhclient: could not restore resolv.conf: No such file or directory Jan 25 19:59:51 tank kernel: Unable to handle kernel NULL pointer dereference at 0000000000000020 RIP: Jan 25 19:59:51 tank kernel: [<ffffffff80240a67>] wq_per_cpu+0x0/0x1a Jan 25 19:59:51 tank kernel: PGD 5c05e067 PUD 64ef9067 PMD 0 Jan 25 19:59:51 tank kernel: Oops: 0000 [1] SMP Jan 25 19:59:51 tank kernel: last sysfs file: /devices/pci0000:00/0000:00:1e.0/0000:15:00.0/pcmcia_socket/pcmcia_socket0/card_eject Jan 25 19:59:51 tank kernel: CPU 1 Jan 25 19:59:51 tank kernel: Modules linked in: ipw3945 ieee80211 ieee80211_crypt ip6t_LOG nf_conntrack_ipv6 xt_pkttype ipt_LOG xt_limit af_packet deflate zlib_deflate twofish_x86_64 twofish_common camellia serpent blowfish des cbc ecb blkcipher aes_x86_64 xcbc sha256 sha1 md5 crypto_null af_key snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device ip6t_REJECT xt_tcpudp ipt_REJECT xt_state iptable_mangle iptable_nat nf_nat cpufreq_conservative cpufreq_userspace iptable_filter cpufreq_powersave acpi_cpufreq ip6table_mangle nf_conntrack_ipv4 nf_conntrack nfnetlink ip_tables ip6table_filter ip6_tables x_tables ipv6 microcode loop dm_mod pcmcia thinkpad_acpi e1000 rtc_cmos rtc_core yenta_socket rsrc_nonstatic i2c_i801 iTCO_wdt battery hwmon sr_mod cdrom ac pcmcia_core snd_hda_intel rtc_lib snd_pcm snd_timer snd soundcore snd_page_alloc i2c_core nsc_ircc irda iTCO_vendor_support dock fglrx(P) button crc_ccitt firmware_class intel_agp joydev sg uinput ehci_hcd sd_mod uhci_hcd usbcore ed d ext3 mbcache jbd fan ata_piix ahc Jan 25 19:59:51 tank kernel: i libata scsi_mod thermal processor Jan 25 19:59:51 tank kernel: Pid: 9420, comm: wpa_supplicant Tainted: P N 2.6.22.13-0.3-default #1 Jan 25 19:59:51 tank kernel: RIP: 0010:[<ffffffff80240a67>] [<ffffffff80240a67>] wq_per_cpu+0x0/0x1a Jan 25 19:59:51 tank kernel: RSP: 0018:ffff810061cebc80 EFLAGS: 00010246 Jan 25 19:59:51 tank kernel: RAX: ffff8100606eabc0 RBX: ffff8100606eabb8 RCX: 0000000000000000 Jan 25 19:59:51 tank kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000 Jan 25 19:59:51 tank kernel: RBP: 0000000000000000 R08: 0000000000000006 R09: ffff8100606e9b78 Jan 25 19:59:51 tank kernel: R10: ffff810001014ba8 R11: ffffffffffffffff R12: ffff810061cebe38 Jan 25 19:59:51 tank kernel: R13: ffffffff80430c38 R14: ffff810061cebe48 R15: 0000000000008b16 Jan 25 19:59:51 tank kernel: FS: 00002b598c04eb00(0000) GS:ffff810037ffb240(0000) knlGS:0000000000000000 Jan 25 19:59:51 tank kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Jan 25 19:59:51 tank kernel: CR2: 0000000000000020 CR3: 0000000070f16000 CR4: 00000000000006a0 Jan 25 19:59:51 tank kernel: Process wpa_supplicant (pid: 9420, threadinfo ffff810061cea000, task ffff8100682de040) Jan 25 19:59:51 tank kernel: Stack: ffffffff80241079 ffff8100606e9088 ffffffff8818c00a 0000000000000000 Jan 25 19:59:51 tank kernel: ffffffff80391c85 0000000000000286 ffff8100606eada8 00000000fffffff4 Jan 25 19:59:51 tank kernel: ffff8100606e9088 00000000fffffff4 ffffffff8818c09d ffff81007aa01900 Jan 25 19:59:51 tank kernel: Call Trace: Jan 25 19:59:51 tank kernel: [<ffffffff80241079>] queue_work+0x2c/0x40 Jan 25 19:59:51 tank kernel: [<ffffffff8818c00a>] :ipw3945:ipw_send_disassociate+0x1ab/0x1fb Jan 25 19:59:51 tank kernel: [<ffffffff80391c85>] sock_sendmsg+0xea/0x107 Jan 25 19:59:51 tank kernel: [<ffffffff8818c09d>] :ipw3945:ipw_disassociate+0x43/0xb4 Jan 25 19:59:51 tank kernel: [<ffffffff8819c111>] :ipw3945:ipw_wx_set_mlme+0x36/0x3c Jan 25 19:59:51 tank kernel: [<ffffffff803f808a>] ioctl_standard_call+0x200/0x2af Jan 25 19:59:51 tank kernel: [<ffffffff8819c0db>] :ipw3945:ipw_wx_set_mlme+0x0/0x3c Jan 25 19:59:51 tank kernel: [<ffffffff803f8263>] wext_handle_ioctl+0x12a/0x38a Jan 25 19:59:51 tank kernel: [<ffffffff8819c0db>] :ipw3945:ipw_wx_set_mlme+0x0/0x3c Jan 25 19:59:51 tank kernel: [<ffffffff8039d5eb>] dev_ioctl+0x427/0x446 Jan 25 19:59:51 tank kernel: [<ffffffff80391542>] sock_ioctl+0x1db/0x1e5 Jan 25 19:59:51 tank kernel: [<ffffffff8029537f>] do_ioctl+0x2b/0xb6 Jan 25 19:59:51 tank kernel: [<ffffffff8029564d>] vfs_ioctl+0x243/0x25c Jan 25 19:59:51 tank kernel: [<ffffffff802956bf>] sys_ioctl+0x59/0x7a Jan 25 19:59:51 tank kernel: [<ffffffff80209c2e>] system_call+0x7e/0x83 Jan 25 19:59:51 tank kernel: Jan 25 19:59:51 tank kernel: Jan 25 19:59:51 tank kernel: Code: 83 7f 20 00 74 06 8b 35 5d 06 38 00 48 8b 07 48 63 d6 48 f7 Jan 25 19:59:51 tank kernel: RIP [<ffffffff80240a67>] wq_per_cpu+0x0/0x1a Jan 25 19:59:51 tank kernel: RSP <ffff810061cebc80> Jan 25 19:59:51 tank kernel: CR2: 0000000000000020 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.