All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Bug 1847232 <1847232@bugs.launchpad.net>
Cc: Ivan Warren <ivan@vmfacility.fr>,
	qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>
Subject: Re: [Bug 1847232] [NEW] qemu TCG in s390x mode issue with calculating HASH
Date: Tue, 8 Oct 2019 14:11:35 +0200	[thread overview]
Message-ID: <20191008141135.11f5a065.cohuck@redhat.com> (raw)
In-Reply-To: <157053356610.22354.6751604707489617887.malonedeb@gac.canonical.com>

On Tue, 08 Oct 2019 11:19:25 -0000
Ivan Warren via <qemu-devel@nongnu.org> wrote:

> Public bug reported:
> 
> When using go on s390x on Debian x64 (buster) (host) and debian s390x
> (sid) (guest) I run into the following problem :
> 
> The following occurs while trying to build a custom project :
> 
> go: github.com/FactomProject/basen@v0.0.0-20150613233007-fe3947df716e:
> Get
> https://proxy.golang.org/github.com/%21factom%21project/basen/@v/v0.0.0-20150613233007-fe3947df716e.mod:
> local error: tls: bad record MAC
> 
> Doing a git bisect I find that this problem only occurs on and after
> commit 08ef92d556c584c7faf594ff3af46df456276e1b
> 
> Before that commit, all works fine. Past this commit, build always
> fails.

What version are you using? Current master?

Can you please share your command line?

> 
> Without any proof, It looks like a hash calculation bug related to using
> z/Arch vector facilities...

Not an unreasonable guess, cc:ing David in case he has seen that before.


  reply	other threads:[~2019-10-08 12:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 11:19 [Bug 1847232] [NEW] qemu TCG in s390x mode issue with calculating HASH Ivan Warren via
2019-10-08 12:11 ` Cornelia Huck [this message]
2019-10-08 13:35   ` David Hildenbrand
2019-10-08 13:35     ` David Hildenbrand
2019-10-08 14:11     ` Ivan Warren
2019-10-08 14:11       ` Ivan Warren via
2019-10-14  9:53       ` David Hildenbrand
2019-10-14  9:53         ` David Hildenbrand
2019-10-14 10:22         ` David Hildenbrand
2019-10-14 10:22           ` David Hildenbrand
2019-10-17 11:28           ` David Hildenbrand
2019-10-17 11:28             ` David Hildenbrand
2019-10-08 13:41 ` [Bug 1847232] " Thomas Huth
2019-10-14 10:48 ` Ivan Warren via
2019-10-14 11:02 ` Ivan Warren via
2019-10-18 16:17 ` David Hildenbrand
2019-10-23  9:05 ` David Hildenbrand
2019-10-23  9:37 ` Ivan Warren via
2019-10-23 10:05   ` David Hildenbrand
2019-10-23 10:34 ` Ivan Warren via
2020-01-23  5:57 ` Thomas Huth
2020-03-13 11:42 ` John Boero
2020-03-13 11:45 ` John Boero
2020-03-13 13:09 ` carlosedp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191008141135.11f5a065.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=1847232@bugs.launchpad.net \
    --cc=david@redhat.com \
    --cc=ivan@vmfacility.fr \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.