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

Bug#606279: marked as done (seems to think everything is a hotpluggable interface)

Your message dated Wed, 22 Dec 2010 16:24:19 -0400
with message-id <20101222202419.GA2843@gnu.kitenet.net>
and subject line Re: seems to think everything is a hotpluggable interface
has caused the Debian Bug report #606279,
regarding seems to think everything is a hotpluggable interface
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.)


-- 
606279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606279
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: hw-detect
Version: 1.83
Severity: normal

It's typical for netcfg to put allow-hotplug in /etc/network/interfaces
for the interface d-i was installed on IME. I get the sense that 
hw-detect.hotplug is buggy somehow:

Dec  3 16:13:37 net/hw-detect.hotplug: Detected hotpluggable network interface lo
Dec  3 16:13:54 net/hw-detect.hotplug: Detected hotpluggable network interface lo
Dec  3 16:13:54 net/hw-detect.hotplug: Detected hotpluggable network interface wlan0
Dec  3 16:14:42 netcfg[4454]: INFO: Detected wlan0 as a hotpluggable device
Dec  4 01:15:22 net/hw-detect.hotplug: Detected hotpluggable network interface wlan0
Dec  4 01:15:22 net/hw-detect.hotplug: Detected hotpluggable network interface lo

This can result in ifup -a not upping it on boot, and a hotplug event
never bringing it up either.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Colin Watson wrote:
> > This can result in ifup -a not upping it on boot, and a hotplug event
> > never bringing it up either.
> 
> I wonder why the latter isn't happening?  If you're getting a udev event
> in d-i, you should get one in the installed system too.  That should hit
> /lib/udev/rules.d/80-drivers.rules, call /lib/udev/net.agent, and that
> should bring up the interface.
> 
> It might be worth tracing that chain to find out which bit is breaking.
> hw-detect and netcfg seem OK here at least in principle.

Yeah, I think I was mistaken, ifup seems to be running, it's just that
dhclient runs in the background and can give up within a second or 2, so
there is no indication of why the network might not come up.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: