[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#644410: linux-image-2.6.32-5-amd64_2.6.32-35squeeze2_amd64 module drbd.ko



Package: linux-image-2.6.32-5-amd64_2.6.32-35squeeze2_amd64
Version: 2.6.32-35squeeze2
 
When I upgrade the kernel "linux-image-2.6.32-5-amd64_2.6.32-35_amd64 to
linux-image-2.6.32-5-amd64_2.6.32-35squeeze2_amd64",
the kernel-module drbd.ko don't work correctly, no communication between the
cluster-node, no ports (7788 etc) open.
modprobe drbd is ok, but 
 
- error message (console)  
root@backup01:~#
Message from syslogd@backup01 at Sep 30 13:29:11 ...
 kernel:[ 5593.901434] Oops: 0000 [#1] SMP

Message from syslogd@backup01 at Sep 30 13:29:11 ...
 kernel:[ 5593.901437] last sysfs file: /sys/devices/virtual/block/drbd0/range

Message from syslogd@backup01 at Sep 30 13:29:11 ...
 kernel:[ 5593.901546] Stack:

Message from syslogd@backup01 at Sep 30 13:29:11 ...
 kernel:[ 5593.901561] Call Trace:

Message from syslogd@backup01 at Sep 30 13:29:11 ...
 kernel:[ 5593.901588] Code: 89 1d 1a 5e 44 00 48 c7 c7 40 1b 4a 81 5b e9 82 b1
0b 00 41 56 41 55 41 54 49 89 d4 55 53 4c 8b af a0 00 00 00 89 f3 49 8b 45 38
<4c> 8b 70 38 8d 83 10 76 ff ff 83 f8 0f 0f 86 d0 01 00 00 8d 83

Message from syslogd@backup01 at Sep 30 13:29:11 ...
 kernel:[ 5593.901625] CR2: 0000000000000038

Message from syslogd@backup01 at Sep 30 13:29:13 ...
 kernel:[ 5596.160619] Oops: 0000 [#2] SMP

Message from syslogd@backup01 at Sep 30 13:29:13 ...
 kernel:[ 5596.160622] last sysfs file: /sys/devices/virtual/block/drbd1/range

Message from syslogd@backup01 at Sep 30 13:29:13 ...
 kernel:[ 5596.160731] Stack:

Message from syslogd@backup01 at Sep 30 13:29:13 ...
 kernel:[ 5596.160746] Call Trace:

Message from syslogd@backup01 at Sep 30 13:29:13 ...
 kernel:[ 5596.160773] Code: 89 1d 1a 5e 44 00 48 c7 c7 40 1b 4a 81 5b e9 82 b1
0b 00 41 56 41 55 41 54 49 89 d4 55 53 4c 8b af a0 00 00 00 89 f3 49 8b 45 38
<4c> 8b 70 38 8d 83 10 76 ff ff 83 f8 0f 0f 86 d0 01 00 00 8d 83

Message from syslogd@backup01 at Sep 30 13:29:13 ...
 kernel:[ 5596.160810] CR2: 0000000000000038

root@backup02:~#
Message from syslogd@backup02 at Sep 30 13:30:01 ...
 kernel:[  114.114051] ------------[ cut here ]------------

Message from syslogd@backup02 at Sep 30 13:30:01 ...
 kernel:[  114.114061] invalid opcode: 0000 [#1] SMP

Message from syslogd@backup02 at Sep 30 13:30:01 ...
 kernel:[  114.114064] last sysfs file: /sys/fs/o2cb/interface_revision

Message from syslogd@backup02 at Sep 30 13:30:01 ...
 kernel:[  114.114173] Stack:

Message from syslogd@backup02 at Sep 30 13:30:01 ...
 kernel:[  114.114187] Call Trace:

Message from syslogd@backup02 at Sep 30 13:30:01 ...
 kernel:[  114.114227] Code: 83 c3 08 48 83 3b 00 eb ec 48 83 fd 10 0f 86 89 00
00 00 48 89 ef e8 b9 e8 ff ff 48 89 c7 48 8b 00 84 c0 78 13 66 a9 00 c0 75 04
<0f> 0b eb fe 5b 5d 41 5c e9 ac 56 fd ff 48 8b 4c 24 18 4c 8b 4f
 

I am using Debian GNU/Linux 6.0.2.

Mit freundlichen Grüßen

Sven Zimmermann
-------------------------------------------
Städtisches Klinikum Görlitz gGmbH
Abteilung Information und Telekommunikation
Dr.-Ing. Sven Zimmermann
Girbigsdorfer Str. 1-3
02828 Görlitz

Tel: 03581-371266
Fax: 03581-371010
-------------------------------------------------------------------------------------
Staedtisches Klinikum Goerlitz gGmbH
Amtsgericht Dresden / HRB Dresden 4115
Geschaeftsfuehrung: Girbigsdorfer Strasse 1-3; 02828 Goerlitz
Geschaeftsfuehrer: Dipl.-PM (FH) René Bostelaar
Aufsichtsratsvorsitzender: Peter Starre

Telefon: (+49) 03581 / 37-0
Telefax: (+49) 03581 / 37-1109
E-Mail: info@klinikum-goerlitz.de
homepage: http://www.klinikum-goerlitz.de

Die in dieser E-Mail enthaltenen Informationen sind vertraulich. Diese E-Mail ist ausschliesslich fuer den Adressaten bestimmt und jeglicher Zugriff durch andere Personen ist nicht zulaessig. Falls Sie nicht einer der genannten Empfaenger sind, ist jede Veroeffentlichung, Vervielfaeltigung, Verteilung oder sonstige in diesem Zusammenhang stehende Handlung untersagt und unter Umstaenden ungesetzlich. Sollte diese Nachricht nicht fuer Sie bestimmt sein, so bitten wir Sie, den Absender unverzueglich zu informieren und die E-Mail zu loeschen.



Reply to: