From: Vladimir Saveliev <vs@namesys.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4.23] kernel BUG at page_alloc.c:235!
Date: Tue, 9 Dec 2003 19:07:04 +0300 [thread overview]
Message-ID: <200312091907.04707.vs@namesys.com> (raw)
In-Reply-To: <20031209165926.18a5c3fa.skraw@ithnet.com>
On Tuesday 09 December 2003 18:59, Stephan von Krawczynski wrote:
> On Mon, 8 Dec 2003 19:39:07 +0300
> Vladimir Saveliev <vs@namesys.com> wrote:
>
> > Hi
> >
> > A program which reads spontaneously 4k blocks from a device (sda1) causes the following quite fast.
>
> > [...]
> > Ksymoops provides
> >
> > vs@tribesman:/tmp/> ksymoops -m System.map file2 -V -O -K
> > ksymoops 2.4.9 on i686 2.4.21-144-default. Options used
>
> What kind of a kernel is this? Are you sure you are running 2.4.23 ?
>
Yes, oops happened on 2.4.23. I ksymoopsed it with proper System.map having 2.4.21-144 running, though
>
> Regards,
> Stephan
>
>
next prev parent reply other threads:[~2003-12-09 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 16:39 [2.4.23] kernel BUG at page_alloc.c:235! Vladimir Saveliev
2003-12-08 18:17 ` Marcelo Tosatti
2003-12-09 15:59 ` Stephan von Krawczynski
2003-12-09 16:07 ` Vladimir Saveliev [this message]
2003-12-15 11:24 ` Marcelo Tosatti
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=200312091907.04707.vs@namesys.com \
--to=vs@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
/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