wired connection not recognizing cable

[Mr.Gosh]

on my Thinkpad x220t in ubuntu 13.04 64bit the wired connection is not setup properly.
The eth0 LED is lighting up if a cable is connected but the networkmanager is not activating the connection.

Even a restart or unloading and reloading the driver doesn't work.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-7-generic 3.8.0-7.15
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bolte 1949 F.... pulseaudio
Date: Wed Feb 27 13:19:06 2013
InstallationDate: Installed on 2013-01-31 (26 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130131)
MachineType: LENOVO 42983XG
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-7-generic root=UUID=9badec85-2dc4-4e38-9de9-c8158d3b7c4e ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-7-generic N/A
 linux-backports-modules-3.8.0-7-generic N/A
 linux-firmware 1.103
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET63WW (1.33 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42983XG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET63WW(1.33):bd07/19/2012:svnLENOVO:pn42983XG:pvrThinkPadX220Tablet:rvnLENOVO:rn42983XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 42983XG
dmi.product.version: ThinkPad X220 Tablet
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced.

[Mr.Gosh (mr-gosh)]

Well sadly I recognized the problem lately - I installed 13.04 in end of january, there the wired connection worked out of the box.
Now after some updates I recognized this problem....

[Joseph Salisbury (jsalisbury)]

I'd like to perform a bisect to figure out what commit caused this regression. It would be very helpful to know the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.

Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:

v3.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc1-quantal/
v3.8-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc3-quantal/
v3.8-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc5-quantal/

You don't have to test every kernel, just up until the kernel that first has this bug.

One thing to note, you will need to install both the linux-image and linux-image-extra .deb packages.

Thanks in advance!

[Joseph Salisbury (jsalisbury)]

This may be related to bug 1131616 . Can you see if having the AC adapter connected affects this issue?

[Igor Gnatenko (i-gnatenko-brain)]

bug 1131616

[Mr.Gosh (mr-gosh)]

Even with AC pluggedin the wired network doesn't work.
I will test the Kernels above to see which one caused the problem...

[Mr.Gosh (mr-gosh)]

But I will use the raring kernels... ;)

[Mr.Gosh (mr-gosh)]

I was WRONG!
With AC Adapter plugged in network works - memo to me "check both sides to be connected"...

So this is aduplicate to bug 1131616 https://bugs.launchpad.net/bugs/1131616

[Mr.Gosh (mr-gosh)]

Should I still post the Kernel tests here - or in Bug 1131616
in RC1 the bug isn't present - I keep testing...

[Mr.Gosh (mr-gosh)]

In RC4 the Bug is present and it only apperas after a resume from sleep

[Mr.Gosh (mr-gosh)]

In RC3 the Bug is not present - that means 3.8.0 RC3 was the last kernel that didn't have the bug...