February 2013 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] kernel-default-base-2.6.29-5.2.x86_64 rpm errors
by Dave Plater 18 Jul '24

18 Jul '24

Hi, I'm busy updating to the latest factory kernel and have received the following errors from kernel-default-base installation (I did insert a blank dvd during the installation of the rpm by zypper):- WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol register_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_ioctl WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_media_changed WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_get_media_event WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_release WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_open WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol unregister_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_number_of_slots And then these errors which I think IIRC happened before when the kernel was first split into three:- Kernel image: /boot/vmlinuz-2.6.29-rc8-5-default Initrd image: /boot/initrd-2.6.29-rc8-5-default Root device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part3 (/dev/sda3) (mounted on / as xfs) Resume device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part2 (/dev/sda2) FATAL: Module processor not found. WARNING: no dependencies for kernel module 'processor' found. FATAL: Module thermal not found. WARNING: no dependencies for kernel module 'thermal' found. FATAL: Module ata_generic not found. WARNING: no dependencies for kernel module 'ata_generic' found. FATAL: Module piix not found. WARNING: no dependencies for kernel module 'piix' found. FATAL: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. FATAL: Module fan not found. WARNING: no dependencies for kernel module 'fan' found. FATAL: Module xfs not found. WARNING: no dependencies for kernel module 'xfs' found. FATAL: Module usbhid not found. WARNING: no dependencies for kernel module 'usbhid' found. Kernel Modules: scsi_mod libata ata_piix edd ahci sd_mod usbcore ohci-hcd ehci-hcd uhci-hcd WARNING: /dev/shm/mkinitramfs.0drQsZ/mnt/lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 22669 blocks Should I open a bug report about the errors which are possibly from inserting a dvd while the kernel rpm was installing? Regards Dave P -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 2

[opensuse-kernel] CONFIG_CC_STACKPROTECTOR
by richard -rw- weinberger 14 Dec '13

14 Dec '13

Hi! I'm wondering why CONFIG_CC_STACKPROTECTOR is disabled on openSUSE. Debian and Fedora seem to enabled it per default. What's the deal? -- Thanks, //richard -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

7 17

[opensuse-kernel] "SLAB: Unable to allocate memory" vs. vm.swappiness & vm/vfs_cache_pressure?
by chrysippus＠operamail.com 01 Mar '13

01 Mar '13

On a 4GB RAM edge server running 12.2 w/ kernel 3.4.28/x86_64 I'm seeing an increasing frequency of "SLAB: Unable to allocate memory on node 0" (http://pastebin.com/xDPgtut8) errors in syslog, e.g.: cat /var/log/messages ... Feb 28 09:24:30 core kernel: [777611.883853] The following is only an harmless informational message. Feb 28 09:24:30 core kernel: [777611.883860] Unless you get a _continuous_flood_ of these messages it means Feb 28 09:24:30 core kernel: [777611.883864] everything is working fine. Allocations from irqs cannot be Feb 28 09:24:30 core kernel: [777611.883868] perfectly reliable and the kernel is designed to handle that. Feb 28 09:24:30 core kernel: [777611.883873] swapper/2: page allocation failure. order:4, mode:0x20 Feb 28 09:24:30 core kernel: [777611.883880] Pid: 0, comm: swapper/2 Tainted: P W O 3.4.28-2.20-default #1 Feb 28 09:24:30 core kernel: [777611.883885] Call Trace: Feb 28 09:24:30 core kernel: [777611.883908] [<ffffffff81004598>] dump_trace+0x78/0x2c0 Feb 28 09:24:30 core kernel: [777611.883921] [<ffffffff81532e6a>] dump_stack+0x69/0x6f Feb 28 09:24:30 core kernel: [777611.883933] [<ffffffff810fdf02>] warn_alloc_failed+0x102/0x1b0 Feb 28 09:24:30 core kernel: [777611.883946] [<ffffffff81101cfb>] __alloc_pages_nodemask+0x68b/0x9a0 Feb 28 09:24:30 core kernel: [777611.883959] [<ffffffff811401e2>] kmem_getpages+0x62/0x190 Feb 28 09:24:30 core kernel: [777611.883969] [<ffffffff81140ddf>] fallback_alloc+0x21f/0x270 Feb 28 09:24:30 core kernel: [777611.883981] [<ffffffff8114153b>] __kmalloc+0x14b/0x1d0 Feb 28 09:24:30 core kernel: [777611.883994] [<ffffffff8143e87c>] pskb_expand_head+0x8c/0x310 Feb 28 09:24:30 core kernel: [777611.884006] [<ffffffff814d9355>] ip6_forward+0x515/0x770 Feb 28 09:24:30 core kernel: [777611.884027] [<ffffffff81449712>] __netif_receive_skb+0x532/0x600 Feb 28 09:24:30 core kernel: [777611.884039] [<ffffffff81449881>] process_backlog+0xa1/0x180 Feb 28 09:24:30 core kernel: [777611.884049] [<ffffffff8144a280>] net_rx_action+0x140/0x230 Feb 28 09:24:30 core kernel: [777611.884062] [<ffffffff810459be>] __do_softirq+0xae/0x1c0 Feb 28 09:24:30 core kernel: [777611.884073] [<ffffffff8154724c>] call_softirq+0x1c/0x30 Feb 28 09:24:30 core kernel: [777611.884082] [<ffffffff810044e5>] do_softirq+0x75/0xb0 Feb 28 09:24:30 core kernel: [777611.884094] [<ffffffff81045d55>] irq_exit+0xa5/0xb0 Feb 28 09:24:30 core kernel: [777611.884105] [<ffffffff8100413b>] do_IRQ+0x5b/0xd0 Feb 28 09:24:30 core kernel: [777611.884115] [<ffffffff8153e5ea>] common_interrupt+0x6a/0x6a Feb 28 09:24:30 core kernel: [777611.884129] [<ffffffff8131861c>] intel_idle+0xec/0x160 Feb 28 09:24:30 core kernel: [777611.884141] [<ffffffff81412bfd>] cpuidle_idle_call+0x9d/0x240 Feb 28 09:24:30 core kernel: [777611.884152] [<ffffffff8100b5f5>] cpu_idle+0x65/0xd0 Feb 28 09:24:30 core kernel: [777611.884163] [<ffffffff8152be3d>] start_secondary+0x208/0x20d Feb 28 09:24:30 core kernel: [777611.884171] SLAB: Unable to allocate memory on node 0 (gfp=0x20) Feb 28 09:24:30 core kernel: [777611.884176] cache: size-65536, object size: 65536, order: 4 Feb 28 09:24:30 core kernel: [777611.884184] node 0: slabs: 19/19, objs: 19/19, free: 0 Feb 28 09:24:30 core kernel: [777611.886007] The following is only an harmless informational message. Feb 28 09:24:30 core kernel: [777611.886015] Unless you get a _continuous_flood_ of these messages it means Feb 28 09:24:30 core kernel: [777611.886018] everything is working fine. Allocations from irqs cannot be Feb 28 09:24:30 core kernel: [777611.886022] perfectly reliable and the kernel is designed to handle that. Feb 28 09:24:30 core kernel: [777611.886027] kswapd0: page allocation failure. order:4, mode:0x20 Feb 28 09:24:30 core kernel: [777611.886034] Pid: 35, comm: kswapd0 Tainted: P W O 3.4.28-2.20-default #1 Feb 28 09:24:30 core kernel: [777611.886038] Call Trace: Feb 28 09:24:30 core kernel: [777611.886061] [<ffffffff81004598>] dump_trace+0x78/0x2c0 Feb 28 09:24:30 core kernel: [777611.886073] [<ffffffff81532e6a>] dump_stack+0x69/0x6f Feb 28 09:24:30 core kernel: [777611.886085] [<ffffffff810fdf02>] warn_alloc_failed+0x102/0x1b0 Feb 28 09:24:30 core kernel: [777611.886097] [<ffffffff81101cfb>] __alloc_pages_nodemask+0x68b/0x9a0 Feb 28 09:24:30 core kernel: [777611.886110] [<ffffffff811401e2>] kmem_getpages+0x62/0x190 Feb 28 09:24:30 core kernel: [777611.886120] [<ffffffff81140ddf>] fallback_alloc+0x21f/0x270 Feb 28 09:24:30 core kernel: [777611.886132] [<ffffffff8114153b>] __kmalloc+0x14b/0x1d0 Feb 28 09:24:30 core kernel: [777611.886145] [<ffffffff8143e87c>] pskb_expand_head+0x8c/0x310 Feb 28 09:24:30 core kernel: [777611.886157] [<ffffffff814d9355>] ip6_forward+0x515/0x770 Feb 28 09:24:30 core kernel: [777611.886178] [<ffffffff81449712>] __netif_receive_skb+0x532/0x600 Feb 28 09:24:30 core kernel: [777611.886194] [<ffffffff81449881>] process_backlog+0xa1/0x180 Feb 28 09:24:30 core kernel: [777611.886210] [<ffffffff8144a280>] net_rx_action+0x140/0x230 Feb 28 09:24:30 core kernel: [777611.886229] [<ffffffff810459be>] __do_softirq+0xae/0x1c0 Feb 28 09:24:30 core kernel: [777611.886245] [<ffffffff8154724c>] call_softirq+0x1c/0x30 Feb 28 09:24:30 core kernel: [777611.886259] [<ffffffff810044e5>] do_softirq+0x75/0xb0 Feb 28 09:24:30 core kernel: [777611.886276] [<ffffffff81045d55>] irq_exit+0xa5/0xb0 Feb 28 09:24:30 core kernel: [777611.886291] [<ffffffff8100413b>] do_IRQ+0x5b/0xd0 Feb 28 09:24:30 core kernel: [777611.886304] [<ffffffff8153e5ea>] common_interrupt+0x6a/0x6a Feb 28 09:24:30 core kernel: [777611.886319] [<ffffffff8153e1d9>] _raw_spin_unlock_irqrestore+0x9/0x30 Feb 28 09:24:30 core kernel: [777611.886329] [<ffffffff8111a1b8>] compaction_alloc+0x288/0x2b0 Feb 28 09:24:30 core kernel: [777611.886342] [<ffffffff81144d83>] migrate_pages+0xb3/0x500 Feb 28 09:24:30 core kernel: [777611.886352] [<ffffffff8111ad47>] compact_zone+0x1d7/0x320 Feb 28 09:24:30 core kernel: [777611.886364] [<ffffffff8111af3b>] __compact_pgdat+0xab/0x170 Feb 28 09:24:30 core kernel: [777611.886374] [<ffffffff8111b237>] compact_pgdat+0x27/0x30 Feb 28 09:24:30 core kernel: [777611.886384] [<ffffffff8110dc8c>] balance_pgdat+0x6cc/0x710 Feb 28 09:24:30 core kernel: [777611.886396] [<ffffffff8110de18>] kswapd+0x148/0x370 Feb 28 09:24:30 core kernel: [777611.886407] [<ffffffff8105ec55>] kthread+0x85/0x90 Feb 28 09:24:30 core kernel: [777611.886417] [<ffffffff81547154>] kernel_thread_helper+0x4/0x10 Feb 28 09:24:30 core kernel: [777611.886426] SLAB: Unable to allocate memory on node 0 (gfp=0x20) Feb 28 09:24:30 core kernel: [777611.886430] cache: size-65536, object size: 65536, order: 4 Feb 28 09:24:30 core kernel: [777611.886439] node 0: slabs: 15/19, objs: 15/19, free: 4 Feb 28 09:24:38 core kernel: [777620.441021] The following is only an harmless informational message. Feb 28 09:24:38 core kernel: [777620.441029] Unless you get a _continuous_flood_ of these messages it means Feb 28 09:24:38 core kernel: [777620.441033] everything is working fine. Allocations from irqs cannot be Feb 28 09:24:38 core kernel: [777620.441036] perfectly reliable and the kernel is designed to handle that. Feb 28 09:24:38 core kernel: [777620.441042] swapper/1: page allocation failure. order:4, mode:0x20 Feb 28 09:24:38 core kernel: [777620.441048] Pid: 0, comm: swapper/1 Tainted: P W O 3.4.28-2.20-default #1 Feb 28 09:24:38 core kernel: [777620.441053] Call Trace: Feb 28 09:24:38 core kernel: [777620.441076] [<ffffffff81004598>] dump_trace+0x78/0x2c0 Feb 28 09:24:38 core kernel: [777620.441089] [<ffffffff81532e6a>] dump_stack+0x69/0x6f ... Atm, `slabtop` shows 99% usage for "ext4_inode_cache": slabtop Active / Total Objects (% used) : 1275578 / 1419483 (89.9%) Active / Total Slabs (% used) : 187764 / 187786 (100.0%) Active / Total Caches (% used) : 109 / 232 (47.0%) Active / Total Size (% used) : 639586.50K / 660294.86K (96.9%) Minimum / Average / Maximum Object : 0.02K / 0.46K / 4096.00K OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 606252 601064 99% 0.85K 151563 4 606252K ext4_inode_cache 380397 283799 74% 0.10K 10281 37 41124K buffer_head 241600 231794 95% 0.19K 12080 20 48320K dentry 34986 34973 99% 0.54K 4998 7 19992K inode_cache 27435 12674 46% 0.06K 465 59 1860K size-64 21952 21115 96% 0.03K 196 112 784K size-32 18734 18690 99% 0.11K 551 34 2204K sysfs_dir_cache 16086 14359 89% 0.55K 2298 7 9192K radix_tree_node 13475 11758 87% 0.05K 175 77 700K jbd2_inode ... This is with default values of: cat /proc/sys/vm/vfs_cache_pressure 100 cat /proc/sys/vm/swappiness 60 Reading @ http://doc.opensuse.org/documentation/html/openSUSE/opensuse-tuning/cha.tun…, and taking a random stab at changing echo 200 > /proc/sys/vm/vfs_cache_pressure echo 25 > /proc/sys/vm/swappiness Seems to reduce -- thought not completely eliminate -- the syslog errors. `slabtop` shows no change. After dropping cache sync && echo 3 > /proc/sys/vm/drop_caches `slabtop` usage for "ext4-inode_cache" seems to have dropped to 74%, although other items are still ~99%: slabtop Active / Total Objects (% used) : 130790 / 216154 (60.5%) Active / Total Slabs (% used) : 12482 / 12506 (99.8%) Active / Total Caches (% used) : 109 / 232 (47.0%) Active / Total Size (% used) : 40954.73K / 54620.83K (75.0%) Minimum / Average / Maximum Object : 0.02K / 0.25K / 4096.00K OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 60740 22518 37% 0.19K 3037 20 12148K dentry 23423 8006 34% 0.06K 397 59 1588K size-64 !! 21952 21119 96% 0.03K 196 112 784K size-32 !! 19397 19126 98% 0.54K 2771 7 11084K inode_cache !! 18734 18690 99% 0.11K 551 34 2204K sysfs_dir_cache 16687 4514 27% 0.10K 451 37 1804K buffer_head 4543 2173 47% 0.05K 59 77 236K anon_vma_chain 4200 3013 71% 0.12K 140 30 560K size-128 !! 4088 4072 99% 0.13K 146 28 584K ext4_groupinfo_4k !! 4084 4079 99% 1.00K 1021 4 4084K size-1024 3784 2956 78% 0.17K 172 22 688K vm_area_struct 3283 962 29% 0.55K 469 7 1876K radix_tree_node 2596 1484 57% 0.06K 44 59 176K anon_vma 2160 1798 83% 0.02K 15 144 60K dm_target_io 2116 1820 86% 0.04K 23 92 92K dm_io 2020 1687 83% 0.19K 101 20 404K size-192 1925 45 2% 0.05K 25 77 100K jbd2_inode 1845 1108 60% 0.25K 123 15 492K filp 1431 1344 93% 0.07K 27 53 108K Acpi-Operand --> 1408 1042 74% 0.85K 352 4 1408K ext4_inode_cache ... With this config, post clear, for ~ 20 minutes, no more SLAB errors in syslog. My understanding of the effect/beahvior of Memory Subsytem tuning is rudimentary at best. Chatting in #opensuse-server, IIUC, it seems that it's not leaking, but not automatically freeing up enough memory. (1) Are the SLAB errors I'm seeing indicative of a problem in the sysctl setting for swappiness & vfs_cache_pressure, particularly for server use? Or something else? (2) What, if any, specific/initial guidance or recommendation exists for these values for Opensuse server, not desktop, usage? Thanks. /C -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 7

[opensuse-kernel] 3.8 for 12.3?
by Andrey Borzenkov 28 Feb '13

28 Feb '13

According to http://lwn.net/Articles/540290/ 3.7.10 is going to be the last update for 3.7 series. Any chance for 12.3 to get 3.8? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 2

[opensuse-kernel] 3.4.34 for 12.2
by Hans-Peter Jansen 28 Feb '13

28 Feb '13

Hi, guess, it's time for a new kernel, due to: http://marc.info/?l=linux-kernel&m=136192380003161&w=2 Cheers, Pete -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 2

[opensuse-kernel] kernel: xhci_queue_intr_tx: N callbacks suppressed
by Cristian Rodríguez 27 Feb '13

27 Feb '13

Hi: I recently plugged a cheap-ass USB 3.0 PCI controller to my desktop. 4: PCI 200.0: 0c03 USB Controller [Created at pci.319] Unique ID: B35A.G7QrRCuD8R9 Parent ID: HnsE.9jym6yN0nc3 SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: usb controller Model: "VIA USB Controller" Vendor: pci 0x1106 "VIA Technologies, Inc." Device: pci 0x3432 SubVendor: pci 0x1106 "VIA Technologies, Inc." SubDevice: pci 0x3432 Revision: 0x03 Driver: "xhci_hcd" Driver Modules: "xhci_hcd" Memory Range: 0xf9800000-0xf9800fff (rw,non-prefetchable) IRQ: 45 (14414965 events) Module Alias: "pci:v00001106d00003432sv00001106sd00003432bc0Csc03i30" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (PCI bridge) it works but I am getting flooded with : kernel: xhci_queue_intr_tx: N callbacks suppressed (N is between 1 and 17) hundreds of times in my logs. This all happends when the only device which is currently plugged there a: 19: USB 00.0: 0000 Unclassified device [Created at usb.122] Unique ID: lcCT.E6C8KV8Ug_9 Parent ID: mozZ.4I_yH2puRXE SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:02:00.0/usb9/9-1/9-1.4/9-1.4:1.0 SysFS BusID: 9-1.4:1.0 Hardware Class: unknown Model: "Logitech Unclassified device" Hotplug: USB Vendor: usb 0x046d "Logitech, Inc." Device: usb 0x0825 Revision: "0.10" Serial ID: "A621BF00" Driver: "uvcvideo" Driver Modules: "uvcvideo" Device File: /dev/input/event18 Device Files: /dev/input/event18, /dev/input/by-id/usb-046d_0825_A621BF00-event-if00, /dev/input/by-path/pci-0000:02:00.0-usb-0:1.4:1.0-event Device Number: char 13:82 Speed: 480 Mbps Module Alias: "usb:v046Dp0825d0010dcEFdsc02dp01ic0Eisc01ip00in00" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #33 (Hub) Is in use. Looking at the sourcecode.. It probably comes from here.. http://lxr.free-electrons.com/source/drivers/usb/host/xhci-ring.c?a=arm#L30… /* FIXME change this to a warning and a suggestion to use new API 3049 * to set the polling interval (once the API is added). 3050 */ 3051 if (xhci_interval != ep_interval) { 3052 if (printk_ratelimit()) 3053 dev_dbg(&urb->dev->dev, "Driver uses different interval" 3054 " (%d microframe%s) than xHCI " 3055 "(%d microframe%s)\n", 3056 ep_interval, 3057 ep_interval == 1 ? "" : "s", 3058 xhci_interval, 3059 xhci_interval == 1 ? "" : "s"); 3060 urb->interval = xhci_interval; 3061 /* Convert back to frames for LS/FS devices */ 3062 if (urb->dev->speed == USB_SPEED_LOW || 3063 urb->dev->speed == USB_SPEED_FULL) 3064 urb->interval /= 8; 3065 } Ok, there is a limitation in the API according to the docs, no problem with that .. however I wonder why I am getting this message at all since neither CONFIG_USB_DEBUG or CONFIG_USB_XHCI_HCD_DEBUGGING are set in openSUSE kernel_HEAD. is this a bug (using dev_dbg instead of xhci_dbg) or I am missing something ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 2

[opensuse-kernel] README.SUSE still relevant?
by Michael Schneider 26 Feb '13

26 Feb '13

Hi, the current openSUSE sources do contain the file README.SUSE which is about "WORKING WITH THE SUSE 2.6.x KERNEL SOURCES" Is the information contained there still relevant? Regards, Mike -- 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] Increasing number of SUSE patches in kernel?
by Stefan Seyfried 22 Feb '13

22 Feb '13

Hi all, I was under the (apparently wrong) impression, that one goal was, to get the openSUSE kernel closer to upstream. Now I see a constant stream of patches for e.g. Hyper-V going into Kernel:HEAD, tagged with fate numbers that cannot even be found on features.opensuse.org. That brought up the following questions: * is there really a valid usecase to putting lots of non-upstream(?) Hyper-V stuff into openSUSE kernels? Is there even a user who uses openSUSE on Hyper-V? * what about the former goal of bringing the openSUSE kernel closer to mainline, thus lowering the maintenance burden? Best regards, seife -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 3

[opensuse-kernel] 12.3 kernel
by Stephan Kulow 22 Feb '13

22 Feb '13

Hi, Please remember to push a 12.3 kernel, there are quite some important fixes in there. Greetings, Stephan -- 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] libvirtd crash on any kind of AMD platform (mem_cgroup_create flat hierarchy)
by Bruno Friedmann 20 Feb '13

20 Feb '13

Before trying to push it further I would like to have your advise from a very specific trouble I encounter on any 12.2 (not yet tested on 12.3) kernel with amd platform 890 & 990 FX with phenom II (X4 or X6) or Phenom FX (8120 & 8350) I got a each boot time [ 24.297596] ------------[ cut here ]------------ [ 24.297613] WARNING: at /home/abuild/rpmbuild/BUILD/kernel- default-3.4.28/linux-3.4/mm/memcontrol.c:5007 mem_cgroup_create+0x3ac/0x510() [ 24.297620] Hardware name: GA-890GPA-UD3H [ 24.297625] Creating hierarchies with use_hierarchy==0 (flat hierarchy) is considered deprecated. If you believe that your setup is correct, we kindly ask you to contact linux-mm(a)kvack.org and let us know [ 24.297632] Modules linked in: xt_CLASSIFY xt_AUDIT xt_tcpudp ip6table_filter ip6_tables xt_state iptable_nat nf_nat ebtable_nat nf_conntrack_ipv4 ebtables nf_defrag_ipv4 nf_conntrack iptable_mangle nfnetlink af_packet ppp_generic slhc bridge stp iptable_filter ip_tables x_tables cpufreq_conservative cpufreq_userspace cpufreq_powersave quota_v2 quota_tree snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_pcm snd_seq snd_timer snd_seq_device firewire_ohci snd_mixer_oss snd firewire_core kvm_amd sp5100_tco shpchp edac_core soundcore ata_generic r8169 crc_itu_t pci_hotplug powernow_k8 mperf button edac_mce_amd sata_sil24 kvm k10temp serio_raw pcspkr i2c_piix4 sg e1000e snd_page_alloc wmi pata_jmicron edd microcode autofs4 usbhid dm_mod linear ohci_hcd ssb mmc_core pcmcia ehci_hcd pcmcia_core radeon xhci_hcd ttm usbcore drm_kms_helper drm usb_common i2c_algo_bit processor thermal_sys scsi_dh_rdac scsi_dh_hp_sw scsi_dh_emc scsi_dh_alua scsi_dh aacraid [ 24.297773] Pid: 2976, comm: libvirtd Not tainted 3.4.28-2.20-default #1 [ 24.297778] Call Trace: [ 24.297802] [<ffffffff81004598>] dump_trace+0x78/0x2c0 [ 24.297816] [<ffffffff81532e6a>] dump_stack+0x69/0x6f [ 24.297829] [<ffffffff8103ead9>] warn_slowpath_common+0x79/0xc0 [ 24.297840] [<ffffffff8103ebd5>] warn_slowpath_fmt+0x45/0x50 [ 24.297851] [<ffffffff8151c04c>] mem_cgroup_create+0x3ac/0x510 [ 24.297868] [<ffffffff810a7983>] cgroup_mkdir+0x103/0x3a0 [ 24.297881] [<ffffffff81160345>] vfs_mkdir+0xb5/0x170 [ 24.297894] [<ffffffff81164444>] sys_mkdirat+0xe4/0xf0 [ 24.297908] [<ffffffff81545c7d>] system_call_fastpath+0x1a/0x1f [ 24.297924] [<00007f424c541f77>] 0x7f424c541f76 [ 24.297929] ---[ end trace ac83d820627dc3ae ]--- On the 990FX 8350, with kernel 3.8+ I didn't have anymore this kind of trouble. Sometimes (but not easy to reproduce with a 100% accurate fashion) the virtual guest could crash or freeze (most of the time with iommu troubles) The different motherboard have all been updated to the latest bios available. (Asus, Gigabyte) I attach the full dmesg for inspection. If any of you is aware of something that could be tested or know already the issue and has a way to get it fixed, thanks to share your advise. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot

3 3