Intel Wireless Adapter "iwl3945" not working after sleep

I can confirm that this issue still exists in the final release of version of 11.04. Same errors and symptoms.

I have the same problem here with Ubuntu 11.04 and Gnome 3 (Hardware: Notebook Compal JFT00/Intelbras i35)

does not occur at every resume.

Yes, it does occur at every resume. It has never worked properly. Marc, please verify that your kernel, hardware and driver details match those in the original bug notes.

In my case this error does not occur after every resume. Now, interested persons might want to read:

1. http://ubuntuforums.org/archive/index.php/t-1322643.html (6th post)
2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/297385 (similar, if not the same bug dating back to 8.10...)

For me this is serious, I sometimes need to resume my laptop and quickly look-up something on the web, sometimes I'm on the phone and I have to reboot. This is very frustrating as this bug hasn't been resolved since 2008....
This is not ubuntu-only bug as it occured on opensuse and fedora.

Some extra information at: https://bugzilla.redhat.com/show_bug.cgi?id=732029

echo 'SUSPEND_MODULES="iwl3945"' > /etc/pm/config.d/iwl3945 seems to resolv my problem.

now, iwl3945 seems to be reloaded after each resume.

sorry : my last comment is wrong ; wakeup issues still present.

Tim Wernicke, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please provide the information noted in https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Christopher,

I am not in a position to be able to further test this bug. I initially reported the problem over a year ago. It never received any official response and, based on feedback as recently as February of this year in the bug comments, the issue is not fixed. It should not come as a surprise that I gave up a long time ago and no longer use Ubuntu on that laptop.

I mean no disrespect. I know that the devs volunteer a lot of time working on Ubuntu. But a year is an absurd amount of time to wait for a fix to a show-stopping bug like this on a laptop, particularly considering the myriad of other operating systems available. And based on the comments in this bug, it seems this problem is endemic in other Linux variants as well, going back as far as 2008. Some other brave soul will have to step-in and confirm whether this remains an issue.

Marc, as of Feb. 15th 2012, you were still experiencing the problem. Can you confirm that the problem still exists?

Regards,
Tim

bug still exists/ it's wery annoying/ ubuntu 12.04 with regular kernel. Also i can say that this error does not occur after every resume.

Bogdan Iavorskyi, if you are having a problem in Ubuntu, please file a new report by executing the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

Tim Wernicke, as you are unwilling to perform the requred steps requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/732174/comments/10 , this report is closed. If you perform this in the future, please feel free to reopen this report and we may work together from there. Please feel free to report any future bugs you may find.

Christopher,

Marking this bug as invalid is wrong. This bug report has multiple people adding comments confirming that the problem exists. You also have someone as recently as 7 hours ago confirming that the problem exists in the latest release. There's absolutely no reason to close this bug and make others jump through more hoops for the exact same problem. This is especially true considering how long this bug has been open with no actual developer attention yet. This bug was reported over 1 year and 3 months ago. And even though it's very old, not one developer attempted to fix it. Are you implying that a newer bug report of the exact same issue will somehow get more attention than this one?

Closing this bug and forcing others with the exact same problem to open a new one makes it seem like you're just going to keep up the same routine; ignore the bug for long enough until most people give up, then close it out as invalid. This bug is not invalid. It is very valid, and confirmed as still existing in the latest release.

If you need someone to post some details about the bug against the current release, it looks as if Bogdan is the best person for that. Bogdan, can you help by executing the following from your terminal:

ubuntu-bug linux

Thanks,
Tim

Tim Wernicke, at this point in the triage process, this report is yours, not anyone elses. If you are unwilling to provide the minimum requirements to debug your problem, then it is closed. However, if someone else has a problem, independent of whether it is the same or not, they should create a new report as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/732174/comments/13 and we can take it from there.

Christopher Penalver,

I'm very willing to provide the minimum requirements to debug the problem. In fact, I already provided them in the original bug notes. However, a year and 3 months later, I don't have access to the hardware anymore. Regardless, there are multiple additional people commenting in this bug report confirming the same problem. One as recently as 9 hours ago. There are plenty of resources to help debug the problem as described in this bug report.

If your unwillingness to investigate this bug is the best way you know how to help these people, then knock yourself out and close the report. Keep up the good work, Christopher!

Over and out,
Tim

Tim Wernicke, regarding your comments:
>"I'm very willing to provide the minimum requirements to debug the problem. In fact, I already provided them in the original bug notes. However, a year and 3 months later, I don't have access to the hardware anymore."

Ok, bug closed Invalid as you do not have the hardware versus you are unwilling to provide the details.

>"Regardless, there are multiple additional people commenting in this bug report confirming the same problem. One as recently as 9 hours ago. There are plenty of resources to help debug the problem as described in this bug report."

We both knew this already.

>"If your unwillingness to investigate this bug is the best way you know how to help these people, then knock yourself out and close the report. Keep up the good work, Christopher!"

This comment indicates you do not understand https://bugs.launchpad.net/ubuntu/+source/linux/+bug/732174/comments/16 . How am I unwilling to investigate bugs if I want others with their problem(s) to report their bug(s) in a new report, so I may provide focused triaged?

Come on. :D

No more comments are required in this report based on this, and due to the fact you do not having the hardware anymore.

OK. I will do all actions from post 10.

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bogdan 1625 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc300000 irq 47'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,104d2800,00100100 HDA:14f12c06,104d1700,00100000'
   Controls : 17
   Simple ctrls : 9
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=bd69618d-587c-42aa-b8dc-5a94174fa793
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Sony Corporation VGN-NR385E
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=uk_UA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=UUID=e7288ee7-1ab2-4b3b-aef9-a8774e8a5736 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-25-generic N/A
 linux-backports-modules-3.2.0-25-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: precise precise
Uname: Linux 3.2.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/23/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R1101J9
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR1101J9:bd10/23/2007:svnSonyCorporation:pnVGN-NR385E:pvrC3LQY9KA:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-NR385E
dmi.product.version: C3LQY9KA
dmi.sys.vendor: Sony Corporation

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Bogdan Iavorskyi, please do not apport-collect to another person's report. If you are having a problem, you are welcome to file a new report via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

Bogdan, please subscribe me to it as well, or at least paste the link to the new report here. It would be useful for others who have the exact same problem.

I'm also curious to see if Christopher actually investigates your bug, or if your report just gets ignored and eventually closed as invalid.

i create new bug - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1134696
bug still exist on 13.04 with 3.8 kernel