netdev
[Top] [All Lists]

Re: Lockup with 2.6.9-ac15 related to netconsole

To: Mark Broadbent <markb@xxxxxxxxxxxxxx>
Subject: Re: Lockup with 2.6.9-ac15 related to netconsole
From: Francois Romieu <romieu@xxxxxxxxxxxxx>
Date: Tue, 21 Dec 2004 21:48:53 +0100
Cc: mpm@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <49295.192.102.214.6.1103635762.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
References: <34721.192.102.214.6.1103274614.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <20041217215752.GP2767@xxxxxxxxx> <20041217233524.GA11202@xxxxxxxxxxxxxxxxxxxxxxxxxx> <36901.192.102.214.6.1103535728.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <20041220211419.GC5974@xxxxxxxxx> <20041221002218.GA1487@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20041221005521.GD5974@xxxxxxxxx> <52121.192.102.214.6.1103624620.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <20041221123727.GA13606@xxxxxxxxxxxxxxxxxxxxxxxxxx> <49295.192.102.214.6.1103635762.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
Mark Broadbent <markb@xxxxxxxxxxxxxx> :
[...]
> Using the patch supplied I get no hang, just the message 'netconsole
> raced' output to the console and the packet capture proceeds as normal.
> Thanks

The patch is more a bandaid for debugging than a real fix. The netconsole
will drop some messages until its locking is fixed

If you can issue one more test, I'd like to know if some messages appear
on the VGA console around the time at which tcpdump is started (the test
assumes that netconsole is not used/insmoded at all). Please check that
the console log_level is set high enough as it will be really disappointing
if nothing appears :o)

--
Ueimor

<Prev in Thread] Current Thread [Next in Thread>