Bug#804351: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue
On Tue, 2015-11-10 at 01:08 +, Ben Hutchings wrote: > On Mon, 2015-11-09 at 14:18 -0800, Martin Michlmayr wrote: > > * Ian Campbell [2015-11-09 08:37]: > > > It might be the same issue as this recent installation report: > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804351 > > > > > > I've not had a chance to dig into what is going on there. Often > this > > > kind of thing turns out to be an upstream change to the modules > > > (different config options, splitting modules into more fine > grained > > > parts) which requires tweaks to the kernel config, or initramfs > -tools > > > or to the kernel udebs for the installer. > > > > There was a report on the QNAP forum about a QNAP no longer booting > > after an update. The logs says: > > > > [8.697480] sdb: sdb1 > > [8.702144] sda: sda1 sda2 sda3 > > [8.705613] sd 1:0:0:0: [sdb] Attached SCSI disk > > [8.713159] sd 0:0:0:0: [sda] Attached SCSI disk > > Begin: Loading essential drivers ... modprobe: module > of:NocpTCsimple-bus not found in modules.dep > > modprobe: module of:NgpioTCmarvell,orion-gpio not found in > modules.dep > > modprobe: module of:NocpTCsimple-bus not found in modules.dep > > modprobe: module of:NgpioTCmarvell,orion-gpio not found in > modules.dep > > modprobe: module of:NocpTCsimple-bus not found in modules.dep > > modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not > found in modules.dep > > modprobe: module of:NocpTCsimple-bus not found in modules.dep > > modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in > modules.dep > > modprobe: module of:NocpTCsimple-bus not found in modules.dep > > modprobe: module platform:reg-dummy not found in modules.dep > > done. > > Begin: Running /scripts/init-premount ... done. > > ... > > [ and then the UUID is not found ] > > > > Any idea what these messages about modules.dep are about? > > All those modaliases correspond to devices whose drivers are built-in. > So it's not surprising that they're not found in modules.dep, and I > don't think this has anything to do with the failure. Indeed, I've been seeing them for a while and I don't believe they are anything more than a cosmetic issue. Ian.
Re: Migrating from fonts-droid to fonts-noto
Christian PERRIER writes: > Quoting Vasudev Kamath (vasu...@copyninja.info): > >> > Is this change going to impact the fonts-android-udeb binary package >> > which is now being used within the Debian Installer? >> >> No, as of now upstream git repository of android source provides 2 >> fallback variants DroidSansFallback and DroidSansFallbackFull along with >> DroidSansMono. So this should not be a problem. > > > I think that Kibi's point is more asking "will you rename the udeb > package", which would then require a change in the D-I build > scripts Ah okay. No I will not rename the package. Only change I'm thinking to do is change the font shipped by udeb, currently it ships DroidSansFallback. I'm thinking of changing it to DroidSansFallbackFull will this cause any problems?.
Re: [Pkg-fonts-devel] Migrating from fonts-droid to fonts-noto
Quoting Vasudev Kamath (2015-11-10 09:39:36) > Christian PERRIER writes: > >> Quoting Vasudev Kamath (vasu...@copyninja.info): >> Is this change going to impact the fonts-android-udeb binary package which is now being used within the Debian Installer? >>> >>> No, as of now upstream git repository of android source provides 2 >>> fallback variants DroidSansFallback and DroidSansFallbackFull along >>> with DroidSansMono. So this should not be a problem. >> >> >> I think that Kibi's point is more asking "will you rename the udeb >> package", which would then require a change in the D-I build >> scripts > > Ah okay. No I will not rename the package. > > Only change I'm thinking to do is change the font shipped by udeb, > currently it ships DroidSansFallback. I'm thinking of changing it to > DroidSansFallbackFull will this cause any problems?. Seems change of font within that udeb can be done in independent of and thus tracked as a separate bug than the issue of migrating non-fallback fonts to Noto. I.e. need not delay the transition and need only be discussed with those directly involved - no need for distro-wide discussion of that :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Migrating from fonts-droid to fonts-noto
Hi, Vasudev Kamath (2015-11-10): > Cyril Brulebois writes: > > Is this change going to impact the fonts-android-udeb binary package > > which is now being used within the Debian Installer? > > No, as of now upstream git repository of android source provides 2 > fallback variants DroidSansFallback and DroidSansFallbackFull along with > DroidSansMono. So this should not be a problem. OK, thanks for your quick reply! Mraw, KiBi. signature.asc Description: Digital signature
Re: Migrating from fonts-droid to fonts-noto
Vasudev Kamath (2015-11-10): > Christian PERRIER writes: > > I think that Kibi's point is more asking "will you rename the udeb > > package", which would then require a change in the D-I build > > scripts > > Ah okay. No I will not rename the package. OK. And yeah, that's mainly what I had in mind. :) > Only change I'm thinking to do is change the font shipped by udeb, > currently it ships DroidSansFallback. I'm thinking of changing it to > DroidSansFallbackFull will this cause any problems?. Some fonts are listed in src/usr/bin/gtk-set-font in src:rootskel-gtk (which has a mapping from language to font name), but there's nothing there for Droid, so as long as the fallback thing works automatically, the name shouldn't matter too much. gtk-set-font: https://anonscm.debian.org/cgit/d-i/rootskel-gtk.git/tree/src/usr/bin/gtk-set-font#n19 Mraw, KiBi. signature.asc Description: Digital signature
Bug#791794: UUID not found for root
Martin Michlmayr (2015-11-09): > * Ian Campbell [2015-11-06 16:03]: > > I've just pushed this change to flash-kenrel.git, so it will be in the > > next upload. > > Thanks! > > Can we also get this into a stable update? I believe some of the > reports were about stable. (As usual: you can safely pretend I didn't follow or fully understand f-k things.) Given the size of the fix and the fact the comment right above the code being fixed is explicit about the initial intent makes me want to cherry-pick it right away. It might be a good idea to let it go through a bit of testing before doing so, just in case something breaks. What do you think? (In the meanwhile I'll be preparing a stable branch for it and adding this to my “next point release” todo list.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#791794: UUID not found for root
On Tue, 2015-11-10 at 11:14 +0100, Cyril Brulebois wrote: > Martin Michlmayr (2015-11-09): > > * Ian Campbell [2015-11-06 16:03]: > > > I've just pushed this change to flash-kenrel.git, so it will be in > > > the > > > next upload. > > > > Thanks! > > > > Can we also get this into a stable update? I believe some of the > > reports were about stable. > > (As usual: you can safely pretend I didn't follow or fully understand f-k > things.) > > Given the size of the fix and the fact the comment right above the code > being fixed is explicit about the initial intent makes me want to > cherry-pick it right away. It might be a good idea to let it go through > a bit of testing before doing so, just in case something breaks. > > What do you think? I was thinking to at least wait for it to hit testing first (should do so at the end of the week) and then probably giving it a little more time (just a week or so) to bake there too, but I may be being too conservative. > (In the meanwhile I'll be preparing a stable branch for it and adding > this to my “next point release” todo list.) Thanks, saves me a job! Ian.
Re: [Pkg-fonts-devel] Migrating from fonts-droid to fonts-noto
Jonas Smedegaard writes: > Quoting Vasudev Kamath (2015-11-10 09:39:36) >> Christian PERRIER writes: >> >>> Quoting Vasudev Kamath (vasu...@copyninja.info): >>> > Is this change going to impact the fonts-android-udeb binary > package which is now being used within the Debian Installer? No, as of now upstream git repository of android source provides 2 fallback variants DroidSansFallback and DroidSansFallbackFull along with DroidSansMono. So this should not be a problem. >>> >>> >>> I think that Kibi's point is more asking "will you rename the udeb >>> package", which would then require a change in the D-I build >>> scripts >> >> Ah okay. No I will not rename the package. >> >> Only change I'm thinking to do is change the font shipped by udeb, >> currently it ships DroidSansFallback. I'm thinking of changing it to >> DroidSansFallbackFull will this cause any problems?. > > Seems change of font within that udeb can be done in independent of and > thus tracked as a separate bug than the issue of migrating non-fallback > fonts to Noto. I.e. need not delay the transition and need only be > discussed with those directly involved - no need for distro-wide > discussion of that :-) Sure thing :-).
Bug#791794: UUID not found for root
Ian Campbell (2015-11-10): > On Tue, 2015-11-10 at 11:14 +0100, Cyril Brulebois wrote: > > (As usual: you can safely pretend I didn't follow or fully understand f-k > > things.) > > > > Given the size of the fix and the fact the comment right above the code > > being fixed is explicit about the initial intent makes me want to > > cherry-pick it right away. It might be a good idea to let it go through > > a bit of testing before doing so, just in case something breaks. > > > > What do you think? > > I was thinking to at least wait for it to hit testing first (should do so > at the end of the week) and then probably giving it a little more time > (just a week or so) to bake there too, but I may be being too conservative. Seems fair to me; feel free to prod me in two weeks if you saw no breakages by then, so that I can push/ask SRM for an upload. I had this kind of timeframe in mind… > > (In the meanwhile I'll be preparing a stable branch for it and adding > > this to my “next point release” todo list.) > > Thanks, saves me a job! … then discovered the fix was from July! But only released a few days ago. :) No problem, that really was a no-brainer. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: CVE-2011-5325: busybox: Directory traversal via crafted tar file which contains a symlink pointing outside of the current directory
Processing commands for cont...@bugs.debian.org: > tags 802702 - patch Bug #802702 [busybox] CVE-2011-5325: busybox: Directory traversal via crafted tar file which contains a symlink pointing outside of the current directory Removed tag(s) patch. > forwarded 802702 https://bugs.busybox.net/8411 Bug #802702 [busybox] CVE-2011-5325: busybox: Directory traversal via crafted tar file which contains a symlink pointing outside of the current directory Changed Bug forwarded-to-address to 'https://bugs.busybox.net/8411' from 'https://bugs.busybox.net/show_bug.cgi?id=8411#c2' > thanks Stopping processing here. Please contact me if you need assistance. -- 802702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#802702: CVE-2011-5325: busybox: Directory traversal via crafted tar file which contains a symlink pointing outside of the current directory
tags 802702 - patch forwarded 802702 https://bugs.busybox.net/8411 thanks (Small issues with patch; see upstream tracker) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
Hi,
The bug still seem to be present, as tried with the most recent Jessie netboot
image.
[ ]netboot.tar.gz 01-Sep-2015 18:32 18M
Following is the output from network-console at the time of issue:
--8<---cut here---start->8---
~ # fdisk -l /dev/sda
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C89CD80E-7C84-42CD-BD07-ED7F424CBB73
Device Start End Sectors Size Type
/dev/sda1 2048499711497664 243M Linux filesystem
/dev/sda2 499712 8499199 7999488 3.8G Linux swap
/dev/sda3 8499200 488396799 479897600 228.9G Linux filesystem
~ # fdisk -l /dev/sda3
Disk /dev/sda3: 228.9 GiB, 245707571200 bytes, 479897600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x
Device Boot Start End Sectors Size Id Type
/dev/sda3p1 2048 479897599 479895552 228.9G 83 Linux
~ # tail /var/log/syslog
Nov 10 16:47:17 kernel: [ 69.492652] device-mapper: ioctl: 4.27.0-ioctl
(2013-10-30) initialised: dm-de...@redhat.com
Nov 10 16:47:17 partman: No matching physical volumes found
Nov 10 16:47:17 partman: Reading all physical volumes. This may take a
while...
Nov 10 16:47:17 partman: No volume groups found
Nov 10 16:47:17 partman-lvm: No volume groups found
Nov 10 16:47:18 kernel: [ 70.632238] sda: sda1 sda2 sda3
Nov 10 16:47:18 kernel: [ 70.749050] Adding 3999740k swap on /dev/sda2.
Priority:-1 extents:1 across:3999740k FS
Nov 10 16:47:18 partman: mke2fs 1.42.12 (29-Aug-2014)
Nov 10 16:47:18 partman: mke2fs 1.42.12 (29-Aug-2014)
Nov 10 16:47:18 partman: Found a dos partition table in /dev/sda3
# ps |grep ext
8529 root 4668 S{50format_ext3} /bin/sh
/lib/partman/commit.d/50format_ext3
8559 root 6308 Slog-output -t partman --pass-stdout mkfs.ext4
/dev/sda3
8560 root 17260 Smkfs.ext4 /dev/sda3
--8<---cut here---end--->8---
To workaround in my case, I'd to SIGKILL the mkfs.ext4 process, and then had
to do 'mkfs.ext4 -F /dev/sda3', and after that went back to debian-installer
screen, and chose "Detect Disks" menu item, and now installation is going on.
HTH
--
Ashish SHUKLA
“Yeah, sure. Babies learn their mother tongue by reading the great
philosophers…“ (Pascal Bourguignon, comp.lang.lisp)
Sent from my Emacs
signature.asc
Description: PGP signature
Bug#804351: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue
Thanks to all those that replied. Due to lack of time to debug this properly I just reverted to a jessie image via recovery mode: http://www.cyrius.com/debian/kirkwood/qnap/ts-219/recovery/ All is fine again... Cheers On 2015-11-10 21:36, Ian Campbell wrote: On Tue, 2015-11-10 at 01:08 +, Ben Hutchings wrote: On Mon, 2015-11-09 at 14:18 -0800, Martin Michlmayr wrote: > * Ian Campbell [2015-11-09 08:37]: > > It might be the same issue as this recent installation report: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804351 > > > > I've not had a chance to dig into what is going on there. Often this > > kind of thing turns out to be an upstream change to the modules > > (different config options, splitting modules into more fine grained > > parts) which requires tweaks to the kernel config, or initramfs -tools > > or to the kernel udebs for the installer. > > There was a report on the QNAP forum about a QNAP no longer booting > after an update. The logs says: > > [8.697480] sdb: sdb1 > [8.702144] sda: sda1 sda2 sda3 > [8.705613] sd 1:0:0:0: [sdb] Attached SCSI disk > [8.713159] sd 0:0:0:0: [sda] Attached SCSI disk > Begin: Loading essential drivers ... modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:NgpioTCmarvell,orion-gpio not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:NgpioTCmarvell,orion-gpio not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module platform:reg-dummy not found in modules.dep > done. > Begin: Running /scripts/init-premount ... done. > ... > [ and then the UUID is not found ] > > Any idea what these messages about modules.dep are about? All those modaliases correspond to devices whose drivers are built-in. So it's not surprising that they're not found in modules.dep, and I don't think this has anything to do with the failure. Indeed, I've been seeing them for a while and I don't believe they are anything more than a cosmetic issue. Ian.
Processing of net-retriever_1.41+kbsd8u1_source.changes
net-retriever_1.41+kbsd8u1_source.changes uploaded successfully to localhost along with the files: net-retriever_1.41+kbsd8u1.dsc net-retriever_1.41+kbsd8u1.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
Processing of net-retriever_1.41+kbsd8u1_source.changes
net-retriever_1.41+kbsd8u1_source.changes uploaded successfully to ftp-master.debian.org along with the files: net-retriever_1.41+kbsd8u1.dsc net-retriever_1.41+kbsd8u1.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org)
Bug#788062: os-prober corrupts LVs/partitions while being mounted inside a VM
Unfortunately I must confirm this bug which is high critical! My workaround was apt-get --purge remove os-prober
net-retriever_1.41+kbsd8u1_source.changes REJECTED
Uploads not including architecture-independent packages are not allowed. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
Processing of net-retriever_1.41+kbsd8u1_all.changes
net-retriever_1.41+kbsd8u1_all.changes uploaded successfully to ftp-master.debian.org along with the files: net-retriever_1.41+kbsd8u1.dsc net-retriever_1.41+kbsd8u1.tar.xz net-retriever_1.41+kbsd8u1_all.udeb download-installer_1.41+kbsd8u1_all.udeb Greetings, Your Debian queue daemon (running on host coccia.debian.org)
Processing of net-retriever_1.41+kbsd8u1_all.changes
net-retriever_1.41+kbsd8u1_all.changes uploaded successfully to localhost along with the files: net-retriever_1.41+kbsd8u1.dsc net-retriever_1.41+kbsd8u1.tar.xz net-retriever_1.41+kbsd8u1_all.udeb download-installer_1.41+kbsd8u1_all.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org)
net-retriever_1.41+kbsd8u1_all.changes ACCEPTED into stable-kfreebsd-proposed-updates
Mapping jessie-kfreebsd to stable-kfreebsd. Mapping stable-kfreebsd to stable-kfreebsd-proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 06 Oct 2015 09:46:11 + Source: net-retriever Binary: net-retriever download-installer Architecture: source all Version: 1.41+kbsd8u1 Distribution: jessie-kfreebsd Urgency: medium Maintainer: Debian Install System Team Changed-By: Steven Chamberlain Description: download-installer - Download installer components (udeb) net-retriever - Fetch modules from the Internet (udeb) Changes: net-retriever (1.41+kbsd8u1) jessie-kfreebsd; urgency=medium . * Support udebs-source having multiple suites Checksums-Sha1: 2d3a81f915e48fe9f16559c4518d61c11182b821 1430 net-retriever_1.41+kbsd8u1.dsc 726b5c902002ded0d1f92435cf014fc3f0fd7433 41388 net-retriever_1.41+kbsd8u1.tar.xz bb433661604c4d3557f6b99a6832f939930ea0f5 20318 net-retriever_1.41+kbsd8u1_all.udeb c15ac7caeb6ce62279969c133ca5701b3e49bf37 3596 download-installer_1.41+kbsd8u1_all.udeb Checksums-Sha256: e66e09e9155561018b87e36e37465add4840f03e63d7b9ea59f36076fdf797a5 1430 net-retriever_1.41+kbsd8u1.dsc 83dc522affa7e375959fe8006dcf4aef250fbe4e62e3da5d54e533a382b416e2 41388 net-retriever_1.41+kbsd8u1.tar.xz 3a89e0a596a87f6755cda18f84fd909d7da3acb56f1e12f85acca3bb04329071 20318 net-retriever_1.41+kbsd8u1_all.udeb 79fb1ffa61ace3fa21c87b1b1cf38a9d41fcc293d2bc16f173f64bc285a3410f 3596 download-installer_1.41+kbsd8u1_all.udeb Files: af9fdeab6b770733bc723c74a06935c0 1430 debian-installer optional net-retriever_1.41+kbsd8u1.dsc e1aad0187016c45e67f91c21cc9bba7f 41388 debian-installer optional net-retriever_1.41+kbsd8u1.tar.xz 81dc61363310634772488e8867e44215 20318 debian-installer optional net-retriever_1.41+kbsd8u1_all.udeb bb30ffbb1a549f8bbe3252e23b762ea6 3596 debian-installer extra download-installer_1.41+kbsd8u1_all.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJWQnFkAAoJELrpzbaMAu5TNXYH/3SOgDjHKrKbzqlmambgtvXf 5oLIRRkPiqakQ8UhGHCg6PbqWgCaroVrQdbsmYol7StVGKkMWu7dmqFJ++IEtiQc QJaKlqjYSxTJbh5jqrZV6gw9FyL4F6e4ifM/MmPGFRadCkACQ9x2RMO3aLmhAUlV jFrgJdJv4pPgb+s07J1I/yW3/Iji1ZkK1966X4ll2VSmgSOMAntckjEPsf7LtDn2 Gr3idjNhJeV5HcLtv9KL7+xIQxWW/MuBhnpeSuLQSDHcn7WVYUXXGtIiyPTgIPsD HzUh8o11cpi2kVxATy8cXe8pWyLKMBcZW0SyVEDaE0tVfySoX9Ovuiipo+xfApA= =YOmi -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#794410: (no subject)
I encountered this perfectly reproducible exact 12% total freeze bug using a Jessie installer image dating back a few months on an Intel J1900 host with integrated Realtek network hardware - I'm afraid I don't know which Jessie sub-version. However, on the exact same hardware (including the USB flash dongle), the Debian installer completed successfully using the debian-8.2.0-amd64-netinst.iso image. Users who encountered this bug with a Jessie DI version older than the 8.2.0 that was published in September 2015 might want to try again with that one.
