January 2012 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] kernel 3.1 openSUSE 12.1/SLES SP2 : arp cache never decreasing - can block all network communications
by Bruno Friedmann 01 Feb '12

01 Feb '12

On a computer here setup years ago, we use the ip pass trough functionality of the router to get all the internet traffic directly on a network card setup with the external ip address. This has been work from years now, and if I restart the 12.1 with the older 11.4 kernel 2.6.37 it works too. Now what's happen, I get thousand of connection on that interface (dns behind) and the arp cache is full in terms of minutes I've already apply new values in sysctl.conf to have more time but it not a real working situation it seems on 3.1 some changes happened in the related code and here it seems to live a patch http://patchwork.ozlabs.org/patch/123208/ a simple ip neigh show | wc -l ARP : 2012-01-09 19:10:39 : 0 ARP : 2012-01-09 19:11:09 : 0 ARP : 2012-01-09 19:11:39 : 42 ARP : 2012-01-09 19:12:09 : 73 ... ARP : 2012-01-09 19:37:09 : 554 ARP : 2012-01-09 19:37:39 : 558 ARP : 2012-01-09 19:38:09 : 562 sysctl.conf # Patch for neibhboor table # Force gc to clean-up quickly net.ipv4.neigh.default.gc_interval = 3600 # Set ARP cache entry timeout net.ipv4.neigh.default.gc_stale_time = 3600 # Setup DNS threshold for arp net.ipv4.neigh.default.gc_thresh3 = 4096 net.ipv4.neigh.default.gc_thresh2 = 2048 net.ipv4.neigh.default.gc_thresh1 = 1024 if someone can drive me to build correctly under openSUSE 12.1 kernel the patch I can test it and report success or failure. Thanks -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 1

Fwd: [opensuse-kernel] Support for 3.1.x branch terminated. Upgrading from kernel 3.2 in openSUSE 12.1 expected?
by Кириллов Александр 30 Jan '12

30 Jan '12

> Just use the regular 12.1 update channel, no need for special repos. > It will get kernel updates with security and bugfixes for the lifetime. > > The openSUSE-12.1 branch will be supported by us for the 18 months > lifetime. > > e.g. 3.1.9 is in the update channel since friday. > > Ciao, Marcus In which repository is a 3.1.9? I'm not connected to the repository http://download.opensuse.org/repositories/Kernel:/openSUSE-12.1/standard/ Will there be a 3.1.9 repository http://download.opensuse.org/update/12.1/x86_64/ ? -- 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] Support for 3.1.x branch terminated. Upgrading from kernel 3.2 in openSUSE 12.1 expected?
by Кириллов Александр 29 Jan '12

29 Jan '12

Or should I install an out of his http://download.opensuse.org/repositories/Kernel:/openSUSE-12.1/standard/ (kernel-desktop-3.1.9-6.1.x86_64.rpm -- Newer than my installed kernel, but 3.1.X !!!). Or should I install an out of his http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ (kernel-desktop-3.2.1-3.1.x86_64.rpm -- Newer than my installed kernel, 3.2.X - SUPPORTED). But in this case, my system may become unstable due to the connection of such a repository. I need only supported by the kernel. P.S. OpenSUSE 12.1, kernel-desktop 3.1.0-1.2.1 (All updates are installed) -- 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] modprobe: Module ext4 not found. WARNING: no dependencies for kernel module 'ext4' found
by Anisha Kaul 25 Jan '12

25 Jan '12

Greetz, I compiled the kernel 3.1.0, and following are the warnings that I am getting: "linux-dopx:/usr/src/linux-3.1.0-1.2 # make installsh /usr/src/linux-3.1.0-1.2/arch/x86/boot/install.sh 3.1.0 arch/x86/boot/bzImage \ System.map "/boot" Kernel image: /boot/vmlinuz-3.1.0Initrd image: /boot/initrd-3.1.0Root device: /dev/disk/by-id/ata-ST3250310AS_6RYNQEXY-part2 (/dev/sda2) (mounted on / as ext4)Resume device: /dev/disk/by-id/ata-ST3250310AS_6RYNQEXY-part1 (/dev/sda1)find: `/lib/modules/3.1.0/kernel/drivers/ata': No such file or directorymodprobe: Module ata_generic not found.WARNING: no dependencies for kernel module 'ata_generic' found.modprobe: Module ext4 not found.WARNING: no dependencies for kernel module 'ext4' found.Features: block usb resume.userspace resume.kernelBootsplash: openSUSE (1280x1024)41713 blocks " The steps I took are: 1. make menuconfig 2. make bzImage 3. make modules 4. make modules_install 5. make install The platform is: # uname -a Linux linux-dopx 3.2.1-12-desktop #1 SMP PREEMPT Thu Jan 19 16:02:50 IST 2012 x86_64 x86_64 x86_64 GNU/Linux Rebooting says: "Could not load /lib/modules/3.1.0/modules.dep" What's the point that I am missing? -Anisha -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 10

[opensuse-kernel] no autofs (automount) after kernel update 3.2.1 (from 3.2.0) on openSUSE 11.4
by Dr. Ralf Czekalla 24 Jan '12

24 Jan '12

Greetings. Since I updated two of my test boxes to kernel 3.2.1 from 3.2.0, I can not use autofs any more. (both x86_64 and i586) I used this feature before (and still with the other openSUSE boxes running with kernel 3.2.0) to mount my private repository mirror via /net/<hostname>/srv/openSUSE-repository... and fetch the rpms in zypper via dir:///net/<hostname>/srv/openSUSE... in the repository definition. (I had to switch from nfs:// to dir:// here because of bug https://bugzilla.novell.com/show_bug.cgi?id=710269 since kernel 2.6.39.) Now with kernel 3.2.1 I can not initiate the mount as used to by executing "cd /net/<hostname>" any more. Only an error message that the file or directory is not found comes back. But I can mount the nfs share manually from the host without a problem. I did not change the setup of /etc/auto.master since it worked in 3.2.0. The rcautofs is started without an error but the syslog offers the following lines during its startup: Jan 23 20:41:29 Grenada automount[8826]: open_lookup:90: cannot open lookup module hosts (/usr/lib64/autofs/lookup_hosts.so: undefined symbol: getnetconfig) Jan 23 20:41:29 Grenada automount[8826]: mount_autofs_indirect: failed to read map for /net Jan 23 20:41:29 Grenada automount[8826]: handle_mounts: mount of /net failed! Jan 23 20:41:29 Grenada automount[8826]: master_do_mount: failed to startup mount It seems to be problem with the lookup_hosts.so. Has anybody else the same problem with automount? Best regards Ralf -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 1

[opensuse-kernel] Fixing Kernel release mismatch: 3.0.17-25-vanilla != 3.0.13-25-vanilla
by doiggl＠velocitynet.com.au 24 Jan '12

24 Jan '12

Hello, Currently I get this error: make: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0' ++ make -s kernelrelease -C /home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0 O=/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-obj + krel=3.0.17-25-vanilla + '[' 3.0.17-25-vanilla '!=' 3.0.13-25-vanilla ']' + echo 'Kernel release mismatch: 3.0.17-25-vanilla != 3.0.13-25-vanilla' Kernel release mismatch: 3.0.17-25-vanilla != 3.0.13-25-vanilla + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.hP9nU8 (%prep) Question -------- How can this error be fixed ? Thanks Glenn Project https://build.opensuse.org/package/show?package=kernel-vanilla&project=home… Log https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kerne… -- 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] How to get a pre-compiled kernel version 3.2 for OpenSuse 12.1?
by Anisha Kaul 24 Jan '12

24 Jan '12

On 19 January 2012 12:46, Greg KH <gregkh(a)suse.de> wrote: > Use the Kernel:stable repo, or the openSUSE:Tumbleweed repo, both of > them have them in there. > > greg k-h > http://download.opensuse.org/repositories/Kernel:/HEAD/standard/>> ... there has been virtually zero testing with it. It may work. It may> not. There is no pending release using it, so any bugs you encounter> should be reproduced with the vanilla 3.2 kernel before reporting it. >> - -Jeff> Thanks to Greg, and Jeff for the prompt replies. -- 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] Strange automounter disconnections
by ariel sabiguero yawelak 20 Jan '12

20 Jan '12

Hi all. I have a very simple automounter configuration, everything works but sometimes, some mounts fails and I need to restart autofs service in order to get them back working. No logs on either server / clients. The distro is OpenSuSE 11.4. Similar configuration with former versions worked flawlessly. The auto.net map follows (*): homes 192.168.1.50:/varios/01/homes socios 192.168.1.50:/varios/01/samba/socios usuarios 192.168.1.50:/varios/01/samba/usuarios sistemas 192.168.1.50:/varios/01/samba/sistemas local 192.168.1.50:/usr/local The following is the /etc/exports file: /varios/01/samba/socios @maquinas(rw,root_squash,sync,no_subtree_check) /varios/01/homes @maquinas(rw,root_squash,sync,no_subtree_check) /varios/01/samba/usuarios @maquinas(rw,no_subtree_check) /varios/01/samba/sistemas @maquinas(rw,no_subtree_check) /usr/local @maquinas(ro,no_subtree_check) I worked-around the problem by installing a cron job running every minute. It checks all the shares and if any fails, it issues a rcautofs restart. Have anyone experienced a similar issue? Could you please provide any clue or way to better debug the problem. regards ariel (*) - initially I got unknown-host messages in the log file, thus, I changed the export from hostnames to IP addresses, but did not fixed the issue. -- 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] after upgrade from 11.2 to 12.1: disk io hog/starvation issue on HW Raid ext4
by rst＠suissimage.ch 19 Jan '12

19 Jan '12

Hi y'all, I've been directed here by the opensuse forums about a problem we are having with our server since we upgraded from opensuse 11.2 (kernel 2.6.31 I believe) to 12.1. The problem is that one process can hog all disk io and starves others. For example progress database restore of multi GB DB starves all others for example mysqld. We see latencies on fsync for mysqld of 15s + with cfq block io scheduler. Still 5s+ with deadline block io scheduler and read_expire reduced to 20ms. Been unable to reduce latency for other processes any further. Our guess to the culprit is that the improvement that was made in 2.6.37 for smp ext4 block io throughput (300-400% according to Linux 2 6 37 - Linux Kernel Newbies ) has made it possible for one process to be that fast and created this starvation problem. Or maybe some kernel bug. Anybody have any pointers about how to reign in disk-io hogs in 3.1? best regards remo Some info about the Server: Dell T710 with 2 Xeon 6 core procs, 48GB Memory. 6x300GB Disks in RAID10 on a H700 Raid Controller. We didn't mess with many default Suse Kernel values. Except swapiness, default blocksize of Tape Driver, Max Semaphore and Shared Memory Segment Values ( /proc/sys/kernel/shmmax shmmni shmall). And of course the ioscheduler as deadline scheduler makes the system less unusable... I'll gladly provide any other info y'all might need to help us improve this starvation issue. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 5

[opensuse-kernel] Network installation failure on Dell XPS 8300
by Giacomo Comes 19 Jan '12

19 Jan '12

I have encountered an installation problem on a Dell XPS 8300 Its network device is Broadcom NetLink BCM57788 (pci id: 14e4:1691) When I do a network installation after loading the kernel and initrd I get the error: no network device found. This is the output when the module tg3 is loaded: tg3.c:v3.119 (May 18, 2011) tg3 0000:03:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 tg3 mdio bus: probed tg3 0000:03:00.0: No PHY devices tg3 0000:03:00.0: Problem fetching invariants of chip, aborting tg3 0000:03:00.0: PCI INT A disabled On the same PC a network installation of openSUSE 11.4 works. I was able to perform the network installation in the following way: I have recompilded openSUSE 12.1 kernel and modules replacing the sources tg3.c and tg3.h with the ones from 11.4 kernel sources (with some small changes in order to make them compile). Then I took the new tg3.ko and replaced the corresponding module in the initrd disk image for the network boot (in the file parts/00_lib). With the tg3 module I have compiled, the netwotk installation works. Of course after the installation the tg3 module of kernel 3.1 is the one that is used, and it works too. It's only during the installation that if fails to detect the network device. FYI, replacing the module tg3 in the initrd with the one compiled using the sources tg3.c and tg3.h from kernel 3.2 (tg3.c v3.121) didn't work either. I'm not filing a bugreport because I have found a solution for myself, but I am anyway reporting the issue in case somebody else found it useful. Giacomo -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0