[Bug 618514] New: Multiple warnings and error messages in installing vanilla 2.6.34 kernel
http://bugzilla.novell.com/show_bug.cgi?id=618514 http://bugzilla.novell.com/show_bug.cgi?id=618514#c0 Summary: Multiple warnings and error messages in installing vanilla 2.6.34 kernel Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain@novell.com ReportedBy: suse@tlinx.org QAContact: jsrain@novell.com Found By: --- Blocker: --- Created an attachment (id=372698) --> (http://bugzilla.novell.com/attachment.cgi?id=372698) linux kernel configuration file User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 I built the 2.6.34 kernel and upon intalling, I see several warnings and messages. Some of the warnings are because the build process assumes I am including old hardware in my build that doesn't apply to my system. Error messages are as follows: Ishtar:linux/ish-2634> sudo make install modules_install sh /home/linux/ish-2634/arch/x86/boot/install.sh 2.6.34T610-Vanilla arch/x86/boot/bzImage \ System.map "/boot" Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ... Kernel image: /boot/vmlinuz-2.6.34T610-Vanilla Initrd image: /boot/initrd-2.6.34T610-Vanilla Root device: /dev/disk/by-id/scsi-360024e8078d76a00ff000049049b00b0-part1 (/dev/sdb1) (mounted on / as xfs) modprobe: Module pata_acpi not found. WARNING: no dependencies for kernel module 'pata_acpi' found. modprobe: Module ata_piix not found. WARNING: no dependencies for kernel module 'ata_piix' found. modprobe: Module ata_generic not found. WARNING: no dependencies for kernel module 'ata_generic' found. modprobe: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. modprobe: Module ohci_hcd not found. WARNING: no dependencies for kernel module 'ohci_hcd' found. Kernel Modules: edd Features: block usb resume.userspace resume.kernel 20320 blocks 2010-06-29 16:18:45 ERROR: UDEVMAPPING: dmdev /dev/dm-0 doesn't have defined DM_NAME in udev 2010-06-29 16:18:51 ERROR: UDEVMAPPING: dmdev /dev/dm-0 doesn't have defined DM_NAME in udev ... Then lilo needs the DEVMAPPER option: shtar:linux/ish-2634> sudo lilo Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Added 2634-Van * Added 26334-Van Added 26332-Van Added 26331-Van Added Params-1 Added Linux_2631123 Added SUSE_LINUX Added Failsafe 12 warnings were issued. --------------- Now the lilo messages can be ignored if you are not booting from a logical volume, but if you are -- it's not likely to work. I want it to work -- as I want to move all my files systems to lvm. Please support lilo again in full -- I have way too many recurring problems with grub, and grub has serious bugs when you use xfs as a boot disk that lilo DOESN'T have. I'll include my config file -- that should allow you to generate the same kernel and see whatever problems I have. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=618514 http://bugzilla.novell.com/show_bug.cgi?id=618514#c1 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse@tlinx.org --- Comment #1 from Jiri Srain <jsrain@novell.com> 2010-06-30 13:48:37 UTC --- Sorry, but I'm confused. Do you have a problem with kernel? With mkinitrd? Can you be either more specific or split this bug into multiple ones? You set component to Bootloader, what's the porblem with bootloader itself or its configuration? Regatrding LILO support: openSUSE surely can support LILO, provided someone from the openSUSE community stands up and provides the support. openSUSE is a community project and Novell is just one member, which in spite of possibly being the biggest contributor cannot deliver everything that the community asks for. Regarding booting from LVM: It usually works with LILO, that's right. However, after LVM operations (which is why you use LVM) booting can very easily stop working unexpectedly. That's why you should boot from a partition outside LVM. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=618514 http://bugzilla.novell.com/show_bug.cgi?id=618514#c2 L. A. Walsh <suse@tlinx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse@tlinx.org | --- Comment #2 from L. A. Walsh <suse@tlinx.org> 2010-06-30 07:32:37 PDT --- Ok, 1st problem -- when I do a "make install" I see several warnings and errors: WARNING: no dependencies for kernel module 'pata_acpi' found. modprobe: Module ata_piix not found. WARNING: no dependencies for kernel module 'ata_piix' found. modprobe: Module ata_generic not found. WARNING: no dependencies for kernel module 'ata_generic' found. modprobe: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. modprobe: Module ohci_hcd not found. WARNING: no dependencies for kernel module 'ohci_hcd' found. Kernel Modules: edd ---- I shouldn't be seeing warnings for things that not problems. 2nd part -- was immediately folling this is an ERROR I've never seen before. I don't know what it means or what the impact is -- I shouldn't be getting error messages: 2010-06-29 16:18:45 ERROR: UDEVMAPPING: dmdev /dev/dm-0 doesn't have defined DM_NAME in udev 2010-06-29 16:18:51 ERROR: UDEVMAPPING: dmdev /dev/dm-0 doesn't have defined DM_NAME in udev when I install. I've had nothing but problems with device mapper, udev...lvm... they don't play together well. I even had a problem with udev that kept my system from booting for 2 days, so when I see udev problems cropping up when I am installing a kernel -- it's very worrysome to say the least. Then to top it off, I run the bootloader config 'lilo' and see more warnings because it wasn't build with LVM support. I tried building LVM -- then none of my snapshots would unmount or work because udev didn't like the new lvm. I tried updating udev -- and that's when my system stopped booting. So...having all these warning and error crop up -- that's the basic complaint, though the details are -- why am I getting all of these problems? As for your assertion about lvm possibly moving things around and that could confuse lilo -- I know enough to rerun lilo if things might move my boot partition around -- but my boot partition is small -- and just has the kernels on it. Root can be lvm based, and lilo doesn't care.
From what I've seen, grub has more problems booting from lvm than lilo has ever had. My proposal is that lilo be moved back to be the first choice -- it has fewer bugs and fewer problems.
It also boots on xfs, while grub doesn't. That alone should move it to first choice. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=618514 http://bugzilla.novell.com/show_bug.cgi?id=618514#c3 --- Comment #3 from L. A. Walsh <suse@tlinx.org> 2010-06-30 07:37:23 PDT --- Oh, FWIW -- I don't NEED mkinitrd. It shouldn't be running for me! Maybe all those error message are in mkinitrd -- in which case, they aren't a major concern for me. But the ones about lilo not being configured to work with LVM are more worrysome, as I'd like to be able to boot from lvm partitions as an option. I think I need 3 boot partitions to be safe -- one for normal use. One for testing, and a third with rescue tools. I've been stuck with an unbootable system too many times -- all since 11.2 came out (and I've been using suse since 7.0). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=618514 http://bugzilla.novell.com/show_bug.cgi?id=618514#c4 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from Jiri Srain <jsrain@novell.com> 2010-07-01 06:15:29 UTC --- make install => you are installing vanilla kernel, not SUSE, right? I don't think that we will do anything about that. Our tools (e.g. mkinitrd) expect that kernel is as modular as the SUSE one. (and I don't know why vanilla's 'make install' always calls mkinitrd) If you have kernel compiled differently, you are on your own. May also be related to different kernel version, I'm not a kernel geek. If you don't agree, create a separate bug on mkinitrd. udev: I'm not sure what causes these error messages, may be incompatibility with some options in your kernel, maybe kernel version, maybe patches in SUSE kernel, but I'm only guessing here. I suggest filing a separate bug against either device mapper or udev, IMHO it is unrelated to warnings regarding some of your modules which are built-in in your kernel by mkinitrd. Regarding LILO: There is only one hint I can give you: Find someone who will maintain LILO itself as well as its support in YaST and other libraries. openSUSE mailing lists (factory) are the right place for this, not bzilla. Just be aware that - LVM operation may move volumes -> system gets unbootable no matter which BL you use, you need /boot outside LVM to be safe - XFS is known for moving files under some circumstances even if they are not changed itself. Therefore even if you successfully install LILO on XFS, at some point of time it can stop working. Maybe you are just more lucky than others. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com