August 2014 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] 3.16.1 kernel for STABLE?
by Andreas Jaeger 19 Aug '14

19 Aug '14

HEAD is currently at 3.16.0 and stable at 3.15.8. Could somebody update, please? Thanks, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

7 11

[opensuse-kernel] [PATCH] rpm/kernel-binary.spec.in: Fix missing quotes around %build_flavor
by Andreas Schwab 18 Aug '14

18 Aug '14

%build_flavor can be an arbitrary string, so it needs to be quoted for string comparison. --- rpm/kernel-binary.spec.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rpm/kernel-binary.spec.in b/rpm/kernel-binary.spec.in index 9db7c12..e319036 100644 --- a/rpm/kernel-binary.spec.in +++ b/rpm/kernel-binary.spec.in @@ -27,9 +27,9 @@ %include %_sourcedir/kernel-spec-macros %define build_flavor @FLAVOR@ -%define build_default (%build_flavor == "default") -%define build_xen (%build_flavor == "xen" || %build_flavor == "ec2") -%define build_vanilla (%build_flavor == "vanilla") +%define build_default ("%build_flavor" == "default") +%define build_xen ("%build_flavor" == "xen" || "%build_flavor" == "ec2") +%define build_vanilla ("%build_flavor" == "vanilla") %define build_src_dir %my_builddir/linux-%srcversion %define src_install_dir /usr/src/linux-%kernelrelease%variant -- 2.1.0 -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] Kernel Oops 3.15.8-44
by bruce 18 Aug '14

18 Aug '14

