Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

On Aug 12, 2016, at 9:21 AM, Pete Batard wrote: > Okay. I have now gone through a dpkg -i install of all the (non dbgsym) .deb > I see on your server, and also issued a reboot for good measure, but I still > see the same problem with journald being failed, along with dependent

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

> On Aug 3, 2016, at 3:58 PM, Felipe Sateler <fsate...@debian.org> wrote: > > On 3 August 2016 at 16:44, Rick Thomas <rbtho...@pobox.com> wrote: >> >> On Aug 3, 2016, at 9:06 AM, Felipe Sateler <fsate...@debian.org> wrote: >> >>> On 1

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

On Aug 3, 2016, at 9:06 AM, Felipe Sateler <fsate...@debian.org> wrote: > On 1 August 2016 at 18:32, Rick Thomas <rbtho...@pobox.com> wrote: >> >> Thanks, Filipe! >> >> What do we have to do at this point to test this and then translate it into

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

On Aug 2, 2016, at 11:15 PM, Michael Biebl wrote: > Am 01.08.2016 um 23:40 schrieb Felipe Sateler: >> So I think the kernel should enable SECCOMP. > > I agree, unless SECCOMP on arm has some unwanted side-effects. > Felipe, can you file a bug report against the linux package

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

On Aug 1, 2016, at 2:40 PM, Felipe Sateler <fsate...@debian.org> wrote: > On 28 July 2016 at 17:04, Michael Biebl <bi...@debian.org> wrote: >> Am 28.07.2016 um 22:50 schrieb Rick Thomas: >>> In the interest of having a working system, I reverted that machine

Bug#461461: [pkg-ntp-maintainers] Bug#461461: This bug is still present -- change to systemd did not fix it!

On Aug 1, 2016, at 6:32 AM, Kurt Roeckx wrote: >> >> The DHCPACK that assigns the IP address to the interface occurs during the >> middle of ntpd's startup, so two of three pool statements get failed DNS. >> The third one succeeds, so ntpd gets some servers, but not all the

Bug#833136: Fwd: [pkg-ntp-maintainers] Bug#461461: This bug is still present -- change to systemd did not fix it!

On Aug 1, 2016, at 2:56 AM, Kurt Roeckx <k...@roeckx.be> wrote: > On Mon, Aug 01, 2016 at 02:37:58AM -0700, Rick Thomas wrote: >> This 8 year old bug is still present in jessie and stretch -- the change to >> systemd did not fix it! >> >> Please, somebody pa

Bug#833136: [pkg-ntp-maintainers] Bug#461461: This bug is still present -- change to systemd did not fix it!

53:30 ultimate ntpd[399]: Soliciting pool server 129.250.35.250 > May 18 03:53:31 ultimate ntpd[399]: Soliciting pool server 50.116.55.65 The DHCPACK that assigns the IP address to the interface occurs during the middle of ntpd’s startup, so two of three pool statements get failed DNS. The

Bug#461461: [pkg-ntp-maintainers] Bug#461461: This bug is still present -- change to systemd did not fix it!

93:3d:bd:bc > Aug 01 02:49:47 dillserver ifup[671]: Sending on Socket/fallback > Aug 01 02:49:47 dillserver ifup[671]: DHCPDISCOVER on eth0 to 255.255.255.255 > port 67 interval 4 > On Aug 1, 2016, at 2:56 AM, Kurt Roeckx <k...@roeckx.be> wrote: > On Mon, Aug 01, 2016 at 02:37:58A

Bug#833136: ntpdate has the same problem as ntp in Bug#461461. ntpdate starts before dhcpclient finishes

Package: ntpdate Version: 1:4.2.6.p5+dfsg-7+deb8u2 Severity: important during system startup ntpdate starts before dhcpclient finishes. hence ntpdate can't find its server so it dies and fails to set the clock. -- System Information: Debian Release: 8.5 APT prefers stable-updates APT

Bug#461461: This bug is still present -- change to systemd did not fix it!

This 8 year old bug is still present in jessie and stretch — the change to systemd did not fix it! Please, somebody pay attention! This bug makes ntpd unreliable tending to useless on systems that get their network config from dhcp. Rick

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

Thanks for you help so far, Michael! Can I ask one last favor on this? It seems that the bug (whatever it is) depends on things like kernel version and machine architecture. So, can you suggest someone who can take this further? Thanks! Rick

Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

On Jul 31, 2016, at 2:02 AM, Christian Marillat <maril...@free.fr> wrote: > On 31 juil. 2016 10:50, Rick Thomas <rbtho...@pobox.com> wrote: > >> Can you send the output of ‘uname -a ; systemd —version’ on that box? > > Linux rpi3.XXX 4.4.0-1-rpi2 #1 SMP Debian 4.4

Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

Can you send the output of ‘uname -a ; systemd —version’ on that box? Thanks! On Jul 31, 2016, at 12:22 AM, Christian Marillat <maril...@free.fr> wrote: > On 31 juil. 2016 08:50, Rick Thomas <rbtho...@pobox.com> wrote: > >> Thanks, Christian! >> >>

Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

Thanks, Christian! What is your armel box? I *do* see it on my SheevaPlug (armel), so there may be a clue. Is your armel kernel customized in some way? Enjoy! Rick > On Jul 30, 2016, at 11:33 PM, Christian Marillat <maril...@free.fr> wrote: > > On 30 juil. 2016 23:02, Ric

Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

Has anyone else noticed this bug? Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start I’ve tried it on armel (SheevaPlug) and armmp (Cubox-i4Pro). It fails on both. I’ve also tried it on amd64 and powerpc hardware. The bug is not present there.

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

(including the systemd version in question) and it does *not* have the problem. This is the same result I saw on the amd64 (virtual) machine. So it seems to be arm specific… Any thoughts? On Jul 29, 2016, at 3:02 PM, Michael Biebl <bi...@debian.org> wrote: > Am 29.07.2016 um 23:29 sch

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

Hmmm… Curiouser and curiouser! I upgraded a VM (amd64) to latest Sid (with systemd version 231-1). The problem is *not* present there. The problem may be specific to arm hardware? I’ll try it on a PowerPC G4 (Apple Mac PPC) machine later today. Rick On Jul 28, 2016, at 5:18 PM, Rick

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

/SECCOMP) Any other thoughts? Rick On Jul 28, 2016, at 2:04 PM, Michael Biebl <bi...@debian.org> wrote: > Am 28.07.2016 um 22:50 schrieb Rick Thomas: >> In the interest of having a working system, I reverted that machine to >> systemd version 230-7. Unsurprisingly,

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

Description: Binary data On Jul 28, 2016, at 1:24 PM, Michael Biebl <bi...@debian.org> wrote: > Am 28.07.2016 um 22:01 schrieb Rick Thomas: >> No. This is a stock kernel. It’s available from both testing and unstable >> repos. The machine itself is a SheevaPlug.

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

info > Am 28.07.2016 um 12:08 schrieb Rick Thomas: >> Main PID: 477 (code=exited, status=228/SECCOMP) > ... >> Kernel: Linux 4.6.0-1-marvell > > That looks like you are using a custom kernel. Is the problem > reproducible with the default Debian Linux kern

Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'

On Jun 30, 2016, at 12:50 AM, Mathieu Malaterre <ma...@debian.org> wrote: > On Thu, Jun 30, 2016 at 9:45 AM, Rick Thomas <rbtho...@pobox.com> wrote: >> Do I understand correctly that I should put “drm.debug=0xe” as a kernel >> argument at boot time? Then boot,

Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'

, 2016, at 11:20 PM, Mathieu Malaterre <ma...@debian.org> wrote: > On Sun, Jun 26, 2016 at 2:59 AM, Rick Thomas <rbtho...@pobox.com> wrote: >> For what it’s worth, I get the same behavior on amd64 running stretch. It’s >> not just on powerpc. > > Great ! Could yo

Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

On May 31, 2016, at 2:18 AM, Santiago Vila <sanv...@unex.es> wrote: > On Mon, 30 May 2016, Rick Thomas wrote: > >> Here’s the setup: >> >> I have a POP/IMAP account at pobox.com. I use cron to run fetchmail which >> retrieves (POP3) mail from pobox to a l

Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

On May 30, 2016, at 2:36 AM, Santiago Vila <sanv...@unex.es> wrote: > On Sun, 29 May 2016, Rick Thomas wrote: > >> Package: procmail >> Version: 3.22-24 >> Severity: normal >> >> Dear Maintainer, >> >> *** Reporter, please

Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

loses: 781873 821056 824730 825458 Changes: u-boot (2016.03+dfsg1-5) unstable; urgency=medium . [ Vagrant Cascadian ] * Add patches from upstream to detect fdtfile on am57xx, and update distro_bootcmd patch accordingly. * u-boot-tools: Add fw_env.config for openrd (Closes: #821056). T

Bug#812395: u-boot-tools: sheevaplug /etc/fw_env.config - explain how env address depends on your version of u-boot.

>> If you could please provide a patch detailing exactly what you would >> like changed, that would be appreciated. It look like the latest u-boot-tools has exactly what I would have said. Very sorry for taking so long to get back. I think this bug can be closed now. Thanks! Rick

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

On Apr 17, 2016, at 8:35 AM, Vagrant Cascadian <vagr...@debian.org> wrote: > On 2016-04-16, Rick Thomas wrote: >> Re-reading this, I realize that I said “0x8” for the environment >> location of legacy u-boot. But when I went to test it, the true value >>

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

the change? Or was it just one of those things that “seemed like a good idea at the time” ? On Apr 16, 2016, at 6:04 PM, Rick Thomas <rbtho...@pobox.com> wrote: > > On Apr 15, 2016, at 12:29 PM, Vagrant Cascadian <vagr...@debian.org> wrote: > >> On 20

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

On Apr 15, 2016, at 12:29 PM, Vagrant Cascadian <vagr...@debian.org> wrote: > On 2016-04-14, Rick Thomas wrote: >> The directory /usr/share/doc/u-boot-tools/examples/ has example .config files >> for a variety of devices, but none for the OpenRD base, client or ultimate.

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

Package: u-boot-tools Version: 2016.03+dfsg1-3 Severity: normal Dear Maintainer, The directory /usr/share/doc/u-boot-tools/examples/ has example .config files for a variety of devices, but none for the OpenRD base, client or ultimate. Until recently, this was not a roblem because recent

Bug#818860: python-gnuplot: errors or warnings from gnuplot when running python-gnuplot demo.py

Package: python-gnuplot Version: 1.8-6 Severity: normal Dear Maintainer, * What led up to the situation? Installed python-gnuplot then unpacked and ran the demo.py from /usr/share/doc/python-gnuplot/examples * What was the outcome of this action? error/warning messages were not expected,

Bug#812719: apticron: Me too

Package: apticron Version: 1.1.58 Followup-For: Bug #812719 Dear Maintainer, I see the same problem. Stock, out of the box, stretch installation. I have tested the fix in the original bugreport. It works. Thanks! -- System Information: Debian Release: stretch/sid APT prefers testing APT

Bug#762634: initramfs-tools: [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs

On Wed, 24 Feb 2016 15:06:27 -0800 Vagrant Cascadian wrote: > On 2016-02-24, Vagrant Cascadian wrote: > > On 2016-02-04, Ben Hutchings wrote: > >> Oh, so the MODULES=most case is bust and we need to list more host > >> controller drivers (or include all modules under

Bug#812611: u-boot should have update-u-boot automatic in postinst like update-grub

On Jan 31, 2016, at 11:37 AM, Kilian Krause wrote: > If you have the impression that "most" of the > ARM systems out there are only equipped with a single boot device that's not > removable, please do give a list. Otherwise, unbricking a vfat or ext4 > partition on a PC

Bug#812611: u-boot should have update-u-boot automatic in postinst like update-grub

On Jan 31, 2016, at 2:42 PM, Rick Thomas <rbtho...@pobox.com> wrote: > boot from internal MMC flash that is soldered to the mainboard. Sorry, *not* "MMC flash". That *should* be "MTD flash". see: http://www.linux-mtd.infradead.org/faq/general.html for an

Bug#812611: u-boot should have update-u-boot automatic in postinst like update-grub

On Jan 25, 2016, at 8:07 AM, Kilian Krause wrote: > Package: u-boot > Severity: wishlist > Tags: d-i > > Hi Vagrant, > > as just discussed the d-i mimic of installing u-boot should also be > available when updating u-boot packages in an installed system. > > There may be

Bug#812395: u-boot-tools: sheevaplug /etc/fw_env.config - explain how env address depends on your version of u-boot.

Package: u-boot-tools Version: 2016.01+dfsg1-1 Severity: wishlist I believe the following to be true based on experiments with my two sheevaplugs: If your Sheevaplug has a u-boot version prior to 2014.10+dfsg1-5, including any of the original "Marvell" versions, the environment is located at

Bug#811351: additional request...

> On Jan 20, 2016, at 2:54 PM, Aaro Koskinen wrote: > > I can add more verbose comments to mainline kernel .dts on how to > enable serial port, and how to select between rs232/485. Andrew, do > you want me to resend the current patches, or can it be done with an >

Bug#811351: additional request...

Hi Aaro, Andrew wrote > On Sun, Jan 17, 2016 at 11:55:19PM -0800, Rick Thomas wrote: >> >> On Jan 17, 2016, at 2:42 PM, Martin Michlmayr <t...@cyrius.com> wrote: >>> * Andrew Lunn <and...@lunn.ch> [2016-01-10 16:38]: >>>> Please can you t

Bug#811351: linux-image-4.3.0-0.bpo.1-kirkwood: MMC does not work on OpenRD Client / fix pending

Package: src:linux Version: 4.3.3-5~bpo8+1 Severity: normal Dear Maintainer, The 4.3.0.0 kernel on an "OpenRD Client" fails to recognize the SD card -- there is no mmc device shown by lsblk. This is fixed by using a modified DTB file provided by Aaro Koskinen. Fix tested by Rick Thom

Bug#806215: problem found in mdadm_3.3.4-1.1+b1_armhf [Re: mdadm: upgraded mdadm now does not recognize RAID6 array causing boot to drop into emergency mode]

This problem persists in mdadm_3.3.4-1.1+b1_armhf. Attached is the output of dmesg after booting, dropping into emergency mode, running “systemctl restart mdadm-raid” and typing “exit” resulting in boot completion. dmesg-mdadm_3.3.4-1.1+b.out Description: Binary data Rick

Bug#810790: u-boot: It would be nice if u-boot was supported on OpenRD boards...

Package: u-boot Version: 2014.10+dfsg1-5 Severity: wishlist Dear Maintainer, I have two OpenRD machines, a "Client" and an "Ultimate" that I'm willing to use for testing new releases. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500,

Bug#809932: installation-reports: Successful install of Debian Stretch on Sheevaplug

On Jan 7, 2016, at 7:25 PM, Martin Michlmayr wrote: > So it sounds like you had: > - standard > - SSH server > - print server > >> tmpfs tmpfs 102788 348102440 1% /run >> /dev/sda2 ext4 2065152 1878636 61896 97% / > > I'm surprised it

Bug#793426: Debian 8.1 - missing separate /usr in guided encrypted LVM partitioning scheme

On Jan 7, 2016, at 9:07 PM, Martin Michlmayr wrote: > * Patryk Hanckowiak [2015-07-24 00:58]: >> The guided LVM encrypted partitioning layout does not create a separate /usr >> partition and creates a 8-10 GB / (root) partition. This happens in both >>

Bug#781874: sheeveplug u-boot environment - correction!

On Jan 6, 2016, at 12:59 PM, Rick Thomas <rbtho...@pobox.com> wrote: > At a minimum, the patch in bug#781874 needs to be applied in order to be > compatible with modern version of u-boot. Oooops! Sorry! Brain-fart… The patch doesn’t do what I thought it did. What I shou

Bug#781874: sheeveplug u-boot environment

On Jan 6, 2016, at 9:10 AM, Vagrant Cascadian wrote: >> So I guess it’s all explained by https://bugs.debian.org/781874 . > > I really don't understand the logic outlined in that bug report, and > your results don't exactly come to the same conclusion, which is why > I've

Bug#809932: installation-reports: Successful install of Debian Stretch on Sheevaplug

Package: installation-reports Severity: normal Dear Maintainer, First, I upgraded U-boot on the machine to version "2014.10+dfsg1-5" Second, I downloaded uImage and uInitrd from https://d-i.debian.org/daily-images/armel/daily/kirkwood/netboot/marvell/sheevaplug/ and put them on a USB stick

Bug#806858: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

Package: s-nail Version: 14.8.5-4 Followup-For: Bug #806858 Dear Maintainer, So what, exactly, are the correct permissions for s-nail-privsep? Should it be: -rwxr-sr-x 1 root mail 10104 Dec 4 14:52 /usr/lib/s-nail/s-nail-privsep or: -rwsr-xr-x 1 root mail 10104 Dec 4 14:52

Bug#806215: mdadm: upgraded mdadm now does not recognize RAID6 array causing boot to drop into emergency mode

Package: mdadm Version: 3.3.4-1 Severity: important Cubox-i system has a RAID6 array of usb-keys (it's just an experiment -- I'd never use it in a production system) Runs Debian Sid. I recently did an upgrade that replaced mdadm_3.3.4-1_armhf.deb with mdadm_3.3.4-1.1_armhf.deb. Reboot

Bug#804766: inetutils-inetd: please support ipv6

Package: inetutils-inetd Version: 2:1.9.2.39.3a460-3 Severity: wishlist Dear Maintainer, inetd does not listen on IPv6 ports, only IPv4. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'),

Bug#618862: systemd: ignores keyscript in crypttab

I tested Marcello’s workaround. It works! That’s wonderful! Thank you so much, Marcello! Now some further thoughts on the subject… It’s a workaround for this bug, but, unfortunately it’s just a workaround not a real fix. In particular, using a “luks=no” kernel command line option disables

Bug#618862: systemd: ignores keyscript in crypttab

On Oct 16, 2015, at 3:02 AM, Marcello Barnaba wrote: >> On Sat, 19 Mar 2011 03:40:25 +0100 Mourad De Clerck wrote: >> my root and swap partition are encrypted with cryptsetup; root uses a custom >> keyscript and swap uses the cryptsetup-provided "decrypt_derived" keyscript. >>

Bug#618862: systemd: ignores keyscript in crypttab

On Oct 16, 2015, at 9:20 AM, Marcello Barnaba wrote: > >>> Workaround: add "luks=no" to the kernel command line to disable systemd's >>> generator: >>> http://www.freedesktop.org/software/systemd/man/systemd-cryptsetup-generator.html > >> Does this work for encrypted root

Bug#800147: cryptsetup: keyscript=/lib/cryptsetup/scripts/passdev and noearly do not work

Package: cryptsetup Version: 2:1.6.6-5 Severity: important Under Wheezy, I was able to put "keyscript=/lib/cryptsetup/scripts/passdev" in /etc/crypttab to make it use a key file on a USB stick Now with jessie, this doesn''t work. The relevant lines from /etc/crypttab look like this: aux

Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'

Package: fbset Version: 2.1-28 Severity: grave Justification: renders package unusable Dear Maintainer, Prior to Jessie, I could use "fbset" toset the screen resolution on my PowerPC Macs. This was often necessary if the system happened to mis-guess the actual screen resolution, or the screen

Bug#794636: dnsmasq: /etc/dnsmasq.conf does not end with newline

Package: dnsmasq Version: 2.72-3+deb8u1 Severity: normal Dear Maintainer, The default /etc/dnsmasq.conf file does not end with a newline. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'),

Bug#794640: dnsmasq: last line of /etc/dnsmasq.conf is missing a comma.

Package: dnsmasq Version: 2.72-3+deb8u1 Severity: normal Dear Maintainer, The last line of the default /etc/dnsmasq.conf file needs a comma to be syntacticaly correct: Currently is: #conf-dir=/etc/dnsmasq.d/*.conf Should be: #conf-dir=/etc/dnsmasq.d/,*.conf -- System

Bug#794642: dnsmasq: pick one of the conf-dir directives and un-comment it, please

Package: dnsmasq Version: 2.72-3+deb8u1 Severity: wishlist Dear Maintainer, The default /etc/dnsmasq.conf file, toward the end of the file, suggests several options for allowing local drop-in configurations without changing the dnsmasq.conf file itself. But they are all commented out. If one

Bug#794642: dnsmasq: pick one of the conf-dir directives and un-comment it, please

-system start script, without the need to include is in /etc/dnsmasq.conf This is documented in para 2 of /usr/shar/doc/dnsmasq/README.Debian Cheers, Simon. On 05/08/15 11:12, Rick Thomas wrote: Package: dnsmasq Version: 2.72-3+deb8u1 Severity: wishlist Dear Maintainer

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Jul 25, 2015, at 3:21 PM, Bastian Blank wrote: On Tue, Jul 21, 2015 at 07:05:42PM -0700, Rick Thomas wrote: I created a virtual machine with VMWare running on my Mac. It has a virtual DVD-drive (loaded with the Jessie 8.1.0 amd64 install image) and three virtual disk drives. One

Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

On Jul 21, 2015, at 12:11 PM, Bastian Blank wa...@debian.org wrote: However I'm still unable to reproduce the problem without a sledgehammer. I reproduced the problem in a tiny test system as follows: I created a virtual machine with VMWare running on my Mac. It has a virtual DVD-drive

Bug#791869: Output of 'systemctl status' in broken state and just after un-breaking it...

In case it helps, here’s systemctl status as logged during emergency shell. Rick Jul 19 22:43:49 stretch fixup[687]: + systemctl status Jul 19 22:43:49 stretch fixup[687]: * stretch Jul 19 22:43:49 stretch fixup[687]: State: maintenance Jul 19 22:43:49 stretch fixup[687]: Jobs: 0

Bug#791869: Info received (Output of 'systemctl status' in broken state and just after un-breaking it...)

On a hunch, I made the following change # diff /SAVE/etc/lvm/lvm.conf /etc/lvm/lvm.conf 823c823 use_lvmetad = 1 --- use_lvmetad = 0 and ran # update-initramfs -u Then rebooted. The problem went away… As I understand it, this makes LVM always check the actual physical volumes

Bug#783381: upgrade from wheezy to jessie on a PowerMac G4 Silver/Confirmation

Try adding append=“ nomodeset to the end of the main stanza in /etc/yaboot.conf. Then (as root) execute “ybin” to propagate the change to the bootstrap routines. This will set the kernel command line to inhibit the kernel from trying to use hardware acceleration for your video. The

Bug#786877: u-boot-tools does not have .config file for cubox

On May 28, 2015, at 9:56 AM, Vagrant Cascadian vagr...@aikidev.net wrote: … lots of useful explanation … Thank you very much! Useful stuff! I suppose I should document this in README.Debian... That would be great! Thank you! Rick -- To UNSUBSCRIBE, email to

Bug#786877: u-boot-tools does not have .config file for cubox

On 05/26/15 13:35, Vagrant Cascadian wrote: On 2015-05-26, Rick Thomas wrote: On May 26, 2015, at 12:44 PM, Rick Thomas rbtho...@pobox.com wrote: On May 26, 2015, at 10:32 AM, Vagrant Cascadian vagr...@aikidev.net wrote: On 2015-05-26, Rick Thomas wrote: The entry committed may not work

Bug#786877: u-boot-tools does not have .config file for cubox

Package: u-boot-tools Version: 2014.10+dfsg1-5 Severity: normal When I try fw_printenv on my cubox i4Pro, it complains Cannot parse config file: No such file or directory Looking in /usr/share/doc/u-boot-tools/examples/ there are several example .config files, but none for the cubox

Bug#786879: u-boot-tools: need a way to set kernel command line parameters in u-boot

Package: u-boot-tools Version: 2015.04+dfsg1-2 Severity: wishlist If I wish to boot into, e.g. single user mode on my arm device, I find that there is no way to set the kernel command parameter single other than by mucking with bootargs_console in ways its creator did not intend. The problem is

Bug#786877: u-boot-tools does not have .config file for cubox

On May 26, 2015, at 12:44 PM, Rick Thomas rbtho...@pobox.com wrote: On May 26, 2015, at 10:32 AM, Vagrant Cascadian vagr...@aikidev.net wrote: Control: tags -1 +pending On 2015-05-26, Rick Thomas wrote: When I try fw_printenv on my cubox i4Pro, it complains Cannot parse config file

Bug#786879: u-boot-tools: need a way to set kernel command line parameters in u-boot

On May 26, 2015, at 9:30 AM, Vagrant Cascadian vagr...@aikidev.net wrote: Control: title -1 way to set kernel command line parameters in u-boot On 2015-05-26, Rick Thomas wrote: If I wish to boot into, e.g. single user mode on my arm device, I find that there is no way to set the kernel

Bug#786877: u-boot-tools does not have .config file for cubox

On May 26, 2015, at 10:32 AM, Vagrant Cascadian vagr...@aikidev.net wrote: Control: tags -1 +pending On 2015-05-26, Rick Thomas wrote: When I try fw_printenv on my cubox i4Pro, it complains Cannot parse config file: No such file or directory Looking in /usr/share/doc/u-boot

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

On May 16, 2015, at 6:02 AM, Ben Hutchings b...@decadent.org.uk wrote: If that’s correct, I’m not sure if even sysvinit with /etc/default/hwclock could have done the right thing in my case. This is not implemented directly by the init system. util-linux installs the script

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

On May 16, 2015, at 6:02 AM, Ben Hutchings b...@decadent.org.uk wrote: This is not implemented directly by the init system. util-linux installs the script/lib/udev/hwclock-set and a udev rule that runs it for each RTC device. However, the hwclock-set script does nothing if systemd is

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

On May 16, 2015, at 12:58 PM, Rick Thomas rbtho...@pobox.com wrote: On May 16, 2015, at 6:02 AM, Ben Hutchings b...@decadent.org.uk wrote: This is not implemented directly by the init system. util-linux installs the script/lib/udev/hwclock-set and a udev rule that runs it for each RTC

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

On May 16, 2015, at 3:13 AM, Ian Campbell i...@debian.org wrote: On Fri, 2015-05-15 at 17:55 -0700, Rick Thomas wrote: [...] There does not seem to be any way to over-ride this. There's code in /etc/default/hwclock that would do part of the work in a sysvinit setup, but it seems

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

Package: src:linux Version: 4.0.2-1 Severity: normal Tags: upstream My cubox-i4pro armhf device has two real-time-clocks. One, snvs, is not battery backed, hence is not useful for setting the system clock on boot after a power failure. The other, pcf8523, does have battery backup.

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On May 6, 2015, at 3:35 AM, Rick Thomas rbtho...@pobox.com wrote: On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote: It would be preferable to test the thing in Sid before the upload to jessie-proposed-updates I’ll keep an eye out for it. But I don’t have one

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On May 12, 2015, at 2:11 AM, Ian Campbell i...@debian.org wrote: On Tue, 2015-05-12 at 01:33 -0700, Rick Thomas wrote: On May 6, 2015, at 3:35 AM, Rick Thomas rbtho...@pobox.com wrote: On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote: It would be preferable to test

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

OK, How will I identify the upload when I see it? The box is running Debian/Sid and I do regular updates. So presumably, I’ll see a “linux-image-3.16.0-4-armmp” package go by sometime soon? And I’ll know I’ve got it when I see two /dev/rtc* devices? As for “rbtho...@cube.rcthomas.org” — I’m

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote: It would be preferable to test the thing in Sid before the upload to jessie-proposed-updates I’ll keep an eye out for it. But I don’t have one of the cubox models without the battery-backed RTC, so I won’t be able to test that

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On Apr 28, 2015, at 8:02 PM, Fabio Estevam feste...@gmail.com wrote: On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings b...@decadent.org.uk wrote: Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware real-time-clock gets reset to midnight UTC, Dec 31, 1970. Even

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On Apr 28, 2015, at 8:02 PM, Fabio Estevam feste...@gmail.com wrote: On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings b...@decadent.org.uk wrote: Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware real-time-clock gets reset to midnight UTC, Dec 31, 1970. Even

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

On Apr 23, 2015, at 1:29 AM, Michael Biebl bi...@debian.org wrote: There might be a race somewhere, i.e. lvm2-activation(-early).service being run *before* mdadm has assembled the RAID. You could test this theory, be artifically delaying those two services. Copy them to

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

On Apr 22, 2015, at 8:17 AM, Michael Biebl bi...@debian.org wrote: Am 22.04.2015 um 12:10 schrieb Rick Thomas: This works. Interestingly, without the sleep loop the vgchange fails. Now, you say that a VM with two virtual disks configured as RAID1 with a logical volume works fresh out

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

On Apr 23, 2015, at 1:29 AM, Michael Biebl bi...@debian.org wrote: Can you boot with systemd.log_level=debug on the kernel command line and attach the journal output of this boot, so we have more information out the timing, i.e. when certain services are started There might be a race

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

On Apr 21, 2015, at 11:17 AM, Michael Biebl bi...@debian.org wrote: If you have the sysvinit package installed, you can try booting with sysvinit temporarily via init=/lib/sysvinit/init on the kernel command line. Does that work? I had to install sysvinit. And I had to make up a suitable

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

On Apr 23, 2015, at 2:31 PM, Michael Biebl bi...@debian.org wrote: Am 23.04.2015 um 21:47 schrieb Rick Thomas: On Apr 23, 2015, at 1:29 AM, Michael Biebl bi...@debian.org wrote: There might be a race somewhere, i.e. lvm2-activation(-early).service being run *before* mdadm has assembled

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

On Apr 22, 2015, at 8:17 AM, Michael Biebl bi...@debian.org wrote: Could you copy /lib/systemd/system/lvm2-activation.service to /etc/systemd/system and add a line After=mdadm-raid.service to the [Unit] section. Will do. Thanks! -- To UNSUBSCRIBE, email to

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

Hi Michael, Thanks very much for helping me with this. (continued following quoted material) On Apr 21, 2015, at 11:17 AM, Michael Biebl bi...@debian.org wrote: control: tags -1 moreinfo unreproducible Am 18.04.2015 um 02:02 schrieb Rick Thomas: On Apr 17, 2015, at 3:44 PM, Michael Biebl

Bug#762953: Bug still present in latest Sid -- /etc/network/interfaces

interfaces Description: Binary data This is “fresh out of the box” as it comes from the debian installer process. I have made no changes. Rick On Apr 17, 2015, at 2:57 PM, Michael Biebl bi...@debian.org wrote: Am 17.04.2015 um 22:49 schrieb Rick Thomas: I’ve seen this bug today

Bug#762953: Bug still present in latest Sid

I’ve seen this bug today. System drops into emergency mode for reasons that have nothing to do with this bug. Network is active when in emergency shell. I type root password then immediately exit, system continues to boot. When boot is finished, network is not active. system journal of

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

On Apr 17, 2015, at 3:17 PM, Michael Biebl bi...@debian.org wrote: Am 17.04.2015 um 23:43 schrieb Rick Thomas: Package: systemd Version: 215-16 Severity: important When /etc/fstab has an ext4 filesystem on a logical volume which is itself on a software raid, the system times out waiting

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

On Apr 17, 2015, at 3:44 PM, Michael Biebl bi...@debian.org wrote: Thanks for the data. Looks like an lvm issue to me: root@cube:~# lvscan inactive '/dev/vg1/backup' [87.29 GiB] inherit and as a result, /dev/disk/by-label/BACKUP is missing. Yes, that’s true, of course. But

Bug#782364: Actually, it makes some sense to keep both clocks

Ben Hutchings indicates that his preference would be to disable the non-battery-backed RTC and enable the battery-backed RTC in the kernel for the Cubox-i4pro. I’m not a kernel hacker, so what I’m about to say may be off the mark, but: If I’m not mistaken, this kernel is intended to be used on

Bug#782364: Actually, it makes some sense to keep both clocks

On Apr 12, 2015, at 6:10 AM, Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2015-04-12 at 01:37 -0700, Rick Thomas wrote: Ben Hutchings indicates that his preference would be to disable the non-battery-backed RTC and enable the battery-backed RTC in the kernel for the Cubox-i4pro. I’m

Bug#782314: fake-hwclock writes to /etc

Hi! Thanks for the clarification. I see your point. Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

Package: src:linux Version: 3.16.7-ckt7-1 Severity: wishlist Tags: newcomer Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware real-time-clock gets reset to midnight UTC, Dec 31, 1970. Even though the SolidRun literature says that the i4Pro has a battery backed RTC.

Bug#773688: ntp: NTP version 4.2.8 is available.

Package: ntp Version: 1:4.2.6.p5+dfsg-2+deb7u1 Severity: wishlist Dear Maintainer, NTP version 4.2.8 includes over 1000 bug fixes and new features, including final replacement and deprecation of the ntpdc command. We should consider upgrading. Anything I can do to help, let me know... --

Bug#705894: arpwatch - buffer overflow detected -- Can we get this fixed?

Christoph provided a patch with the initial bug report in April 2013. Can we get this fix into the Jessie release? Please! Hasn’t it been long enough? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

<    1   2   3   4   5   6   7   >