February 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 731197] New: Lenovo 3000 G410: Kernel panic whan pressing Fn+F2
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=731197 https://bugzilla.novell.com/show_bug.cgi?id=731197#c0 Summary: Lenovo 3000 G410: Kernel panic whan pressing Fn+F2 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gagarin.gtn(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 On my laptop Fn+F2 keyboard shortcut used to turn on/off screen backlight. When I'm pressing it first time, screen backlight turns off. I can wake up the screen by tapping on touchpad or pressing any key (And it works fine). But when I am pressing Fn+F2 again (hoping that that will turn backlight on) kernel panic occurs and I need to reboot my computer. Reproducible: Always Steps to Reproduce: 1. Press Fn+F2 2. Press Fn+F2 again Actual Results: Kernel panic Expected Results: Turning screen backlight on and off. Unfortunately I don't know where to get additional info about this kernel panic. Should I attach photo of the screen or there is anther way to get this info after reboot? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 727379] New: BUG: soft lockup - CPU#2 stuck for 67s!
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=727379 https://bugzilla.novell.com/show_bug.cgi?id=727379#c0 Summary: BUG: soft lockup - CPU#2 stuck for 67s! Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: bernd(a)helber-it-services.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=459622) --> (http://bugzilla.novell.com/attachment.cgi?id=459622) hardware infos -->hwinfo >>hwinfo.txt User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 Box got partially frozen... but wasn't killed completely. SSHD was killed, but the system was responsive regarding network access. Also a few processes seemed to be alive. On the System/Serial Console i received those messages [88416.412007] BUG: soft lockup - CPU#2 stuck for 67s! [sshd:8681] It seemed also that there was an issue with the pacemaker/Corosync Lock Manager. --------------------------------------------------------------------------- [88404.312002] Process lrmd (pid: 3701, threadinfo ffff8802069dc000, task ffff88020ff52740) [88404.312002] Stack: [88404.312002] ffffffff811dd094 ffff88020ff52740 ffff88020fe24d4c 00000136fffff000 [88404.312002] ffff88015569cbc0 ffff8801557b7b40 0000000000000182 0000000000000000 [88404.312002] 0000000000001000 ffff88015569cbc0 ffffffff811bda49 ffff880100000001 --------------------------------------------------------------------------- What makes me really wonder Iptables seemed to be responsive. Between the Traces, i was able to see those Messages. ----------------------------------------------------------------------- [88416.416002] [<ffffffff81002e4b>] system_call_fastpath+0x16/0x1b [88416.416002] [<00007f518dc6d080>] 0x7f518dc6d080 [88422.307225] iptables denied: IN=br0 OUT= PHYSIN=eth1 MAC=01:00:5e:00:00:01:00:24:21:5f:a8:c3:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [88422.338187] SFW2-INext-DROP-DEFLT IN=br0 OUT= MAC=33:00:00:00:00:00:24:21:5f:a8:c3:86:dd:60 SRC=0000:0000:0000:0000:0000:0000:0000:0000 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 OPT ( ) PROTO=ICMPv6 TYPE=130 CODE=0 [88488.308007] BUG: soft lockup - CPU#1 stuck for 67s! [lrmd:3701] [88488.312002 ------------------------------------------------------------------------- Reproducible: Couldn't Reproduce Steps to Reproduce: First appearance, but it made the impression that it could be a serious issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 726566] New: Kernel 3.1, Freeze, log errors and lost file
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=726566 https://bugzilla.novell.com/show_bug.cgi?id=726566#c0 Summary: Kernel 3.1, Freeze, log errors and lost file Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: aaatoja(a)o2.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Today I have updated kernel to 3.1 (http://download.opensuse.org/repositories/Kernel:/stable/standard/) 3 hours after update, I clicked a submit form button in Firefox and just after that lost normal screen and see green suse splash with cursor freezed in position of that button. After restart I see in logs: Oct 26 11:01:14 linux kernel: [11800.632590] ------------[ cut here ]------------ Oct 26 11:01:14 linux kernel: [11800.632603] kernel BUG at /usr/src/packages/BUILD/kernel-desktop-3.1.0/linux-3.1/mm/slab.c:3111! Oct 26 11:01:14 linux kernel: [11800.632615] invalid opcode: 0000 [#1] PREEMPT SMP Oct 26 11:01:14 linux kernel: [11800.632621] CPU 1 Oct 26 11:01:14 linux kernel: [11800.632623] Modules linked in: fuse ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit af_packet edd ip6t_REJECT nf_conntrack_ipv6 Oct 26 11:02:00 linux kernel: imklog 5.6.5, log source = /proc/kmsg started. Oct 26 11:02:00 linux rsyslogd: [origin software="rsyslogd" swVersion="5.6.5" x-pid="1245" x-info="http://www.rsyslog.com"] start Oct 26 11:02:00 linux kernel: [ 12.081407] splash_write_proc: Oct 26 11:02:00 linux kernel: [ 12.081409] splash_write_proc: unit: 0 Oct 26 11:02:00 linux kernel: [ 12.081410] splash_write_proc: show/hide Oct 26 11:02:00 linux kernel: [ 12.081412] splash_set_percent: console: 0 val: 8564 And I lost a file saved 3 minutes earlier (zero lenght). Reproducible: Sometimes Steps to Reproduce: 1. Not sure, short work on this kernel Actual Results: Green suse splash, computer freezed, lost a file -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 724338] New: BUG soft lockup CPU#0 stuck for 22s modprobe:645
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=724338 https://bugzilla.novell.com/show_bug.cgi?id=724338#c0 Summary: BUG soft lockup CPU#0 stuck for 22s modprobe:645 Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: rcoe(a)wi.rr.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I installed opensuse 12.1 Beta, and after the initial restart, the kernel locked up printing the message: BUG: soft lockup - CPU#0 stuck for 22s! (modprobe:645) It repeated the message several more times as I waited, but never completed to boot. Last message before BUG: udevd[370]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/power/level} for writing I powered off and powered on, and the system booted normally. Manufacturer: Hewlett-Packard Product Name: HP Compaq nc8430 (RB555UA) Version: F.15 Reproducible: Didn't try -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 712298] New: Wake from sleep causes filesystem module to crash (3.0/Tumbleweed)
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=712298 https://bugzilla.novell.com/show_bug.cgi?id=712298#c0 Summary: Wake from sleep causes filesystem module to crash (3.0/Tumbleweed) Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: tyler(a)monkeypox.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/15.0.846.0 Safari/535.1 SUSE/15.0.846.0 This has happened a couple times with the 3.0.0-39.1 kernel-desktop package from the Tumbleweed repository: Aug 12 19:22:30 kiwi kernel: [182076.434497] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 Aug 12 19:22:30 kiwi kernel: [182076.434515] IP: [<ffffffff813b92d1>] sd_revalidate_disk+0x31/0x320 Aug 12 19:22:30 kiwi kernel: [182076.434527] PGD 107352067 PUD 107358067 PMD 0 Aug 12 19:22:30 kiwi kernel: [182076.434534] Oops: 0000 [#1] PREEMPT SMP Aug 12 19:22:30 kiwi kernel: [182076.434541] CPU 1 Aug 12 19:22:30 kiwi kernel: [182076.434543] Modules linked in: udlfb fb_sys_fops sysimgblt sysfillrect syscopyarea tun sit tunnel4 ip6t_LOG xt_tcpudp xt_pk ttype ipt_LOG xt_limit joydev cdc_acm snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device vboxpci vboxnetadp vboxnetflt vboxdrv af_packet ip6t_REJECT nf_conntr ack_ipv6 nf_defrag_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conn track_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables cpufreq_conservative microcode cpufreq_userspace cpufreq_p owersave acpi_cpufreq mperf sha256_generic cbc edd dm_crypt loop dm_mod btusb bluetooth snd_hda_codec_conexant arc4 sg iwlagn i2c_i801 iTCO_wdt pcspkr iTCO_ vendor_support mac80211 snd_hda_intel snd_hda_codec snd_hwdep cfg80211 snd_pcm thinkpad_acpi snd_timer e1000e mei(C) snd_page_alloc battery tpm_tis rfkill t pm snd tpm_bios soundcore ac wmi i915 drm_kms_helper drm i2c_algo_bit button video fan pr Aug 12 19:22:30 kiwi kernel: ocessor thermal thermal_sys Aug 12 19:22:30 kiwi kernel: [182076.434681] Aug 12 19:22:30 kiwi kernel: [182076.434685] Pid: 14195, comm: hald-addon-stor Tainted: G C 3.0.0-39-desktop #1 LENOVO 7454CTO/7454CTO Aug 12 19:22:30 kiwi kernel: [182076.434696] RIP: 0010:[<ffffffff813b92d1>] [<ffffffff813b92d1>] sd_revalidate_disk+0x31/0x320 Aug 12 19:22:30 kiwi kernel: [182076.434705] RSP: 0018:ffff88012d5bdbb8 EFLAGS: 00010293 Aug 12 19:22:30 kiwi kernel: [182076.434710] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000001 Aug 12 19:22:30 kiwi kernel: [182076.434716] RDX: ffff8800365fb900 RSI: ffff8800365fb920 RDI: ffff880130b7ac00 Aug 12 19:22:30 kiwi kernel: [182076.434722] RBP: ffff880130b7ac00 R08: ffff88012d5bdb84 R09: 0000000000000006 Aug 12 19:22:30 kiwi kernel: [182076.434728] R10: 0000000000000001 R11: 0000000000000008 R12: 00000000ffffff85 Aug 12 19:22:30 kiwi kernel: [182076.434734] R13: ffff8801141feb58 R14: ffff880130b7ac00 R15: ffff88012d5bdc08 Aug 12 19:22:30 kiwi kernel: [182076.434741] FS: 00007fcdc01fd700(0000) GS:ffff88013bc80000(0000) knlGS:0000000000000000 Aug 12 19:22:30 kiwi kernel: [182076.434748] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Aug 12 19:22:30 kiwi kernel: [182076.434753] CR2: 0000000000000008 CR3: 0000000107360000 CR4: 00000000000406e0 Aug 12 19:22:30 kiwi kernel: [182076.434759] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Aug 12 19:22:30 kiwi kernel: [182076.434766] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Aug 12 19:22:30 kiwi kernel: [182076.434772] Process hald-addon-stor (pid: 14195, threadinfo ffff88012d5bc000, task ffff88012c886400) Aug 12 19:22:30 kiwi kernel: [182076.434780] Stack: Aug 12 19:22:30 kiwi kernel: [182076.434782] ffff88012d5bdc08 ffff8801141feb40 0000000000000000 00000000ffffff85 Aug 12 19:22:30 kiwi kernel: [182076.434792] ffff8801141feb58 ffffffff811c6d68 ffff8801141feb40 00000000812b93a3 Aug 12 19:22:30 kiwi kernel: [182076.434800] ffff880130b7ac78 ffff880130b7ac0c ffff880130b7ac00 0000000000000000 Aug 12 19:22:30 kiwi kernel: [182076.434809] Call Trace: Aug 12 19:22:30 kiwi kernel: [182076.434821] [<ffffffff811c6d68>] rescan_partitions+0xa8/0x320 Aug 12 19:22:30 kiwi kernel: [182076.434830] [<ffffffff81191bce>] __blkdev_get+0x2be/0x420 Aug 12 19:22:30 kiwi kernel: [182076.434838] [<ffffffff81191d92>] blkdev_get+0x62/0x2d0 Aug 12 19:22:30 kiwi kernel: [182076.434847] [<ffffffff8115ae34>] __dentry_open+0x184/0x3b0 Aug 12 19:22:30 kiwi kernel: [182076.434855] [<ffffffff8116ba48>] do_last+0x428/0x760 Aug 12 19:22:30 kiwi kernel: [182076.434862] [<ffffffff8116c203>] path_openat+0xd3/0x3f0 Aug 12 19:22:30 kiwi kernel: [182076.434869] [<ffffffff8116c56d>] do_filp_open+0x4d/0xc0 Aug 12 19:22:30 kiwi kernel: [182076.434876] [<ffffffff8115c451>] do_sys_open+0x101/0x1e0 Aug 12 19:22:30 kiwi kernel: [182076.434884] [<ffffffff81593892>] system_call_fastpath+0x16/0x1b Aug 12 19:22:30 kiwi kernel: [182076.434894] [<00007fcdbf781b20>] 0x7fcdbf781b1f Aug 12 19:22:30 kiwi kernel: [182076.434898] Code: 16 d1 9e 00 48 89 6c 24 10 48 89 5c 24 08 48 89 fd 4c 89 64 24 18 4c 89 6c 24 20 c1 e8 15 48 8b 9f 28 03 00 00 83 e0 07 83 f8 03 <4c> 8b 63 08 0f 87 8e 02 00 00 41 8b 84 24 50 06 00 00 31 d2 83 Aug 12 19:22:30 kiwi kernel: [182076.434952] RIP [<ffffffff813b92d1>] sd_revalidate_disk+0x31/0x320 Aug 12 19:22:30 kiwi kernel: [182076.434959] RSP <ffff88012d5bdbb8> Aug 12 19:22:30 kiwi kernel: [182076.434962] CR2: 0000000000000008 Aug 12 19:22:30 kiwi kernel: [182076.434967] ---[ end trace f6b4bf5dd71c313a ]--- Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. I use an encrypted ext3 USB volume in addition to my internal (SATA) encrypted volume, I'm assuming this is an issue with the USB one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 700290] New: Terrible slow pwrite() (and lseek/write) speed on ext4 filesystem
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=700290 https://bugzilla.novell.com/show_bug.cgi?id=700290#c0 Summary: Terrible slow pwrite() (and lseek/write) speed on ext4 filesystem Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: sergey1369(a)narod.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=434778) --> (http://bugzilla.novell.com/attachment.cgi?id=434778) Sample pwrite test program User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 I've got serious ext4fs performance problem on random write to large file (4GB). I've used attached program pwrite_test.c and found out that performance on same hardware is very different. On ext4 it takes about 1minute 26s, and on ext3 it takes 10seconds. I guess that something wrong with ext4 filesystem. Reproducible: Always Steps to Reproduce: # mkdir /mnt/sdb1 # mkfs.ext3 /dev/sdb1 # mount /dev/sdb1 /mnt/sdb1 # cc pwrite_test.c # time ./a.out Last sample writen at 4294901760 real 0m10.541s user 0m0.116s sys 0m1.314s # umount /dev/sdb1 # mkfs.ext4 /dev/sdb1 # mount /dev/sdb1 /mnt/sdb1 # time ./a.out Last sample writen at 4294901760 real 1m29.475s user 0m0.123s sys 0m0.805s Actual Results: (ext3) real time 0m10.541s (ext4) real 1m29.475s Expected Results: something about 10s for both filesystems.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 754049] New: Kernel Panic after reboot with a extra /usr ext4 partion
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=754049 https://bugzilla.novell.com/show_bug.cgi?id=754049#c0 Summary: Kernel Panic after reboot with a extra /usr ext4 partion Classification: openSUSE Product: openSUSE 12.2 Version: Milestone 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: fabian-mail(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Problem with Partion swap ext4 / ext4 /usr Reproducible: Always Steps to Reproduce: 1. Start Install 2. German 3. weiter (some next) 4. GNOME-Desktop 5. Remove "Separate Home-Partition" vorschlagen (mix german and englisch) 6. create 3 partions swap ext4 / ext4 /usr 7. change no defaults Actual Results: I test it on normal pc and can reproduce on VirtualBox. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 751664] New: Fail-safe mode does not work
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=751664 https://bugzilla.novell.com/show_bug.cgi?id=751664#c0 Summary: Fail-safe mode does not work Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Fail-safe mode brings the machine into a vegetative state. Reproducible: Always Steps to Reproduce: 1. Boot into Failsafe -- openSUSE 12.1 - 3.1.9-1.4. Actual Results: 1. showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe The system enters run level 5. After displaying the log-in prompt in console, the screen goes blank black and the keyboard is dead. There is no visible activity. Expected Results: 1. I would say, fail-safe boot should enter run level 2. Workaround: append "acpi=off". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 744237] New: No sound with Realtek/VIA (VT1708/A) HDA sound card.
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=744237 https://bugzilla.novell.com/show_bug.cgi?id=744237#c0 Summary: No sound with Realtek/VIA (VT1708/A) HDA sound card. Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jbrsubscribe(a)xs4all.nl QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=473425) --> (http://bugzilla.novell.com/attachment.cgi?id=473425) Various command output with relavant info. Also part of syslog. User-Agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en-GB) Presto/2.10.238 Version/12.00 Hardware scan on my system (Medion 8822) detects a Realtek/VIA VT1708/A HDA soundcard. The driver for this card (snd_hda_intel) appears NOT to load and the card is disabled. It appears that an 'ioremap' error is encountered by the kernel. The system log bears this out. As a result of this error, all sound is crippled. Reproducible: Always Steps to Reproduce: 1. Boot system 2. Try to reproduce sound 3. Sound card not recognized... no sound card installed (although card is recognized in Yast) Actual Results: No sound possible. Expected Results: No sound reproduction possible. Expected results: Sound card should work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 732923] New: Can't install Kobil CT-API and PC/SC drivers
by bugzilla_noreply＠novell.com 16 Feb '13

16 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=732923 https://bugzilla.novell.com/show_bug.cgi?id=732923#c0 Summary: Can't install Kobil CT-API and PC/SC drivers Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: peter.mark(a)onlinehome.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0 Hardware: Kobil TriB@nk This driverpackage from http://www.kobil.com/fileadmin/download/support/download/driver/ct-linux.zip cant't be installed since 12.1 (11.4 works fine). Msg output:{ Going to call CT_init CT_init (Port 1): -1 CT_Reset: -1 CT_Reset: 0 bedeutet Kartenleser gefunden. } Reproducible: Always Steps to Reproduce: 1. ./install32 from current installation directory 2. 3. Actual Results: Installer can't find the Reader Expected Results: Successful installation of Kobil-drivers -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2