[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#577559: marked as done (linux-image-2.6.32-3-amd64: Intel 5100 wireless doesn't work on Thinkpad SL500 anymore.)



Your message dated Thu, 15 Apr 2010 21:33:59 +0200
with message-id <20100415193359.GJ10984@baikonur.stro.at>
and subject line Re: Bug#577559: linux-image-2.6.32-3-amd64: Intel 5100 wireless doesn't work on Thinkpad SL500 anymore.
has caused the Debian Bug report #577559,
regarding linux-image-2.6.32-3-amd64: Intel 5100 wireless doesn't work on Thinkpad SL500 anymore.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
577559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577559
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.32-3-amd64
Version: 2.6.32-9
Severity: important
Tags: squeeze

The intel 5100 wireless on my thinkpad SL500 no longer works properly.
It works perfectly with 2.6.31, and it worked with at least 2.6.32-rc3
as well.  Now however, it will connect, work for a few seconds (it seems
to depend on the quantity of data passed through).  After a few seconds
of heavy traffic (like reloading a page in iceweasel), the wireless link
simply stops passing any traffic.  This if course makes the 2.6.32 kernel
rather useless on this laptop.  I have no idea if other laptops with the
same wireless chipset are affected, or if it is specific to this one
(given the lack of bug reports, I am inclined to believe it might be
specific to this machine type).

Any suggestion on how to track down what broke it so I can move on to
a current kernel on my laptop?

If I force a reconnect on the wireless, then I get another few seconds
of working traffic before it dies again.

I am using 5GHz 802.11n by the way, just in case the reason no one else
is seeing the bug is that everyone else runs 2.4GHz.  I suppose I should
test that by connecting to 2.4GHz instead to test that theory.

It works with 2.6.31 though, so clearly this can be fixed again.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (amd64)

Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash



--- End Message ---
--- Begin Message ---
Version: 2.6.32-11

On Thu, Apr 15, 2010 at 03:40:13PM -0400, Len Sorensen wrote:
> On Mon, Apr 12, 2010 at 05:12:04PM -0400, Ben Hutchings wrote:
> > There are so many changes in upstream stable updates (so far, 932 for
> > Linux 2.6.32) that we now list only the changes that have Debian bug
> > numbers or CVE numbers associated with them.
> 
> I can confirm that 2.6.32-11 does in fact appear to have fixed the
> problem.  My iwlwifi (intel 5100) now seems to keep passing traffic again.
> At least it hasn't died yet.

thanks for feedback, closing.


--- End Message ---

Reply to: