l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
October 7: Social gathering
Next Installfest:
TBD
Latest News:
Aug. 18: Discounts to "Velocity" in NY; come to tonight's "Photography" talk
Page last updated:
2002 Jan 17 17:22

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Network Configuration
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Network Configuration



begin ME <dugan@passwall.com> 
> On Thu, 17 Jan 2002, Ken Bloom wrote:
> > I didn't say I had a problem with my network card, I just said that
> > `dmesg` didn't say anything about the card. Perhaps you missed it when
> > I said that this ethernet card that `dmesg` didn't report was the one
> > I was using to post my response to the list. So the question lies,
> > what good is the `dmesg` test if it doesn't report a card I know to
> > *is* working?
> 
> dmesg can report kernel boot information (including hardware
> detection) unless your machine has been on a while , or something has been
> logging stuff for dmesg to cause the older stuff to be wiped out.
> 
> You can think of the data available to dmesg as being limited for being
> over-written as new data comes in. Immediately after a boot, assuming
> other things are not complaining, dmesg should show you good detailed
> information about your hardware.
> 
> Perhaps you have more wrong with your box. Check out 
> # dmesg |more
> and see what you have. 
> 
> A properly configured server which has been up for 175 days, has so little
> reported for access with dmesg, that I can see to the top of where my
> kernel was just starting to load. (And this is a busy web server.)
> 
> (Have had other servers with >300 days of uptime that also allow me to see
> the top of my dmesg data from boot >300 days ago.
 
just small note:

on one of my overclocked machines, i get constant APIC errors.  they
aren't fatal; just an annoyance.  they can rapidly fill the kernel ring
log buffer.  i'd say in 2 days, easily.

also, an oft run daemon or program that tries to get kmod to load
something like NLS can really fill up your ring buffer too!   this
machine currently suffers from that.  i've been so busy that i haven't
had a chance to look into what's causing it..  :(

pete
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.