Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #64412 > unrolled thread

Bug#931707: linux: HW_RANDOM_OMAP disabled for arm64 --> please enable

Back to article view | Back to linux.debian.kernel

Contents

  Bug#931707: linux: HW_RANDOM_OMAP disabled for arm64 --> please enable Josua Mayer <josua.mayer97@gmail.com> - 2019-07-09 14:50 +0200
    Bug#931707: linux: HW_RANDOM_OMAP disabled for arm64 --> please enable Ben Hutchings <ben@decadent.org.uk> - 2019-08-05 02:30 +0200
      Bug#931707: linux: HW_RANDOM_OMAP disabled for arm64 --> please enable Riku Voipio <riku.voipio@linaro.org> - 2019-08-07 16:00 +0200
    Bug#931707: marked as done (linux: HW_RANDOM_OMAP disabled for  arm64 --> please enable) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-08-19 07:40 +0200

#64412 — Bug#931707: linux: HW_RANDOM_OMAP disabled for arm64 --> please enable

Source: linux
Severity: normal

Dear Maintainer,

While testing Debian 10 on a Marvell 8040 SoC I found that the rng and SSH were
coming up extremely slow, taking over a minute to start.

This is caused by somebody disabling the rng driver for arm64 kernels a long time ago:
linux (4.14.13-1) unstable; urgency=medium
...
  [ Riku Voipio ]
  * [arm64] disable CONFIG_HW_RANDOM_OMAP until the IRQ storm bug is fixed

What is this IRQ storm bug? Has it been fixed? Can we re-enable this driver?

Yours sincerely
Josua Mayer

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.1.0-trunk-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[toc] | [next] | [standalone]

#64634

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2019-07-09 at 12:43 +0000, Josua Mayer wrote:
> Source: linux
> Severity: normal
> 
> Dear Maintainer,
> 
> While testing Debian 10 on a Marvell 8040 SoC I found that the rng and SSH were
> coming up extremely slow, taking over a minute to start.
> 
> This is caused by somebody disabling the rng driver for arm64 kernels a long time ago:
> linux (4.14.13-1) unstable; urgency=medium
> ...
>   [ Riku Voipio ]
>   * [arm64] disable CONFIG_HW_RANDOM_OMAP until the IRQ storm bug is fixed
> 
> What is this IRQ storm bug? Has it been fixed? Can we re-enable this driver?

Riku, what do you think?  I see that the MacchiatoBin has an Armada 8K
SoC, and there was an upstream commit in February 2018 that could be a
relevant fix:

commit b166be0044913a4ce03564e7c81f172025d78867
Author: Gregory CLEMENT <gregory.clement@bootlin.com>
Date:   Wed Feb 28 15:27:23 2018 +0100

    hwrng: omap - Fix clock resource by adding a register clock

Ben.

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein

[toc] | [prev] | [next] | [standalone]

#64680

On Mon, 5 Aug 2019 at 03:21, Ben Hutchings <ben@decadent.org.uk> wrote:
>
> On Tue, 2019-07-09 at 12:43 +0000, Josua Mayer wrote:
> > Source: linux
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > While testing Debian 10 on a Marvell 8040 SoC I found that the rng and SSH were
> > coming up extremely slow, taking over a minute to start.
> >
> > This is caused by somebody disabling the rng driver for arm64 kernels a long time ago:
> > linux (4.14.13-1) unstable; urgency=medium
> > ...
> >   [ Riku Voipio ]
> >   * [arm64] disable CONFIG_HW_RANDOM_OMAP until the IRQ storm bug is fixed
> >
> > What is this IRQ storm bug? Has it been fixed? Can we re-enable this driver?
>
> Riku, what do you think?  I see that the MacchiatoBin has an Armada 8K
> SoC, and there was an upstream commit in February 2018 that could be a
> relevant fix:
>
> commit b166be0044913a4ce03564e7c81f172025d78867
> Author: Gregory CLEMENT <gregory.clement@bootlin.com>
> Date:   Wed Feb 28 15:27:23 2018 +0100
>
>     hwrng: omap - Fix clock resource by adding a register clock
>
> Ben.

I think the problem was rather in the tianocore firmware than device
tree - but it might be the more accurate device tree fixes it. We can
enable it again, and then re-open the bug dialog with upstream if the
bug is still there.

Riku

> --
> Ben Hutchings
> Beware of programmers who carry screwdrivers. - Leonard Brandwein
>
>

[toc] | [prev] | [next] | [standalone]

#64801 — Bug#931707: marked as done (linux: HW_RANDOM_OMAP disabled for arm64 --> please enable)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 19 Aug 2019 05:32:12 +0000
with message-id <E1hzaH6-0009gS-Pe@fasolo.debian.org>
and subject line Bug#931707: fixed in linux 5.2.9-1
has caused the Debian Bug report #931707,
regarding linux: HW_RANDOM_OMAP disabled for arm64 --> please enable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
931707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931707
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web