From ftpmaster at ftp-master.debian.org Fri Sep 4 12:31:59 2015 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Fri, 04 Sep 2015 12:31:59 +0000 Subject: Processing of grub2_2.02~beta2-27_source.changes Message-ID: grub2_2.02~beta2-27_source.changes uploaded successfully to localhost along with the files: grub2_2.02~beta2-27.dsc grub2_2.02~beta2-27.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) From ftpmaster at ftp-master.debian.org Fri Sep 4 12:34:29 2015 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Fri, 04 Sep 2015 12:34:29 +0000 Subject: grub2_2.02~beta2-27_source.changes ACCEPTED into unstable Message-ID: Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 04 Sep 2015 12:35:59 +0100 Source: grub2 Binary: grub2 grub-linuxbios grub-efi grub-common grub2-common grub-emu grub-emu-dbg grub-pc-bin grub-pc-dbg grub-pc grub-rescue-pc grub-coreboot-bin grub-coreboot-dbg grub-coreboot grub-efi-ia32-bin grub-efi-ia32-dbg grub-efi-ia32 grub-efi-amd64-bin grub-efi-amd64-dbg grub-efi-amd64 grub-efi-ia64-bin grub-efi-ia64-dbg grub-efi-ia64 grub-efi-arm-bin grub-efi-arm-dbg grub-efi-arm grub-efi-arm64-bin grub-efi-arm64-dbg grub-efi-arm64 grub-ieee1275-bin grub-ieee1275-dbg grub-ieee1275 grub-firmware-qemu grub-uboot-bin grub-uboot-dbg grub-uboot grub-xen-bin grub-xen-dbg grub-xen grub-xen-host grub-yeeloong-bin grub-yeeloong-dbg grub-yeeloong grub-theme-starfield grub-mount-udeb Architecture: source Version: 2.02~beta2-27 Distribution: unstable Urgency: medium Maintainer: GRUB Maintainers Changed-By: Colin Watson Description: grub-common - GRand Unified Bootloader (common files) grub-coreboot - GRand Unified Bootloader, version 2 (Coreboot version) grub-coreboot-bin - GRand Unified Bootloader, version 2 (Coreboot binaries) grub-coreboot-dbg - GRand Unified Bootloader, version 2 (Coreboot debug files) grub-efi - GRand Unified Bootloader, version 2 (dummy package) grub-efi-amd64 - GRand Unified Bootloader, version 2 (EFI-AMD64 version) grub-efi-amd64-bin - GRand Unified Bootloader, version 2 (EFI-AMD64 binaries) grub-efi-amd64-dbg - GRand Unified Bootloader, version 2 (EFI-AMD64 debug files) grub-efi-arm - GRand Unified Bootloader, version 2 (ARM UEFI version) grub-efi-arm-bin - GRand Unified Bootloader, version 2 (ARM UEFI binaries) grub-efi-arm-dbg - GRand Unified Bootloader, version 2 (ARM UEFI debug files) grub-efi-arm64 - GRand Unified Bootloader, version 2 (ARM64 UEFI version) grub-efi-arm64-bin - GRand Unified Bootloader, version 2 (ARM64 UEFI binaries) grub-efi-arm64-dbg - GRand Unified Bootloader, version 2 (ARM64 UEFI debug files) grub-efi-ia32 - GRand Unified Bootloader, version 2 (EFI-IA32 version) grub-efi-ia32-bin - GRand Unified Bootloader, version 2 (EFI-IA32 binaries) grub-efi-ia32-dbg - GRand Unified Bootloader, version 2 (EFI-IA32 debug files) grub-efi-ia64 - GRand Unified Bootloader, version 2 (IA64 version) grub-efi-ia64-bin - GRand Unified Bootloader, version 2 (IA64 binaries) grub-efi-ia64-dbg - GRand Unified Bootloader, version 2 (IA64 debug files) grub-emu - GRand Unified Bootloader, version 2 (emulated version) grub-emu-dbg - GRand Unified Bootloader, version 2 (emulated debug files) grub-firmware-qemu - GRUB firmware image for QEMU grub-ieee1275 - GRand Unified Bootloader, version 2 (Open Firmware version) grub-ieee1275-bin - GRand Unified Bootloader, version 2 (Open Firmware binaries) grub-ieee1275-dbg - GRand Unified Bootloader, version 2 (Open Firmware debug files) grub-linuxbios - GRand Unified Bootloader, version 2 (dummy package) grub-mount-udeb - export GRUB filesystems using FUSE (udeb) grub-pc - GRand Unified Bootloader, version 2 (PC/BIOS version) grub-pc-bin - GRand Unified Bootloader, version 2 (PC/BIOS binaries) grub-pc-dbg - GRand Unified Bootloader, version 2 (PC/BIOS debug files) grub-rescue-pc - GRUB bootable rescue images, version 2 (PC/BIOS version) grub-theme-starfield - GRand Unified Bootloader, version 2 (starfield theme) grub-uboot - GRand Unified Bootloader, version 2 (ARM U-Boot version) grub-uboot-bin - GRand Unified Bootloader, version 2 (ARM U-Boot binaries) grub-uboot-dbg - GRand Unified Bootloader, version 2 (ARM U-Boot debug files) grub-xen - GRand Unified Bootloader, version 2 (Xen version) grub-xen-bin - GRand Unified Bootloader, version 2 (Xen binaries) grub-xen-dbg - GRand Unified Bootloader, version 2 (Xen debug files) grub-xen-host - GRand Unified Bootloader, version 2 (Xen host version) grub-yeeloong - GRand Unified Bootloader, version 2 (Yeeloong version) grub-yeeloong-bin - GRand Unified Bootloader, version 2 (Yeeloong binaries) grub-yeeloong-dbg - GRand Unified Bootloader, version 2 (Yeeloong debug files) grub2 - GRand Unified Bootloader, version 2 (dummy package) grub2-common - GRand Unified Bootloader (common files for version 2) Closes: 744954 777648 Changes: grub2 (2.02~beta2-27) unstable; urgency=medium . [ Felix Zielcke ] * Remove Robert Millan from Uploaders with his permission. Thanks for all the work he did for GRUB 2! * Stop forcing gcc-4.9 for building. * Update to Policy 3.9.6. * Update the Browser URL for our git repository. * Use dpkg-buildflags at least for the host binaries. * Simplify Build-Depends. . [ Colin Watson ] * Go back to forcing a particular compiler version, but this time gcc-5. The reason for this is that new compiler versions often make slight changes to the size of compiled code which break delicate parts of GRUB, and we want to make sure that we test newer versions before switching to them. * Make builds that are not limited to architecture-dependent packages (i.e. dpkg-buildpackage -b) work on non-x86 architectures (closes: #744954). . [ Mathieu Trudel-Lapierre ] * debian/build-efi-images: Look for grub.cfg in $cmdpath too in gcdx64.efi, to simplify embedded scenarios: putting a grub.cfg snippet that loads the right "real" grub.cfg can be useful. (LP: #1468111) * debian/patches/uefi_firmware_setup.patch: Take into account that the UEFI variable OsIndicationsSupported is a bit field, and as such should be compared as hex values in 30_uefi-firmware.in. (LP: #1456911) * Update quick boot logic to handle abstractions for which there is no write support. (LP: #1274320) . [ dann frazier ] * d/p/arm64-set-correct-length-of-device-path-end-entry.patch: Fixes booting arm64 kernels on certain UEFI implementations. (LP: #1476882) . [ Debconf translations ] * [lv] Latvian (Rudolfs Mazurs; closes: #777648). Checksums-Sha1: 91836ead584e0883798ac1f8492397cbe6160bc7 6331 grub2_2.02~beta2-27.dsc 4257084908e20efa1918263e8828743c020d59a7 1020880 grub2_2.02~beta2-27.debian.tar.xz Checksums-Sha256: a72756aa9490c52e595d25e63abe0794711195591435f8591459fcc05524f457 6331 grub2_2.02~beta2-27.dsc f71fb88ae6458cb10b21020b33fffc4b3bd8da02007bdee4b12420ccd0518b98 1020880 grub2_2.02~beta2-27.debian.tar.xz Files: f38379dce6ca3730c928b74c47a63d59 6331 admin extra grub2_2.02~beta2-27.dsc f978892a82a362ecd1161e8a55bccf5c 1020880 admin extra grub2_2.02~beta2-27.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Colin Watson -- Debian developer iQIVAwUBVemOMDk1h9l9hlALAQgAbRAAjPOTEoXNaoq7+smxkQfYcgSV5kKHKCoT Vl/iFDbF8c6hbhs/n1NkYwYWm7bzNeni50qXw0+7AaUYyqnJtmv199o5BUxTsSyO h/Rtqvg+tlwgDM7MPzv496OfnPi1uNjJu1+NCf1E/dmTMDEjtE0t4bUJmveGWDs5 a8sP8hO/QPP27LdKjqAKViuc9D2E2mEsQYVmDiR1ygVnVM5/pjG7AKlqveKYX78s 3VTIGCoAdOHEFe7fLLXhwIcO2fTCFawSChFFIsoA4ifCr3cfQTR2L6OV4psG4zL4 lRCeKg9AAr0AOAGFleajYcykY7VQRKORMWVxV6AVfU5XfhLo6XVySz5o6Nzn4PiJ lBH4mf7mk5ISiqWrci4aTSaWj3CHCZEag3a7ewQjMcz5gO5R8zu+PISSkawXuDQb 7J2HKrX3kYa98jKxnHndRMDc9ejDcxSFMK0piXR1X+3M+9Dhsfar8eIqU37+vdJ6 bFizotJr53lUy529LX4eBaKjzXt9gbl0Ls+X/rIkABJdJ10NSqqefrCDQHMo7cFx 3fkrrbGfKlSCVUEWZLtizBL9fyCKX7A5vx1gMGnc0htz6ic8Ni82nM30mKYS0qB/ hNq07iBGEeNX/QuDeOrVVDqUj5tosuqeEArR0xO2Jtjo3tp2QFFIk+KQ4XNe7G3k EATqpTvpwMw= =lRGr -----END PGP SIGNATURE----- Thank you for your contribution to Debian. From owner at bugs.debian.org Fri Sep 4 12:39:08 2015 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 04 Sep 2015 12:39:08 +0000 Subject: Bug#744954: marked as done (grub2: FTBFS on powerpc) References: <20140416163313.GA24272@tryphon.debian.net> Message-ID: Your message dated Fri, 04 Sep 2015 12:34:29 +0000 with message-id and subject line Bug#744954: fixed in grub2 2.02~beta2-27 has caused the Debian Bug report #744954, regarding grub2: FTBFS on powerpc 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 744954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744954 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Nicolas Boullis Subject: grub2: FTBFS on powerpc Date: Wed, 16 Apr 2014 18:33:13 +0200 Size: 5870 URL: -------------- next part -------------- An embedded message was scrubbed... From: Colin Watson Subject: Bug#744954: fixed in grub2 2.02~beta2-27 Date: Fri, 04 Sep 2015 12:34:29 +0000 Size: 10394 URL: From owner at bugs.debian.org Fri Sep 4 12:39:12 2015 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 04 Sep 2015 12:39:12 +0000 Subject: Bug#777648: marked as done ([I18N:lv] Updated Latvian translation of debconf templates) References: <1423628460.31964.9.camel@debian.org> Message-ID: Your message dated Fri, 04 Sep 2015 12:34:29 +0000 with message-id and subject line Bug#777648: fixed in grub2 2.02~beta2-27 has caused the Debian Bug report #777648, regarding [I18N:lv] Updated Latvian translation of debconf templates 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 777648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777648 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Ian Campbell Subject: [I18N:lv] Updated Latvian translation of debconf templates Date: Wed, 11 Feb 2015 04:21:00 +0000 Size: 79972 URL: -------------- next part -------------- An embedded message was scrubbed... From: Colin Watson Subject: Bug#777648: fixed in grub2 2.02~beta2-27 Date: Fri, 04 Sep 2015 12:34:29 +0000 Size: 10419 URL: From cjwatson at debian.org Sat Sep 5 20:34:38 2015 From: cjwatson at debian.org (Colin Watson) Date: Sat, 5 Sep 2015 21:34:38 +0100 Subject: [noreply@buildd.debian.org: failed ppc64el build of grub2 2.02~beta2-27] Message-ID: <20150905203438.GP2382@riva.ucam.org> I can't reproduce the attached failure in an unstable chroot on pastel. One difference I see is that current unstable has gcc-5 5.2.1-16 while this build log has gcc-5 5.2.1-15. Would it be possible to upgrade the chroots and try again? (It doesn't really feel like a correct use of a versioned Build-Depends to me, since if this fixes it then it's really just a particular buggy version.) Thanks, -- Colin Watson [cjwatson at debian.org] -------------- next part -------------- An embedded message was scrubbed... From: Debian buildds Subject: failed ppc64el build of grub2 2.02~beta2-27 Date: Fri, 04 Sep 2015 13:00:02 +0000 Size: 3672 URL: From cjwatson at debian.org Sat Sep 5 23:11:12 2015 From: cjwatson at debian.org (Colin Watson) Date: Sun, 6 Sep 2015 00:11:12 +0100 Subject: [noreply@buildd.debian.org: failed ppc64el build of grub2 2.02~beta2-27] In-Reply-To: <20150905221307.GA18839@aurel32.net> References: <20150905203438.GP2382@riva.ucam.org> <20150905221307.GA18839@aurel32.net> Message-ID: <20150905231112.GQ2382@riva.ucam.org> On Sun, Sep 06, 2015 at 12:13:07AM +0200, Aurelien Jarno wrote: > On 2015-09-05 21:34, Colin Watson wrote: > > I can't reproduce the attached failure in an unstable chroot on pastel. > > One difference I see is that current unstable has gcc-5 5.2.1-16 while > > this build log has gcc-5 5.2.1-15. Would it be possible to upgrade the > > chroots and try again? (It doesn't really feel like a correct use of a > > versioned Build-Depends to me, since if this fixes it then it's really > > just a particular buggy version.) > > Done, let's see how it goes. That worked, thanks a lot! -- Colin Watson [cjwatson at debian.org] From ftpmaster at ftp-master.debian.org Sun Sep 6 00:31:47 2015 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Sun, 06 Sep 2015 00:31:47 +0000 Subject: Processing of grub2_2.02~beta2-28_source.changes Message-ID: grub2_2.02~beta2-28_source.changes uploaded successfully to localhost along with the files: grub2_2.02~beta2-28.dsc grub2_2.02~beta2-28.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) From ftpmaster at ftp-master.debian.org Sun Sep 6 00:34:01 2015 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Sun, 06 Sep 2015 00:34:01 +0000 Subject: grub2_2.02~beta2-28_source.changes ACCEPTED into unstable Message-ID: Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 06 Sep 2015 01:25:56 +0100 Source: grub2 Binary: grub2 grub-linuxbios grub-efi grub-common grub2-common grub-emu grub-emu-dbg grub-pc-bin grub-pc-dbg grub-pc grub-rescue-pc grub-coreboot-bin grub-coreboot-dbg grub-coreboot grub-efi-ia32-bin grub-efi-ia32-dbg grub-efi-ia32 grub-efi-amd64-bin grub-efi-amd64-dbg grub-efi-amd64 grub-efi-ia64-bin grub-efi-ia64-dbg grub-efi-ia64 grub-efi-arm-bin grub-efi-arm-dbg grub-efi-arm grub-efi-arm64-bin grub-efi-arm64-dbg grub-efi-arm64 grub-ieee1275-bin grub-ieee1275-dbg grub-ieee1275 grub-firmware-qemu grub-uboot-bin grub-uboot-dbg grub-uboot grub-xen-bin grub-xen-dbg grub-xen grub-xen-host grub-yeeloong-bin grub-yeeloong-dbg grub-yeeloong grub-theme-starfield grub-mount-udeb Architecture: source Version: 2.02~beta2-28 Distribution: unstable Urgency: medium Maintainer: GRUB Maintainers Changed-By: Colin Watson Description: grub-common - GRand Unified Bootloader (common files) grub-coreboot - GRand Unified Bootloader, version 2 (Coreboot version) grub-coreboot-bin - GRand Unified Bootloader, version 2 (Coreboot binaries) grub-coreboot-dbg - GRand Unified Bootloader, version 2 (Coreboot debug files) grub-efi - GRand Unified Bootloader, version 2 (dummy package) grub-efi-amd64 - GRand Unified Bootloader, version 2 (EFI-AMD64 version) grub-efi-amd64-bin - GRand Unified Bootloader, version 2 (EFI-AMD64 binaries) grub-efi-amd64-dbg - GRand Unified Bootloader, version 2 (EFI-AMD64 debug files) grub-efi-arm - GRand Unified Bootloader, version 2 (ARM UEFI version) grub-efi-arm-bin - GRand Unified Bootloader, version 2 (ARM UEFI binaries) grub-efi-arm-dbg - GRand Unified Bootloader, version 2 (ARM UEFI debug files) grub-efi-arm64 - GRand Unified Bootloader, version 2 (ARM64 UEFI version) grub-efi-arm64-bin - GRand Unified Bootloader, version 2 (ARM64 UEFI binaries) grub-efi-arm64-dbg - GRand Unified Bootloader, version 2 (ARM64 UEFI debug files) grub-efi-ia32 - GRand Unified Bootloader, version 2 (EFI-IA32 version) grub-efi-ia32-bin - GRand Unified Bootloader, version 2 (EFI-IA32 binaries) grub-efi-ia32-dbg - GRand Unified Bootloader, version 2 (EFI-IA32 debug files) grub-efi-ia64 - GRand Unified Bootloader, version 2 (IA64 version) grub-efi-ia64-bin - GRand Unified Bootloader, version 2 (IA64 binaries) grub-efi-ia64-dbg - GRand Unified Bootloader, version 2 (IA64 debug files) grub-emu - GRand Unified Bootloader, version 2 (emulated version) grub-emu-dbg - GRand Unified Bootloader, version 2 (emulated debug files) grub-firmware-qemu - GRUB firmware image for QEMU grub-ieee1275 - GRand Unified Bootloader, version 2 (Open Firmware version) grub-ieee1275-bin - GRand Unified Bootloader, version 2 (Open Firmware binaries) grub-ieee1275-dbg - GRand Unified Bootloader, version 2 (Open Firmware debug files) grub-linuxbios - GRand Unified Bootloader, version 2 (dummy package) grub-mount-udeb - export GRUB filesystems using FUSE (udeb) grub-pc - GRand Unified Bootloader, version 2 (PC/BIOS version) grub-pc-bin - GRand Unified Bootloader, version 2 (PC/BIOS binaries) grub-pc-dbg - GRand Unified Bootloader, version 2 (PC/BIOS debug files) grub-rescue-pc - GRUB bootable rescue images, version 2 (PC/BIOS version) grub-theme-starfield - GRand Unified Bootloader, version 2 (starfield theme) grub-uboot - GRand Unified Bootloader, version 2 (ARM U-Boot version) grub-uboot-bin - GRand Unified Bootloader, version 2 (ARM U-Boot binaries) grub-uboot-dbg - GRand Unified Bootloader, version 2 (ARM U-Boot debug files) grub-xen - GRand Unified Bootloader, version 2 (Xen version) grub-xen-bin - GRand Unified Bootloader, version 2 (Xen binaries) grub-xen-dbg - GRand Unified Bootloader, version 2 (Xen debug files) grub-xen-host - GRand Unified Bootloader, version 2 (Xen host version) grub-yeeloong - GRand Unified Bootloader, version 2 (Yeeloong version) grub-yeeloong-bin - GRand Unified Bootloader, version 2 (Yeeloong binaries) grub-yeeloong-dbg - GRand Unified Bootloader, version 2 (Yeeloong debug files) grub2 - GRand Unified Bootloader, version 2 (dummy package) grub2-common - GRand Unified Bootloader (common files for version 2) Changes: grub2 (2.02~beta2-28) unstable; urgency=medium . * Reduce the CFLAGS -O3 default on Ubuntu ppc64el to -O2; it introduces various -Werror failures and isn't worth it here. Checksums-Sha1: 97355bae9f41651ba5e2c0ec12e73ea1dae89eb1 6331 grub2_2.02~beta2-28.dsc 79fc4464641b430fa276446e5592ef52ca66feb4 1020968 grub2_2.02~beta2-28.debian.tar.xz Checksums-Sha256: 0bccb49462ceb2cfa5bcf7bd3b846ff094de27ffc5b80b5c66ef255705803016 6331 grub2_2.02~beta2-28.dsc bd6683ececb21e8bec82e95c94d62d712431b74b7bbf5aa6aba642689a9a67e0 1020968 grub2_2.02~beta2-28.debian.tar.xz Files: 35d13a56b3071979624a47ba23119fe7 6331 admin extra grub2_2.02~beta2-28.dsc f5224fa625a7d6aa38a3ce276f856a72 1020968 admin extra grub2_2.02~beta2-28.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Colin Watson -- Debian developer iQIVAwUBVeuIajk1h9l9hlALAQhE+A//ZJyEWAvdKLbIBbtsYGohTQroOrSLLyi1 rnrgEf7qTfOc0S3U12eMV8xGIQlGRQvTiP/wglRQzjxo+QgzA7Gpmeg+5CNJ5KR9 Y1FGhZBvn7doZ1WeFMcJm0EmHvECjLw+LbvoEoLKtzN+QXYPDj85TUMLqBDHjM5d qceVLZX9UNU3Yf9AsYvxcoefQ/Fld7zBkmSGBMKTcGR96QBeui2RBiG7NPvXGYMM DRuEIqIHppD6WG7fTvpxLWlDtkOJORRpur1klsxcCKjicJV8QSuJqpF7Xk13ExY9 g9TmOgCoJre72o9CAmLJE21pzZWhlMbAamG/KcdrADNVPV4CFEF8DRpG/jr1VNIc qtC0iS2G2bI6ruYE8whv+T5gJRYWjm++wIbCPk2Im/Rz99wBCi02i0QUqKKmW49L /Mlaam+9Guyp+ulokWs0/PQVXh0lEFMPz/pYkQTc0CZ/NtASjDXq06G09i894fUN 3//QavrDyelzE8+Tb6mKfHQJyFAFvr65i2pbahGVavGDAgNudltX6hAuD4frN2oI KGWHW2kJV8nRi/v4/TUeV9oNfpf4blve/S5OCxnpUKbhcl91qrLYPYKVePu+Wo5x bIPo9GjyZ01VfWXb24oOhk03zMup+Rv/R0gdD5QH+QFeeyO8lObNrDb4gVfxFNbk R+0fT5z0wG4= =J0eh -----END PGP SIGNATURE----- Thank you for your contribution to Debian. From cjwatson at debian.org Sun Sep 6 02:17:44 2015 From: cjwatson at debian.org (Colin Watson) Date: Sun, 6 Sep 2015 03:17:44 +0100 Subject: [noreply@buildd.debian.org: failed ppc64el build of grub2 2.02~beta2-27] In-Reply-To: <20150905231112.GQ2382@riva.ucam.org> References: <20150905203438.GP2382@riva.ucam.org> <20150905221307.GA18839@aurel32.net> <20150905231112.GQ2382@riva.ucam.org> Message-ID: <20150906021744.GA2520@riva.ucam.org> On Sun, Sep 06, 2015 at 12:11:12AM +0100, Colin Watson wrote: > That worked, thanks a lot! But then 2.02~beta2-28 failed again on the previous builder: https://buildd.debian.org/status/fetch.php?pkg=grub2&arch=ppc64el&ver=2.02~beta2-28&stamp=1441500965&file=log I don't suppose you're able to upgrade ppc64el-unicamp-01's chroots? If not, it would be good to take this on ppc64el-osuosl-01 again. Thanks, -- Colin Watson [cjwatson at debian.org] From riesebie at lxtec.de Sun Sep 6 08:54:47 2015 From: riesebie at lxtec.de (Elimar Riesebieter) Date: Sun, 6 Sep 2015 10:54:47 +0200 Subject: Bug#741365: grub-common: On grub apt-get uprade I got many "/proc/devices: No entry for device-mapper found" Message-ID: <20150906085446.GA21480@galadriel.home.lxtec.de> Control: fixed -1 2.02~beta2-27 Bug seems to be fixed in 2.02~beta2-27 Elimar -- Experience is something you don't get until just after you need it! From owner at bugs.debian.org Sun Sep 6 08:57:13 2015 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sun, 06 Sep 2015 08:57:13 +0000 Subject: Processed: grub-common: On grub apt-get uprade I got many "/proc/devices: No entry for device-mapper found" References: <20150906085446.GA21480@galadriel.home.lxtec.de> <20140311182050.5984.96914.reportbug@galadriel.home.lxtec.de> Message-ID: Processing control commands: > fixed -1 2.02~beta2-27 Bug #741365 [grub-common] grub-common: On grub apt-get uprade I got many "/proc/devices: No entry for device-mapper found" Marked as fixed in versions grub2/2.02~beta2-27. -- 741365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741365 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From owner at bugs.debian.org Sun Sep 6 08:57:16 2015 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sun, 06 Sep 2015 08:57:16 +0000 Subject: Bug#741365: marked as done (grub-common: On grub apt-get uprade I got many "/proc/devices: No entry for device-mapper found") References: <20150906085446.GA21480@galadriel.home.lxtec.de> <20140311182050.5984.96914.reportbug@galadriel.home.lxtec.de> Message-ID: Your message dated Sun, 6 Sep 2015 10:54:47 +0200 with message-id <20150906085446.GA21480 at galadriel.home.lxtec.de> and subject line grub-common: On grub apt-get uprade I got many "/proc/devices: No entry for device-mapper found" has caused the Debian Bug report #741365, regarding grub-common: On grub apt-get uprade I got many "/proc/devices: No entry for device-mapper found" 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 741365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741365 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Elimar Riesebieter Subject: grub-common: On grub apt-get uprade I got many "/proc/devices: No entry for device-mapper found" Date: Tue, 11 Mar 2014 19:20:50 +0100 Size: 3234 URL: -------------- next part -------------- An embedded message was scrubbed... From: Elimar Riesebieter Subject: grub-common: On grub apt-get uprade I got many "/proc/devices: No entry for device-mapper found" Date: Sun, 6 Sep 2015 10:54:47 +0200 Size: 2729 URL: From cjwatson at debian.org Sun Sep 6 10:44:48 2015 From: cjwatson at debian.org (Colin Watson) Date: Sun, 6 Sep 2015 11:44:48 +0100 Subject: [noreply@buildd.debian.org: failed ppc64el build of grub2 2.02~beta2-27] In-Reply-To: <20150906085640.GA12675@aurel32.net> References: <20150905203438.GP2382@riva.ucam.org> <20150905221307.GA18839@aurel32.net> <20150905231112.GQ2382@riva.ucam.org> <20150906021744.GA2520@riva.ucam.org> <20150906085640.GA12675@aurel32.net> Message-ID: <20150906104448.GR2382@riva.ucam.org> On Sun, Sep 06, 2015 at 10:56:40AM +0200, Aurelien Jarno wrote: > Actually I did a give back with --extra-depends instead of upgrading the > chroot. I did the same for the new version, as anyway the chroots are > recreated weekly, and the next time is in about 12 hours. Ah, OK. Thanks again. -- Colin Watson [cjwatson at debian.org] From axst at users.sourceforge.net Sun Sep 6 13:28:57 2015 From: axst at users.sourceforge.net (Axel) Date: Sun, 6 Sep 2015 15:28:57 +0200 Subject: Bug#798182: grub-common: menu creation based on settings should be easy to customise Message-ID: <20150906132857.GA13362@flora.lan> Package: grub-common Version: 2.02~beta2-22 Severity: wishlist Dear Maintainer, Currently, two menu entries are created for every bootable operating system. Please make the settings for this easier to configure so tahat, e.g., I can include a third entry containing the ?fastboot? option for every installed Linux version. *********************** BEGIN /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then set have_grubenv=true load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="0" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod part_msdos insmod ext2 set root='hd0,msdos7' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7 4b58f6c0-091b-4687-b6c0-26624f0db80c else search --no-floppy --fs-uuid --set=root 4b58f6c0-091b-4687-b6c0-26624f0db80c fi font="/share/grub/unicode.pf2" fi if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm set locale_dir=$prefix/locale set lang=en_IE insmod gettext fi terminal_output gfxterm if [ "${recordfail}" = 1 ] ; then set timeout=-1 else if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/05_debian_theme ### insmod part_msdos insmod ext2 set root='hd0,msdos7' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7 4b58f6c0-091b-4687-b6c0-26624f0db80c else search --no-floppy --fs-uuid --set=root 4b58f6c0-091b-4687-b6c0-26624f0db80c fi insmod png if background_image /share/images/desktop-base/lines-grub.png; then set color_normal=white/black set color_highlight=black/white else set menu_color_normal=cyan/blue set menu_color_highlight=white/blue fi ### END /etc/grub.d/05_debian_theme ### ### BEGIN /etc/grub.d/10_linux ### function gfxmode { set gfxpayload="${1}" } set linux_gfx_mode= export linux_gfx_mode menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-67f3ac86-e1e4-48a7-99f2-05af41574a14' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 67f3ac86-e1e4-48a7-99f2-05af41574a14 else search --no-floppy --fs-uuid --set=root 67f3ac86-e1e4-48a7-99f2-05af41574a14 fi echo 'Loading Linux 3.16.0-4-amd64 ...' linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=67f3ac86-e1e4-48a7-99f2-05af41574a14 ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.16.0-4-amd64 } submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-67f3ac86-e1e4-48a7-99f2-05af41574a14' { menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-amd64-advanced-67f3ac86-e1e4-48a7-99f2-05af41574a14' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 67f3ac86-e1e4-48a7-99f2-05af41574a14 else search --no-floppy --fs-uuid --set=root 67f3ac86-e1e4-48a7-99f2-05af41574a14 fi echo 'Loading Linux 3.16.0-4-amd64 ...' linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=67f3ac86-e1e4-48a7-99f2-05af41574a14 ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.16.0-4-amd64 } menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-amd64-recovery-67f3ac86-e1e4-48a7-99f2-05af41574a14' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 67f3ac86-e1e4-48a7-99f2-05af41574a14 else search --no-floppy --fs-uuid --set=root 67f3ac86-e1e4-48a7-99f2-05af41574a14 fi echo 'Loading Linux 3.16.0-4-amd64 ...' linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=67f3ac86-e1e4-48a7-99f2-05af41574a14 ro single echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.16.0-4-amd64 } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'Debian GNU/Linux (7.8) (on /dev/sdd6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-d62495d6-dd20-4fbb-a96e-42b3c8b7aa83' { insmod part_msdos insmod ext2 set root='hd3,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos6 --hint-efi=hd3,msdos6 --hint-baremetal=ahci3,msdos6 d62495d6-dd20-4fbb-a96e-42b3c8b7aa83 else search --no-floppy --fs-uuid --set=root d62495d6-dd20-4fbb-a96e-42b3c8b7aa83 fi linux /boot/vmlinuz-3.2.0-4-686-pae root=/dev/sdd6 initrd /boot/initrd.img-3.2.0-4-686-pae } submenu 'Advanced options for Debian GNU/Linux (7.8) (on /dev/sdd6)' $menuentry_id_option 'osprober-gnulinux-advanced-d62495d6-dd20-4fbb-a96e-42b3c8b7aa83' { menuentry 'Debian GNU/Linux (7.8) (on /dev/sdd6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.2.0-4-686-pae--d62495d6-dd20-4fbb-a96e-42b3c8b7aa83' { insmod part_msdos insmod ext2 set root='hd3,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos6 --hint-efi=hd3,msdos6 --hint-baremetal=ahci3,msdos6 d62495d6-dd20-4fbb-a96e-42b3c8b7aa83 else search --no-floppy --fs-uuid --set=root d62495d6-dd20-4fbb-a96e-42b3c8b7aa83 fi linux /boot/vmlinuz-3.2.0-4-686-pae root=/dev/sdd6 initrd /boot/initrd.img-3.2.0-4-686-pae } } ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/30_uefi-firmware ### ### END /etc/grub.d/30_uefi-firmware ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### *********************** END /boot/grub/grub.cfg *********************** BEGIN /proc/mdstat cat: /proc/mdstat: No such file or directory *********************** END /proc/mdstat *********************** BEGIN /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 Sep 5 22:20 ata-Hitachi_HDS724040ALE640_PK2331PAH37H6T -> ../../sdb lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-Hitachi_HDS724040ALE640_PK2331PAH37H6T-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Sep 5 22:20 ata-SAMSUNG_HD103UJ_S13PJDWS305738 -> ../../sdd lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD103UJ_S13PJDWS305738-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 11 Sep 5 22:20 ata-SAMSUNG_HD103UJ_S13PJDWS305738-part10 -> ../../sdd10 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD103UJ_S13PJDWS305738-part2 -> ../../sdd2 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD103UJ_S13PJDWS305738-part5 -> ../../sdd5 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD103UJ_S13PJDWS305738-part6 -> ../../sdd6 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD103UJ_S13PJDWS305738-part7 -> ../../sdd7 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD103UJ_S13PJDWS305738-part8 -> ../../sdd8 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD103UJ_S13PJDWS305738-part9 -> ../../sdd9 lrwxrwxrwx 1 root root 9 Sep 5 22:20 ata-SAMSUNG_HD204UI_S2HGJD2B205543 -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD204UI_S2HGJD2B205543-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Sep 5 22:20 ata-SAMSUNG_HD753LJ_S13UJ1DQ203606 -> ../../sda lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD753LJ_S13UJ1DQ203606-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD753LJ_S13UJ1DQ203606-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD753LJ_S13UJ1DQ203606-part4 -> ../../sda4 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD753LJ_S13UJ1DQ203606-part5 -> ../../sda5 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD753LJ_S13UJ1DQ203606-part6 -> ../../sda6 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD753LJ_S13UJ1DQ203606-part7 -> ../../sda7 lrwxrwxrwx 1 root root 10 Sep 5 22:20 ata-SAMSUNG_HD753LJ_S13UJ1DQ203606-part8 -> ../../sda8 lrwxrwxrwx 1 root root 9 Sep 5 22:20 ata-_NEC_DVD_RW_ND-3550A -> ../../sr0 lrwxrwxrwx 1 root root 9 Sep 5 22:20 usb-Intenso_External_USB_3.0_20130303060263-0:0 -> ../../sde lrwxrwxrwx 1 root root 10 Sep 5 22:20 usb-Intenso_External_USB_3.0_20130303060263-0:0-part8 -> ../../sde8 lrwxrwxrwx 1 root root 9 Sep 5 22:20 wwn-0x50000f0009026360 -> ../../sda lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50000f0009026360-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50000f0009026360-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50000f0009026360-part4 -> ../../sda4 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50000f0009026360-part5 -> ../../sda5 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50000f0009026360-part6 -> ../../sda6 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50000f0009026360-part7 -> ../../sda7 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50000f0009026360-part8 -> ../../sda8 lrwxrwxrwx 1 root root 9 Sep 5 22:20 wwn-0x5000cca22bcf90bc -> ../../sdb lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x5000cca22bcf90bc-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Sep 5 22:20 wwn-0x50024e900114746b -> ../../sdd lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50024e900114746b-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 11 Sep 5 22:20 wwn-0x50024e900114746b-part10 -> ../../sdd10 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50024e900114746b-part2 -> ../../sdd2 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50024e900114746b-part5 -> ../../sdd5 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50024e900114746b-part6 -> ../../sdd6 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50024e900114746b-part7 -> ../../sdd7 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50024e900114746b-part8 -> ../../sdd8 lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50024e900114746b-part9 -> ../../sdd9 lrwxrwxrwx 1 root root 9 Sep 5 22:20 wwn-0x50024e9004b62edc -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 5 22:20 wwn-0x50024e9004b62edc-part1 -> ../../sdc1 *********************** END /dev/disk/by-id *********************** BEGIN /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 10 Sep 5 22:20 181acfe7-7f36-427e-8e47-ec7ec3109fe8 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 5 22:20 1a20c3bf-c5cb-4e47-8257-ed9c1eb37b1c -> ../../sdd1 lrwxrwxrwx 1 root root 10 Sep 5 22:20 4b58f6c0-091b-4687-b6c0-26624f0db80c -> ../../sda7 lrwxrwxrwx 1 root root 10 Sep 5 22:20 641fdd27-63f7-4a94-932e-19939323f867 -> ../../sdd5 lrwxrwxrwx 1 root root 10 Sep 5 22:20 67f3ac86-e1e4-48a7-99f2-05af41574a14 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 5 22:20 7759f978-198e-4e5a-8bf7-9e9889452acd -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 5 22:20 7f59312c-b0d2-4c66-bbfd-8c27e37e90d1 -> ../../sde8 lrwxrwxrwx 1 root root 10 Sep 5 22:20 81ea5cac-d2ab-4a13-98de-7e916eb7fabd -> ../../sda6 lrwxrwxrwx 1 root root 10 Sep 5 22:20 8e142806-71de-4647-a317-b2039c25019e -> ../../sdb1 lrwxrwxrwx 1 root root 10 Sep 5 22:20 8eb8e5fc-bdbd-4687-b8eb-408ed1bc9bb3 -> ../../sda8 lrwxrwxrwx 1 root root 11 Sep 5 22:20 b3d9fc92-653a-47b2-96af-fe47c783944a -> ../../sdd10 lrwxrwxrwx 1 root root 10 Sep 5 22:20 cc0e61a2-30f7-48fb-bf2b-5d5a47c2c485 -> ../../sda5 lrwxrwxrwx 1 root root 10 Sep 5 22:20 d62495d6-dd20-4fbb-a96e-42b3c8b7aa83 -> ../../sdd6 lrwxrwxrwx 1 root root 10 Sep 5 22:20 d7c96e65-20ae-4f8d-ba9e-4b5c7aa952cd -> ../../sdd9 lrwxrwxrwx 1 root root 10 Sep 5 22:20 e8b9bad3-aa4c-4424-b208-a4f919fad69e -> ../../sdd8 lrwxrwxrwx 1 root root 10 Sep 5 22:20 f8b1a8b8-9737-4b10-a0ce-8b4b9d448bd4 -> ../../sdd7 *********************** END /dev/disk/by-uuid -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages grub-common depends on: ii gettext-base 0.19.3-2 ii libc6 2.19-18+deb8u1 ii libdevmapper1.02.1 2:1.02.90-2.2 ii libfreetype6 2.5.2-3 ii libfuse2 2.9.3-15+deb8u1 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libpng12-0 1.2.50-2+b2 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages grub-common recommends: ii os-prober 1.65 Versions of packages grub-common suggests: ii console-setup 1.123 ii desktop-base 8.0.2 pn grub-emu pn multiboot-doc pn xorriso -- no debconf information From cattybaby75 at gmail.com Mon Sep 7 01:48:27 2015 From: cattybaby75 at gmail.com (macsek) Date: Mon, 07 Sep 2015 03:48:27 +0200 Subject: Bug#798228: grub-pc: I see in GRUB binaryes stack overflow and OOM errors, I'm traying to send a file's to behold Message-ID: <20150907014827.17228.51450.reportbug@macsek.macsek> Package: grub-pc Version: 2.02~beta2-22 Severity: important Dear Maintainer, GRUB binary files, these seem critical errors; /dev/tty %s: warning: %s: info: %s: error: out of memory error: %s. assert: error stack overflow detected! unknown filesystem unrecognized number overflow is detected (null) %s:%d: source; /usr/sbin/grub-install All GROUB binary file as shown in this error. Thank you, if you look. Regards; cat -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) From owner at bugs.debian.org Mon Sep 7 10:12:04 2015 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 07 Sep 2015 10:12:04 +0000 Subject: Bug#798228: marked as done (grub-pc: I see in GRUB binaryes stack overflow and OOM errors, I'm traying to send a file's to behold) References: <20150907100938.GS2382@riva.ucam.org> <20150907014827.17228.51450.reportbug@macsek.macsek> Message-ID: Your message dated Mon, 7 Sep 2015 11:09:38 +0100 with message-id <20150907100938.GS2382 at riva.ucam.org> and subject line Re: Bug#798228: grub-pc: I see in GRUB binaryes stack overflow and OOM errors, I'm traying to send a file's to behold has caused the Debian Bug report #798228, regarding grub-pc: I see in GRUB binaryes stack overflow and OOM errors, I'm traying to send a file's to behold 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 798228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798228 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: macsek Subject: grub-pc: I see in GRUB binaryes stack overflow and OOM errors, I'm traying to send a file's to behold Date: Mon, 07 Sep 2015 03:48:27 +0200 Size: 3497 URL: -------------- next part -------------- An embedded message was scrubbed... From: Colin Watson Subject: Re: Bug#798228: grub-pc: I see in GRUB binaryes stack overflow and OOM errors, I'm traying to send a file's to behold Date: Mon, 7 Sep 2015 11:09:38 +0100 Size: 3079 URL: From aurelien at aurel32.net Sat Sep 5 22:13:07 2015 From: aurelien at aurel32.net (Aurelien Jarno) Date: Sun, 6 Sep 2015 00:13:07 +0200 Subject: [noreply@buildd.debian.org: failed ppc64el build of grub2 2.02~beta2-27] In-Reply-To: <20150905203438.GP2382@riva.ucam.org> References: <20150905203438.GP2382@riva.ucam.org> Message-ID: <20150905221307.GA18839@aurel32.net> On 2015-09-05 21:34, Colin Watson wrote: > I can't reproduce the attached failure in an unstable chroot on pastel. > One difference I see is that current unstable has gcc-5 5.2.1-16 while > this build log has gcc-5 5.2.1-15. Would it be possible to upgrade the > chroots and try again? (It doesn't really feel like a correct use of a > versioned Build-Depends to me, since if this fixes it then it's really > just a particular buggy version.) Done, let's see how it goes. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien at aurel32.net http://www.aurel32.net From aurelien at aurel32.net Sun Sep 6 08:56:40 2015 From: aurelien at aurel32.net (Aurelien Jarno) Date: Sun, 6 Sep 2015 10:56:40 +0200 Subject: [noreply@buildd.debian.org: failed ppc64el build of grub2 2.02~beta2-27] In-Reply-To: <20150906021744.GA2520@riva.ucam.org> References: <20150905203438.GP2382@riva.ucam.org> <20150905221307.GA18839@aurel32.net> <20150905231112.GQ2382@riva.ucam.org> <20150906021744.GA2520@riva.ucam.org> Message-ID: <20150906085640.GA12675@aurel32.net> On 2015-09-06 03:17, Colin Watson wrote: > On Sun, Sep 06, 2015 at 12:11:12AM +0100, Colin Watson wrote: > > That worked, thanks a lot! > > But then 2.02~beta2-28 failed again on the previous builder: > > https://buildd.debian.org/status/fetch.php?pkg=grub2&arch=ppc64el&ver=2.02~beta2-28&stamp=1441500965&file=log > > I don't suppose you're able to upgrade ppc64el-unicamp-01's chroots? If > not, it would be good to take this on ppc64el-osuosl-01 again. Actually I did a give back with --extra-depends instead of upgrading the chroot. I did the same for the new version, as anyway the chroots are recreated weekly, and the next time is in about 12 hours. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien at aurel32.net http://www.aurel32.net From linn at hpe.com Thu Sep 10 23:10:40 2015 From: linn at hpe.com (Linn Crosetto) Date: Thu, 10 Sep 2015 17:10:40 -0600 Subject: Bug#798607: grub2: docs, mpi, and other cleanup Message-ID: <20150910231040.31726.57480.reportbug@hlinux-build.usa.hp.com> Source: grub2 Version: 2.02~beta2-28 Severity: normal Tags: patch override_dh_clean does not remove all necessary files to rebuild from source using gbp. This cleanup was part of Makefile.in before the conversion to Automake. Example failure message: dpkg-source: error: cannot represent change to grub-core/lib/libgcrypt-grub/mpi/mpih-rshift.c: dpkg-source: error: new version is symlink to generic/mpih-rshift.c dpkg-source: error: old version is plain file [...] dpkg-source: error: unrepresentable changes to source dpkg-buildpackage: error: dpkg-source -i -I -b grub gave error exit status 2 -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-override_dh_clean-cleanup.patch Type: text/x-diff Size: 1643 bytes Desc: not available URL: From cjwatson at debian.org Fri Sep 11 13:21:45 2015 From: cjwatson at debian.org (Colin Watson) Date: Fri, 11 Sep 2015 14:21:45 +0100 Subject: Bug#798607: grub2: docs, mpi, and other cleanup In-Reply-To: <20150910231040.31726.57480.reportbug@hlinux-build.usa.hp.com> References: <20150910231040.31726.57480.reportbug@hlinux-build.usa.hp.com> Message-ID: <20150911132145.GU2382@riva.ucam.org> On Thu, Sep 10, 2015 at 05:10:40PM -0600, Linn Crosetto wrote: > override_dh_clean does not remove all necessary files to rebuild from source > using gbp. I can't guarantee that gbp in general will work since grub2 uses git-dpm for patch management, but I guess this part of it ought to. > diff --git a/debian/rules b/debian/rules > index cc192ce..bf1e003 100755 > --- a/debian/rules > +++ b/debian/rules > @@ -495,6 +495,15 @@ override_dh_auto_clean: > -rm -rf debian/grub-extras-enabled debian/stamps obj > -rm -f contrib grub-core/contrib > > +MPI_CLEAN_FILES = $(patsubst %,grub-core/lib/libgcrypt-grub/mpi/%, \ > + mpi-asm-defs.h mpih-add1.c mpih-sub1.c mpih-mul1.c \ > + mpih-mul2.c mpih-mul3.c mpih-lshift.c mpih-rshift.c) > +DOCS_CLEAN_FILES = $(patsubst %,docs/%, \ > + stamp-vti version.texi stamp-1 version-dev.texi) \ > + $(shell ls docs/*.info) > +CLEAN_FILES = $(MPI_CLEAN_FILES) $(DOCS_CLEAN_FILES) \ > + include/grub/gcrypt/g10lib.h po/grub.pot > + > override_dh_clean: > dh_autoreconf_clean > dh_clean > @@ -506,6 +515,13 @@ override_dh_clean: > done > rm -f debian/grub-common.maintscript > rm -rf debian/tmp-*/ > + > + for i in $(CLEAN_FILES) ; do \ > + if [ -e "$$i" ] || [ -h "$$i" ]; then \ > + rm "$$i"; \ > + fi ; \ > + done > + > ifneq (,$(SB_PACKAGE)) > rm -rf debian/grub2-images > endif This is unnecessarily much code, I think. Could you please send a patch that just adds these file names to debian/clean instead? You can use wildcards. Directories can't be there, but anything that can be removed using "rm -f" can be. Thanks, -- Colin Watson [cjwatson at debian.org] From noreply at release.debian.org Fri Sep 11 16:39:13 2015 From: noreply at release.debian.org (Debian testing watch) Date: Fri, 11 Sep 2015 16:39:13 +0000 Subject: grub2 2.02~beta2-28 MIGRATED to testing Message-ID: FYI: The status of the grub2 source package in Debian's testing distribution has changed. Previous version: 2.02~beta2-26 Current version: 2.02~beta2-28 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. From linn at hpe.com Fri Sep 11 18:56:44 2015 From: linn at hpe.com (Linn Crosetto) Date: Fri, 11 Sep 2015 11:56:44 -0700 Subject: Bug#798607: Patch to debian/clean Message-ID: <20150911185644.GA3154@oranje.usa.hp.com> Here is a patch to debian/clean. I avoided wildcards for some files to be consistent with autogen.sh. -- Linn Crosetto Linux for HP Helion OpenStack -------------- next part -------------- A non-text attachment was scrubbed... Name: v2-0001-Clean-up-docs-mpi-and-other-files.patch Type: text/x-diff Size: 1121 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From owner at bugs.debian.org Fri Sep 11 21:39:20 2015 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 11 Sep 2015 21:39:20 +0000 Subject: Processed: found 673972 in 6.1.24~dfsg-1, found 788253 in gfarm/2.6.6+dfsg-1, found 782156 in 2.02~beta2-28 ... References: <1442007358-3152-bts-anbe@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > found 673972 6.1.24~dfsg-1 Bug #673972 [sympa] sympa: unowned directories after purge: /var/spool/sympa/* Marked as found in versions sympa/6.1.24~dfsg-1. > found 788253 gfarm/2.6.6+dfsg-1 Bug #788253 [dh-systemd] gfsd: unowned files after purge (policy 6.8, 10.8): /var/lib/systemd/deb-systemd-helper-masked/gfsd.service Marked as found in versions gfarm/2.6.6+dfsg-1. > found 782156 2.02~beta2-28 Bug #782156 [grub-xen] grub-xen: unowned files after purge (policy 6.8, 10.8): /boot/grub/{locale, x86_64-xen}/* and some more Marked as found in versions grub2/2.02~beta2-28. > found 782155 2.02~beta2-28 Bug #782155 [grub-pc] grub-pc: unowned files after purge (policy 6.8, 10.8): /boot/grub/unicode.pf2 Marked as found in versions grub2/2.02~beta2-28. > found 798382 4.3+dfsg-2 Bug #798382 [wordpress] wordpress: unowned directory after purge: /var/lib/wordpress/wp-content/languages/ Marked as found in versions wordpress/4.3+dfsg-2. > notfound 789914 fusionforge-web/6.0.2+20150708-1 Bug #789914 {Done: Stefan Fritsch } [apache2] apache2: fails to install: ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It needs to be disabled first! The source fusionforge-web and version 6.0.2+20150708-1 do not appear to match any binary packages No longer marked as found in versions fusionforge-web/6.0.2+20150708-1. > found 770251 ruby-devise-lastseenable/0.0.5.REALLY.0.0.4-1 Bug #770251 [ruby-jbuilder,ruby-responders] ruby-jbuilder,ruby-responders: error when trying to install together Marked as found in versions ruby-devise-lastseenable/0.0.5.REALLY.0.0.4-1. > affects 798453 + plasma-desktop Bug #798453 {Done: Maximiliano Curia } [kinfocenter] kinfocenter: fails to purge: rm: cannot remove '/var/lib/ieee-data/kinfocenter_oui.db': No such file or directory Added indication that 798453 affects plasma-desktop > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was anbe at debian.org). > usertags 794300 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 765592 piuparts Usertags were: broken-symlink adequate. Usertags are now: piuparts broken-symlink adequate. > affects 765592 + libc-dev-bin Bug #765592 [manpages-dev] manpages-dev: broken symlinks /usr/share/man/man3/cerf*.3.gz Bug #773672 [manpages-dev] manpages-dev: broken symlink breaks f.ex. erlang Added indication that 765592 affects libc-dev-bin Added indication that 773672 affects libc-dev-bin > notfound 786773 4.1.10-1 Bug #786773 [ruby-activesupport] ruby-activesupport: Tries to overwrite files from `ruby-activesupport-3.2` There is no source info for the package 'ruby-activesupport' at version '4.1.10-1' with architecture '' Unable to make a source version for version '4.1.10-1' No longer marked as found in versions 4.1.10-1. > found 786773 2:4.1.10-1 Bug #786773 [ruby-activesupport] ruby-activesupport: Tries to overwrite files from `ruby-activesupport-3.2` Marked as found in versions rails/2:4.1.10-1. > found 798712 ruby-activesupport-2.3/2:4.1.8-1 Bug #798712 [ruby] ruby: transitional package ruby-activesupport-2.3 not installable in jessie The source ruby-activesupport-2.3 and version 2:4.1.8-1 do not appear to match any binary packages Marked as found in versions ruby-activesupport-2.3/2:4.1.8-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 673972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673972 765592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765592 770251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770251 773672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773672 782155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782155 782156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782156 786773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786773 788253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788253 789914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789914 798382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798382 798453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798453 798712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798712 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From cjwatson at debian.org Sat Sep 12 16:38:53 2015 From: cjwatson at debian.org (Colin Watson) Date: Sat, 12 Sep 2015 17:38:53 +0100 Subject: Bug#798607: Patch to debian/clean In-Reply-To: <20150911185644.GA3154@oranje.usa.hp.com> References: <20150911185644.GA3154@oranje.usa.hp.com> Message-ID: <20150912163853.GV2382@riva.ucam.org> Control: tag -1 pending On Fri, Sep 11, 2015 at 11:56:44AM -0700, Linn Crosetto wrote: > Here is a patch to debian/clean. I avoided wildcards for some files to be > consistent with autogen.sh. Lovely, thanks. Applied. -- Colin Watson [cjwatson at debian.org] From owner at bugs.debian.org Sat Sep 12 16:42:05 2015 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 12 Sep 2015 16:42:05 +0000 Subject: Processed: Re: Bug#798607: Patch to debian/clean References: <20150912163853.GV2382@riva.ucam.org> <20150910231040.31726.57480.reportbug@hlinux-build.usa.hp.com> Message-ID: Processing control commands: > tag -1 pending Bug #798607 [src:grub2] grub2: docs, mpi, and other cleanup Added tag(s) pending. -- 798607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798607 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From ijc at debian.org Sun Sep 13 07:57:21 2015 From: ijc at debian.org (Ian Campbell) Date: Sun, 13 Sep 2015 08:57:21 +0100 Subject: Bug#782156: grub-xen: unowned files after purge (policy 6.8, 10.8): /boot/grub/{locale, x86_64-xen}/* and some more In-Reply-To: <1430581630.15640.183.camel@debian.org> References: <20150408161636.3196.82367.reportbug@zam581.zam.kfa-juelich.de> <1430581630.15640.183.camel@debian.org> Message-ID: <1442131041.24382.81.camel@debian.org> On Sat, 2015-05-02 at 16:47 +0100, Ian Campbell wrote: > > IMHO either /boot/grub/* should be whitelisted for piuparts (based on > the above argument regarding making systems unbootable) or the existing > debconf template and postrm code for grub-pc should be applied to all > grub-* and not just extended to cover grub-xen. I've made a stab at the latter see: people/ianc/bug782156-purge in the grub package repository. It turns the existing grub -pc/postrm_purge_boot_grub debconf question into grub2/postrm_purge_boot_grub for each grub flavour and tries to cleanup the right common stuff. I lack systems to check for per-variant things though. It's definitely incomplete as it doesn't clean up: /boot/grub/fonts/ /boot/grub/grubenv /boot/grub/locale/ This is because I think they are common to all grub-* variants, so removing them when you purge grub-variantA to install grub-variantB would be incorrect. Perhaps grub-common or grub2-common ought to take care of those. Or perhaps because grub2/postrm_purge_boot_grub is a pretty special use case we should just nuke them from each package. Note that I retained the historical behaviour of grub-pc, which included purging these files. The grub-pc historical case also removes all sorts of other things which no longer appear to exist or where it looks to me that the path is wrong (omits the i386-pc part of the path, but maybe that's a legacy/historical thing). I've attached grub2.piu.tar which contains some helpful wrappers and some piuparts scripts to preseed the cleanup debconf question (which should be deployed on piuparts.d.o I think) and to dump some additional info after things are done. I've also attached grub2.2.02~beta2-28.piuparts.tar.xz and grub2.2.02~beta2-29.piuparts.tar.xz which are a full set of logs with those scripts for 2.02~beta2-28 (released) and the WIP ~2.02~beta2-29 in my branch above. Note that piuparts appears clean in both versions for many of the grub packages when actually they are detecting the lack of whichever environment they are for (EFI, OpenFirmware, etc) and not populating /boot at all. Only grub-xen lacks this behaviour AFAICT. Note that piuparts appears clean in both versions for many of the grub packages when actually they are detecting the lack of whichever environment they are for (EFI, OpenFirmware, etc) and not populating /boot at all. Only grub-xen lacks this behaviour AFAICT. Note that piuparts appears clean in both versions for many of the grub packages when actually they are detecting the lack of whichever environment they are for (EFI, OpenFirmware, etc) and not populating /boot at all. Only grub-xen lacks this detection AFAICT hence this bug because it unconditionally installs things (I believe that is correct for the -xen package). Ian. -------------- next part -------------- A non-text attachment was scrubbed... Name: grub2.piu.tar Type: application/x-tar Size: 10240 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: grub2.2.02~beta2-28.piuparts.tar.xz Type: application/x-xz-compressed-tar Size: 25464 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: grub2.2.02~beta2-29.piuparts.tar.xz Type: application/x-xz-compressed-tar Size: 25024 bytes Desc: not available URL: From sunkan+debian.bugs at zappa.cx Sat Sep 19 16:49:33 2015 From: sunkan+debian.bugs at zappa.cx (Andreas Sundstrom) Date: Sat, 19 Sep 2015 18:49:33 +0200 Subject: Bug#799480: grub-xen-host: XEN domU crash when PV grub chainloads 32-bit domU grub Message-ID: <20150919164933.21200.25954.reportbug@sunkan.zappa.cx> Package: grub-xen-host Version: 2.02~beta2-22 Severity: important Dear Maintainer, Using 64-bit dom0 and 32-bit domU PV (para-virtualized) grub sometimes fail when chainloading the domU's grub. 64-bit domU seem to work 100% of the time. My understanding of the process: * dom0 launches domU with grub that is loaded from dom0's disk. * Grub reads config file from memdisk, and then looks for grub binary in domU filesystem. * If grub is found in domU it then chainloads (multiboot) that grub binary and the domU grub reads grub.cfg and continue booting. * If grub is _not_ found in domU it reads grub.cfg and continues with boot. It fails at step 3 in my list of the boot process, but sometimes it does work so it may be something like a race condition that causes the problem? A workaround is to not install or rename /boot/xen in domU so that the first grub that is loaded from dom0's disk will not find the grub binary in the domU filesystem and hence continues to read grub.cfg and boot. The drawback of this is of course that the two versions can't differ too much as there are different setups creating grub.cfg and then reading/parsing it at boot time. I am not sure at this point whether this is a problem in XEN or a problem in grub but I compiled the legacy pvgrub that uses some minios from XEN (don't really know much more about it) and when that legacy pvgrub chainloads the domU grub it seems to work 100% of the time. Now the legace pvgrub is not a real alternative as it's not packaged for Debian though. When it fails "xl create vm -c" outputs this: Parsing config from /etc/xen/vm libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type for domid=16 Unable to attach console libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1 And "xl dmesg" shows errors like this: (XEN) traps.c:2514:d15 Domain attempted WRMSR 00000000c0010201 from 0x0000000000000000 to 0x000000000000ffff. (XEN) d16:v0: unhandled page fault (ec=0010) (XEN) Pagetable walk from 0000000000000000: (XEN) L4[0x000] = 0000000200256027 000000000000049c (XEN) L3[0x000] = 0000000200255027 000000000000049d (XEN) L2[0x000] = 0000000200251023 00000000000004a1 (XEN) L1[0x000] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S: fault at ffff82d08021feb0 compat_create_bounce_frame+0xc6/0xde (XEN) Domain 16 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.4.1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e019:[<0000000000000000>] (XEN) RFLAGS: 0000000000000246 EM: 1 CONTEXT: pv guest (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) rdx: 0000000000000000 rsi: 0000000000499000 rdi: 0000000000800000 (XEN) rbp: 000000000000000a rsp: 00000000005a5ff0 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: ffff83023e9b9000 r11: ffff83023e9b9000 (XEN) r12: 0000033f3d335bfb r13: ffff82d080300800 r14: ffff82d0802ea940 (XEN) r15: ffff83005e819000 cr0: 000000008005003b cr4: 00000000000506f0 (XEN) cr3: 0000000200b7a000 cr2: 0000000000000000 (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 (XEN) Guest stack trace from esp=005a5ff0: (XEN) 00000010 00000000 0001e019 00010046 0016b38b 0016b38a 0016b389 0016b388 (XEN) 0016b387 0016b386 0016b385 0016b384 0016b383 0016b382 0016b381 0016b380 (XEN) 0016b37f 0016b37e 0016b37d 0016b37c 0016b37b 0016b37a 0016b379 0016b378 (XEN) 0016b377 0016b376 0016b375 0016b374 0016b373 0016b372 0016b371 0016b370 (XEN) 0016b36f 0016b36e 0016b36d 0016b36c 0016b36b 0016b36a 0016b369 0016b368 (XEN) 0016b367 0016b366 0016b365 0016b364 0016b363 0016b362 0016b361 0016b360 (XEN) 0016b35f 0016b35e 0016b35d 0016b35c 0016b35b 0016b35a 0016b359 0016b358 (XEN) 0016b357 0016b356 0016b355 0016b354 0016b353 0016b352 0016b351 0016b350 (XEN) 0016b34f 0016b34e 0016b34d 0016b34c 0016b34b 0016b34a 0016b349 0016b348 (XEN) 0016b347 0016b346 0016b345 0016b344 0016b343 0016b342 0016b341 0016b340 (XEN) 0016b33f 0016b33e 0016b33d 0016b33c 0016b33b 0016b33a 0016b339 0016b338 (XEN) 0016b337 0016b336 0016b335 0016b334 0016b333 0016b332 0016b331 0016b330 (XEN) 0016b32f 0016b32e 0016b32d 0016b32c 0016b32b 0016b32a 0016b329 0016b328 (XEN) 0016b327 0016b326 0016b325 0016b324 0016b323 0016b322 0016b321 0016b320 (XEN) 0016b31f 0016b31e 0016b31d 0016b31c 0016b31b 0016b31a 0016b319 0016b318 (XEN) 0016b317 0016b316 0016b315 0016b314 0016b313 0016b312 0016b311 0016b310 (XEN) 0016b30f 0016b30e 0016b30d 0016b30c 0016b30b 0016b30a 0016b309 0016b308 (XEN) 0016b307 0016b306 0016b305 0016b304 0016b303 0016b302 0016b301 0016b300 (XEN) 0016b2ff 0016b2fe 0016b2fd 0016b2fc 0016b2fb 0016b2fa 0016b2f9 0016b2f8 (XEN) 0016b2f7 0016b2f6 0016b2f5 0016b2f4 0016b2f3 0016b2f2 0016b2f1 0016b2f0 An easy way to find out which grub you are in if the machine boots is to hit 'c' and type 'ls', only the grub from dom0 will know about (memdisk). So when trying to replicate the issue (and the domU actually starts) you can hit 'c', type 'ls' (check for memdisk) and then type 'halt' and relaunch the domU. Usually I can't launch more than 4-5 times in a row before it fails, often it fails on my first try. For information I have reproduced on two different AMD desktop processor machines, not sure if Intel would be any different. I'm pretty sure I did tests with grub from unstable with same result at some point, but can test again if that is likely to work. The package that is in installed on the domU side is "grub-xen". I am unable to understand how to debug grub further on my own, I have printed out text from grub so that I understood that it is the chainload that fails. I see no output from the domU grub (except when it works as it should of course). I can help with further testing if needed. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages grub-xen-host depends on: ii grub-xen-bin 2.02~beta2-22 grub-xen-host recommends no packages. grub-xen-host suggests no packages. -- no debconf information /Andreas From ijc at hellion.org.uk Sun Sep 20 16:51:14 2015 From: ijc at hellion.org.uk (Ian Campbell) Date: Sun, 20 Sep 2015 17:51:14 +0100 Subject: Bug#799480: grub-xen-host: XEN domU crash when PV grub chainloads 32-bit domU grub In-Reply-To: <20150919164933.21200.25954.reportbug@sunkan.zappa.cx> References: <20150919164933.21200.25954.reportbug@sunkan.zappa.cx> Message-ID: <1442767874.24382.139.camel@hellion.org.uk> On Sat, 2015-09-19 at 18:49 +0200, Andreas Sundstrom wrote: > Package: grub-xen-host > Version: 2.02~beta2-22 > Severity: important > > Dear Maintainer, > > Using 64-bit dom0 and 32-bit domU PV (para-virtualized) grub sometimes > fail when chainloading the domU's grub. 64-bit domU seem to work 100% > of the time. Which grub are you starting with from dom0? If you want to boot a 32-bit guest (which includes chainloading a 32 -bit grub) then you must start with the 32-bit grub-i386-xen.bin grub binary to create a 32-bit guest. kexecing from 64-bit to 32-bit is not possible in the general case. In fact I thought it was _impossible_ in all cases and would have ruled it out as something you might be doing, except some of these registers look like 64-bit values: > (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000 > (XEN) rdx: 0000000000000000 rsi: 0000000000499000 rdi: 0000000000800000 > (XEN) rbp: 000000000000000a rsp: 00000000005a5ff0 r8: 0000000000000000 > (XEN) r9: 0000000000000000 r10: ffff83023e9b9000 r11: ffff83023e9b9000 > (XEN) r12: 0000033f3d335bfb r13: ffff82d080300800 r14: ffff82d0802ea940 > (XEN) r15: ffff83005e819000 cr0: 000000008005003b cr4: 00000000000506f0 > (XEN) cr3: 0000000200b7a000 cr2: 0000000000000000 Ian. From ijc at hellion.org.uk Sun Sep 20 16:51:14 2015 From: ijc at hellion.org.uk (Ian Campbell) Date: Sun, 20 Sep 2015 17:51:14 +0100 Subject: Bug#799480: grub-xen-host: XEN domU crash when PV grub chainloads 32-bit domU grub In-Reply-To: <20150919164933.21200.25954.reportbug@sunkan.zappa.cx> References: <20150919164933.21200.25954.reportbug@sunkan.zappa.cx> Message-ID: <1442767874.24382.139.camel@hellion.org.uk> On Sat, 2015-09-19 at 18:49 +0200, Andreas Sundstrom wrote: > Package: grub-xen-host > Version: 2.02~beta2-22 > Severity: important > > Dear Maintainer, > > Using 64-bit dom0 and 32-bit domU PV (para-virtualized) grub sometimes > fail when chainloading the domU's grub. 64-bit domU seem to work 100% > of the time. Which grub are you starting with from dom0? If you want to boot a 32-bit guest (which includes chainloading a 32 -bit grub) then you must start with the 32-bit grub-i386-xen.bin grub binary to create a 32-bit guest. kexecing from 64-bit to 32-bit is not possible in the general case. In fact I thought it was _impossible_ in all cases and would have ruled it out as something you might be doing, except some of these registers look like 64-bit values: > (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000 > (XEN) rdx: 0000000000000000 rsi: 0000000000499000 rdi: 0000000000800000 > (XEN) rbp: 000000000000000a rsp: 00000000005a5ff0 r8: 0000000000000000 > (XEN) r9: 0000000000000000 r10: ffff83023e9b9000 r11: ffff83023e9b9000 > (XEN) r12: 0000033f3d335bfb r13: ffff82d080300800 r14: ffff82d0802ea940 > (XEN) r15: ffff83005e819000 cr0: 000000008005003b cr4: 00000000000506f0 > (XEN) cr3: 0000000200b7a000 cr2: 0000000000000000 Ian. From sunkan+debian.bugs at zappa.cx Sun Sep 20 18:15:33 2015 From: sunkan+debian.bugs at zappa.cx (Andreas Sundstrom) Date: Sun, 20 Sep 2015 20:15:33 +0200 Subject: Bug#799480: grub-xen-host: XEN domU crash when PV grub chainloads 32-bit domU grub In-Reply-To: <1442767874.24382.139.camel@hellion.org.uk> References: <20150919164933.21200.25954.reportbug@sunkan.zappa.cx> <1442767874.24382.139.camel@hellion.org.uk> Message-ID: <55FEF7C5.3090801@zappa.cx> On 2015-09-20 18:51, Ian Campbell wrote: > On Sat, 2015-09-19 at 18:49 +0200, Andreas Sundstrom wrote: >> Package: grub-xen-host >> Version: 2.02~beta2-22 >> Severity: important >> >> Dear Maintainer, >> >> Using 64-bit dom0 and 32-bit domU PV (para-virtualized) grub sometimes >> fail when chainloading the domU's grub. 64-bit domU seem to work 100% >> of the time. > Which grub are you starting with from dom0? > > If you want to boot a 32-bit guest (which includes chainloading a 32 > -bit grub) then you must start with the 32-bit grub-i386-xen.bin grub > binary to create a 32-bit guest. > > kexecing from 64-bit to 32-bit is not possible in the general case. In > fact I thought it was _impossible_ in all cases and would have ruled it > out as something you might be doing, except some of these registers > look like 64-bit values: As you say it has not been possible at any time to use 64-bit grub from dom0 and then load either 32-bit grub or linux kernel from domU. I am using /usr/lib/grub-xen/grub-i386-xen.bin when I start my i386 domU's Thanks for your great blog entry about this by the way: https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/ I have used it to get a better understanding of the whole process. >> (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: > 0000000000000000 >> (XEN) rdx: 0000000000000000 rsi: 0000000000499000 rdi: 0000000000800000 >> (XEN) rbp: 000000000000000a rsp: 00000000005a5ff0 r8: 0000000000000000 >> (XEN) r9: 0000000000000000 r10: ffff83023e9b9000 r11: ffff83023e9b9000 >> (XEN) r12: 0000033f3d335bfb r13: ffff82d080300800 r14: ffff82d0802ea940 >> (XEN) r15: ffff83005e819000 cr0: 000000008005003b cr4: 00000000000506f0 >> (XEN) cr3: 0000000200b7a000 cr2: 0000000000000000 Well I don't know but I guess the XEN hypervisor is always running in 64-bit mode yes? I suppose that maybe even if the domU is 32-bit any errors showing up in "xl dmesg" reflects the mode that the hypervisor is run in? /Andreas From lgp171188 at gmail.com Sun Sep 20 18:40:56 2015 From: lgp171188 at gmail.com (L. Guruprasad) Date: Mon, 21 Sep 2015 00:10:56 +0530 Subject: Bug#799598: grub2-common: options documentation duplicated in the grub-install manpage Message-ID: <20150920184056.7192.95272.reportbug@kal-el.lguruprasad.in> Package: grub2-common Version: 2.02~beta2-28 Severity: minor Dear Maintainer, In the manpage of the grub-install command, the documentation for all the options is repeated from the beginning after the -s, --skip-fs-probe option. -- Package-specific info: *********************** BEGIN /proc/mounts /dev/sda6 / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/sda7 /home ext4 rw,relatime,data=ordered 0 0 /dev/sdb1 /media/guruprasad/UUI vfat rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,showexec,utf8,flush,errors=remount-ro 0 0 *********************** END /proc/mounts *********************** BEGIN /boot/grub/device.map (hd0) /dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_071213BB0F00WDH3MKZC (hd1) /dev/disk/by-id/usb-JetFlash_Transcend_32GB_522542879-0:0 *********************** END /boot/grub/device.map *********************** BEGIN /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then set have_grubenv=true load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="0" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod part_msdos insmod ext2 set root='hd0,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6 --hint='hd0,msdos6' e4f0f32b-3a48-4d1c-9263-406c49393cbb else search --no-floppy --fs-uuid --set=root e4f0f32b-3a48-4d1c-9263-406c49393cbb fi font="/usr/share/grub/unicode.pf2" fi if loadfont $font ; then set gfxmode=1440x900x32 load_video insmod gfxterm set locale_dir=$prefix/locale set lang=en_IN insmod gettext fi terminal_output gfxterm if [ "${recordfail}" = 1 ] ; then set timeout=30 else if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/05_debian_theme ### insmod part_msdos insmod ext2 set root='hd0,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6 --hint='hd0,msdos6' e4f0f32b-3a48-4d1c-9263-406c49393cbb else search --no-floppy --fs-uuid --set=root e4f0f32b-3a48-4d1c-9263-406c49393cbb fi insmod png if background_image /usr/share/images/desktop-base/lines-grub.png; then set color_normal=white/black set color_highlight=black/white else set menu_color_normal=cyan/blue set menu_color_highlight=white/blue fi ### END /etc/grub.d/05_debian_theme ### ### BEGIN /etc/grub.d/10_linux ### function gfxmode { set gfxpayload="${1}" } set linux_gfx_mode= export linux_gfx_mode menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e4f0f32b-3a48-4d1c-9263-406c49393cbb' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6 --hint='hd0,msdos6' e4f0f32b-3a48-4d1c-9263-406c49393cbb else search --no-floppy --fs-uuid --set=root e4f0f32b-3a48-4d1c-9263-406c49393cbb fi echo 'Loading Linux 4.1.0-2-amd64 ...' linux /boot/vmlinuz-4.1.0-2-amd64 root=UUID=e4f0f32b-3a48-4d1c-9263-406c49393cbb ro quiet splash echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-4.1.0-2-amd64 } submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-e4f0f32b-3a48-4d1c-9263-406c49393cbb' { menuentry 'Debian GNU/Linux, with Linux 4.1.0-2-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.1.0-2-amd64-advanced-e4f0f32b-3a48-4d1c-9263-406c49393cbb' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6 --hint='hd0,msdos6' e4f0f32b-3a48-4d1c-9263-406c49393cbb else search --no-floppy --fs-uuid --set=root e4f0f32b-3a48-4d1c-9263-406c49393cbb fi echo 'Loading Linux 4.1.0-2-amd64 ...' linux /boot/vmlinuz-4.1.0-2-amd64 root=UUID=e4f0f32b-3a48-4d1c-9263-406c49393cbb ro quiet splash echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-4.1.0-2-amd64 } menuentry 'Debian GNU/Linux, with Linux 4.1.0-2-amd64 (sysvinit)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.1.0-2-amd64-init-sysvinit-e4f0f32b-3a48-4d1c-9263-406c49393cbb' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6 --hint='hd0,msdos6' e4f0f32b-3a48-4d1c-9263-406c49393cbb else search --no-floppy --fs-uuid --set=root e4f0f32b-3a48-4d1c-9263-406c49393cbb fi echo 'Loading Linux 4.1.0-2-amd64 ...' linux /boot/vmlinuz-4.1.0-2-amd64 root=UUID=e4f0f32b-3a48-4d1c-9263-406c49393cbb ro quiet splash init=/lib/sysvinit/init echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-4.1.0-2-amd64 } menuentry 'Debian GNU/Linux, with Linux 4.1.0-1-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.1.0-1-amd64-advanced-e4f0f32b-3a48-4d1c-9263-406c49393cbb' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6 --hint='hd0,msdos6' e4f0f32b-3a48-4d1c-9263-406c49393cbb else search --no-floppy --fs-uuid --set=root e4f0f32b-3a48-4d1c-9263-406c49393cbb fi echo 'Loading Linux 4.1.0-1-amd64 ...' linux /boot/vmlinuz-4.1.0-1-amd64 root=UUID=e4f0f32b-3a48-4d1c-9263-406c49393cbb ro quiet splash echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-4.1.0-1-amd64 } menuentry 'Debian GNU/Linux, with Linux 4.1.0-1-amd64 (sysvinit)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.1.0-1-amd64-init-sysvinit-e4f0f32b-3a48-4d1c-9263-406c49393cbb' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6 --hint='hd0,msdos6' e4f0f32b-3a48-4d1c-9263-406c49393cbb else search --no-floppy --fs-uuid --set=root e4f0f32b-3a48-4d1c-9263-406c49393cbb fi echo 'Loading Linux 4.1.0-1-amd64 ...' linux /boot/vmlinuz-4.1.0-1-amd64 root=UUID=e4f0f32b-3a48-4d1c-9263-406c49393cbb ro quiet splash init=/lib/sysvinit/init echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-4.1.0-1-amd64 } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'Windows 8 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-8432864E328644E0' { insmod part_msdos insmod ntfs set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 8432864E328644E0 else search --no-floppy --fs-uuid --set=root 8432864E328644E0 fi parttool ${root} hidden- drivemap -s (hd0) ${root} chainloader +1 } ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/30_uefi-firmware ### ### END /etc/grub.d/30_uefi-firmware ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### *********************** END /boot/grub/grub.cfg *********************** BEGIN /proc/mdstat cat: /proc/mdstat: No such file or directory *********************** END /proc/mdstat *********************** BEGIN /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 Sep 20 23:34 ata-Hitachi_HTS542525K9SA00_071213BB0F00WDH3MKZC -> ../../sda lrwxrwxrwx 1 root root 10 Sep 20 23:34 ata-Hitachi_HTS542525K9SA00_071213BB0F00WDH3MKZC-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 20 23:34 ata-Hitachi_HTS542525K9SA00_071213BB0F00WDH3MKZC-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 20 23:34 ata-Hitachi_HTS542525K9SA00_071213BB0F00WDH3MKZC-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Sep 20 23:34 ata-Hitachi_HTS542525K9SA00_071213BB0F00WDH3MKZC-part5 -> ../../sda5 lrwxrwxrwx 1 root root 10 Sep 20 23:34 ata-Hitachi_HTS542525K9SA00_071213BB0F00WDH3MKZC-part6 -> ../../sda6 lrwxrwxrwx 1 root root 10 Sep 20 23:34 ata-Hitachi_HTS542525K9SA00_071213BB0F00WDH3MKZC-part7 -> ../../sda7 lrwxrwxrwx 1 root root 9 Sep 20 23:34 ata-Slimtype_DVD_A_DS8A1H_710310004953 -> ../../sr0 lrwxrwxrwx 1 root root 9 Sep 20 23:34 usb-JetFlash_Transcend_2GB_WN1XC1OO-0:0 -> ../../sdb lrwxrwxrwx 1 root root 10 Sep 20 23:34 usb-JetFlash_Transcend_2GB_WN1XC1OO-0:0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Sep 20 23:34 wwn-0x5000cca533cfbe1e -> ../../sda lrwxrwxrwx 1 root root 10 Sep 20 23:34 wwn-0x5000cca533cfbe1e-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 20 23:34 wwn-0x5000cca533cfbe1e-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 20 23:34 wwn-0x5000cca533cfbe1e-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Sep 20 23:34 wwn-0x5000cca533cfbe1e-part5 -> ../../sda5 lrwxrwxrwx 1 root root 10 Sep 20 23:34 wwn-0x5000cca533cfbe1e-part6 -> ../../sda6 lrwxrwxrwx 1 root root 10 Sep 20 23:34 wwn-0x5000cca533cfbe1e-part7 -> ../../sda7 *********************** END /dev/disk/by-id *********************** BEGIN /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 10 Sep 20 23:34 1d7f0a92-bfc0-4b92-8532-d4c2999feb7b -> ../../sda5 lrwxrwxrwx 1 root root 9 Sep 20 23:34 2014-05-19-06-54-05-00 -> ../../sdb lrwxrwxrwx 1 root root 10 Sep 20 23:34 7080BFB180BF7C62 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 20 23:34 96E2-E634 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Sep 20 23:34 9df505fb-dc1c-40ca-8d6c-734e9370eed5 -> ../../sda7 lrwxrwxrwx 1 root root 10 Sep 20 23:34 DCAAA3DFAAA3B484 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 20 23:34 e4f0f32b-3a48-4d1c-9263-406c49393cbb -> ../../sda6 *********************** END /dev/disk/by-uuid -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages grub2-common depends on: ii dpkg 1.18.2 ii grub-common 2.02~beta2-28 ii install-info 6.0.0.dfsg.1-3 ii libc6 2.19-20 ii libdevmapper1.02.1 2:1.02.104-1 ii liblzma5 5.1.1alpha+20120614-2.1 grub2-common recommends no packages. grub2-common suggests no packages. -- no debconf information From sunkan+debian.bugs at zappa.cx Sun Sep 20 18:15:33 2015 From: sunkan+debian.bugs at zappa.cx (Andreas Sundstrom) Date: Sun, 20 Sep 2015 20:15:33 +0200 Subject: Bug#799480: grub-xen-host: XEN domU crash when PV grub chainloads 32-bit domU grub In-Reply-To: <1442767874.24382.139.camel@hellion.org.uk> References: <20150919164933.21200.25954.reportbug@sunkan.zappa.cx> <1442767874.24382.139.camel@hellion.org.uk> Message-ID: <55FEF7C5.3090801@zappa.cx> On 2015-09-20 18:51, Ian Campbell wrote: > On Sat, 2015-09-19 at 18:49 +0200, Andreas Sundstrom wrote: >> Package: grub-xen-host >> Version: 2.02~beta2-22 >> Severity: important >> >> Dear Maintainer, >> >> Using 64-bit dom0 and 32-bit domU PV (para-virtualized) grub sometimes >> fail when chainloading the domU's grub. 64-bit domU seem to work 100% >> of the time. > Which grub are you starting with from dom0? > > If you want to boot a 32-bit guest (which includes chainloading a 32 > -bit grub) then you must start with the 32-bit grub-i386-xen.bin grub > binary to create a 32-bit guest. > > kexecing from 64-bit to 32-bit is not possible in the general case. In > fact I thought it was _impossible_ in all cases and would have ruled it > out as something you might be doing, except some of these registers > look like 64-bit values: As you say it has not been possible at any time to use 64-bit grub from dom0 and then load either 32-bit grub or linux kernel from domU. I am using /usr/lib/grub-xen/grub-i386-xen.bin when I start my i386 domU's Thanks for your great blog entry about this by the way: https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/ I have used it to get a better understanding of the whole process. >> (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: > 0000000000000000 >> (XEN) rdx: 0000000000000000 rsi: 0000000000499000 rdi: 0000000000800000 >> (XEN) rbp: 000000000000000a rsp: 00000000005a5ff0 r8: 0000000000000000 >> (XEN) r9: 0000000000000000 r10: ffff83023e9b9000 r11: ffff83023e9b9000 >> (XEN) r12: 0000033f3d335bfb r13: ffff82d080300800 r14: ffff82d0802ea940 >> (XEN) r15: ffff83005e819000 cr0: 000000008005003b cr4: 00000000000506f0 >> (XEN) cr3: 0000000200b7a000 cr2: 0000000000000000 Well I don't know but I guess the XEN hypervisor is always running in 64-bit mode yes? I suppose that maybe even if the domU is 32-bit any errors showing up in "xl dmesg" reflects the mode that the hypervisor is run in? /Andreas From ijc at debian.org Mon Sep 21 09:51:12 2015 From: ijc at debian.org (Ian Campbell) Date: Mon, 21 Sep 2015 10:51:12 +0100 Subject: Bug#799480: grub-xen-host: XEN domU crash when PV grub chainloads 32-bit domU grub In-Reply-To: <55FEF7C5.3090801@zappa.cx> References: <20150919164933.21200.25954.reportbug@sunkan.zappa.cx> <1442767874.24382.139.camel@hellion.org.uk> <55FEF7C5.3090801@zappa.cx> Message-ID: <1442829072.10338.40.camel@debian.org> On Sun, 2015-09-20 at 20:15 +0200, Andreas Sundstrom wrote: > On 2015-09-20 18:51, Ian Campbell wrote: > > On Sat, 2015-09-19 at 18:49 +0200, Andreas Sundstrom wrote: > > > Package: grub-xen-host > > > Version: 2.02~beta2-22 > > > Severity: important > > > > > > Dear Maintainer, > > > > > > Using 64-bit dom0 and 32-bit domU PV (para-virtualized) grub > > > sometimes > > > fail when chainloading the domU's grub. 64-bit domU seem to work 100% > > > of the time. > > Which grub are you starting with from dom0? > > > > If you want to boot a 32-bit guest (which includes chainloading a 32 > > -bit grub) then you must start with the 32-bit grub-i386-xen.bin grub > > binary to create a 32-bit guest. > > > > kexecing from 64-bit to 32-bit is not possible in the general case. In > > fact I thought it was _impossible_ in all cases and would have ruled it > > out as something you might be doing, except some of these registers > > look like 64-bit values: > > As you say it has not been possible at any time to use 64-bit grub from > dom0 and then load either 32-bit grub or linux kernel from domU. > > I am using /usr/lib/grub-xen/grub-i386-xen.bin when I start my i386 > domU's OK good (well, bad, because now I have no idea what is going wrong...) > Thanks for your great blog entry about this by the way: > https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-x > en-pv-guests/ > I have used it to get a better understanding of the whole process. > > > (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: > > 0000000000000000 > > > (XEN) rdx: 0000000000000000 rsi: 0000000000499000 rdi: > > > 0000000000800000 > > > (XEN) rbp: 000000000000000a rsp: 00000000005a5ff0 r8: > > > 0000000000000000 > > > (XEN) r9: 0000000000000000 r10: ffff83023e9b9000 r11: > > > ffff83023e9b9000 > > > (XEN) r12: 0000033f3d335bfb r13: ffff82d080300800 r14: > > > ffff82d0802ea940 > > > (XEN) r15: ffff83005e819000 cr0: 000000008005003b cr4: > > > 00000000000506f0 > > > (XEN) cr3: 0000000200b7a000 cr2: 0000000000000000 > Well I don't know but I guess the XEN hypervisor is always running in > 64-bit mode yes? > I suppose that maybe even if the domU is 32-bit any errors showing up in > "xl dmesg" > reflects the mode that the hypervisor is run in? I think it's supposed to reflect the mode which the processor is in at the time. I trimmed the quotes but there was a line in the dump which said: (XEN) RFLAGS: 0000000000000246 EM: 1 CONTEXT: pv guest Suggesting that this was guest context (this string doesn't distinguish 32- from 64-bit). Actually, I just spotted: (XEN) domain_crash_sync called from entry.S: fault at ffff82d08021feb0 compat_create_bounce_frame+0xc6/0xde where compat == 32-bit, so that bit is correct. So I think the large register values are a red-herring. I think it would be worth reporting this to upstream (both Xen and Grub), would you mind doing so? Ian. From sunkan+debian.bugs at zappa.cx Mon Sep 21 12:00:42 2015 From: sunkan+debian.bugs at zappa.cx (Andreas Sundstrom) Date: Mon, 21 Sep 2015 12:00:42 +0000 Subject: Bug#799480: grub-xen-host: XEN domU crash when PV grub chainloads 32-bit domU grub In-Reply-To: <1442829072.10338.40.camel@debian.org> References: <20150919164933.21200.25954.reportbug@sunkan.zappa.cx> <1442767874.24382.139.camel@hellion.org.uk> <55FEF7C5.3090801@zappa.cx> <1442829072.10338.40.camel@debian.org> Message-ID: <20150921120042.Horde.QsJU3QLroaVH8f8fes-R2YK@apache.zappa.cx> Citerar Ian Campbell : > Actually, I just spotted: > (XEN) domain_crash_sync called from entry.S: fault at > ffff82d08021feb0 compat_create_bounce_frame+0xc6/0xde > > where compat == 32-bit, so that bit is correct. > > So I think the large register values are a red-herring. > > I think it would be worth reporting this to upstream (both Xen and Grub), > would you mind doing so? Ok, I will try my best. /Andreas From ravirjoshi at hotmail.com Mon Sep 21 17:42:06 2015 From: ravirjoshi at hotmail.com (Ravi Joshi) Date: Mon, 21 Sep 2015 23:12:06 +0530 Subject: GRUB 2 RFH Message-ID: Hello, Any help required with GRUB? -------------- next part -------------- An HTML attachment was scrubbed... URL: From fzielcke at z-51.de Tue Sep 22 17:18:34 2015 From: fzielcke at z-51.de (Felix Zielcke) Date: Tue, 22 Sep 2015 19:18:34 +0200 Subject: GRUB 2 RFH In-Reply-To: References: Message-ID: <1442942314.9461.1.camel@z-51.de> Am Montag, den 21.09.2015, 23:12 +0530 schrieb Ravi Joshi: > Hello, > Any help required with GRUB? Hi, you're always welcome to help out with the open bug reports From mitchell at wyatt672earp.force9.co.uk Wed Sep 23 15:41:12 2015 From: mitchell at wyatt672earp.force9.co.uk (Mitchell) Date: Wed, 23 Sep 2015 16:41:12 +0100 Subject: Bug#799873: grub: GRUB Booting Delay Debian 8.x.x Message-ID: <20150923154112.19123.43458.reportbug@a780.lan> Package: grub Version: Debian 8.2.0 Severity: normal Tags: d-i Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: 7.8 Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Installed Debian 8.x.x using GPT, both i386 & amd64. Whichever first installed suffered a "Start Job" delay while booting GRUB. Just annoying. From darryl.underwood at rbn.kz Sun Sep 27 23:00:30 2015 From: darryl.underwood at rbn.kz (District Court) Date: Mon, 28 Sep 2015 05:00:30 +0600 Subject: Bug#735935: Notice of appearance in Court #0000367169 Message-ID: <1ce486cb37b261d6622db45023d18acd@rbn.kz> Notice to Appear, You have to appear in the Court on the October 05. You are kindly asked to prepare and bring the documents relating to the case to Court on the specified date. Note: The case may be heard by the judge in your absence if you do not come. You can find the Court Notice is in the attachment. Kind regards, Darryl Underwood, District Clerk. -------------- next part -------------- A non-text attachment was scrubbed... Name: Court_Notification_0000367169.zip Type: application/zip Size: 3192 bytes Desc: not available URL: