Bug#860316: CVE-2017-7861

2017-04-26 Thread Steinar H. Gunderson
On Fri, Apr 14, 2017 at 03:06:35PM +0200, Moritz Muehlenhoff wrote: > Source: grpc > Severity: grave > Tags: security > > Please see > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7861 for details. Since the packaging team seems to be dead, I've uploaded an NMU of gRPC 1.2.5 to

Bug#859217: closed by "Steinar H. Gunderson" <sgunder...@bigfoot.com> (Re: Bug#859217: nageru: just segfaults)

2017-04-05 Thread Steinar H. Gunderson
On Sat, Apr 01, 2017 at 08:46:34PM +0200, Steinar H. Gunderson wrote: > I found a relatively clean fix and uploaded it to unstable. Please test if it > works for you before I send it on to the release team. Seemingly it was unblocked without any action on my behalf: Migration stat

Bug#859217: closed by "Steinar H. Gunderson" <sgunder...@bigfoot.com> (Re: Bug#859217: nageru: just segfaults)

2017-04-01 Thread Steinar H. Gunderson
On Sat, Apr 01, 2017 at 08:58:11AM +0200, Steinar H. Gunderson wrote: > While I agree failing to show a friendly message is a bug, I'm not sure > whether it fits the definition of grave (“makes the package in question > unusable or mostly so”). I'll try to investigate how easy it i

Bug#859217: closed by "Steinar H. Gunderson" <sgunder...@bigfoot.com> (Re: Bug#859217: nageru: just segfaults)

2017-04-01 Thread Steinar H. Gunderson
severity 859217 important thanks On Sat, Apr 01, 2017 at 02:34:13AM +0300, Adrian Bunk wrote: > I am also getting segfaults when trying to start Nageru on my computer > (old AMD card). > > Whether Nageru is ever expected to work on my or Antonios computer is > one thing. > > But failing with a

Bug#859217: nageru: just segfaults

2017-03-31 Thread Steinar H. Gunderson
On Fri, Mar 31, 2017 at 03:54:01PM -0300, Antonio Terceiro wrote: >> Do you think you could supply a backtrace? > argh, forgot the attachment. I was hoping for a gdb backtrace, though, not an strace log. But I think we're already getting to it. >> Also, do you have working OpenGL? Can you say

Bug#859217: nageru: just segfaults

2017-03-31 Thread Steinar H. Gunderson
On Fri, Mar 31, 2017 at 02:41:12PM -0300, Antonio Terceiro wrote: > I deciced to try nageru here, and it just segfaults: > > $ nageru > QEGLPlatformContext: Failed to create context: 3009 > QEGLPlatformContext: Failed to create context: 3009 > QEGLPlatformContext: Failed to create context: 3009 >

Bug#859218: nageru: please include some documentation in the package

2017-03-31 Thread Steinar H. Gunderson
On Fri, Mar 31, 2017 at 02:42:57PM -0300, Antonio Terceiro wrote: > The documentation from https://nageru.sesse.net/doc/ seems very nice, it > would be great if it could be included in the package. Unfortunately, this is too late for stretch, but it would probably be possible for unstable. Out

Bug#824391: Pending fixes for bugs in the shadow package

2017-01-25 Thread Steinar H. Gunderson
On Wed, Jan 25, 2017 at 04:00:18PM +, pkg-shadow-de...@lists.alioth.debian.org wrote: > The full diff can be seen at > http://anonscm.debian.org/gitweb/?p=pkg-fonts/shadow.git;a=commitdiff;h=d779e83 FWIW; this 404-s. pkg-fonts/shadow? /* Steinar */ -- Homepage: https://www.sesse.net/

Bug#850955: libapache2-request-perl: description should include the names of the libraries

2017-01-11 Thread Steinar H. Gunderson
On Wed, Jan 11, 2017 at 04:41:00PM +0100, Seb wrote: > It would be useful if the names of the libraries included in the package > could > be found with Debian's usual tools. Hi! Thanks for your bug report. It is certainly a valid concern, but I will add that if you're looking for a specific

Bug#850226: no longer advertises route

2017-01-07 Thread Steinar H. Gunderson
On Sun, Jan 08, 2017 at 01:16:20AM +1100, Scott Leggett wrote: > Though the broken versions appear to be different, this issue looks > similar to an existing upstream bug: > https://bugzilla.quagga.net/show_bug.cgi?id=870 > > Does this look like the same issue to you? It might be the same, but

Bug#850226: no longer advertises route

2017-01-05 Thread Steinar H. Gunderson
Package: quagga-bgpd Version: 1.1.0-3 Severity: grave Hi, I lost all of my IPv6 connectivity this morning; a bit of searching shows that it is due to an automated upgrade of: 2017-01-05 07:36:26 upgrade quagga:amd64 1.0.20160315-2 1.1.0-3 None of the neighbors see my IPv6 route anymore; it

Bug#847135: openconnect: vpn connection mtu too big

2016-12-19 Thread Steinar H. Gunderson
On Mon, Dec 19, 2016 at 09:53:06AM -0800, Mike Miller wrote: > That it affects only some people does not make it grave, but I'll > compromise with serious. Regardless of severity, 7.08 is coming soon, > which is expected to fix this. I hope you will update to it before it > hits testing and let us

Bug#847135: openconnect: vpn connection mtu too big

2016-12-19 Thread Steinar H. Gunderson
severity 847135 grave thanks On Mon, Dec 05, 2016 at 09:04:57PM +, martin wrote: > * What led up to the situation? > Connecting to the VPN > Any connection sending large amounds of data fails > http downloads of any non trivial file, opening a remote desktop connection Hi, I'm seeing this,

Bug#818327: missing protoc plugin

2016-11-19 Thread Steinar H. Gunderson
On Wed, Mar 16, 2016 at 12:57:22AM +0100, Steinar H. Gunderson wrote: > After looking around a bit, it looks like this (and the C++ version of the > shared library) depends on protobuf 3.0.0 (beta) entering Debian, but I cannot > find a bug for that to block this one with. Seemingl

Bug#842206: nmu: Please binNMU bmusb against newer libusb-1.0

2016-10-26 Thread Steinar H. Gunderson
Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal Hi, bmusb can benefit strongly from being linked to libusb-1.0 (>= 2:1.0.21-1). Do you think it would be possible to schedule a binNMU for all architectures? Once upon a time, the format

Bug#839574: ciscolist file not installed in /etc

2016-10-02 Thread Steinar H. Gunderson
Package: snmp-mibs-downloader Version: 1.1+nmu1 Severity: normal Hi, In /etc/snmp-mibs-downloader, cisco.conf is installed, but ciscolist isn't; it's just installed into the example section in /usr/share/doc. This means that “download-mibs cisco” won't work out of the box. -- System

Bug#837571: libbmusb-dev: Please build libbmusb.a with -fPIC

2016-09-29 Thread Steinar H. Gunderson
On Thu, Sep 29, 2016 at 11:28:52PM +0200, Bálint Réczey wrote: > The set of architectures enabling PIE by default is not set yet and it looks > like we may target all architectures. > I don't know about any current issue with linking PIC static libraries. > > I suggest simply switching on all

Bug#837571: libbmusb-dev: Please build libbmusb.a with -fPIC

2016-09-29 Thread Steinar H. Gunderson
On Mon, Sep 12, 2016 at 04:32:49PM +0200, Balint Reczey wrote: > During a rebuild of all packages in sid, nageru > failed to build on amd64 with patched GCC and dpkg. The root > cause seems to be that libbmusb.a is shipped as a non-PIC library. > > The rebuild tested if packages are ready for a

Bug#838638: [Cloud-packages] Bug#838638: /usr/bin/python3-google-api-tools broken; missing several dependencies, does not work even after doing so

2016-09-23 Thread Steinar H. Gunderson
On Fri, Sep 23, 2016 at 11:27:11PM +0200, Thomas Goirand wrote: >> But in 2.7, there are tons of similar issues. > Like what? I really don't think so. pannekake:~> /usr/bin/python2-google-api-tools Traceback (most recent call last): File "/usr/bin/python2-google-api-tools", line 6, in from

Bug#838638: [Cloud-packages] Bug#838638: /usr/bin/python3-google-api-tools broken; missing several dependencies, does not work even after doing so

2016-09-23 Thread Steinar H. Gunderson
On Fri, Sep 23, 2016 at 03:47:08PM +0200, Thomas Goirand wrote: > If I'm not mistaking, that's not what's going on. httplib is a standard > Python 2.7 library, but in Python 3, it was renamed as "http". So here, > we're in a case of not-good-enough Python 3 support. But in 2.7, there are tons of

Bug#838638: /usr/bin/python3-google-api-tools broken; missing several dependencies, does not work even after doing so

2016-09-23 Thread Steinar H. Gunderson
Package: python3-google-apputils Version: 0.4.1-1 Severity: grave Hi, python3-google-apputils packages /usr/bin/python3-google-api-tools, but completely fails to declare the dependencies it needs: pannekake:~> /usr/bin/python3-google-api-tools Traceback (most recent call last): File

Bug#837397: broke SSH to HP devices

2016-09-11 Thread Steinar H. Gunderson
Package: rancid Version: 3.5.0-1 Severity: grave Hi, We're running this through the jessie backport (3.5.0-1~bpo8+1), but given that there are no changes (just a straight rebuild), I guess it should apply to the base, too. Since the upgrade, SSH to all of our HP switches have been broken:

Bug#832095: zita-resampler - debian bug

2016-09-04 Thread Steinar H. Gunderson
On Mon, Aug 29, 2016 at 06:58:24PM +, Fons Adriaensen wrote: > I wil not accept the patch in its current form, but OTOH the > code is too good to just be ignored, so I will integrate it > in another way. > > For the next release of zita-resampler I will reorganise the > code a bit, so it will

Bug#836315: unneccessary build-dependency on libmysqld-dev

2016-09-01 Thread Steinar H. Gunderson
Package: ruby-mysql2 Version: 0.4.3-2 Severity: normal Hi, ruby-mysql2 declares a Build-Dependency on libmysqld-dev. libmysqld-dev is a product known as “Embedded MySQL”; it is essentially all of mysqld packed up in a single library meant for single-user use, similar to SQLite. >From what I can

Bug#835194: NEWS file is missing

2016-08-23 Thread Steinar H. Gunderson
Package: cubemap Version: 1.3.1-1 Severity: normal Hi, It seems the NEWS file (essentially the upstream changelog) is not in /usr/share/doc/cubemap; it probably should be. -- System Information: Debian Release: 8.5 APT prefers stable APT policy: (750, 'stable'), (500, 'proposed-updates')

Bug#834500: “i” key shortcut changed meaning, to a nonsensical one

2016-08-16 Thread Steinar H. Gunderson
Package: mutt Version: 1.6.2-1 Severity: normal Hi, I upgraded mutt today, and when I press “i” to go out from a message, it suddenly started beeping and saying No news server defined! It turns out someone has remapped “i” in the message view to to “change-newsgroup”. This doesn't make sense

Bug#833365: libapache2-mpm-itk: installation fails when apache2 is not running

2016-08-05 Thread Steinar H. Gunderson
On Fri, Aug 05, 2016 at 11:20:12AM +0200, Florent Bervas wrote: > Regarding your script (libapache2-mpm-itk.postinst), the returned value > doesn't seem to be handled correctly (line 9), so should the suggested > patch be considered as a (small and modest) improvement? I also forward it > to

Bug#833365: libapache2-mpm-itk: installation fails when apache2 is not running

2016-08-03 Thread Steinar H. Gunderson
On Wed, Aug 03, 2016 at 04:43:38PM +0200, Florent Bervas wrote: > In both case, a command's result is not handled correctly as a string. When > the command "a2query -M" is executed while the apache2 server is not > running, the command returns an empty string and bash fails the comparison. Hi,

Bug#833304: closed by se...@debian.org (Steinar H. Gunderson) (Bug#833304: fixed in nageru 1.3.4-1)

2016-08-02 Thread Steinar H. Gunderson
On Wed, Aug 03, 2016 at 12:16:10AM +0200, Chris Lamb wrote: >> Fixes FTBFS. (Closes: #833304) > This seems a little terse. Could you elaborate..? I guess I could have pasted in the relevant commit from upstream: commit 156470e2dca8813f8eb736f52363e94501ab36f5 Author: Steinar H.

Bug#832095: patch for SSE-optimizing resampling of stereo signals

2016-08-02 Thread Steinar H. Gunderson
On Sun, Jul 24, 2016 at 02:24:48PM +0200, Jaromír Mikeš wrote: > as the patch is rather complex and change code quite a lot I would > like to see rather a new upstream release > including your work. Than apply it only in debian. > Or at least upstream approval of this patch. I've made another

Bug#833304: nageru: FTBFS: quicksync_encoder.cpp:996:15: error: 'close' was not declared in this scope

2016-08-02 Thread Steinar H. Gunderson
On Tue, Aug 02, 2016 at 10:41:02PM +0200, Chris Lamb wrote: >> That's odd; I built it in a pbuilder, and several buildds have built it in >> the past few days. Is there anything special about your setup? > Not that I am aware of, sorry. Up-to-date pretty minimal-ish chroot, etc., the > usual. :)

Bug#833304: nageru: FTBFS: quicksync_encoder.cpp:996:15: error: 'close' was not declared in this scope

2016-08-02 Thread Steinar H. Gunderson
On Tue, Aug 02, 2016 at 07:59:28PM +0200, Chris Lamb wrote: > nageru fails to build from source in unstable/amd64: That's odd; I built it in a pbuilder, and several buildds have built it in the past few days. Is there anything special about your setup? /* Steinar */ -- Homepage:

Bug#832549: xserver-xorg: X now defaults to using built-in modesetting video driver on Intel. X no longer functioned

2016-07-28 Thread Steinar H. Gunderson
On Thu, Jul 28, 2016 at 07:34:45PM +0200, Julien Cristau wrote: >> X broke for me, too -- the Intel driver somehow isn't autodetected anymore, >> which leads to using some unaccelerated driver (which breaks e.g. OpenGL >> pretty badly). > The intel X driver not being loaded is on purpose. That

Bug#832773: nageru: FTBFS w/o SSE: no matching Filter::init

2016-07-28 Thread Steinar H. Gunderson
On Thu, Jul 28, 2016 at 02:03:20PM -0400, Aaron M. Ucko wrote: > Builds of nageru for non-SSE architectures (i.e., all but amd64, since > x32 isn't whitelisted) have been failing: Sorry! I saw this myself and built a fixed package, but I didn't get to upload it. Will rebuild with a Closes: on

Bug#832549: xserver-xorg: X now defaults to using built-in modesetting video driver on Intel. X no longer functioned

2016-07-27 Thread Steinar H. Gunderson
On Tue, Jul 26, 2016 at 02:57:47PM -0400, jackson wrote: > Contents of /etc/X11/xorg.conf: > --- > Section "Device" > Identifier "Intel" > Driver "intel" > # Option "AccelMethod" "uxa" > EndSection X broke for me, too -- the Intel driver somehow isn't

Bug#832095: patch for SSE-optimizing resampling of stereo signals

2016-07-24 Thread Steinar H. Gunderson
On Sun, Jul 24, 2016 at 02:24:48PM +0200, Jaromír Mikeš wrote: > as the patch is rather complex and change code quite a lot I would > like to see rather a new upstream release > including your work. Than apply it only in debian. > Or at least upstream approval of this patch. That would be nice,

Bug#832154: new version 1.3.1 available

2016-07-22 Thread Steinar H. Gunderson
Package: cubemap Version: 1.3.0-1 Severity: wishlist Sorry for releasing 1.3.1 so shortly after 1.3.0! But there's a new version available, with a timestamping feature that's neat for Nageru. :-) There should be no surprises for you in packaging, from what I know. -- System Information: Debian

Bug#832097: new upstream version 1.0.21-rc1

2016-07-22 Thread Steinar H. Gunderson
On Fri, Jul 22, 2016 at 11:57:11AM +0200, Aurelien Jarno wrote: > I don't think it's appropriate for unstable yet, but I'll put it in > experimental. Thanks, that sounds reasonable. /* Steinar */ -- Homepage: https://www.sesse.net/

Bug#832097: new upstream version 1.0.21-rc1

2016-07-22 Thread Steinar H. Gunderson
Source: libusb-1.0 Version: 2:1.0.20-1 Severity: wishlist Hi, libusb-1.0 1.0.21-rc1 is out; do you think it would be possible to package it for unstable? I'm interested especially since it has zerocopy USB support that I need for my live video mixer. Thanks! -- System Information: Debian

Bug#832095: patch for SSE-optimizing resampling of stereo signals

2016-07-22 Thread Steinar H. Gunderson
this patch back in the day, and he seemed happy to accept it, but somehow just stopped answering -- I guess he got busy with other things in life. It would be nice if we could get it into Debian nevertheless (I want it for reducing CPU used in my realtime video mixer). It is taken to be by Steinar H

Bug#831054: new version 1.3.0 available

2016-07-13 Thread Steinar H. Gunderson
Package: cubemap Version: 1.2.2-1 Severity: wishlist Hi, I've just released Cubemap 1.3.0. Please package it at your leisure. :-) There should be no big surprises or upgrade issues that I know of. -- System Information: Debian Release: 8.5 APT prefers stable APT policy: (750, 'stable'),

Bug#824391: [Pkg-shadow-devel] Bug#824391: please add ttySAC* to securetty

2016-06-06 Thread Steinar H. Gunderson
On Sun, Jun 05, 2016 at 08:30:56PM -0400, Mike Frysinger wrote: > please see: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768020;msg=7 A valid point, but I'm not going to NMU shadow removing pam_securetty by default; that's pretty drastic :-) /* Steinar */ -- Homepage:

Bug#824391: [Pkg-shadow-devel] Bug#824391: please add ttySAC* to securetty

2016-06-05 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 03:01:59PM +, Serge Hallyn wrote: > Seems reasonable to me. I see there hasn't been a maintainer upload of shadow since November 2014 (there was an NMU November 2015). Does this mean that if I want this for stretch, I'll need to NMU? /* Steinar */ -- Homepage:

Bug#823552: [PATCH] dwc3-exynos: Fix deferred probing storm.

2016-05-30 Thread Steinar H. Gunderson
On Fri, May 27, 2016 at 04:26:42PM +0300, Felipe Balbi wrote: >> Sent. As a fix, there's a chance it could go into 4.7, right? > yup, shouldn't be a problem. But only after v4.7-rc1 is tagged. Seemingly v4.7-rc1 is out today (I was surprised at how quick that was). /* Steinar */ -- Homepage:

Bug#824941: linux-image-4.5.0-2-armmp-lpae: please enable PWM for ODROID boards

2016-05-29 Thread Steinar H. Gunderson
On Sun, May 29, 2016 at 01:45:49PM +0100, Ben Hutchings wrote: >> Perhaps you can enlighten me on an issue: Why don't we simply enable all >> modules? > - It's a waste of build time and a waste of disk space > - Some modules conflict with each other at run-time > - A few modules are experimental,

Bug#825688: grub-efi-arm: refuses to install to an ext* device

2016-05-29 Thread Steinar H. Gunderson
On Sun, May 29, 2016 at 11:18:51AM +0200, Steinar H. Gunderson wrote: > This is probably true, but non-Mac UEFI firmware won't speak HFS+ either, > and that's gladly allowed, even on ARM. I would say that as long as there is > a legitimate usecase for it (and chainloading from U-Boot

Bug#824941: linux-image-4.5.0-2-armmp-lpae: please enable PWM for ODROID boards

2016-05-29 Thread Steinar H. Gunderson
On Sun, May 29, 2016 at 01:45:10PM +0900, Roger Shimizu wrote: > Thanks for your suggestion! > It will be included in next sid kernel. Thanks! Perhaps you can enlighten me on an issue: Why don't we simply enable all modules? One would think that if there's a driver somewhere, it would actually

Bug#825688: grub-efi-arm: refuses to install to an ext* device

2016-05-29 Thread Steinar H. Gunderson
On Sun, May 29, 2016 at 09:02:13AM +0100, Ian Campbell wrote: > What about actual UEFI firmware? I think in general that won't speak > ext* or anything other than FAT. This is probably true, but non-Mac UEFI firmware won't speak HFS+ either, and that's gladly allowed, even on ARM. I would say

Bug#825688: grub-efi-arm: refuses to install to an ext* device

2016-05-28 Thread Steinar H. Gunderson
Package: grub-efi-arm Version: 2.02~beta2-36 Severity: normal Hi, grub-install completely refuses to install an EFI GRUB to a /boot/EFI that is not on vfat or hfs+ (the C source code has explicit checks). However, there's no good reason why, on ARM, /boot/EFI couldn't be on ext2/ext3/ext4;

Bug#824941: linux-image-4.5.0-2-armmp-lpae: please enable PWM for ODROID boards

2016-05-28 Thread Steinar H. Gunderson
On Sat, May 21, 2016 at 04:41:47PM +0200, Steinar H. Gunderson wrote: > I also no longer get errors about LEDs not being able to get a PWM line. For the sake of completeness: This also means that the heartbeat LED actually works (as soon as the right module is loaded). So double win. /* Stei

Bug#823552: Cloning to initramfs-tools

2016-05-28 Thread Steinar H. Gunderson
clone 823552 -1 reassign -1 initramfs-tools retitle -1 initramfs-tools: Must include I2C drivers when MODULES=most severity -1 normal found -1 0.125 thanks Hi, I'm splitting off an initramfs-tools bug from this kernel bug, since seemingly what caused this not to be an issue in jessie was that

Bug#823552: [PATCH] dwc3-exynos: Fix deferred probing storm.

2016-05-27 Thread Steinar H. Gunderson
On Fri, May 27, 2016 at 04:12:59PM +0300, Felipe Balbi wrote: > yes, please do that. Keep in mind, also, that we're still in the middle > of the merge window and nothing will really happen until v4.7-rc1 is > tagged. Sent. As a fix, there's a chance it could go into 4.7, right? /* Steinar */ --

Bug#823552: [PATCH] dwc3-exynos: Fix deferred probing storm.

2016-05-27 Thread Steinar H. Gunderson
On Fri, May 27, 2016 at 03:23:35PM +0530, Vivek Gautam wrote: > I don't have any concerns with the patch apart from the ones > Krzysztof has already pointed out. > LGTM. Should I repost the patch, or will people just make these commit message changes for me? I guess balbi@ is the right person to

Bug#823552: [PATCH] Re: Endless "supply vcc not found, using dummy regulator"

2016-05-27 Thread Steinar H. Gunderson
On Fri, May 27, 2016 at 03:02:48PM +0530, Vivek Gautam wrote: > Above mentioned patches were not accepted by the maintainers of generic-phy > and usb. I couldn't get any response on them for quite a long time. So, the > patches could never make it to the mainline. > I can try initiating the entire

Bug#823552: [PATCH] Re: Endless "supply vcc not found, using dummy regulator"

2016-05-26 Thread Steinar H. Gunderson
On Wed, May 25, 2016 at 07:52:36PM +0200, Steinar H. Gunderson wrote: >> Actually their are some missing patches to tune the usb3 phy. >> >> https://lkml.org/lkml/2014/10/31/266 > This explains why the default networking speed refused to go above > ~300 Mbit/sec! What ha

Bug#823552: [PATCH] Re: Endless "supply vcc not found, using dummy regulator"

2016-05-25 Thread Steinar H. Gunderson
On Wed, May 25, 2016 at 05:46:51PM +0530, Anand Moon wrote: > Actually their are some missing patches to tune the usb3 phy. > > https://lkml.org/lkml/2014/10/31/266 This explains why the default networking speed refused to go above ~300 Mbit/sec! What happened to the patches, I wonder? /*

Bug#823552: [PATCH] Re: Endless "supply vcc not found, using dummy regulator"

2016-05-24 Thread Steinar H. Gunderson
On Tue, May 24, 2016 at 05:53:34PM +0200, Krzysztof Kozlowski wrote: > exynos->clk = devm_clk_get(dev, "usbdrd30"); > if (IS_ERR(exynos->clk)) { > + // On each error path since here we need to > + // revert work done by dwc3_exynos_register_phys() >

Bug#823552: Endless "supply vcc not found, using dummy regulator"

2016-05-24 Thread Steinar H. Gunderson
On Tue, May 24, 2016 at 05:53:34PM +0200, Krzysztof Kozlowski wrote: >> Which devm_clk_get() error are you talking about? The one with susp_clk? > Now I saw your original report on Debian bugzilla. Let's stick to v4.5. I'm actually developing on 4.6, but sure. The differences are small from what

Bug#823552: Endless "supply vcc not found, using dummy regulator"

2016-05-24 Thread Steinar H. Gunderson
On Tue, May 24, 2016 at 05:06:43PM +0200, Krzysztof Kozlowski wrote: > I looked quickly through the thread and I am not sure what is exactly > your problem. My immediate problem is that the repeated (deferred) probing is causing so much logging that the system doesn't actually boot. The root

Bug#825136: patch to get ACPI thermal zones from /sys

2016-05-23 Thread Steinar H. Gunderson
rom 724d90f600bdd5c91736a54b80641a2110c403e4 Mon Sep 17 00:00:00 2001 From: "Steinar H. Gunderson" <se...@google.com> Date: Tue, 24 May 2016 00:53:10 +0200 Subject: [PATCH 1/1] Update acpi plugin to use the /sys interface. This is pretty universal now; none of my machines even have thermal zones in

Bug#823552: Endless "supply vcc not found, using dummy regulator"

2016-05-23 Thread Steinar H. Gunderson
On Mon, May 23, 2016 at 07:06:17PM +0200, Steinar H. Gunderson wrote: > Then, there's the issue of why the messages come for each deferred probe > attempt. It seems from your message this is about something in the > declaration of the device tree; I don't understand the nuances he

Bug#823552: Endless "supply vcc not found, using dummy regulator"

2016-05-23 Thread Steinar H. Gunderson
On Mon, May 23, 2016 at 05:24:55PM +0100, Mark Brown wrote: >>> Cc-ing Mark in case he has any insights (I hope I have the right email >>> address). > But nobody who works on probe deferral or made any of the suggestions I > mentioned in the message you linked to, nor anyone who works on the >

Bug#823552: Endless "supply vcc not found, using dummy regulator"

2016-05-23 Thread Steinar H. Gunderson
On Mon, May 23, 2016 at 03:47:37PM +0200, Steinar H. Gunderson wrote: > I don't understand entirely why it tries 2000+ times before it succeeds Now I do; the initramfs doesn't include i2c-exynos5, and before that is loaded, s2mps11 (the regulator) can't come up either. So fixing initramfs-to

Bug#823552: Endless "supply vcc not found, using dummy regulator"

2016-05-23 Thread Steinar H. Gunderson
On Sat, May 21, 2016 at 04:43:08PM +0200, Steinar H. Gunderson wrote: > I still have this problem. > > I've noticed that somehow, there's a huge amount of USB PHYs being > autodetected; > probably related to this issue. > > sesse@soldroid:~$ ls -ld /sys/devices/plat

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
On Sun, May 22, 2016 at 09:42:38PM +0200, Steinar H. Gunderson wrote: > Well, if you count number of device trees, it's about 110 devices out of > 741 (having heartbeat or default-on as policy). So it's a minority (at least > if you don't try to weight by number of sold devices, wh

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
On Sun, May 22, 2016 at 08:10:18PM +0100, Ben Hutchings wrote: > We build in code because we have to, not because it's merely useful. > And here we're talking about modules that are useful for only a small > proportion of armhf systems. Well, if you count number of device trees, it's about 110

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
On Sun, May 22, 2016 at 07:49:35PM +0100, Ben Hutchings wrote: > The device tree already tells the kernel what trigger should be used, > and the kernel can then make the decision whether that requires loading > a module. Does this mean the initramfs would also need to know that the module should

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
On Sun, May 22, 2016 at 05:23:08PM +0200, Steinar H. Gunderson wrote: > My ODROID XU4 has a blue LED on it, which, after # has been fixed, I meant #824941. /* Steinar */ -- Homepage: https://www.sesse.net/

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

2016-05-22 Thread Steinar H. Gunderson
Package: src:linux Version: 4.5.3-2 Severity: normal Hi, My ODROID XU4 has a blue LED on it, which, after # has been fixed, is supposed to be a heartbeat LED, being solid-on during the bootloader and then flashing when the OS is active. (The manual says so, and “heartbeat” is the default mapping

Bug#824954: flash-kernel: please provide a way to integrate with GRUB

2016-05-21 Thread Steinar H. Gunderson
Package: flash-kernel Version: 3.66 Severity: wishlist Hi, I have an ODROID XU4 (a SBC based on Exynos5422). Since I'm one of those PC people that would like everything to work like my PC does, I use GRUB on it (plus, it gives me a nice boot menu when I can choose older kernels or rescue mode,

Bug#824941: linux-image-4.5.0-2-armmp-lpae: please enable PWM for ODROID boards

2016-05-21 Thread Steinar H. Gunderson
Package: src:linux Version: 4.5.3-2 Severity: wishlist Hi again, I've been diffing upstream's .config file against Debian's armmp config, and I found a setting that I'd like you to include: CONFIG_PWM_SAMSUNG=m CONFIG_SENSORS_PWM_FAN=m With these two together, my ODROID-XU4 no longer spins

Bug#824535: vlan: no way to hotplug a VLAN device

2016-05-17 Thread Steinar H. Gunderson
On Tue, May 17, 2016 at 11:23:51AM +0200, Ard van Breemen wrote: >> I've got an ARM system where eth0 is hotplugged pretty slowly >> (it hangs off of USB, and takes a while to initialize), so for >> networking to work in general, the system needs to be able to >> hotplug it. Thus, I have: > I

Bug#824535: vlan: no way to hotplug a VLAN device

2016-05-17 Thread Steinar H. Gunderson
Package: vlan Version: 2.0 Severity: important Hi, I've got an ARM system where eth0 is hotplugged pretty slowly (it hangs off of USB, and takes a while to initialize), so for networking to work in general, the system needs to be able to hotplug it. Thus, I have: allow-hotplug eth0 iface

Bug#824491: udev: impossible to disable predictable network interface names

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 09:52:10PM +0200, Michael Biebl wrote: > This is the culprit, i.e. 73-special-net-names.rules. Blacklisting that > rules file should give you the kernel names back. Thanks! Indeed it does. I don't know who maintains the freedesktop.org page, but I suppose it should be

Bug#824491: udev: impossible to disable predictable network interface names

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 09:59:20PM +0200, Michael Biebl wrote: > journalctl | less > wraps the lines here Sure, but journalctl alone doesn't, and journalctl | less disables syntax highlighting. > You can override > $SYSTEMD_PAGER and $SYSTEMD_LESS if you want custom behaviour. Thanks. /*

Bug#824491: udev: impossible to disable predictable network interface names

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 09:22:45PM +0200, Michael Biebl wrote: > I'm using > lsinitramfs /boot/initrd.img-$(uname -r) | grep rules Ah, there's an lsinitramfs! Well, there the file is, indeed. >> May 16 19:10:21 soldroid systemd-udevd[1022]: IMPORT '/sbin/ifrename -u -i >> eth0'

Bug#824491: udev: impossible to disable predictable network interface names

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 09:07:32PM +0200, Michael Biebl wrote: > That's odd. Which initramfs-tools version is that? 0.125. > Do you have any custom hooks in /etc/initramfs-tools? No. > If you check /usr/share/initramfs-tools/hooks/udev, you'll see that > 80-net-setup-link.rules is copied into

Bug#824435: please enable CONFIG_EXYNOS_VIDEO

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 07:29:46PM +0100, Ben Hutchings wrote: >> ccache is probably a good idea. I ended up mostly just cp-ing the merged >> config from /boot, so I could do with just building one kernel instead of >> multiple ones. > Oh, of course there is: >

Bug#824435: please enable CONFIG_EXYNOS_VIDEO

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 07:14:15PM +0100, Ben Hutchings wrote: >> On a guess, the relevant parts would probably be >> >>   CONFIG_EXYNOS_VIDEO=m >>   CONFIG_EXYNOS_MIPI_DSI=m > That still won't work. OK, that's everything under that heading. >>   CONFIG_DRM_EXYNOS=m >>  

Bug#824494: lvm2: should filter RPMB devices

2016-05-16 Thread Steinar H . Gunderson
Package: lvm2 Version: 2.02.153-1 Severity: minor Hi, I have an ARM-based device where I run LVM on /dev/mmcblk0p1; however, during pvscan (which includes initramfs), it complains with: root@soldroid:~# pvscan /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error

Bug#824491: udev: impossible to disable predictable network interface names

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 07:49:25PM +0200, Michael Biebl wrote: 1. ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules >>> Have you rebuilt the initramfs after that change? Does the initramfs >>> contain the rules file? >> No on both counts. > If you rebuild the initramfs (see

Bug#824491: udev: impossible to disable predictable network interface names

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 07:21:08PM +0200, Michael Biebl wrote: >> Error: argument "enx001e06303327.20" is wrong: "name" too long > That sounds like a bug on its own Yes. Although perhaps it's a kernel limitation? >> 1. ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules > Have you

Bug#824435: please enable CONFIG_EXYNOS_VIDEO

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 02:43:06PM +0200, Steinar H. Gunderson wrote: > CONFIG_ARM_EXYNOS_CPUIDLE=y seems to cause problems, so I turned that off. > Apart from that, setting the variables above on 4.6.0 gives me wonderful > fbcon on the XU4. Scratch that, th

Bug#824435: please enable CONFIG_EXYNOS_VIDEO

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 11:14:26AM +0200, Steinar H. Gunderson wrote: > On a guess, the relevant parts would probably be > > CONFIG_EXYNOS_VIDEO=m > CONFIG_EXYNOS_MIPI_DSI=m > CONFIG_DRM_EXYNOS=m > CONFIG_DRM_EXYNOS_MIXER=y [not in that config,

Bug#824435: please enable CONFIG_EXYNOS_VIDEO

2016-05-16 Thread Steinar H. Gunderson
On Mon, May 16, 2016 at 01:44:38AM +0100, Ben Hutchings wrote: > That has no useful effect, as it is a boolean option that only enables > a menu of further options. > > Please explain what changes are really needed. Hm. I was trying to compile a kernel to verify this, but it took more than

Bug#824435: please enable CONFIG_EXYNOS_VIDEO

2016-05-15 Thread Steinar H. Gunderson
Package: linux-image-4.5.0-2-armmp-lpae Version: 4.5.3-2 Severity: wishlist Hi, The ODROID XU3/XU4 run linux-image-4.5.0-2-armmp-lpae quite well (barring cpufreq and proper big.LITTLE support), but there's no video output support, only serial console. Would you please consider setting

Bug#824356: closed by Vagrant Cascadian <vagr...@aikidev.net> (Re: Bug#824356: XU4 does not boot)

2016-05-15 Thread Steinar H. Gunderson
On Sun, May 15, 2016 at 12:53:33AM +0200, Steinar H. Gunderson wrote: > I suppose there's no d-i support happening for the XU4 anytime soon? :-) I figured not, so I hacked together some images myself (based on said U-Boot!). You may or may not be interested: http://storage.sesse.net/debian-

Bug#824403: O: pvm -- Parallel Virtual Machine

2016-05-15 Thread Steinar H. Gunderson
On Sun, May 15, 2016 at 04:03:49PM +0100, James Clarke wrote: > As discussed in [1], the maintainer wants to orphan this package. There > have been no maintainer uploads since squeeze, with the current version > in unstable (3.4.5-12.6, same as jessie) being the 6th NMU. There is > also a new

Bug#824399: Missing devicetree statements for ARM

2016-05-15 Thread Steinar H. Gunderson
Package: grub-common Version: 2.02~beta2-36 Severity: normal Hi, I'm setting up GRUB on my ODROID XU4 (chainloading via U-Boot). It actually works surprisingly well, but grub-mkconfig has one serious omission; it doesn't load the device tree, which causes the kernel not to boot. I suppose the

Bug#824389: grub-efi-arm-bin: the .efi file itself is missing

2016-05-15 Thread Steinar H. Gunderson
On Sun, May 15, 2016 at 11:39:39AM +0200, Steinar H. Gunderson wrote: > Debian ships a package “grub-efi-arm-bin” that's supposed to contain an .efi > image (and “grub-efi-arm” that wraps in some /etc/kernel hooks), and U-Boot > is set up to search for it, but all it contains are the GRU

Bug#824349: Bug#824389: grub-efi-arm-bin: the .efi file itself is missing

2016-05-15 Thread Steinar H. Gunderson
On Sun, May 15, 2016 at 12:43:13PM +0200, Steinar H. Gunderson wrote: > I can confirm that if I build the .efi manually, it does indeed work and > boot a working GRUB (given an appropriate device tree already in /boot/dtbs): Sorry, wrong bug number. Please ignore. /* Steinar */ -- Ho

Bug#824349: Bug#824389: grub-efi-arm-bin: the .efi file itself is missing

2016-05-15 Thread Steinar H. Gunderson
On Sun, May 15, 2016 at 11:39:39AM +0200, Steinar H. Gunderson wrote: > Debian ships a package “grub-efi-arm-bin” that's supposed to contain an .efi > image (and “grub-efi-arm” that wraps in some /etc/kernel hooks), and U-Boot > is set up to search for it, but all it contains are the GRU

Bug#824391: please add ttySAC* to securetty

2016-05-15 Thread Steinar H. Gunderson
Package: login Version: 1:4.2-3.1 Severity: normal Hi, I have an ODROID XU4 (an ARM-based board). Its serial console comes up by default on /dev/ttySAC2; however, there's no entry for that in /dev/securetty, so it's impossible to log in as root on the serial console. Do you think you could add

Bug#824389: grub-efi-arm-bin: the .efi file itself is missing

2016-05-15 Thread Steinar H. Gunderson
Package: grub-efi-arm-bin Version: 2.02~beta2-22 Severity: grave Justification: breaks entire (binary) package Hi, Debian ships a package “grub-efi-arm-bin” that's supposed to contain an .efi image (and “grub-efi-arm” that wraps in some /etc/kernel hooks), and U-Boot is set up to search for it,

Bug#824356: closed by Vagrant Cascadian <vagr...@aikidev.net> (Re: Bug#824356: XU4 does not boot)

2016-05-14 Thread Steinar H. Gunderson
On Sat, May 14, 2016 at 10:42:05PM +, Debian Bug Tracking System wrote: > Well, first issue is that u-boot target is for older Odroid boards based > on exynos4. You'll want the odroid-xu3 target to use with Odroid-XU4. Wow, that wasn't so easy to guess; there's a odroid target and a README

Bug#824356: XU4 does not boot

2016-05-14 Thread Steinar H. Gunderson
Package: u-boot-exynos Version: 2016.03+dfsg1-4 Severity: important Hi, I'm trying to make a bootable SD card on my XU4 (100% compatible with XU3). It works fine if I use the binary U-Boot binary from Hardkernel, but it is a relatively old U-Boot, and I'd like to use Debian's instead. However,

Bug#824153: 08_hlogin_paging.patch breaks all (?) ProCurve logins

2016-05-12 Thread Steinar H. Gunderson
Package: rancid Version: 3.4.1-3 Severity: grave Hi, Since upgrading to 3.4.x (from an upstream 2.3.9), HP ProCurve logins have been completely broken for me. It turns out 08_hlogin_paging.patch breaks this; it makes hlogin send “no page\r” and then wait for first a partial prompt (the

Bug#823552: endless "supply vcc not found, using dummy regulator"

2016-05-10 Thread Steinar H. Gunderson
On Thu, May 05, 2016 at 11:29:18PM +0200, Steinar H. Gunderson wrote: > I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid > and > installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and updating > boot.ini -- I'm not entirely sure if this can

Bug#823955: grub-uboot: crashed during load from U-Boot (Exynos 5422)

2016-05-10 Thread Steinar H. Gunderson
Package: grub-uboot Version: 2.02~beta2-36 Severity: important Hi, I have an ODROID XU4 (Exynos 5422-based), and I want to run GRUB (chainloaded from U-Boot). I've been generally following the instructions on https://wiki.linaro.org/LEG/Engineering/Kernel/GRUBonUBOOT In particular, I've run

Bug#823552: endless "supply vcc not found, using dummy regulator"

2016-05-05 Thread Steinar H. Gunderson
On Thu, May 05, 2016 at 11:01:48PM +0100, Ben Hutchings wrote: >> I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid >> and >> installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and >> updating >> boot.ini -- I'm not entirely sure if this can be done more

<    1   2   3   4   5   6   7   8   9   10   >