Can anyone suggest what I might do to troubleshoot the issue below? Aug 16 18:38:28 myhost myhost kernel: [ 1088.683384] BUG: unable to handle kernel paging request at 000020000000001c Aug 16 18:38:28 myhost myhost kernel: [ 1088.700663] IP: [<ffffffff81140438>] find_get_entry+0x38/0xa0 Aug 16 18:38:28 myhost myhost kernel: [ 1088.718420] PGD 0 Aug 16 18:38:28 myhost myhost kernel: [ 1088.736230] Oops: 0000 [#1] PREEMPT SMP Aug 16 18:38:28 myhost myhost kernel: [ 1088.754186] Modules linked in: joydev fuse bnep bluetooth 6lowpan_iphc rfkill iTCO_wdt iTCO_vendor_support snd_hda_codec_hdmi snd_hda_c odec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec x86_pkg_temp_thermal intel_powerclamp r8169 sr_mod coretemp snd_hwdep cdrom kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_pcm pcspkr i2c_i801 lpc_ich mfd_core snd_seq snd_seq_device snd_timer sn d firewire_ohci firewire_core crc_itu_t soundcore mii shpchp mei_me mei battery sg dm_mod xhci_hcd i915 i2c_algo_bit drm_kms_helper drm fan thermal button video processor scsi_dh_rdac scsi_ dh_hp_sw scsi_dh_alua scsi_dh_emc scsi_dh Aug 16 18:38:28 myhost myhost kernel: [ 1088.843637] CPU: 0 PID: 3263 Comm: rsync Not tainted 3.15.8-44.g258e3b0-desktop #1 Aug 16 18:38:28 myhost myhost kernel: [ 1088.867519] Hardware name: Shuttle Inc. SH67H/FH67H, BIOS 2.02 05/07/2012 Aug 16 18:38:28 myhost myhost kernel: [ 1088.891478] task: ffff8807f3456210 ti: ffff8800d5130000 task.ti: ffff8800d5130000 Aug 16 18:38:28 myhost myhost kernel: [ 1088.915968] RIP: 0010:[<ffffffff81140438>] [<ffffffff81140438>] find_get_entry+0x38/0xa0 Aug 16 18:38:28 myhost myhost kernel: [ 1088.940933] RSP: 0018:ffff8800d5133bf0 EFLAGS: 00010246 Aug 16 18:38:28 myhost myhost kernel: [ 1088.966009] RAX: ffff88027f5dc590 RBX: 0000200000000000 RCX: 00000000fffffffa Aug 16 18:38:28 myhost myhost kernel: [ 1088.991279] RDX: ffff88027f5dc590 RSI: 0000000000010c1c RDI: 0000000000000020 Aug 16 18:38:28 myhost myhost kernel: [ 1089.016320] RBP: ffff880031056dc0 R08: ffff88027f5dc590 R09: ffff88027f5dc488 Aug 16 18:38:28 myhost myhost kernel: [ 1089.041668] R10: ffff8800d5133be0 R11: ffff8800d54193c0 R12: 0000000000010c1c Aug 16 18:38:28 myhost myhost kernel: [ 1089.067211] R13: 0000000000010c1c R14: 00000000000000d0 R15: ffff880031056db8 Aug 16 18:38:28 myhost myhost kernel: [ 1089.092686] FS: 00007f92f8bb6700(0000) GS:ffff88081f200000(0000) knlGS:0000000000000000 Aug 16 18:38:28 myhost myhost kernel: [ 1089.118417] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 16 18:38:28 myhost myhost kernel: [ 1089.144077] CR2: 000020000000001c CR3: 00000000d5337000 CR4: 00000000000407f0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.169884] Stack: Aug 16 18:38:28 myhost myhost kernel: [ 1089.195729] ffff880031056db8 0000000000010c1c 00000000010200da ffffffff81140e2c Aug 16 18:38:28 myhost myhost kernel: [ 1089.222377] ffffffff81833eb0 ffff8807f3644500 ffff880031056db8 ffffffff81140f8d Aug 16 18:38:28 myhost myhost kernel: [ 1089.249189] 0000000010c1c000 ffff8807f3644500 ffff880031056c68 ffff8800d5133d10 Aug 16 18:38:28 myhost myhost kernel: [ 1089.276017] Call Trace: Aug 16 18:38:28 myhost myhost kernel: [ 1089.302773] [<ffffffff81140e2c>] find_lock_entry+0x1c/0x70 Aug 16 18:38:28 myhost myhost kernel: [ 1089.329991] [<ffffffff81140f8d>] grab_cache_page_write_begin+0x5d/0xd0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.357577] [<ffffffff81232814>] ext4_da_write_begin+0x94/0x2e0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.385249] [<ffffffff81140681>] generic_perform_write+0xc1/0x1c0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.413046] [<ffffffff811426f3>] __generic_file_aio_write+0x1d3/0x3e0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.440808] [<ffffffff8114294b>] generic_file_aio_write+0x4b/0xc0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.468481] [<ffffffff81228932>] ext4_file_write+0x92/0x3b0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.496385] [<ffffffff811acdec>] do_sync_write+0x5c/0x90 Aug 16 18:38:28 myhost myhost kernel: [ 1089.524203] [<ffffffff811ad525>] vfs_write+0xb5/0x1e0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.551934] [<ffffffff811ae022>] SyS_write+0x42/0xa0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.579429] [<ffffffff81614bad>] system_call_fastpath+0x1a/0x1f Aug 16 18:38:28 myhost myhost kernel: [ 1089.606914] [<00007f92f80d29e0>] 0x7f92f80d29df Aug 16 18:38:28 myhost myhost kernel: [ 1089.634622] Code: fd 48 83 c5 08 53 e8 b8 88 f7 ff 4c 89 e6 48 89 ef e8 7d db 1c 00 48 85 c0 49 89 c0 74 3d 48 8b 18 48 85 db 74 25 f6 c 3 03 75 49 <8b> 53 1c 85 d2 74 d9 8d 72 01 48 8d 7b 1c 89 d0 3e 0f b1 73 1c Aug 16 18:38:28 myhost myhost kernel: [ 1089.665058] RIP [<ffffffff81140438>] find_get_entry+0x38/0xa0 Aug 16 18:38:28 myhost myhost kernel: [ 1089.694371] RSP <ffff8800d5133bf0> Aug 16 18:38:28 myhost myhost kernel: [ 1089.723570] CR2: 000020000000001c Aug 16 18:38:28 myhost myhost kernel: [ 1089.759887] ---[ end trace a3b65352af4cb807 ]--- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] Bug 889660 - nVidia proprietary driver does not consistently resume from sleep/suspend.
by Gordon Dickens 17 Aug '14

17 Aug '14

Hello everybody, I am inquiring about this bug: https://bugzilla.novell.com/show_bug.cgi?id=889660 In summary, when resuming from suspend, the proprietary nVidia driver fails to resume 25% to 50% of the timeand the screen becomes distorted and unusable. This has been an outstanding issue that has been reported in the OpenSUSE forum, KDE forum and other forums for over 6 months as noted in the aformentioned bug. The OpenSUSE kernel folks seem to think that its an nVidia bug. So, I filedabug report with nVidia who subsequently replied via email verbatim as follows: "there is not any error related to nvidia driver in log. I think this is issue with kernel other component." This email from nVidia, along with a log dump is included in comments 6, 7 and 8 in the OpenSUSE bug 889660 mentioned above. So, it appears that we arein an infinite loop with nVidia blaming the kernel folks and the kernel folks blaming nVidia. Another Arch Linux user reported that the failure to resume can be rectified in KDE by issuing "kwin --replace" via a hot key. I have found that worksfor me too. I believe that the fact that "Kwin --replace" rectifies the problem could be a very significant clue as to what is causing this problem. However, as a side note, after a few resumes with kwin--replace, /var/log/messages and /var/log/warn become HUGE with each growing by as much as 3GB per day. In any event, I have no idea if this is an nVidia problem, a kernel problem, a KDE problem or something else. Doesany of the OpenSUSE kernel developers have any ideasas to what is going on here and what can be done to fix this? At the very least,if the kernel developers believe that its an nVidia problem, then I respectfully request that a dialog be started with the nVidia Linux developers to solve this problem ASAP. nVidia is very popular graphics hardware and the opensource driver, Nouveau, has its own set of problems, primarily that it doesn't always redraw the screen properly when scrolling within a window. Therefore, some type of resolution needs to be attained especially prior to the release of OpenSUSE 13.2. Thanks for your consideration! Gordon -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

5 8

[opensuse-kernel] factory armv7l builds broken by omapdrm, patch available
by Josua Mayer 14 Aug '14

14 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, The armv7l builds of kernel-default for openSUSE Factory have been broken for quite a while now. Recently a patch fo fix the error with %x and omapdrm has landed in linux-next: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/dri… It would be nice if this patch could also be applied on the current 3.16 suse kernel. kind regards Josua Mayer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJT61ClAAoJEAgPKSyhCrKUEH0IAKvV3RYBcXFQXzYYKK+pomlm +cGAH+yQDCGC1uLnxpPzNfSQhIPbXM1B1VmxR4hFVlsLCqsfZvLuVS1RUIsskSYe PIJtTA4gX1mObsSJz9IOcLmqA6cbHB2EEdsvw5jjf4CUzChl5Gs+TBVUH4mkrRR5 myVk7nd6UkJiqbERiK2T7Ia6L4f/CAA3AzFPWAecb6jbR3fknTHz7/7TaYJvgfxa xYmAkGoGe7Dq1oYWXwKOyVhPRpeeYvZrErZiCWkEOOgLqb76Fpb7YjVKG3ullVaQ YpGs77pMIJhPCM6qwnff/uCqnigJyTBeEKM3+zB6LTBkVSNw9GqP8sPYASXxUHw= =bJKc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 4

[opensuse-kernel] taking ab0431059ed0d0e3a9e532ad0488ada25021249d
by Oliver Neukum 13 Aug '14

13 Aug '14

Hi, what do you think about taking ab0431059ed0d0e3a9e532ad0488ada25021249d platform: add chrome platform directory It is a major reorganisation, but necessary to fix bnc#882294 Regards Oliver -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 3

[opensuse-kernel] [PATCH] arm64/default: make rtc-pl03[01] built-in
by Andreas Schwab 13 Aug '14

13 Aug '14

--- config/arm64/default | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config/arm64/default b/config/arm64/default index 527b190..ae8c8ba 100644 --- a/config/arm64/default +++ b/config/arm64/default @@ -3590,8 +3590,8 @@ CONFIG_RTC_INTF_DEV=y # # on-CPU RTC drivers # -CONFIG_RTC_DRV_PL030=m -CONFIG_RTC_DRV_PL031=m +CONFIG_RTC_DRV_PL030=y +CONFIG_RTC_DRV_PL031=y # CONFIG_RTC_DRV_SNVS is not set # CONFIG_RTC_DRV_MOXART is not set CONFIG_RTC_DRV_XGENE=y -- 2.0.4 -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] [PATCH] arm64/default: increase LOG_BUF_SHIFT to 18
by Andreas Schwab 11 Aug '14

11 Aug '14

--- config/arm64/default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/arm64/default b/config/arm64/default index e6b60e1..edc70d4 100644 --- a/config/arm64/default +++ b/config/arm64/default @@ -103,7 +103,7 @@ CONFIG_RCU_NOCB_CPU=y CONFIG_RCU_NOCB_CPU_ALL=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y -CONFIG_LOG_BUF_SHIFT=14 +CONFIG_LOG_BUF_SHIFT=18 CONFIG_GENERIC_SCHED_CLOCK=y CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set -- 2.0.3 -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] hardware or kernel?
by Bruce Ferrell 10 Aug '14

