From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] kernel BUG at fs/dlm/ast.c:41!
Date: Fri, 24 Nov 2006 09:44:09 +0100 [thread overview]
Message-ID: <4566B0D9.50101@ubuntu.com> (raw)
I guys,
i was able to trigger this with .19-rc6 on a 2node cluster sharing one ip.
Cluster was formed and quored, rebooted the node owning the service to verify
the failover and this lovely message hitted me on the passive node.
[ 160.726237] ------------[ cut here ]------------
[ 160.726293] kernel BUG at fs/dlm/ast.c:41!
[ 160.726349] invalid opcode: 0000 [#1]
[ 160.726404] SMP
[ 160.726537] Modules linked in: nfs nfsd exportfs lockd sunrpc video sbs
i2c_ec i2c_core button battery container ac asus_acpi sctp ipv6 lock_dlm gfs2
dlm configfs nls_utf8 ntfs dm_mod lp af_packet snd_intel8x0 snd_ac97_codec
snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss tsdev
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd
soundcore snd_page_alloc serio_raw parport_pc parport intel_agp agpgart shpchp
pci_hotplug psmouse floppy iTCO_wdt pcspkr evdev ext3 jbd mbcache ide_cd cdrom
ide_disk ata_generic libata piix generic lpfc scsi_transport_fc scsi_mod 3c59x
mii tg3 ehci_hcd uhci_hcd usbcore raid10 raid456 xor raid1 raid0 multipath
linear md_mod thermal processor fan fbcon tileblit font bitblit softcursor
vesafb capability commoncap
[ 160.730558] CPU: 0
[ 160.730559] EIP: 0060:[<e0c3f148>] Not tainted VLI
[ 160.730560] EFLAGS: 00010286 (2.6.19-6-server #2)
[ 160.730737] EIP is at dlm_add_ast+0xd8/0xf0 [dlm]
[ 160.730795] eax: 00000013 ebx: dc5a276c ecx: 00000046 edx: 00000000
[ 160.730855] esi: 00000001 edi: fffefffe ebp: de06fda0 esp: dc697f10
[ 160.730915] ds: 007b es: 007b ss: 0068
[ 160.730971] Process dlm_recoverd (pid: 4013, ti=dc696000 task=dfa1d030
task.ti=dc696000)
[ 160.731032] Stack: e0c4edb1 00000029 e0c4eda4 e0c4d43c ffffc299 dbd45380
dc5a276c e0c42fa6
[ 160.731464] dc5a276c e0c41809 de06fc40 dbd45388 de06feec dc5a276c
de06fc40 de06fc00
[ 160.731897] e0c453e6 e0c4dab8 de06feec 0001027f 00000003 00000001
de06fc88 de06fc78
[ 160.732329] Call Trace:
[ 160.732450] [<e0c42fa6>] _receive_unlock_reply+0x96/0xa0 [dlm]
[ 160.732566] [<e0c453e6>] dlm_recover_waiters_pre+0x236/0x250 [dlm]
[ 160.732683] [<e0c4bbbe>] dlm_recoverd+0x1ee/0x420 [dlm]
[ 160.732804] [<c0137f16>] kthread+0xf6/0x100
[ 160.732911] [<c0103d2f>] kernel_thread_helper+0x7/0x18
[ 160.733015] =======================
[ 160.733073] Code: c7 44 24 04 29 00 00 00 89 44 24 10 c7 04 24 64 d4 c4 e0 e8
7b 51 4e df 89 d8 e8 e4 24 00 00 c7 04 24 b1 ed c4 e0 e8 68 51 4e df <0f> 0b 29
00 a4 ed c4 e0 c7 04 24 c0 d4 c4 e0 e8 84 44 4e df 8d
[ 160.735767] EIP: [<e0c3f148>] dlm_add_ast+0xd8/0xf0 [dlm] SS:ESP 0068:dc697f10
--
I'm going to make him an offer he can't refuse.
reply other threads:[~2006-11-24 8:44 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=4566B0D9.50101@ubuntu.com \
--to=fabbione@ubuntu.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.