32bit PAE Thinkpad W510 cannot suspend when > 4 GB memory are in the machine
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
I've got a Thinkpad W510, which can handle up to 16 GB of memory. Running 32bit Maverick (because I need some 32bit binary only applications). The machine shipped with 4 GB of memory, and suspended and resumed regularly. However after upgrading to 12 GB of memory the machine would consistantly fail to resume after the second suspend in a row.
On the second attempted resume all lights on the keyboard flash every 4 seconds, and a hard reset is required. After trying different configurations of the DIMMS, dropping down to 8 GB, it still happened. After the last crash I removed another 4GB of RAM taking me back to 4GB, and now suspend resume has worked 4 times in a row without fail.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: No
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 54'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,
Controls : 6
Simple ctrls : 4
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
Mixer name : 'Nvidia GT220 HDMI'
Components : 'HDA:10de000a,
Controls : 16
Simple ctrls : 4
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'
Mixer name : 'ThinkPad EC 6MHT44WW-1.19'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Fri May 20 19:01:44 2011
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: LENOVO 4389AN7
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: linux
dmi.bios.date: 02/24/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NET76WW (1.37 )
dmi.board.name: 4389AN7
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 4389AN7
dmi.product.
dmi.sys.vendor: LENOVO
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Sean Dague, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https:/ /wiki.ubuntu. com/DebuggingKe rnelSuspend ? As well, could you please confirm this issue exists with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/daily/ current/ . If the issue remains, could you please run the following command from a Terminal (Applications- >Accessories- >Terminal) , as it will automatically gather and attach updated debug information to this report:
apport-collect -p %s %d
Additionally, could you please try to reproduce this with the upstream mainline kernel? It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.
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' , and comment as to why specifically you were unable to test it.
Please let us know your results. Thanks in advance.
Helpful Bug Reporting Links: /help.ubuntu. com/community/ ReportingBugs# Bug_Reporting_ Etiquette /help.ubuntu. com/community/ ReportingBugs# A3._Make_ sure_the_ bug_hasn. 27t_already_ been_reported /help.ubuntu. com/community/ ReportingBugs# Adding_ Apport_ Debug_Informati on_to_an_ Existing_ Launchpad_ Bug /help.ubuntu. com/community/ ReportingBugs# Adding_ Additional_ Attachments_ to_an_Existing_ Launchpad_ Bug
https:/
https:/
https:/
https:/