From: Bartlomiej Solarz-Niesluchowski <B.Solarz-Niesluchowski@wsisiz.edu.pl>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Lukasz Trabinski <lukasz@wsisiz.edu.pl>,
akpm@zip.com.au, Andreas Dilger <adilger@clusterfs.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-pre3 - problems with ext3 (long)
Date: Tue, 21 Jan 2003 15:54:49 +0100 [thread overview]
Message-ID: <5.2.0.9.0.20030121155241.02be03c0@oceanic.wsisiz.edu.pl> (raw)
In-Reply-To: <1043159893.2424.59.camel@sisko.scot.redhat.com>
At 14:38 2003-01-21 +0000, Stephen C. Tweedie wrote:
>Hi,
>
>On Tue, 2003-01-21 at 14:22, Bartlomiej Solarz-Niesluchowski wrote:
> > At 13:56 2003-01-21 +0000, Stephen C. Tweedie wrote:
> >
> > >If that happens again, serial console is the best way of getting the
> > >full oops. How much memory does your system have? Have you ever seen
> > >this error before?
> >
> > Yes - we have seen this error before.....
>
>Well, the kmap() bug looks like kunmap() being done twice on a page. If
>that's happening, we really do need to find out where, so capturing that
>trace via serial console would be a _big_ help, thanks.
OK I make serial console especially for this.... - see you soon (I think
that my system will have crash about tomorrow (est. uptime now is about 3-4
days)).....
--
Bartlomiej Solarz-Niesluchowski, Administrator WSISiZ
e-mail: B.Solarz-Niesluchowski@wsisiz.edu.pl
next prev parent reply other threads:[~2003-01-21 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 13:15 2.4.21-pre3 - problems with ext3 Lukasz Trabinski
2003-01-14 15:15 ` Stephen C. Tweedie
2003-01-14 15:48 ` Lukasz Trabinski
2003-01-20 22:38 ` Stephen C. Tweedie
2003-01-21 0:25 ` 2.4.21-pre3 - problems with ext3 (long) Lukasz Trabinski
2003-01-21 13:56 ` Stephen C. Tweedie
2003-01-21 14:22 ` Bartlomiej Solarz-Niesluchowski
2003-01-21 14:38 ` Stephen C. Tweedie
2003-01-21 14:54 ` Bartlomiej Solarz-Niesluchowski [this message]
2003-02-06 15:47 ` Bartlomiej Solarz-Niesluchowski
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=5.2.0.9.0.20030121155241.02be03c0@oceanic.wsisiz.edu.pl \
--to=b.solarz-niesluchowski@wsisiz.edu.pl \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz@wsisiz.edu.pl \
--cc=sct@redhat.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
all inboxes | Powered by JetHome®