Re: i386 biarch support for lenny
On Sun, Sep 02, 2007 at 11:50:29PM +0200, Matthias Klose wrote: Bastian Blank writes: | linux-image-2.6.18-5-amd64 | 2.6.18.dfsg.1-13 |stable | amd64, i386 Available in etch and newer. nice, are all the i386 buildds runnig this kernel? I doubt that any of the i386 buildds runs an amd64 kernel. Please ask [EMAIL PROTECTED] Bastian -- Women professionals do tend to over-compensate. -- Dr. Elizabeth Dehaver, Where No Man Has Gone Before, stardate 1312.9. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440654: linux-image-2.6.18-5-sparc64: fails to boot on SunFire v880: CPU Exception
Package: linux-image-2.6.18-5-sparc64 Version: 2.6.18.dfsg.1-13etch2 Severity: important Booting this kernel on a SunFire v880 results in a CPU exception: Remapping the kernel... done. Booting Linux... ERROR: CPU3 RED State Exception [..long output: see attached file..] This makes Etch uninstallable on v880 machines as this kernel is used by the installer. I've searched a bit on google, seems stripping the CPUs from the machine is a workaround, none I'm willing to go though. I've tried the latestest d-i with linux-image-2.6.21-2-sparc64, it neither runs into a CPU exception, nor does it boot at all. THe machine freezes after printing Booting Linux... Cheers, Bernd ERROR: CPU3 RED State Exception System State (CPU3 reporting) BBC Devices: ...000f... BBC Arb: ...000f...000f BBC Quiesce: ...0003...000c BBC WDogAct: ...0001...0001 BBC POR Gen: ...... BBC XIR Gen: ...... BBC POR Src: ...... BBC XIR Src: ...0007...000f BBC EBus TC: 014f.99fd.a7e6.3f29014f.99fd.a7e6.3f29 CPU0 Config/Control/Status registers: CPUVersion: 003e.0014.5400.0507 SafConfig: 0caa.01bc..8002 5:1 ID:0 HBM TOL:15 SafBaseAdr: .0400.. DispatchCtl: ...0009 MS SI DCacheCtl: .0200.. WE ECacheCtl: ..0009.4400 3:1 8MB mode=3-3-3 R/W-turn:2 ECC:on ErrorEnable: ...000b CEEN NCEEN UCEEN AFAR:... AFSR:... (no errors set) DMMU SFAR: ..fff7.90c8 DMMU SFSR: ..0080.8008 TM PR IMMU SFSR: ... (no status set) CPU0 Trap registers: Trap Level = 1 *TL=1 TT: ...0003 TSTATE: .0099.5800.1600 XCC:NC ICC:NC MM=TSO PEF PRIV IE TPC:..f004.fac0 TnPC: ..f004.fac4 TL=2 TT: ...0068 TSTATE: .0099.5804.1400 XCC:NC ICC:NC MM=TSO PEF PRIV TPC:..f004.a304 TnPC: ..f004.a308 TL=3 TT: ... TSTATE: ... XCC:(clear) ICC:(clear) MM=TSO TPC:... TnPC: ... TL=4 TT: ... TSTATE: ... XCC:(clear) ICC:(clear) MM=TSO TPC:... TnPC: ... TL=5 TT: ... TSTATE: ... XCC:(clear) ICC:(clear) MM=TSO TPC:... TnPC: ... CPU0 General registers: %PIL:15 %PC: ..f004.fac0 %nPC:..f004.fac4 %PSTATE: ...0035 MM=TSO AG %CCR:...0099 XCC:NC ICC:NC %FPRS: ...0005 FEF DL %v0: ... %v1: ...004a %v2: ... %v3: ..fff7.8000 %v4: ...10f0 %v5: 0caa.01bc..8002 %v6: ...007f %v7: ...0194 %m0: ... %m1: ...000d %m2: 8000.00b0.ffbf.80b6 %m3: ..fff7.8000 %m4: ..fff7.8000 %m5: .fffc.003f.e000 %m6: 8000.00b0.ffbe.a0b6 %m7: ...0001 %a0: ... %a1: .07ff.f000. %a2: .0200.. %a3: ..f018.5fb2 %a4: ... %a5: ... %a6: ..f000.dacc %a7: ..f001.fc4c %g0: ... %g1: ... %g2: ..f000. %g3: ..fff7.8000 %g4: ..0004.ff64 %g5: ..f004.fba4 %g6: ..fef7.27f8 %g7: ..fef7.1800 %o0: ..f000.00e0 %o1: ...0005 %o2: ...0004 %o3: ..f000.00e0 %o4: ...001f %o5: ... %o6: f000...c5f1 %o7: ..f000.dacc %l0: ..fef7. %l1: ...4020 %l2: ...0021 %l3: ...0011 %l4: ..f004.6e78 %l5: ... %l6: .07ff.fff8.0006 %l7: ..07ff.fed6 %i0: ... %i1: ... %i2: ... %i3: ... %i4: ... %i5: ... %i6: ... %i7: ... CPU0 Mem Ctrl registers: Mem Time Ctl1: 106e.9246.18a2.959a Mem Time Ctl2: 25c9.a82e.4a09.0020 Mem Time Ctl3: 1050.04c9.24a2.82d0 Mem Time Ctl4: 257d.382c.4a69.0020 Mem Addr Dec1: 8000.7e02.8002. Mem Addr Dec2: 8000.7e02.8002.0200 Mem Addr Dec3: 8000.7e02.8002.0400 Mem Addr Dec4: 8000.7e02.8002.0600 Mem Addr Ctl: 4904.1124.4221.1088 CPU1 Config/Control/Status registers: CPUVersion: 003e.0014.5400.0507 SafConfig: 0caa.01bc.0002.8002 5:1 ID:1 HBM TOL:15 SafBaseAdr:
Processed: Re: Bug#440676: nfs-kernel-server: Simultaneous transfer on mirrored nfs mounts causes service freezes
Processing commands for [EMAIL PROTECTED]: reassign 440676 linux-image-2.6.18-5-powerpc Bug#440676: nfs-kernel-server: Simultaneous transfer on mirrored nfs mounts causes service freezes Bug reassigned from package `nfs-kernel-server' to `linux-image-2.6.18-5-powerpc'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440694: initramfs-tools: hook-functions:dep_add_modules() breaks with /dev/md/x device names
Package: initramfs-tools
Version: 0.90a
Hello,
using a device name like /dev/md/0 or /dev/md/root as root device breaks
the creation of the intramfs-image because of an syntax error in the awk
script in dep_add_modules():
block=$(awk /^${root}/{print substr(\$5, 1, 3); exit} \
/proc/mdstat)
which then gets expanded to something like awk /^md/x/, which is, of
course, syntactically incorrect. A possible solution would be to escape
/-es in $root before... `root=${root//\//\\/}' should do the trick.
regards
Mario
--
I've never been certain whether the moral of the Icarus story should
only be, as is generally accepted, Don't try to fly too high, or
whether it might also be thought of as, Forget the wax and feathers
and do a better job on the wings.-- Stanley Kubrick
signature.asc
Description: Digital signature
Kernel sparc maintainer wanted
Hi folks The kernel team currently lacks a maintainer of the sparc port. There are now 2 RC bugs open which needs attention if sparc don't want to be dropped in the near future. Bastian -- But Captain -- the engines can't take this much longer! signature.asc Description: Digital signature
Processed: Re: Bug#440536: initramfs-tools: runaway modprobe loop: net-pf-1 and char-major-5-1
Processing commands for [EMAIL PROTECTED]: severity 440536 normal Bug#440536: initramfs-tools: runaway modprobe loop: net-pf-1 and char-major-5-1 Severity set to `normal' from `critical' tags 440536 moreinfo unreproducible Bug#440536: initramfs-tools: runaway modprobe loop: net-pf-1 and char-major-5-1 There were no tags set. Tags added: moreinfo, unreproducible stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433187: linux-2.6 - [sparc64-smp] produces unkillable processes
On Sat, Sep 01, 2007 at 05:18:52PM +0200, Bastian Blank wrote: On Sun, Jul 15, 2007 at 11:04:23AM +0200, Bastian Blank wrote: This problem exists up to 2.6.21 (and most likely also .22) and makes it mostly impossible to run a reliable buildd. Okay, further informations: The problem is somewhere in the robust_list implementation. If I disable the functions the kernels does not longer show this behaviour. As this code is generic, I expect a toolchain bug, but was not able to find anything. Bastian -- No one can guarantee the actions of another. -- Spock, Day of the Dove, stardate unknown signature.asc Description: Digital signature
Bug#440229: initramfs-tools: multipath-tools installation makes kenrel unbootable
severity 440229 normal reassign 440229 multipath-tools-initramfs stop On Fri, 31 Aug 2007, Ritesh Raj Sarraf wrote: Package: initramfs-tools Version: 0.90a Severity: grave Justification: renders package unusable first of all this severity is highly overrated! I found that post install of multipath-tools if an initrd image is updated, the kernel goes unbootable. On looking at the failure, it shows that the root device was held busy when in initrd's /init it tries to mount the device to /root The workaround was to remove multipath-tools and regenerate the initrd image. IIRC this bug was related to kpartx. I had seen this issue on my laptop and with the workaround have been able to avoid this bug. second initramfs-tools does _not_ shipp kpartx. third the hooks to add kpartx are in multipath-tools-initramfs thus reassigning. fourth you didn't paste the actual error message. thanks for your feedback, pls keep me on cc as i'm not related to multipath-tools-initramfs -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#440229: initramfs-tools: multipath-tools installation makes kenrel unbootable
Processing commands for [EMAIL PROTECTED]: severity 440229 normal Bug#440229: initramfs-tools: multipath-tools installation makes kenrel unbootable Severity set to `normal' from `grave' reassign 440229 multipath-tools-initramfs Bug#440229: initramfs-tools: multipath-tools installation makes kenrel unbootable Bug reassigned from package `initramfs-tools' to `multipath-tools-initramfs'. stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440536: initramfs-tools: runaway modprobe loop: net-pf-1 and char-major-5-1
severity 440536 normal tags 440536 moreinfo unreproducible stop On Sun, 02 Sep 2007, Paul Check wrote: Package: initramfs-tools Version: 0.85h Severity: critical Justification: breaks the whole system highly overrated, downgrading serverrity. Running kernel 2.6.16 on stable, root/boot on raid 1 on scsi devices, rest of system is lvm on raid 1 on same scsi devices. urrgs why are you using such an old kernel? Upgrading from initrd-tools to initramfs-tools results in the error message: runaway modprobe loop can you post more context no idea where this should happen. on boot, and then hangs (hence critical). The looping messages are modprobe for: net-pf-1 char-major-5-1 I used modules=list and put the same list of modules in the initramfs config file as are in my initrd config file. When I unpack the cpio archive I see that initramfs added the module unix to the list, which of course is alised to net-pf-1. Also, I have no idea what char-major-5-1 is. check the modprobe alias files ;) also this bugs pertains to module-init-tools, as initramfs-tools directly invoces modprobe. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440694: initramfs-tools: hook-functions:dep_add_modules() breaks with /dev/md/x device names
tags 440694 moreinfo
stop
[ please use reportbug in furture it adds important info ]
On Mon, 03 Sep 2007, Mario 'BitKoenig' Holbe wrote:
using a device name like /dev/md/0 or /dev/md/root as root device breaks
the creation of the intramfs-image because of an syntax error in the awk
script in dep_add_modules():
block=$(awk /^${root}/{print substr(\$5, 1, 3); exit} \
/proc/mdstat)
which then gets expanded to something like awk /^md/x/, which is, of
course, syntactically incorrect. A possible solution would be to escape
/-es in $root before... `root=${root//\//\\/}' should do the trick.
hmm that's partitioned md, or is this still the old devfs naming scheme?
please post output of
cat /proc/cmdline
sed 's/#.*$//;/^[[:space:]]*$/d' /etc/initramfs-tools/initramfs.conf
find /sys/block
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#440694: initramfs-tools: hook-functions:dep_add_modules() breaks with /dev/md/x device names
Processing commands for [EMAIL PROTECTED]: tags 440694 moreinfo Bug#440694: initramfs-tools: hook-functions:dep_add_modules() breaks with /dev/md/x device names There were no tags set. Tags added: moreinfo stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439397: initramfs-tools: split networking code into separate function
hello vagrant, On Fri, 24 Aug 2007, Vagrant Cascadian wrote: please consider the attached patch that splits the networking code from the nfs scripts into a separate function, which would allow other network boot methods to re-use it. live well, vagrant thanks for your patch, can you motivate it? what are other network boot methods? looks fine so far regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#440176: mkinitramfs: does not work properly with symlinked config files
Processing commands for [EMAIL PROTECTED]: severity 440176 normal Bug#440176: mkinitramfs: does not work properly with symlinked config files Severity set to `normal' from `important' # non standard setup stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440176: mkinitramfs: does not work properly with symlinked config files
severity 440176 normal # non standard setup stop On Thu, 30 Aug 2007, Sascha Silbe wrote: mkinitramfs (called by update-initramfs, called in postinst) does not work properly if the config files to be included in the initramfs are symlinks: [EMAIL PROTECTED]:~# mkinitramfs -o /boot/initrd.img-2.6.18-5-686 2.6.18-5-686 cpio: ./etc/udev/links.conf: No such file or directory cpio: ./etc/udev/udev.conf: No such file or directory cpio: ./etc/modprobe.d/arch/i386: No such file or directory cpio: ./etc/modprobe.d/blacklist: No such file or directory cpio: ./etc/modprobe.d/pnp-hotplug: No such file or directory cpio: ./etc/modprobe.d/aliases: No such file or directory cpio: ./etc/modprobe.d/display_class: No such file or directory cpio: ./etc/modprobe.d/arch-aliases: No such file or directory [EMAIL PROTECTED]:~# ls -l /etc/udev/links.conf lrwxrwxrwx 1 root root 35 2007-08-30 14:25 /etc/udev/links.conf - ../infra/system-1.0/udev/links.conf [EMAIL PROTECTED]:~# ls -l /etc/infra/system-1.0/udev/links.conf -rw-r--r-- 1 root root 430 2007-03-23 16:30 /etc/infra/system-1.0/udev/links.conf strace shows that cpio is already called with --dereference. Since I didn't find anything about udev in /usr/sbin/mkinitramfs, I don't know how to proceed further to fix this bug. the trouble you point too lies in symlinking your hole etc :P any cp -a invokation will break, you have to switch those to cp -Lpr, there is one invocation in mkinitramfs itself and the other is in the udev hook. i find this an highly questionable usage and will wait for input from others before deciding on it. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: update-initramfs, chroots ro /boot, and debian-live (Re: d-l and /boot ro)
On Tue, 28 Aug 2007, Justin Pryzby wrote: On Tue, Aug 28, 2007 at 09:13:00PM +0200, Daniel Baumann wrote: Justin Pryzby wrote: Check update-initramfs, which reads from proc/mounts, which makes the scripts not completely hostfs agnostic. ummm.. bad one that, thanks for pointing it out. someone has a good idea about that? actually, at the time where update-initramfs is run, we should not mount /proc, but that's going to be a bit nasty to mount/unmount it just before and after lh_chroot_hacks. well update-initramfs checks if there is a readable /proc/mounts, so if /proc is !mounted everything si fine. initramfs people, see thread starting at: http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-August/002075.html hope aboves helps, regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: update-initramfs, chroots ro /boot, and debian-live (Re: d-l and /boot ro)
On Mon, Sep 03, 2007 at 08:57:41PM +0200, Daniel Baumann wrote: maximilian attems wrote: well update-initramfs checks if there is a readable /proc/mounts, so if /proc is !mounted everything si fine. that's what i stated.. but it's ugly to mount, do stuff, unmount, update initramfs, mount, do stuff, and unmount again. it would be, probably, better if update-initramfs could handle read-only /boot. Unfortunately the problem is that it *does* handle ro boot, as a special case (and not chroot). Perhaps it should also test `stat -c '%i' /boot` = `stat -c '%i' /proc/1/root/boot` or some such other chroot indicator. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: update-initramfs, chroots ro /boot, and debian-live (Re: d-l and /boot ro)
On Mon, Sep 03, 2007 at 08:57:41PM +0200, Daniel Baumann wrote: maximilian attems wrote: well update-initramfs checks if there is a readable /proc/mounts, so if /proc is !mounted everything si fine. that's what i stated.. but it's ugly to mount, do stuff, unmount, update initramfs, mount, do stuff, and unmount again. sorry i don't get you, please explain what you need. it would be, probably, better if update-initramfs could handle read-only /boot. it does. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440694: initramfs-tools: hook-functions:dep_add_modules() breaks with /dev/md/x device names
On Mon, Sep 03, 2007 at 08:44:10PM +0200, maximilian attems wrote: [ please use reportbug in furture it adds important info ] ...and add python to my system... grrr :) On Mon, 03 Sep 2007, Mario 'BitKoenig' Holbe wrote: using a device name like /dev/md/0 or /dev/md/root as root device breaks hmm that's partitioned md, or is this still the old devfs naming scheme? Well... mdadm knows two 'standard' naming schemes /dev/mdNN and /dev/md/NN for non-partitioned arrays - probably the latter from devfs times, yes - and /dev/md_dNN and /dev/md/dNN for 2.6 partitioned arrays. Furthermore, mdadm adds some auto functionality which is expected to be used to create device entries with more meaningful names like /dev/md/root. In this case it was a non-partitioned raid which i just tried to name more meaningful. I tried both - first to rename my array to /dev/md/root and since this didn't work I went a step back and tried to name it /dev/md/0 which didn't work as well. please post output of cat /proc/cmdline sed 's/#.*$//;/^[[:space:]]*$/d' /etc/initramfs-tools/initramfs.conf find /sys/block Would not help you, since I reverted the changes to get back a bootable system :) Kernel command line would most likely have contained something like root=97F (lilo), initramfs.conf is unmodified: [EMAIL PROTECTED]:/home/holbe% md5sum /etc/initramfs-tools/initramfs.conf b155f3c78e63f9779ccf77ff77fcbb5d /etc/initramfs-tools/initramfs.conf [EMAIL PROTECTED]:/home/holbe% grep /etc/initramfs-tools/initramfs.conf /var/lib/dpkg/status /etc/initramfs-tools/initramfs.conf b155f3c78e63f9779ccf77ff77fcbb5d [EMAIL PROTECTED]:/home/holbe% and /sys/block would most likely have contained something like a md127 directory, would the system have booted :) Mario -- delta talk softly and carry a keen sword signature.asc Description: Digital signature
Re: update-initramfs, chroots ro /boot, and debian-live (Re: d-l and /boot ro)
On Mon, Sep 03, 2007 at 03:28:00PM -0400, Justin Pryzby wrote: On Mon, Sep 03, 2007 at 08:57:41PM +0200, Daniel Baumann wrote: maximilian attems wrote: well update-initramfs checks if there is a readable /proc/mounts, so if /proc is !mounted everything si fine. that's what i stated.. but it's ugly to mount, do stuff, unmount, update initramfs, mount, do stuff, and unmount again. it would be, probably, better if update-initramfs could handle read-only /boot. Unfortunately the problem is that it *does* handle ro boot, as a special case (and not chroot). Perhaps it should also test `stat -c '%i' /boot` = `stat -c '%i' /proc/1/root/boot` or some such other chroot indicator. so could you reexplain what your request is, cool thanks. i'll try to rephrase you have chroot where /proc is mounted, where the exterior /boot is ro. thus no initramfs is generated inside of the chroot? why is proc mounted? but maybe i don't get it as daniel was speaking of having to mount.. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433187: linux-2.6 - [sparc64-smp] produces unkillable processes
Hi, #433187 is the bug that has killed the buildds on lebrun and spontini, right? -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel sparc maintainer wanted
On Mon, Sep 03, 2007 at 08:32:34PM +0200, Bastian Blank wrote: Hi folks The kernel team currently lacks a maintainer of the sparc port. There are now 2 RC bugs open which needs attention if sparc don't want to be dropped in the near future. I'll try to help with that. I have an ultra 10 machine that I can use for testing. However, I'll need someone who could help me when I get stuck. Bastian -- But Captain -- the engines can't take this much longer! Best Regards, Aníbal Monsalve Salazar -- http://v7w.com/anibal signature.asc Description: Digital signature
Bug#440536: initramfs-tools: runaway modprobe loop: net-pf-1 and char-major-5-1
severity 440536 normal tags 440536 moreinfo unreproducible stop On Sun, 02 Sep 2007, Paul Check wrote: Package: initramfs-tools Version: 0.85h Severity: critical Justification: breaks the whole system highly overrated, downgrading serverrity. How is it overrated to say critical when it breaks a system? Perhaps it isn't a bug at all, and it's my own error in terms of setup. But, if it is a bug, it's rather critical that you can no longer boot a system. Running kernel 2.6.16 on stable, root/boot on raid 1 on scsi devices, rest of system is lvm on raid 1 on same scsi devices. urrgs why are you using such an old kernel? So, are you saying that this behavior will go away when I upgrade? Somehow I doubt that, but I will try. I was waiting to upgrade the kernel when I moved from stable to unstable, and I was waiting to do the latter change after I get mkinitramfs working. Upgrading from initrd-tools to initramfs-tools results in the error message: runaway modprobe loop can you post more context no idea where this should happen. More context? Ok, I re-boot my computer. Some crytographic routines print messages and then the runaway modprobe loop messages print. It's very, very early in the boot process. Is there any more information I can provide wrt the context? If there is anything you'd like me to transcribe the next time I do this break, then I will do so. on boot, and then hangs (hence critical). The looping messages are modprobe for: net-pf-1 char-major-5-1 I used modules=list and put the same list of modules in the initramfs config file as are in my initrd config file. When I unpack the cpio archive I see that initramfs added the module unix to the list, which of course is alised to net-pf-1. Also, I have no idea what char-major-5-1 is. check the modprobe alias files ;) Ummm..I did, and I don't see it referenced anywhere. Should it be? Perhaps that is my problem?? Ok... also this bugs pertains to module-init-tools, as initramfs-tools directly invoces modprobe. [cont'd]...if that is the case then I agree with the comment just above! However, a google search for char-major-5-1 results in only 4 hits, and I couldn't see what it referenced there. It seems a little early to definitively say this is a problem with module-init-tools, since initrd-tools has no problem but initramfs-tools does. --Paul Thanks, Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433187: linux-2.6 - [sparc64-smp] produces unkillable processes
Hi, On Tue Sep 04, 2007 at 00:09:53 +0200, Josip Rodin wrote: Hi, #433187 is the bug that has killed the buildds on lebrun and spontini, right? AIUC, yes. at least i can reproduce that on my buildd. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: update-initramfs, chroots ro /boot, and debian-live (Re: d-l and /boot ro)
On Mon, Sep 03, 2007 at 10:36:56PM +0200, maximilian attems wrote: On Mon, Sep 03, 2007 at 03:28:00PM -0400, Justin Pryzby wrote: On Mon, Sep 03, 2007 at 08:57:41PM +0200, Daniel Baumann wrote: maximilian attems wrote: well update-initramfs checks if there is a readable /proc/mounts, so if /proc is !mounted everything si fine. that's what i stated.. but it's ugly to mount, do stuff, unmount, update initramfs, mount, do stuff, and unmount again. it would be, probably, better if update-initramfs could handle read-only /boot. Unfortunately the problem is that it *does* handle ro boot, as a special case (and not chroot). Perhaps it should also test `stat -c '%i' /boot` = `stat -c '%i' /proc/1/root/boot` or some such other chroot indicator. so could you reexplain what your request is, cool thanks. I'm wondering whether initramfs should have some more checks before exiting without doing anything. In particular whether it should check for a chroot. I'm not sure either way, but I think I agree with Daniel it would be a kludge to solve this within debian-live. It would be something like: . unmounting and remounting proc and manually rather than automatically calling update-initramfs (since otherwise dpkg and who knows what else will be run without /proc); or, . trying to hide from initramfs that the external /boot is ro. i'll try to rephrase you have chroot where /proc is mounted, where the exterior /boot is ro. thus no initramfs is generated inside of the chroot? Right. The readonly boot is specific to me (but could happen anywhere). The chroot with mounted /proc is normal debian-live build process. why is proc mounted? For the same reason it has to be mounted outside the chroot: things fail in obscure ways when it isn't. Within the chroot dpkg runs maintainer scripts which run next to everything. Here, IIRC, update-initramfs is being run by a kernel installation. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel sparc maintainer wanted
Hi, Just for clarity, is the call for help for sparc or sparc 64, or both? Thanks, Chris. On 03/09/07, Aníbal Monsalve Salazar [EMAIL PROTECTED] wrote: On Mon, Sep 03, 2007 at 08:32:34PM +0200, Bastian Blank wrote: Hi folks The kernel team currently lacks a maintainer of the sparc port. There are now 2 RC bugs open which needs attention if sparc don't want to be dropped in the near future. I'll try to help with that. I have an ultra 10 machine that I can use for testing. However, I'll need someone who could help me when I get stuck. Bastian -- But Captain -- the engines can't take this much longer! Best Regards, Aníbal Monsalve Salazar -- http://v7w.com/anibal -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG3I53gY5NIXPNpFURAmOYAJ961bosA+jD4nUr6dj/Df+ZWfpjeACeK5Sh 963SiAl7JyoHadaawogXcG8= =lv0w -END PGP SIGNATURE-
Bug#440749: linux-image-2.6.18-5-amd64: install fails mkinitramfs-kpkg failed to create initrd image
Package: linux-image-2.6.18-5-amd64 Version: 2.6.18.dfsg.1-13etch2 Severity: grave Justification: renders package unusable Attempting to install linux-image-2.6.18-5-amd64, as per the sarge security advisory Output follows: # apt-get install linux-image-2.6-amd64 linux-doc-2.6.18 Reading package lists... Done Building dependency tree... Done The following extra packages will be installed: linux-image-2.6.18-5-amd64 The following NEW packages will be installed: linux-doc-2.6.18 linux-image-2.6.18-5-amd64 The following packages will be upgraded: linux-image-2.6-amd64 1 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Preconfiguring packages ... Selecting previously deselected package linux-image-2.6.18-5-amd64. (Reading database ... 181917 files and directories currently installed.) Unpacking linux-image-2.6.18-5-amd64 (from .../linux-image-2.6.18-5-amd64_2.6.18.dfsg.1-13etch2_amd64.deb) ... Done. Selecting previously deselected package linux-doc-2.6.18. Unpacking linux-doc-2.6.18 (from .../linux-doc-2.6.18_2.6.18.dfsg.1-13etch2_all.deb) ... Preparing to replace linux-image-2.6-amd64 2.6.18+6 (using .../linux-image-2.6-amd64_2.6.18+6etch2_amd64.deb) ... Unpacking replacement linux-image-2.6-amd64 ... Setting up linux-image-2.6.18-5-amd64 (2.6.18.dfsg.1-13etch2) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-5-amd64/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-5-amd64/source Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. gzip: stdout: No space left on device mkinitramfs-kpkg failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.18-5-amd64 (--configure): subprocess post-installation script returned error exit status 9 Setting up linux-doc-2.6.18 (2.6.18.dfsg.1-13etch2) ... dpkg: dependency problems prevent configuration of linux-image-2.6-amd64: linux-image-2.6-amd64 depends on linux-image-2.6.18-5-amd64; however: Package linux-image-2.6.18-5-amd64 is not configured yet. dpkg: error processing linux-image-2.6-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.18-5-amd64 linux-image-2.6-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (900, 'stable'), (500, 'stable'), (20, 'testing'), (10, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-5-amd64 depends on: ii coreutil 5.97-5.3The GNU core utilities ii debconf 1.5.11 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib ii initramf 0.85h tools for generating an initramfs ii module-i 3.3-pre4-2 tools for managing Linux kernel mo linux-image-2.6.18-5-amd64 recommends no packages. -- debconf information: linux-image-2.6.18-5-amd64/postinst/create-kimage-link-2.6.18-5-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-5-amd64/postinst/old-system-map-link-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/initrd-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/preinst/elilo-initrd-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/postinst/depmod-error-2.6.18-5-amd64: false linux-image-2.6.18-5-amd64/preinst/bootloader-initrd-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/already-running-this-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/prerm/removing-running-kernel-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/lilo-initrd-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/abort-overwrite-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/preinst/failed-to-move-modules-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/prerm/would-invalidate-boot-loader-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/postinst/bootloader-error-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/postinst/old-initrd-link-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/overwriting-modules-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/postinst/old-dir-initrd-link-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.18-5-amd64/postinst/depmod-error-initrd-2.6.18-5-amd64: false linux-image-2.6.18-5-amd64/postinst/bootloader-test-error-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/postinst/kimage-is-a-directory: linux-image-2.6.18-5-amd64/preinst/abort-install-2.6.18-5-amd64: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440749: marked as done (linux-image-2.6.18-5-amd64: install fails mkinitramfs-kpkg failed to create initrd image)
Your message dated Tue, 4 Sep 2007 02:47:24 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#440749: linux-image-2.6.18-5-amd64: install fails mkinitramfs-kpkg failed to create initrd image has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.18-5-amd64 Version: 2.6.18.dfsg.1-13etch2 Severity: grave Justification: renders package unusable Attempting to install linux-image-2.6.18-5-amd64, as per the sarge security advisory Output follows: # apt-get install linux-image-2.6-amd64 linux-doc-2.6.18 Reading package lists... Done Building dependency tree... Done The following extra packages will be installed: linux-image-2.6.18-5-amd64 The following NEW packages will be installed: linux-doc-2.6.18 linux-image-2.6.18-5-amd64 The following packages will be upgraded: linux-image-2.6-amd64 1 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Preconfiguring packages ... Selecting previously deselected package linux-image-2.6.18-5-amd64. (Reading database ... 181917 files and directories currently installed.) Unpacking linux-image-2.6.18-5-amd64 (from .../linux-image-2.6.18-5-amd64_2.6.18.dfsg.1-13etch2_amd64.deb) ... Done. Selecting previously deselected package linux-doc-2.6.18. Unpacking linux-doc-2.6.18 (from .../linux-doc-2.6.18_2.6.18.dfsg.1-13etch2_all.deb) ... Preparing to replace linux-image-2.6-amd64 2.6.18+6 (using .../linux-image-2.6-amd64_2.6.18+6etch2_amd64.deb) ... Unpacking replacement linux-image-2.6-amd64 ... Setting up linux-image-2.6.18-5-amd64 (2.6.18.dfsg.1-13etch2) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-5-amd64/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-5-amd64/source Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. gzip: stdout: No space left on device mkinitramfs-kpkg failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.18-5-amd64 (--configure): subprocess post-installation script returned error exit status 9 Setting up linux-doc-2.6.18 (2.6.18.dfsg.1-13etch2) ... dpkg: dependency problems prevent configuration of linux-image-2.6-amd64: linux-image-2.6-amd64 depends on linux-image-2.6.18-5-amd64; however: Package linux-image-2.6.18-5-amd64 is not configured yet. dpkg: error processing linux-image-2.6-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.18-5-amd64 linux-image-2.6-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (900, 'stable'), (500, 'stable'), (20, 'testing'), (10, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-5-amd64 depends on: ii coreutil 5.97-5.3The GNU core utilities ii debconf 1.5.11 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib ii initramf 0.85h tools for generating an initramfs ii module-i 3.3-pre4-2 tools for managing Linux kernel mo linux-image-2.6.18-5-amd64 recommends no packages. -- debconf information: linux-image-2.6.18-5-amd64/postinst/create-kimage-link-2.6.18-5-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-5-amd64/postinst/old-system-map-link-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/initrd-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/preinst/elilo-initrd-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/postinst/depmod-error-2.6.18-5-amd64: false linux-image-2.6.18-5-amd64/preinst/bootloader-initrd-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/already-running-this-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/prerm/removing-running-kernel-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/lilo-initrd-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/preinst/abort-overwrite-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/preinst/failed-to-move-modules-2.6.18-5-amd64: linux-image-2.6.18-5-amd64/prerm/would-invalidate-boot-loader-2.6.18-5-amd64: true linux-image-2.6.18-5-amd64/postinst/bootloader-error-2.6.18-5-amd64:
Bug#439397: initramfs-tools: split networking code into separate function
On Mon, Sep 03, 2007 at 08:59:58PM +0200, maximilian attems wrote: On Fri, 24 Aug 2007, Vagrant Cascadian wrote: please consider the attached patch that splits the networking code from the nfs scripts into a separate function, which would allow other network boot methods to re-use it. thanks for your patch, can you motivate it? not sure what you mean by motivate ... ? what are other network boot methods? ltsp in ubuntu started using NBD+unionfs+squashfs instead of NFS, and debian-live uses has a network boot methods using cifs in addition to a different way of using NFS (i think it also uses unionfs and maybe squashfs, not just a plain NFS/cifs mount)... so splitting out the networking related code into a separate function would move towards not having forked code for all of these different network boot methods. at least, that's my hope. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433187: linux-2.6 - [sparc64-smp] produces unkillable processes
Martin Zobel-Helas wrote: Hi, On Tue Sep 04, 2007 at 00:09:53 +0200, Josip Rodin wrote: Hi, #433187 is the bug that has killed the buildds on lebrun and spontini, right? AIUC, yes. at least i can reproduce that on my buildd. Greetings Martin Hi guys, We (David Miller and I) are already working on this. We finally got some info dump from a debugging patched kernel and I expect we will have a fix within the next 3/4 weeks. From our first look it seems like a futex bug and some users have reported that the latest 2.6.23-rcX do not show this behavior. Clearly we also want to figure out a fix for .22. Fabio -- I'm going to make him an offer he can't refuse. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-modules-extra-2.6_2.6.22-1_i386.changes
linux-modules-extra-2.6_2.6.22-1_i386.changes uploaded successfully to localhost along with the files: linux-modules-extra-2.6_2.6.22-1.dsc linux-modules-extra-2.6_2.6.22-1.tar.gz aufs-modules-2.6.22-2-486_2.6.22+0+20070806-1_i386.deb aufs-modules-2.6-486_2.6.22-1_i386.deb gspca-modules-2.6.22-2-486_2.6.22+01.00.18-1_i386.deb gspca-modules-2.6-486_2.6.22-1_i386.deb squashfs-modules-2.6.22-2-486_2.6.22+3.2r2-1_i386.deb squashfs-modules-2.6-486_2.6.22-1_i386.deb aufs-modules-2.6.22-2-686_2.6.22+0+20070806-1_i386.deb aufs-modules-2.6-686_2.6.22-1_i386.deb gspca-modules-2.6.22-2-686_2.6.22+01.00.18-1_i386.deb gspca-modules-2.6-686_2.6.22-1_i386.deb squashfs-modules-2.6.22-2-686_2.6.22+3.2r2-1_i386.deb squashfs-modules-2.6-686_2.6.22-1_i386.deb aufs-modules-2.6.22-2-k7_2.6.22+0+20070806-1_i386.deb aufs-modules-2.6-k7_2.6.22-1_i386.deb gspca-modules-2.6.22-2-k7_2.6.22+01.00.18-1_i386.deb gspca-modules-2.6-k7_2.6.22-1_i386.deb squashfs-modules-2.6.22-2-k7_2.6.22+3.2r2-1_i386.deb squashfs-modules-2.6-k7_2.6.22-1_i386.deb aufs-modules-2.6.22-2-686-bigmem_2.6.22+0+20070806-1_i386.deb aufs-modules-2.6-686-bigmem_2.6.22-1_i386.deb gspca-modules-2.6.22-2-686-bigmem_2.6.22+01.00.18-1_i386.deb gspca-modules-2.6-686-bigmem_2.6.22-1_i386.deb squashfs-modules-2.6.22-2-686-bigmem_2.6.22+3.2r2-1_i386.deb squashfs-modules-2.6-686-bigmem_2.6.22-1_i386.deb aufs-modules-2.6.22-2-amd64_2.6.22+0+20070806-1_i386.deb aufs-modules-2.6-amd64_2.6.22-1_i386.deb gspca-modules-2.6.22-2-amd64_2.6.22+01.00.18-1_i386.deb gspca-modules-2.6-amd64_2.6.22-1_i386.deb squashfs-modules-2.6.22-2-amd64_2.6.22+3.2r2-1_i386.deb squashfs-modules-2.6-amd64_2.6.22-1_i386.deb aufs-modules-2.6.22-2-vserver-686_2.6.22+0+20070806-1_i386.deb aufs-modules-2.6-vserver-686_2.6.22-1_i386.deb gspca-modules-2.6.22-2-vserver-686_2.6.22+01.00.18-1_i386.deb gspca-modules-2.6-vserver-686_2.6.22-1_i386.deb squashfs-modules-2.6.22-2-vserver-686_2.6.22+3.2r2-1_i386.deb squashfs-modules-2.6-vserver-686_2.6.22-1_i386.deb aufs-modules-2.6.22-2-vserver-k7_2.6.22+0+20070806-1_i386.deb aufs-modules-2.6-vserver-k7_2.6.22-1_i386.deb gspca-modules-2.6.22-2-vserver-k7_2.6.22+01.00.18-1_i386.deb gspca-modules-2.6-vserver-k7_2.6.22-1_i386.deb squashfs-modules-2.6.22-2-vserver-k7_2.6.22+3.2r2-1_i386.deb squashfs-modules-2.6-vserver-k7_2.6.22-1_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
