From: Gregor Jasny <gjasny@googlemail.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Samuel CHEMLA <chemla.samuel@gmail.com>
Cc: Sean Young <sean@mess.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>
Subject: Re: [Bug report] dvbv5-zap crash dvb-tool ARMHF builds
Date: Thu, 28 Mar 2019 20:48:34 +0100 [thread overview]
Message-ID: <62429f4e-eabb-8ee9-4137-47540e8131ef@googlemail.com> (raw)
In-Reply-To: <20190328161758.2da2bf4e@coco.lan>
Hello,
On 28.03.19 20:17, Mauro Carvalho Chehab wrote:
> Em Thu, 28 Mar 2019 19:48:35 +0100
> Samuel CHEMLA <chemla.samuel@gmail.com> escreveu:
>> 1) I did reproduce the bug with a serial console, but the serial
>> console was also frozen, and there was no message before freeze.
>
> The only way for a machine to freeze even on serial console is due to
> a very serious Kernel or hardware bug, like a bad lock/semaphore.
Does anything speak against upgrading Debian to latest 1.16.5 release?
Thanks,
Gregor
next prev parent reply other threads:[~2019-03-28 19:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f4b69417-06c3-f9ab-2973-ae23d76088b8@gmail.com>
[not found] ` <29bad771-843c-1dee-906c-6e9475aed7d8@gmail.com>
2019-03-12 15:07 ` [Bug report] dvbv5-zap crash dvb-tool ARMHF builds Gregor Jasny
2019-03-15 22:34 ` Sean Young
2019-03-17 9:52 ` Mauro Carvalho Chehab
2019-03-19 19:45 ` Mauro Carvalho Chehab
2019-03-20 19:38 ` Gregor Jasny
2019-03-21 9:41 ` Sean Young
2019-03-21 11:30 ` Mauro Carvalho Chehab
2019-03-21 19:59 ` Gregor Jasny
[not found] ` <CANJnhGfRtEwAony5Z4rFMPcu58aF2k0G+9NSkMKsq_PhfmSNqw@mail.gmail.com>
2019-03-25 17:08 ` Mauro Carvalho Chehab
2019-03-26 7:35 ` Samuel CHEMLA
2019-03-26 13:26 ` Sean Young
2019-03-26 15:10 ` Samuel CHEMLA
2019-03-26 15:31 ` Mauro Carvalho Chehab
2019-03-28 18:48 ` Samuel CHEMLA
2019-03-28 19:17 ` Mauro Carvalho Chehab
2019-03-28 19:48 ` Gregor Jasny [this message]
2019-03-28 20:04 ` Mauro Carvalho Chehab
2019-04-01 18:58 ` Samuel CHEMLA
2019-04-08 6:32 ` Samuel CHEMLA
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=62429f4e-eabb-8ee9-4137-47540e8131ef@googlemail.com \
--to=gjasny@googlemail.com \
--cc=chemla.samuel@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@s-opensource.com \
--cc=sean@mess.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox