From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] oopses in 2.6.19.1
Date: Mon, 15 Jan 2007 18:06:20 +0100 [thread overview]
Message-ID: <200701151806.20526.philipp.reisner@linbit.com> (raw)
In-Reply-To: <20070111180322.GD15730@kwaak.net>
> Kernel BUG at ...ed/kernel/tyan-s2891/modules/drbd/drbd/lru_cache.c:312
> invalid opcode: 0000 [1] SMP
> CPU 1
> Modules linked in: drbd sha1 cn ipv6 tg3
>
[...]
Hi Ard,
Although I can not reproduce this crash here, I was able to trigger
"LOGIC BUG" Messages, by finishing the resync by by application-IO...
This bug fixes (at least parts of) the problem.
http://lists.linbit.com/pipermail/drbd-cvs/2007-January/001434.html
Could you verify if this patch changes the situation for you ?
-Phil
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
next prev parent reply other threads:[~2007-01-15 17:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 12:31 [Drbd-dev] drbd 2.6.19 crypto changes Ard van Breemen
2007-01-10 13:48 ` Lars Ellenberg
2007-01-10 16:09 ` Ard van Breemen
2007-01-10 19:33 ` Ard van Breemen
2007-01-10 16:23 ` Philipp Reisner
2007-01-10 20:17 ` Ard van Breemen
2007-01-11 14:38 ` Ard van Breemen
2007-01-11 17:12 ` Ard van Breemen
2007-01-11 18:03 ` [Drbd-dev] oopses in 2.6.19.1 Ard van Breemen
2007-01-12 13:53 ` Philipp Reisner
2007-01-15 17:06 ` Philipp Reisner [this message]
2007-01-16 10:37 ` Ard van Breemen
2007-01-25 17:45 ` Ard van Breemen
2007-01-25 21:32 ` Lars Ellenberg
2007-01-25 22:26 ` Lars Ellenberg
2007-01-28 10:59 ` Ard van Breemen
2007-01-28 11:38 ` Ard van Breemen
[not found] ` <20070126142857.GE9639@kwaak.net>
2007-01-26 14:34 ` Ard van Breemen
2007-02-11 21:55 ` Ard van Breemen
2007-01-12 13:50 ` [Drbd-dev] drbd 2.6.19 crypto changes Philipp Reisner
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=200701151806.20526.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=drbd-dev@lists.linbit.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 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.