dhcpcd stops working if I install 2.4.4. Replacing the 2.4.4 version of
8139too.c with the 2.4.3 version and leaving everything else exactly
the same gets things working again. Configuring the interface by hand
after dhcpcd has timed out also works. Has anyone else seen this?
ISC DHCP 2.0, kernel compiled with gcc 2.95.2
lspci:
00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 8139 (rev 10)
Boot messages with 2.4.3 version:
8139too Fast Ethernet driver 0.9.15c loaded
PCI: Found IRQ 5 for device 00:12.0
eth0: RealTek RTL8139 Fast Ethernet at 0xc9804f00, 00:10:a7:05:8e:da, IRQ 5
eth0: Identified 8139 chip type 'RTL-8139C'
Boot messages with 2.4.4 version:
8139too Fast Ethernet driver 0.9.16
PCI: Found IRQ 5 for device 00:12.0
eth0: RealTek RTL8139 Fast Ethernet at 0xc9804f00, 00:10:a7:05:8e:da, IRQ 5
eth0: Identified 8139 chip type 'RTL-8139C'
Michael Gordon
On Sat, 28 Apr 2001, Michael F Gordon wrote:
> dhcpcd stops working if I install 2.4.4. Replacing the 2.4.4 version of
> 8139too.c with the 2.4.3 version and leaving everything else exactly
> the same gets things working again. Configuring the interface by hand
> after dhcpcd has timed out also works. Has anyone else seen this?
I noticed this in 2.4.3-acX series as well. But here's the funny part:
When dhcp starts up during bootup it doesn't work. But as
soon as I log in and do a su -c '/etc/rc.d/init.d/network restart' there's
instant success!
This is on Mandrake 8.0
It doesn't make much sense to me.
--
Garett
> ISC
DHCP 2.0, kernel compiled with gcc 2.95.2 >
> lspci:
> 00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 8139 (rev 10)
>
> Boot messages with 2.4.3 version:
> 8139too Fast Ethernet driver 0.9.15c loaded
> PCI: Found IRQ 5 for device 00:12.0
> eth0: RealTek RTL8139 Fast Ethernet at 0xc9804f00, 00:10:a7:05:8e:da, IRQ 5
> eth0: Identified 8139 chip type 'RTL-8139C'
>
> Boot messages with 2.4.4 version:
> 8139too Fast Ethernet driver 0.9.16
> PCI: Found IRQ 5 for device 00:12.0
> eth0: RealTek RTL8139 Fast Ethernet at 0xc9804f00, 00:10:a7:05:8e:da, IRQ 5
> eth0: Identified 8139 chip type 'RTL-8139C'
>
>
>
> Michael Gordon
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
I too have this problem. The first time dhcpcd is executed it fails due
to timeout.
If we execute it again it works fine. Looks like the first packets
sent/received through the interface don't get treated right.
If I reverse the 2.4.4 patch to 2.4.3 it starts working well again.
Something's up with the realtek driver update I would say.
I'm not on the list so please CC me replys.
Thanks.
------------
Andr? Cruz
what sort of switch are you plugged into? some Cisco switches have a
'feature' that ignores all traffic from a port for X seconds after a
machine is plugged in / powered on on a port (they claim somehting about
preventing loops) it may be that the new kernel now boots up faster then
the old one so that the DHCP request is lost in the switch, a few seconds
later when you do it by hand the swich has enabled your port and
everything works.
David Lang
On Sat, 28 Apr 2001, Garett Spencley
wrote:
> Date: Sat, 28 Apr 2001 11:44:58 -0400 (EDT)
> From: Garett Spencley <[email protected]>
> To: Michael F Gordon <[email protected]>
> Cc: [email protected]
> Subject: Re: 2.4.4 breaks dhcpcd with Realtek 8139
>
> On Sat, 28 Apr 2001, Michael F Gordon wrote:
>
> > dhcpcd stops working if I install 2.4.4. Replacing the 2.4.4 version of
> > 8139too.c with the 2.4.3 version and leaving everything else exactly
> > the same gets things working again. Configuring the interface by hand
> > after dhcpcd has timed out also works. Has anyone else seen this?
>
> I noticed this in 2.4.3-acX series as well. But here's the funny part:
> When dhcp starts up during bootup it doesn't work. But as
> soon as I log in and do a su -c '/etc/rc.d/init.d/network restart' there's
> instant success!
>
> This is on Mandrake 8.0
>
> It doesn't make much sense to me.
>
> --
> Garett
>
> > ISC
> DHCP 2.0, kernel compiled with gcc 2.95.2 >
> > lspci:
> > 00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 8139 (rev 10)
> >
> > Boot messages with 2.4.3 version:
> > 8139too Fast Ethernet driver 0.9.15c loaded
> > PCI: Found IRQ 5 for device 00:12.0
> > eth0: RealTek RTL8139 Fast Ethernet at 0xc9804f00, 00:10:a7:05:8e:da, IRQ 5
> > eth0: Identified 8139 chip type 'RTL-8139C'
> >
> > Boot messages with 2.4.4 version:
> > 8139too Fast Ethernet driver 0.9.16
> > PCI: Found IRQ 5 for device 00:12.0
> > eth0: RealTek RTL8139 Fast Ethernet at 0xc9804f00, 00:10:a7:05:8e:da, IRQ 5
> > eth0: Identified 8139 chip type 'RTL-8139C'
> >
> >
> >
> > Michael Gordon
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Sat, Apr 28, 2001 at 11:29:15AM -0700, David Lang wrote:
> what sort of switch are you plugged into? some Cisco switches have a
> 'feature' that ignores all traffic from a port for X seconds after a
> machine is plugged in / powered on on a port (they claim somehting about
> preventing loops) it may be that the new kernel now boots up faster then
> the old one so that the DHCP request is lost in the switch, a few seconds
> later when you do it by hand the swich has enabled your port and
> everything works.
I'm plugged in to a cable modem, with the DHCP server at the ISP. The
server requires the MAC address to be registered, so sending the DHCP
request with a different MAC address could cause the symptoms. I doubt
it's a timing problem - replacing the 8139 driver with the 2.4.3 version
but otherwise using the distributed 2.4.4 makes DHCP work as expected.
Michael Gordon
On Sat, Apr 28, 2001 at 11:11:51PM +0100, Michael F Gordon wrote:
> On Sat, Apr 28, 2001 at 11:29:15AM -0700, David Lang wrote:
> > what sort of switch are you plugged into? some Cisco switches have a
> > 'feature' that ignores all traffic from a port for X seconds after a
> > machine is plugged in / powered on on a port (they claim somehting about
> > preventing loops) it may be that the new kernel now boots up faster then
> > the old one so that the DHCP request is lost in the switch, a few seconds
> > later when you do it by hand the swich has enabled your port and
> > everything works.
>
> I'm plugged in to a cable modem, with the DHCP server at the ISP. The
> server requires the MAC address to be registered, so sending the DHCP
> request with a different MAC address could cause the symptoms. I doubt
> it's a timing problem - replacing the 8139 driver with the 2.4.3 version
> but otherwise using the distributed 2.4.4 makes DHCP work as expected.
The Windows drivers distributed along with that Realtek cards
have this problem[1] any many users of the CSN[2] run into the
"secure mode" on our hubs/switches, causing their port to be
disabled.
So we have just ported a BUG from Windows to Linux, if you are
right ;-)
BTW: CC'ed the maintainer. He might be interested, as maintainers
usally are on BUGs ;-)
Regards
Ingo Oeser
[1] Sometimes forgetting their MAC and sending either random or
zero MAC out. This depends on whatever.
[2] Chemnitz Students Network - large LAN with >1000 computers
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< been there and had much fun >>>>>>>>>>>>
> I'm plugged in to a cable modem, with the DHCP server at the ISP. The
> server requires the MAC address to be registered, so sending the DHCP
> request with a different MAC address could cause the symptoms. I doubt
> it's a timing problem - replacing the 8139 driver with the 2.4.3 version
> but otherwise using the distributed 2.4.4 makes DHCP work as expected.
I meant to get back sooner. I'm also plugged into a cable modem (though
trhough a 5 port hub). Same symptoms for me.
--
Garett
Garett Spencley <[email protected]> writes:
> On Sat, 28 Apr 2001, Michael F Gordon wrote:
>
> > dhcpcd stops working if I install 2.4.4. Replacing the 2.4.4 version of
> > 8139too.c with the 2.4.3 version and leaving everything else exactly
> > the same gets things working again. Configuring the interface by hand
> > after dhcpcd has timed out also works. Has anyone else seen this?
>
> I noticed this in 2.4.3-acX series as well. But here's the funny part:
> When dhcp starts up during bootup it doesn't work. But as
> soon as I log in and do a su -c '/etc/rc.d/init.d/network restart' there's
> instant success!
>
> This is on Mandrake 8.0
>
> It doesn't make much sense to me.
you may want to report the bug at :
https://qa.mandrakesoft.com/