Debian Bug report logs - #837629
u-boot 2016.09~rc2+dfsg1-1 bricks my openrd ultimate

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@rcthomas.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: u-boot 2016.09~rc2+dfsg1-1 bricks my openrd ultimate

Date: Mon, 12 Sep 2016 20:09:03 -0700

Package: u-boot
Version: 2016.09~rc2+dfsg1-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
As requested by Vagrant I'm testing u-boot 2016.09~rc2+dfsg1-1 on my OpenRD Ultimate machine.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I followed the instructions for upgrading u-boot on Martin's web page at
         https://www.cyrius.com/debian/kirkwood/openrd/uboot-upgrade/
   * What was the outcome of this action?
After telling u-boot to "reset", the machine went dead.  There was no output on the serial console, no answer to ping ... nothing.
   * What outcome did you expect instead?
I expected it to reset and reboot.  But it didn't do that.

*** End of the template - remove these template lines ***

I unbricked it follwing the instructions at
        https://www.newit.co.uk/forum/index.php?topic=2835.0
and I'm writing this bugreport on it.  It boots using
        U-Boot 2016.03+dfsg1-3 (Apr 04 2016 - 18:23:06 +0000)

Please advise what I can do to help debug this.


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (900, 'stable-updates'), (900, 'testing'), (900, 'stable'), (50, 'unstable')
Architecture: armel (armv5tel)

Kernel: Linux 4.6.0-1-marvell
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Message #10 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>

Cc: Karsten Merker <merker@debian.org>, u-boot@packages.debian.org, 837629@bugs.debian.org

Subject: Re: u-boot 2016.09 in Debian

Date: Wed, 14 Sep 2016 21:31:06 -0700

On Sep 14, 2016, at 5:31 PM, Vagrant Cascadian <vagrant@debian.org> wrote:

> Worst case, we have to remove it from stretch again if it really is that
> bad...

I’ll certainly do the test.  If it still doesn’t work on the OpenRD, I would not remove it from stretch just yet.  Frankly, there just aren’t that many OpenRD machines out there, and it works on everything else we’ve tested it on — including my non-ESATA SheevaPlug.  If we can’t fix it for OpenRD, we’ll have to put a warning in NEWS.Debian, but IMHO that’s not a reason for denying its benefits to all the other machine types.

BTW, are there in fact any new features, or is it just a collection of bug fixes?

Enjoy!
Rick

Message #15 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>

Cc: Karsten Merker <merker@debian.org>, u-boot@packages.debian.org

Subject: Re: u-boot 2016.09 in Debian

Date: Wed, 14 Sep 2016 17:13:04 -0700

> On Sep 12, 2016, at 2:37 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
> 
> On 2016-09-10, Karsten Merker wrote:
>> On Mon, Sep 05, 2016 at 09:22:23AM -0700, Vagrant Cascadian wrote:
>>> The current u-boot packages in Debian experimental (2016.09~rc2+dfsg1-1)
>>> appear to be working fine for the platforms I've tested, and I would
>>> like to upload 2016.09 to unstable in the next few weeks, which is
>>> scheduled to be released on September 12th:
> 
> And uploaded to Debian unstable just now…

in light of bug 837629 (u-boot 2016.09~rc2+dfsg1-1 bricks my openrd ultimate), is there enough difference between that and the version you just uploaded to unstable to warrant my trying the version from unstable?

Thanks!
Rick

Message #20 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: Rick Thomas <rbthomas@pobox.com>

Cc: Karsten Merker <merker@debian.org>, u-boot@packages.debian.org

Subject: Re: u-boot 2016.09 in Debian

Date: Wed, 14 Sep 2016 17:31:58 -0700

On 2016-09-14, Rick Thomas wrote:
>> On Sep 12, 2016, at 2:37 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>> 
>> On 2016-09-10, Karsten Merker wrote:
>>> On Mon, Sep 05, 2016 at 09:22:23AM -0700, Vagrant Cascadian wrote:
>>>> The current u-boot packages in Debian experimental (2016.09~rc2+dfsg1-1)
>>>> appear to be working fine for the platforms I've tested, and I would
>>>> like to upload 2016.09 to unstable in the next few weeks, which is
>>>> scheduled to be released on September 12th:
>> 
>> And uploaded to Debian unstable just now…
> 
> in light of bug 837629 (u-boot 2016.09~rc2+dfsg1-1 bricks my openrd
> ultimate), is there enough difference between that and the version you
> just uploaded to unstable to warrant my trying the version from
> unstable?

It would be great if you could test the version in unstable, too, and
update in the bug report with additional information, be it positive or
negative...

Worst case, we have to remove it from stretch again if it really is that
bad...


live well,
 vagrant

Message #25 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: Rick Thomas <rbthomas@pobox.com>

Cc: 837629@bugs.debian.org

Subject: Re: u-boot 2016.09 in Debian

Date: Thu, 15 Sep 2016 22:43:37 -0700

[Message part 1 (text/plain, inline)]

Control: severity 837629 serious

On 2016-09-14, Rick Thomas wrote:
> On Sep 14, 2016, at 5:31 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>
>> Worst case, we have to remove it from stretch again if it really is that
>> bad...
>
> I’ll certainly do the test.  If it still doesn’t work on the OpenRD, I
> would not remove it from stretch just yet.  Frankly, there just aren’t
> that many OpenRD machines out there, and it works on everything else
> we’ve tested it on — including my non-ESATA SheevaPlug.  If we can’t
> fix it for OpenRD, we’ll have to put a warning in NEWS.Debian, but
> IMHO that’s not a reason for denying its benefits to all the other
> machine types.

No, a warning in NEWS.Debian is not good enough; I meant removing the
targets that "brick" devices. There's no point in shipping something
known to be broken in ways that cause boot failures.

At one point I disabled the OpenRD* targets as it was failing to
build... now we're in a similar situation, only they fail to boot at all
even though they build, which is considerably more dangerous...

Upgrading the severity to prevent migration to stretch, until we have
a better handle on the situation...


live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>, 837629@bugs.debian.org

Subject: Re: Bug#837629: u-boot 2016.09 in Debian

Date: Thu, 15 Sep 2016 23:54:40 -0700

On Sep 15, 2016, at 10:43 PM, Vagrant Cascadian <vagrant@debian.org> wrote:

> Control: severity 837629 serious
> 
> On 2016-09-14, Rick Thomas wrote:
>> On Sep 14, 2016, at 5:31 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>> 
>>> Worst case, we have to remove it from stretch again if it really is that
>>> bad...
>> 
>> I’ll certainly do the test.  If it still doesn’t work on the OpenRD, I
>> would not remove it from stretch just yet.  Frankly, there just aren’t
>> that many OpenRD machines out there, and it works on everything else
>> we’ve tested it on — including my non-ESATA SheevaPlug.  If we can’t
>> fix it for OpenRD, we’ll have to put a warning in NEWS.Debian, but
>> IMHO that’s not a reason for denying its benefits to all the other
>> machine types.
> 
> No, a warning in NEWS.Debian is not good enough; I meant removing the
> targets that "brick" devices. There's no point in shipping something
> known to be broken in ways that cause boot failures.

That would work, too.

> At one point I disabled the OpenRD* targets as it was failing to
> build... now we're in a similar situation, only they fail to boot at all
> even though they build, which is considerably more dangerous...
> 
> Upgrading the severity to prevent migration to stretch, until we have
> a better handle on the situation…

OK.  I’ll do the test ASAP (probably Friday or Saturday).  Please let me know if there’s anything else I can do to help get this debugged.  I’ll also try it on my OpenRD “Client” machine, incase the problem is specific to that one device.

> live well,
>  vagrant

Message #37 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>

Cc: rbthomas@rcthomas.org, 837629@bugs.debian.org

Subject: OpenRD* with debian's u-boot 2016.09

Date: Fri, 16 Sep 2016 15:19:24 -0700

[Message part 1 (text/plain, inline)]

There is at one report of an OpenRD ultimate that would not boot with
the 2016.09~rc2 version of u-boot in debian. Uploaded 2016.09+dfsg-1 to
unstable a few days ago. Would you be able to confirm if OpenRD variants
that you have still work with the version in unstable?

  https://bugs.debian.org/837629

If it can't be fixed, I'll likely remove OpenRD ultimate at some point
so that u-boot 2016.09 can migrate to stretch... but it would be more
ideal to fix it, of course! :)


live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #42 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>, 837629@bugs.debian.org

Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Sat, 17 Sep 2016 16:33:59 -0700

On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian <vagrant@debian.org> wrote:

> There is at one report of an OpenRD ultimate that would not boot with
> the 2016.09~rc2 version of u-boot in debian. Uploaded 2016.09+dfsg-1 to
> unstable a few days ago. Would you be able to confirm if OpenRD variants
> that you have still work with the version in unstable?
> 
>  https://bugs.debian.org/837629
> 
> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
> so that u-boot 2016.09 can migrate to stretch... but it would be more
> ideal to fix it, of course! :)
> 
> 
> live well,
>  vagrant

Sorry!

It looks like you’ll have to pull OpenRD support out of this version.  I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no response following u-boot “reset” command.

Enjoy!
Rick

Message #47 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: Rick Thomas <rbthomas@pobox.com>, 837629@bugs.debian.org

Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Sat, 01 Oct 2016 15:39:14 -0700

[Message part 1 (text/plain, inline)]

On 2016-09-17, Rick Thomas wrote:
> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>>  https://bugs.debian.org/837629
>> 
>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>> ideal to fix it, of course! :)
>
> It looks like you’ll have to pull OpenRD support out of this version.
> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
> response following u-boot “reset” command.

I've uploaded packages based on 2016.09.01 to:

  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main

The repository should be signed by my key, available in the
debian-keyring package in the archive
(F0ADA5240891831165DF98EA7CFCD8CD257721E9).

There were two critical fixes in 2016.09.01, *maybe* they fix the issue?

If not, I'll likely be removing OpenRD* from the packages on future
uploads.


live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #52 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>

Cc: 837629@bugs.debian.org, Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Sat, 1 Oct 2016 17:32:15 -0700

OK.  I’ll give it a try.

More when I know more.

Rick

On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian <vagrant@debian.org> wrote:

> On 2016-09-17, Rick Thomas wrote:
>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>>> https://bugs.debian.org/837629
>>> 
>>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>>> ideal to fix it, of course! :)
>> 
>> It looks like you’ll have to pull OpenRD support out of this version.
>> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
>> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
>> response following u-boot “reset” command.
> 
> I've uploaded packages based on 2016.09.01 to:
> 
>  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
> 
> The repository should be signed by my key, available in the
> debian-keyring package in the archive
> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
> 
> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?
> 
> If not, I'll likely be removing OpenRD* from the packages on future
> uploads.
> 
> 
> live well,
>  vagrant

Message #57 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>

Cc: 837629@bugs.debian.org, Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Mon, 3 Oct 2016 00:23:43 -0700

On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian <vagrant@debian.org> wrote:

> On 2016-09-17, Rick Thomas wrote:
>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>>> https://bugs.debian.org/837629
>>> 
>>> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
>>> so that u-boot 2016.09 can migrate to stretch... but it would be more
>>> ideal to fix it, of course! :)
>> 
>> It looks like you’ll have to pull OpenRD support out of this version.
>> I tried 2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result
>> with it as I got with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no
>> response following u-boot “reset” command.
> 
> I've uploaded packages based on 2016.09.01 to:
> 
>  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
> 
> The repository should be signed by my key, available in the
> debian-keyring package in the archive
> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
> 
> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?
> 
> If not, I'll likely be removing OpenRD* from the packages on future
> uploads.
> 
> 
> live well,
>  vagrant

Sadly, it doesn’t look like it fixed the problem.  Still nothing after installing the new u-boot.kwb and typing “reset”.

let me know if there’s anything more I can do to help…

Rick

Message #62 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: Rick Thomas <rbthomas@pobox.com>, 837629@bugs.debian.org

Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Wed, 05 Oct 2016 13:26:42 -0700

[Message part 1 (text/plain, inline)]

On 2016-10-03, Rick Thomas wrote:
> On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>> On 2016-09-17, Rick Thomas wrote:
>>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>>>> https://bugs.debian.org/837629
...
>>  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
>> 
>> The repository should be signed by my key, available in the
>> debian-keyring package in the archive
>> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
>> 
>> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?

And now uploaded 2016.11~rc1 to my "UNRELEASED" repository, please test
that...


>> If not, I'll likely be removing OpenRD* from the packages on future
>> uploads.
...
> Sadly, it doesn’t look like it fixed the problem.  Still nothing after
> installing the new u-boot.kwb and typing “reset”.
>
> let me know if there’s anything more I can do to help…

If it's not fixed in 2016.11~rc1, the only thing left to try is git
bisecting the issue...


live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #67 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>, 837629@bugs.debian.org

Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, Rick Thomas <rbthomas@rcthomas.org>

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Fri, 7 Oct 2016 01:34:05 -0700

On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian <vagrant@debian.org> wrote:

> And now uploaded 2016.11~rc1 to my "UNRELEASED" repository, please test
> that…

Will do. Sometime this weekend.

> 
>> let me know if there’s anything more I can do to help…
> 
> If it's not fixed in 2016.11~rc1, the only thing left to try is git
> bisecting the issue...

Are you located in the US?

If you think it would help, I could loan you one of the OpenRD devices,
as long as I can ship it without getting customs and immigration involved.

Rick

Message #72 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: 837629@bugs.debian.org, Rick Thomas <rbthomas@pobox.com>

Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Mon, 17 Oct 2016 11:25:14 -0700

[Message part 1 (text/plain, inline)]

On 2016-10-05, Vagrant Cascadian wrote:
> On 2016-10-03, Rick Thomas wrote:
>> On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>>> On 2016-09-17, Rick Thomas wrote:
>>>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
...
>>> If not, I'll likely be removing OpenRD* from the packages on future
>>> uploads.
> ...
>> Sadly, it doesn’t look like it fixed the problem.  Still nothing after
>> installing the new u-boot.kwb and typing “reset”.
>>
>> let me know if there’s anything more I can do to help…
>
> If it's not fixed in 2016.11~rc1, the only thing left to try is git
> bisecting the issue...

Could also try building with a different version of gcc (e.g. the one in
jessie, or gcc-5* from sid, which may take more configuring). There may
be issues triggered by gcc-6...


live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #77 received at 837629-close@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: 837629-close@bugs.debian.org

Subject: Bug#837629: fixed in u-boot 2016.09+dfsg1-2

Date: Mon, 24 Oct 2016 05:50:41 +0000

Source: u-boot
Source-Version: 2016.09+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
u-boot, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837629@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian <vagrant@debian.org> (supplier of updated u-boot package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 23 Oct 2016 19:36:36 -0700
Source: u-boot
Binary: u-boot u-boot-imx u-boot-qcom u-boot-tegra u-boot-omap u-boot-sunxi u-boot-exynos u-boot-rockchip u-boot-rpi u-boot-tools
Architecture: source
Version: 2016.09+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian <vagrant@debian.org>
Changed-By: Vagrant Cascadian <vagrant@debian.org>
Description:
 u-boot     - A boot loader for embedded systems
 u-boot-exynos - A boot loader for exynos systems
 u-boot-imx - A boot loader for imx systems
 u-boot-omap - A boot loader for omap systems
 u-boot-qcom - A boot loader for qcom systems
 u-boot-rockchip - A boot loader for rockchip systems
 u-boot-rpi - A boot loader for Raspberry PI systems
 u-boot-sunxi - A boot loader for sunxi systems
 u-boot-tegra - A boot loader for NVIDIA Tegra systems
 u-boot-tools - companion tools for Das U-Boot bootloader
Closes: 837629 841351
Changes:
 u-boot (2016.09+dfsg1-2) unstable; urgency=medium
 .
   * odroid-xu3: Add patch to use the default bootdelay from
     distro_bootcmd.
   * Remove Philip Rinn from Cubieboard2 testers.
   * u-boot-rpi: Add documentation for configuring raspberry pi to use
     u-boot.
   * debian/watch: Add signature checking of upstream tarball.
   * u-boot-tools: Add device-tree-compiler to Recommends. Thanks to
     Pierre-Hugues Husson.  (Closes: #841351).
   * Apply patches from v2016.09.01:
     - 0001-Revert-Increase-default-of-CONFIG_SYS_MALLOC_F_LEN-f.patch
     - 0002-Revert-image-fit-switch-ENOLINK-to-ENOENT.patch
   * Remove openrd targets, as they do not boot (Closes: #837629).
Checksums-Sha1:
 262612f012864c641f1fe76021c0a65264d507ce 2660 u-boot_2016.09+dfsg1-2.dsc
 2ea9d5c60d0ae1d3406104b632d661ad42d4aa04 36572 u-boot_2016.09+dfsg1-2.debian.tar.xz
Checksums-Sha256:
 df4ed781583d47363e0966da067e62fc9f6e968a11bde2944ff82a4902b69794 2660 u-boot_2016.09+dfsg1-2.dsc
 80e91072446b638a86e03dcd11660426ef83823ecc86d10ce39d568cd36c350c 36572 u-boot_2016.09+dfsg1-2.debian.tar.xz
Files:
 5fffac88b33ccca02fecb1daa860e222 2660 admin optional u-boot_2016.09+dfsg1-2.dsc
 cd1ec8c914b34a6a9112f48aa5789d4f 36572 admin optional u-boot_2016.09+dfsg1-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIwBAEBCgAaBQJYDXRAExx2YWdyYW50QGRlYmlhbi5vcmcACgkQt4uC1IFLkbb+
8g/+MWJoH5RRlVkT9ySBFRaWUQMumbMuYt3SJygZLunQLSQhQDYimZFNfHlnRZpA
KsoIa8O6eXmfbANDfZ+o8K18mVg9DxrbIQrLCwWgnQSo2b73dvnP2Ojr8TFjFaTx
y3HTxps5BCSVvjfGOHBDeqmkUHkNuC8PqVWBUefi7yhvjkx/42P01sPfHnOpR3/6
nRH7kkd6vng70RedlbTEKCHKXrM1Ebu55zmlL9Yri69PU3D16/xhiJIOrn8Eh86K
muuPtbXKLfMM2ytU1PUnNggY+7BWfpyMGxeByxy3pVwg+pZ9bfDOdv5pvO0CJJ62
3OU7ILK67fb6VK97IW6J8GmbN2DyQuHbPfvZdmNCooaQtQt3s7kH/ae4GDo7oeAF
FUlfEDXKlU1NQw/+KHwqrQET147+PQVrs2bn++3+PZAeiF+zTujQAiU5lCjaWtBh
OrmR1+j3QT/Wy7JN8yctsMIRKYfnJMQEHHOPSur6zIZ4SlJX1HQ3sRRAvoeOXRyn
VPWsdysWrOskl+x+eRy+0/E2E72hoQnkNS+rzeximoAoZlUagrOClnw1IQqE18lO
5gIh54zXp9cGAFnZgRFWFrmk+ti4DtuNz/TdQJzfthcbV6UaXdUEWHw7lIJLTaBW
+OJTV4JMnvoqOPPnRbTrL4IdaPXmJw4wbHzgcyEkijzx3Qc=
=8Pqd
-----END PGP SIGNATURE-----

Message #82 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>

Cc: 837629@bugs.debian.org, Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Thu, 27 Oct 2016 18:31:23 -0700

On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian <vagrant@debian.org> wrote:

> On 2016-10-03, Rick Thomas wrote:
>> On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>>> On 2016-09-17, Rick Thomas wrote:
>>>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>>>>> https://bugs.debian.org/837629
> ...
>>> deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
>>> 
>>> The repository should be signed by my key, available in the
>>> debian-keyring package in the archive
>>> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
>>> 
>>> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?
> 
> And now uploaded 2016.11~rc1 to my "UNRELEASED" repository, please test
> that...
> 
> 
>>> If not, I'll likely be removing OpenRD* from the packages on future
>>> uploads.
> ...
>> Sadly, it doesn’t look like it fixed the problem.  Still nothing after
>> installing the new u-boot.kwb and typing “reset”.
>> 
>> let me know if there’s anything more I can do to help…
> 
> If it's not fixed in 2016.11~rc1, the only thing left to try is git
> bisecting the issue...
> 
> 
> live well,
>  vagrant

Hi,

It’s been an “interesting” month (in the sense of the ancient curse: “May you live in interesting times!”)

Unfortunately testing u-boot on OpenRD fell by the wayside.
I gather that the current u-boot in experimental has OpenRD support removed?

But… as of now, all the “interesting” bits are temporarily under control.
Would you like me to test something?

Rick

Message #87 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: Rick Thomas <rbthomas@pobox.com>, 837629@bugs.debian.org

Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Wed, 02 Nov 2016 10:38:06 -0700

[Message part 1 (text/plain, inline)]

On 2016-10-27, Rick Thomas wrote:
> On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian <vagrant@debian.org> wrote:
>> On 2016-10-03, Rick Thomas wrote:
>>>> deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
>>>> 
>>>> The repository should be signed by my key, available in the
>>>> debian-keyring package in the archive
>>>> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
...
> Unfortunately testing u-boot on OpenRD fell by the wayside.
> I gather that the current u-boot in experimental has OpenRD support removed?

Both in experimental and unstable.


> But… as of now, all the “interesting” bits are temporarily under control.
> Would you like me to test something?

I've uploaded u-boot 2016.11~rc3 to the cascadia.debian.net
repository. I won't hold my breath, but give it a try...


Another option which might help debug the issue is to build u-boot
mainline from source with an older GCC, such as what's shipped in
jessie. You could then build the individual targets rather than the
whole package, and it shouldn't take too long. Could also insert some
printf statements in the early boot, maybe to figure out exactly where
it is failing...


live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #92 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>

Cc: 837629@bugs.debian.org, Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Wed, 2 Nov 2016 10:51:27 -0700

On Nov 2, 2016, at 10:38 AM, Vagrant Cascadian <vagrant@debian.org> wrote:

> I've uploaded u-boot 2016.11~rc3 to the cascadia.debian.net
> repository. I won’t hold my breath, but give it a try...

I will.  No promises on the target date, but “soon”!  (-;

> Another option which might help debug the issue is to build u-boot
> mainline from source with an older GCC, such as what's shipped in
> jessie. You could then build the individual targets rather than the
> whole package, and it shouldn't take too long. Could also insert some
> printf statements in the early boot, maybe to figure out exactly where
> it is failing...

I’ve never done anything like that.  (Though I’m familiar with the usual UNIX software development tools, such as gnu-autoconf, gcc and make, etc.  And I’d be glad to learn what I don’t know.) Would you be willing to walk me through the steps?

Thanks!
Rick

Message #97 received at 837629@bugs.debian.org (full text, mbox, reply):

From: Rick Thomas <rbthomas@pobox.com>

To: Vagrant Cascadian <vagrant@debian.org>, 837629@bugs.debian.org

Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>, Philip Hands <phil@hands.com>, rbthomas@rcthomas.org

Subject: Re: Bug#837629: OpenRD* with debian's u-boot 2016.09

Date: Sat, 12 Nov 2016 17:21:16 -0800

On 11/02/16 10:38, Vagrant Cascadian wrote:
> I've uploaded u-boot 2016.11~rc3 to the cascadia.debian.net
> repository. I won't hold my breath, but give it a try...
Good thing you didn't hold your breath.  I tried it.  Same result as 
before:  No response after "reset".

I think I heard that support for armel will be withdrawn from Debian 
after Stretch.  If that's true,
there's not much percentage in expending any more effort on this project.

It was worth a try, I guess, but facts are facts and time marches on.

Let me know if there's anything else I can do that would be helpful. For 
example, I've got a couple of sheevaplug devices.  Has anything more 
recent than "2016.09-rc2+dfsg1-1 (Aug 30, 2016)" been
tested on a sheevaplug?

Rick

Send a report that this bug log contains spam.