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". Jesse - 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: Randy Dunlap <[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: Justin Piszcz <[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
- 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]>
- [PATCH] trim memory not covered by WB MTRRs
- Prev by Date: Re: [PATCH 03/22] 2.6.22-rc3 perfmon2 : new system calls support
- Next by Date: [patch 1/8] fdmap v2 - fdmap core
- 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):
 |