public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5-ac12 kernel oops
Date: Tue, 26 Jun 2001 00:33:14 -0700 (PDT)	[thread overview]
Message-ID: <20010626073314.C208C7846A@mail.clouddancer.com> (raw)
In-Reply-To: <9h7oho$9dc$1@ns1.clouddancer.com>
In-Reply-To: <730.993486023@ocs3.ocs-net> Your message of    "Mon, 25 Jun 2001 09:02:19 MST."    <20010625160219.84967784D9@mail.clouddancer.com> <9h7oho$9dc$1@ns1.clouddancer.com>


>>Hmm, I would have thought that /proc was more up to date, because it
>>would reflect changes.  No reboot, never even considered it (I've
>>rescued too many junior sysadmins that think rebooting is _the_ answer).
>
>/proc/ksyms is dynamic, it changes as modules are loaded and unloaded.
>And often the oops is so bad that the machine is dead so reboot is the
>only option, ksyms after reboot may be for a completely different
>kernel.  If you want accurate ksyms and lsmod data to feed into
>ksymoops, 'man insmod' and read section 'KSYMOOPS ASSISTANCE'.

OK, I added the cron task and directory, perhaps I need them sometime.
In any event, thanks for the info.  This certainly seems very well
thought out!


-- 
"Or heck, let's just make the VM a _real_ Neural Network, that self
trains itself to the load you put on the system. Hideously complex and
evil?  Well, why not wire up that roach on the floor, eating that stale
cheese doodle. It can't do any worse job on VM that some of the VM
patches I've seen..."  -- Jason McMullan

ditto

      parent reply	other threads:[~2001-06-26  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-25 15:15 2.4.5-ac12 kernel oops Colonel
2001-06-25 15:41 ` Keith Owens
     [not found] ` <9h7mbt$p2b$1@ns1.clouddancer.com>
2001-06-25 16:02   ` Colonel
2001-06-25 16:20     ` Keith Owens
     [not found]     ` <9h7oho$9dc$1@ns1.clouddancer.com>
2001-06-26  7:33       ` Colonel [this message]

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=20010626073314.C208C7846A@mail.clouddancer.com \
    --to=klink@clouddancer.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