Package: linux-image-2.6-amd64
Version: 2.6.18+6etch3
Severity: important


Using the latest debian kernel on smp 64bit systems we can see random "general protection fault: 0000 [11] SMP" stack traces.
This is always related to high nfsv3 traffic (e.g. imap or pop3 services).

I attach some stack traces samples of three different x64 IBM 3550 machines.

Keep in mind that after these stack traces the machine is unstable and after some time its kernel is going to be crash.
Another hint is that if you try to reboot the machine you always get this stack trace followed by a kernel crash.

I would be grateful if i can send you any feedback.

Thanks,

general protection fault: 0000 [11] SMP
CPU 2
Modules linked in: xt_state nfsd exportfs iptable_nat ip_nat ip_conntrack nfnetlink ipt_LOG xt_limit xt_tcpudp iptable_filter iptable_mangle ip_tables x_tables button ac battery nfs
lockd nfs_
acl sunrpc bonding dm_snapshot dm_mirror dm_mod loop i2c_i801 i2c_core shpchp pcspkr pci_hotplug evdev joydev ext3 jbd mbcache usbhid ide_cd cdrom generic sd_mod e1000 bnx2 piix
ide_core uhci_
hcd ehci_hcd aacraid scsi_mod thermal processor fan
Pid: 18744, comm: popper Not tainted 2.6.18-6-amd64 #1
RIP: 0010:[<ffffffff881ec955>] [<ffffffff881ec955>] :nfs:nfs_complete_unlink+0x10/0x97
RSP: 0000:ffff81011636beb8 EFLAGS: 00010206
RAX: ffff8101557ae770 RBX: 77ac070c00000000 RCX: ffff8101660c5dc8
RDX: 0000000000000000 RSI: ffff8101660c5d98 RDI: ffff81020fb34d80
RBP: ffff81020fb34d80 R08: 0000000000000000 R09: ffff8101660c5eb0
R10: 0000000000000008 R11: ffffffff881e44f4 R12: ffff8101660c5d98
R13: ffff81020fb34d80 R14: ffff810237e0ddc0 R15: 0000000000000000
FS: 00002b0cf8392dd0(0000) GS:ffff8101fef752c0(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000000041701b CR3: 0000000178bfb000 CR4: 00000000000006e0
Process popper (pid: 18744, threadinfo ffff81011636a000, task ffff8101557ae770)
Stack: ffff8101660c5d98 ffff81020fb34d80 ffff8101660c5d98 ffffffff881e4525
ffff8101660c5d98 ffff81020fb34d80 ffff810140c49c80 ffffffff8020c9c7
0000000000000008 0000000000000008 ffff810140c49c80 ffffffff80210a82
Call Trace:
[<ffffffff881e4525>] :nfs:nfs_dentry_iput+0x31/0x4f
[<ffffffff8020c9c7>] dput+0x135/0x153
[<ffffffff80210a82>] __fput+0x148/0x16e
[<ffffffff80221c08>] filp_close+0x5c/0x64
[<ffffffff8021bd30>] sys_close+0x88/0xa2
[<ffffffff80257c16>] system_call+0x7e/0x83


Code: 48 3b 6b 10 74 0a 48 8b 1b 48 85 db 75 f2 eb 72 ff 83 98 01
RIP [<ffffffff881ec955>] :nfs:nfs_complete_unlink+0x10/0x97
RSP <ffff81011636beb8>

-----------------------------------------------------------------

general protection fault: 0000 [11] SMP
CPU 2
Modules linked in: xt_state nfsd exportfs iptable_nat ip_nat ip_conntrack nfnetlink ipt_LOG xt_limit xt_tcpudp iptable_filter iptable_mangle ip_tables x_tables button ac battery nfs
lockd nfs_
acl sunrpc bonding dm_snapshot dm_mirror dm_mod loop i2c_i801 i2c_core shpchp pcspkr pci_hotplug evdev joydev ext3 jbd mbcache usbhid ide_cd cdrom generic sd_mod e1000 bnx2 piix
ide_core uhci_
hcd ehci_hcd aacraid scsi_mod thermal processor fan
Pid: 18744, comm: popper Not tainted 2.6.18-6-amd64 #1
RIP: 0010:[<ffffffff881ec955>] [<ffffffff881ec955>] :nfs:nfs_complete_unlink+0x10/0x97
RSP: 0000:ffff81011636beb8 EFLAGS: 00010206
RAX: ffff8101557ae770 RBX: 77ac070c00000000 RCX: ffff8101660c5dc8
RDX: 0000000000000000 RSI: ffff8101660c5d98 RDI: ffff81020fb34d80
RBP: ffff81020fb34d80 R08: 0000000000000000 R09: ffff8101660c5eb0
R10: 0000000000000008 R11: ffffffff881e44f4 R12: ffff8101660c5d98
R13: ffff81020fb34d80 R14: ffff810237e0ddc0 R15: 0000000000000000
FS: 00002b0cf8392dd0(0000) GS:ffff8101fef752c0(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000000041701b CR3: 0000000178bfb000 CR4: 00000000000006e0
Process popper (pid: 18744, threadinfo ffff81011636a000, task ffff8101557ae770)
Stack: ffff8101660c5d98 ffff81020fb34d80 ffff8101660c5d98 ffffffff881e4525
ffff8101660c5d98 ffff81020fb34d80 ffff810140c49c80 ffffffff8020c9c7
0000000000000008 0000000000000008 ffff810140c49c80 ffffffff80210a82
Call Trace:
[<ffffffff881e4525>] :nfs:nfs_dentry_iput+0x31/0x4f
[<ffffffff8020c9c7>] dput+0x135/0x153
[<ffffffff80210a82>] __fput+0x148/0x16e
[<ffffffff80221c08>] filp_close+0x5c/0x64
[<ffffffff8021bd30>] sys_close+0x88/0xa2
[<ffffffff80257c16>] system_call+0x7e/0x83


Code: 48 3b 6b 10 74 0a 48 8b 1b 48 85 db 75 f2 eb 72 ff 83 98 01
RIP [<ffffffff881ec955>] :nfs:nfs_complete_unlink+0x10/0x97
RSP <ffff81011636beb8>

-----------------------------------------------------------------------

general protection fault: 0000 [2] SMP
CPU 2
Modules linked in: ipt_LOG xt_limit xt_state xt_tcpudp iptable_filter iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_tables button ac battery nfs lockd nfs_acl sunrpc bonding
dm_snapsho
t dm_mirror dm_mod loop i2c_i801 pcspkr shpchp pci_hotplug i2c_core joydev evdev usbhid ext3 jbd mbcache ide_cd cdrom generic sd_mod e1000 piix uhci_hcd bnx2 ehci_hcd ide_core aacraid
scsi_mod
thermal processor fan
Pid: 19065, comm: popper Not tainted 2.6.18-6-amd64 #1
RIP: 0010:[<ffffffff881ec955>] [<ffffffff881ec955>] :nfs:nfs_complete_unlink+0x10/0x97
RSP: 0018:ffff8100ac86deb8 EFLAGS: 00010206
RAX: ffff81023704e100 RBX: 77ac070c00000000 RCX: ffff8101d9d70210
RDX: 0000000000000000 RSI: ffff8101d9d701e0 RDI: ffff8100a4ac5560
RBP: ffff8100a4ac5560 R08: 0000000000000000 R09: ffff8101d9d702f8
R10: 0000000000000008 R11: ffffffff881e44f4 R12: ffff8101d9d701e0
R13: ffff8100a4ac5560 R14: ffff810238152a80 R15: 0000000000000007
FS: 00002aeef9529dd0(0000) GS:ffff8101fef752c0(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002aeef870c640 CR3: 000000000f067000 CR4: 00000000000006e0
Process popper (pid: 19065, threadinfo ffff8100ac86c000, task ffff81023704e100)
Stack: ffff8101d9d701e0 ffff8100a4ac5560 ffff8101d9d701e0 ffffffff881e4525
ffff8101d9d701e0 ffff8100a4ac5560 ffff8101f6d0fc80 ffffffff8020c9c7
0000000000000008 0000000000000008 ffff8101f6d0fc80 ffffffff80210a82
Call Trace:
[<ffffffff881e4525>] :nfs:nfs_dentry_iput+0x31/0x4f
[<ffffffff8020c9c7>] dput+0x135/0x153
[<ffffffff80210a82>] __fput+0x148/0x16e
[<ffffffff80221c08>] filp_close+0x5c/0x64
[<ffffffff8021bd30>] sys_close+0x88/0xa2
[<ffffffff80257c16>] system_call+0x7e/0x83


Code: 48 3b 6b 10 74 0a 48 8b 1b 48 85 db 75 f2 eb 72 ff 83 98 01
RIP [<ffffffff881ec955>] :nfs:nfs_complete_unlink+0x10/0x97
RSP <ffff8100ac86deb8>



-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=C, LC_CTYPE=el_GR (charmap=ISO-8859-7)

Versions of packages linux-image-2.6-amd64 depends on:
ii linux-image-2.6.18 2.6.18.dfsg.1-18etch6 Linux 2.6.18 image on AMD64

linux-image-2.6-amd64 recommends no packages.

-- no debconf information



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, Jun 27, 2008 at 02:20:18PM +0300, Evaggelos Souglakos wrote:
> Package: linux-image-2.6-amd64
> Version: 2.6.18+6etch3
> Severity: important
>
>
> Using the latest debian kernel on smp 64bit systems we can see random "general protection fault: 0000 [11] SMP" stack traces.
> This is always related to high nfsv3 traffic (e.g. imap or pop3 services).
>
> I attach some stack traces samples of three different x64 IBM 3550 machines.
>
> Keep in mind that after these stack traces the machine is unstable and after some time its kernel is going to be crash.
> Another hint is that if you try to reboot the machine you always get this stack trace followed by a kernel crash.
>
> I would be grateful if i can send you any feedback.

Could you try to reproduce this bug with the 2.6.24 based kernel added
in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html

Cheers,
Moritz



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org