[opensuse-factory] Kernels 3.18X problem
Toshiba Satellite L775D laptop running openSUSE 13.2 Tumbleweed. Kernels 3.18X usually (about 90% of the time) boot up but keyboard and mouse do not work. 10% of the time when keyboard and mouse do work, the wifi card records firmware downloading failed messages in the log and network performance over wifi is very very poor. Kernel 3.16 from mainline openSUSE 13.2 works fine. Sound does not work at all with any kernel. I would be happy to open bug reports for the issues, but I am not sure what logs/diags to run to put into bug reports. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Moby <moby@mobsternet.com> [01-07-15 21:48]:
Toshiba Satellite L775D laptop running openSUSE 13.2 Tumbleweed.
Toshiba Satellite Inspiration 1750 running openSUSE Tumbleweed.
Kernels 3.18X usually (about 90% of the time) boot up but keyboard and mouse do not work. 10% of the time when keyboard and mouse do work, the wifi card records firmware downloading failed messages in the log and network performance over wifi is very very poor.
Also 3.18x, keyboard works but is junk. I don't have a mouse with the laptop but can plug one in and it works. I do have a Satellite X205 that has wifi probs but it's running windoz in front of my wife :^). I didn't have wifi probs when running openSUSE.
Kernel 3.16 from mainline openSUSE 13.2 works fine.
Sound does not work at all with any kernel.
Sound works on all my systems but I have screwed it up on occasion.
I would be happy to open bug reports for the issues, but I am not sure what logs/diags to run to put into bug reports.
Just make them the best that you can. If someone bothers to look at them, they will ask for information not provided. Best to get the ball rolling and display that you are conserned. If you don't initiate action, there will be none. ps: I closed 3 bugs > 2 year old just a few minutes ago. They lacked action and I cannot recreate the conditions to even see if and solution is in fact a solution. RESOLVED INVALID/NORESPONSE :^( -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/08/2015 04:44 AM, Moby wrote:
Toshiba Satellite L775D laptop running openSUSE 13.2 Tumbleweed.
Kernels 3.18X usually (about 90% of the time) boot up but keyboard and mouse do not work. 10% of the time when keyboard and mouse do work, the wifi card records firmware downloading failed messages in the log and network performance over wifi is very very poor.
Kernel 3.16 from mainline openSUSE 13.2 works fine.
Sound does not work at all with any kernel.
I would be happy to open bug reports for the issues, but I am not sure what logs/diags to run to put into bug reports.
- likewise my experience too : with kernel 3.18X am getting endless delays with ; hci-pci [ 1398.987049] usb 1-1: new high-speed USB device number 23 using ehci-pci [ 1399.463043] usb 1-1: new high-speed USB device number 25 using ehci-pci .................. regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/08/2015 03:19 AM, ellanios82 wrote:
On 01/08/2015 04:44 AM, Moby wrote:
Toshiba Satellite L775D laptop running openSUSE 13.2 Tumbleweed.
Kernels 3.18X usually (about 90% of the time) boot up but keyboard and mouse do not work. 10% of the time when keyboard and mouse do work, the wifi card records firmware downloading failed messages in the log and network performance over wifi is very very poor.
Kernel 3.16 from mainline openSUSE 13.2 works fine.
Sound does not work at all with any kernel.
I would be happy to open bug reports for the issues, but I am not sure what logs/diags to run to put into bug reports.
- likewise my experience too :
with kernel 3.18X am getting endless delays with ;
hci-pci [ 1398.987049] usb 1-1: new high-speed USB device number 23 using ehci-pci [ 1399.463043] usb 1-1: new high-speed USB device number 25 using ehci-pci
..................
regards
The ModemManager service ended up being the culprit. Not sure why, but disabling ModemManager fixed the issue with the keyboard/mouse not working with kernels 3.18X -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/08/2015, 03:44 AM, Moby wrote:
Toshiba Satellite L775D laptop running openSUSE 13.2 Tumbleweed.
Kernels 3.18X usually (about 90% of the time) boot up but keyboard and mouse do not work. 10% of the time when keyboard and mouse do work, the wifi card records firmware downloading failed messages in the log and network performance over wifi is very very poor.
Kernel 3.16 from mainline openSUSE 13.2 works fine.
Sound does not work at all with any kernel.
I would be happy to open bug reports for the issues, but I am not sure what logs/diags to run to put into bug reports.
/var/log/message in most cases might be enough. To the sound bug report, attach the output of alsa-info.sh -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Moby wrote:
Kernels 3.18X usually (about 90% of the time) boot up but keyboard and mouse do not work. 10% of the time when keyboard and mouse do work, the wifi card records firmware downloading failed messages in the log and network performance over wifi is very very poor.
Likely unrelated, but had two crashes (hangs needing power cycling) on 3.18.1 then on 3.18.0... am now back on 3.17.3 (which had a prior uptime >40days). Seems odd both hangs happened when smbd failed to break an oplock, but 'replied anyway'. The smbd failure could be the first symptom of it starting to crash as easily as a trigger. Odd it would hang breaking a lock for the same file both times... Log messages: prev-kernel: reboot system boot 3.17.3-Isht-Van Thu Nov 13 14:06 - 09:29 (3+19:22) ** uptime=41+06:36 (41 days+) on 3.17.3 reboot system boot 3.18.1-Isht-Van Sun Dec 28 16:19 - 13:09 (1+20:50) -- latest kernel ** uptime ~ 19:32 (19 hours+) on 3.18.1 -- then: Dec 29 11:47:15 Ishtar smbd[4776]: [2014/12/29 11:47:15, 0] smbd/oplock.c:330(oplock_timeout_handler) Dec 29 11:47:15 Ishtar smbd[4776]: Oplock break failed for file Scans/HighSchoolDxD/Visual/Thumbs.db -- replying anyway Dec 29 11:47:15 Ishtar kernel: [70136.106709] PGD 0 Dec 29 11:47:15 Ishtar kernel: [70136.108728] Oops: 0000 [#1] PREEMPT SMP Dec 29 11:47:15 Ishtar kernel: [70136.112677] Modules linked in: xt_nat iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack edd mpt3sas mpt2sas mptctl ipv6 iptable_filter ip_tables coretemp kvm_intel kvm aesni_intel tpm_tis aes_x86_64 ablk_helper ses cryptd tpm psmouse lrw iTCO_wdt mousedev acpi_cpufreq button gf128mul ioatdma processor serio_raw gpio_ich glue_helper enclosure iTCO_vendor_support wmi i7core_edac thermal_sys ixgbe mdio dca hwmon bnx2 Dec 29 11:47:15 Ishtar kernel: [70136.152131] CPU: 2 PID: 4776 Comm: smbd Not tainted 3.18.1-Isht-Van #2 Dec 29 11:47:15 Ishtar kernel: [70136.158655] Hardware name: Dell Inc. PowerEdge T610/0CX0R0, BIOS 6.3.0 07/24/2012 Dec 29 11:47:15 Ishtar kernel: [70136.166133] task: ffff880bf3cca510 ti: ffff880bf2208000 task.ti: ffff880bf2208000 Dec 29 11:47:15 Ishtar kernel: [70136.173611] RIP: 0010:[<ffffffff81235e4f>] [<ffffffff81235e4f>] generic_setlease+0x14f/0x6d0 Dec 29 11:47:15 Ishtar kernel: [70136.182141] RSP: 0018:ffff880bf220be58 EFLAGS: 00010286 Dec 29 11:47:15 Ishtar kernel: [70136.187449] RAX: 0000000000000082 RBX: ffff88134f6e4700 RCX: 0000000000000000 Dec 29 11:47:15 Ishtar kernel: [70136.194579] RDX: ffff880bf220be88 RSI: 0000000000000002 RDI: ffff88125104fbe8 Dec 29 11:47:15 Ishtar kernel: [70136.201708] RBP: ffff880bf220bec8 R08: 0000000000000235 R09: 0000000000004680 Dec 29 11:47:15 Ishtar kernel: [70136.208837] R10: 0000000000000000 R11: ef7bdef7bdef7bdf R12: ffff88125104f9e0 Dec 29 11:47:15 Ishtar kernel: [70136.215967] R13: ffff880bf220be88 R14: ffff88125104fbe8 R15: ffff881455590e00 Dec 29 11:47:15 Ishtar kernel: [70136.223096] FS: 00007f68d9ceb840(0000) GS:ffff88180ec00000(0000) knlGS:0000000000000000 Dec 29 11:47:15 Ishtar kernel: [70136.231178] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 29 11:47:15 Ishtar kernel: [70136.236917] CR2: 0000000000000038 CR3: 0000000bf2ded000 CR4: 00000000000007e0 Dec 29 11:47:15 Ishtar kernel: [70136.244045] Stack: Dec 29 11:47:15 Ishtar kernel: [70136.246052] ffff880bf220be78 ffffffff810851eb ffff880bf220be78 0000000000000001 Dec 29 11:47:15 Ishtar kernel: [70136.253478] ffff880bf220be98 ffff88125104fa68 ffff880bf220be88 ffff880bf220be88 Dec 29 11:47:15 Ishtar kernel: [70136.260900] ffff880bf220bed8 0000000000000002 ffff881455590e00 0000000000000400 Dec 29 11:47:15 Ishtar kernel: [70136.268325] Call Trace: Dec 29 11:47:15 Ishtar kernel: [70136.270774] [<ffffffff810851eb>] ? preempt_count_sub+0x4b/0x60 Dec 29 11:47:15 Ishtar kernel: [70136.276692] [<ffffffff812363f5>] vfs_setlease+0x25/0x30 Dec 29 11:47:15 Ishtar kernel: [70136.282004] [<ffffffff81237021>] fcntl_setlease+0x91/0xd0 Dec 29 11:47:15 Ishtar kernel: [70136.287491] [<ffffffff811f1ed8>] SyS_fcntl+0x308/0x6b0 Dec 29 11:47:15 Ishtar kernel: [70136.292716] [<ffffffff8139b85e>] ? trace_hardirqs_on_thunk+0x3a/0x3f Dec 29 11:47:15 Ishtar kernel: [70136.299156] [<ffffffff816dffd2>] system_call_fastpath+0x12/0x17 Dec 29 11:47:15 Ishtar kernel: [70136.305159] Code: aa 00 65 ff 0c 25 e0 a9 00 00 0f 84 b4 01 00 00 48 85 db 0f 84 d7 04 00 00 4c 8b 93 d8 00 00 00 4c 89 ea be 02 00 00 00 4c 89 f7 <41> ff 52 38 41 89 c4 48 8b 7d b8 e8 e1 92 4a 00 4c 89 ef e8 69 Dec 29 11:47:15 Ishtar kernel: [70136.330796] RSP <ffff880bf220be58> Dec 29 11:47:15 Ishtar kernel: [70136.334281] CR2: 0000000000000038 Dec 29 11:47:15 Ishtar kernel: [70136.337924] ---[ end trace f2f2c0fe017f371e ]--- System unresponsive to keyboard or net... reboot to 3.18.0... .. .about 4.5 minutes later: Dec 29 11:57:24 Ishtar smbd[4368]: Oplock break failed for file Scans/HighSchoolDxD/Visual/Thumbs.db -- replying anyway Dec 29 11:57:24 Ishtar kernel: [ 266.909376] PGD 0 Dec 29 11:57:24 Ishtar kernel: [ 266.909378] Oops: 0000 [#1] PREEMPT SMP Dec 29 11:57:24 Ishtar kernel: [ 266.909382] Modules linked in: mpt3sas mpt2sas mptctl ipv6 iptable_filter ip_tables ses iTCO_wdt psmouse mousedev ioatdma iTCO_vendor_support tpm_tis serio_raw gpio_ich acpi_cpufreq enclosure tpm wmi i7core_edac processor thermal_sys button ixgbe dca mdio hwmon bnx2 Dec 29 11:57:24 Ishtar kernel: [ 266.909406] CPU: 4 PID: 4368 Comm: smbd Not tainted 3.18.0-Isht-Van #1 Dec 29 11:57:24 Ishtar kernel: [ 266.909408] Hardware name: Dell Inc. PowerEdge T610/0CX0R0, BIOS 6.3.0 07/24/2012 Dec 29 11:57:24 Ishtar kernel: [ 266.909409] task: ffff880bf66bca20 ti: ffff880bf6840000 task.ti: ffff880bf6840000 Dec 29 11:57:24 Ishtar kernel: [ 266.909411] RIP: 0010:[<ffffffff811fca3f>] [<ffffffff811fca3f>] generic_setlease+0x14f/0x620 Dec 29 11:57:24 Ishtar kernel: [ 266.909414] RSP: 0018:ffff880bf6843e58 EFLAGS: 00010286 Dec 29 11:57:24 Ishtar kernel: [ 266.909415] RAX: 0000000000000082 RBX: ffff881799a3b400 RCX: 0000000000000000 Dec 29 11:57:24 Ishtar kernel: [ 266.909417] RDX: ffff880bf6843e88 RSI: 0000000000000002 RDI: ffff8817beadd1e8 Dec 29 11:57:24 Ishtar kernel: [ 266.909418] RBP: ffff880bf6843ec8 R08: 0000000000000236 R09: 0000000000000000 Dec 29 11:57:24 Ishtar kernel: [ 266.909419] R10: ffff88180ee0c320 R11: ef7bdef7bdef7bdf R12: ffff8817beadcfe0 Dec 29 11:57:24 Ishtar kernel: [ 266.909420] R13: ffff880bf6843e88 R14: ffff8817beadd1e8 R15: ffff8817e914ea00 Dec 29 11:57:24 Ishtar kernel: [ 266.909422] FS: 00007faea9c5a840(0000) GS:ffff88180ee00000(0000) knlGS:0000000000000000 Dec 29 11:57:24 Ishtar kernel: [ 266.909424] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 29 11:57:24 Ishtar kernel: [ 266.909426] CR2: 0000000000000038 CR3: 0000000bfab23000 CR4: 00000000000007e0 Dec 29 11:57:24 Ishtar kernel: [ 266.909426] Stack: Dec 29 11:57:24 Ishtar kernel: [ 266.909430] 00007fff96e51000 000000000000f88f 0000000000000000 ffff880bf66bca20 Dec 29 11:57:24 Ishtar kernel: [ 266.909432] ffff880bf6843e98 ffff8817beadd068 ffff880bf6843e88 ffff880bf6843e88 Dec 29 11:57:24 Ishtar kernel: [ 266.909435] ffff880bf6843ef8 0000000000000002 ffff8817e914ea00 0000000000000400 Dec 29 11:57:24 Ishtar kernel: [ 266.909435] Call Trace: Dec 29 11:57:24 Ishtar kernel: [ 266.909441] [<ffffffff811fcf35>] vfs_setlease+0x25/0x30 Dec 29 11:57:24 Ishtar kernel: [ 266.909444] [<ffffffff811fda19>] fcntl_setlease+0x99/0xc0 Dec 29 11:57:24 Ishtar kernel: [ 266.909449] [<ffffffff811c0301>] SyS_fcntl+0x2e1/0x680 Dec 29 11:57:24 Ishtar kernel: [ 266.909454] [<ffffffff8162e9d2>] system_call_fastpath+0x12/0x17 Dec 29 11:57:24 Ishtar kernel: [ 266.909483] Code: ad 00 65 ff 0c 25 e0 a9 00 00 0f 84 94 01 00 00 48 85 db 0f 84 0b 04 00 00 4c 8b 8b d8 00 00 00 4c 89 ea be 02 00 00 00 4c 89 f7 <41> ff 51 38 41 89 c4 48 8b 7d b8 e8 f1 11 43 00 4c 89 ef e8 39 Dec 29 11:57:24 Ishtar kernel: [ 266.909487] RSP <ffff880bf6843e58> Dec 29 11:57:24 Ishtar kernel: [ 266.909488] CR2: 0000000000000038 Dec 29 11:57:24 Ishtar kernel: [ 266.909491] ---[ end trace 24195753a6dfc13d ]--- reboot back to 3.17.3 .... still up and stable @using 3.17.3. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/09/2015, 08:24 AM, Linda Walsh wrote:
Likely unrelated, but had two crashes (hangs needing power cycling) on 3.18.1 then on 3.18.0... am now back on 3.17.3 (which had a prior uptime >40days).
Seems odd both hangs happened when smbd failed to break an oplock, but 'replied anyway'. The smbd failure could be the first symptom of it starting to crash as easily as a trigger. Odd it would hang breaking a lock for the same file both times...
Log messages:
prev-kernel: reboot system boot 3.17.3-Isht-Van Thu Nov 13 14:06 - 09:29 (3+19:22) ** uptime=41+06:36 (41 days+) on 3.17.3 reboot system boot 3.18.1-Isht-Van Sun Dec 28 16:19 - 13:09 (1+20:50) -- latest kernel ** uptime ~ 19:32 (19 hours+) on 3.18.1 -- then:
Dec 29 11:47:15 Ishtar smbd[4776]: [2014/12/29 11:47:15, 0] smbd/oplock.c:330(oplock_timeout_handler) Dec 29 11:47:15 Ishtar smbd[4776]: Oplock break failed for file Scans/HighSchoolDxD/Visual/Thumbs.db -- replying anyway Dec 29 11:47:15 Ishtar kernel: [70136.106709] PGD 0 Dec 29 11:47:15 Ishtar kernel: [70136.108728] Oops: 0000 [#1] PREEMPT SMP Dec 29 11:47:15 Ishtar kernel: [70136.112677] Modules linked in: xt_nat iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack edd mpt3sas mpt2sas mptctl ipv6 iptable_filter ip_tables coretemp kvm_intel kvm aesni_intel tpm_tis aes_x86_64 ablk_helper ses cryptd tpm psmouse lrw iTCO_wdt mousedev acpi_cpufreq button gf128mul ioatdma processor serio_raw gpio_ich glue_helper enclosure iTCO_vendor_support wmi i7core_edac thermal_sys ixgbe mdio dca hwmon bnx2 Dec 29 11:47:15 Ishtar kernel: [70136.152131] CPU: 2 PID: 4776 Comm: smbd Not tainted 3.18.1-Isht-Van #2 Dec 29 11:47:15 Ishtar kernel: [70136.158655] Hardware name: Dell Inc. PowerEdge T610/0CX0R0, BIOS 6.3.0 07/24/2012 Dec 29 11:47:15 Ishtar kernel: [70136.166133] task: ffff880bf3cca510 ti: ffff880bf2208000 task.ti: ffff880bf2208000 Dec 29 11:47:15 Ishtar kernel: [70136.173611] RIP: 0010:[<ffffffff81235e4f>] [<ffffffff81235e4f>] generic_setlease+0x14f/0x6d0 Dec 29 11:47:15 Ishtar kernel: [70136.182141] RSP: 0018:ffff880bf220be58 EFLAGS: 00010286 Dec 29 11:47:15 Ishtar kernel: [70136.187449] RAX: 0000000000000082 RBX: ffff88134f6e4700 RCX: 0000000000000000 Dec 29 11:47:15 Ishtar kernel: [70136.194579] RDX: ffff880bf220be88 RSI: 0000000000000002 RDI: ffff88125104fbe8 Dec 29 11:47:15 Ishtar kernel: [70136.201708] RBP: ffff880bf220bec8 R08: 0000000000000235 R09: 0000000000004680 Dec 29 11:47:15 Ishtar kernel: [70136.208837] R10: 0000000000000000 R11: ef7bdef7bdef7bdf R12: ffff88125104f9e0 Dec 29 11:47:15 Ishtar kernel: [70136.215967] R13: ffff880bf220be88 R14: ffff88125104fbe8 R15: ffff881455590e00 Dec 29 11:47:15 Ishtar kernel: [70136.223096] FS: 00007f68d9ceb840(0000) GS:ffff88180ec00000(0000) knlGS:0000000000000000 Dec 29 11:47:15 Ishtar kernel: [70136.231178] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 29 11:47:15 Ishtar kernel: [70136.236917] CR2: 0000000000000038 CR3: 0000000bf2ded000 CR4: 00000000000007e0 Dec 29 11:47:15 Ishtar kernel: [70136.244045] Stack: Dec 29 11:47:15 Ishtar kernel: [70136.246052] ffff880bf220be78 ffffffff810851eb ffff880bf220be78 0000000000000001 Dec 29 11:47:15 Ishtar kernel: [70136.253478] ffff880bf220be98 ffff88125104fa68 ffff880bf220be88 ffff880bf220be88 Dec 29 11:47:15 Ishtar kernel: [70136.260900] ffff880bf220bed8 0000000000000002 ffff881455590e00 0000000000000400 Dec 29 11:47:15 Ishtar kernel: [70136.268325] Call Trace: Dec 29 11:47:15 Ishtar kernel: [70136.270774] [<ffffffff810851eb>] ? preempt_count_sub+0x4b/0x60 Dec 29 11:47:15 Ishtar kernel: [70136.276692] [<ffffffff812363f5>] vfs_setlease+0x25/0x30 Dec 29 11:47:15 Ishtar kernel: [70136.282004] [<ffffffff81237021>] fcntl_setlease+0x91/0xd0 Dec 29 11:47:15 Ishtar kernel: [70136.287491] [<ffffffff811f1ed8>] SyS_fcntl+0x308/0x6b0 Dec 29 11:47:15 Ishtar kernel: [70136.292716] [<ffffffff8139b85e>] ? trace_hardirqs_on_thunk+0x3a/0x3f Dec 29 11:47:15 Ishtar kernel: [70136.299156] [<ffffffff816dffd2>] system_call_fastpath+0x12/0x17 Dec 29 11:47:15 Ishtar kernel: [70136.305159] Code: aa 00 65 ff 0c 25 e0 a9 00 00 0f 84 b4 01 00 00 48 85 db 0f 84 d7 04 00 00 4c 8b 93 d8 00 00 00 4c 89 ea be 02 00 00 00 4c 89 f7 <41> ff 52 38 41 89 c4 48 8b 7d b8 e8 e1 92 4a 00 4c 89 ef e8 69 Dec 29 11:47:15 Ishtar kernel: [70136.330796] RSP <ffff880bf220be58> Dec 29 11:47:15 Ishtar kernel: [70136.334281] CR2: 0000000000000038
RIP and CR2 indicate fl->fl_lmops is NULL in generic_delete_lease: trace_generic_delete_lease(inode, fl); if (fl) error = fl->fl_lmops->lm_change(before, F_UNLCK, &dispose); spin_unlock(&inode->i_lock); locks_dispose_list(&dispose); Linda, could you create a bug report with this info and let us know the number?
Dec 29 11:47:15 Ishtar kernel: [70136.337924] ---[ end trace f2f2c0fe017f371e ]---
System unresponsive to keyboard or net...
...
reboot back to 3.17.3 .... still up and stable @using 3.17.3.
Hmm, so this is 3.18 regression. commit 5c97d7b1479982a48cf2129062b880c2555049ac Author: Kinglong Mee <kinglongmee@gmail.com> Date: Fri Aug 22 10:18:43 2014 -0400 locks: New ops in lock_manager_operations for get/put owner ============ and commit f328296e27414394f25cebaef4a111a82ce0df32 Author: Kinglong Mee <kinglongmee@gmail.com> Date: Fri Aug 22 10:18:43 2014 -0400 locks: Copy fl_lmops information for conflock in locks_copy_conflock() ============ look like suspects. Honza, Neil, any ideas? thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jiri Slaby wrote:
Linda, could you create a bug report with this info and let us know the number?
bugid 912569
commit 5c97d7b1479982a48cf2129062b880c2555049ac Author: Kinglong Mee <kinglongmee@gmail.com> Date: Fri Aug 22 10:18:43 2014 -0400
locks: New ops in lock_manager_operations for get/put owner ============ and
commit f328296e27414394f25cebaef4a111a82ce0df32 Author: Kinglong Mee <kinglongmee@gmail.com> Date: Fri Aug 22 10:18:43 2014 -0400
locks: Copy fl_lmops information for conflock in locks_copy_conflock() ============ look like suspects. Honza, Neil, any ideas?
thanks, -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
ellanios82 -
Jiri Slaby -
Linda Walsh -
Moby -
Patrick Shanahan