r8169 does not work if I boot Karmic, only works if I boot Windows, reboot and boot Karmic

Bug #455953 reported by Alexander 'gil' Tarasov
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Karmic by Alexander 'gil' Tarasov

Bug Description

Hi.

If I boot Ubuntu Karmic (latest development branch, updated from 9.04 via "update-manager -d") from "cold state" - my integrated network adapter (RTL8169sb/8110sb) does not work.
If I reboot, and boot Karmic again - it doesn't work again.
If I boot Windows XP, reboot, and boot Karmic - it works fine.

I tried:
1) "sudo rmmod r8169" and "sudo modprobe r8169" - this does not help;
2) "sudo service udev restart" - this doestn't help too.
3) load kernel with "acpi=off noacpi" - this doesn't help.
---
Architecture: i386
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
Package: linux (not installed)
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.34-999-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :
Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :
Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :
Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :
Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :

working dmesg and lspci:

Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :

working dmesg and lspci:

Revision history for this message
Pelládi Gábor (pelladigabor) wrote :

I have a network card that uses the r8169 kernel driver, lspci attached. Sometimes at boot the network card is not detected, it is completely missing from the lspci listing, and no eth0 interface is created. There is no sign in dmesg of the network card, when this bug happens.

Revision history for this message
Pelládi Gábor (pelladigabor) wrote :
Revision history for this message
Pelládi Gábor (pelladigabor) wrote :
Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :

Pelládi Gábor, you have another bug.

Revision history for this message
Pelládi Gábor (pelladigabor) wrote :

I have created a separate bug for my problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/473789

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Alexander,

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 from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 455953

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

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :

Hi,

Now I downloading daily build of Lucid Lynx, and test it in about 3-5 hours (daily build and mainline kernels).

Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :

Hi,

I update my karmic to latest Lucid (via update-manager -d).
Same story.

(1) If I boot from "cold state" - my network card doesn't work (log files: dmesg-2.6.32.20-doesnt-work.log, lspci_vvnn-2.6.32.20-doesnt-work.log, uname_a-2.6.32.20-doesnt-work.log).
(2) If I boot Windows, reboot, and boot Lucid - network card works (log files: dmesg-2.6.32.20-work.log, lspci_vvnn-2.6.32.20-work.log, uname_a-2.6.32.20-work.log).

I update kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-04-09-lucid/) - same stroy.
(3) If I boot from "cold state" - my network card doesn't work (log files: dmesg-2.6.34.999-doesnt-work.log, lspci_vvnn-2.6.34.999-doesnt-work.log, uname_a-2.6.34.999-doesnt-work.log).
(4) If I boot Windows, reboot, and boot Lucid - network card works (log files: dmesg-2.6.34.999-work.log, lspci_vvnn-2.6.34.999-work.log, uname_a-2.6.34.999-work.log).

Logs in attachments.

tags: added: apport-collected
description: updated
Revision history for this message
Alexander 'gil' Tarasov (alexander.gil.tarasov) wrote :

I can run apport-collect only when connected to network, here is apport-collect for kernel 2.6.34.999 with working network card.

tags: removed: needs-upstream-testing
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.