Bug#680168: sparc install bug report
Package: installation-reports Boot method: network Image version: http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-sparc/current/images/netboot/boot.img Date: 07.04.2012 03:50am et Machine: Sun Netra X1 Processor: UltraSPARC-IIe 400MHz Memory: 768MB Partitions: best i've got is: http://jeremy.kister.net/tmp/debpart.txt Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[E] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[E] Comments/Problems: system hangs while Receiving Packages right after confirming partition table. sending break and then 'go' shows: [ 2919.327720] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oo tried multiple machines, all error. in a similar way. Only difference was once right after confirming the partition table, the system hung before Receiving Packages and after hitting enter a few times i saw: Segmentation Fault -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff3f9eb.6080...@jeremykister.com
Re: netinstall via PXE
Dear Samuel, Samuel Thibault schrieb: Hello, Ulrich Krause, le Thu 03 May 2012 12:08:22 +0200, a écrit : The line in /etc/dhcp3/dhcp.conf regarding the filename should read ' filename pxelinux.0;' (instead of ' filename /pxelinux.0;' It seems it was already fixed in another place. I don't see why '/' should be needed, my tests show it is not, so I have removed it. Uncompressing netboot/netboot.tar.gz into the tftp boot image directory leaves pxelinux.cfg as a link to the directory debian-installer/i386/pxelinux.cfg. Setting this link to debian-installer/i386/pxelinux.cfg/default resolves the directory error of PXE, but doesn't start the installation. This is only achieved by copying the configuration file debian-installer/i386/boot-screens/syslinux.cfg to pxelinux.cfg/ip-address-in-hex-with-uppercase-letters. In my example the client-IP was 192.168.1.2, so the files name had to be C0A80102. This did the trick ! But that's not supposed to be needed, that's odd. See pxelinux.txt documentation, pxelinux.cfg is really supposed to be a directory, containing various possibilities, including default, which is what we provide since that's independent from any hardware. Since we provide pxelinux.0 ourself, that's really how things are supposed to happen. Where did you take your netboot.tar.gz? Samuel I am not a computer expert. I just followed the instructions after downloading the files (Debian mirror at ftp.halifax.rwth-aachen.de). The instructions didn't work for me, so I searched the web for hints. The ip-address-in-hex-with-uppercase-letters did it. Unfortunately I don't recall which other small changes (/ or not) I did previously in which order. I just thought that a footnote indicating that for some equipment the HEX filname might work could save other peoples time. Thank you for getting back to me ! Ulrich attachment: ulrich_krause.vcf
Re: netinstall via PXE
Ulrich Krause, le Wed 04 Jul 2012 09:43:08 +0200, a écrit : I just followed the instructions after downloading the files (Debian mirror at ftp.halifax.rwth-aachen.de). Where exactly? I just thought that a footnote indicating that for some equipment the HEX filname might work could save other peoples time. The thing is: AIUI, it does *not* depend on the equipment, since it is pxelinux itself which is supposed to look for default (and it does in my tests). Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120704110046.gf25...@type.lan
No disk found (C602 chipset)
Hi, I was trying to install Debian on a new Lenovo S30 system. I downloaded the file http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso (label: Debian GNU/Linux testing Wheezy - Official Snapshot amd64 NETINST Binary-1 20120704-09:15) and started the installer from the CD. Unfortunately, it was unable to detect any drives. I did some searching, and found that it seems to not contain the right drivers for the SAS controller of my system. lspci -v shows 05:00.0 Serial Attached SCSSI controller: Intel Corporation C602 chipset 4-Port SATA Storage Control Unit (rev 06). When running from a Knoppix CD, I got some line saying 'Kernel driver in use: isci'. I do not see that line when running the Debian installer. For reference, lspci -n shows '05:00.0 0107: 8086:1d6b (rev 06)'. It seems to me that the installer doesn't contain or is unable to load the isci driver. Is this a known problem? Should I send this in as a bug report? At the same time, does anyone here know of a fix I might try? I'd really like to start using this computer... Best, Koen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/225994ae07215f82fb47c5e899cd0...@vermeer.tv
Bug#679377: Segmentation fault when initramfs is booting
tags 679377 + moreinfo thanks On 28.06.2012 13:14, Jordi Pujol wrote: Package: busybox Version: 1:1.20.0-4 Severity: important the patch shell-ash-export-HOME.patch causes a segmentation fault when initramfs boots, I believe that this fault occurs the first time that initramfs looks for some executable in the initramfs filesystem, Does whole thing actually work? Why do you think it is this patch which causes the SIGSEGV? The change in this patch is quite, well, innocent, it does not look like it can be a cause for any such issues. Can you describe your initramfs/environment a bit? Maybe give me access to your initramfs for testing? Also, the latest release of busybox, 1.20.1 is a bit different of that, and Different of what, exactly? The version of busybox you're filing bugreport against is actually 1.20.1, so there are two questions actually: what is different, and different between what and what? -- since you're comparing the same thing with itself. more upstream stable patches have been added. A new release can be packaged containing this changes, The only upstream change not included in debian package is busybox-1.20.1-mke2fs.patch, which is only relevant for busybox-static since other variants don't enable mkfs. Modifying this, busybox works fine, http://livenet.selfip.com/ftp/debian/package- modifications/busybox_1.20.1-1.lnet1.debian.tar.gz Now that's fantastic. Let's see. diff -u -p -r debian/patches/series lnet/patches/series --- 1.20.0-4/patches/series 2012-06-12 22:04:46.0 +0400 +++ lnet1/patches/series2012-06-22 19:15:34.0 +0400 @@ -1,6 +1,4 @@ -1.20.1.patch - -shell-ash-export-HOME.patch +#shell-ash-export-HOME.patch # we need to get rid of this one: #applets-fallback.patch version.patch @@ -11,10 +9,12 @@ u-mount-FreeBSD-support.patch swaponoff-FreeBSD-support.patch # FTBFS on non-linux -ps-get-uptime.patch +#ps-get-uptime.patch # upstream stable patches busybox-1.20.1-ash.patch busybox-1.20.1-ifupdown.patch busybox-1.20.1-man.patch +busybox-1.20.1-mke2fs.patch +busybox-1.20.1-ps.patch busybox-1.20.1-tar.patch So you reverted all fixes which went into 1.20.1 bugfix release, you reverted my ps-get-uptime.patch but added busybox-1.20.1-ps.patch (it has exactly the same content), added busybox-1.20.1-mke2fs.patch (which is not relevant for the issue in question), and reverted shell-ash-export-HOME.patch which looks completely innocent here, without trying to understand what it does and WHY it is here. Wherer's the improvement? This is definitely NOT a way to do things. So, I really want to know more about your environment and the segfault. I don't see any segfaults here. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff46a7e.4040...@msgid.tls.msk.ru
Processed: Re: Bug#679377: Segmentation fault when initramfs is booting
Processing commands for cont...@bugs.debian.org: tags 679377 + moreinfo Bug #679377 [busybox] Segmentation fault when initramfs is booting Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 679377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.134141811716457.transcr...@bugs.debian.org
Bug#676001: Processed: reassign 676001 to busybox
severity 676001 wishlist tags 676001 + wontfix thanks As shown, historically it was util-linux which implemented functionality previously found in busybox, not the other way around, and as noted several times, it is none of switch_root business to deal with other filesystems (it is more a misfeature in util-linux implementation). So marking this bug as wontfix, and appropriately lowering severity. Thanks, /mjt On 08.06.2012 21:36, Michael Tokarev wrote: On 08.06.2012 15:22, maximilian attems wrote: On Fri, Jun 08, 2012 at 03:10:42PM +0400, Michael Tokarev wrote: On 08.06.2012 14:52, maximilian attems wrote: dude care to have a bit of patience before reassigning back, that be really nice. I gave a few days, maybe it was too few, I dunno. On Tue, Jun 05, 2012 at 08:45:59AM +0400, Michael Tokarev wrote: [] I disagree it is a busybox problem, and don't think it is a switch_root business (be it from busybox or from util-linux). switch_root in util-linux does it. Yes, but it is still none of its business. that is your personal opinon and shown to be wrong. (: If you name a command switch-root and not run-init, you'd have to take care to emmulate what the original command does. In this case it is util-linux is clearly predating busybox and thus busybox is buggy not fully implementing the command. Almost no of busybox commands implements fully the corresponding big brother behavour. well in the cases where it is needed and as busybox doesn't do it is a bug. Switch_root utility in util-linux appeared _after_ the same utility appeared in busybox. In util-linux it was implemented in 2009, http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commit;h=711ea7307d54caa74aa89fc7e8614236e3721f1c This command there were taken from dracut apparently. In there, it has been written in 2002 (I guess), has been called switchroot (no underscore), and it does _umounting_ of /dev, /proc, /sys, as can be seen at http://pjones.fedorapeople.org/mkstart/usr/lib/mkstart/switchroot.c In busybox it has been implemented as switch_root in 2005, in this commit: http://git.busybox.net/busybox/commit/util-linux/switch_root.c?id=0f34a821ab99e4936c7aa4974f58784442172211 which, obviously, pre-dates the same command in util-linux. There in busybox, it is named switch_root right from the beginning, and were made after run-init behavour (instead of the switchroot from dracut). So we can conclude these implementations (in util-linux and busybox) are independent and not follows or modelled from one another. In dractu, were it umounted /dev /proc /sys instead of moving these, I guess it was modelled after nash which was a bad example of shell to use in initrd, it didn't have most standard shell constructs so it weren't easy to program in it. But I can only guess. [] run-init doesn't move mount things, you could rename switch_root to run-init, then it would be correct. You confuse things, switch_root is the new command name by util-linux and it does a certain number of things. It doesn't matter, if you personally agree with them or not. Ah and please stop evading into the init script. I'm not. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff46e4b.6010...@msgid.tls.msk.ru
Processed: Re: Bug#676001: Processed: reassign 676001 to busybox
Processing commands for cont...@bugs.debian.org: severity 676001 wishlist Bug #676001 [busybox] initramfs-tools: busybox's switch_root doesn't handle /proc or /sys moving Severity set to 'wishlist' from 'important' tags 676001 + wontfix Bug #676001 [busybox] initramfs-tools: busybox's switch_root doesn't handle /proc or /sys moving Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 676001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.134141908821511.transcr...@bugs.debian.org
Processed: 678206 + 678209
Processing commands for cont...@bugs.debian.org: merge 678206 678209 Bug #678206 [busybox-static] Busybox-static telnetd doesn't allow to select the listening port Bug #678209 [busybox-static] Busybox-static telnetd doesn't allow to select the listening port Merged 678206 678209 thanks Stopping processing here. Please contact me if you need assistance. -- 678206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678206 678209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13414223866943.transcr...@bugs.debian.org
Processing of debian-installer-netboot-images_20120508_amd64.changes
debian-installer-netboot-images_20120508_amd64.changes uploaded successfully to localhost along with the files: debian-installer-netboot-images_20120508.dsc debian-installer-netboot-images_20120508.tar.gz debian-installer-7.0-netboot-amd64_20120508_all.deb debian-installer-7.0-netboot-armel_20120508_all.deb debian-installer-7.0-netboot-armhf_20120508_all.deb debian-installer-7.0-netboot-i386_20120508_all.deb debian-installer-7.0-netboot-ia64_20120508_all.deb debian-installer-7.0-netboot-kfreebsd-amd64_20120508_all.deb debian-installer-7.0-netboot-kfreebsd-i386_20120508_all.deb debian-installer-7.0-netboot-mips_20120508_all.deb debian-installer-7.0-netboot-mipsel_20120508_all.deb debian-installer-7.0-netboot-powerpc_20120508_all.deb debian-installer-7.0-netboot-sparc_20120508_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1smu1d-0001gm...@franck.debian.org
debian-installer-netboot-images_20120508_amd64.changes is NEW
(new) debian-installer-7.0-netboot-amd64_20120508_all.deb optional misc Debian-installer network boot images for amd64 This package contains images of the Debian Installer for the amd64 architecture. (new) debian-installer-7.0-netboot-armel_20120508_all.deb optional misc Debian-installer network boot images for armel This package contains images of the Debian Installer for the armel architecture. (new) debian-installer-7.0-netboot-armhf_20120508_all.deb optional misc Debian-installer network boot images for armhf This package contains images of the Debian Installer for the armhf architecture. (new) debian-installer-7.0-netboot-i386_20120508_all.deb optional misc Debian-installer network boot images for i386 This package contains images of the Debian Installer for the i386 architecture. (new) debian-installer-7.0-netboot-ia64_20120508_all.deb optional misc Debian-installer network boot images for ia64 This package contains images of the Debian Installer for the ia64 architecture. (new) debian-installer-7.0-netboot-kfreebsd-amd64_20120508_all.deb optional misc Debian-installer network boot images for kfreebsd-amd64 This package contains images of the Debian Installer for the kfreebsd-amd64 architecture. (new) debian-installer-7.0-netboot-kfreebsd-i386_20120508_all.deb optional misc Debian-installer network boot images for kfreebsd-i386 This package contains images of the Debian Installer for the kfreebsd-i386 architecture. (new) debian-installer-7.0-netboot-mips_20120508_all.deb optional misc Debian-installer network boot images for mips This package contains images of the Debian Installer for the mips architecture. (new) debian-installer-7.0-netboot-mipsel_20120508_all.deb optional misc Debian-installer network boot images for mipsel This package contains images of the Debian Installer for the mipsel architecture. (new) debian-installer-7.0-netboot-powerpc_20120508_all.deb optional misc Debian-installer network boot images for powerpc This package contains images of the Debian Installer for the powerpc architecture. (new) debian-installer-7.0-netboot-sparc_20120508_all.deb optional misc Debian-installer network boot images for sparc This package contains images of the Debian Installer for the sparc architecture. debian-installer-netboot-images_20120508.dsc to main/d/debian-installer-netboot-images/debian-installer-netboot-images_20120508.dsc debian-installer-netboot-images_20120508.tar.gz to main/d/debian-installer-netboot-images/debian-installer-netboot-images_20120508.tar.gz Changes: debian-installer-netboot-images (20120508) unstable; urgency=low . * Update to Wheezy's 20120508 images. . [ Daniel Baumann ] * Adding tftpd-hpa to suggests, this is the tftp server that is covered in the installer manual (Closes: #597116). . [ Didier Raboud ] * Put the architectures list in one place: - Let the maintainer build the control file from templates. - Generate the lintian overrides automatically at build-time. - Install the downloaded images directly to their destination places, drop the .install files. - Only download the specified architectures. - Drop the debian/TODO now requiring the above. * Update the architectures list to Wheezy: + Add armhf, kfreebsd-amd64, kfreebsd-i386 - Drop hppa * Add myself to Uploaders. * Bump Standards-Version to 3.9.3 without changes needed. Override entries for your package: debian-installer-netboot-images_20120508.dsc - source misc Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 597116 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1smu8f-0002bt...@franck.debian.org
Bug#680318: installation-reports: no big problems on EeeTop ET2011EGT-B073E
Package: installation-reports Severity: normal User: l...@pca.it Usertags: pca.it-installation User: eve...@debian.org Usertags: events-hardware Hi there! This machine is the one used in the Debian Events Box: https://wiki.debian.org/Teams/Events/DebianEventsBox Debian squeeze 6.0.4 amd64 was installed the first time just before FOSDEM 2012: graphical install worked like a charm (and FWIW even suspend...). For the forthcoming RMLL 2012 I re-installed it, but this time with wheezy, to give an idea of the next Debian stable release and check d-i status. The report is about this latter installation. Thx, bye, Gismo / Luca -- Package-specific info: Boot method: USB key Image version: CD-1_20120618-04:55; d-i_20120508 Date: 20120625T1800+0200 Machine: Asus All-in-One EeeTop ET2011EGT-B073E http://www.asus.com/Allinone_PCs/20_inch/ET2011EGT/ Partitions: sorry, no access right now (it is in .ch with myself in .ni), but basically out of 500G: 1=480G=/, 2=8G=swap and the rest to be used later for d-i BabelBox https://wiki.debian.org/DebianInstaller/BabelBox Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [ ] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [E] Install boot loader:[O] Overall install:[E] Comments/Problems: 1) I did not have any network at home, so d-i could not configure anything. 2) tasksel was strange: given that I had only CD-1, I was aware that the final Debian will not have a full DE. However, I was quite surprised that tasksel offered Debian desktop environment and Standard system only. IMHO there should be at least another task via CD-1, SSH server. 3) the primary user (events) was in the following groups only: events cdrom floppy audio dip video plugdev IIRC some important group (e.g. netdev) is missing: is this related to the fact that these groups are not present when the user is added to them? If so, they should be created by d-i beforehand. 4) I tried then to install the full DE via tasksel using a wheezy DVD-1 ISO image from the same 20120618-04:55 set. a) apt-cdrom needed manual intervention: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676302#33 b) `tasksel --new-install` did not installed all the packages in the default task. I have now discovered that maybe I should have specified the task: I do not remember if I did and the fact that the machine is in my flat in .ch with me being in .ni does not help. However, what I am sure I manually installed after tasksel is: gnome libreoffice iceweasel icedove c) at reboot GNOME3 failed to load, going into fallback mode, because it was missing firmware-linux-nonfree (Radeon). d) the first time I installed squeeze, Wi-Fi card did not work: there is no hardware switch and the manual says Windows software settings are necessary to use the wireless LAN. Fn+F2 did not work neither Network Manager could activate it, only rfkill. e) according to the specifications on the ASUS website (and other websites as well) the machine does not have any Bluetooth dongle, still the Bluetooth icon appears in the GNOME3 panel: http://bugs.debian.org/680316 f) I have not tried the touchscreen yet with this installation. g) not d-i-specific, but hardware virtualization (VT-X, vmx in /proc/cpuinfo) is disabled in BIOS 0315: http://ark.intel.com/products/42802/Intel-Pentium-Processor-E5800-%282M-Cache-3_20-GHz-800-MHz-FSB%29 -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7.0 (wheezy) - installer build 20120508 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux events-box-1 3.2.0-2-amd64 #1 SMP Sun Apr 15 16:47:38 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e30] (rev 03) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8476] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI Express Root Port [8086:2e31] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1b.0 Audio
Bug#680320: os-prober: Hangs
Package: os-prober Version: 1.53 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Ran os-prober * What exactly did you do (or not do) that was effective (or ineffective)? I ran os-prober * What was the outcome of this action? /dev/sda1:Windows Vista (loader):Windows:chain rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy /dev/sda2:Windows Vista (loader):Windows1:chain /dev/sdg1:unknown Linux distribution:Linux:linux rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy [ at this point all output stops ] * What outcome did you expect instead? A list of operating systems. *** End of the template - remove these lines *** njh@packard:~$ cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 # /dev/sda6 / ext3errors=remount-ro,noatime 0 1 UUID=38cb96ce-03b3-48e8-bb07-ada30a8f9c54 / ext3 errors=remount-ro,noatime 0 1 # /dev/sdb2 /home ext3noatime0 2 UUID=924ab451-776c-4558-bca5-f52dee7a4ea2 /home ext3noatime 0 2 # /dev/sda5 noneswapsw 0 0 UUID=0fa1b1a3-d3cc-4a3c-aa6f-37b5ee44261c noneswapsw 0 0 # /dev/hdc/media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 /dev/cdrom1/media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 # /dev/sda2 /mnt/c ntfs-3g defaults,umask=0,nls-utf8 0 0 UUID=BA7657137656CFAD /mnt/c ntfs-3g defaults,umask=0,nls-utf8 00 # /dev/sdb1 /mnt/d ntfs-3g defaults,umask=0,nls-utf8 0 0 UUID=5A3A6E293A6E027D /mnt/d ntfs-3g defaults,umask=0,nls-utf8 00 gateway:/ /mnt/gatewaynfs rw,hard,intr,nolock 0 0 gateway:/home /mnt/gateway/home nfs rw,hard,intr,nolock 0 0 gateway:/var/mnt/gateway/varnfs rw,hard,intr,nolock 0 0 gateway:/var/www/mirrors/CPAN /mnt/CPAN nfs ro,intr 0 0 # 192.168.7.97:/Users/nigel/web /mnt/webnfs rw,intr 0 0 /dev/sdg1 /mnt/sdg1 ufs ro,ufstype=sun 0 0 # LABEL=packard-mnt-sdg1/mnt/sdg1 ufs ro,ufstype=sun 0 0 /dev/sdg8 /mnt/sdg8 ufs ro,ufstype=sun 0 0 # LABEL=packard-mnt-sdg8/mnt/sdg8 ufs ro,ufstype=sun 0 0 njh@packard:~$ It looks as though os-prober has hung because it hasn't noticed that the mount command has finished: 28179 pts/0S 0:00 /bin/sh /usr/lib/os-probes/50mounted-tests /dev/sdg8 28506 pts/0D 0:00 mount -o ro -t ufs /dev/sdg8 /var/lib/os-prober/mount -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages os-prober depends on: ii libc6 2.13-34 os-prober recommends no packages. os-prober suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705002102.31114.18034.report...@packard.bandsman.co.uk
Bug#679377: Segmentation fault when initramfs is booting
Hi
On Wednesday 04 July 2012, Michael Tokarev wrote:
[…]
On 28.06.2012 13:14, Jordi Pujol wrote:
[…]
the patch shell-ash-export-HOME.patch causes a segmentation fault when
initramfs boots,
I believe that this fault occurs the first time that initramfs looks for
some
executable in the initramfs filesystem,
Does whole thing actually work? Why do you think it is this patch
which causes the SIGSEGV? The change in this patch is quite, well,
innocent, it does not look like it can be a cause for any such issues.
I'm having trouble with the same problem in a custom (not Debian live)
live boot environment, where busybox awk segfaults with
shell-ash-export-HOME.patch applied. The code in question is[1]:
FINGERED=$(awk -F: '
$1 == drive name NF 1 {
split($2, node, )
for (n in node) {
if (!system(test -b /dev/ node[n]))
cdrom[i++] = /dev/ node[n]
}
}
END {
for (c in cdrom)
print cdrom[c]
}
' /proc/sys/dev/cdrom/info)
Leading to:
Loading, please wait...
modprobe: module unix not found in modules.dep
mdadm: No arrays found in config file or automatically
Segmentation fault
Waiting for up to 30s for devices to settle...
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Failed to detect live media
modprobe: module i8042 not found in modules.dep
modprobe: module atkbd not found in modules.dep
BusyBox v1.20.1 (Debian 1:1.20.0-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
Executing the very same awk command from the initramfs shell (busybox
ash) afterwards succeeds however:
(initramfs) FINGERED=$(awk -F: '
$1 == drive name NF 1 {
split($2, node, )
for (n in node) {
if (!system(test -b /dev/ node[n]))
cdrom[i++] = /dev/ node[n]
}
}
END {
for (c in cdrom)
print cdrom[c]
}
' /proc/sys/dev/cdrom/info)
(initramfs) echo $FINGERED
/dev/sr0
Likewise rewriting the /proc/sys/dev/cdrom/info parsing to use
different busybox applets succeeds as well, while using awk in
different functions (fll_meminfo() and fll_copy_with_perc()) segfaults
the same way.
Can you describe your initramfs/environment a bit? Maybe give me
access to your initramfs for testing?
I'll provide a link to a test environment in a (private) follow up
mail, using this live code. While this particular initramfs hook is
not packaged in Debian, I expect similar issues to arise with standard
Debian initramfs hooks.
Also, the latest release of busybox, 1.20.1 is a bit different of that, and
Different of what, exactly? The version of busybox you're
filing bugreport against is actually 1.20.1, so there are
two questions actually: what is different, and different
between what and what? -- since you're comparing the same
thing with itself.
[…]
For testing purposes, I've rebuilt busybox (1:1.20.0-4) with only
shell-ash-export-HOME.patch disabled:
--- busybox-1.20.0/debian/patches/series
+++ busybox-1.20.0/debian/patches/series
@@ -1,6 +1,6 @@
1.20.1.patch
-shell-ash-export-HOME.patch
+#shell-ash-export-HOME.patch
# we need to get rid of this one:
#applets-fallback.patch
version.patch
and the segfaults in busybox awk vanished.
Regards
Stefan Lippers-Hollmann
[1]
http://svn.berlios.de/svnroot/repos/fullstory/fll-live-initramfs/trunk/scripts/fll
signature.asc
Description: This is a digitally signed message part.
Re: Preparation for d-i beta 1
Hi all, (Dropping -cd, -kernel and -live) As allocating time got easier with DebCamp, I have now successively tackled two issues regarding the debian-netboot packages which should probably land in for Wheezy (but could be delayed to a later beta): a) src:debian-installer-netboot-images [0,1] hadn't seen updates in a while and wasn't (IMHO) ready for Wheezy. I refactored the packaging to have the list in one single place (debian/rules); debian/control can now be maintainer- generated when the list of architectures change. This has now been uploaded [2] with the latest installer version available in wheezy and is now waiting in NEW. That said, I've been told over IRC that: a1) these packages will probably be broken soon a2) that these packages should probably not carry the mighty 7.0 label before containing at least betas (especially because of a1 above…) [0] http://packages.qa.debian.org/debian-installer-netboot-images [1] http://anonscm.debian.org/gitweb/?p=d-i/debian-installer-netboot- images.git [2] http://lists.debian.org/debian-boot/2012/07/msg00055.html b) Then, discussing this over the lunch with Philipp Kern, we agreed that instead of downloading netboot.tar.gz's from mirrors (without checking them) to create those debian-installer-$version-netboot-$arch packages, it would actually be saner to build them within the d-i build process. I have been implementing this on the generate_netboot_package branch [3,4] on the debian-installer.git. The approach I have been taking is to keep producing arch:all packages (as was done in src:debian-installer-netboot-images ), but one at a time: when amd64's d-i is built, then the debian-installer-7.0- netboot-amd64:all package is built by unpacking the just-built netboot.tar.gz's. debian/control becomes a maintainer-generated file. This leads to the following problem: buildds are very probably not letting arch:all packages go towards the archive. Each d-i .changes would be Architecture: $arch all with a different arch:all package. I wanted to upload d-i to experimental to test this without affecting Wheezy. There are probably two ways out though: b1) build arch:any, multi-arch:same packages instead. This has the downside of imposing the complete foreign archive for each -installer package that an admin would like to provide over tftp but makes more sense in terms of DEB_BUILD_ARCH. b2) fix sbuild :-) [3] http://anonscm.debian.org/gitweb/?p=d-i/debian- installer.git;a=shortlog;h=refs/heads/generate_netboot_package [4] http://anonscm.debian.org/gitweb/?p=d-i/debian- installer.git;a=commit;h=ed43166 Opinions, comments ? Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: amd64 Jul 04 21:59 debian-cd@pettersson 1sidmips http://cdbuilder.debian.org/cdimage-log/1sidmips * FAILED BUILD: amd64 Jul 04 21:59 debian-cd@pettersson 2sidmips http://cdbuilder.debian.org/cdimage-log/2sidmips Totals: 117 builds (2 failed, 0 old) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1smaqo-00042y...@ravel.debian.org
