Bug#594092: initramfs-tools: Detection of resume device could terminate prematurely
reassign 594092 cryptsetup stop On Mon, Aug 23, 2010 at 07:12:59PM +0300, Dmitry Astapov wrote: Package: initramfs-tools Version: 0.98 Severity: normal Hi, My configuration includes (among other things) encrypted swap + uswsusp. Within last month one of the initrams-tools upgrades rendered my setup unusable: resume device (/dev/mapper/swap) was not available during boot. I went and peppered /usr/share/initramfs-tools/hooks/cryptroot with debug output and found out that: 1)I have (orphaned) /etc/suspend.conf lying around since Good Olde Times which lists /dev/sda8 as resume target 2)All other (proper) places list /dev/mapper/swap as resume target 3)cryptroot hook terminates prematurely trying to find canonical name for /dev/sda8. Specifically, line 97 of cryptroot: device=$(canonical_device $device) || return 0 causes hook to terminate prematurely, broking the resume process. I think that old config files lying around are not the only possible cause for breakage in this place, so other users might be affected as well - for example, if they made errors in their config files. I think that either user should be warned (Resume device ... is not available, fix manually) or more sensible approach to error handling should be employed. Thank you! reassigning to the good folks that do the encryption. happy day. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 8.8M Aug 23 18:59 /boot/initrd.img-2.6.30-1-686 -rw-r--r-- 1 root root 8.6M Aug 10 15:04 /boot/initrd.img-2.6.30-1-686.bak -- /proc/cmdline root=/dev/sda1 ro ramdisk_size=8192 resume=/dev/mapper/swap -- resume RESUME=/dev/mapper/swap -- /proc/filesystems ext2 ext3 fuseblk -- lsmod Module Size Used by iwl394561064 0 omnibook 47824 0 sco 8832 2 rfcomm 30368 14 bnep 10860 4 l2cap 18120 19 rfcomm,bnep vboxnetadp 6428 0 vboxnetflt 12324 0 vboxdrv 155584 2 vboxnetadp,vboxnetflt acpi_cpufreq7640 0 cpufreq_powersave 1292 0 cpufreq_userspace 2768 0 cpufreq_stats 3520 0 cpufreq_conservative 6256 2 autofs420544 1 irda 95720 0 crc_ccitt 1816 1 irda binfmt_misc 7120 1 vmnet 33260 13 parport_pc 22420 0 parport31144 1 parport_pc vmblock11256 1 vmci 42584 0 vmmon 59876 0 kvm_intel 39744 0 kvm 138608 1 kvm_intel fuse 47752 1 nfsd 204900 0 exportfs3792 1 nfsd nfs 221580 0 lockd 57972 2 nfsd,nfs fscache34440 1 nfs nfs_acl 2640 2 nfsd,nfs auth_rpcgss31416 2 nfsd,nfs sunrpc163772 6 nfsd,nfs,lockd,nfs_acl,auth_rpcgss ext3 107172 3 jbd41036 1 ext3 btusb 10276 2 bluetooth 47060 9 sco,rfcomm,bnep,l2cap,btusb visor 13812 0 usbserial 27456 1 visor coretemp5176 0 ip_tables 10188 0 x_tables 14108 1 ip_tables sha256_generic 11216 0 cbc 3012 1 aes_i5868092 4 aes_generic27436 1 aes_i586 dm_crypt 11092 3 dm_mod 49992 7 dm_crypt snd_hda_codec_si3054 4024 1 snd_hda_codec_realtek 178472 1 snd_hda_intel 22192 0 snd_hda_codec 63580 3 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 6120 1 snd_hda_codec arc41560 2 snd_pcm_oss32232 0 snd_mixer_oss 12368 1 snd_pcm_oss ecb 2368 4 snd_pcm62420 4 snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi5688 0 snd_rawmidi18596 1 snd_seq_midi iwlcore92264 1 iwl3945 snd_seq_midi_event 6212 1 snd_seq_midi pcmcia 24280 0 snd_seq42436 2 snd_seq_midi,snd_seq_midi_event snd_timer 17436 2 snd_pcm,snd_seq snd_seq_device 6136 3 snd_seq_midi,snd_rawmidi,snd_seq joydev 8576 0 snd49060 12 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device mac80211 142848 2 iwl3945,iwlcore yenta_socket 21168 1 tifm_7xx1 4864 0 intel_agp 22900 0 rsrc_nonstatic 9664 1 yenta_socket soundcore
Re: [initramfs] /etc/elilo.conf not found
hello please learn to post to mailinglists and not post random personal message, cool thanks. On Sun, 22 Aug 2010, Jose Antonio Quevedo Muñoz wrote: Hi Maks, I'm having a trouble probably with initramfs. I have already read the bug related to this issue [1] where you say that this is solved in the last version of initramfs but I'm using sid and it's not working properly. why do you have elilo installed if you don't use it!? as root nuke it: dpkg -P elilo if you need elilo you should configure it properly. good weekend. -- maks These are the messages that I'm receiving: - $ aptitude safe-upgrade Resolving dependencies... The following partially installed packages will be configured: initramfs-tools linux-image-2.6.26-2-686 linux-image-2.6.32-5-486 linux-image-2.6.32-5-686 No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 9 not upgraded. Need to get 0B of archives. After unpacking 0B will be used. Setting up initramfs-tools (0.98) ... update-initramfs: deferring update (trigger activated) Setting up linux-image-2.6.26-2-686 (2.6.26-24lenny1) ... Running depmod. Running mkinitramfs-kpkg. Deprecation WARNING: use update-initramfs(8) Not updating initrd symbolic links since we are being updated/reinstalled (2.6.26-24 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.26-24 was configured last, according to dpkg) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.26-2-686 /boot/vmlinuz-2.6.26-2-686 run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.26-2-686 /boot/vmlinuz-2.6.26-2-686 run-parts: executing /etc/kernel/postinst.d/zz-elilo 2.6.26-2-686 /boot/vmlinuz-2.6.26-2-686 elilo: /etc/elilo.conf: No such file or directory run-parts: /etc/kernel/postinst.d/zz-elilo exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.26-2-686.postinst line 1166. dpkg: error processing linux-image-2.6.26-2-686 (--configure): subprocess installed post-installation script returned error exit status 2 Setting up linux-image-2.6.32-5-486 (2.6.32-18) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-486 initrd.img(/boot/initrd.img-2.6.32-5-486 ) points to /boot/initrd.img-2.6.32-5-486 (/boot/initrd.img-2.6.32-5-486) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-486.postinst line 347. vmlinuz(/boot/vmlinuz-2.6.32-5-486 ) points to /boot/vmlinuz-2.6.32-5-486 (/boot/vmlinuz-2.6.32-5-486) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-486.postinst line 347. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-5-486 /boot/vmlinuz-2.6.32-5-486 run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.32-5-486 /boot/vmlinuz-2.6.32-5-486 run-parts: executing /etc/kernel/postinst.d/zz-elilo 2.6.32-5-486 /boot/vmlinuz-2.6.32-5-486 elilo: /etc/elilo.conf: No such file or directory run-parts: /etc/kernel/postinst.d/zz-elilo exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.32-5-486.postinst line 799. dpkg: error processing linux-image-2.6.32-5-486 (--configure): subprocess installed post-installation script returned error exit status 9 Setting up linux-image-2.6.32-5-686 (2.6.32-20) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-5-686 /boot/vmlinuz-2.6.32-5-686 run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.32-5-686 /boot/vmlinuz-2.6.32-5-686 run-parts: executing /etc/kernel/postinst.d/zz-elilo 2.6.32-5-686 /boot/vmlinuz-2.6.32-5-686 elilo: /etc/elilo.conf: No such file or directory run-parts: /etc/kernel/postinst.d/zz-elilo exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.32-5-686.postinst line 799. dpkg: error processing linux-image-2.6.32-5-686 (--configure): subprocess installed post-installation script returned error exit status 2 Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 elilo: /etc/elilo.conf: No such file or directory run-parts: /etc/initramfs/post-update.d//elilo exited with return code 1 dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.26-2-686 linux-image-2.6.32-5-486 linux-image-2.6.32-5-686 initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up initramfs-tools (0.98) ... update-initramfs: deferring
Bug#593702: RM: usplash -- ROM; buggy as hell
Package: ftp.debian.org Severity: normal usplash squarbles your screen and is in the days of KMS graphic drivers no longer useful. Newer initramfs should use plymouth for graphical display. usplash was a nice hack, but includes duplicate bogl. please remove from sid. thanks -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100820132300.16688.2714.report...@dual.itp.tuwien.ac.at
Bug#593276: initramfstools =0.94 not compatible with lenny?
tags 593276 moreinfo stop On Mon, Aug 16, 2010 at 11:06:53PM +0200, Holger Fischer wrote: package: initramfs-tools version: 0.97 all of the text below is against some out of tree not supported Debian version. please specify what is the trouble with 0.97. If it involves ipconfig you want to look at #584583, which will be fixed soonest. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100817092404.gd1...@baikonur.stro.at
2.6.35 exp upload
I plan to upload 2.6.35 with it's too latest stable release tomorrow after 12:00 UT to experimental. if you have any objection please voice. signature.asc Description: Digital signature
Re: 2.6.35 exp upload
On Sat, Aug 14, 2010 at 01:30:14PM +0200, maximilian attems wrote: I plan to upload 2.6.35 with it's too latest stable release tomorrow after 12:00 UT to experimental. if you have any objection please voice. will delay until this bug is resolved: https://bugzilla.kernel.org/show_bug.cgi?id=16588 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100814170611.gc1...@baikonur.stro.at
Bug#592971: linux-image-2.6.32-5-amd64: wlan0 disconnect with reason=3
On Sat, Aug 14, 2010 at 05:54:22PM +0200, Daniel wrote: Wireless disconnect immediately after associating to AP with deauthenticating by local choice (reason=3) I also tested with 2.6.34-1 kernel from experimental, as well as with few APs (WEP, WAP or open), no more luck. experimental has since 2.6.35, any chance to try it? Module is iwl3945 for 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100814170319.gb1...@baikonur.stro.at
Bug#584583: [PATCH] Additional fix for ipconfig
[ adding relevant cc's ] On Tue, 10 Aug 2010, Julien-externe BLACHE wrote: Hi, Attached is a second patch for ipconfig, which further improves (actually, restores) ipconfig's behaviour on busy LANs with UDP noise. Commit 4efbcf90f60e27febe883ef052454d8cfded5c15 really is the root of all evil, it badly broke ipconfig by doing a lot of changes all over the place that were not warranted and badly tested. Indeed as mailinglist history show I had been sceptic to that monster patch, but several users had pushed for it, see: http://bugs.debian.org/511959 After this commit, if a random UDP packet comes in before the expected DHCP reply packet_recv() will exit with an error and the interface will be sent into DEVST_ERROR instead of just ignoring this packet. On busy LANs, ipconfig can go through this loop several times. JB. as mika is currently on vacation after Debconf. I will look into the issue and see if said patch resolves his testcase which is nicely layed out in http://bugs.debian.org/552554 thank you for the patch. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100812180020.gb28...@stro.at
Bug#591073: linux-image-2.6.32-5-amd64: Suspend-to-RAM regression
On Mon, 09 Aug 2010, Josef Spillner wrote: The issue remains with linux-image-2.6.35-trunk-amd64 in today's version 2.6.35-1~experimental.1. This leaves me with the debug things. Documentation/power/basic-pm-debugging.txt is the guide for nailing what is going wrong. also in this case please report upstream in bugzilla.kernel.org and let us know upstream bug nr for tracking thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100809220450.ga27...@stro.at
Bug#591473: linux-image-2.6.32-5-amd64: kernel panics on reboot or when nic has no link
tags 591473 moreinfo stop On Tue, Aug 03, 2010 at 01:37:22PM +0100, FRLinux wrote: Package: linux-2.6 Version: 2.6.32-15 Severity: grave Justification: causes non-serious data loss no only if *lots* of boxes would be affected, also prove posted. We use this server as a bridging firewall, it has 3 NICs configured, first one for incoming traffic, second one for outgoing and third one for management. Whenever we use kernel 2.6.32-5, it panics when there is no link between the router and the incoming interface on the server. Panics also on reboot. Tried to disable acpid but doesn't seem to be related. When switching to previous kernel (2.6.32-3), works perfectly. please post panic, we have no crystall balls allowing it to verify this case. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100803124541.gu19...@baikonur.stro.at
Bug#584583: Bug#552554: ipconfig does not time out (klibc-utils)
On Mon, 02 Aug 2010, Michael Prokop wrote: maks, you can easily reproduce this issue with kvm, a live system (latest Grml release works fine) and two virtual NICs. If you need any further information I'm happy to provide it, debugging klibc-utils 1.5.12-2-1.5.18-1 is PITA with all its header and build changes. please don't be shy to describe or tell the setup whith which you reproduce, thanks! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100803211459.gb17...@stro.at
Bug#591320: /etc/modprobe.d/initramfs.conf is lost
On Mon, Aug 02, 2010 at 11:14:43PM +0200, Harald Dunkel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is the intended behaviour. Is this documented somewhere? This restriction would make the blacklist feature pretty useless, doesn't it? As soon as udev is started in single user mode (using /etc/modprobe.d found on root filesystem) all the blacklisted modules are no longer suppressed. In my case I get a bad acpi module crashing the system before single user mode is completely setup. What would you suggest? Of course I understand that this would be difficult to implement, since the root filesystem becomes writable very late in the boot procedure. I'd suggest to have m-i-t parse the blacklist bootparam. the thing is this one is initramfs-tools specific dracut prefix rd to it marking it as a non linux-2.6 param. We didn't have that discussion yet. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100802212826.gs19...@baikonur.stro.at
Bug#591073: linux-image-2.6.32-5-amd64: Suspend-to-RAM regression
On Mon, Aug 02, 2010 at 09:31:26PM +0200, Josef Spillner wrote: Am Sonntag, 1. August 2010, 22:56:40 schrieb maximilian attems: unstable versions just install fine in testing, no point in waiting for transition. Well, so much for that theory: One needs at least a newer extlinux installed, otherwise the postinst fails. Yet one more case of missing tight dependencies. Anyway, after taking this hurdle, all I can say is that the issue remains. well then you have either to go for the suspend to ram debug things or test latest 2.6.35 in experimental. second choice is easier and best advice. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100802220509.gt19...@baikonur.stro.at
Bug#591025: Remove the irrelevent BOOT in initramfs.conf - patch available
On Fri, 30 Jul 2010, wol...@yahoo.com wrote: Package: initramfs-tools Version: 0.97.2 The BOOT switch should not be set in the initramfs.conf. why do you come to that conclusion? it is used by live-initramfs afair. It should be determined in boot time by the boot commandline, by either explicitly a boot=foo or implicitly such as root=/root/nfs. I suggest that the BOOT directive in initramfs.conf be deprecated. you don't give any rationale, so will close unless this gets motivated properly and it be clear why we want that and what gain that would be. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100801070611.ga30...@stro.at
Bug#591073: linux-image-2.6.32-5-amd64: Suspend-to-RAM regression
On Sun, Aug 01, 2010 at 08:22:42AM +0200, Josef Spillner wrote: outdated test against 2.6.32-18 from unstable, Will do so in two days when that version enters testing. Is it possible through bugs.d.o to get a notification when a package which fixes a bug becomes available for a certain distribution or suite? This would be an awesome feature. unstable versions just install fine in testing, no point in waiting for transition. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100801205640.gr19...@baikonur.stro.at
Bug#591073: linux-image-2.6.32-5-amd64: Suspend-to-RAM regression
tags 591073 moreinfo stop On Sat, Jul 31, 2010 at 06:42:03PM +0200, Josef Spillner wrote: Package: linux-2.6 Version: 2.6.32-15 Severity: normal Suspending the computer to RAM (e.g., from the KDE menu) works fine in the previous kernel linux-image-2.6.32-3-amd64. But with the current -5 kernel it has ceased to work. The machine falls asleep but the system doesn't come up again afterwards when the hardware runs again but nothing is shown on the screen. This is on a fully up-to-date squeeze system. The bug was already present with the same kernel on last week's squeeze. It's clearly a regression, as it's the first Debian kernel which doesn't get this right on this machine. outdated test against 2.6.32-18 from unstable, thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100731211308.gp19...@baikonur.stro.at
Bug#590744: Fails to boot if /sbin/init is a symlink
On Sat, Jul 31, 2010 at 08:25:09PM +0200, Michael Prokop wrote: dracut doesn't seem to support symlinks at all AFAICS. well this seems sane to me. maks: I've implemented a fastfoward path, please review branch mika/validate_init at http://git.debian.org/?p=kernel/initramfs-tools.git will do in the next 48 hours, but haven't been told that the ! symlink cause is the usual fastpath. not sure this symlink complication is really worth it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100731211529.gq19...@baikonur.stro.at
Bug#590744: Fails to boot if /sbin/init is a symlink
On Fri, Jul 30, 2010 at 11:49:32AM +0200, Michael Biebl wrote:
On 30.07.2010 11:31, Michael Biebl wrote:
On 30.07.2010 06:21, Michael Prokop wrote:
Can you please give the following snapshot version a try:
http://people.debian.org/~mika/initramfs-tools/initramfs-tools_0.97.3~1.gbp8d572e_all.deb
I've tested the following:
- /sbin/init being a relative symlink: works
- /sbin/init being an absolute symlink: works
- /sbin/init missing: correctly dropped to rescue shell, even if upstart
installed (/etc/init/)
- passing init=/bin/systemd on the boot command line: works
- passing bogus init=/sbin/foo on the boot command line: warning message
that
requested init was not found, is displayed, but continues booting with
/sbin/init.
So yes, it works correctly now for all cases I tested and expect.
Looking at the code, the only issue I see, is that validate_init is *always*
executed at least twice, even if we find a valid init at the first try.
This means, for most cases we unnecessarily execute validate_init at
# No init on rootmount
if ! validate_init ${init} ; then
Not that much of an issue, just an idea for a small optimization.
please this is executed on every boot, could we have a fastforward
path for the common cases.
dracut probably solved this long ago, please have a look there
what fedora guys are doing.
thanks.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100730110430.go19...@baikonur.stro.at
Bug#588770: initramfs-tools: modules=dep in initramfs.conf breaks suspend-to-disk
On Mon, 12 Jul 2010, Matthias Berndt wrote: Package: initramfs-tools Version: 0.97.2 Severity: normal Tags: sid Hi, i just noticed using modules=dep instead of modules=most breaks suspend-to-disk for me. My swap partition lies on a PATA disk while my root file system lies on a SATA disk, so the needed PATA drivers aren't loaded and thus the device file for the swap partition doesn't exist. Perhaps there should be a resume hook script that checks for this condition? this isn't as trivial as said. the sys walking code is nicely abstracted in a function the ugly^Wdiverse root parsing code not. so it should do that and then one can add aboves. this is clearly wishlist as MODULES=dep is not default. not a priority for squeeze, thanks for the report. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100728180705.gc16...@stro.at
Bug#590661: linux-image-2.6.32-5-openvz-amd64: openswan ipsec packets do not reach openvz instances
On Wed, Jul 28, 2010 at 10:29:40AM +0200, Daniel Tombeil wrote: Package: linux-2.6 Version: 2.6.32-18 Severity: important Tags: squeeze -- Package-specific info: ** Version: Linux version 2.6.32-5-openvz-amd64 (Debian 2.6.32-18) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Sat Jul 24 02:32:56 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-openvz-amd64 root=/dev/mapper/osfw--v3--01--vda1-osfw--v3--01--root ro quiet see no posted evidence here, but anyway please post tcpdumps and setup in upstream bugzilla.openvz.org and let us know bug nr so that it can be tracked. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100728085026.gl19...@baikonur.stro.at
Bug#590661: linux-image-2.6.32-5-openvz-amd64: openswan ipsec packets do not reach openvz instances
On Wed, Jul 28, 2010 at 11:09:41AM +0200, Daniel Tombeil wrote: see no posted evidence here, but anyway please post tcpdumps and setup in upstream bugzilla.openvz.org and let us know bug nr so that it can be tracked. I attached some ASCII-tcpdump output at the end of the report. Below the More information:-Line. But I'll try if it is reproducable in an easier setup. base-install, one bridge-device, and then trying to access the veth-attached VE's on the bridge-devices network using an ipsec tunnel terminated using openswan in netkey-mode. I'll post the setup-guide for reproduction and the binary tcpdump ASAP. ok sorry overlooked, as wasn't in body, please make upstream devs aware by filing there. development and fixes happens there. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100728093050.gm19...@baikonur.stro.at
Bug#589804: Implement missing syscalls on Alpha
On Fri, Jul 23, 2010 at 06:36:20PM +1200, Michael Cree wrote: On 22/07/10 07:14, maximilian attems wrote: On Wed, 21 Jul 2010, Michael Cree wrote: I have tested both these patches applied to the Debian 2.6.32-17 kernel source (though I did have to disable the buildcheck.py script as the ABI didn't match) and it is running successfully on an Alpha PWS600au. please send in the log of the broken ABI so that it can be ignored on purpose. Attached. I see thanks allmost everything changes as expected, this leaves two opportunities: A) ignore the abi change, as it is a clear improvement for alpha and external module should be less of a trouble on this arch. (considering that we haven't released yet).. B) wait for an ABI bump to slide in those patches. I prefer A, but will wait a while to see if anyone voices against. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723075504.gh19...@baikonur.stro.at
Bug#589804: Implement missing syscalls on Alpha
On Wed, 21 Jul 2010, Michael Cree wrote: It would be nice to have the missing syscalls on Alpha wired up to bring it up to date with the other architectures. It was unfortunate that the patch sent upstream to achieve this was missed during the 2.6.32 development window and didn't get merged by Linus unto 2.6.33. I am happy to add those, they are on my todo list, thanks for reporting. I attach the patch patch-alpha-wire-up-syscalls.txt that wires up the missing syscalls on the Alpha architecture and brings it up to date with the other architectures. This patch is a modification of the upstream commits 6e17e8b9fb74b9fb9f6ea331f7f4a049c5b4c4b8 and 21797c599c710d3851d241c4b50690f2482bf618 in that it replaces the recvmmsg syscall with a placeholder as it is not available in 2.6.32. As mentioned in bug report #588409 (which is now closed) support for performance events on Alpha was merged upstream for 2.6.33. I include here the patch patch-alpha-implement-sw-perf-events.txt which is a combination of the upstream commits a582e6f01b90211933e70edcec9bc0bbb1157402 and fcd14b3203b538dca04a2b065c774c0b57863eec and wires up the performance events syscall and provides the Alpha specific code to the perf tools. I have tested both these patches applied to the Debian 2.6.32-17 kernel source (though I did have to disable the buildcheck.py script as the ABI didn't match) and it is running successfully on an Alpha PWS600au. please send in the log of the broken ABI so that it can be ignored on purpose. still need to have a look at it. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100721191426.gf11...@stro.at
Bug#588936: initramfs-tools: still does not work with kernel-package kernels
reassign 588936 kernel-package stop On Tue, Jul 13, 2010 at 05:23:39PM +0200, Michal Suchanek wrote: Package: initramfs-tools Version: 0.97.2 Severity: normal Hello, there was a bug about initramfs not created for kernel-package kernels. I am trying to build a live CD with a kernel-package kernel and the initramfs is still not created: first of all kernel-package is legacy, use make deb-pkg. P: Begin install linux-image... cp: cannot stat `chroot/boot/initrd.img-*': No such file or directory how on earth is this an initramfs-tools trouble? P: Begin unmounting filesystems... r...@virtual:6(2) 07131715 1161]/srv/dl-test # ls chroot/boot/ config-2.6.34-1-686 System.map-2.6.34-1-686 vmlinuz-2.6.34-1-686 r...@virtual:6(2) 07131716 1162]/srv/dl-test # chroot chroot update-initramfs -u -k all r...@virtual:6(2) 07131716 1163]/srv/dl-test # chroot chroot update-initramfs -c -k all both this calls make no sense. r...@virtual:6(2) 07131716 1164]/srv/dl-test # chroot chroot update-initramfs -c -k 2.6.34-1-686 update-initramfs: Generating /boot/initrd.img-2.6.34-1-686 Moreover there is no way to diagnose this failure as the initramfs-tools kernel postinst.d script does not say if it buils an initramfs or not. if it is not invoked not indeed. proper diagnosis is welcome. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100713162033.gi9...@baikonur.stro.at
Re: Bug#588936: initramfs-tools: still does not work with kernel-package kernels
[ changed cc to d-kernel and not unrelated bug report ] On Tue, Jul 13, 2010 at 06:51:12PM +0200, Michael Prokop wrote: * maximilian attems m...@stro.at [Tue Jul 13, 2010 at 06:20:33PM +0200]: On Tue, Jul 13, 2010 at 05:23:39PM +0200, Michal Suchanek wrote: there was a bug about initramfs not created for kernel-package kernels. I am trying to build a live CD with a kernel-package kernel and the initramfs is still not created: first of all kernel-package is legacy, use make deb-pkg. As long as make deb-pkg can't build neither header nor source packages I personally just can't switch to deb-pkg. So even though I'm not the original bugreporter I just want to mention that I don't want to see kernel-package called legacy. I prefer to call things by their name. The simple conclusion is that nobody really needs those things. As they are easy to add in linux-2.6 and nobody proposed it. source deb package!? simple git clone gets more data. headers to built against? again same git clone settled it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100713174713.gj9...@baikonur.stro.at
Bug#565225: over my head
On Mon, Jul 12, 2010 at 09:53:28AM +0800, jida...@jidanni.org wrote: B thanks for the feedback, closing as not a Debian bug. B please report back to antiX dev. I hope somebody reports that to whomever. bug is reopened, this reporter confused and his bug is not related to the topic of that one, aboves discussion is thus unrelated. have a nice day. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100712080417.gh9...@baikonur.stro.at
Bug#565225: No /etc/initramfs-tools/conf.d/resume file after Sid upgrade
On Sat, 10 Jul 2010, michael conner wrote: Package: initramfs-tools Version: 0.97.2 Severity: normal I upgraded to Sid from Squeeze today and went to run update-initramfs -u after changing my /etc/uswsusp.conf file, and was unable to resume from hibernation. There was no /etc/initramfs-tools/conf.d/resume file there, which was not the expected behavior. I created one and added RESUME=/dev/disk/by- uuid/ and my swap partition's uuid, then ran update-initramfs -u. It then worked as expected and my laptop resumed from hibernate. this files gets created either by Debian Installer or on install by initramfs-tools. So it must have been removed by yourself, I don't see a bug here. There is a report asking to regenerate this file. #565225 Playing with config files in Debian is considerated evil, so not yet sure yet how to resolve that bug. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100711151941.ga13...@stro.at
Bug#588466: klibc-utils: kernel panic when resume failed and normal boot continues
tags 588466 moreinfo -patch
stop
On Thu, 08 Jul 2010, Bastian Kleineidam wrote:
all my newly built kernels failed to boot with the following message:
[...]
kinit: No resume image, doing normal boot...
E: /scripts/local-premount/resume failed with return 255
Kernel panic - not syncing: Attempted to kill init!
is the /tmp on your box mounted noexec?
please sent output of:
cat /proc/mounts
Attached patch fixes the issue by falling back gracefully to normal
booting of the system.
My swap partition is crypted btw:
$ cat /etc/crypttab | grep swap
cswap /dev/mapper/grog-swap_1 /dev/urandomswap
$ cat /etc/fstab | grep swap
/dev/mapper/cswap noneswapsw 0 0
As a sidenote: I do not understand why my system is trying to resume
from a crypted swap ?artition anyway.
It tries this everytime, even though the system has always been
rebooted cleanly without suspending anything to the swap partition.
please send output of
cat /etc/initramfs-tools/conf.d/resume
--- /usr/share/initramfs-tools/scripts/local-premount/resume~ 2010-07-07
23:13:20.0 +0200
+++ /usr/share/initramfs-tools/scripts/local-premount/resume 2010-07-08
20:29:31.0 +0200
@@ -58,6 +58,13 @@
# hardcode path, uswsusp ships an resume binary too
if [ -n ${resume_offset} ]; then
/bin/resume ${resume} ${resume_offset}
+ res=$?
else
/bin/resume ${resume}
+ res=$?
fi
+if [ $res -eq -1 ]; then
+ # do not fail when falling back to normal boot
+ exit 0
+fi
+exit $res
checked indeed resume from klibc does return -1 when
suspend doesn't happen.
I haven't seen the resulting bootfailure yet, currently I can only
explain it by noexec tmp and thus not precache run.
the errexit for hooks on run_script() mika would thus also be hit
on boot and not only on mkinitramfs. not sure that is what we want.
--
maks
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100711161315.gc13...@stro.at
Re: Proposed changes to initramfs-tools hook scripts
On Fri, 02 Jul 2010, maximilian attems wrote: On Wed, 30 Jun 2010, Stephen Powell wrote: Max, As promised, here are my proposed changes to the initramfs-tools hook scripts. /etc/kernel/postinst.d/initramfs-tools: http://www.wowway.com/~zlinuxman/kernel/postinst.d/initramfs-tools /etc/kernel/postrm.d/initramfs-tools: http://www.wowway.com/~zlinuxman/kernel/postrm.d/initramfs-tools I release the changes under the same license as currently used. I did not include the scripts or patches in-line in my e-mail because my e-mail client has the nasty habit of expanding tabs, inserting extra line breaks, etc. So I up-loaded the files to my web site and included links to them in this e-mail. Changes: (1) Does not create an initial RAM file system image for a custom kernel created by make-kpkg if one was not requested by the --initrd flag of make-kpkg. (2) Redirects STDOUT to STDERR when invoking update-initramfs. (Avoids output being swallowed by debconf's redirection of STDOUT.) (3) Postinst.d version always exits with status code zero, even if an error occurs attempting to delete the initramfs. thank you very much. applied your 3 changes to branch maks/hooks on http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary please review before I'd merge into master for next upload. I'm not sure if the indirection to STDERR is needed for make deb-pkg, but it shouldn't hurt there? so mika reviewed http://git.debian.org/?p=kernel/initramfs-tools.git;a=shortlog;h=refs/heads/maks/hooks he critisize the exit 0 without any stdout/stderr message. so rethinking why do you want that anyway? I do not see the point of it, update-initramfs is already told to not care if that initramfs exists with the takeover flag so will not errexit. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100708132402.gc2...@stro.at
Bug#584583: initramfs-tools: configure_networking function: repeatedly makes DHCP requests
On Fri, 04 Jun 2010, Vagrant Cascadian wrote: Package: initramfs-tools Version: 0.95.1 Severity: normal i've been testing the newest initramfs-tools network booting support, though it seems to make 10 DHCP requests in rapid sucession. fortunately, the last DHCP request does work. switching back to hard-coded DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf doesn't trigger this issue, oddly enough. could you compile klibc ipconfig with debug on, although it is possible to pass it on the command line it seems dash breaks the klibc build with global debug on, thus this is easiest: # you may skip first step if you have already current klibc sources cd ~/src git clone git://git.kernel.org/pub/scm/libs/klibc/klibc.git cd klibc ~/src/klibc$ echo EXTRA_KLIBCCFLAGS := -DDEBUG=1 usr/kinit/ipconfig/Kbuild ~/src/klibc$ make KLIBCKERNELSRC=`pwd`/../linux-2.6 third step assumes built ~/src/linux-2.6 aka make defconfig, make there. now you need to put that debug ipconfig in the initramfs of where you are seeing that loop. it be interested in the log that ipconfig outputs. thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100706121432.gb4...@stro.at
Bug#588241: update-initramfs: failed for /boot/initrd.img-2.6.30-1-686
On Tue, Jul 06, 2010 at 02:39:33PM +0200, Dirk Schleicher wrote: Package: initramfs-tools Version: 0.97 Severity: important I have problem to update initramfs-tools ein (0.97) ... Richte initramfs-tools ein (0.97) ... update-initramfs: deferring update (trigger activated) Verarbeite Trigger für initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 update-initramfs: failed for /boot/initrd.img-2.6.30-1-686 unrelated but this kernel is not supported any longer please fetch and install linux image 2.6.32-5 from testing/sid. thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100706123859.gs9...@baikonur.stro.at
Bug#588241: update-initramfs: failed for /boot/initrd.img-2.6.30-1-686
On Tue, Jul 06, 2010 at 02:39:33PM +0200, Dirk Schleicher wrote: Package: initramfs-tools Version: 0.97 Severity: important outdated version. I have problem to update initramfs-tools ein (0.97) ... Richte initramfs-tools ein (0.97) ... update-initramfs: deferring update (trigger activated) Verarbeite Trigger für initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 update-initramfs: failed for /boot/initrd.img-2.6.30-1-686 dpkg: Fehler beim Bearbeiten von initramfs-tools (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) Ein Paket konnte nicht installiert werden. Versuche zu lösen: Richte initramfs-tools ein (0.97) ... update-initramfs: deferring update (trigger activated) Verarbeite Trigger für initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 cpio: Fehler beim Schreiben: Datenübergabe unterbrochen (broken pipe) update-initramfs: failed for /boot/initrd.img-2.6.30-1-686 dpkg: Fehler beim Bearbeiten von initramfs-tools (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: initramfs-tools please report back on latest version 0.97.2, just uploaded 2 hours ago should hit mirrors soonest. thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100706123738.gr9...@baikonur.stro.at
Bug#588241: update-initramfs: failed for /boot/initrd.img-2.6.30-1-686
On Tue, Jul 06, 2010 at 03:01:52PM +0200, Dirk Schleicher wrote: Am Tue, 6 Jul 2010 14:38:59 +0200 schrieb maximilian attems: unrelated but this kernel is not supported any longer please fetch and install linux image 2.6.32-5 from testing/sid. thanks. But I run unstable! Is there a newer on in testing? then please install linux-image-2.6-686 metapackage to keep up with latest linux-2.6 :) did you test newer initramfs-tools? may not have hit .de mirrors yet? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100706125510.gt9...@baikonur.stro.at
Re: Fwd: [Users] vzcpt kernel module crash while trying to dump with vzctl chkpnt
On Tue, 06 Jul 2010, Kir Kolyshkin wrote: An OpenVZ user Benjamin Henrion (cced) reported a bug (see below, also [1], [2]) which is already fixed in our latest kernel 2.6.32-budarin.1 (by commit 7e99ed1bc34b60ed42eb2008edbb4f98684edb0a). Can you please bring the Debian OpenVZ kernel up-to-date, which will fix this bug as well as a few same-critical others? 2.6.32-16 has been uploaded ~6 hours ago, we were waiting for 2.6.32.16 ;) it contains openvz image with patch including up to 5fd638726a69 with a fix to not break ABI on commit 7e99ed1bc34b60ed42eb2008edbb4f98684edb0a. thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100706163156.ge4...@stro.at
Re: Fwd: [Users] vzcpt kernel module crash while trying to dump with vzctl chkpnt
On Tue, Jul 06, 2010 at 08:37:54PM +0400, Kir Kolyshkin wrote: On 07/06/2010 08:31 PM, maximilian attems wrote: On Tue, 06 Jul 2010, Kir Kolyshkin wrote: An OpenVZ user Benjamin Henrion (cced) reported a bug (see below, also [1], [2]) which is already fixed in our latest kernel 2.6.32-budarin.1 (by commit 7e99ed1bc34b60ed42eb2008edbb4f98684edb0a). Can you please bring the Debian OpenVZ kernel up-to-date, which will fix this bug as well as a few same-critical others? 2.6.32-16 has been uploaded ~6 hours ago, we were waiting for 2.6.32.16 ;) it contains openvz image with patch including up to 5fd638726a69 with a fix to not break ABI on commit 7e99ed1bc34b60ed42eb2008edbb4f98684edb0a. Can you please elaborate on this one? sure http://svn.debian.org/viewsvn/kernel/dists/sid/linux-2.6/debian/patches/features/all/openvz/partially-revert-CPT-Replace-legacy-net-statistics.patch?view=markup -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100706163450.gx9...@baikonur.stro.at
Bug#588140: linux-image-2.6.32-5-amd64: can't install: dpkg: error processing linux-image-2.6-amd64
On Mon, Jul 05, 2010 at 01:52:26PM +0200, Bruno Boettcher wrote: Package: linux-2.6 Version: 2.6.32-15 Severity: normal wrong package, but who reads text one copies and pastes? ;) Hello i have quite a fear at the moment about rebooting my comp, since i don't know if it will get up again... yep. an upgrade run gives the following: Setting up initramfs-tools (0.97) ... update-initramfs: deferring update (trigger activated) Setting up linux-image-2.6.26-2-amd64 (2.6.26-24) ... Running depmod. Running mkinitramfs-kpkg. Deprecation WARNING: use update-initramfs(8) mkinitramfs-kpkg failed to create initrd image. so here we have the failure. Failed to create initrd image. dpkg: error processing linux-image-2.6.26-2-amd64 (--configure): subprocess installed post-installation script returned error exit status 9 Setting up linux-image-2.6.32-5-amd64 (2.6.32-15) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 update-initramfs: failed for /boot/initrd.img-2.6.32-5-amd64 update-initramfs failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.32-5-amd64 (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-2.6-amd64: linux-image-2.6-amd64 depends on linux-image-2.6.32-5-amd64; however: Package linux-image-2.6.32-5-amd64 is not configured yet. dpkg: error processing linux-image-2.6-amd64 (--configure): dependency problems - leaving unconfigured Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-amd64 update-initramfs: failed for /boot/initrd.img-2.6.32-trunk-amd64 dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.26-2-amd64 linux-image-2.6.32-5-amd64 linux-image-2.6-amd64 initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) please provide output of: cat /etc/initramfs-tools/initramfs.conf and dpkg -l iscan* -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100705121232.gp9...@baikonur.stro.at
Bug#587608: Sorted out this bug
hello Valentin, On Fri, 02 Jul 2010, Valentin QUEQUET wrote: Package: initramfs-tools Version: 0.97 Severity: normal Hello, Dear Maks, It's a long time since we last talked together. he :) I've sorted out the bug, thought I can't explain why my system was broken in such a way to explose this bug. Please, read on. good explanation indeed, have a fix for it, will upload shortly 0.97.1: http://git.debian.org/?p=kernel/initramfs-tools.git;a=commitdiff;h=3bdc6b1d6419359309f261d045bf9c78269b9292;hp=c327689d1a2f1620e63f0f5fb8264e106444c644 thanks a lot. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100705172410.gb4...@stro.at
Bug#588140: linux-image-2.6.32-5-amd64: can't install: dpkg: error processing linux-image-2.6-amd64
forcemerge 586554 588140 stop On Mon, Jul 05, 2010 at 06:36:33PM +0200, Bruno Boettcher wrote: On Mon, Jul 05, 2010 at 02:12:32PM +0200, maximilian attems wrote: wrong package, but who reads text one copies and pastes? ;) hmmm i did :D but i was unsure whose fault it is this time well the one that shows the first error message is usally the one to hit ;) dpkg -S mkinitramfs-kpkg would have shown you that initramfs-tools is the package who carries the mkinitramfs command. yep. yes i am right to fear? or yes it will start up again? ;) won't boot with that initramfs, so correct fear. mkinitramfs-kpkg failed to create initrd image. so for future reference i should have posted the bug for that program? just for my culture, how do i find to which package that one belongs? see above, hope it helped? please provide output of: cat /etc/initramfs-tools/initramfs.conf ok that one is fine, so no trouble. and dpkg -l iscan* how did you know i have those installed? well we already got hit by people having it installed, their hook script is bogus, see bugs.debian.org/586554 for the whole story. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100705172134.gq9...@baikonur.stro.at
Re: Proposed changes to initramfs-tools hook scripts
On Wed, 30 Jun 2010, Stephen Powell wrote: Max, As promised, here are my proposed changes to the initramfs-tools hook scripts. /etc/kernel/postinst.d/initramfs-tools: http://www.wowway.com/~zlinuxman/kernel/postinst.d/initramfs-tools /etc/kernel/postrm.d/initramfs-tools: http://www.wowway.com/~zlinuxman/kernel/postrm.d/initramfs-tools I release the changes under the same license as currently used. I did not include the scripts or patches in-line in my e-mail because my e-mail client has the nasty habit of expanding tabs, inserting extra line breaks, etc. So I up-loaded the files to my web site and included links to them in this e-mail. Changes: (1) Does not create an initial RAM file system image for a custom kernel created by make-kpkg if one was not requested by the --initrd flag of make-kpkg. (2) Redirects STDOUT to STDERR when invoking update-initramfs. (Avoids output being swallowed by debconf's redirection of STDOUT.) (3) Postinst.d version always exits with status code zero, even if an error occurs attempting to delete the initramfs. thank you very much. applied your 3 changes to branch maks/hooks on http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary please review before I'd merge into master for next upload. I'm not sure if the indirection to STDERR is needed for make deb-pkg, but it shouldn't hurt there? you may want to have a look at for initramfs-tools dev http://git.debian.org/?p=kernel/initramfs-tools.git;a=blob_plain;f=docs/maintainer-notes.html;h=eeceafdfc498bd6585328d1eeb52e6e454d524ee;hb=HEAD changes in git send-email or online git repo are easier to handle. Although not strictly within your jurisdiction, I will also send you another e-mail soon with links to my proposed boot loader hook script for lilo and zipl. I'd like you to take a look at it to make sure that everything is going to flow together smoothly. I'm talking about the kernel hook script at this point, not the initramfs hook script. okay cool. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100702062045.ga4...@stro.at
Bug#587754: linux-image-2.6.32-5-686-bigmem: dpkg failed dependency problems prevent configuration of linux-image
reassign 587754 grub stop On Fri, Jul 02, 2010 at 10:01:11AM +0530, B Raveendra Reddy wrote: This is not the complete output. You removed the important parts. Bastian I am sorry. This is my first post. Here is the complete output. I am not able to install any kernel. I hope this will help you. - Setting up linux-image-2.6.32-5-686-bigmem (2.6.32-15) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686-bigmem This kernel does not seem to support TuxOnIce user interface, skipping... initrd.img(/boot/initrd.img-2.6.32-5-686-bigmem ) points to /boot/initrd.img-2.6.32-5-686-bigmem (/boot/initrd.img-2.6.32-5-686-bigmem) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686-bigmem.postinst line 400. vmlinuz(/boot/vmlinuz-2.6.32-5-686-bigmem ) points to /boot/vmlinuz-2.6.32-5-686-bigmem (/boot/vmlinuz-2.6.32-5-686-bigmem) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686-bigmem.postinst line 400. Running update-grub. Searching for GRUB installation directory ... found: /boot/grub User postinst hook script [update-grub] exited with value 1 grub error. dpkg: error processing linux-image-2.6.32-5-686-bigmem (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-686-bigmem: linux-image-2.6-686-bigmem depends on linux-image-2.6.32-5-686-bigmem; however: Package linux-image-2.6.32-5-686-bigmem is not configured yet. dpkg: error processing linux-image-2.6-686-bigmem (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.32-5-686-bigmem linux-image-2.6-686-bigmem Setting up linux-image-2.6.32-5-686-bigmem (2.6.32-15) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686-bigmem This kernel does not seem to support TuxOnIce user interface, skipping... initrd.img(/boot/initrd.img-2.6.32-5-686-bigmem ) points to /boot/initrd.img-2.6.32-5-686-bigmem (/boot/initrd.img-2.6.32-5-686-bigmem) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686-bigmem.postinst line 400. vmlinuz(/boot/vmlinuz-2.6.32-5-686-bigmem ) points to /boot/vmlinuz-2.6.32-5-686-bigmem (/boot/vmlinuz-2.6.32-5-686-bigmem) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686-bigmem.postinst line 400. Running update-grub. Searching for GRUB installation directory ... found: /boot/grub User postinst hook script [update-grub] exited with value 1 dpkg: error processing linux-image-2.6.32-5-686-bigmem (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-686-bigmem: linux-image-2.6-686-bigmem depends on linux-image-2.6.32-5-686-bigmem; however: Package linux-image-2.6.32-5-686-bigmem is not configured yet. dpkg: error processing linux-image-2.6-686-bigmem (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.32-5-686-bigmem linux-image-2.6-686-bigmem regards, ravi -- http://www.imsc.res.in B. Raveendra Reddy | email: r...@imsc.res.in The Institute of Mathematical Sciences | phone: (91)44-2254 3222 Chennai 600 113 |(91)44-2448 7845 (Res) India | fax : (91)44-2254 1586 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.1.10.1007020953270.3...@as100.imsc.res.in -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100702062726.go9...@baikonur.stro.at
Bug#587608: Repeatable bug here.
a separate bug report might have been cool, currently no idea that your both report are identicaly anyway, let's try to sort that out. On Wed, Jun 30, 2010 at 04:55:30PM +0200, Valentin QUEQUET wrote: -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=no backup_initramfs=yes why did you set that? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100630130352.gm9...@baikonur.stro.at
Bug#587608: Repeatable bug here.
On Wed, 30 Jun 2010, Valentin QUEQUET wrote: Package: initramfs-tools Version: 0.97 Severity: normal Hello the hurd, I've updated a few packages yesterday, amongst them is initramfs-tools (0.97). please send also output of: ls /usr/share/initramfs-tools/hooks/ and sh -x /usr/sbin/update-initramfs -u and sh -x /usr/sbin/mkinitramfs -o /tmp/foo -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100630133147.gb29...@stro.at
Re: [DRAFT] Policy for Linux kernel, initramfs, boot loader update process
On Wed, Jun 30, 2010 at 10:31:32AM -0400, Stephen Powell wrote: dpkg does not prevent multiple boot loaders from being installed concurrently; but this environment is not supported by the various system maintainer scripts of Debian, even today. For example, update-initramfs -u currently checks to see if lilo is installed, and if it is, it runs lilo. But if grub (either version 1 or version 2) is installed also, it issues the following messages: WARNING: grub and lilo installed. Please de-install unused bootloader. It could also test for other boot loaders as well, such as extlinux, but it doesn't. The point is that Debian's maintainer scripts do not support multiple concurrently-installed boot loaders even today. It did support it, but it turned out to be a greater pain to keep that then to kick that support, see cc33aa5bfb7f68793 in initramfs-tools git repo for the support that was there until lenny. bug #574553 axed it. support was fragile and thus I don't plan to reinstate that. extlinux is quite new in debian. the usual case were people having upgraded from lilo to grub but didn't change the do_bootloader setting in /etc/kernel-img.conf, because they didn't knew it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100630143154.gn9...@baikonur.stro.at
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
On Tue, Jun 29, 2010 at 09:05:55AM +0900, Olaf Meeuwissen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the info. I've checked the dash and bash manual pages but
running under errexit seems to be the same as using `set -e`. The hook
provided by iscan has done a `set -e` from the beginning so that can't
be the reason (unless I misunderstood the errexit stuff).
FTR, I've attached the hook scripts template. The @...@ stuff is
substituted at package build time.
hmm I don'T see at a quick look why it failed.
Hope this helps,
but I don't get it'S purpose?
why do you want mkinitramfs to clean some file in your statedir?
this seems the wrong location to do such
also why does it need udev (just a minor nit..)?
#! /bin/sh
# Copyright (C) 2009 SEIKO EPSON CORPORATION
#
# License: GPLv2+
state_d...@deb_configure_localstatedir@/lib/@DEB_SOURCE_PACKAGE@
set -e
PREREQS=udev
prereqs()
{
echo $PREREQS
}
case $1 in
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
test -r $STATE_DIR/clean-files || exit 0
awk '{print $2}' $STATE_DIR/clean-files \
| while read file; do
test -e ${DESTDIR}$file rm -f ${DESTDIR}$file
done
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100629093312.ge9...@baikonur.stro.at
Bug#573144: Re: Bug#573144: linux-image-2.6-686: kernel freezes related to i915 handle error
On Tue, Jun 29, 2010 at 11:02:55AM +0200, Zbynek Michl wrote: So 2.6.32-3-686 freezes too. I don't know how to debug it, because kernel seems to be completely dead :( Zbynek did you check with latest experimental intel driver? also we will shortly make 2.6.35-rcX available. the old intel driver support is since some time messy, sorry for that. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100629112911.gf9...@baikonur.stro.at
Re: [DRAFT] Policy for Linux kernel, initramfs, boot loader update process
On Tue, Jun 29, 2010 at 04:24:48PM -0400, Stephen Powell wrote: On Mon, 28 Jun 2010 19:07:16 -0400 (EDT), Ben Hutchings wrote: ... I can put a one-time warning into linux-base. But the default for squeeze must be 'no'. It should not be necessary to create /etc/kernel-img.conf at all in squeeze. Sorry I didn't think of this the first time, but there are up to four steps to preparing a kernel for booting: (1) Installation of the kernel itself (2) Creation of an initial RAM file system (3) Updating symbolic links they are deprecated and shouldn't be necessary. there are even more evil incarnations like reverse symlinks or whatever. which we no longer support since longer.. it be better to just get rid of them. (4) Running the boot loader installer Not all steps are required in all cases, depending on the circumstances. Neither grub version 1 nor grub version 2 generally use symbolic links; so that hasn't been on the forefront of most people's minds. Strictly speaking, the historic boot loaders such as lilo and zipl don't *have* to use symbolic links, but as they have historically been used in Debian systems, they generally do. Obviously, item 1 takes care of itself. For stock kernels, item 2 also takes care of itself. And it appears that the latest version of initramfs-tools provides hook scripts of the same name in /etc/kernel/postinst.d and /etc/kernel/postrm.d which take care of item 2 for kernel image packages created by make-kpkg and make deb-pkg as well. (Actually, that item does need some work, but I'll come back to that later. For now, let's assume that item 2 is taken care of.) Item 4 is what we've been talking about. Each boot loader that needs some kind of update will have to provide a hook script starting with zz-. Now the question is, what should we do about item 3, maintaining the symlinks? For stock kernels, that has historically been handled by variables in /etc/kernel-img.conf: do_symlinks, relative_links, and link_in_boot, mainly, though there are other seldom-used variations. But you just said that the goal was to be able to eliminate /etc/kernel-img.conf. So what do we do about symlinks? Fortunately, the update-initramfs -u issue doesn't affect the symlinks. The symlinks only need to be maintained, if at all, when a kernel is installed, updated, or removed. The symlinks are not, strictly speaking, associated with a package. Should the boot loader script take care of it? Or should this be a separate script? What do you think? get rid of them. they are ugly and useless. I said I would come back to initramfs-tools; so now I'm back. There are two issues with the script as written today. (1) it does not redirect standard output to standard error when invoking update-initramfs. Thus, the user sees no output (since debconf swallows it) and, depending on the output, it may cause problems for debconf. (2) it unconditionally creates an initial RAM file system for kernel image packages created by make-kpkg, even if the user doesn't want one. There is a way to check to see if one is needed. I can submit a revised version of the script if you like. Would you like me to do so? hate those indirections due to debconf magic, but why would the hook scripts need one. thanks for hints, been staying away from debconf for long.. the unconditional is expected and there is a wishlist bug open for that it has not high priority as many things do not work if you don'T use an initramfs. thanks ps if you want the no cc thing set up your mua appropriately. here in d-kernel we do cc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100629203540.gh9...@baikonur.stro.at
Bug#582177: grub-pc: system with RAID CRYPTO; system with problem to be deactivated August 2010
On Tue, Jun 29, 2010 at 04:45:33PM -0400, crop...@acm.org wrote: Sirs and Dames: The system that has the problem discussed under bug #'s 582177 and 582342 will be deactivated the second week of August 2010. It will not be reactivated until October 2010; it might be cannibalized. Should you want me to do anymore major smoke-tests on this bug, I will gladly do two-to-three more until the computer is deactivated. Please get any tests or instructions to me soon. afaik this is a grub2 bug, please update to latest available grub2 in sid and do grub-install /dev/sda grub-install /dev/sdb .. (dont' remember how many discs you have) update-grub and then try to reboot, thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100629204438.gi9...@baikonur.stro.at
Bug#581596: linux-2.6: pxe-booting a qemu-kvm or kvm guest with virtio network (fai-client) produces kernel panic
On Tue, Jun 29, 2010 at 11:38:36PM +0200, Holger Fischer wrote: Hallo, it's not a kernel problem. When installing the newer initramfs-tools from official lenny fai repo (http://www.informatik.uni-koeln.de/fai/download/lenny/, initramfs-tools_0.93.4-grml02_all.deb) pxe boots fine with virtio-net guests (both with plain lenny 2.6.26... and backported 2.6.32 from squeeze). Possibly you want to assign this bug initramfs-tools. newer initramfs-tools has several network boot fixes indeed. can you please test that it works with latest 0.97 in squeeze. that one should install just fine in lenny. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100629215737.gj9...@baikonur.stro.at
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
On Mon, Jun 28, 2010 at 05:16:40PM +0900, Olaf Meeuwissen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Image Scan! for Linux upstream maintainer here. Care to point out why iscan is the culprit? I went through the logs but nothing ran a bell. you are sending the message to the wrong recipient. we do not maintain that iscan software, nor their initramfs-tools hooks please nag them. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100628083143.gy9...@baikonur.stro.at
Re: [DRAFT] Policy for Linux kernel, initramfs, boot loader update process
On Mon, 28 Jun 2010, Ben Hutchings wrote: 2. Packages for boot loaders that need to be updated whenever the files they load are modified must also install hook scripts in /etc/mkinitramfs/post-update.d. Initramfs builders must call these scripts using run-parts after they create, update or delete an initramfs. The arguments given to these hook scripts are the kernel ABI version and the absolute path to the initramfs image. Please rename to more generic /etc/initramfs path. mkinitramfs is initramfs-tools specific. otherwise ack. 3. Initramfs builders must complete their work before returning from the kernel postinst hook script. [initramfs-tools currently uses a trigger to defer this because it can also be invoked twice, but this means it also has to know how to update specific boot loaders.] not twice but multiple times, if you upgrade together for example udev, lvm2, cryptsetup, mdadm and linux-2.6. 4. During a kernel package installation, upgrade or removal, various boot loader hooks may be invoked (in this order): a. A postinst_hook or postrm_hook command set by the user or the installer in /etc/kernel-img.conf b. A hook script in /etc/mkinitramfs/post-update.d c. A hook script in /etc/kernel/postinst.d or .../postrm.d To avoid unnecessary updates, the hooks invoked at step a and b may check whether $DPKG_MAINTSCRIPT_PACKAGE begins with 'linux-image-' and do nothing in this case. [Is this sensible or is it too 'clever'?] what is the intent of that point? sorry you lost me here. 5. Kernel and initramfs builder packages must not invoke boot loaders except via hooks. If /etc/kernel-img.conf contains an explicit 'do_bootloader = yes', kernel package maintainer scripts should warn that this is now ignored. for backward compat and upgrade purpose from lenny, I think the must is wrong. 6. The installer must not define do_bootloader, postinst_hook or postrm_hook in /etc/kernel-img.conf. --- thanks -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100628084532.ga23...@stro.at
Re: [DRAFT] Policy for Linux kernel, initramfs, boot loader update process
On Mon, Jun 28, 2010 at 11:16:58AM -0400, Stephen Powell wrote: --- 1. Packages for boot loaders that need to be updated whenever the files they load are modified (i.e. those that store a block list) must install hook scripts in /etc/kernel/postinst.d and /etc/kernel/postrm.d, which will be called on installation/upgrade and removal of kernel packages, respectively. The arguments given to all kernel hook scripts are the kernel ABI version (the string that uname -r reports) and the absolute path to the kernel image. Currently, hook scripts invoked by a stock kernel maintainer script or a maintainer script from a kernel image package created by make-kpkg pass these exact same arguments. no. But a maintainer script for a kernel image package created by make deb-pkg passes only the first argument. no. Existing hook scripts rely on that difference to determine whether or not to take action. For example, the initramfs hook script provided by the initramfs-tools package tests the number of arguments and exits without doing anything if more than one argument is supplied. In other words, this hook script is designed to create the initial RAM file system for a kernel image created by make deb-pkg, and only for a kernel image created by make deb-pkg. It does nothing otherwise. Are you proposing to change this behavior? please get your facts right before spamming the world. kthxbye. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100628164510.gb9...@baikonur.stro.at
Re: [DRAFT] Policy for Linux kernel, initramfs, boot loader update process
On Mon, Jun 28, 2010 at 01:35:20PM +0100, Ben Hutchings wrote: On Mon, 2010-06-28 at 10:45 +0200, maximilian attems wrote: On Mon, 28 Jun 2010, Ben Hutchings wrote: [...] 4. During a kernel package installation, upgrade or removal, various boot loader hooks may be invoked (in this order): a. A postinst_hook or postrm_hook command set by the user or the installer in /etc/kernel-img.conf b. A hook script in /etc/mkinitramfs/post-update.d c. A hook script in /etc/kernel/postinst.d or .../postrm.d To avoid unnecessary updates, the hooks invoked at step a and b may check whether $DPKG_MAINTSCRIPT_PACKAGE begins with 'linux-image-' and do nothing in this case. [Is this sensible or is it too 'clever'?] what is the intent of that point? sorry you lost me here. I'm wondering whether this is a reasonable way to test whether a kernel package upgrade is in progress. currently it is easy to tell in /etc/kernel if you are invoked by linux-2.6 as it doesn't define KERNEL_PACKAGE_VERSION. make deb-pkg run-parts invocation doesn't pass at all the second stupid arg. for update-initramfs it shouldn't be necessary as the updates are trigger updated anyway. 5. Kernel and initramfs builder packages must not invoke boot loaders except via hooks. If /etc/kernel-img.conf contains an explicit 'do_bootloader = yes', kernel package maintainer scripts should warn that this is now ignored. for backward compat and upgrade purpose from lenny, I think the must is wrong. [...] Do you mean that the boot loader might not get updated during a dist-upgrade? I think that even if the kernel or initramfs builder package is installed/upgraded before the boot loader package is upgraded to include hook scripts, the boot loader package will update the boot loader when it is upgraded. (And the boot loader package is sure to be upgraded in order to add those hook scripts.) yes the bootloader might be Lenny one and thus no hooks to be run. in partial upgrades you get all kind of crazy pathes, thus it is better to handle the previsous distro. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100628165728.gc9...@baikonur.stro.at
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
On Tue, Jun 29, 2010 at 08:02:03AM +0900, Olaf Meeuwissen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2010???06???28??? 17:31, maximilian attems wrote: On Mon, Jun 28, 2010 at 05:16:40PM +0900, Olaf Meeuwissen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Image Scan! for Linux upstream maintainer here. Care to point out why iscan is the culprit? I went through the logs but nothing ran a bell. you are sending the message to the wrong recipient. we do not maintain that iscan software, nor their initramfs-tools hooks please nag them. # I'd have to nag myself then. I maintain iscan. Let me put the question differently then. What exactly led to the conclusion that iscan's initramfs hooks are the culprit. There is nothing in the log that gives me any clues about why iscan is the culprit. The hook provided by iscan is so trivial (and has worked fine upto at leat 0.94.4) that I don't see what is wrong. I haven't looked at the iscan hook script yet. The difference in initramfs-tools is that now the hooks are run under errexit and thus may abort. afair it has been determined that your hook script fails (mkinitramfs needs to be more explicit about what goes on). -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100628225506.gd9...@baikonur.stro.at
Bug#585677: linux-image-2.6.32-5-486: impossible to mount partitions (except /)
reassign 585677 initscripts stop On Sat, Jun 26, 2010 at 09:57:21PM +0100, Ben Hutchings wrote: On Fri, 2010-06-25 at 22:49 +0200, Stéphane Blondon wrote: 2010/6/20 Ben Hutchings b...@decadent.org.uk: Please try booting with 'break=premount' added to the kernel parameters. When the boot process stops you should get an '(initramfs)' prompt. At the prompt, please run 'blkid' and send the output. Feel free to abbreviate the UUIDs if you copy the output by hand. This is what I get (the longest UUID are abbreviated (those for swap and ext3)): (initramfs) blkid /dev/sda1: SEC_TYPE=msdos UUID=6466-FB4C TYPE=vfat /dev/sda3: UUID=1E21-1DFD TYPE=vfat /dev/sda5: LABEL=XP UUID=8444-ACD1 TYPE=vfat /dev/sda6: UUID=0bd127f7-...89d0 TYPE=swap /dev/sda7: UUID=9e7a1cee-...806a SEC_TYPE=ext2 TYPE=ext3 /dev/sdb5: UUID=58027110-...91d1 SEC_TYPE=ext2 TYPE=ext3 /dev/sdb6: UUID=8a64c937-...52db SEC_TYPE=ext2 TYPE=ext3 /dev/sdb7: UUID=47f58f90-...64e5 SEC_TYPE=ext2 TYPE=ext3 (initramfs) Given that the kernel command-line has 'root=UUID=9e7a1cee-d7c8-4244-95fe-757af64d806a', and that that filesystem is accessible, I think this must be some strange bug in the initramfs scripts and not the kernel. I'll reassign it accordingly. Ben. given that the root is mounted correctly and the initramfs business is not to mount cat and dogs of /etc/fstsab, reassigning: dpkg -S /etc/init.d/mountall.sh initscripts but it might very well be a util-linux bug. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100627112156.gx9...@baikonur.stro.at
Bug#587014: [linux-2.6] screen brightness can't be modified on Panasonic S9
On Thu, Jun 24, 2010 at 11:22:51PM +0900, Nicolas Limare wrote: Package: linux-2.6 Severity: normal --- Please enter the report below this line. --- Presing the light up / light down keys doesn't modify the LCD screen brightness. Directly writing to /sys/class/backlight/panasonic/brightness has the same effect : nothing. /sys/class/backlight/panasonic/actual_brightness is modified, but the screen brightness isn't affected. I tried to reboot with lenny 2.6.26-2 kernel on the same system, and the brightness could be changed by pressing the up/down keys, so I believe it is a kernel issue (but gdm couldn't properly start, so it is not a proper workaround). It is a serious issue, since the screen default brightness is very strong and uncomfortable. I believe it is related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588983 I tried to use acpi packages from unstable, without improvement. please use reportbug the next time this report is missing important info, followup is possible with: reportbug -N bugnr did you try 2.6.34 from experimental, does it work there? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100624144142.gw9...@baikonur.stro.at
Re: [RFC] Updating boot loaders in lenny and squeeze
On Wed, Jun 23, 2010 at 11:20:59AM -0400, Stephen Powell wrote: On Wed, 23 Jun 2010 11:04:06 -0400 (EDT), Ben Hutchings wrote: yaird is no longer present in testing or unstable, so it is a non-issue as far as I'm concerned. I see it is gone from testing, but it is still present in unstable, as of this moment, according to the Debian web site. it has no support for any recent linux-2.6. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100623203059.gv9...@baikonur.stro.at
Bug#586363: closed by maximilian attems m...@stro.at (Re: Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated)
On Tue, Jun 22, 2010 at 11:30:58AM +0200, Michal Suchanek wrote: I am not concerned that initramfs would not boot (which is what the backup initramfs is for) but that the new kernel might not boot (or might boot but bring the system up in unusable state) which is unfortunately not uncommon. Then I would appreciate having an up-to-date initramfs for the running kernel rather than later, possibly broken kernel. linux-2.6 early testers is not the major concern of the sorting alg, again thanks for raising the point. anyway if you want policy changes of initramfs next time please discuss that first on d-kernel or initra...@vger so that a consensus could emerge. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100622093117.gt9...@baikonur.stro.at
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
On Sat, 19 Jun 2010, Michal Suchanek wrote: On 19 June 2010 15:23, maximilian attems m...@stro.at wrote: On Sat, Jun 19, 2010 at 03:17:20PM +0200, Michal Suchanek wrote: Why is sorting code required? dpkg --compare-versions does sort rc images before non rc ones. as mentioned in the manpages initramfs-tools updates the newest one. here the assumption is that rc is newer then not rc, which is wrong. but rc admin should be smart enough to kick rc once the real is out. So the issue is that it updates the newest kernel, not the running kernel if that is different. please explain why it should update the running one? this makes zero sense for the most usual case of newer linux-2.6 installed but not yet rebooted. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100621221338.gc7...@stro.at
Bug#582776: initramfs-tools: pointless generation of an initrd for initrd-free custom kernels
On Mon, 21 Jun 2010, Michael Prokop wrote: What about a configuration variable to completely disable it (as mentioned above) and another one to white- or blacklist specific kernels? well we could have one that can be tristate all, none, version_list? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100621221055.gb7...@stro.at
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
hello, On Mon, 21 Jun 2010, thebickhams wrote: log file as attachment from a quick look at this looks like an older mkinitramfs, we'd need belows output from the one that fails to install: sh -x /usr/sbin/mkinitramfs -o /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64.new 2.6.34-0.slh.9-sidux-amd64 1/tmp/mkinitramfs.log 21 please resend from 0.97, thanks. your first report shows clearly an mkinitramfs failure, currently we don't know where to trace it. thanks -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100621220600.ga7...@stro.at
Bug#509077: initramfs-tools: support alternate DHCP port and DHCP vendor-class-identifier
On Tue, 08 Jun 2010, Michael Prokop wrote: * Vagrant Cascadian vagrant+debianb...@freegeek.org [Mit Dez 17, 2008 at 07:01:51 -0800]: please consider the attached patch, which adds boot prompt parameters for two of ipconfig's commandline options in the configure_networking function: - using an alternate DHCP port (dhcpport=NNN, ipconfig -p NNN) - specifying the vendor-class-identifier (dhcpvci=XXX, ipconfig -i XXX) supporting these options gives additional flexibility in distinguishing thin clients from conventional workstations in a mixed network. Sorry that no one took care of your bugreport for so long, Vagrant. Patch looks fine to me. maks, any objections against inclusion of the patches? I had been dragging that patch as I do not like to add to many bootparams that are outside of documented upstream linux-2.6 handling and thus initramfs-tools specific. waited to see if a second voice would raise.. I do not see so much the point of setting ipconfig vendor class id. why would that be needed for booting? the alternate DHCP port looks indeed more interesting, but no idea how common that is in the wild? and if there is not a place in the ip= monster bootparam? thanks -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100619164316.gc24...@stro.at
Bug#582776: initramfs-tools: pointless generation of an initrd for initrd-free custom kernels
On Wed, 09 Jun 2010, Michael Prokop wrote: How about giving people the chance to disable generation of initrds through e.g. /etc/default/initramfs-tools? well that would assume that you want *none* anywhere, which is often not the case as you may very well have a mixed setup. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100619150627.gb24...@stro.at
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
On Sat, Jun 19, 2010 at 03:17:20PM +0200, Michal Suchanek wrote: Why is sorting code required? dpkg --compare-versions does sort rc images before non rc ones. as mentioned in the manpages initramfs-tools updates the newest one. here the assumption is that rc is newer then not rc, which is wrong. but rc admin should be smart enough to kick rc once the real is out. I would just expect that the running kernel is updated, no sorting is required for that. so i do not see a special point for adding more complex sorting code. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100619132330.gr9...@baikonur.stro.at
Re: [initramfs-tools PATCH] scripts/nfs: cleanup retry logic
On Thu, 17 Jun 2010, Ferenc Wagner wrote: The condition of log_end_msg was always true. Calling do_nfsmount before the loop lets us drop two other checks. Signed-off-by: Ferenc Wagner wf...@niif.hu thanks nice, merged and pushed out, will be in next upstream release. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100618094443.gb25...@stro.at
Bug#505609: loader varialbe in kernel maintainer scripts
On Fri, Jun 18, 2010 at 10:55:35AM -0400, Stephen Powell wrote: So far, Ben has only agreed to reinstate the historic function of do_bootloader = yes in /etc/kernel-img.conf for Lenny kernel maintainer scripts. It hasn't actually happened yet, but he has agreed to restore its former function in Lenny as it was in Etch and previous releases. I am trying to persuade him to restore its function in Squeeze too. Whether or not I am successful remains to be seen. it is gone, get over it. In the mean time, for lilo users of Squeeze/Sid who use *only* official stock Debian kernels, I recommend that they use the hook script described in an earlier post to this bug log in conjunction with other appropriate settings in /etc/kernel-img.conf. it is about time that lilo gets an hook script. even extlinux has one although that one seems to trigger funny bug reports, but we are used to forward such bugs. For lilo users of Squeeze/Sid who use custom kernels created by make-kpkg, k-p is deprecated, use upstream way: make deb-pkg needs no strange debian scripting and is maintained in linux-2.6 itself. As for update-initramfs -u, it *will* invoke lilo if lilo is installed and do_bootloader = yes is specified in /etc/kernel-img.conf, which I highly recommend. this fall back will be gone as soon as squeeze is out. so you'd really need to gear up. There are types of upgrades which do not affect the kernel itself but which do require that the initial RAM file system be re-built. And for lilo users, it is essential that lilo be run after any changes are made to the initial RAM file system. update-initramfs -c and update-initramfs -d, however, will *not* invoke lilo, even if do_bootloader = yes is specified in /etc/kernel-img.conf. yes in those case either you have valid hooks or an intelligent postinst. thanks -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100618155110.gp9...@baikonur.stro.at
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
On Fri, Jun 18, 2010 at 09:55:12PM +0200, Michal Suchanek wrote:
Package: initramfs-tools
Version: 0.94.4~bpo50+1
Severity: normal
Note that the initramfs is updated for a non-running kernel on package
removal.
The following packages will be REMOVED:
plymouth plymouth-themes-solar{a}
0 packages upgraded, 0 newly installed, 2 to remove and 4 not upgraded.
Need to get 0B of archives. After unpacking 1307kB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
(Reading database ... 266342 files and directories currently installed.)
Removing plymouth-themes-solar ...
Removing plymouth ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.34-rc4-amd64
Processing triggers for man-db ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done
Writing extended state information... Done
rc linux images are special, people having them are expected
to handle their initramfs.
i don't see the point of introducing special sorting code that
would discriminate those rcs.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2010061907.gq9...@baikonur.stro.at
Bug#586002: initramfs-tools: should work around 'find -printf %Y' bug
tags 586002 pending
stop
On Tue, 15 Jun 2010, Colin Watson wrote:
The change to filter out looping or broken symlinks from the initramfs,
written by me for Ubuntu and applied to Debian for #575157, tickles a
bug in find (which I think also had an associated Debian bug, but I've
been unable to find it):
https://savannah.gnu.org/bugs/index.php?29460
This was fixed in 4.5.8, which is currently only in experimental. In
any case findutils is very deep in the dependency chain for upgrades and
I believe it would be a good idea to avoid requiring a new version of it
(I've had problems quite recently with strict dependencies on findutils
causing unresolvable dependency loops). The following patch works
around this bug in a reasonably straightforward way.
diff --git a/mkinitramfs b/mkinitramfs
index 1c6ad28..e3b392e 100755
--- a/mkinitramfs
+++ b/mkinitramfs
@@ -304,8 +304,8 @@ fi
# Remove any looping or broken symbolic links, since they break cpio.
[ ${verbose} = y ] xargs_verbose=-t
-find ${DESTDIR} -type l -printf '%p %Y\n' | sed -n 's/ [LN]$//p' \
- | xargs ${xargs_verbose:-} -rL1 rm -f
+(cd ${DESTDIR} find . -type l -printf '%p %Y\n' | sed -n 's/ [LN]$//p' \
+ | xargs ${xargs_verbose:-} -rL1 rm -f)
[ ${verbose} = y ] echo Building cpio ${outfile} initramfs
(
Thanks,
findutils debian bug was #576772.
thanks applied and pushed out will be in next release.
--
maks
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100616135818.gb14...@stro.at
Bug#583643: linux-image-2.6.34-1-686: iwlagn disassociate under high load
On Sat, May 29, 2010 at 08:19:25AM +0200, Friedemann Stoyan wrote: Package: linux-2.6 Version: 2.6.34-1~experimental.1 Severity: normal Dear Maintainers, after upgrading to kernel 2.6.34-1~experimental.1 my iwlagn based wirless lan gets unstable under higher/heavy load: [226918.161883] wlan0: deauthenticated from 00:13:5f:ff:04:80 (Reason: 10) [226918.176600] mac80211-phy0: failed to remove key (0, 00:13:5f:ff:04:80) from hardware (-22) [226918.192593] cfg80211: Calling CRDA to update world regulatory domain [226918.192637] cfg80211: Calling CRDA for country: EU [226918.765130] ADDRCONF(NETDEV_UP): wlan0: link is not ready [226922.877709] wlan0: authenticate with 00:13:5f:ff:04:80 (try 1) [226922.878811] wlan0: authenticated [226922.878851] wlan0: associate with 00:13:5f:ff:04:80 (try 1) [226922.880158] wlan0: RX AssocResp from 00:13:5f:ff:04:80 (capab=0x111 status=0 aid=1) [226922.880165] wlan0: associated [226922.884919] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [228503.826349] wlan0: deauthenticated from 00:13:5f:ff:04:80 (Reason: 2) [228503.844068] mac80211-phy0: failed to remove key (0, 00:13:5f:ff:04:80) from hardware (-22) [228503.868282] cfg80211: Calling CRDA to update world regulatory domain [228503.868336] cfg80211: Calling CRDA for country: EU [228504.465770] ADDRCONF(NETDEV_UP): wlan0: link is not ready [228508.580218] wlan0: authenticate with 00:13:5f:ff:04:80 (try 1) [228508.581246] wlan0: authenticated [228508.581285] wlan0: associate with 00:13:5f:ff:04:80 (try 1) [228508.582488] wlan0: RX AssocResp from 00:13:5f:ff:04:80 (capab=0x111 status=0 aid=1) [228508.582494] wlan0: associated In my accesspoint (cisco 1131ag) logfile I can see: May 28 2010 22:00:13.519 CEST: %DOT11-6-ASSOC: Interface Dot11Radio1, Station 0016.eaef.2cea Associated KEY_MGMT[WPAv2 PSK] May 28 2010 22:13:51.212 CEST: %DOT11-4-MAXRETRIES: Packet to client 0016.eaef.2cea reached max retries, removing the client May 28 2010 22:13:51.213 CEST: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 0016.eaef.2cea Reason: Previous authentication no longer valid May 28 2010 22:13:51.215 CEST: %DOT11-4-MAXRETRIES: Packet to client 0016.eaef.2cea reached max retries, removing the client May 28 2010 22:13:57.856 CEST: %DOT11-6-ASSOC: Interface Dot11Radio1, Station 0016.eaef.2cea Associated KEY_MGMT[WPAv2 PSK] May 28 2010 22:40:18.691 CEST: %DOT11-4-MAXRETRIES: Packet to client 0016.eaef.2cea reached max retries, removing the client May 28 2010 22:40:18.695 CEST: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 0016.eaef.2cea Reason: Previous authentication no longer valid May 28 2010 22:40:23.558 CEST: %DOT11-6-ASSOC: Interface Dot11Radio1, Station 0016.eaef.2cea Associated KEY_MGMT[WPAv2 PSK] With kernel linux-image-2.6.32-5-686 the wlan works prefectly. please report upstream on bugzilla.kernel.org and let us know bug nr to track it, thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100529064000.gf9...@baikonur.stro.at
Re: Uploading 2.6.32-14
On Fri, May 28, 2010 at 04:03:19AM +0100, Ben Hutchings wrote: So far as I'm aware, there are no remaining blockers for an upload (and 2.6.32-13 cannot transition to testing due to the build failure on hppa). Therefore I intend to upload on Friday or Saturday. Shout if there's something I need to wait for. updating openvz to latest in a sec, please wait. thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100528153114.ga9...@baikonur.stro.at
Bug#583532: linux-image-2.6.34-1-amd64: Please, enable VGASWITCHEROO support
force-merge 582637 583532 stop On Fri, May 28, 2010 at 09:17:51AM +0200, Federico Di Gregorio wrote: Package: linux-2.6 Version: 2.6.34-1~experimental.1 Severity: wishlist Please, enable support for VGASWITCHEROO. It should not do any bad to people not using it and it is extremely useful for all the double-board laptops out there. Thanks, federico from a debian guy, I'd expect to check for dups before reporting, but I need to revisit my low expectations as door entry focuses on bureaucracy and not skills. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100528155817.gb9...@baikonur.stro.at
Bug#579702: mkinitramfs fails on mylex raid devices (DAC960)
On Fri, 30 Apr 2010, Claus Herwig wrote: Once figured out, this is easily corrected. Please find a short patch for /usr/share/initramfs-tools/hook-functions attached. Thank you, Claus Herwig applied allmost as is and will be in next upload. thank you! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100528234434.gh3...@stro.at
initramfs-tools 0.95 release
most notably a license change to GPL in order to ease collaboration with dracut. LZO compression and xHCI boot support may stick out for users. pxelinux BOOTIF saw fixes. thanks for the patches. shortlog tells it all, mostly small bugfixes all over the place: Axel Beckert (1): mkinitramfs.8: Add information about $TMPDIR environment variable Claus Herwig (1): mkinitramfs: fix MODULES=dep on mylex raid devices (DAC960) Michael Prokop (1): Support booting from USB 3 xHCI-based controllers Vagrant Cascadian (2): configure_networking: pxelinux BOOTIF fixes init: add BOOTIF bootarg bert schulze (2): mkinitramfs: add LZO support mkinitramfs: use -9 for lzop maximilian attems (33): update TODO list hook-functions: refactor copy_exec mkinitramfs: check only once for existing ldd mkinitramfs: Use TMPDIR definition mkinitramfs: guard against empty EXTRA_CONF update-initramfs: Use nounset mkinitramfs: Fix several unbound variables mkinitramfs: On verbose indication what we rm bug script: include sizes of generated initramfs debian/script: add generated resume param to bug init: fix hardcoded resume handling hook-functions: manual_add_modules simplify hook-functions: copy_modules_dir() small simplifications mkinitramfs.8: Fix wrong sourcing in boot script initramfs-tools.8: Mention /scritps/functions initramfs-tools.8: cryptopts param gone initramfs-tools.8: document BOOTIF variable configure_networking(): work with empty DEVICE string hook-functions: add hid-apple Revert mkinitramfs: only copy modprobe conf files initramfs-tools: change license to GPL hook-functions: re-add hid-microsoft Merge branch 'sid' debian/copyright: add boilerplate to keep lintian happy. hook-functions: Fix copy_modules_dir() release 0.95 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100529044833.gc9...@baikonur.stro.at
Bug#578152: NFS problems with kernel 2.6.32
tags 578152 moreinfo stop On Wed, May 26, 2010 at 11:13:52AM +0400, Vladimir Kuklin wrote: Package: linux-2.6 Version: 2.6.32-11~bpo50+1 Followup-For: Bug #578152 ** Version: Linux version 2.6.32-bpo.4-openvz-amd64 (Debian 2.6.32-11~bpo50+1) (norb...@tretkowski.de) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Thu Apr 8 11:21:30 UTC 2010 please test against newer in unstable that is outdated and not a supported openvz release, thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100526171954.gg19...@baikonur.stro.at
2.6.32.14 stable
hello merged in baladin openvz release for debian upcoming 2.6.32-14, but seeing conflicts with now already latest upstream stable. could you please merge 2.6.32.14? thank you -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100526230306.gc3...@stro.at
Bug#583310: linux-image-2.6.32-5-686: kernel panic! booting 2.6.32-5-686
tags 583310 moreinfo stop On Wed, May 26, 2010 at 06:34:11PM -0400, Patrick Naylor wrote: Package: linux-2.6 Version: 2.6.32-13 Severity: critical Tags: sid Justification: breaks the whole system no breaking one box is not RC. I get a kernel panic when booting kernel 2.6.32-686 and -486, which does not happen with 2.6.32-3 or 2.6.32-2. Machine: Pentium 3 600 MHz. you have to post it, don't have any remote cristall ball divine capabilities available yet. either set up a netconsole or post an image of it at least. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100526225807.gb5...@baikonur.stro.at
Bug#582481: [pkg-cryptsetup-devel] Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
tags 582481 moreinfo stop On Tue, May 25, 2010 at 07:46:16AM +0200, Andre Pawlowski wrote: Hi, if it is a bug in udev, why does the system start with the old initramfs? dude you have not provided the error message or presumed failure of the new initramfs!? how about telling that as a start. can you still reproduce it with latest initramfs-tools? thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100525065953.gf19...@baikonur.stro.at
Bug#582637: [linux-2.6] Please enable CONFIG_VGA_SWITCHEROO
On Sat, May 22, 2010 at 12:53:04PM +0200, Daniele Benucci wrote: Package: linux-2.6 Version: 2.6.34-1 Severity: wishlist --- Please enter the report below this line. --- Please enable CONFIG_VGA_SWITCHEROO kernel config option (available from 2.6.34) to enable support for video card switching on notebooks with both integrated and discrete video card (aka hybrid graphics). you have to check that it does not break xorg, did you? (considering xorg packages from squeeze) until no one checks that no point in making loud noise. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100524181828.gd19...@baikonur.stro.at
Bug#582637: [linux-2.6] Please enable CONFIG_VGA_SWITCHEROO
On Mon, May 24, 2010 at 08:51:13PM +0200, Joachim Breitner wrote: Hi, I didn't and I will check as soon as possible (this means this weekend as I'm going to be away for work this week) As far as I have understood how vga switcheroo works I think it doesn't break anything in Xorg (the switch is made via echoing in /sys, but the actual switch is performed when restarting Xorg), but you're right this is a thing worth to be checked. I just tried it on my Thinkpad T400, and after loading the right modules (i915 and radeon) with the right option (modeset=1), it worked as advertised. No problem with X. I also second the request to enable this option. (I reverted to unstable???s kernel, though, because my iwlagn wireless connection was instable with 2.6.34) did you check with intel xorg driver from unstable/testing? please provide version? as soon this is done, I can turn it on. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100524185033.ge19...@baikonur.stro.at
Bug#574523: igb backport
On Sat, May 22, 2010 at 08:26:01PM +0200, Moritz Muehlenhoff wrote: On Sat, Apr 03, 2010 at 11:49:57PM +0100, Ben Hutchings wrote: On Thu, 2010-03-18 at 20:49 +0100, maximilian attems wrote: Package: linux-2.6 Version: 2.6.32-10 Severity: important see in git ubuntu lucid git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git git shortlog 5f78f17a5b5518120eaa28021e76a267a3ad27d0.. -- drivers/net/igb depends also on followup fix 97a21d3ae6477ef00e39f21e47ce767a8ca1a22a x86: Avoid race condition in pci_enable_msix() seems worthwile to debian too, anyone against adding that backport? I have no specific objection. However, I thought that as a general rule we cherry-pick fixes and new hardware support rather than completely updating drivers. I'm aware that we've broken that rule for sfc and for DRM, but in those cases we have a commitment from upstream to support the backport. Can we get that for igb? Maks, what's the status? no time currently to clear upstream status. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100524032229.gc19...@baikonur.stro.at
Bug#580149: linux-image-2.6.32-trunk-amd64: usb - sata Sense not available
tags 580149 moreinfo stop On Fri, May 21, 2010 at 11:56:48AM +0200, formin...@t-online.hu wrote: More information. The usb mouse works fine on PCI USB 2.0 Host Controller Card (4-Ext, 1-Int. Ports) but the usb storage (DataTraveler), and the USB-SATA converter does not work. could you please try to reproduce on a recent 2.6.32 aka 2.6.32-13 from unstable, thanks. also is it fixed in 2.6.34 in experimental? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100521141533.gb13...@baikonur.stro.at
Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
On Fri, 21 May 2010, Andre Pawlowski wrote: Package: initramfs-tools Version: 0.94.4 Severity: important This bugreport was written with the initrd.img-2.6.32-trunk-amd64.bak before updating yesterday to initramfs-tools 0.94.4. I have an encrytped lvm which contains every partition except /boot. It was created by the Debian squeeze setup when I installed the system. Today I tried to boot the system with the new initramfs-tools and after I entered the password I get this message: kernel-provided name 'dm-0' and NAME='/mapper/sda2_crypt' disagree, please use SYMLINK+= or change the kernel to provide the proper name This bug appears after I upgraded libudev0 udev insserv groff-base initramfs-tools libglib2.0-0 libglib2.0-dev libglib2.0-data libgps19 libgudev-1.0-0 libjack0 libschroedinger-1.0-0 libwebkit-1.0-common libwebkit-1.0-2 xserver-xorg-video-intel xterm because I only changed the initrd.img and after that I could boot the system again I think it is a bug in initramfs-tools. no we dont set udev symlinks, so it is either a crytsetup or an udev bug. -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.32-trunk-amd64 root=/dev/mapper/handtuch--vg-root ro quiet -- /proc/filesystems ext4 fuseblk -- lsmod Module Size Used by nf_conntrack_ipv4 9817 2 nf_defrag_ipv4 1139 1 nf_conntrack_ipv4 xt_state1303 2 nf_conntrack 46359 2 nf_conntrack_ipv4,xt_state xt_tcpudp 2319 2 iptable_filter 2258 1 ip_tables 13899 1 iptable_filter x_tables 12813 3 xt_state,xt_tcpudp,ip_tables vboxnetadp 4225 0 vboxnetflt 9978 0 vboxdrv 1710854 2 vboxnetadp,vboxnetflt fuse 50078 1 loop 11767 0 firewire_sbp2 11450 0 snd_hda_codec_conexant21789 1 joydev 8411 0 snd_hda_intel 18147 0 arc41274 2 ecb 1841 2 snd_hda_codec 54212 2 snd_hda_codec_conexant,snd_hda_intel snd_hwdep 5364 1 snd_hda_codec snd_pcm_oss32399 0 snd_mixer_oss 12606 1 snd_pcm_oss iwlagn 71452 0 iwlcore77494 1 iwlagn snd_pcm60615 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi4208 0 snd_rawmidi15291 1 snd_seq_midi snd_seq_midi_event 4628 1 snd_seq_midi snd_seq42769 2 snd_seq_midi,snd_seq_midi_event mac80211 135407 2 iwlagn,iwlcore snd_timer 15502 2 snd_pcm,snd_seq pcmcia 19426 0 uvcvideo 51663 0 cfg80211 101253 3 iwlagn,iwlcore,mac80211 videodev 29977 1 uvcvideo thinkpad_acpi 50043 0 yenta_socket 19051 1 v4l1_compat11442 2 uvcvideo,videodev rsrc_nonstatic 7294 1 yenta_socket snd_seq_device 4477 3 snd_seq_midi,snd_rawmidi,snd_seq v4l2_compat_ioctl32 8538 1 videodev i2c_i8017766 0 rfkill 12996 2 cfg80211,thinkpad_acpi pcspkr 1699 0 pcmcia_core24054 3 pcmcia,yenta_socket,rsrc_nonstatic snd44718 11 snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device battery 4998 0 ac 2192 0 wmi 4307 0 psmouse49521 0 soundcore 4598 1 snd nvram 5061 1 thinkpad_acpi snd_page_alloc 6217 2 snd_hda_intel,snd_pcm evdev 7336 24 serio_raw 3752 0 processor 29479 2 ext4 285067 4 mbcache 4970 1 ext4 jbd2 66855 1 ext4 crc16 1319 1 ext4 sha256_generic 8692 2 cryptd 5366 0 aes_x86_64 7340 2 aes_generic25714 1 aes_x86_64 cbc 2539 1 dm_crypt 10507 1 dm_mod 53658 15 dm_crypt fan 3346 0 sg 18728 0 sr_mod 12602 0 sd_mod 29673 3 crc_t10dif 1276 1 sd_mod cdrom 29399 1 sr_mod uhci_hcd 18457 0 firewire_ohci 19452 0 ahci 31494 2 sdhci_pci 5565 0 sdhci 13966 1 sdhci_pci i915 247359 2 drm_kms_helper 18883 1 i915 libata131655 1 ahci ricoh_mmc 3069 0 mmc_core 45456 1 sdhci led_class 2401 3 iwlcore,thinkpad_acpi,sdhci firewire_core
Bug#577981: i have the same problem
On Wed, May 19, 2010 at 04:09:27PM +0100, Pedro R wrote: Hi, I just noticed this exact same problem with today's update of initramfs-tools. My USB audio card now loads before the internal, contrary to my /etc/modprobe.d/ settings. your modprobe config needs to end with .conf, upstream will soon ignore any that doesn't. BTW, should the USB audio drivers really be included in the most modules? I know most means the majority, but USB audio drivers? Doesn't make much sense to me. this is a separate story please reportbug it. never seen this. thank you. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519151145.gv13...@baikonur.stro.at
Bug#582177: initramfs-tools: fails to load ramdisk on boot
On Wed, May 19, 2010 at 08:20:30PM +0500, Aziz Sabirov wrote: I think I get similar problem here. My system (32-bit squeeze with /home on a separate partition on SD card) fails to recognize SD card partition on boot after upgrading to Initramfs-tools 0.94.4. please open a seperate bug report with properly submited info. using reportbug against initramfs-tools. also checkout out http://wiki.debian.org/InitramfsDebug above is useless as I miss the ability of remote diagnose thanks to crystall ball guessing. thank you. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519155144.gw13...@baikonur.stro.at
Bug#582177: initramfs-tools: fails to load ramdisk on boot; ... version downgrade
On Wed, May 19, 2010 at 10:36:10AM -0400, crop...@acm.org wrote: More information I downgraded the initramfs-tools back to version 93.4 and the problem is STILL PRESENT. sure, the initramfs won't be changed without telling so, so to have the effect of the downgrade one needs: update-initramfs -u Honestly, I don't know what to do... it would seem to be that my setup is tenuous at best and there is probably an instability in the boot process that I do not understand. Please advise... looked at both the initramfs and they look good. contain modules you'd wish they do. qemu can unpack and run it's stuff. well the left suspicion is the boot precaching biting your setup. what I would need is you to boot with rootdelay=12 or something and then see on the bootconsole what is wrong. is the raid running? check cat /proc/mdstat if not try to enable it with mdadm, is the crypto device there. currently I have not much info on where the failure happens. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519173853.gx13...@baikonur.stro.at
Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate
On Wed, May 19, 2010 at 11:56:34PM +0530, Ritesh Raj Sarraf wrote: On Tuesday 18 May 2010 11:21:10 Ritesh Raj Sarraf wrote: Hello Ben, On Sunday 16 May 2010 01:18:36 Ben Hutchings wrote: [29747.217066] iwlagn :03:00.0: Failed to allocate SKB buffer with GFP_ATOMIC. Only 1 free buffers remaining. [...] You are not testing the right kernel version. This error message was removed by the first patch Max applied. This is the log from syslog. The following kernel was used. May 14 12:09:42 champaran kernel: [0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-13) (f...@debian.org) (gcc version 4.3.2 (Deb ian 4.3.2-1.1) ) #1 SMP Sat May 8 22:47:58 CEST 2010 The recent upload of the same version of the package to unstable should cut all confusion. This one was built by Max. yep but without the iwlwifi patches, i have still to add f82a924cc88a5541df1d4b9d38a0968cd077a051 on top of the two patches. currently moving around so most likely will only happen next week. as the tests weren't conclusive the patches didn't get added to the uploaded linux-2.6. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519184052.gz13...@baikonur.stro.at
Bug#582177: initramfs-tools: fails to load ramdisk on boot; ... BOOT DEBUG DATA
On Wed, May 19, 2010 at 02:50:42PM -0400, crop...@acm.org wrote: Ok, more data... old school capture (pen and paper!) thanks a lot that made the picture much clearer. _ Preparations: 1) Reinstalled most recent initramfs-tools version 2) executed update-initramfs -c -k all 3) executed update-grub _ GRUB menu at boot: linux /vmlinuz-2.6.32-3-amd64 root=/dev/mapper/md1_crypt ro debug=vc rootdelay=12 echo Loading initial ramdisk initrd /initrd.img-2.6.32-3-amd64 _ Kernel output (LITERAL DATA, except for ... area below): [1.185516] rtc_cmos 00:0a: setting system clock to 2010-05-19 18:18:27 UTC (1274293107) [1.185628] Waiting 12sec before mounting root device [1.199432] input: AT translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 [12.992053] List of all partitions: [12.992128] No filesystem could mount root, tried: [12.992221] kernel panic - no syncing: VFS: unable to mount root fs on unknown wn-block(0,0) [12.992287] Pid: 1, comm: swapper Not tainted 2.6.32-3-amd64 #1 [12.992340] Call Trace: [12.992397] [812ed349] ? panic+0x86/0x141 ... ...... ... ...... [12.992880] [81011ba0] ? child_rip+0x0/0x20 aboves says that linux-2.6 is not getting the initramfs. thus indeed blaming GRUB seems the current state of affair. ___ Observations and opinions: This output format really has NOT changed in the days we have been messing with this problem. 1) the RAID is NOT starting 2) it never gets to the crypto (not started either) 3) no USB/firewire devices are detected (no evidence of drivers loading) 4) no block devices (Hard disks, CDROMs, etc) are detected (no evidence of drivers loading) indeed 1-4 can't happen if initramfs is not unpacked. strange that size seems not the issue: ls -lrt img-2.6.32-3-amd64.* -rw-r--r-- 1 maks maks 9458502 May 19 04:32 img-2.6.32-3-amd64.working -rw-r--r-- 1 maks maks 9665786 May 19 04:32 img-2.6.32-3-amd64.broken also qemu just unpacks fine the broken one and it's good for file too: file img-2.6.32-3-amd64.broken img-2.6.32-3-amd64.broken: gzip compressed data, from Unix, last modified: Wed May 19 01:49:38 2010 ___ Questions: 1) Could this be grub? 2) Could resynchronizing md0 fix this problem? I seem to remember doing something like this and the problem went away in March... :-/ 3) Any other suggestions? adding GRUB maintainers to Cc as this new bug report seems to be a recurring trend. #578473 seems to be duplicate of that one. GRUB maintainers can you advise? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519194956.ga13...@baikonur.stro.at
uploading 2.6.34
upload planed by tomorrow 12 UT. remaining issues, please speakup: * one last run through open config variables (will do later today) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100518133055.gb2...@stro.at
Bug#580660: linux-image-2.6.32-5-amd64: LVM volumes fail to detect on newer kernels
On Tue, May 18, 2010 at 09:41:03PM +0200, Frederik Vanrenterghem wrote: Same problem on my system. +++-===-===-== ii cryptsetup 2:1.1.0-2.1 configures encrypted block devices ii lvm22.02.62-1 The Linux Logical Volume Manager See also bug 576488. Let me know if I can provide more info? provide a new bugreport against initramfs-tools properly sent by reportbug. instead of following up to unrelated stuff, you seem to have cryptsetup installed, thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100518200728.gm13...@baikonur.stro.at
Bug#582177: initramfs-tools: fails to load ramdisk on boot; system with RAID CRYPTO; udev problems?
On Tue, May 18, 2010 at 05:29:17PM -0400, C. Cropper wrote: Package: initramfs-tools Version: 0.94.4 Severity: important Tags: squeeze Very recent changes to the initramfs-tools have caused my system to fail to load ramdisk at boot. I have to boot the system with the backup initrd image. I have checked with rootdelay=10--no change. The problem does not appear to be related to grub. When I boot the machine and watch the mass of kernel data fly by I get the impression that udev is not working or has somehow changed from mid-February till now (all of these problems first appeared in late Feb/early March of 2010). I am only using the squeeze dataset without items from experimental or other sources. My system is different from most in that my / partition is inside a luks crypto container which is then on a RAID 6 volume. The /boot is on an unencrypted RAID 1 volume. Each physical disk has a separate bios_grub partition (128k) and the partition tables are GPT. As I said before this above setup WORKS and I have a 6TB system where the boot disk can fail (I tested this) and the system comes back alive. For whatever reason, recent changes to initramfs-tools 1) make it not see the hard drives or any USB devices for that mater, 2) fails to start the RAID devices, and thus 3) the kernel panics at about 2secs into the boot sequence. Thank you for all your work. Squeeze really is shaping into a mighty force. C. Cropper thanks for your feedback, will need more data to see whats gone wrong. please post output of: sh -x mkinitramfs -v -o /tmp/foo dpkg -l cryptsetup and mount thank you and sorry. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100518214643.gp13...@baikonur.stro.at
Bug#582177: initramfs-tools: fails to load ramdisk on boot; DEBUG DATA ATTACHED
On Tue, May 18, 2010 at 08:39:02PM -0400, crop...@acm.org wrote: Data as requested. this looks good, please send me privately borked initramfs and working initramfs, so that I can compare. thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519004835.gr13...@baikonur.stro.at
Bug#582002: Modules not loading in the proper order (initramfs-tools: s390 architecture)
severity 582002 important stop On Mon, May 17, 2010 at 11:39:29AM -0400, Stephen Powell wrote: I run Debian testing (Squeeze) on the s390 architecture. I just performed an aptitude update and aptitude full-upgrade sequence, and among the updates was a new version of initramfs-tools: 0.94.4. (I noticed that Debian bug report 576603 was opened with a severity of serious with the apparent goal of keeping the package from migrating from Sid to Squeeze, and the bug has not been marked as resolved, nevertheless the package did migrate to Squeeze within the past few days.) The new package completely broke my system's ability to boot. Allow me to explain the boot mechanism that the old version successfully accomplished, and then explain how the new version fails. I have four different disks, one partition each, that are mounted on four different mount points, as follows: Device Mount Point 0200 / 0201 /boot 0202 /home 0203 swap I have a file called /etc/modprobe.d/dasd which contains the following statement: options dasd_mod dasd=0.0.0200(diag),0.0.0201,0.0.0202-0.0.0203(diag) you need give it a .conf ending then it ends up in initramfs. soon modprobe will not even look at your file without that ending. this special needs to be reverted due to stable - testing upgrade, but will reappear soon. This accomplishes two things: (1) it guarantees the correspondence of Linux devices names to s390 device numbers as follows: Device 0200 /dev/dasda 0201 /dev/dasdb 0202 /dev/dasdc 0203 /dev/dasdd and (2) it specifies the device driver used for each disk as follows: iam not familiar where this files comes from, so please feel free to reassign to whomever who created it. and/or maybe to release notes. thanks ps thanks for reminding me of 576603, will nuke that and get soonest latest git out. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100517171353.gh13...@baikonur.stro.at
Bug#582002: Modules not loading in the proper order (initramfs-tools: s390 architecture)
On Mon, May 17, 2010 at 12:33:15PM -0400, Stephen Powell wrote: Oops! I accidentally sent the e-mail prematurely. Allow me to continue ... and (2) it specifies the device driver used for each disk as follows: Device Device Name Driver -- - /dev/dasda dasd_diag_mod /dev/dasdb dasd_eckd_mod /dev/dasdc dasd_diag_mod /dev/dasdd dasd_diag_mod I run Debian GNU/Linux in a virtual machine under IBM's z/VM operating system, of course. Otherwise, the DIAG driver cannot be used. The way the module dependencies work, the modules must be loaded in the following order: (1) dasd_mod (no dependencies on another module) (2) dasd_diag_mod (dependency on dasd_mod) (3) dasd_eckd_mod or dasd_fba_mod (both have a dependency on dasd_mod) Although strictly speaking neither dasd_eckd_mod nor dasd_fba_mod have a dependency on dasd_diag_mod, nevertheless dasd_diag_mod must be loaded *before* either dasd_eckd_mod or dasd_fba_mod if a dasd of that type is to use the DIAG driver. you can use modprobe config here again see man modprobe.conf and the softdep line. To guarantee this I have the following lines in /etc/initramfs-tools/modules: dasd_mod dasd_diag_mod in that order. Neither dasd_eckd_mod nor dasd_fba_mod are listed here, since they are loaded as needed by the hot plug system (i.e. udev). I do not use sysconfig-hardware touch files (i.e. /etc/sysconfig/hardware/config-ccw-0.0.0200, /etc/sysconfig/hardware/config-ccw-0.0.0201, etc.), since I have had trouble in the past getting one of these devices varied offline dynamically if they are brought online at boot time via this method. Instead, I bring the devices online at boot time via the dasd option passed to the dasd_mod module via the /etc/modprobe.d/dasd file. All of this has been working flawlessly through a number of releases until now. All of a sudden, nothing works. The boot process times out waiting for the permanent root file system and drops me into an ash shell while the initial RAM filesystem is still mounted as /. I investigated and found that /etc/modprobe.d/dasd was not included in the initial RAM filesystem. That's a problem! Seeing that all other files that were included in /etc/modprobe.d had an extension of .conf, I renamed /etc/modprobe.d/dasd to /etc/modprobe.d/dasd.conf, rebuilt the initial RAM filesystem, re-ran zipl, and rebooted. This time it tried to bring the devices online but got errors of the form: dasd: 0.0.0200 Setting the DASD online failed because of missing DIAG discipline dasd: 0.0.0200: Setting the DASD online failed with rc=-19 0.0.0201 (/dev/dasdb) was the only device that it could get online. I knew immediately what was the cause of this: dasd_diag_mod was not loaded soon enough. By the time it dropped me into an ash shell, dasd_diag_mod was loaded, but at the time that dasd_eckd_mod was trying to bring the devices online, dasd_diag_mod was not loaded. The modules listed in /etc/initramfs-tools/modules must be loaded *before* udev is allowed to do its thing. The message udev: starting version 154 occurs in the log before Begin: Loading essential drivers ... done. it is necessary nowadays to have udev running when people put modules in there due to firmware requirements. thus you cannot rely on initramfs-tools second guessing module requirements anymore indeed. To further complicate matters, it appears that the entire /etc/initramfs-tools directory, including /etc/initramfs-tools/modules, is absent from the initial RAM filesystem. How would it even know what modules need to be loaded as essential drivers if this file is not present? no it is, just the location is a bit unusual conf/modules. A new kernel, linux-image-2.6.32-5-s390x, was also included in the upgrade; so perhaps this is part of the problem as well. Previously, I was using linux-image-2.6.32-3-s390x. that should be fine, but again i'm not a s390 porter, so not familiar with this specific case. anyway modprobe ordering seems the way to go. thanks -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100517173305.gi13...@baikonur.stro.at
Bug#582002: [SOLVED] Bug#582002: Modules not loading in the proper order (initramfs-tools: s390 architecture)
On Mon, May 17, 2010 at 02:17:54PM -0400, Stephen Powell wrote: On Mon, 17 May 2010 13:33:05 -0400 (EDT), Maximilian Attems wrote: you can use modprobe config here again see man modprobe.conf and the softdep line. That did the trick! I changed /etc/modprobe.d/dasd (now called /etc/modprobe.d/dasd.conf) as follows: options dasd_mod dasd=0.0.0200(diag),0.0.0201,0.0.0202-0.0.0203(diag) softdep dasd_eckd_mod pre: dasd_diag_mod softdep dasd_fba_mod pre: dasd_diag_mod cool, nice! :) I also removed the two lines from /etc/initramfs-tools/modules dasd_mod dasd_diag_mod since they are no longer needed. yep. I then rebuilt the initial RAM filesystem and re-ran the boot loader (zipl). It's working now! Thanks for your help. happy it boots. I'll leave this problem record open though, to remind you that files in /etc/modprobe.d which do not have an extension of .conf need to be re-enabled (at least for a while longer) to prevent migration problems. But my system is bootable again, now that I've made the changes indicated above. #577981 is open for the transition no point in having two bugs for that. unless you want to reassign this bug to debian installer or the package that created aboves modprobe file, i'd say it can be closed. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100517183159.gk13...@baikonur.stro.at
Bug#578007: initramfs-tools: no lvm in initramfs with 0.94.4
tags 578007 moreinfo stop is your /tmp noexec mounted? this bug report currently has zero information on what went wrong, please respond on the followup request to send the output of sh -x mkinitramfs -v -o /tmp/foo for initramfs-tools 0.94.4 thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100517185241.ga2...@stro.at
Bug#581377: initramfs-tools: Multipath does not load correctly at boot time
reassign 581377 initramfs-tools forcemerge 337176 581377 stop On Sat, May 15, 2010 at 06:24:12PM -0400, Steve Langasek wrote: an error like this: ... /lib64/multipath/libcheckdirectio.so cannot open shared object file Sorry, i didn't get the full message. It semms that multipath is expecting this file in /lib64/multipath but this file is located in /lib/multipath in the initrd-image. When i create a symbolic link in lib64 pointing to lib/multipath the initializing of the multipaths works. Almost certainly a bug in the multipath-tools package or its initramfs hook, not in initramfs-tools. Reassigning. this is a duplicate of #337176, badly reported. will be working on it now that initramfs is GPL and can steal the better dracut code in that area. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100518025116.gl13...@baikonur.stro.at
Re: uploading 2.6.32-13
On Sat, 15 May 2010, maximilian attems wrote: we have merged latest stable and the hpa fix, thus no point in delaying this anymore. HPA fixes evolved upstream, so upload gets delayed until further call till monday 12 UT. signature.asc Description: Digital signature
Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate
On Fri, May 14, 2010 at 09:15:37PM +0530, Ritesh Raj Sarraf wrote: thanks, not yet boot test, need to finish something. Triggered again after 2 suspend cycles. grr, can you repost the first appearance of it. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100514173050.ge13...@baikonur.stro.at
Bug#581527: closed by maximilian attems m...@stro.at (Re: Bug#581527: [linux-2.6] linux-image-2.6.32-5-686 hangs on boot)
On Fri, May 14, 2010 at 04:58:16PM +0200, Abou Al Montacir wrote: closing as user error not to accept the UUID change. newer template have Sorry, but I'm not sure I've understood this sentence, I did accept the UUID change, but the grub boot line still have root=/dev/hda1 how about providing that grub.cfg that wasn't updated and relevant files like fstab, please use reportbug to follow up on this: reportbug -N 581527 without this nothing can be done. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100514175626.gf13...@baikonur.stro.at
Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate
On Sat, May 15, 2010 at 12:05:19AM +0530, Ritesh Raj Sarraf wrote: On Friday 14 May 2010 23:00:51 maximilian attems wrote: On Fri, May 14, 2010 at 09:15:37PM +0530, Ritesh Raj Sarraf wrote: thanks, not yet boot test, need to finish something. Triggered again after 2 suspend cycles. grr, can you repost the first appearance of it. thanks I am not sure what you meant by the first appearance. I am attaching the full dmesg though. ok we need another foolowon fix. thanks for reposting, will build later today and ping you once built. afais my box is already more responsive with the Rx paged linux-2.6 and recovers somehow, so it is the important fix. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100514192102.gg13...@baikonur.stro.at
uploading 2.6.32-13
hello, we have merged latest stable and the hpa fix, thus no point in delaying this anymore. remaining issues: * release name (release naming should be handled this time by Ben) if you have any open issue please shout, will upload after 12 UT tomorrow on 15. May. thanks -- maks ps the ongoing iwlwifi saga is not a blocker this is usual business. pps nouveau boot trouble has not been debugged so doesn't qualify either. signature.asc Description: Digital signature
