Re: Kernel Panic when accessing NFS share and locking files

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Michael Lang
Date: Thursday, May 15, 2008 - 4:30 am

Arjan van de Ven wrote:

at least 2.6.25-3 also reports it as a kernel bug, but doesn't panic any 
more ...
i attached the whole dmesg to the mail ...
regards

Michael Lang

------------[ cut here ]------------
kernel BUG at fs/locks.c:2051!
invalid opcode: 0000 [1] SMP
CPU 1
Modules linked in: ipt_REJECT iptable_filter ip_tables bridge nfsd 
auth_rpcgss exportfs autofs4 hidp nfs lockd nfs_acl rfcomm l2cap 
bluetooth sunrpc raid1 dm_round_robin tun ip6t_REJECT xt_tcpudp 
ip6table_filter ip6_tables x_tables ib_iser rdma_cm ib_cm iw_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi 
cpufreq_ondemand acpi_cpufreq ipv6 dm_multipath sbs sbshc battery 
acpi_memhotplug ac lp sg floppy ide_cd_mod cdrom serio_raw snd_hda_intel 
parport_pc snd_seq_dummy snd_seq_oss button parport snd_seq_midi_event 
snd_seq snd_seq_device 8139too 8139cp snd_pcm_oss i2c_i801 mii 
snd_mixer_oss snd_pcm i2c_core snd_timer snd pcspkr soundcore shpchp 
snd_page_alloc dm_snapshot dm_zero dm_mirror dm_mod ata_piix libata 
sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd [last unloaded: 
microcode]
Pid: 4763, comm: python Not tainted 2.6.25.3 #1
RIP: 0010:[<ffffffff80299f5d>] [<ffffffff80299f5d>] 
locks_remove_flock+0xe2/0x102
RSP: 0018:ffff81000d1dfe38 EFLAGS: 00010246
RAX: 0000000000000081 RBX: ffff81000d31d2e8 RCX: ffff81001cc638c0
RDX: ffff81000f4101c0 RSI: 0000000000000286 RDI: ffffffff80580dc0
RBP: ffff810011232140 R08: ffff81001747aac0 R09: ffff81000d1dfb00
R10: 0000000000000004 R11: 000000200000001f R12: ffff81000d31d1e8
R13: ffff81000d31d1e8 R14: ffff81001ac4c680 R15: ffff81000df68220
FS: 00000000421e6940(0063) GS:ffff81001d979840(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000003335ebfe80 CR3: 000000000ee12000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process python (pid: 4763, threadinfo ffff81000d1de000, task 
ffff81000f4101c0)
Stack: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 ffff810011232140 0000000000001299 0000000000000000
0000000000000000 0000000000000000 0000000000000000 ffff810011232140
Call Trace:
[<ffffffff8028d229>] ? __fput+0x97/0x17e
[<ffffffff80297692>] ? sys_fcntl+0x2eb/0x2f7
[<ffffffff8020be19>] ? tracesys+0xdc/0xe1


Code: 48 39 68 58 75 29 0f b6 40 60 a8 02 74 0a 48 89 df e8 5f fe ff ff 
eb 1a a8 20 74 0f be 02 00 00 00 48 89 df e8 e9 fe ff ff eb 07 <0f> 0b 
eb fe 48 89 c3 48 8b 03 48 85 c0 75 c6 e8 97 9d 1d 00 48
RIP [<ffffffff80299f5d>] locks_remove_flock+0xe2/0x102
RSP <ffff81000d1dfe38>
---[ end trace e4d79afa854e3611 ]---
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Kernel Panic when accessing NFS share and locking files, Michael Lang, (Wed May 14, 10:27 am)
Re: Kernel Panic when accessing NFS share and locking files, Arjan van de Ven, (Wed May 14, 8:55 pm)
Re: Kernel Panic when accessing NFS share and locking files, Michael Lang, (Thu May 15, 4:30 am)
Re: Kernel Panic when accessing NFS share and locking files, J. Bruce Fields, (Mon May 19, 2:13 pm)