April 2009 - openSUSE Kernel - openSUSE Mailing Lists

Re: [opensuse-kernel] after kernel update (-> 2.6.27.21-31), mkinitrd fails @ "Device md3 not handled"
by PGNet Dev 29 Apr '09

29 Apr '09

dennis, On Tue, Apr 28, 2009 at 4:58 PM, Dennis Gallion <dwgallien(a)bellsouth.net> wrote: > fwiw . . . I encountered the same problem after a recent update that was done > in conjunction with a VBox update; I also as using mdraid. Similar but not > identical error message as yours, but also thrown by that same script. My > workaround is to run mkinitrd with "rootdev=/dev/md1". I have done several > subsequent kernel/VBox updates, but the problem persists. ok, will try rootdev= when the problem next arises. thanks for the hint! -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] DomU kernel update to -> 2.6.27.21-35 causes hang on DomU relaunch
by PGNet Dev 27 Apr '09

27 Apr '09

i'm running OS 11.1/xen as Dom0, uname -ri 2.6.27.21-35-xen x86_64 i've launched a working OS11.1 DomU, cd /home/os111/ xm create -c OS111_T.cfg uname -ri 2.6.27.21-32-xen x86_64 all's well/functional with the DomU. updating the DomU's kernel with 'zypper dup Kernel.repo', where, cat Kernel.repo baseurl=http://download.opensuse.org/repositories/Kernel:/SL111_BRANCH/open… ... goes seemingly smoothly. next, @ DomU, shutdown -h now then @ Dom0, xm create -c OS111_T.cfg now hangs @, ... devices/virtual/input/input0 input: Xen Virtual Pointer as /devices/virtual/input/input1 PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP cubic registered registered taskstats version 1 XENBUS: Device with no driver: device/console/0 XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 284k freed Write protecting the kernel read-only data: 4424k xen-vbd: registered block device major 202 blkfront: xvda: barriers enabled xvda: xvda1 xvda2 netfront: Initialising virtual ethernet driver. SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled SGI XFS Quota Management subsystem device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel(a)redhat.com udevd version 128 started md: linear personality registered for level -1 and goes no further. :-/ @ Dom0, i kill the VM, xm destroy OS111_T then attempt to remove the LV, so as to replace/rebuild a working version, but 'lvremove' fails, lvremove -f /dev/VGU/vm_OS111_T Can't remove open logical volume "vm_OS111_T" reboot Dom0, try again, lvremove -f /dev/VGU/vm_OS111_T Logical volume "vm_OS111_T" successfully removed lvcreate -n vm_OS111_T -L 4G /dev/VGU Logical volume "vm_OS111_T" created after restore to a known working DomU, i'm back in business with the "old" kernel version, uname -ri 2.6.27.21-32-xen x86_64 is this a bug that's cropped up? thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] mkspec
by Jan Blunck 27 Apr '09

27 Apr '09

Is it really necessary to replace the spec file generation in tar-up.sh by a perl version called mkspec? I personally learned to hate perl. Additionally to my personal dislikes this introduces the first perl script that is necessary to build our kernel package. Is there any reason why we can't live with a shell version as we did before? Comments? Jan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 8

[opensuse-kernel] 2.6.30-rc3-master_20090423155553_3503087d x86_64
by Markus Koßmann 24 Apr '09

24 Apr '09

If I try to boot KOTD 2.6.30-rc3-master_20090423155553_3503087d x86_64 it fails miserably with : Probing EDD (edd=off to disable) ... ok PANIC : early exception 0e rip 10:ffffffff802f6e69 error 0 cr2 0 "Failsafe mode" doesn't change anything. Any ideas howto debug that further ? Hardware is Athlon 64 X2 on AMD/ATI board ASUS M3A78 with 4GB RAM. No problems with 2.6.29. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] i386 kernel changes
by Jeff Mahoney 23 Apr '09

23 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - commit 3503087dd017ca5ad81a1abf01cef29f1440fdc8 Author: Jeff Mahoney <jeffm(a)suse.de> Date: Thu Apr 23 11:55:53 2009 -0400 - Moved i386 kernel-default to kernel-legacy. - Moved i386 kernel-pae config to kernel-default. - Disabled CONFIG_ISA in i386 kernel-default to improve boot speed. Pretty much every i386 system in recent history should be running kernel-pae instead of kernel-default. Every processor except an oddball Pentium M since the Pentium Pro and Athlon series has had the PAE feature. Since it includes things like NX, everyone should be using it even if they have less than 4 GB RAM. The other change is to speed up booting. According to Greg KH, probing for ISA PNP devices can cost us up to several seconds while starting up the kernel. Machines with ISA devices are now a distinct minority, so I've disabled it in the -default config. Using the -legacy kernel for this should be sufficient. I'm still investigating the separate -desktop and -server configs. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknwtH4ACgkQLPWxlyuTD7KYuQCfb6juI4SpSAUA8WnMgjxpzCfl kRQAnA64n8B3RaVJVtmt2yO4AcBDt6NF =z+2D -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] after kernel update (-> 2.6.27.21-31), mkinitrd fails @ "Device md3 not handled"
by PGNet Dev 23 Apr '09

23 Apr '09

after a kernel update today to, 2.6.27.21-31 from, .../repositories/Kernel:/SL111_BRANCH/openSUSE_11.1/ the usual, mkinitrd fails to execute -- _not_ creating the initrd*'s ... trying manually, mkinitrd fails, reporting, Kernel image: /boot/vmlinuz-2.6.27.21-31-default Initrd image: /boot/initrd-2.6.27.21-31-default Root device: /dev/VG0/ROOT (mounted on / as ext3) Resume device: /dev/VGS/SWAP --> Device md3 not handled Script /lib/mkinitrd/setup/72-block.sh failed! Kernel image: /boot/vmlinuz-2.6.27.21-31-xen Initrd image: /boot/initrd-2.6.27.21-31-xen Root device: /dev/VG0/ROOT (mounted on / as ext3) Resume device: /dev/VGS/SWAP --> Device md3 not handled Script /lib/mkinitrd/setup/72-block.sh failed! booting to RESCUE, mounting as req'd, & running 'mkinitrd' works fine; initrd*'s are generated in /boot/. rebooting normally subsequently works, uname -ri 2.6.27.21-31-xen x86_64 & now, mkinitrd Kernel image: /boot/vmlinuz-2.6.27.21-31-default Initrd image: /boot/initrd-2.6.27.21-31-default Root device: /dev/VG0/ROOT (mounted on / as ext3) Resume device: /dev/VGS/SWAP Kernel Modules: raid0 raid1 ... linear Features: dm block usb md lvm2 resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 30183 blocks Kernel image: /boot/vmlinuz-2.6.27.21-31-xen Initrd image: /boot/initrd-2.6.27.21-31-xen Root device: /dev/VG0/ROOT (mounted on / as ext3) Resume device: /dev/VGS/SWAP Kernel Modules: raid0 raid1 ... linear Features: dm block usb md lvm2 resume.userspace resume.kernel Bootsplash: No bootsplash for kernel flavor xen 30298 blocks so, i clearly have a workaround. but, what might be the issue in the first place? until today's update, i've had no problems ... something on my sys, or an issue in mkinitrd's scripts? thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] scripts to generate spec files from templates
by Michal Marek 16 Apr '09

16 Apr '09

Hi, to make it easier to build custom kernel versions and flavors, I'm working on the kernel packaging scripts to make work standalone. Also, Jeff has been doing quite some cleanup of the spec templates lately. The current state is here: http://download.opensuse.org/repositories/home:/michal-m:/kernel:/mkspec/op… (or at http://ftp.suse.com/pub/projects/kernel/kotd/master-mkspec/ but the KOTD gets published only once a day). This is how it currently works $ rpm2cpio kernel-source-*.src.rpm | cpio -i $ chmod +x mkspec arch-symbols compute-PATCHVERSION.sh # will be fixed # (re)generate all spec files: $ ./mkspec # add new flavor $ tar xf config.tar.bz2 $ cp config/i386/default config/i386/myconfig # ...tweak myconfig... $ tar cjf config.tar.bz2 config $ echo '+i386 i386/myconfig' >>config.conf $ ./mkspec $ osc build ... kernel-myconfig.spec ... and so on. Please keep in mind that this is rather new and not tested much, it might not work for you, it might change in the future based on feedback (hint, hint!), etc. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 1

[opensuse-kernel] Update to 2.6.30-rcX
by Jeff Mahoney 15 Apr '09

15 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone - Just a quick heads up to avoid duplication of effort. I have 2.6.30-rc1 merged in a local tree, but it's pretty rough and fails to build in many cases. I'm going to wait until 2.6.30-rc2 to merge into master. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknjqOsACgkQLPWxlyuTD7KtyQCfeLMxy2yXociH1Uj7V4kGCsMZ 3xMAn1IvywgoL4AtXnVHZEYJtzGSa5eG =5EiC -----END PGP SIGNATURE----- -- 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] Problem with SuSEfirewall2 and Kernel 2.6.30-rc1
by Tulio Magno Quites Machado Filho 10 Apr '09

10 Apr '09

Hi, I'm testing the kernel 2.6.30-rc1, but I'm getting some problems with OpenSuSEfirewall. As /var/log/messages shows, the firewall is running before loading all iptables modules: Apr 9 09:16:08 joutaro syslog-ng[1764]: syslog-ng starting up; version='2.0.9' Apr 9 09:16:11 joutaro SuSEfirewall2: batch committing... Apr 9 09:16:11 joutaro SuSEfirewall2: Error: iptables-batch failed, re-running using iptables Apr 9 09:16:12 joutaro SuSEfirewall2: Firewall rules set to CLOSE. Apr 9 09:16:13 joutaro kernel: klogd 1.4.1, log source = /proc/kmsg started. Apr 9 09:16:13 joutaro kernel: [ 18.141657] NET: Registered protocol family 10 Apr 9 09:16:13 joutaro kernel: [ 18.147461] lo: Disabled Privacy Extensions Apr 9 09:16:13 joutaro kernel: [ 18.561511] ip6_tables: (C) 2000-2006 Netfilter Core Team Apr 9 09:16:13 joutaro kernel: [ 18.826128] ip_tables: (C) 2000-2006 Netfilter Core Team Do you have any good idea to start it only after iptables' modules are completely loaded? Best regards, -- Tulio Magno -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 1

[opensuse-kernel] How to choose a kernel?
by Oddball 09 Apr '09

09 Apr '09

Hi, Maybe it sounds stupid for experts, but which kernel should i choose for an eee-pc? I thought kernel default, but that must be wrong, as this is huge! -- Have a nice day ;) Oddball aka M9. OS: Linux 2.6.29-60-default i686 Huidige gebruiker: oddball@EEEPC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.2.2 (KDE 4.2.2) "release 111" -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 4