10 Aug '14

I'm running the following kernel on 13.1 3.12.0-34.ge8fa6b4-desktop #1 SMP PREEMPT Mon Nov 4 13:06:33 UTC 2013 (e8fa6b4) x86_64 x86_64 x86_64 GNU/Linux And seeming the following message in dmesg with depressing regularity: [45080.377905] ata2.00: exception Emask n SAct 0x20 SErr 0x0 action 0x6 frozen [45080.377911] ata2.00: failed command: READ FPDMA QUEUED [45080.377917] ata2.00: cmd 60/01:28:00:2a:d4/00:00:4c:00:00/40 tag 5 ncq 512 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [45080.377920] ata2.00: status: { DRDY } [45080.377924] ata2: hard resetting link [45085.734173] ata2: link is slow to respond, please be patient (ready=0) [45090.428230] ata2: COMRESET failed (errno=-16) [45090.428236] ata2: hard resetting link [45095.784590] ata2: link is slow to respond, please be patient (ready=0) My question is do I have a bad disk, cable, motherboard or what might it be and how do I test? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

6 5

[opensuse-kernel] kernel-desktop-3.15.8-2.1.g258e3b0.x86_64 - Horrible Backlight Flicker (3.15.6 OK)
by David C. Rankin 08 Aug '14

08 Aug '14

All, I have the Kernel:/stable/standard/ repo configured (bug testing on backlight control) and today I pulled in the updated kernel: kernel-desktop-3.15.8-2.1.g258e3b0.x86_64 Every 1-2 seconds the backlight flickers horribly (not related to bug report of backlight keyboard keys not controlling backlight). It makes the laptop unusable. I booted back into kernel-desktop-3.15.6-2.1.gedc5ddf.x86_64 and all is fine. Does a bug report need to go somewhere? I know this is from Kernel:/stable/standard/, but if this is getting folded into factory, then a bug needs to go somewhere. Anybody have anything to check? The flicker starts as soon as the kernel is booted, is present during the splash screen and remain unchanged after the display and window managers load -- so it is kernel/module related and not desktop related... This is on a Toshiba p205d [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270]. I have never seen backlight flicker before on this laptop and dropping back to 3.15.6 all is fine. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1