8086:1049 e1000e NIC doesn't work in docking station after resume from suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
When I do a suspend of my Lenovo T61p laptop in stand-alone mode and then dock it, then resume from suspend my e1000e NIC doesn't work at all.
It is detected and all but I cannot get a link. I cannot get a link through the on-the-
I have tried unloading the module e1000e and then adding it again but it doesn't help. Only a reboot helps.
This is a regression since Lucid.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-generic 2.6.35.24.28
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-24-generic i686
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: AD198x Analog [AD198x Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe220000 irq 49'
Mixer name : 'Analog Devices AD1984'
Components : 'HDA:11d41984,
Controls : 31
Simple ctrls : 19
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'
Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Mon Jan 10 09:31:22 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: LENOVO 6458VJJ
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, user)
LANG=en_DK.utf8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: linux
dmi.bios.date: 05/11/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC6WW (2.26 )
dmi.board.name: 6458VJJ
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: 6458VJJ
dmi.product.
dmi.sys.vendor: LENOVO
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
ThomasNovin, 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, 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 a supported 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/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:/