IWLAGN 4965abg MAC is in deep sleep

Bug #463316 reported by Francesco P.
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: yelp

9.10 rc is unable to wake up the wireless and a
[ 126.028619] iwlagn 0000:0c:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x080433D8
message appear.

ProblemType: Bug
Architecture: amd64
Date: Thu Oct 29 14:01:59 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/yelp
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
Package: yelp 2.28.0-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: yelp
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
Francesco P. (fpedersoli) wrote :
affects: yelp (Ubuntu) → ubuntu
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect 463316

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

Revision history for this message
Francesco P. (fpedersoli) wrote : apport-collect data

Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 4681 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 11'
   Mixer name : 'SigmaTel STAC9200'
   Components : 'HDA:83847690,102801cd,00102201 HDA:14f12bfa,14f100c3,00090000'
   Controls : 13
   Simple ctrls : 7
DistroRelease: Ubuntu 9.10
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
MachineType: Dell Inc. MP061
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- noapic console-setup/layoutcode=it
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:4735): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:4735): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:4851): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:4873): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:4850): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 24
dmi.bios.date: 06/27/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0YD479
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/27/2007:svnDellInc.:pnMP061:pvr:rvnDellInc.:rn0YD479:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MP061
dmi.sys.vendor: Dell Inc.

Revision history for this message
Francesco P. (fpedersoli) wrote : AlsaDevices.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : AplayDevices.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : BootDmesg.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : Card0.Amixer.values.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : Card0.Codecs.codec.0.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : Card0.Codecs.codec.1.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : CurrentDmesg.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : Lspci.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : Lsusb.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : PciMultimedia.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : ProcCpuinfo.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : ProcInterrupts.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : ProcModules.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : RfKill.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : UdevDb.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : UdevLog.txt
Revision history for this message
Francesco P. (fpedersoli) wrote : WifiSyslog.txt
Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Revision history for this message
Sceptic (keith-no) wrote :

Is this related to 7d930bc33653d5592dc386a76a38f39c2e962344? Apparently there were reports of problems after deauthenticating that were fixed by reverting that commit.

Whether it's related to that commit or not, I'm seeing a very similar problem with 2.6.31-15-generic. It seems to start after the following in dmesg:
[18363.512539] No probe response from AP 00:17:31:ae:21:6f after 500ms, disconnecting.
[18364.152558] iwlagn 0000:07:00.0: Error sending REPLY_RXON: time out after 500ms.
[18364.152570] iwlagn 0000:07:00.0: Error setting new RXON (-110)
[18364.653817] iwlagn 0000:07:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.

After a number of similar messages, it eventually starts spitting out
[36369.096452] iwlagn 0000:07:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0xFFFFFFFF

Revision history for this message
superlex (e-lex) wrote :

Hi!
Can you try this solution:

Add pci=use_crs at the end of the line

linux /boot/vmlinuz-2.6.31-19-generic root=UUID=8a7ca0ae-ec6e-4df9-9661-edccf300d223 ro quiet splash

in the file /boot/grub/grub.cfg and reboot

Revision history for this message
sahas (napster-it) wrote :

@superlex: So does this mean that this problem arises because of incorrect or failure in allocation of PCI resources?

I shall give your solution a shot. The problem comes up very randomly so even a weeks worth of testing would not be enough to know for sure in my case. Is there anything in the log files that will tell me if the fix is working?

Thanks for the help!

Revision history for this message
superlex (e-lex) wrote :

The best way to know if it works is waiting and seeing what happens.
According to me, messages in dmesg are important only when the problem occurs.

I do not know if the solution is correct, that's why I'm trying and I ask you to try too.
Until now I had no more problems.

Revision history for this message
Francesco P. (fpedersoli) wrote : Re: [Bug 463316] Re: IWLAGN 4965abg MAC is in deep sleep

Sorry for the delay, but I'm in holiday (ops) and I'll be back with my
notebook next week. I'll try to apply the suggested parameter
immediately and to send all the feedback.

Thanks' for the support. Frank.

sahas wrote:
> @superlex: So does this mean that this problem arises because of
> incorrect or failure in allocation of PCI resources?
>
> I shall give your solution a shot. The problem comes up very randomly so
> even a weeks worth of testing would not be enough to know for sure in my
> case. Is there anything in the log files that will tell me if the fix is
> working?
>
> Thanks for the help!
>
>

--
SPIN Networks Italia
Francesco Pedersoli
Technical Manager

E-mail: <email address hidden>
GSM : +39-335-7490929

Questa e-mail può contenere informazioni confidenziali e/o riservate. Se non siete il destinatario del messaggio (o avete ricevuto questa e-mail per errore) siete pregati di notificarlo al mittente e distruggere immediatamente la presente e-mail. La copia non autorizzata, la pubblicazione, l'uso e la distribuzione a terzi del materiale e delle informazioni contenute nella presente e-mail, senza autorizzazione preventiva da parte del mittente, è proibita e sarà perseguita nei termini consentiti dalla legge.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure, distribution of the material in this e-mail is strictly forbidden.

Revision history for this message
Francesco P. (fpedersoli) wrote :

Hi,
another time, sorry for the delay. No, nothing change adding the
parameters. The only VERY strange behavior is that, for the first time,
I saw the WiFI green light on, when I restart the PC from the login
display. Really strange and after two times I was no longer able to
replicate the behavior.
The only I did was to use the iwconfig command "iwconfig wlan1 txpower
15" that usually is 0.

Now I'm using the 2.6.31-21 kernel and the compat-wireless-2010-03-19.
Ubunt backport is unusable: MAC in deep sleep.

Thanks' Frank

superlex wrote:
> Hi!
> Can you try this solution:
>
> Add pci=use_crs at the end of the line
>
> linux /boot/vmlinuz-2.6.31-19-generic root=UUID=8a7ca0ae-ec6e-
> 4df9-9661-edccf300d223 ro quiet splash
>
> in the file /boot/grub/grub.cfg and reboot
>
>

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Francesco,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
dcam (david-pastornet)
Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
dcam (david-pastornet) wrote :

Confirming this behaviour in an up-to-date Maverick and also its predecessors...

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.