September 2012 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] [PATCH] fixup build of kernel-imx51 for armv7hl
by Dirk Müller 07 Sep '12

07 Sep '12

Hi, need to nuke a few more drivers that do not compile on ARM. Please apply TIA, Dirk

1 0

[opensuse-kernel] write lockups with Factory kernels
by Dirk Müller 07 Sep '12

07 Sep '12

Hi, starting since 3.6rcX in factory, I have regularly lockups in all code that tries to write to the filesystem. It doesn't happen immediately, but after a bit of an update of about a day, and with autobuild(or other builds) running in the background. The symptom is that starting at one particular point in time, no new writes to the filessytem are possible: All tasks are in "D" state with the backtrace ending in: [87428.047819] [<ffffffff8116548b>] __sb_start_write+0xcb/0x110 [87428.047826] [<ffffffff811801db>] mnt_want_write+0x1b/0x50 [87428.047832] [<ffffffff81172142>] do_last+0xa12/0xe70 [87428.047839] [<ffffffff81172661>] path_openat+0xc1/0x4c0 [87428.047846] [<ffffffff81172ec4>] do_filp_open+0x44/0xb0 [87428.047852] [<ffffffff81162865>] do_sys_open+0xf5/0x1e0 [87428.047859] [<ffffffff8156ad3d>] system_call_fastpath+0x1a/0x1f (basically mnt_want_write / __sb_start_write) the filesystem is ext4 mounted with data=writeback and noatime. Any idea where to start hunting? I went back from kernel-desktop to kernel- default, and I'll try kernel-vanilla next. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 2

[opensuse-kernel] irq_remap: disable IRQ remapping if any IOAPIC lacks an IOMMU
by acho＠suse.com 07 Sep '12

07 Sep '12

From: Seth Forshee <seth.forshee(a)canonical.com> Subject: irq_remap: disable IRQ remapping if any IOAPIC lacks an IOMMU Git-commit: 32ab31e01e2def6f48294d872d9bb42573aae00f Patch-mainline: v3.6-rc3~25^2~1 References: Date: Wed, 8 Aug 2012 08:27:03 -0500 The ACPI tables in the Macbook Air 5,1 define a single IOAPIC with id 2, but the only remapping unit described in the DMAR table matches id 0. Interrupt remapping fails as a result, and the kernel panics with the message "timer doesn't work through Interrupt-remapped IO-APIC." To fix this, check each IOAPIC for a corresponding IOMMU. If an IOMMU is not found, do not allow IRQ remapping to be enabled. v2: Move check to parse_ioapics_under_ir(), raise log level to KERN_ERR, and add FW_BUG to the log message v3: Skip check if IOMMU doesn't support interrupt remapping and remove existing check that the IOMMU count equals the IOAPIC count Acked-by: Suresh Siddha <suresh.b.siddha(a)intel.com> Signed-off-by: Seth Forshee <seth.forshee(a)canonical.com> Acked-by: Yinghai Lu <yinghai(a)kernel.org> Signed-off-by: Joerg Roedel <joerg.roedel(a)amd.com> Acked-by: Cho, Yu-Chen <acho(a)suse.com> --- drivers/iommu/intr_remapping.c | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) --- a/drivers/iommu/intr_remapping.c +++ b/drivers/iommu/intr_remapping.c @@ -752,6 +752,7 @@ int __init parse_ioapics_under_ir(void) { struct dmar_drhd_unit *drhd; int ir_supported = 0; + int ioapic_idx; for_each_drhd_unit(drhd) { struct intel_iommu *iommu = drhd->iommu; @@ -764,13 +765,20 @@ int __init parse_ioapics_under_ir(void) } } - if (ir_supported && ir_ioapic_num != nr_ioapics) { - printk(KERN_WARNING - "Not all IO-APIC's listed under remapping hardware\n"); - return -1; + if (!ir_supported) + return 0; + + for (ioapic_idx = 0; ioapic_idx < nr_ioapics; ioapic_idx++) { + int ioapic_id = mpc_ioapic_id(ioapic_idx); + if (!map_ioapic_to_ir(ioapic_id)) { + pr_err(FW_BUG "ioapic %d has no mapping iommu, " + "interrupt remapping will be disabled\n", + ioapic_id); + return -1; + } } - return ir_supported; + return 1; } int __init ir_dev_scope_init(void) -- 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] File System Problem in 12.2
by Günther J. Niederwimmer 03 Sep '12

03 Sep '12

Hello, I have a Problem with my 12.2 Installation for booting ? Question: Have the Kernel for the 12.2 a Problem with dmraid ? I have installed my new 12.2 on a new SSD with (U)EFI and like to include my old /home from the 12.1. /home is on a raid1 mounted with dmraid but the kernel from 12.2 can't include the raid1 ? Depency failed /home !! I have in moment not tested with mdadm but ..... -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 2

[opensuse-kernel] How to compile the kernel style "OpenSuSE"?
by João Silva 03 Sep '12

03 Sep '12

Hello, I have a doubt in the correct procedure for compiling the operating system kernel in OpenSUSE. I have sought help in forums, but nobody could help me, so I'm turning to you. I hope you can understand me, my English is not very good. I'm using version 12.1 of the "OpenSUSE" with kernel "1.3.10-1.16-default." After downloading the kernel source code and all the build dependencies via "YAST", run the following commands as "root": cd /usr/src/linux-3.1.10-1.16/; make clean; make mrproper; cp /boot/config-3.1.10-1.16-default ./.config; make menuconfig; At this stage I would not change any configuration of the kernel, just select the file ".config" and choose a name for the kernel that will be compiled. After these procedures, I save and start the build process via the command: make dep; make rpm; After waiting for the build is done, I checked the package ".rpm" generated has a size of 317 MB, and the repository of the "OpenSUSE", the size of this file is approximately 37 MB. After installing the kernel compiled, I noticed no difference in the number of generated binary files, only in their size. So, I wonder, because the kernel is compiled much mair than the kernel provided by the repository "OpenSUSE"?, And I'm using the same configuration. And what is the correct way to compile the kernel in OpenSUSE?. So I can generate a size compatible with the repository. Thank you for the information, João -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 8