From: David Ford <david@linux.com>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/REQ] Increase kmsg buffer from 16K to 32K, kernel/printk.c
Date: Wed, 31 Jan 2001 15:12:32 -0800 [thread overview]
Message-ID: <3A789BE0.2727B585@linux.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1010131181206.16241A-100000@delta.ds2.pg.gda.pl>
"Maciej W. Rozycki" wrote:
> On Wed, 31 Jan 2001, Alan Cox wrote:
>
> > > Does Linus or anyone object to raising the ksmg buffer from 16K to 32K?
> > > 4/5 systems I have now overflow the buffer during boot before init is
> > > even launched.
> >
> > Thats just an indication that 2.4.x is currently printking too much crap on
> > boot
>
> We could probably get rid of much of the crap for i386 by #undef
> APIC_DEBUG in include/asm-i386/apic.h. Too bad broken SMP systems get
> reported every now and then and the crap proves useful in getting what
> actually is wrong.
The largest bodies of text come from scsi, irda, usb, and udf.
The LP/parport could stand being trimmed too.
The fatfs barfs out bogus cluster size messages when I don't have any FAT type
filesystems.
Question is, If I submit patches to tidy up the boot messages, when will(can)
they be applied? 2.4 or 2.5?
-d
--
There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-31 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 8:01 [PATCH/REQ] Increase kmsg buffer from 16K to 32K, kernel/printk.c David Ford
2001-01-31 17:06 ` Alan Cox
2001-01-31 17:19 ` Maciej W. Rozycki
2001-01-31 23:12 ` David Ford [this message]
2001-01-31 17:21 ` Gabor Lenart
2001-01-31 20:46 ` Rik van Riel
2001-01-31 20:58 ` Mark Hahn
2001-02-03 19:41 ` Paul Gortmaker
[not found] <cs.lists.linux-kernel/3A72804A.E6052E1B@linux.com>
2001-01-27 10:14 ` Ion Badulescu
2001-01-27 11:45 ` David Ford
-- strict thread matches above, loose matches on Subject: below --
2001-02-01 1:26 Chris Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A789BE0.2727B585@linux.com \
--to=david@linux.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox