[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#844749: marked as done (live-build: Jessie image with backported kernel (linux-image-4.7.0-0.bpo.1-amd64) doesn't boot)



Your message dated Fri, 25 Aug 2023 23:00:18 +0200
with message-id <4f72c97e-b6b9-471f-b06f-2d7e698fa3d5@rclobus.nl>
and subject line Bug report cleanup
has caused the Debian Bug report #844749,
regarding live-build: Jessie image with backported kernel (linux-image-4.7.0-0.bpo.1-amd64) doesn't boot
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@bugs.debian.org
immediately.)


-- 
844749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844749
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: live-build
Version: 4.0.3-1
Severity: important

Dear Maintainer,

   * I'm trying to build live Jessie image with backported kernel. 
     Kernel version: linux-image-4.7.0-0.bpo.1-amd64

   * Steps to reproduce:
   lb config noauto \
   	--apt-indices false \
   	--apt-source-archives false \
   	--architectures amd64 \
   	--bootstrap debootstrap \
   	--backports true \
   	--linux-packages linux-image-4.7.0-0.bpo.1 \
   	--debian-installer false \
   	--system live \
   	--iso-application "xxxxxxxxx" \
   	--iso-publisher "xxxxxxxxx" \
   	--iso-volume "xxxxxxxxx" \
   	--archive-areas "main contrib non-free" \
   	--source false \
   	--memtest none \
   	--verbose \
   	--debug \
   	--win32-loader false \
   	--updates true \
   	--firmware-chroot true \
   	--firmware-binary true \
   	--bootappend-live "boot=live config live-config.utc=no" \
   	--binary-filesystem fat32 \
   	--binary-images hdd \
   	--zsync false 
   
   echo "linux-base/jessie-backports" > config/package-lists/jessie-backports.list.chroot
   lb build 2>&1 | tee build.log
   
   Then I was trying to boot kvm from this image.

   * This leads to:
   Image boots, then after a while during booting kernel and initrd I see messages like this:
   ---------------------------
   [    2.971437] cloclsource: Switched to clocksource tsc
   [    2.974235] FAT-fs (sda1): IO charset ascii not found
   mount: mounting /dev/sda1 on /live/medium failed: Invalid argument
      ....  skipped similar lines ....
   [   63.554664] FAT-fs (sda1): IO charset ascii not found
   mount: mounting /dev/sda1 on /live/medium failed: Invalid argument
   ---------------------------
   and boot process exits to initrd's BusyBox prompt.

   * Expected result:
   Normal kernel boot process, leading to bash prompt.

   I've changed /usr/lib/live/build/binary_hdd file, but this was nesessary to fix other bug in debian-live:
   https://lists.debian.org/debian-live/2014/12/msg00122.htmlhttps://lists.debian.org/debian-live/2014/12/msg00122.html

-- Package-specific info:

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages live-build depends on:
ii  debootstrap  1.0.67

Versions of packages live-build recommends:
ii  cpio                            2.11+dfsg-4.1+deb8u1
ii  live-boot-doc                   4.0.2-1
ii  live-config-doc                 4.0.4-1
ii  live-manual-html [live-manual]  1:4.0.1-1

live-build suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/lib/live/build/binary_hdd (from live-build package)

--- End Message ---
--- Begin Message --- This bug report refers to Jessie, which is now some years out of LTS (but Freexian still offers ELTS)

If you still need this, please reopen this bug report.

With kind regards,
Roland Clobus

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply to: