Re: [PATCH] trim memory not covered by WB MTRRs

On Wed, 6 Jun 2007 15:28:43 -0700 Jesse Barnes wrote:

> On Wednesday, June 6, 2007 3:26 pm Justin Piszcz wrote:
> > Nope, I booted with only netconsole= options.  I have a lot of HW in
> > the box and I guess the buffer is too small.  Not sure where to
> > change it in the kernel.  Looking..
> 
> It's called "kernel log buffer size" and it's in "General setup".

or you can just boot with "log_buf_len=256k" on the kernel boot line (e.g.)

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] trim memory not covered by WB MTRRs
    • From: Justin Piszcz <[email protected]>
  • Re: [PATCH] trim memory not covered by WB MTRRs
    • From: Justin Piszcz <[email protected]>

• References:
  • [PATCH] trim memory not covered by WB MTRRs
    • From: Jesse Barnes <[email protected]>
  • Re: [PATCH] trim memory not covered by WB MTRRs
    • From: Jesse Barnes <[email protected]>
  • Re: [PATCH] trim memory not covered by WB MTRRs
    • From: Justin Piszcz <[email protected]>
  • Re: [PATCH] trim memory not covered by WB MTRRs
    • From: Jesse Barnes <[email protected]>

• Prev by Date: Re: [PATCH] trim memory not covered by WB MTRRs
• Next by Date: Re: [PATCH 00/10] Containers(V10): Generic Process Containers
• Previous by thread: Re: [PATCH] trim memory not covered by WB MTRRs
• Next by thread: Re: [PATCH] trim memory not covered by WB MTRRs
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]