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

Bug#322723: marked as done ('ip route' kernel problem w/ gcc-4.0)

Your message dated Wed, 29 Mar 2006 16:37:53 +0200
with message-id <200603291637.54487.aragorn@tiscali.nl>
and subject line Bug#322723: 'ip route' kernel problem w/ gcc-4.0
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: dhcp-client-udeb
Version: 2.0pl5-19.1
Severity: serious
Tags: d-i

Installations for 1386 using current daily builds (using 2.6.12) are 
failing with a screen saying "no default route could be set".
The cause for this is that in /etc/dhclient the 'ip route add' command is 
failing. It returns "ip: RTNETLINK answers: Network is unreachable".

This problem has been seen both on real hardware (like my laptop) and both 
qemu and vmware. I'm able to reproduce it consistently. I've never seen 
the problem during installations using images based on 2.6.8 or 2.6.11.
It happens both when using DHCP and for static net configuration.

I've been trying to trace the problem using several different daily 
netinst images (using 2.6.12) and the official Sarge netinst (using 
2.6.8) for comparison and using different network devices/modules.

The error happens both when dhclient is run from netcfg and when it's run 
from VT2 in busybox. A log with set -x in /etc/dhclient-script is 
attached.

I've also run an strace on the 'ip route add' command. Attached are an 
strace for the failed command and one for a successful command from a 
2.6.8 install.

Currently I'm unsure whether this is a kernel problem, a d-i problem, a 
busybox problem and/or related to other changes in unstable (like gcc 
transition). I've reached the end of my skills, somebody else needs to 
take over from here.
I'm submitting this bug against dhcp-client-udeb because that's where it 
manifests itself, but feel free to add info and reassign.


Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

+ set -e
+ [ -n  ]
+ [ -n  ]
+ [ -n  ]
+ [ -n  ]
+ ip link set lo up
+ sleep 1
+ exit 0
+ set -e
+ [ -n  ]
+ [ -n  ]
+ [ -n  ]
+ [ -n  ]
+ ip link set eth0 up
+ sleep 1
+ exit 0
Listening on LPF/lo/<null>
Sending on   LPF/lo/<null>
Listening on LPF/eth0/00:0c:29:cb:57:af
Sending on   LPF/eth0/00:0c:29:cb:57:af
Sending on   Socket/fallback/fallback-net
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 6
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 172.16.249.254
+ set -e
+ [ -n 255.255.255.0 ]
+ ptom 255.255.255.0
+ new_mask=/24
+ [ -n  ]
+ [ -n 172.16.249.255 ]
+ new_broadcast_arg=broadcast 172.16.249.255
+ [ -n  ]
+ set_hostname
+ cat /proc/sys/kernel/hostname
+ local current_hostname=
+ [ -z  ]
+ echo 
+ [ -n  ]
+ [ -n  ]
+ [ -z  ]
+ ip link set eth0 up
+ ip addr flush dev eth0
+ ip addr add 172.16.249.130/24 broadcast 172.16.249.255 dev eth0
+ ip route add default via 172.16.249.2
ip: RTNETLINK answers: Network is unreachable
bound to 172.16.249.130 -- renewal in 900 seconds.

Attachment: dhclient_2.6.12.strace.gz
Description: GNU Zip compressed data

Attachment: dhclient_2.6.8.strace.gz
Description: GNU Zip compressed data

Attachment: pgp2lLxPxK1Iv.pgp
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On Saturday 25 March 2006 00:30, Falk Hueffner wrote:
> is this still reproducible with current 4.0 or 4.1? If so, how?

No, it looks like the problem has been resolved. Closing the BR.
I've reverted the workaround we introduced in the installer for the issue.
Thanks for the reminder.

Cheers,
FJP

Attachment: pgpQ973wDy4DC.pgp
Description: PGP signature


--- End Message ---
Reply to: