Message-ID: <4416DBC2.8000103@cfl.rr.com>
Date: Tue, 14 Mar 2006 10:05:38 -0500
From: Phillip Susi <psusi@cfl.rr.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Peter Hagervall <hager@cs.umu.se>
CC: CIJOML <cijoml@volny.cz>, linux-kernel@vger.kernel.org
Subject: Re: Dmesg is not showing whole boot list
References: <200603140901.27746.cijoml@volny.cz> <20060314083812.GA27338@brainysmurf.cs.umu.se>
In-Reply-To: <20060314083812.GA27338@brainysmurf.cs.umu.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 838
Lines: 26

Or look in your /var/log/kern.log file instead of asking dmesg.  dmesg 
just dumps the kernel ring buffer which is of finite size.  The entire 
contents should be logged to /var/log/kern.log.

Peter Hagervall wrote:
> On Tue, Mar 14, 2006 at 09:01:27AM +0100, CIJOML wrote:
>> Hello,
>>
>> maybe this si a wrong list to ask, bug after boot, dmesg shows that few lines 
>> at the beginning are missing.
>>
>> Is there any option I can increase to get full dmesg?
> 
> Try increasing CONFIG_LOG_BUF_SHIFT and recompile. That's likely the
> source of your problem.
> 
> 
> 
> 	Peter Hagervall
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/