From: Con Kolivas <kernel@kolivas.org>
To: Alexander Skwar <listen@alexander.skwar.name>
Cc: linux-kernel@vger.kernel.org, pi@pihost.us
Subject: Re: Another report of "kernel BUG at mm/slab.c:2839!".
Date: Thu, 27 Oct 2005 09:25:26 +1000 [thread overview]
Message-ID: <200510270925.26773.kernel@kolivas.org> (raw)
In-Reply-To: <435F8316.9020006@mid.message-center.info>
On Wed, 26 Oct 2005 11:22 pm, Alexander Skwar wrote:
> Hello.
>
> Just like Anthony Martinez <pi <at> pihost.us> reported
> at 2005-09-24 17:35:43, I'm also hitting kernel BUG at mm/slab.c:2839!.
>
> I cannot really reproduce it. It just happens from
> time to time.
>
> [15:21:02 vz6tml@dewup-ww02:~] $ uname -a
> Linux dewup-ww02 2.6.13-ck8.03.reiser-stat.megaraid_newgen.no-preempt #2
> SMP Mon Oct 24 10:01:43 CEST 2005 i686 Intel(R) Xeon(TM) CPU 2.40GHz
> GenuineIntel GNU/Linux
>
> [15:21:30 vz6tml@dewup-ww02:~] $ cat /proc/version
> Linux version 2.6.13-ck8.03.reiser-stat.megaraid_newgen.no-preempt
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If you were running a vanilla kernel you'd get full support from the mailing
list. If you were running plain ck8 I could offer you limited support. But
adding your own patches makes it impossible for us to know what your code
looks like and that you haven't merged incompatible code wrongly. Only the
person who merged the code would be able to provide you with support.
My advice to you is try a mainline kernel release that has the features you
need and see if the bug exists. Then you'll get more response from the
mailing list.
Cheers,
Con
next prev parent reply other threads:[~2005-10-26 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 13:22 Another report of "kernel BUG at mm/slab.c:2839!" Alexander Skwar
2005-10-26 23:25 ` Con Kolivas [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-26 18:59 Alexander Skwar
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=200510270925.26773.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=listen@alexander.skwar.name \
--cc=pi@pihost.us \
/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