Riku Voipio wrote:
> On Tue, Nov 18, 2008 at 01:37:11PM +0100, Martin Michlmayr wrote:
>> 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 INT
On Tue, Nov 18, 2008 at 01:37:11PM +0100, Martin Michlmayr wrote:
> 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/ifp
* Ross Burton <[EMAIL PROTECTED]> [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
* Ross Burton <[EMAIL PROTECTED]> [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.
OK, I can reproduce it and it's a regression from 2.6.25.
--
Martin Michlmayr
http://www.cyrius.com/
--
To
On Mon, 2008-11-17 at 11:31 +0100, Martin Michlmayr wrote:
> * Ross Burton <[EMAIL PROTECTED]> [2008-11-16 15:47]:
> > On Sun, 2008-11-16 at 13:07 +, Ross Burton wrote:
> > > I'm going to try an flash an older kernel and hope that fixes it now...
> >
> > I discovered that ifplugd was causing t
* Ross Burton <[EMAIL PROTECTED]> [2008-11-16 15:47]:
> On Sun, 2008-11-16 at 13:07 +, Ross Burton wrote:
> > I'm going to try an flash an older kernel and hope that fixes it now...
>
> I discovered that ifplugd was causing this, I'm guessing a locking bug
> in r8139.ko? I've disabled ifplugd
On Sun, 2008-11-16 at 13:07 +, Ross Burton wrote:
> I'm going to try an flash an older kernel and hope that fixes it now...
I discovered that ifplugd was causing this, I'm guessing a locking bug
in r8139.ko? I've disabled ifplugd for now and it is booting again. Is
this is a known issue or s
Hi,
I finally got around to putting a serial port onto my semibricked N2100
and got a log of the boot. Attached is the full log, the interesting
line is:
[42949526.36] BUG: scheduling while atomic: swapper/0/0x0100
:(
I'm going to try an flash an older kernel and hope that fixes it now
8 matches
Mail list logo