1039:0191 Network issue when I disable eth0

[emperium]

Hello, I have this problem, Everytime a switch my network connection to wifi or 3G I haver to turn off the eth0, and when I try do get the eth0 to work again I have to do sudo ifconfig eth0 down/sudo ifconfig eth0 up 2 or 3 times, or in last resort I have to reboot the system. Thank you.
EmperiuM

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SIS966 [HDA SIS966], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SIS966 [HDA SIS966], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: emperium 1896 F.... pulseaudio
 /dev/snd/pcmC0D0p: emperium 1896 F...m pulseaudio
CRDA: Error: [Errno 2] Ficheiro ou directoria inexistente
Card0.Amixer.info:
 Card hw:0 'SIS966'/'HDA SIS966 at 0xd4200000 irq 18'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,10ec0000,00100003'
   Controls : 13
   Simple ctrls : 8
Date: Mon Jun 7 16:17:42 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 006: ID 0af0:6711 Option
 Bus 002 Device 002: ID 145f:011a Trust
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5515
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=/dev/sda2 loop=/hostname/disks/root.disk ro quiet splash
ProcEnviron:
 LANGUAGE=pt:pt_BR:en
 PATH=(custom, user)
 LANG=pt_PT.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 11/30/07
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.10
dmi.board.name: Z17M
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Rev 1.07
dmi.chassis.asset.tag: User Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: V1.07
dmi.modalias: dmi:bvnPhoenix:bvrV1.10:bd11/30/07:svnFUJITSUSIEMENS:pnESPRIMOMobileV5515:pvrV1.07:rvnFUJITSUSIEMENS:rnZ17M:rvrRev1.07:cvnFUJITSUSIEMENS:ct1:cvrV1.07:
dmi.product.name: ESPRIMO Mobile V5515
dmi.product.version: V1.07
dmi.sys.vendor: FUJITSU SIEMENS

[Jeremy Foshee (jeremyfoshee)]

Hi emperium,

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.]

[emperium (smarcelino)]

hello again,
with this Kernel linux-headers-2.6.34-999 my problem was solved. But I'll make a bisec until I found when was the bug fixed.

[penalvch (penalvch)]

emperium, 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? 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 . 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.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]