From: Ali Akcaagac <aliakc@web.de>
To: linux-kernel@vger.kernel.org
Subject: [OOPS] Linux 2.5.74-bk4 & XFS == oops
Date: Sun, 06 Jul 2003 19:31:40 +0200 [thread overview]
Message-ID: <1057512700.827.9.camel@localhost> (raw)
Hello,
This problem is following me since I first played with 2.5 (around
2.5.52). Every now and then the XFS driver causes a Kernel oops. First I
thought this may be a normal issue because it's a development Kernel and
I ignored it because I hoped that this was a known issue and tracked
down one day. But yesterday I had 3-4 of these oops'es in a row and now
I gonna report this in hope to see it fixed really soon.
I compiled kmsgdump-2565.diff into the Kernel (with some minor tweaks)
and tried to force this issue for half a day and guess, as soon as it
comes to demonstration it doesn't happen but I bet my pants that this
problem will show up pretty soon anyways.
Ok I can't show you a full output but I wrote the last one down on
paper.
;-------------------------------
fs/xfs/pagebuf/page_buf.c:1288
Unknown command: 00000000
;-------------------------------
I am not sure for the second line if it should say 'unknown command' but
something like this. Sorry, I can't offer you more right now but better
this than nothing.
reply other threads:[~2003-07-06 17:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1057512700.827.9.camel@localhost \
--to=aliakc@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.