[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#386972: marked as done (Networking on old machines requires "acpi=off")

Your message dated Thu, 8 May 2008 23:11:19 +0200
with message-id <20080508211119.GK13915@stro.at>
and subject line Re: Networking on old machines requires "acpi=off"
has caused the Debian Bug report #386972,
regarding Networking on old machines requires "acpi=off"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
386972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386972
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.16-2-686-smp
Version: 2.6.16-18
Severity: grave
Justification: causes debilitating loss of functionality

Greetings,

I just upgraded a machine from sarge to etch, and in the process
upgraded from 2.6.8 to 2.6.16.  When I rebooted, and on multiple reboots
since, the network has been completely non-functional.  The kernel seems
to sense the wire, but is unable to send or receive packets.

The machine has two interfaces: an Intel Ethernet Pro 100 and Realtek
8139 compatible.  On boot, it loads e100, 8139cp and
8139too.  /etc/modules does not have any network modules (needs eepro100
for 2.6.8, but I removed it, no change).  The relevant lspci listings
are:

00:09.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 05)
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

lspci -v shows that the RTL8139 shares IRQ 10 with the USB controller
(Intel 82371AB/EB/MB PIIX4), and the eepro100 shares IRQ 11 with the
video card (Voodoo 3).

Trying to configure the network:

e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
then the usual DHCP messages, with DHCPDISCOVER repeated to failure.

"dmesg | grep eth" gives:

eth0: RealTek RTL8139 at 0xe800, 00:40:f4:15:2d:e5, IRQ 10
eth0:  Identified 8139 chip type 'RTL-8139C'
e100: eth1: e100_probe: addr 0xeb100000, irq 11, MAC addr 00:00:AC:A6:0B:DD
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
eth1: link down
ADDRCONF(NETDEV_UP): eth1: link is not ready
eth0: no IPv6 routers present
eth0: no IPv6 routers present

DHCP also fails on eth1.  With a static address, no packets get in or
out, on eth0 or eth1.

[2.6.16 also hung twice in the course of working on this, console cursor
still blinking but the keyboard dead.  2.6.8 has never hung on me, under
sarge or etch.]

Both interfaces still work perfectly with 2.6.8, but of course hotplug,
gamin, etc. don't...

Please let me know what other information you need to try to resolve
this.

Thank you,
-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Welcome to the best software in the world today cafe!
http://www.take6.com/albums/greatesthits.html

--- End Message ---
--- Begin Message --- 
Version: 2.6.24-1

marked fixed upstream, if still reproducible with 2.6.25 or
newer please holler upstream too.

thanks

-- 
maks

--- End Message ---
Reply to: