May 2013 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] Samsung NP300V5A -- no backlight brightness change
by Денис Купляков 15 May '13

15 May '13

Hello all! Fn + F2(down) and Fn + F3(up) don't change brightness level of backlight on my Samsung NP300V5A laptop. I have OpenSUSE 12.3 with bumblebee installed as described in Wiki ( Repo URL: Index of /repositories/home:/Overman79:/Laptop/openSUSE_12.3 ). There we no brightness change before installation of bumblebee (so I don't think it has influence) With no special setup, I can't lower brightness (screen is flickering), and have 3 entries under /sys/class/backlight: Code: acpi0_backlight acpi1_backlight intel_backlight Haven't tried to manipulate them through console. With acpi_backlight=vendor, I can't up brightness, and have 2 entries: Code: intel_backlight samsung Changing brightness with intel_backlight through console seems OK, but changing it with samsung don't work, I can set only 0 or 1 brightness level(same with Fn-##) Code: dmesg | grep samsung [ 16.423716] samsung_laptop: enabled workaround for brightness stepping quirk [ 16.424060] samsung_laptop: detected SABI interface: SwSmi@ I have solved problem for me, by deleting strange workaround from samsung-laptop.c and recompiling module. I think that it is a bug. I can see that we have some notebooks models hardcoded in module for quirk workaround (there is no my model). So I think that actual bug is inside code that determines whether workaround is needed or not (it is check_for_stepping_quirk(..) function)). Also I don't clearly understand what #ifdef CONFIG_ACPI do. But I have no samsung-laptop-acpi related messages in logs. Diff for samsung-laptop.c: http://zalil.ru/34466753 Some related links: https://bugs.launchpad.net/ubuntu/+s...ux/+bug/810093 https://lists.ubuntu.com/archives/ke...er/018086.html -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 9

[opensuse-kernel] [PATCH] fix kernel-devel for armv7hl
by Dirk Müller 15 May '13

15 May '13

Hi, The patch below is needed for the openSUSE-12.3 branch in order to have the -kmp's compile correctly. Please apply. Ideally it should also be in master/. TIA, Dirk

2 2

Re: [opensuse-kernel] Headphones work with Kernel 3.8, but not kernel 3.9--Speakers OK on both
by Edward Reiss 14 May '13

14 May '13

On Tuesday, May 14, 2013 03:15:26 PM Basil Chupin wrote: > Have you tried disabling pulseaudio? And then checking with alsamixer > the settings for the channels after using F6 to set your audio card? > > If you must have pulseaudio, do you have pavucontrol installed (and the > headphones selected)? > > BC > > I did the following steps: 1) Disable PulseAudion in YaST 2) Reboot 3) Test with headphones--silence 4) Unplug headphones--I hear sound 5) Install pavucontrol 6) Select Output Devices 7) Select Headhones--I see the bar moving, which indicates pavucontrol is sending the sound to the headphones, but no sound in headphones I even re-installed pulseaudio according to the instrucyions in the Timbleweed thread on the openSUSE forums. No change. Is there a reason you believe it is a pulse audio issue? Thank you -- Quis custodiet ipsos custodes? -- 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] Headphones work with Kernel 3.8, but not kernel 3.9--Speakers OK on both
by Edward Reiss 14 May '13

14 May '13

When I upgraded the kernel to 3.9, for some reason I get no sound through the headphones, but the speaker works fine. I went through the typical troubleshooting steps, e.g. editing /etc/modprobe.d/50-sound.conf, with no luck. So I tried the earlier kernel and much to my surprise, it worked! I did an lsmod on both kernels and they both have the same modules loaded, though as expected the 3.9 modules are of different sizes. I suspect there is an issue with the drivers, but I really don't know how to procede at this time. My sound card/mixer settings are OK because everything works with kernel 3.8; the ONLY difference is the kernel and some of the modules. I have the ICH9 chipset. Here is the output of the ALSA debug: 3.9 Kernel http://www.alsa-project.org/db/?f=7ce3c0a19dde078619a3c16bb8fce1f861226679 3.8 Kernel http://www.alsa-project.org/db/?f=1b5e4d7aaf024caed25c47f6f9c7645608ad5106 I have a bug opened with ID 818828 -- Edward Reiss <ebreiss(a)gmail.com> -- 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:HEAD: kernel: ida_remove called for id=0 which is not allocated.
by Cristian Rodríguez 08 May '13

08 May '13

Hi: Is the message is $SUBJECT something to be concerned about or a bug ? Unfortunately no extra information is shown about what subsystem or piece of code called ida_remove with id=0.. Cheers. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 8

Re: [opensuse-kernel] Built-in kernel drivers
by Jeff Mahoney 07 May '13

07 May '13

On 5/7/13 10:04 AM, Jan Beulich wrote: >>>> On 07.05.13 at 15:52, Jeff Mahoney <jeffm(a)suse.com> wrote: >> On 5/6/13 10:05 AM, Jean Delvare wrote: >>> pci/drivers/ioapic >> >> I think this is used all over the place. > > No, it isn't. This is only about hot pluggable I/O-APICs, which is a > pointless business on x86 (as the rest of the infrastructure to > support this is missing). At most IA64 ever had a use for this, > which is why some time ago I actually submitted the patch to allow > this to be a module on x86 (so one could keep building it, but > wouldn't have it around all the time). > > Furthermore, I guess even on IA64 it was dead code (maybe just > following some never implemented spec), because up until that > very patch the driver didn't even have its ID table right, i.e. > would never have got bound to a matching device by the PCI > core. Ok, thanks for weighing in. I scanned sysfs and dmesg real quick to see if I could find matching strings and found something similar. Must've been the regular ioapic. -Jeff -- Jeff Mahoney SUSE Labs

1 0

[opensuse-kernel] PCI support on S/390
by Jean Delvare 06 May '13

06 May '13

Hi Jeff, PCI support was recently added to S/390. In our commit a952042e2ea9b1d50c6488f1e3aad61cc7e3434a the support became available but you went for CONFIG_PCI=n. Was it a default choice or a deliberate choice? It happens that this indirectly causes a build failure, due to missing Kconfig dependencies. While the root cause should be addressed, setting CONFIG_PCI=y in all s390x config files would solve the problem too. So, unless you or anyone has a good reason for not including PCI support in our 64-bit S/390 kernels, I'd rather just do that to fix the build, and let upstream deal with the missing dependencies. -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0

[opensuse-kernel] 3.7.10-1.4-desktop: iwl3945 dropped off - hardware or software?
by Andrey Borzenkov 04 May '13

04 May '13

As I just recently updated kernel on 12.3 I /hope/ it may be software issue (I would really hate to be forced into replacing this notebook ...) 2013-05-04T19:47:04.129268+04:00 opensuse kernel: [20145.070514] iwl3945 0000:0c:00.0: HARDWARE GONE?? INTA == 0xffffffff 2013-05-04T19:47:04.556376+04:00 opensuse kernel: [20145.568196] iwl3945 0000:0c:00.0: Error sending C_TX_PWR_TBL: time out after 500ms. 2013-05-04T19:47:04.556443+04:00 opensuse kernel: [20145.568212] iwl3945 0000:0c:00.0: Error setting Tx power (-110). 2013-05-04T19:47:05.116304+04:00 opensuse kernel: [20146.128198] iwl3945 0000:0c:00.0: Error sending C_RXON: time out after 500ms. 2013-05-04T19:47:05.116366+04:00 opensuse kernel: [20146.128213] iwl3945 0000:0c:00.0: Error clearing ASSOC_MSK on current configuration (-110). 2013-05-04T19:47:05.916390+04:00 opensuse kernel: [20146.928197] iwl3945 0000:0c:00.0: Error sending C_RXON: time out after 500ms. 2013-05-04T19:47:05.916459+04:00 opensuse kernel: [20146.928212] iwl3945 0000:0c:00.0: Error clearing ASSOC_MSK on current configuration (-110). 2013-05-04T19:47:06.452371+04:00 opensuse kernel: [20147.464146] iwl3945 0000:0c:00.0: Queue 4 stuck for 2396 ms. 2013-05-04T19:47:06.452438+04:00 opensuse kernel: [20147.464159] iwl3945 0000:0c:00.0: On demand firmware reload 2013-05-04T19:47:06.476406+04:00 opensuse kernel: [20147.488195] iwl3945 0000:0c:00.0: Error sending C_RXON: time out after 500ms. 2013-05-04T19:47:06.476463+04:00 opensuse kernel: [20147.488210] iwl3945 0000:0c:00.0: Error clearing ASSOC_MSK on current configuration (-110). 2013-05-04T19:47:06.476472+04:00 opensuse kernel: [20147.488596] ieee80211 phy0: Hardware restart was requested 2013-05-04T19:47:06.606798+04:00 opensuse kernel: [20147.489230] ------------[ cut here ]------------ 2013-05-04T19:47:06.630767+04:00 opensuse kernel: [20147.489230] WARNING: at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.7.10/linux-3.7/drivers/net/wireless/iwlegacy/common.c:117 _il_grab_nic_access+0x80/0x90 [iwlegacy]() 2013-05-04T19:47:06.630855+04:00 opensuse kernel: [20147.489230] Hardware name: XPS M1330 2013-05-04T19:47:06.630912+04:00 opensuse kernel: [20147.489230] Timeout waiting for ucode processor access (CSR_GP_CNTRL 0xffffffff) 2013-05-04T19:47:06.630969+04:00 opensuse kernel: [20147.489230] Modules linked in: loop nls_utf8 fuse ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables af_packet rfcomm bnep snd_hda_codec_idt nvidia(PO) snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss arc4 snd_pcm iwl3945 iwlegacy btusb r852 snd_seq snd_timer mac80211 acpi_cpufreq snd_seq_device uvcvideo sm_common nand videobuf2_core mtd bluetooth mperf iTCO_wdt iTCO_vendor_support coretemp snd_mixer_oss videodev kvm_intel sr_mod gpio_ich nand_ids lpc_ich nand_bch kvm r592 tg3 snd cfg80211 cdrom bch ata_piix firewire_ohci firewire_core i2c_i801 sdhci_pci videobuf2_vmalloc sdhci memstick videobuf2_memops mmc_core rfkill mfd_core nand_ecc soundcore crc_itu_t dell_laptop snd_page_alloc button video battery dell_wmi sparse_keymap pcspkr joydev dcdbas wmi ac microcode sg pciehp pci_hotplug autofs4 dm_mod linear thermal processor thermal_sys scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac scsi_dh_alua scsi_ dh ata_generic 2013-05-04T19:47:06.631094+04:00 opensuse kernel: [20147.489230] Pid: 19670, comm: kworker/0:2 Tainted: P O 3.7.10-1.4-desktop #1 2013-05-04T19:47:06.631153+04:00 opensuse kernel: [20147.489230] Call Trace: 2013-05-04T19:47:06.631218+04:00 opensuse kernel: [20147.489230] [<ffffffff81004818>] dump_trace+0x88/0x300 2013-05-04T19:47:06.631270+04:00 opensuse kernel: [20147.489230] [<ffffffff8158b0f3>] dump_stack+0x69/0x6f 2013-05-04T19:47:06.631324+04:00 opensuse kernel: [20147.489230] [<ffffffff81045249>] warn_slowpath_common+0x79/0xc0 2013-05-04T19:47:06.631379+04:00 opensuse kernel: [20147.489230] [<ffffffff81045345>] warn_slowpath_fmt+0x45/0x50 2013-05-04T19:47:06.631436+04:00 opensuse kernel: [20147.489230] [<ffffffffa0491f40>] _il_grab_nic_access+0x80/0x90 [iwlegacy] 2013-05-04T19:47:06.631494+04:00 opensuse kernel: [20147.489230] [<ffffffffa049260f>] il_wr_prph+0x3f/0xb0 [iwlegacy] 2013-05-04T19:47:06.631550+04:00 opensuse kernel: [20147.489230] [<ffffffffa04927ea>] il_apm_init+0x16a/0x1d0 [iwlegacy] 2013-05-04T19:47:06.631608+04:00 opensuse kernel: [20147.489230] [<ffffffffa04813b9>] il3945_apm_init+0x19/0x150 [iwl3945] 2013-05-04T19:47:06.631666+04:00 opensuse kernel: [20147.489230] [<ffffffffa0481d37>] il3945_hw_nic_init+0x37/0x5c0 [iwl3945] 2013-05-04T19:47:06.631723+04:00 opensuse kernel: [20147.489230] [<ffffffffa047cf28>] __il3945_up+0xb8/0x2c0 [iwl3945] 2013-05-04T19:47:06.631781+04:00 opensuse kernel: [20147.489230] [<ffffffffa047d438>] il3945_mac_start+0x308/0x6a0 [iwl3945] 2013-05-04T19:47:06.631838+04:00 opensuse kernel: [20147.489230] [<ffffffffa03ed5a9>] ieee80211_reconfig+0x1b9/0x1540 [mac80211] 2013-05-04T19:47:06.631896+04:00 opensuse kernel: [20147.489230] [<ffffffffa03c772a>] ieee80211_restart_work+0x8a/0xb0 [mac80211] 2013-05-04T19:47:06.631963+04:00 opensuse kernel: [20147.489230] [<ffffffff810616ab>] process_one_work+0x12b/0x4d0 2013-05-04T19:47:06.632021+04:00 opensuse kernel: [20147.489230] [<ffffffff81062f1d>] worker_thread+0x15d/0x460 2013-05-04T19:47:06.632073+04:00 opensuse kernel: [20147.489230] [<ffffffff810681c3>] kthread+0xb3/0xc0 2013-05-04T19:47:06.632127+04:00 opensuse kernel: [20147.489230] [<ffffffff8159ebbc>] ret_from_fork+0x7c/0xb0 2013-05-04T19:47:06.632187+04:00 opensuse kernel: [20147.489230] ---[ end trace 39be7e3c2c923f40 ]--- 2013-05-04T19:47:07.457687+04:00 opensuse kernel: [20148.447715] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b 0xf802020 2013-05-04T19:47:07.457961+04:00 opensuse kernel: [20148.447727] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5 2013-05-04T19:47:07.587995+04:00 opensuse kernel: [20148.578302] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b 0xf802020 2013-05-04T19:47:07.588244+04:00 opensuse kernel: [20148.578310] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5 2013-05-04T19:47:07.718239+04:00 opensuse kernel: [20148.708746] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b 0xf802020 2013-05-04T19:47:07.718465+04:00 opensuse kernel: [20148.708754] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5 2013-05-04T19:47:07.848300+04:00 opensuse kernel: [20148.839420] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b 0xf802020 2013-05-04T19:47:07.849108+04:00 opensuse kernel: [20148.839427] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5 2013-05-04T19:47:07.957739+04:00 opensuse kernel: [20148.969774] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b 0xf802020 2013-05-04T19:47:07.957819+04:00 opensuse kernel: [20148.969781] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5 2013-05-04T19:47:07.957875+04:00 opensuse kernel: [20148.970107] iwl3945 0000:0c:00.0: Unable to initialize device after 5 attempts. 2013-05-04T19:47:08.982264+04:00 opensuse kernel: [20149.994311] ieee80211 phy0: wlan0: No probe response from AP 4c:ac:0a:70:e2:cf after 500ms, disconnecting. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0

