[Bug 11696] New: ipw2200 kernel module working erratically in linux-image-2.6.10-5-686 version 2.6.10-34.2

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=11696
Ubuntu | linux

           Summary: ipw2200 kernel module working erratically in linux-
                    image-2.6.10-5-686 version 2.6.10-34.2
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: linux
        AssignedTo: fabbione at ubuntu.com
        ReportedBy: vdv at dyomedea.com
         QAContact: kernel-bugs at lists.ubuntu.com


The machine is a Sony VAIO VGN-S2XP laptop. 

lspci -v gives:

0000:02:0b.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05)
        Subsystem: Intel Corp.: Unknown device 2753
        Flags: bus master, medium devsel, latency 64, IRQ 9
        Memory at d0206000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2

The wireless that used to work beautifully under Ubuntu Warty is using the
ipw2200 kernel module (I am using WEP and managed mode).

After upgrading to Ubuntu Hoary, linux-image-2.6.10-5-686 version 2.6.10-34
introduced a slight degradation: the wireless that comes up OK at boot time
stops working after a while without any error message in the logs. However, if I
type the following commands:

sudo rmmod ipw2200
sudo modprobe ipw2200
sudo ifup eth1

the wireless can then work for days without any problem.

After upgrading to linux-image-2.6.10-5-686 version 2.6.10-34.2, I have the same
issue after rebooting with the difference that after bringing the wireless down
and up again, it remains unstable and stops working after 10 minutes or so.

Thanks,

Eric

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.