public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: "\"Bertrand VIEILLE [Bébert]\"" <Bertrand.Vieille@crans.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unable to handle kernel NULL pointer kernel 2.4.21-pre3-ac4
Date: Thu, 16 Jan 2003 00:53:49 -0800	[thread overview]
Message-ID: <3E26731D.1010104@tupshin.com> (raw)
In-Reply-To: <2973405.67FiTA12eK@adelaide.crans.org>

Bertrand VIEILLE [Bébert] wrote:

>Hello !!
>
>I have the same problem with -ac tree.
>
>Alan Cox said he suspected several things to induce this oops:
>
>* Guess #1 is reverting mm/shmem.c.
>* Guess #2 is reverting the buffer cache changes.
>* Guess #3 is new IDE + highmem
>
no highmem enabled here.

>* Guess #4 is quota related (are people seeing the problem with quota
>disabled ?)
>
I do have quota enabled, so I'll try it without just to double check 
your results.

>
>Personnally, I answered him, I dont'have quota enabled, so Guess #4 doesn't
>exist anymore.
>
>  
>
It's looking like shmem or buffer cache.

The call trace that I posted certainly looks more like the buffer cache, 
but obviously doesn't eliminate shmem as the culprit. Is there an easy 
way to back out one or the other of these changes? I'm happy to do some 
testing.

-Tupshin


       reply	other threads:[~2003-01-16  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030115040016$0ac9@gated-at.bofh.it>
     [not found] ` <20030115071009$2e07@gated-at.bofh.it>
     [not found]   ` <20030115221017$1adf@gated-at.bofh.it>
     [not found]     ` <2973405.67FiTA12eK@adelaide.crans.org>
2003-01-16  8:53       ` Tupshin Harper [this message]
2003-01-15  3:55 Unable to handle kernel NULL pointer kernel 2.4.21-pre3-ac4 Tupshin Harper
2003-01-15  7:08 ` Tupshin Harper
2003-01-15 22:05   ` Tupshin Harper

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=3E26731D.1010104@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=Bertrand.Vieille@crans.org \
    --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