Re: [opensuse-kernel] kernel 3.8 and 3.9 crash/reboot
by Jean Delvare 03 May '13

03 May '13

Please keep the list included so that others can help too. Le Friday 03 May 2013 à 11:53 +0200, Klier Rainer a écrit : > Am 03.05.2013 11:08, schrieb Jean Delvare: > > Did you notice any fan spinning difference between kernel 3.7 and kernel > > 3.8 (for example fan spinning with 3.7 and no longer with 3.8)? > > YES! > you are right! > > at 3.7 the fan runs the whole time. > at 3.8/3.9 it starts and stops from time to time, and is off most of the > time. > > this is one of the first things i noticed, when i tried 3.8 the first time. > > so it sounds very plausible to me, that this can be the problem. Check in the BIOS if there is any option related to thermal management or fan speed. This may help you work around the issue until it gets properly fixed, and also hint at what the problem may be. > > Install sensors and see if it reports some temperature value. Maybe run > > sensors-detect to get additional temperature sensors (from the coretemp > > driver most probably.) Compare the temperatures (and any thermal setting > > you can find) between kernels 3.7 and 3.8. > > > > Also compare powertop output between kernels, to make sure that C states > > and cpufreq are working the same. > > thanks for the tips. > > do you know a way to force the fan to run the whole time? > with 3.7 it does it automatically, but not with 3.8/3.9. > if i know how to control the fan, ich can force it to work the whole > time with 3.8/3.9. I don't think there is any generic way to force an ACPI-controlled fan to full speed. What you can do is compare the contents and attributes of /sys/class/thermal. You should see active and passing cooling devices as well as thermal zones. Maybe something is missing or wrong with kernel 3.8+. For example, trip points may be wrong. -- Jean Delvare Suse L3 -- 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 3.8 and 3.9 crash/reboot
by Klier Rainer 03 May '13

03 May '13

hi, since kernel 3.8 i have the following problem with my hp compaq 8710w notebook: https://bugzilla.novell.com/show_bug.cgi?id=807312 it reboots itself after some time with now noticeable error. does anybody of you also use a 8710w notebook and runs kernel 3.8 or 3.9 without problems? kernel 3.7.10 is working fine. or does anybody know this problem? -- Rainer Klier Research & Development xyzmo Software GmbH, SIGNificant E-Signature Solutions A-4052 Ansfelden, Haiderstraße 23 Tel.: +43 7229 88060-0, E-Mail: rainer.klier(a)xyzmo.com N��r��y隊Z)z{.��w��칻�&ޢ��'��-��w�zf��^�ˬzG��~� ޮ�^�ˬz��

2 2