nfs4 daemon crashes, eventually PC locks up

[Kim Tyler]

Aug 7 01:05:46 mike kernel: [60329.252525] PGD 5b4ac067 PUD 5b4ad067 PMD 0
Aug 7 01:05:46 mike kernel: [60329.252532] Oops: 0000 [#1] SMP
Aug 7 01:05:46 mike kernel: [60329.252538] Modules linked in: rfcomm bnep bluetooth nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_nec_decoder ir_rc5_decoder fc0012 rtl2832 dvb_usb_rtl28xxu rtl2830 dvb_usb_v2 dvb_core rc_core nvidia(POF) snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event serio_raw snd_rawmidi k8temp edac_core edac_mce_amd snd_seq snd_seq_device usblp snd_timer snd soundcore i2c_nforce2 mac_hid parport_pc ppdev lp parport zfs(POF) zunicode(POF) zavl(POF) zcommon(POF) znvpair(POF) spl(OF) hid_generic usbhid pata_acpi hid firewire_ohci firewire_core psmouse e100 forcedeth mii crc_itu_t sata_nv pata_amd
Aug 7 01:05:46 mike kernel: [60329.252626] CPU: 0 PID: 2099 Comm: nfsd Tainted: PF O 3.13.0-32-generic #57-Ubuntu
Aug 7 01:05:46 mike kernel: [60329.252632] Hardware name: /GA-K8N Pro-SLI, BIOS F4 07/16/2005
Aug 7 01:05:46 mike kernel: [60329.252638] task: ffff880060f5c7d0 ti: ffff88005b42e000 task.ti: ffff88005b42e000
Aug 7 01:05:46 mike kernel: [60329.252642] RIP: 0010:[<ffffffffa0fbb06b>] [<ffffffffa0fbb06b>] set_nfsv4_acl_one+0x1b/0x90 [nfsd]
Aug 7 01:05:46 mike kernel: [60329.252660] RSP: 0018:ffff88005b42fcf8 EFLAGS: 00010246
Aug 7 01:05:46 mike kernel: [60329.252664] RAX: 0000000000000000 RBX: ffff88002e9f3d80 RCX: 00000000008036d0
Aug 7 01:05:46 mike kernel: [60329.252668] RDX: ffffffffa0fe86e7 RSI: 0000000000000000 RDI: ffff88002e9f3d80
Aug 7 01:05:46 mike kernel: [60329.252672] RBP: ffff88005b42fd20 R08: 00000000000171e0 R09: ffff88007fc171e0
Aug 7 01:05:46 mike kernel: [60329.252676] R10: ffffea0000282500 R11: ffffffffa0fbb0c7 R12: 0000000000000000
Aug 7 01:05:46 mike kernel: [60329.252680] R13: ffff88002e9f3d80 R14: ffffffffa0fe86e7 R15: 0000000000000660
Aug 7 01:05:46 mike kernel: [60329.252685] FS: 00007f62c5fb5780(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000
Aug 7 01:05:46 mike kernel: [60329.252689] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 7 01:05:46 mike kernel: [60329.252693] CR2: 0000000000000010 CR3: 000000005b4ab000 CR4: 00000000000007f0
Aug 7 01:05:46 mike kernel: [60329.252697] Stack:
Aug 7 01:05:46 mike kernel: [60329.252700] ffff88002e9f3d80 ffff88000a094940 ffff88005c2540b0 ffff880060fe0000
Aug 7 01:05:46 mike kernel: [60329.252707] 0000000000000660 ffff88005b42fd60 ffffffffa0fbb492 ffff880060fe0000
Aug 7 01:05:46 mike kernel: [60329.252714] ffff88000a094900 0000000000000000 ffff880060fe8040 ffff8800667ee240
Aug 7 01:05:46 mike kernel: [60329.252720] Call Trace:
Aug 7 01:05:46 mike kernel: [60329.252740] [<ffffffffa0fbb492>] nfsd4_set_nfs4_acl+0x122/0x130 [nfsd]
Aug 7 01:05:46 mike kernel: [60329.252759] [<ffffffffa0fc8f5d>] nfsd4_setattr+0x10d/0x1a0 [nfsd]
Aug 7 01:05:46 mike kernel: [60329.252777] [<ffffffffa0fca5ca>] nfsd4_proc_compound+0x56a/0x7c0 [nfsd]
Aug 7 01:05:46 mike kernel: [60329.252792] [<ffffffffa0fb6d2b>] nfsd_dispatch+0xbb/0x200 [nfsd]
Aug 7 01:05:46 mike kernel: [60329.252838] [<ffffffffa0f1162d>] svc_process_common+0x46d/0x6d0 [sunrpc]
Aug 7 01:05:46 mike kernel: [60329.252864] [<ffffffffa0f11997>] svc_process+0x107/0x170 [sunrpc]
Aug 7 01:05:46 mike kernel: [60329.252879] [<ffffffffa0fb671f>] nfsd+0xbf/0x130 [nfsd]
Aug 7 01:05:46 mike kernel: [60329.252894] [<ffffffffa0fb6660>] ? nfsd_destroy+0x80/0x80 [nfsd]
Aug 7 01:05:46 mike kernel: [60329.252904] [<ffffffff8108b3d2>] kthread+0xd2/0xf0
Aug 7 01:05:46 mike kernel: [60329.252911] [<ffffffff8108b300>] ? kthread_create_on_node+0x1d0/0x1d0
Aug 7 01:05:46 mike kernel: [60329.252922] [<ffffffff8172c5bc>] ret_from_fork+0x7c/0xb0
Aug 7 01:05:46 mike kernel: [60329.252928] [<ffffffff8108b300>] ? kthread_create_on_node+0x1d0/0x1d0
Aug 7 01:05:46 mike kernel: [60329.252932] Code: eb e6 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 57 41 56 49 89 d6 41 55 49 89 fd 41 54 49 89 f4 53 <48> 63 46 10 be d0 00 00 00 4c 8d 3c c5 04 00 00 00 4c 89 ff e8
Aug 7 01:05:46 mike kernel: [60329.253003] RSP <ffff88005b42fcf8>
Aug 7 01:05:46 mike kernel: [60329.253006] CR2: 0000000000000010
Aug 7 01:05:46 mike kernel: [60329.253012] ---[ end trace 737bd44e2270bead ]---

and

Aug 7 03:00:10 mike kernel: [67193.680580] PGD 36391067 PUD 36392067 PMD 0
Aug 7 03:00:10 mike kernel: [67193.680588] Oops: 0000 [#2] SMP
Aug 7 03:00:10 mike kernel: [67193.680594] Modules linked in: rfcomm bnep bluetooth nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_nec_decoder ir_rc5_decoder fc0012 rtl2832 dvb_usb_rtl28xxu rtl2830 dvb_usb_v2 dvb_core rc_core nvidia(POF) snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event serio_raw snd_rawmidi k8temp edac_core edac_mce_amd snd_seq snd_seq_device usblp snd_timer snd soundcore i2c_nforce2 mac_hid parport_pc ppdev lp parport zfs(POF) zunicode(POF) zavl(POF) zcommon(POF) znvpair(POF) spl(OF) hid_generic usbhid pata_acpi hid firewire_ohci firewire_core psmouse e100 forcedeth mii crc_itu_t sata_nv pata_amd
Aug 7 03:00:10 mike kernel: [67193.680681] CPU: 0 PID: 2098 Comm: nfsd Tainted: PF D O 3.13.0-32-generic #57-Ubuntu
Aug 7 03:00:10 mike kernel: [67193.680688] Hardware name: /GA-K8N Pro-SLI, BIOS F4 07/16/2005
Aug 7 03:00:10 mike kernel: [67193.680693] task: ffff880060f5afe0 ti: ffff880060fde000 task.ti: ffff880060fde000
Aug 7 03:00:10 mike kernel: [67193.680697] RIP: 0010:[<ffffffffa0fbb06b>] [<ffffffffa0fbb06b>] set_nfsv4_acl_one+0x1b/0x90 [nfsd]
Aug 7 03:00:10 mike kernel: [67193.680715] RSP: 0018:ffff880060fdfcf8 EFLAGS: 00010246
Aug 7 03:00:10 mike kernel: [67193.680719] RAX: 0000000000000000 RBX: ffff88004a9e0840 RCX: 00000000008c923e
Aug 7 03:00:10 mike kernel: [67193.680723] RDX: ffffffffa0fe86e7 RSI: 0000000000000000 RDI: ffff88004a9e0840
Aug 7 03:00:10 mike kernel: [67193.680727] RBP: ffff880060fdfd20 R08: 00000000000171e0 R09: ffff88007fc171e0
Aug 7 03:00:10 mike kernel: [67193.680731] R10: ffffea0001eb8040 R11: ffffffffa0fbb0c7 R12: 0000000000000000
Aug 7 03:00:10 mike kernel: [67193.680735] R13: ffff88004a9e0840 R14: ffffffffa0fe86e7 R15: 0000000000000660
Aug 7 03:00:10 mike kernel: [67193.680740] FS: 00007f08bffff700(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000
Aug 7 03:00:10 mike kernel: [67193.680744] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 7 03:00:10 mike kernel: [67193.680748] CR2: 0000000000000010 CR3: 0000000036390000 CR4: 00000000000007f0
Aug 7 03:00:10 mike kernel: [67193.680752] Stack:
Aug 7 03:00:10 mike kernel: [67193.680755] ffff88004a9e0840 ffff88007ae019c0 ffff880006bf72a8 ffff880060eb6000
Aug 7 03:00:10 mike kernel: [67193.680762] 0000000000000660 ffff880060fdfd60 ffffffffa0fbb492 ffff880060eb6000
Aug 7 03:00:10 mike kernel: [67193.680768] ffff88007ae01980 0000000000000000 ffff8800667e9040 ffff8800667eb240
Aug 7 03:00:10 mike kernel: [67193.680775] Call Trace:
Aug 7 03:00:10 mike kernel: [67193.680795] [<ffffffffa0fbb492>] nfsd4_set_nfs4_acl+0x122/0x130 [nfsd]
Aug 7 03:00:10 mike kernel: [67193.680814] [<ffffffffa0fc8f5d>] nfsd4_setattr+0x10d/0x1a0 [nfsd]
Aug 7 03:00:10 mike kernel: [67193.680832] [<ffffffffa0fca5ca>] nfsd4_proc_compound+0x56a/0x7c0 [nfsd]
Aug 7 03:00:10 mike kernel: [67193.680847] [<ffffffffa0fb6d2b>] nfsd_dispatch+0xbb/0x200 [nfsd]
Aug 7 03:00:10 mike kernel: [67193.680894] [<ffffffffa0f1162d>] svc_process_common+0x46d/0x6d0 [sunrpc]
Aug 7 03:00:10 mike kernel: [67193.680920] [<ffffffffa0f11997>] svc_process+0x107/0x170 [sunrpc]
Aug 7 03:00:10 mike kernel: [67193.680934] [<ffffffffa0fb671f>] nfsd+0xbf/0x130 [nfsd]
Aug 7 03:00:10 mike kernel: [67193.680949] [<ffffffffa0fb6660>] ? nfsd_destroy+0x80/0x80 [nfsd]
Aug 7 03:00:10 mike kernel: [67193.680959] [<ffffffff8108b3d2>] kthread+0xd2/0xf0
Aug 7 03:00:10 mike kernel: [67193.680966] [<ffffffff8108b300>] ? kthread_create_on_node+0x1d0/0x1d0
Aug 7 03:00:10 mike kernel: [67193.680977] [<ffffffff8172c5bc>] ret_from_fork+0x7c/0xb0
Aug 7 03:00:10 mike kernel: [67193.680983] [<ffffffff8108b300>] ? kthread_create_on_node+0x1d0/0x1d0
Aug 7 03:00:10 mike kernel: [67193.680987] Code: eb e6 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 57 41 56 49 89 d6 41 55 49 89 fd 41 54 49 89 f4 53 <48> 63 46 10 be d0 00 00 00 4c 8d 3c c5 04 00 00 00 4c 89 ff e8
Aug 7 03:00:10 mike kernel: [67193.681058] RSP <ffff880060fdfcf8>
Aug 7 03:00:10 mike kernel: [67193.681061] CR2: 0000000000000010
Aug 7 03:00:10 mike kernel: [67193.681067] ---[ end trace 737bd44e2270beae ]---

After this sequence, the server will lockup solid, and even REISUB will not reset it, it requires either hardware reset or power cycle.

It happens about 3 times a week (it has a function as file server for other linux machines), and only started happening after upgrade from saucy to trusty.

Hardware has been tested, with no obvious errors.
---
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kit284 2690 F.... pulseaudio
 /dev/snd/controlC1: kit284 2690 F.... pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=8bc3362d-e136-453f-bb6c-284013a5dd11
InstallationDate: Installed on 2014-10-01 (23 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: CLEVO D900K
NonfreeKernelModules: nvidia
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=7f8ca46f-0efa-4971-b7fc-9b787d5b660f ro quiet splash
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-37-generic N/A
 linux-backports-modules-3.13.0-37-generic N/A
 linux-firmware 1.127.7
Tags: trusty
Uname: Linux 3.13.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: fuse
_MarkForUpload: True
dmi.bios.date: 12/06/2005
dmi.bios.vendor: Phoenix
dmi.bios.version: 4.06CJ15
dmi.board.name: D900K
dmi.board.vendor: CLEVO
dmi.board.version: VT8341B
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd12/06/2005:svnCLEVO:pnD900K:pvrVT8341B:rvnCLEVO:rnD900K:rvrVT8341B:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: D900K
dmi.product.version: VT8341B
dmi.sys.vendor: CLEVO

[Kim Tyler (ktyler)]

further investigation :-

I have 4 partitions on 2 disks mounted in fstab, then these 4 partitions (ext4) are mounted with "bind" to /exports for eventual nfs4 export.

After reboot, some of these partitions are mounted, (according to mount) but are empty. If these /exports bind directories are umounted, then remounted with mount -a, then nfs-kernel-server restarted, there is no problem. It has been running without problem for some days now, when before it would show crash in logs every day, and freeze once per day or so.

It is a pain to have to log into the file server and jigger around with mounts/exportfs manually, after every reboot.

Could it be that some of the directories are exported before the "bind" mount is done, confusing the exportfs command?

Is there some delay or change of dependencies in boot up that could delay the exportfs until all directories are correctly mounted?

Is there some problem with nfs4 facls as noted with other launchpad bugs?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Stian Skjelstad (mywave)]

Happened out of the blue for my server that had an uptime for 54 days, last 2-3 weeks running as nfs-server. Reboots goes straight into this

[ 15.029841] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 15.050206] NFSD: starting 90-second grace period (net ffffffff81cda540)
[ 15.364029] init: plymouth-upstart-bridge main process ended, respawning
[ 22.260448] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
[ 22.260567] IP: [<ffffffffa059b06b>] set_nfsv4_acl_one+0x1b/0x90 [nfsd]
[ 22.260657] PGD 20fde3067 PUD 20fe03067 PMD 0
[ 22.260730] Oops: 0000 [#1] SMP
[ 22.260782] Modules linked in: nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi ppdev kvm_amd kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw edac_core fam15h_power snd_hda_codec_realtek k10temp edac_mce_amd radeon snd_hda_intel sp5100_tco i2c_piix4 snd_hda_codec snd_hwdep ttm snd_pcm drm_kms_helper snd_page_alloc drm snd_timer snd soundcore i2c_algo_bit shpchp parport_pc mac_hid lp wmi parport raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 pata_acpi multipath r8169 ahci usb_storage pata_atiixp libahci mii linear
[ 22.261818] CPU: 0 PID: 1130 Comm: nfsd Not tainted 3.13.0-36-generic #63-Ubuntu
[ 22.261908] Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7596/760GM-E51(MS-7596), BIOS V3.6 10/26/2012
[ 22.262024] task: ffff8800ce78b000 ti: ffff880036be4000 task.ti: ffff880036be4000
[ 22.262112] RIP: 0010:[<ffffffffa059b06b>] [<ffffffffa059b06b>] set_nfsv4_acl_one+0x1b/0x90 [nfsd]
[ 22.262225] RSP: 0018:ffff880036be5cf8 EFLAGS: 00010246
[ 22.262289] RAX: 0000000000000000 RBX: ffff880211a852c0 RCX: 0000000000006653
[ 22.262374] RDX: ffffffffa05c86e7 RSI: 0000000000000000 RDI: ffff880211a852c0
[ 22.262457] RBP: ffff880036be5d20 R08: 00000000000171e0 R09: ffff8802156171e0
[ 22.262542] R10: ffffea0008378580 R11: ffffffffa059b0c7 R12: 0000000000000000
[ 22.262625] R13: ffff880211a852c0 R14: ffffffffa05c86e7 R15: 0000000000000660
[ 22.262710] FS: 00007f31cc3d8780(0000) GS:ffff880215600000(0000) knlGS:0000000000000000
[ 22.262806] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 22.262874] CR2: 0000000000000010 CR3: 000000020fd19000 CR4: 00000000000407f0
[ 22.262959] Stack:
[ 22.262985] ffff880211a852c0 ffff88020f9e3c00 ffff8800cf51ec50 ffff880036ae8000
[ 22.263092] 0000000000000660 ffff880036be5d60 ffffffffa059b492 ffff880036ae8000
[ 22.263199] ffff88020de16c80 0000000000000000 ffff8800ce4d9040 ffff8800ce4dc240
[ 22.263305] Call Trace:
[ 22.263340] [<ffffffffa059b492>] nfsd4_set_nfs4_acl+0x122/0x130 [nfsd]
[ 22.263422] [<ffffffffa05a8f5d>] nfsd4_setattr+0x10d/0x1a0 [nfsd]
[ 22.263501] [<ffffffffa05aa5ca>] nfsd4_proc_compound+0x56a/0x7c0 [nfsd]
[ 22.263584] [<ffffffffa0596d2b>] nfsd_dispatch+0xbb/0x200 [nfsd]
[ 22.263666] [<ffffffffa050c62d>] svc_process_common+0x46d/0x6d0 [sunrpc]
[ 22.263752] [<ffffffffa050c997>] svc_process+0x107/0x170 [sunrpc]
[ 22.263830] [<ffffffffa059671f>] nfsd+0xbf/0x130 [nfsd]
[ 22....

[Stian Skjelstad (mywave)]

I do not have bind mounts, but the exported filesystem is however stored on a software raid1 block device

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Kim Tyler, both the Oneiric and Quantal enablement kernels are no longer supported as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack . Hence, would this still be reproducible in a supported kernel/release (ex. Trusty)?

[Kim Tyler (ktyler)]

yes - it still happens (happened) with trusty. I use a backup program called backintime which uses rsync, and I backup the laptop to an nfs4 mount. During the backup, the nfs4 server crashes just as specified above in trusty (kernel 3.13.0-32-generic). The backup program then stops, leaving the rsync running.

If I restart the server, without restarting the client, the backup program continues and corrupts the disk that is being backed up to, requiring an fsck.

From the logs of backintime, the command is:- (where pio is the laptop being backed up, mike is the nfs4 server, and the disk /media/seagate on mike is mounted nfs4 at pio as /media/mike/seagate

rsync -rtDH --links --no-p --no-g --no-o --delete --delete-excluded -v --chmod=Du+wx --exclude="/media/mike/seagate/backintime" --exclude="/home/kit284/.local/share/backintime" --include="/home/kit284/" --include="/home/" --include="/home/mythtv/" --exclude="*.backup*" --exclude="*~" --exclude="/home/kit284/root" --exclude="/home/kit284/tmp" --exclude="/home/kit284/Ubuntu One" --exclude="*.thumbnails" --exclude="*.iso" --exclude="/home/kit284/.gvfs" --exclude="[Cc]ache*" --include="/home/kit284/**" --include="/home/mythtv/**" --exclude="*" / "/media/mike/seagate/backintime/backintime/pio/kit284/1/new_snapshot/backup/"

I am currently running backintime via a FUSE mounted ssh connection built in to backintime, and this is working OK. However, is is very disquieting to know that NFS4 can crash, and take out the disk, requiring a reboot and fsck.

I note that some research on the internet show that rsync can have problems with change attributes on nfs4 mounts, and the suggestion is that this is a bug with nfs4.

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[penalvch (penalvch)]

Kim Tyler, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]