Re: BUG booting 2.6.26-1-iop32x on Thecus N2100

To: Ross Burton <ross@burtonini.com>
Cc: debian-arm@lists.debian.org, riku.voipio@iki.fi
Subject: Re: BUG booting 2.6.26-1-iop32x on Thecus N2100
From: Martin Michlmayr <tbm@cyrius.com>
Date: Tue, 18 Nov 2008 13:37:11 +0100
Message-id: <20081118123711.GJ27693@deprecation.cyrius.com>
In-reply-to: <1226919596.15818.1.camel@blackadder>
References: <1226840840.3439.2.camel@blackadder> <1226850432.3439.5.camel@blackadder> <20081117103142.GP3664@deprecation.cyrius.com> <1226919596.15818.1.camel@blackadder>

* Ross Burton <ross@burtonini.com> [2008-11-17 10:59]:
> Installing ifplugd and setting INTERFACES in /etc/default/ifplugd to
> "auto" causes the bug for me.  auto may well be the default.

It happens because of Riku's LED driver.  When I compile a kernel
without the driver, I can start ifplugd just fine.

Riku, the best way to reproduce this is to install ifplugd (but _not_
change INTERFACES in /etc/default/ifplugd to "auto") and then you can
trigger it with:
  /usr/sbin/ifplugd -i eth0

-- 
Martin Michlmayr
http://www.cyrius.com/

Reply to:

Follow-Ups:
- Re: BUG booting 2.6.26-1-iop32x on Thecus N2100
  - From: Riku Voipio <riku.voipio@iki.fi>

References:
- BUG booting 2.6.26-1-iop32x on Thecus N2100
  - From: Ross Burton <ross@burtonini.com>
- Re: BUG booting 2.6.26-1-iop32x on Thecus N2100
  - From: Ross Burton <ross@burtonini.com>
- Re: BUG booting 2.6.26-1-iop32x on Thecus N2100
  - From: Martin Michlmayr <tbm@cyrius.com>
- Re: BUG booting 2.6.26-1-iop32x on Thecus N2100
  - From: Ross Burton <ross@burtonini.com>

Prev by Date: Re: BUG booting 2.6.26-1-iop32x on Thecus N2100
Next by Date: Re: BUG booting 2.6.26-1-iop32x on Thecus N2100
Previous by thread: Re: BUG booting 2.6.26-1-iop32x on Thecus N2100
Next by thread: Re: BUG booting 2.6.26-1-iop32x on Thecus N2100
Index(es):
- Date
- Thread