From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 15:17:59 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65E6A16A417 for ; Wed, 6 Feb 2008 15:17:59 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id BE31213C45E for ; Wed, 6 Feb 2008 15:17:58 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m16FHsSX067365; Wed, 6 Feb 2008 16:17:54 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m16FHslq067364; Wed, 6 Feb 2008 16:17:54 +0100 (CET) (envelope-from olli) Date: Wed, 6 Feb 2008 16:17:54 +0100 (CET) Message-Id: <200802061517.m16FHslq067364@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, jhs@berklix.org In-Reply-To: <200801261540.m0QFepNs021618@fire.js.berklix.net> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 06 Feb 2008 16:17:55 +0100 (CET) Cc: Subject: Re: dmesg : no output on 1 of 2 7-stable boxes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, jhs@berklix.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2008 15:17:59 -0000 Hello Julian, I'm sorry this is a late reply, but I noticed your post on the freebsd-stable list just now. Julian H. Stacey wrote: > One of 2 laptops running 7-stable shows nothing with dmesg, (other is OK). Did you try "dmesg -a"? The dmesg buffer is a circular buffer containing both kernel output and console output. However, "dmesg" displays only the kernel output. If there was lots of console output, it filled all of the dmesg buffer, so "dmesg" displays nothing (all of the kernel output was overwritten by console output). "dmesg -a" will display everything, i.e. kernel + console output. If "dmesg -a" doesn't print anything either, I'm afraid I have no idea what might be wrong. Well, you could try "sysctl -b kern.msgbuf" which will retrieve the raw contents of the dmesg buffer. > - I tried loader.conf kern.msgbuf=64000 I think it must be a multiple of the pages size, i,e, 4K = 4096 on FreeBSD/i386. I usually set it to 65536 or 131072. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Python tricks" is a tough one, cuz the language is so clean. E.g., C makes an art of confusing pointers with arrays and strings, which leads to lotsa neat pointer tricks; APL mistakes everything for an array, leading to neat one-liners; and Perl confuses everything period, making each line a joyous adventure . -- Tim Peters