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

Bug#609407: firmware-iwlwifi: Can't resume from hibernate due to iwlagn



Package: firmware-iwlwifi
Version: 0.27
Severity: normal

I recently upgraded debian squeeze a week ago and now I have a problem with
hibernate, which is related to iwlagn. Everything was working fine before the
upgrade.

This is on a Dell Latitude E6400. That computer has a switch on its right side,
that enable/disable wifi and bluetooth. Starting the computer with that switch
off (I don't use wifi often), everything works fine. Then I put the computer
into hibernate mode (either through the menu or with pm-hibernate).
The computer goes to sleep. At wake up, the following message is printed
on screen.

[2282-124196] iwlagn 000:0c:00.0: MAC is in deep sleep! CSR_GP_CNTRL = 0xOOO
.... repeated several times
[2282-124196] iwlagn 000:0c:00.0: Hardware error detected. Restarting
[2282-62340] hub 3.0: 1.0: unable to enumerate USB device on port 1

Then, nothing else and a hard reboot is needed.

The problem does not appear if the wifi switch is on. So my guess is, it tries
to
find the wifi after waking up even if it is not enabled, and fails in that
case.
The problem also appears sometimes when suspending the computer,
but not always.

Sidenote: the only wifi related packages on the computer are
firmware-iwlwifi and wireless-tools.



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools         0.98.6           tools for generating an initramfs
ii  linux-image-2.6.30-2-68 2.6.30-8squeeze1 Linux 2.6.30 image on PPro/Celeron
ii  linux-image-2.6.32-5-68 2.6.32-29        Linux 2.6.32 for modern PCs

-- no debconf information



Reply to: