Ubuntu
linux-backports-modules-2.6.27 package

Aspire one - ethernet not running under 2.6.27.11 kernel (Intrepid)

Bug #315261 reported by TimWintle on 2009-01-08

This bug report is a duplicate of: Bug #326891: 2.6.27.11 kernel breaks r8169 support for rtl8102e. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux-backports-modules-2.6.27 (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

(sorry if this is the wrong package - I'm not sure if the ethernet driver is in linux-backports-modules or linux-restriced-modules)

I'm running intrepid on the Aspire One.

When booting under kernel 2.6.27.11 my ethernet fails to get an ip address via dhcp (afraid I don't have logs dump available here as I'm on a different machine, although I could generate them if they are required).

I have tried manually setting the ip address, but no packets are being sent onto the network.

Rebooting in 2.6.27.9 resolves the problem for me.

Tags:

Revision history for this message

Florian Diesch (diesch) wrote on 2009-01-09:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

Changed in linux-backports-modules-2.6.27:
status:	New → Incomplete

Revision history for this message

TimWintle (timwintle) wrote on 2009-01-09:

dmesg.log Edit (38.6 KiB, text/plain)

Revision history for this message

TimWintle (timwintle) wrote on 2009-01-09:

lspci-vvnn.log Edit (20.7 KiB, text/plain)

Revision history for this message

TimWintle (timwintle) wrote on 2009-01-09:

uname is

Linux tim-aspire 2.6.27-11-generic #1 SMP Fri Dec 19 16:29:52 UTC 2008 i686 GNU/Linux

( Sorry for not sending the info to begin with - I didn't have ethernet or any external storage devices to transfer the data over or I'd have used the command line tool. )

Revision history for this message

Florian Diesch (diesch) wrote on 2009-01-09:

No problem - it's nice that you take the time to file a bug report.

There seems to be a problem with the MAC when the module is loaded:

[ 4.680662] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 4.680701] r8169 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 4.680736] r8169 0000:02:00.0: setting latency timer to 64
[ 4.680758] r8169 0000:02:00.0: unknown MAC (27a00000)
[ 4.681625] eth0: RTL8169 at 0xe0040000, 00:1e:68:bd:74:c9, XID 24a00000 IRQ 219

and lspci reports a problem, too:

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: r8169
Kernel modules: r8169

Could you please add the dmesg.log and lspci-vvnn.log for the working kernel? Thank you! :-)

Revision history for this message

Florian Diesch (diesch) wrote on 2009-01-09:

This may be related to Bug #288845 and maybe Bug #286489

Revision history for this message

Florian Diesch (diesch) wrote on 2009-01-10:

Mots likely it's a duplicate of #313866

Revision history for this message

TimWintle (timwintle) wrote on 2009-01-11:

dmesg_working.log Edit (37.5 KiB, text/plain)

working dmesg

Revision history for this message

TimWintle (timwintle) wrote on 2009-01-11:

lspci-vvnn_working.log Edit (11.7 KiB, text/plain)

working lspci-vvnn

Revision history for this message

Florian Diesch (diesch) wrote on 2009-01-12:

#10

Thank you. The logs show that this is indeed a duplicate of bug #313866, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.