From: Andrew Morton <akpm@zip.com.au>
To: Arjan Opmeer <a.d.opmeer@student.utwente.nl>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: Anyone else seen VM related oops on 2.4.18?
Date: Sun, 24 Mar 2002 17:52:26 -0800 [thread overview]
Message-ID: <3C9E82DA.99D53C94@zip.com.au> (raw)
In-Reply-To: <20020325005633.GA1121@Ado.student.utwente.nl> <Pine.LNX.4.44L.0203242200080.18660-100000@imladris.surriel.com> <20020325011139.GA1165@Ado.student.utwente.nl>
Arjan Opmeer wrote:
>
> On Sun, Mar 24, 2002 at 10:01:09PM -0300, Rik van Riel wrote:
> > On Mon, 25 Mar 2002, Arjan Opmeer wrote:
> >
> > > Are there other people that are suffering from a VM related oops on
> > > kernel 2.4.18?
> > >
> > > ... I am just trying to find out whether the kernel or the driver
> > > upgrade is causing this problem.
> >
> > Well, can you reproduce the problem without the NVidia driver ?
>
> I am waiting... :)
>
Please ensure that the kernel was built with `verbose BUG reporting',
under the kernel hacking menu.
And when it happens again, make sure that you take note
of the line number at which it's hitting the BUG(). It'll
be `Kernel BUG at page_alloc.c:NNN'.
-
next prev parent reply other threads:[~2002-03-25 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 0:56 Anyone else seen VM related oops on 2.4.18? Arjan Opmeer
2002-03-25 1:01 ` Rik van Riel
2002-03-25 1:11 ` Arjan Opmeer
2002-03-25 1:52 ` Andrew Morton [this message]
2002-03-25 3:16 ` Arjan Opmeer
-- strict thread matches above, loose matches on Subject: below --
2002-03-27 9:58 Stas Sergeev
2002-03-27 11:24 ` Mike Galbraith
2002-03-27 12:27 Stas Sergeev
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=3C9E82DA.99D53C94@zip.com.au \
--to=akpm@zip.com.au \
--cc=a.d.opmeer@student.utwente.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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